For array-based replication, the SAN provider is the interface between Site Recovery Manager and your storage replication adapter (SRA). Some SRAs require you to change default SAN provider values. You can change the default timeout values and other behaviors of the Site Recovery Manager SAN provider.

About this task

You can change settings for resignaturing, fixing datastore names, host rescan counts, and timeouts. For more information about these values, see the SRA documentation from your array vendor.

Procedure

  1. Click Sites in the Site Recovery Manager interface, right-click the site on which to change settings, and select Advanced Settings.
  2. Click storageProvider.
  3. Modify the SAN provider settings.

    Option

    Action

    Make Site Recovery Manager attempt to detach and reattach LUNs with duplicate volumes

    Select the storageProvider.autoDetachLUNsWithDuplicateVolume check box.

    Set the LVM.EnableResignature flag on ESXi hosts during test and recovery

    In the storageProvider.autoResignatureMode text box, type 0 to disable, 1 to enable, or 2 to ignore the flag. The default setting is 0. If you set this flag to 1, Site Recovery Manager resignatures all known VMFS snapshot volumes, including any volumes that Site Recovery Manager does not manage. If you leave the flag set to 0, Site Recovery Manager only resignatures the VMFS snapshot volumes that it manages.

    Force removal, upon successful completion of a recovery, of the snap-xx prefix applied to recovered datastore names

    Select the storageProvider.fixRecoveredDatastoreNames check box.

    Delay host scans during testing and recovery

    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, type 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

    Type 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

    Type a new value in the storageProvider.hostRescanTimeoutSec text box.

    Set the number of times that Site Recovery Manager attempts to resignature a VMFS volume

    Type a new value in the storageProvider.resignatureFailureRetryCount text box.

    Set a timeout for resignaturing a VMFS volume

    Type 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.

    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 option is selected by default. Deselect the storageProvider.storageVmotionVmxSearch check box to disable this option.

    Identify VMX file paths that Site Recovery Manager should not consider as potential VMX file candidates after Storage vMotion

    Some arrays create VMX file paths that the storageProvider.storageVmotionVmxSearch search algorithm should ignore. Type 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.

    Change the interval that Site Recovery Manager waits for recovered datastores to become accessible

    Type a new value in the storageProvider.waitForAccessibleDatastoreTimeoutSec text box. Change this value if you experience timeouts caused by Site Recovery Manager checking for datastores that are not available yet. This setting is available in Site Recovery Manager 5.5.1 and later.

    Change the interval that Site Recovery Manager waits for recovered datastores to be added to vCenter Server

    Type a new value in the storageProvider.waitForRecoveredDatastoreTimeoutSec text box. Change this value if you experience timeouts caused by Site Recovery Manager checking for datastores that have not been detected by vCenter Server yet. This setting is available in Site Recovery Manager 5.5.1 and later.

    Change the interval that Site Recovery Manager waits for VMFS volumes to be mounted

    Type a new value in the storageProvider.waitForVmfsVolumesMountedStateTimeoutSec text box. Change this value if you experience timeouts caused by Site Recovery Manager checking for VMFS volumes that take a long time to mount. This setting is available in Site Recovery Manager 5.5.1 and later.

  4. Click OK to save your changes.