Home > Storage > PowerMax and VMAX > Storage Admin > Implementing Dell SRDF SRA with VMware SRM > Configuring SRDF SRA behavior
By default, the SRDF SRA is configured to act a certain way during discovery, recovery or test failover operations. The default options are configured in accordance with recommended best practices or to accommodate the most common environments and are typically sufficient for planned migration or failover activities. For test failover, the default parameters require intervention to successfully conduct a test. Changing these options can be accomplished by modifying an XML file called EmcSrdfSraGlobalOptions.xml as seen in Figure 36.
To edit the file, follow the section Configuring the SRDF SRA.
The file offers the following options shown in Table 11. In-depth discussions on each option will be reserved for the relevant sections in this book.
Option name | Default value | Description of SRA behavior when the option is enabled | Does the option setting need to be identically configured for both SRAs? |
SYMAPI Debug[17] | Disabled | The target Solutions Enabler server logs extremely detailed information about Solutions Enabler interactions from the SRA. Should only be enabled at the direction of EMC Support. | No |
Test failover force | Disabled | Allows test failover operations to continue regardless of the state of the RDF link. This setting permits testing when the protection site is unavailable. | No |
Terminate copy sessions | Disabled | The SRA will terminate replicas or snapshots after a test failover operation. The value of this option should be opposite of AutoTargetDeviceReuse - versions prior to 10.x will report an error. | No |
Test failover without local snapshots | Disabled | Allows test failover operations to be run off of the R2 devices instead of creating a TimeFinder replica. | No |
Failover if gold copy fails | Enabled | If local or remote gold copy creation fails during failover the Failover operation will continue regardless. | No |
Ignore activated snapshots | Disabled | Allows the user to activate TimeFinder/Clone or SnapVX devices at a scheduled time instead of having the SRA perform the activate during test failover. This option also allows the user to manually split the RDF link in case the option TestFailoverWithoutLocalSnapshots is enabled as well. | No |
Filter non-VMware devices[18] | Enabled | Filter out RDF devices that are not presented to the VMware environment during discovery. | Yes |
Check for virtual disks[19] | Disabled | Adds an additional filter to test failover and Gold Copy operations to ensure input replica devices are not in use in the recovery environment as an RDM or a VMFS volume. | No |
Failover to Async site | Disabled | Allows for the discovery and failover of Asynchronous target devices of 3-site SRDF configurations. | Yes |
Set Replica Target To Ready | Disabled | Enables the SRDF SRA to support replication targets that been made “not ready” by an admin | No |
Test Replica Masking Control | Disabled | During test recovery, the SRDF SRA will automatically mask the replica devices to the recovery site if not already presented and then remove them during cleanup. | No |
RDF Replica Masking Control | Disabled | During recovery, the SRDF SRA will automatically mask the R2 devices to the recovery site if not already presented. The R1 devices will be removed from the protected site as well. | Not required, but recommended |
Reverse Replication During Recovery | Disabled | When enabled, the SRDF SRA will swap RDF personalities of the failed over devices and establish the replication at the end of the SRM recovery operation instead of waiting for a SRM reprotect operation. This only affects Non-Star devices | No |
Ignore Disconnected Star | Disabled | When enabled, the SRDF SRA will no longer attempt to connect, protect, and enable the entire Star configuration when it finds at least one leg in a disconnected state. This includes Star configurations not in use by SRM. | Yes |
Auto Target Device | Disabled | When enabled, SRA dynamically creates target devices to link snapshots and in subsequent Cleanup operations deletes these devices. In addition, devices are added and removed from the R2 storage group, as long as AutoTargetDeviceReuse is disabled. Note only SnapVX copy type is supported. | No |
Auto Target Device Reuse | Enabled | When enabled along with AutoTargetDevice, SRA retains No dynamically created target devices and adds source to target mapping in the EmcSrdfSraTestFailoverConfig.xml file. The value of this option must be opposite of TerminateCopySessions - versions prior to 10.x will report an error. | No |
Auto Target Device Free Tracks | Disabled | When enabled along with AutoTargetDevice and AutoTargetDeviceReuse, the SRA will deallocate most tracks from the target devices, returning them to the SRP. | No |
ViClient Ignore Security Exception | Enabled | SRA uses ViClient to connect with vCenter Server. This flag is used to Ignore Security Exceptions while establishing a secure connection. Enable this flag to establish a secure connection by using existing user verified trust store certificates. | Yes |
Failover With Targetless Gold Copy | Disabled | When this option is enabled, SRA supports targetless gold copy for a failover or failback operation. This avoids having additional devices as TimeFinder targets when linking it to snapshots. | No |
The SRA implements the different levels of logging supported by SRM. SRM supports eight logging levels. The logging levels are: