Specifications

ManualsBrandsVMware ManualsComputer equipmentVC-SRM4-A - vCenter Site Recovery Manager

it is necessary to configure the environment with an igroup for each ESX host, rather than creating one

igroup for the entire cluster or group of hosts.

STORAGE RESCANS

In some cases ESX might require a second storage rescan before a newly connected datastore is

recognized. In this case the SRM recovery plan might fail, indicating that a storage location cannot be found

even though the storage has been properly prepared during the DR test or failover.

For VI3 environments a workaround is provided in the VMware SRM release notes here:

http://www.vmware.com/support/srm/srm_10_releasenotes.html - miscellaneous.

In vSphere environments the same workaround can be applied in the GUI by right-clicking the Site Recovery

icon in the upper left of the SRM GUI, selecting Advanced Settings, and adjusting the

SanProvider.hostRescanRepeatCnt value.

PREFIX ON DATASTORE NAMES

By default VMFS datastores that are recovered by SRM during a DR test or failover will be prefixed with a

character string snap-xxxxx. This is standard behavior when a clone of a previously connected datastore is

attached to an ESX server.

In VI3 environments can be configured to maintain datastore names by making the following change in the

SRM xml configuration file at C:\Program Files\VMware\VMware Site Recovery Manager\config\vmware-

dr.xml on the recovery-side SRM server.

Change the line:

<fixRecoveredDatastoreNames>false</fixRecoveredDatastoreNames>

To read:

In vSphere environments right-clicking the Site Recovery icon in the upper left of the SRM GUI, selecting

Advanced Settings, and adjusting the SanProvider.fixRecoveredDatastoreNames value can control this

behavior.

FIREWALL RULES: TCP PORTS

To enable communication in an SRM environment the following ports must be available.

SRM server to vCenter server (local site only):

- SOAP port 8095 (default)

- SRM Client Download HTTP port 8096 (default)

- SRM External API SOAP port 9007 (default)

SRM communication (site-to-site):

- HTTP port 80

Note: SRM creates tunnel to the vCenter server on port 80, then performs an SSL handshake

within that tunnel. (It does not use port 443.)

SRM to storage communication (local and site-to-site):

- HTTP port 80 (default)

- SSL port 443 (if SecureAdmin™ software is configured in Data ONTAP)

Additional steps are required to enable SSL communication between a SRM storage adapter and storage

array. Please see the following kb article for more information

https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb54012

LOG FILES

Log files for SRM are stored in the following location on each SRM server:

C:\Documents and Settings\All Users\Application Data\VMware\VMware Site Recovery Manager\Logs Note

that commands sent to remote site arrays are sent by proxy through the remote SRM server, so checking

logs at both sites is important when troubleshooting.

CLEANING UP SHADOW VMS (DR TEST BUTTON DISABLED)

If the test button does not appear active after establishing protection for a virtual machine, verify that there

were no preexisting shadow virtual machine directories in the temporary datastore at the DR site. If these