6.1

Cause
Site Recovery Manager does not check how snapshot volumes are presented to ESXi hosts.
Site Recovery Manager does not support setting the LVM.enableResignature flag to 0. If you set the flag
from 1 to 0, a virtual machine outage might occur each time you perform a test recovery or an actual
recovery occurs.
Setting the LVM.enableResignature flag on ESXi hosts is a host-wide operation. When this flag is set to 1,
during the host rescan or the next host reboot, all snapshot LUNs that are visible to the ESXi host, and that
can be resignatured, are resignatured.
If snapshot volumes unrelated to Site Recovery Manager are forcefully mounted to ESXi hosts on the
recovery site, these LUNs are resignatured as part of a host rescan during a test recovery or an actual
recovery process. As a result, all the virtual machines in these volumes become inaccessible.
Solution
To prevent outages, make sure that no snapshot LUNs that are unrelated to Site Recovery Manager, and that
are forcefully mounted, are visible to ESXi hosts on the recovery site.
Adding Virtual Machines to a Protection Group Fails with an
Unresolved Devices Error
Adding virtual machines to a protection group fails with an error if you did not map the devices of the
virtual machine.
Problem
When you add a virtual machine to a protection group, you see the error Unable to protect VM 'virtual
machine name' due to unresolved devices.
Cause
You did not map the devices of the virtual machine on the protected site to the corresponding devices on the
recovery site.
Solution
Configure the protection settings of the virtual machine as described in “Modifying the Settings of a
Protected Virtual Machine,” on page 59.
Configuring Protection fails with Placeholder Creation Error
When you configure protection on multiple virtual machines, the configuration fails with a placeholder
creation error.
Problem
Configuring protection on a large number of virtual machines at the same time fails with either a
placeholder creation timeout error or a placeholder creation naming error:
n
Placeholder VM creation error:Operation timed out:300 seconds
n
Placeholder VM creation error:The name 'placeholder_name' already exists
This problem occurs when you configure protection in different ways:
n
You create a protection group that contains a datastore or datastores that contain a large number of
virtual machines.
n
You use the Protection Groups > Virtual Machines > Restore All option in the Site Recovery Manager
interface on a large number of virtual machines.
Site Recovery Manager Administration
172 VMware, Inc.