Object Storage Service:Replication behavior in special scenarios

Data replication with versioning

The following limitations apply when you use data replication with versioning:

• Enable data replication only between two buckets that have the same versioning state, which is either enabled or disabled. Do not change the versioning state of the source or destination bucket while data is being synchronized.

• Do not pause versioning for the source or destination bucket during data synchronization. To pause versioning, you must first delete the data replication rule.

When you delete an object from a versioning-enabled source bucket, the following scenarios occur:

Data replication with lifecycle rules

Data replication with versioning creates multiple previous versions in the destination bucket, which increases storage consumption. To reduce storage costs, use lifecycle rules to control storage costs and implement custom data retention policies.

When you use data replication with lifecycle rules, note the following:

• Data replication replicates the outcomes of a lifecycle rule from the source bucket to the destination bucket, but not the rule itself. If you want the destination bucket to follow the same lifecycle rule, you must configure the same rule for the destination bucket.

• An object replica in the destination bucket retains the creation time of the original object in the source bucket, not the time when the object is replicated to the destination bucket.

• If a lifecycle rule deletes an object in the source bucket while the object is being replicated, the replication of that object may still be completed. In this case, the object replica is retained in the destination bucket.

• When you use cross-region replication for a versioning-enabled bucket, delete markers from the source bucket are replicated to the destination bucket. This operation makes the delete marker the current version of the object in the destination bucket, and the previous current version becomes a noncurrent version. If the destination bucket has a lifecycle rule to delete noncurrent versions, such as deleting them after one day, the object's noncurrent version is permanently deleted when the condition is met. Therefore, exercise caution when you configure lifecycle rules that delete noncurrent versions to prevent unintended data loss in the destination bucket.

Data replication with server-side encryption

Data replication within the same account supports both unencrypted objects and objects encrypted using server-side encryption with KMS-managed keys or OSS-managed keys (SSE-OSS). For more information, see Server-side encryption.

When you use data replication with server-side encryption, the following scenarios occur:

Data replication with retention policies

After a retention policy (WORM) for a bucket is locked, you can upload and read objects in the bucket. However, you cannot modify (overwrite) or delete objects until their retention period expires.

For more information about retention policies, see Retention policies.

When you use data replication with retention policies, the following scenarios occur: