6.1

Table Of Contents
n
You use the Site Recovery Manager API to protect a large number of virtual machines manually.
Cause
The infrastructure on the recovery site is unable to handle the volume of concurrent creations of placeholder
virtual machines.
Solution
Increase the replication.placeholderVmCreationTimeout setting from the default of 300 seconds. See
“Change Replication Settings,” on page 141.
You do not need to restart Site Recovery Manager Server after changing this setting. Site Recovery Manager
applies the setting the next time that you configure protection on a virtual machine.
Rapid Deletion and Recreation of Placeholders Fails
If you delete all of the placeholder virtual machines from a datastore, unmount the datastore, and remount
the datastore, recreation of the placeholder virtual machines might fail.
Problem
Recreating the placeholders too rapidly after unmounting the datastore can fail with the error
NoCompatibleHostFound.
Cause
The associations between ESXi hosts and datastores are updated at 10-minute intervals. If you recreate the
placeholders after unmounting and remounting the datastore but before the next update, the host cannot be
found.
Solution
Wait for more than 10 minutes after unmounting and remounting the datastore before you recreate the
placeholder virtual machines.
Planned Migration Fails Because Host is in an Incorrect State
If you put the ESXi host on the recovery site into maintenance mode during a planned migration, the
planned migration fails.
Problem
Planned migration fails with the error Error - The operation is not allowed in the current state of
the host.
Cause
Site Recovery Manager cannot power on virtual machines on the recovery site when the ESXi host on the
recovery site is in maintenance mode.
Solution
Exit maintenance mode on the ESXi host on the recovery site and rerun the planned migration.
Chapter 15 Troubleshooting Site Recovery Manager
VMware, Inc. 173