posted

2 Comments

VMware Support Alert VMware has become aware of an issue whereby when the Recovery workflow is invoked through the VR 5.1 user interface, the VRMS are instructed to sync to the latest changes from the primary virtual machine. However, since the primary host (or its storage) is not accessible, the sync fails, hence the entire recovery fails. Symptoms include:

  • vSphere Replication 5.1 (VR) cannot recover protected virtual machines after the ESX host on the primary site is down, disconnected from the network, or its storage is not available.
  • Affected deployment topologies: 1 vCenter Server (ROBO), 2 vCenter servers:
  • With VR 5.1, 1 vCenter Server (ROBO) topology (Site A)
  • vSphere Replication is configured on at least one virtual machine from ESX1 to ESX2
  • ESX1 becomes unavailable (such as a host failure, power outage, or network issue) or its storage becomes unavailable
  • An attempt to recover any replicated virtual machine on may ESX2 fail.
  • With VR 5.1, 2 vCenter Servers topology (Primary Site A and Secondary Site B)
  • vSphere Replication is configured on at least one virtual machine from ESX1 (in Site A) to ESX2 (in Site B)
  • The ESX1 host becomes unavailable (such as a host crash, power outage, or network issue) or its storage becomes unavailable
  • An attempt to recover any replicated virtual machine on may Site B fail.

Note: This issue does not occur if the vCenter Server in Site A is also down.

Important Note: This issue does not occur in any deployments of VMware vCenter Site Recovery Manager where vSphere Replication is also being used.

For further updates and more information on this alert, refer to KB article:
vSphere Replication 5.1 (VR) unable to recover protected virtual machines (2035929).