Which replication policy is primarily utilized for disaster recovery?

The mirror policy is primarily utilized for disaster recovery because it ensures that an exact copy of the data is maintained in a separate location. This approach provides a synchronous or asynchronous replication of data from one site to another. In the event of a disaster, having a mirror copy allows for quick recovery of business operations, as it minimizes data loss by keeping the backup closely aligned with the original data. Mirroring actively replicates changes in real-time or near-real-time, which is crucial for maintaining operational continuity in the face of unexpected events.

Other policies, such as backup, send, and snapshot policies, serve different purposes. Backup policies generally focus on creating backups of data, which might not be immediately available for recovery. Send policies are used for moving data between systems rather than maintaining a precise, real-time replica. Snapshot policies create point-in-time images of data for recovery but do not provide the continuous replication of active data needed for disaster recovery scenarios. Therefore, the mirror policy stands out as the most effective method for ensuring data availability and resilience in disaster recovery situations.