You are here: Disaster Recovery User's Guide > Managing Disaster Recovery Operations > Failing Over to a DR VM (Unplanned)

Failing Over to a DR VM (Unplanned)

You can recover from a primary VM failure by starting its DR VM and using a recent snapshot. When you recover from a VM failure:

Caution: Data that accumulated between the time when the most recent snapshot of the primary VM was completed and the time of the failure is lost.

You can minimize the amount of lost data by setting an appropriate value for your Recovery Point Objective (RPO) when you enable DR protection for your VM (see Enabling Disaster Recovery Protection for a Virtual Machine). Be aware, though, that bandwidth increases as your RPO value drops, so you may not want to set the value too low.

Notes:  
  1. 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.
  2. After an unplanned failover, 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.
  3. 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.

To fail over to a DR VM (Unplanned)

  1. In the Stratus One View Console masthead, click VIRTUAL MACHINES.
  2. On the VIRTUAL MACHINES page, click the DR VM that corresponds to the failed primary VM.
  3. On the VM pane for the DR VM, click the desired snapshot (here, called a recovery point).
  4. Click Recover.

of