4.1

Cause
This error usually occurs when a virtual machine has been recently created but its files have not yet been
replicated to the
recovery site. For instance, you have created a virtual machine at the protected site, added it
to a protection group, and then tested or run a recovery plan that includes the new virtual machine. If the
virtual machine files have not yet been replicated to the recovery site, the recovery plan cannot recover the
virtual machine.
This problem can also occur if the virtual machine files have been replicated but then moved by a recovery site
administrator using Storage vMotion or a similar tool.
Solution
Make sure that all virtual machines in a protection group have been replicated to the recovery site before you
test or run a recovery plan for the protection group. The virtual machine files can be missing even if the
corresponding placeholder virtual machine exists. Placeholders are created by SRM, not by array replication,
and do not include the files necessary to recover a virtual machine.
Recovery Plan Time-Out During the Change Network Settings Step
When you are testing or running a recovery plan and it fails during the Change Network Settings step, verify
that the time-out for this step is long enough, and that the requested network settings can be provided by the
recovery network.
Problem
When attempting to recover a virtual machine, the Change Network Settings step of a recovery plan fails with
a Timed Out error.
Cause
If the network settings for the virtual machine’s guest operating system are being customized as part of
recovery, this error indicates that the virtual machine failed to report the new network settings within the
allotted amount of time.
Solution
1 Ensure that the latest version of VMware Tools is installed on all protected virtual machines.
VMware Tools is required for IP customization.
2 Edit the recovery plan to increase the Change Network Settings timeout value.
The default timeout is 300 seconds. A shorter timeout might not allow enough time for the guest operating
system to boot and report that it has successfully changed its network settings. Some virtual machines
might require a longer timeout than the default.
3 If the virtual machine is configured as a DHCP client, verify that a DHCP server is available on the recovery
network.
4 If the virtual machine is configured with a static IP address, verify that the address is available and not in
use on the recovery network.
What to do next
The customization process creates log files on each virtual machine. On Windows, these log files are written
in the C:\windows\temp\vmware-imc\ directory. On Linux, these log files are written in the /var/log/vmware-
imc/ directory. Review the log files for more information about errors that prevented the step from completing
in time.
Chapter 6 Troubleshooting SRM
VMware, Inc. 67