Use a checklist to verify that you have satisfied all the requirements to initiate disaster recovery and planned migration of the SDDC management applications.

Table 1. Checklist for Failover and Failback



Activation and Assessment

Verify that the disaster failover or failback is really required. 

For example, an application failure might not be a cause to perform a failover or failback, while an extended region outage is a valid cause.

Also, consider business continuity events such as planned building maintenance or the possibility of a hurricane.


Submit required documentation for approval to the following roles:

  • IT management

  • Business users

  • CTO

Activation Logistics

  • Ensure that all required facilities and personnel are available to start and complete the disaster recovery process.

  • Verify that Site Recovery Manager is available in the recovery region.

  • Verify the replication status of the applications.

  • Verify the state of the NSX Edge in the recovery region.

    • Are the NSX Edges available?

    • Are the IP addresses for VXLAN backed networks correct?

    • Is load balancer on the NSX Edge configured according to the design?

    • Is the firewall on the NSX Edge correctly configured according to the design?

Communication, Initiation and Failover/Failback Validation

  • In the case of a planned migration,

    • Notify the users of the outage.

    • At the scheduled time initiate the failover or failback process.

  • In the case of a disaster recovery failover/failback, notify all stakeholders and initiate the failover or failback process

  • Test the application availability after the completion of failover or failback.

  • Notify all stakeholders of completed failover or failback.

Post Failover/Failback Configuration

In the case of disaster recovery failover/failback, perform the following configuration:

  • Update the backup jobs to include the applications that are now running in Region B.

  • Configure the NSX Controllers and the UDLR Control VM to forward events to vRealize Log Insight in the recovery region.

  • Redirect the log data from the failed over or failed back applications to vRealize Log Insight in the recovery region.

  • Complete a post-recovery assessment. For example, note which items worked and which did not work, and identify places for improvement that you can incorporate back in the recovery plan.