4.0

Troubleshooting SRM 6
If you have problems with storage replication, site pairing, or guest customization, you can try to troubleshoot
the problem. To help identify the cause, you might need to collect SRM server or client log files to review or
send to VMware Support.
Errors encountered during SRM operations are displayed in error dialogs or shown in the Recent Tasks
window. Most errors also generate an entry in an SRM log files. It is important to check the recent tasks and
log files for the recovery site and the protected site.
When searching for the cause of a problem, also check the VMware knowledge base at
http://kb.vmware.com.
This chapter includes the following topics:
n
“No Replicated Datastores Listed,” on page 63
n
“Inconsistent Mount Points Warning When Configuring NFS Arrays,” on page 64
n
“Array Script Files Not Found,” on page 64
n
“Expected Virtual Machine File Path Cannot Be Found,” on page 64
n
“Recovery Plan Time-Out During the Change Network Settings Step,” on page 65
n
“Collecting SRM Log Files,” on page 66
No Replicated Datastores Listed
If the Review Replicated Datastores page does not show any replicated datastores after you have configured
the array managers, this usually indicates that there are no virtual machines on any datastore that uses the
array you are configuring.
Problem
After you complete the Configure Array Managers task, the protected site and recovery site arrays are
discovered successfully, but the Review Replicated Datastores page shows no replicated datastores.
Cause
The Review Replicated Datastores page shows only the replicated datastores that use the array and host at
least one virtual machine. Replicated datastores that do not have virtual machines are not listed.
Solution
1 Ask your storage management team which datastores are hosted on the arrays that you have configured
to work with SRM.
2 In the vSphere Client, create a virtual machine on each of the datastores managed by the arrays.
VMware, Inc.
63