Which replication policy is primarily utilized for disaster recovery?

The mirrored policy is primarily utilized for disaster recovery because it involves maintaining a real-time copy of the data at a secondary location. This means that any changes made at the primary site are immediately replicated to the secondary site, ensuring that in the event of a disaster—such as hardware failure, natural disasters, or data corruption—the organization can quickly switch to the mirrored copy with minimal data loss and downtime. This level of synchronization is critical for effective disaster recovery.

In contrast, the other policies serve different purposes. The backup policy typically involves creating periodic copies of data for recovery, but these are not real-time and may result in some data loss if a disaster occurs before the next backup is taken. Asynchronous policy, while useful for replication, does not provide immediate real-time updates, meaning there could be a lag time in which data changes at the primary site are not yet reflected at the secondary site. The snapshot policy focuses on taking point-in-time snapshots of data, which can help with recovery but does not involve ongoing replication or the immediate data protection needed for disaster recovery.