***NOTE: THIS PROCEDURE SHOULD BE COMPLETED BY TIER 1/TIER 2 DURING A DECLARED DISASTER.  IF YOU NEED ASSISTANCE PLEASE REACH OUT TO ENGINEERING.

Note:  Any VPGs that are in the process of being synchronized, cannot be recovered, unless the synchronization is a bitmap synchronization.

To Initiate a Failover:

1. Login to Zerto East or Zerto West. There is no rhyme/reason to how customers are set up in these respective sites, so you may need to login to both to find your customer. Use your XTIUM domain credentials to login
   1. Zerto East - https://10.32.65.222:9669/zvm
   2. Zerto West - https://10.32.67.8:9669/zvm
2. Upon logging in you'll see the Dashboard
3. Find the Live/Test toggle switch and the red FAILOVER option in the bottom right-hand corner of the window. Set the operation to LIVE and click FAILOVER.
   
   The FAILOVER wizard is displayed
   
4.  Select the VPGs to failover.  By default, all VPGs are listed.
   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.)
5. Click NEXT
   The EXECUTION PARAMETERS step is displayed
   
   You can change the following values to use for recovery
   The commit policy
   The checkpoint to use
   The shutdown policy
   The reverse protection settings
6. By Default, the last checkpoint added tot he journal is displayed.  If you want to use this checkpoint, go to the next step.  If you want to change the checkpoint, click the checkpoint.
   
7. Select the checkpoint to use.  Click the refresh button to refresh the list.  You can choose from one of the following checkpoints:
   Latest - recovery is to the latest checkpoint.  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\
   If you do not want to use the latest checkpoint, choose SELECT FROM ALL AVAILABLE CHECKPOINTS.  (By default, this option displays all checkpoints in the system.)
8. Click OK
9. To change the commit policy, click on the field or select the VPG and click EDIT SELECTED.
   To commit the recovery operation automatically, without any checking, select AUTO-COMMIT and 0 minutes
   If you do not want an automatic commit or rollback, select NONE.  (You must manually commit or roll back.)
   To specify the shutdown policy, click the VM SHUTDOWN field and select the shutdown policy:
   No (default) – The protected virtual machines (source side) are not touched before starting the failover.
   Yes – If the protected virtual machines have VMware Tools available, the virtual machines are gracefully shut down
   Force Shutdown – The protected virtual machines are forcibly shut down before starting the failover.
10. Click NEXT. The FAILOVER step is displayed.
    

11. Click START FAILOVER to start the failover.

    (If a commit policy was set with a timeout greater than zero, you can check the failed over virtual machines on the recovery site before committing the failover operation.)

    *** Note: DO NOT TOUCH THE SERVERS IN VCLOUD WHILE THE FAILOVER IS RUNNING.  ONCE THE FAILOVER IS COMPLETE, THE SOURCE SERVERS WILL BE MOVED FROM THE SOURCE DATACENTER***