6.1

Option Action
Change the time that
Site Recovery Manager waits before
removing the snap-xx prefix applied
to recovered datastore names. The
default value is 0 seconds.
Enter a new value in the
storageProvider.fixRecoveredDatastoreNamesDelaySec text box.
Delay host scans during testing and
recovery. The default value is 0
seconds.
SRAs can send responses to Site Recovery Manager before a promoted
storage device on the recovery site is available to the ESXi hosts. When
Site Recovery Manager receives a response from an SRA, it rescans the
storage devices. If the storage devices are not fully available yet, ESXi
Server does not detect them and Site Recovery Manager does not find the
replicated devices when it rescans. Datastores are not created and
recovered virtual machines cannot be found.
To delay the start of storage rescans until they are available on the ESXi
hosts, enter a new value in the storageProvider.hostRescanDelaySec text
box.
Only change this value if you experience problems with unavailable
datastores.
Repeat host scans during testing
and recovery. The default value is 1.
Enter a new value in the storageProvider.hostRescanRepeatCnt text box.
Some storage arrays require more than one rescan, for example to discover
the snapshots of failed-over LUNs. In previous releases, you might have
used the storageProvider.hostRescanRepeatCnt parameter to introduce a
delay in recoveries. Use the storageProvider.hostRescanDelaySec
parameter instead.
Change the interval that
Site Recovery Manager waits for
each HBA rescan to complete. The
default value is 300 seconds.
Enter a new value in the storageProvider.hostRescanTimeoutSec text box.
Set the number of times that
Site Recovery Manager attempts to
resignature a VMFS volume. The
default value is 1.
Enter a new value in the storageProvider.resignatureFailureRetryCount
text box.
Set a timeout for resignaturing a
VMFS volume. The default value is
900 seconds.
Enter a new value in the storageProvider.resignatureTimeoutSec text box.
If you change the storageProvider.hostRescanTimeoutSec setting,
increase the storageProvider.resignatureTimeoutSec setting to the same
timeout that you use for storageProvider.hostRescanTimeoutSec.
Identify VMX file paths that
Site Recovery Manager should not
consider as potential VMX file
candidates after Storage vMotion.
The default value is .snapshot,
Some arrays create VMX file paths that the
storageProvider.storageVmotionVmxSearch search algorithm should
ignore. Enter a comma-separated list of strings in the
storageProvider.storageVmotionVmxFilePathsToSkip text box to identify
VMX file paths to ignore after Storage vMotion. Site Recovery Manager
does not consider VMX file paths that contain one or more of these strings
as potential candidate VMX files after Storage vMotion.
Search for VMX files in recovered
datastores to identify virtual
machines that Storage vMotion has
moved before or during a test or a
recovery. The default value is true.
The option is selected by default. Deselect the
storageProvider.storageVmotionVmxSearch check box to disable this
option.
Set the timeout in seconds for local
stretched devices to be matched to
the corresponding remote stretched
devices. The default is 300 seconds.
Enter the new value in the
storageProvider.stretchedDevicesMatchTimeout text box.
Set the number of parallel xVC-
vMotion requests per host. This
limit applies to both source and
target hosts. The default value is 2.
Enter the new value in the storageProvider.vmMigrationLimitPerHost
text box.
Set the timeout in seconds to wait
for newly discovered datastores to
become accessible. The default
value is 60 seconds.
Enter the new value in the
storageProvider.waitForAccessibleDatastoreTimeoutSec text box.
Chapter 12 Advanced Site Recovery Manager Configuration
VMware, Inc. 145