Users Guide

Troubleshooting tips

In certain environments, you may need to implement one or all the following settings to enable successful operation of the SRA. Do

not change these settings unless advised by technical support. These are nonstandard settings; therefore, you should use them only

if your environment is experiencing the symptoms described for the change.

Datastore expected to be automounted

Error: Failed to recover Datastore ‘XYZZY’. Datastore residing on recovered devices and expected to be automounted during HBA

rescan cannot be found.

Potential Fix: Modify C:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\config

\vmware-dr.xml le and add the following to the <storageProvider> section.

<waitForRecoveredDatastoreTimeoutSec>300waitForRecoveredDatastoreTimeoutSec>300>

<waitForAccessibleDatastoreTimeoutSec>900waitForAccessibleDatastoreTimeoutSec>900>

</storageProvider>

You must restart the VMware vCenter Site Recovery Manager Server after applying this change. This increases the timeout for

snapshot mount operations.

Unable to communicate with remote host

Error: Failed to recover datastore 'CG26'. VMFS virtual disk residing on recovered devices '"67:82:BC:B0:00:28:AB:8B:

00:00:41:C8:50:C8:26:BA"' cannot be found. Recovered device '67:82:BC:B0:00:28:AB:8B:00:00:41:C8:50:C8:26:BA' not found after

HBA rescan. Failed to rescan HBAs on host '10.26.25.108'. Unable to communicate with the remote host, since it is disconnected.

Possible Solution 1: (For vCenter Server 5.x only) Modify C:\Program Files\VMware\ Infrastructure\tomcat\conf

\wrapper.conf and change the following:

wrapper.java.additional.9="-Xmx2048M"

This modication changes the maximum disk space for the VMware vCenter Inventory Services. Restart the vCenter Server to apply

this change.

Possible Solution 2: (For ESXi 5.x Only) Modify /etc/vmware/vpxa/vpxa.cfg and add the following section to increase the

ping timeout for SOAP requests.

<vmomi>

<calls>false</calls>