You can use the data replication feature of Object Storage Service (OSS) 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 will be 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
Object metadata
Object ACLs
Object tags
Parts and objects that are generated by combining all parts
What will not be replicated in data replication?
Storage classes 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 will not be replicated to C.
Bucket-level configurations
For example, the following items will not be replicated: lifecycle rules, cross-origin resource sharing (CORS) settings, static website hosting settings, hotlink protection settings, and bucket policies
In what scenarios should I use cross-region replication?
Compliance
By default, OSS enables data redundancy. However, if your compliance requirements necessitate replicating data across geographically dispersed data centers, you can utilize cross-region replication (CRR) to ensure regulatory compliance and data availability.
Minimal latency
To minimize data access latency, you can keep object replicas in OSS data centers that are geographically closer to users.
Data backup and disaster recovery
Ensuring robust data security and high availability is essential for your application. To safeguard against regional disruptions, you want to maintain a complete copy of all data in a geographically separate data center. If a catastrophic event, such as an earthquake or tsunami, affects one data center, the replicated data in the secondary location ensures business continuity by enabling rapid recovery.
Data migration
You want 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.
In what scenarios should I use same-region replication?
Compliance
When regulatory mandates require data residency within a specific country or region, you can leverage same-region replication (SRR) to replicate data from the source bucket to multiple destination buckets within the same geographic region.
Synchronization between test and production environments
To ensure the test environment closely mirrors the production environment, you can use SRR to securely and efficiently synchronize data between them. This enables validation of new features in a controlled setting without compromising production data integrity.
Aggregation of logs to a single bucket
If you store logs in multiple buckets or across multiple accounts, you can use SRR to replicate logs to a single bucket within the same region for centralized processing.