Starting and Stopping Failover Tests
You can test specific VMs in a VPG, a single VPG or multiple VPGs to make sure that if an actual failover is needed, the failover will perform as expected.
Note: You can initiate the failover test from either the protected site or recovery site.
To test failover:
1. In the Zerto User Interface set the operation to TEST and click FAILOVER.
The Failover Test wizard is displayed.
2. Select the VPGs to test. By default, all VPGs are listed.
a) To select specific VMs in a VPG, click the icon next to each VPG to get a list of VMs. The Select VMs to Failover dialog is displayed. By default, all VMs are selected.
b) Select the VMs to test.
Note: Selecting specific VMs in a VPG to failover is not supported when replicating from a vCD site.
At the bottom, the selection details show the amount of data and the total number of virtual machines selected.
The Direction arrow shows the direction of the process: from the protected site to the peer, recovery, site.
3. Click NEXT.
The EXECUTION PARAMETERS step is displayed.
You can select the checkpoint to use for the recovery and see if a boot order and scripts are defined for the VPG.
4. By default, the last checkpoint added to the journal is displayed in the Checkpoint column
■ To use this checkpoint, proceed to the next step.
■ To change the checkpoint, click the link that appears as the checkpoint.
A window appears, displaying a list of the VPGs’ checkpoints.
Latest: Recovery is to the latest checkpoint. This ensures that the data is crash-consistent for the recovery.
When selecting the latest checkpoint, the checkpoint used is the latest at this point.
If a checkpoint is added between this point and starting the failover, this later checkpoint is not used.
Latest Tagged Checkpoint: The recovery operation is to the latest checkpoint added in one of the following situations:
■ By a user.
■ When a failover test was previously performed on the VPG that includes the virtual machine.
■ When the virtual machine was added to an existing VPG after the added virtual machine was synchronized.
5. To use a checkpoint which is not the latest checkpoint, or the latest tagged checkpoint, choose Select from all available checkpoints. By default, this option displays all checkpoints in the system. You can choose to display only automatic, or tagged checkpoints, or any combination of these types.
6. Click OK. A warning appears informing the user if the selected VMs were not protected with the selected checkpoint.
7. Click NEXT.
The FAILOVER TEST step is displayed. The topology shows the number of VPGs and virtual machines being tested to failover to each recovery site. In the following example, 2 VPGs will be failed over to Site6-Ent2-R2, and they contain 5 virtual machines; and 1 VPG will be failed over to Site5-Ent2-P2-R2 and it contains 2 virtual machines.
8. To start the test, click START FAILOVER TEST.
The test starts for the selected VPGs. The test begins with an initialization period during which the new instances are created in AWS. The protected virtual machines are created as new instances in EC2.
The default value for new instances in Zerto Virtual Replication is m3.xlarge except in the Asia Pacific (Seoul) region where they are defined as m4.xlarge instances. If these instances do not meet your needs, you can change this value in the Policies tab of the Site Settings dialog, see
“Configuring Disaster Recovery Policies”, on page 133. You can also change the instance type of new instances when you create or edit a VPG.
If you did not define a private IP for a virtual machine in the VPG definition, during recovery AWS sets the private IP from the defined subnet range.
