Data availability in the Atmos Cloud

Hi,

Our customer has an Atmos deployment ( multiple Atmos Systems ) in two DCs ( async distance ). While working on a Archival solution we are thinking on maintaining atleast 4 copies of the data, combining both GeoMirror  and GeoParity ( local DC -- site one sync mirror and distributed Erasure Coding of 9,12 between multiple Atmos and Remote DC- one GeoMirror copy and distributed Erasure Coding 9,12 between Atmos of both the DCs).

The GeoMirror between the two DCs is Asynchronous.

Checksum mechanism is also incorporated with REST calls (along with erasure coding ) to provide end-to-end checksum protection to the Data.

When considering primary site failure as part of disaster recovery, we are also replicating the object metadata so that the copy of the Data will be available ( RO ) at the secondary site in case of the primary site failure.

Atmos documentations states that for Async replication there is no guarantee of when the data will be available at the remote site, i am unable to specify any numbers to my customer of what will be the lag between data in the primary and the  secondary site in case of a site failure (RTO).

Any thoughts/recommendations anyone ?

Regards,

Deb.

Message was edited by: debmdig