System information

Cause
This problem can occur for one of the following reasons.
n
The VMware Tools package is not installed on the virtual machine that you are recovering.
n
The cluster on the recovery site is experiencing heavy resource use while trying to simultaneously
recover multiple virtual machines. In this case you can increase certain timeout settings to allow more
time for tasks to complete. See “Change Recovery Settings,” on page 105.
Solution
1 Verify that VMware Tools is installed on the virtual machine that you are recovering.
2 Check the available capacity on the recovery site.
If the recovery site is experiencing heavy resource use, increasing the timeout period for guest
customization can resolve the issue.
a In the vSphere Web Client, click Site Recovery > Sites, select a site and click Manage > Advanced
Settings.
b Select Recovery and click Edit.
c Increase the recovery.customizationTimeout parameter from the default of 600 seconds.
d Increase the recovery.powerOnTimeout parameter from the default of 300 seconds.
3 Run the recovery again.
Recovery Fails with Unavailable Host and Datastore Error
Recovery or test recovery fails with an error about host hardware and datastores being unavailable if you
run the recovery or test shortly after changes occur in the vCenter Server inventory.
Problem
Recovery or test recovery fails with the error No host with hardware version '7' and datastore 'ds_id'
which are powered on and not in maintenance mode are available....
Cause
Site Recovery Manager Server keeps a cache of the host inventory state. Sometimes when recent changes
occur to the inventory, for example if a host becomes inaccessible, is disconnected, or loses its connection to
some of the datastores, Site Recovery Manager Server can require up to 15 minutes to update its cache. If
Site Recovery Manager Server has the incorrect host inventory state in its cache, a recovery or test recovery
might fail.
Solution
Wait for 15 minutes before running a recovery if you change the host inventory. If you receive the error
again, wait for 15 minutes and rerun the recovery.
Reprotect Fails with a vSphere Replication Timeout Error
When you run reprotect on a recovery plan that contains vSphere Replication protection groups, the
operation times out with an error.
Problem
Reprotect operations on recovery plans that contain vSphere Replication protection groups fail with the
error
Operation timed out: 7200 seconds VR synchronization failed for VRM
group <Unavailable>. Operation timed out: 7200 seconds
Site Recovery Manager Administration
140 VMware, Inc.