Disaster Recovery Operations

This topic provides an overview of the DR operations.

Migrating to a DR VM (Planned)

When a system containing primary VMs must be shut down (for example, when performing maintenance), you can migrate each primary VM to a DR VM running on a second system with no data loss. Once the DR VMs are running, you can then shut down the first system. See Migrating to a DR VM (Planned) for details.

Failing Over to a DR VM (Unplanned)

If a primary VM fails, you can recover--with minimal data loss--by failing over to the DR VM. In this case, the DR VM is started using data from a selected snapshot. See Failing Over to a DR VM (Unplanned) for details.

Migrating Current Data Back to the Primary VM

If a DR VM has been running long enough to accumulate new data that you want to preserve, you can migrate this data back to the primary VM with no data loss. See Migrating Current Data Back to the Primary VM for details.

Reverting to the Original Data on the Primary VM

If a DR VM has been running for a brief period of time and has not accumulated any data that you wish to preserve, you can revert back to the primary VM with its original data. You might choose to do this if the primary VM unexpectedly becomes available soon after an unplanned failover. See Reverting to the Original Data on the Primary VM for details.

Taking an Unscheduled Snapshot

If you suspect that a system failure is imminent, or if you are about to perform an activity that could result in a system failure, you can take an unscheduled snapshot to capture the most recent data. See Taking an Unscheduled Snapshot for details.