Bucket Synchronization Policies: Difference between revisions

From OSNEXUS Online Documentation Site
Jump to navigation Jump to search
No edit summary
Line 27: Line 27:


=== Multi-site is setup with full zone replication selected ===
=== Multi-site is setup with full zone replication selected ===
[[File:Bucket Sync - Multi-Site Full Zone Replication.jpg|none|thumb|800x800px]]
[[index.php?title=File:Bucket_Sync_-_Multi-Site_Full_Zone_Replication.jpg|link=File:Bucket_Sync_-_Multi-Site_Full_Zone_Replication.jpg|800x800px]]

Revision as of 05:15, 6 October 2025

index.php?title=Category:Admin guide

Multi-Site Setup with and without bucket sync policies


This document goes over the different use cases of bucket sync policies and zone level multi-site object setup.

Zones: Three zones are depicted: us-east1 (Primary), us-west1 (Secondary), and us-west2 (Secondary).

Primary to Secondary Replication:

If "symmetrical replication" is chosen, default "enable" rules exist between the primary and each secondary zone.

If "bucket level replication" is chosen, default "deny" rules (default-deny-us-east1-us-west1, default-deny-us-east1-us-west2) are created in "allowed" state, meaning they prevent replication until specific bucket rules are added.

Secondary to Secondary Replication:

No default deny rules are created between secondary zones (e.g., default-deny-us-west1-us-west2 is not automatically created).

To sync buckets between us-west1 and us-west2, a specific "enable" rule like enable-us-west1-us-west2 needs to be manually created. This rule is directional and only applies to specific buckets once bucket-specific rules are added.


Note : While the AWS replication feature allows bucket replication within the same zone, RGW does not allow it at the moment.

Multi-site is setup with full zone replication selected

link=File:Bucket_Sync_-_Multi-Site_Full_Zone_Replication.jpg|800x800px