You can use the OSS data replication feature to replicate data from one bucket to another. The two buckets can be in the same region or different regions and can belong to the same account or different accounts.
What content is replicated in data replication?
Historical objects that exist before the replication rule takes effect and objects that are added or updated after the replication rule takes effect
KMS-encrypted objects
Object metadata
Object ACL
Object tags
Parts and objects that are generated by combining all parts
What content is not replicated in data replication?
Storage class of objects
Last access time of objects (x-oss-last-access-time)
Object replicas generated by other replication rules
For example, if you configure two replication rules (A to B and B to C), data that is replicated from A to B is not replicated to C
Bucket-level configurations
For example, lifecycle rules, cross-domain settings, static website hosting, hotlink protection, bucket policies, and other configurations
When should I use cross-region replication?
Compliance requirements
OSS provides a data redundancy mechanism for objects. However, to meet compliance requirements, the replicas must be stored in multiple data centers that are located at a geographical distance from each other. CRR allows you to replicate data between geographically distant data centers to meet compliance requirements.
Minimal latency
To minimize the latency when users access objects, you can maintain object replicas in OSS data centers that are geographically closer to the users.
Data backup and disaster recovery
You have strict requirements for data security and availability. You want all data written in one data center replicated to another data center. If one data center is damaged in a catastrophic event such as an earthquake or a tsunami, you can use data that is backed up in the other data center.
Data migration
To ensure business continuity, you may need to migrate data from one data center to another data center.
Operational purposes
You have compute clusters that are deployed in two data centers to analyze the same group of objects. You can maintain the replicas of the objects in the two regions.
When should I use same-region replication?
Compliance requirements
When local regulatory compliance requires that data cannot leave your country or region, you can use same-region replication to store replicas of data from the source bucket in multiple destination buckets within the same region.
Synchronization between test and production environments
To ensure that the test environment simulates the production environment as closely as possible, you can use same-region replication to quickly and securely synchronize data between the two environments. This allows you to verify new features without affecting actual production data.
Aggregation of logs to a single bucket
If you store logs in multiple buckets or across multiple accounts, you can use same-region replication to replicate logs to a single bucket within the same region for centralized processing.