"Error - Operation timed out” during failover operation from Site B to Site A

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:
On a stretched storage environment using IBM SVCSRA Version 3.3.3 and 3.4.0, you experience these symptoms:

• Failover operation from Site B to Site A fails.
• You see the error:
  
  Operation timed out.

Environment

VMware Site Recovery Manager 8.2.x

Cause

This issue occurs because after running Disaster Recovery when the Site A is down, the LUNs get unmapped from the protected site.

Resolution

This is a known issue affecting VMware Site Recovery Manager 8.2.x.

Currently, there is no resolution.

Workaround:
To workaround this issue, add this parameter in the vmware-dr.xml file on both the SRM servers before running the Disaster Recovery operation.

<storage>
    <adapterRootPath>D:\SRM\storage\sra\</adapterRootPath>
    <commandTimeout>600</commandTimeout>
    <perlPath>D:\SRM\external\perl\perl\bin\perl.exe</perlPath>
   <forcePrepareAndReverseReplicationForNoopDevices>true</forcePrepareAndReverseReplicationForNoopDevices>
</storage>

Once completed, restart the SRM service.

Notes:

• For SRM-Windows, restart the “VMware vCenter Site Recovery Manager server” service.
• If the DR workflow is already executed without the above workaround, then the LUNs needs to be mapped manually to the ESXi hosts after bringing the Site A to run the Failover operations from Site B to Site A.