After you configure a cross-region replication (CRR) rule for a source bucket and a destination bucket, if the objects in the source bucket are not replicated to the destination bucket, check the following reasons to locate and resolve the problem.
In CRR, data is asynchronously replicated in near real time. It takes several minutes to several hours to copy data from the source bucket to the destination bucket based on the size of the data. If objects in the source bucket are large in size, wait a moment and check whether the objects are replicated to the destination bucket.
- Source bucket configurations
- Check whether the status of the data synchronization task is Enabled.
- Check whether the prefix of the objects to replicate is correctly configured.
- To synchronize objects whose names contained a specific prefix from the source bucket to the destination bucket, set the Prefix parameter to the prefix when you configure the data replication rule. For example, if you set the Prefix parameter to log, only objects whose names contain the log prefix, such as log/date1.txt and log/date2.txt, are replicated. Objects whose names do not contain the log prefix, such as date3.txt, are not replicated.
- To synchronize all objects from the source bucket to the destination bucket, set the Prefix parameter to empty.
- Replication mechanism
If an object in the source bucket is replicated from a bucket rather than the destination bucket based on another data replication rule, the object is not replicated to the destination bucket. For example, if you configure a data replication rule to replicate objects from Bucket A to Bucket B and another replication rule to replicate objects from Bucket B to Bucket C, objects that are replicated from Bucket A to Bucket B are not replicated to Bucket C.
- Versioning status
Both the source bucket and destination bucket must be versioned or unversioned.