Written disaster recovery plan with continual updating
Disaster recovery (DR) is the science of returning a system to operating status after a site-wide disaster.
DR enables business continuity for significant data center failures for which high availability features cannot cover.
Achieving Low RPO with Scheduled Mirroring For files in your Map R cluster, use mirroring on a scheduled basis to ensure remote mirrors frequently get the latest updates.
The window of potential data loss depends on how frequently your mirroring operations are scheduled.
This feature is generally used to recover from data corruption due to application or user error.
For more information, please see the Map R Snapshots tech brief. The recovery point objective (RPO) is a planned estimate on how much data the organization can afford to lose in case of a disaster.
Lower RPO and RTO values enable greater protection against data loss and downtime, but those will take more resources to implement.
The snapshot will include all data in the volume, including files, Map R-DB database tables and documents, and Map R Streams topics.Mirroring is more expensive due to the redundant hardware in the remote mirrors, but enables lower risk of data loss.The Map R Converged Data Platform includes backup and mirroring capabilities to protect against data loss after a site-wide disaster.For example, if your master cluster is in New York, and you want to mirror to Sydney and Singapore, it would make sense to mirror from New York to Sydney, and then have a separate mirror chain from Sydney to Singapore.With database tables and streams topics, you automatically get low RPO since table and stream replication continuously transfers all database and topic updates to the remote clusters.