Section | Parameter | Description |
Configure Destination Bucket | Source Bucket | The region and name of the source bucket are displayed. You do not need to specify the parameter. |
Destination Bucket | Select Specify a bucket that belongs to another Alibaba Cloud account, select a region from the Region drop-down list, and then enter the name of the destination bucket. |
Configure Replication Policy | Objects to Replicate | Select the objects that you want to replicate to the destination bucket. Valid values: All Objects in Source Bucket: OSS replicates all objects from the source bucket to the destination bucket. Objects with Specified Prefix: OSS replicates the objects whose names contain a specific prefix from the source bucket to the destination bucket. You can specify up to 10 prefixes.
|
Replication Policy | Configure the data replication mode. Valid values: Note After you create a data replication rule, changes to the x-oss-last-access-time attribute of the objects and the storage class conversion of objects in the source bucket because of lifecycle rules or the CopyObject operation are not synchronized to the destination bucket. Add/Change (applicable to disaster recovery): OSS replicates only object creation and update operations from the source bucket to the destination bucket. Important If this replication policy is applied, only objects that are uploaded or updated after the policy takes effect will be replicated to the destination bucket, and objects deleted from the source bucket will not be deleted from the destination bucket. This policy effectively prevents data loss in the destination bucket resulting from manual deletion or automated deletion triggered by lifecycle policies in the source bucket. Add/Delete/Change (applicable to scenarios in which multiple users or applications need to share and access the same dataset): OSS replicates object creation, update, and deletion operations from the source bucket to the destination bucket. Important Besides replication of newly uploaded and updated objects, this replication policy includes replication of deletion, which ensures the consistency of data. This policy is applicable to scenarios in which multiple users or applications need to share and access the same dataset. Objects deleted from the source bucket, either manually or through lifecycle policies, will also be deleted from the destination bucket. Objects cannot be recovered after they are deleted.
If you perform multipart upload to upload an object to the source bucket, each uploaded part is replicated to the destination bucket. The complete object that is obtained by calling the CompleteMultipartUpload operation is also replicated to the destination bucket. For more information, see Use data replication with versioning. |
Replicate Historical Data | Specify whether to replicate historical data (data that exists in the source bucket before you enable CRR) to the destination bucket. |
Replicate Objects Encrypted Based on KMS | Specify whether to replicate objects encrypted based on KMS from the source bucket to the destination bucket. Valid values: Yes: If KMS-based encryption is configured for the destination bucket or objects in the source bucket, the objects are replicated to the destination bucket. If you set Replicate Objects Encrypted Based on KMS to Yes, you must specify the CMK ID parameter. Note You can call the HeadObject operation to query the encryption rules of objects in the source bucket and the GetBucketEncryption operation to query the encryption rules of the destination bucket. No: Objects that are encrypted based on KMS are not replicated to the destination bucket.
|
CMK ID | Specify the ARN of the KMS key. For more information about how to obtain the ARN of a KMS key, see Create a key in the KMS instance. |
RAM Role Name | Select the RAM role that you created in Step 1 from the drop-down list. |
| Acceleration Type | Transfer Acceleration is supported only when the source and destination buckets are respectively located in a region in the Chinese mainland and a region outside the Chinese mainland. If you enable transfer acceleration, you are charged transfer acceleration fees. For more information, see Transfer acceleration fees. |
RTC | Note RTC is available in the following regions: China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), and China (Shenzhen). RTC is available in the following regions: US (Silicon Valley) and US (Virginia).
After Replication Time Control (RTC) is enabled, OSS replicates most of the objects that you uploaded to OSS within a few seconds and replicates 99.99% of objects within 10 minutes. For more information, see RTC. You are charged when you enable RTC. For more information, see RTC traffic fees. |