Migrating to a DR VM (Planned)
For planned outages (for example, system or site maintenance), you can migrate to a DR VM. When you migrate to a DR VM:
- DR protection is paused.
- The primary VM is gracefully shut down.
- A snapshot of the final state of the primary VM is taken.
- The final snapshot is replicated to the DR VM.
- The DR VM boots from the final snapshot.
Notes:
- No data is lost during a planned migration. However, for a period of time, neither the primary VM nor the DR VM will be running.
- During the failover, monitor the primary VM to make sure it shuts down. If it does not, shut it down manually by going into the guest operating system and performing a shutdown. See Enabling Disaster Recovery Protection for a Virtual Machine for more information.
- After a planned migration, the DR VM is not DR protected (that is, no snapshots of it are taken). Snapshots and updates start when you click Begin Migration. To provide maximum protection, do this as soon as the other system is running again and connected.
- When the DR VM is booted, it starts up with all network interfaces disabled. You can enable the networks by using the Reprovision Virtual Machine wizard in the everRun Availability Console on the DR system.
- If you initiate a planned migration to a DR VM while a snapshot is being transferred to the DR system, the snapshot will be aborted.
To migrate to a DR VM (Planned)
- In the Stratus One View Console masthead, click VIRTUAL MACHINES.
- On the VIRTUAL MACHINES page, click the primary VM that you want to migrate.
- In the action bar, click Start Migration.
- When the migration is complete, the message Disaster Recovery has migrated to the DR VM appears.