VMware Live Recovery: Checklist for Test Recovery and Planned Migration

Products

• VMware Live Recovery

Issue/Introduction

This KB article details the mandatory pre-execution checks and operational procedures required before initiating a Test Recovery, Planned Migration, or Disaster Recovery (DR) plan in VMware Live Recovery / Site Recovery Manager (SRM).

Environment

VMware Live Recovery 9.x

Resolution

Follow the two-phase validation and execution process outlined below to ensure a smooth recovery operation and prevent VMware Live Recovery workflow failures.

Phase 1: Pre-Execution Health Checklist

Perform and verify all of the following checks in the SRM / VMware Live Recovery interface prior to triggering any recovery workflow:

1. Ensure SRM site pairing as Connected.
   
   
2. Ensure all target Protection Groups (PGs) and Recovery Plans (RPs) are free of error banners or warnings.
   
   
3. Verify that all member virtual machines in the target PGs and RPs show no underlying vSphere errors, uncommitted snapshots, or missing file dependencies.
   
   
4. Check the Storage Replication Adapter (SRA) status for errors.
   Click Discover Devices under SRA pairs and ensure no LUNs/datastores show a status of Unknown or In Progress.
   
   
5. Validate that network mappings, IP customization rules, and target port groups are correctly configured for the recovery site.

Phase 2: Test Recovery | Disaster Recovery Execution Procedure

1. Ensure the target recovery site has full local connectivity to its local vCenter Server, ESXi hosts, and underlying physical storage arrays.

2. Initiate the Test / Disaster Recovery Plan based on the requirement:

   • Access the recovery site SRM appliance management interface at: https://<Recovery_SRM_IP>/dr

   • Select the target Recovery Plan.

   • Click Run and choose the Disaster Recovery option.

3. Post-Failover Cleanup:

   • Once virtual machines are successfully powered on and verified at the recovery site, remove any active site isolation configurations.

4. Execute Reprotect Workflow:

   • After network communication and site pairing are fully restored between both sites, execute the Reprotect command in SRM.

   • This step reverses the replication direction and creates placeholder VMs at the original primary site for future failback operations.

Note : Running a recovery plan while SRA devices are in an In Progress or Unknown state can lead to storage mounting failures and inconsistent datastore states at the recovery site. Always wait for device discovery to complete fully before proceeding.

Additional Information

Refer : Performing a Planned Migration or Disaster Recovery by Running a Recovery Plan