When you have set a replication rule you may wish to check the status of the replication. This can only be done on the source account, and on a file-by-file basis.
Note that a source bucket may be used in more than one rule. Currently, we restrict you to leveraging the same Bucket in two rules only. The third rule will fail when you try to create it.
The file status returned also manages these multiple rule scenarios.
How to check the status of individual files included in your replication rule:
1: Navigate to the “Buckets” page of your account and locate the source bucket that you have set the replication rule for. Click the button labeled “Upload/Download”
2: This will show you a list of the files included in the bucket, navigate to one of the files included in the replication rule and click the “i” icon next to it to view the file’s information.
3: With the file information displayed, locate the area labeled “Replication Status” to see the status of that file. It will read as either “completed”, “pending”, or “failed”
What does the Replication Status mean?
As mentioned before, there are three possible statuses that you will see for the file. Below you will find a brief explanation of each:
Completed: This status indicates the file has successfully replicated to the destination bucket.
For multiple rules, this means both rules have completed successfully.
Pending: This status indicates that this is a file that is in the process of being replicated, or waiting to be replicated. For multiple rules, this means at least one rule is in process.
Failed: This status indicates that the file has encountered an error that cannot be resolved. Files that are given this status will not be attempted again. In the case of a file that has failed to replicate, the only way to attempt it again is with a new replication rule.
For multiple rules, this status means at least one rule has failed. You’ll need to check the destination to understand which rule failed.
Replica: For files that are the result of a replication, the replication status will return “replica”. Note that replica files cannot be used for further replication activities.
What if I see a Failed state? What can I do?
A failed state is a non-recoverable state of the file. We do not expect this state to be resolved, and this file will not be re-evaluated in its current state.
A few areas to think about for what is causing a Failed state:
- Permissions: Ensure that the permissions we created for replication are still there. We need read access to the source for the authentication key, and write access for the destination authentication key. We create these keys when the Web UI completes successfully. Removing and changing the properties of how these are set up may cause failures.
- Object Lock and Encryption: Object lock is required to be set up with the destination account when the source has object lock setup. Similarly, for encryption, SSE-C, managed by the client, is not supported. These may also return failed states.
- Part Files: When uploading large files, replication for large files is only done after the large files are finalized (following a call to b2_finish_large_file ). Once completed all parts will be queued for replication. Until the final b2_finish_large_file is executed, the part files will be ignored by the replication process.
If you believe that your file is a valid file and you’d like to retry it, the best way is to upload the file again, creating a new version. This will trigger the file to be re-evaluated.
For more information about Cloud Replication see here.
For further assistance with Cloud Replication please email support at: B2Feedback@backblaze.com