From a9485af881379ea45ab203eb25c2d3f16db7c925 Mon Sep 17 00:00:00 2001 From: Yann Chaysinh Date: Thu, 14 Aug 2025 14:47:23 +0200 Subject: [PATCH] Added link to the checksum replication before using the --filestore parameter of the transfer-files command --- .../jfrog-cli/cli-for-jfrog-cloud-transfer.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/jfrog-applications/jfrog-cli/cli-for-jfrog-cloud-transfer.md b/jfrog-applications/jfrog-cli/cli-for-jfrog-cloud-transfer.md index d5216495..61d70ddf 100644 --- a/jfrog-applications/jfrog-cli/cli-for-jfrog-cloud-transfer.md +++ b/jfrog-applications/jfrog-cli/cli-for-jfrog-cloud-transfer.md @@ -482,6 +482,12 @@ When your self-hosted Artifactory hosts hundreds of terabytes of binaries, you m The `jf rt transfer-files` command transfers the metadata of the binaries to the database (file paths, file names, properties, and statistics). The command also transfers the binaries that have been created and modified after you copy the filestore. +**Note** + +> Make sure to first enable the [checksum replication](https://jfrog.com/help/r/jfrog-rest-apis/configure-checksum-replication) + +*** + To run the file transfer after you copy the filestore, add the `--filestore` command option to the `jf rt transfer-files` command. #### Using Replication