Georedundancy

Details about our implementation of georedundant S3 storage.

Using the “-mirr” suffix

When you create a bucket with the “-mirr” suffix, all objects in that bucket are mirrored to a different GEO location. This means that each object in both regions has a 1:1 copy. The objects are duplicated using either erasure coding or replication. For more information, see General storage of objects. This option is suitable for data that must remain available in the event of a complete data center failure and requires additional redundancy. The prices for this option are included in your individual contract. Plusserver S3 objects have a minimum billable object size of 128 KB. Smaller objects can be stored but will be billed at 128 KB.

Using the “-repl” suffix

Alternatively, you can create a bucket with the “-repl” suffix to store all objects within that bucket as replication. In this case, the replication of objects is distributed between two GEO locations rather than in a data center. This option provides a lower cost geo-redundancy option compared to the “-mirr” option. Pricing for this option is included in your individual contract. Plusserver S3 objects have a minimum billable object size of 128 KB. Smaller objects can be stored but will be billed at 128 KB.

Differences between the options:

OptionStorageRedundancyExample SiteExample Workloads
-mirrDuplicate Storage with Erasure Coding and Duplicate ReplicationGeoredundant + Site Redundanten-north-2 and de-west-1Production Critical Applications or User Data
-replReplication of objects distributed to both data centersgeoredundant onlyen-north-2 and de-west-1Double backup, cost-effective georedundancy
StandardRegional Storage with Erasure Coding and ReplicationSite Redundant onlyde-north-2 or de-west-1Production Data, Secure Data Storage within one Geolocation
Last modified 2023-10-26: Initial insertion of content. (87587ca)