Dell EMC Solutions Enabler 9.2 SRDF Family CLI User Guide

• The symrecover session must be started either at the primary R1 site or the remote R2 site.
• If the group is concurrent, then symrecover must be run from the R1 workload site.
• SRDF/Metro configurations cannot be monitored by SRDF Automated Recovery.
• Solutions Enabler binaries must either be in the PATH or specified as a parameter.
• The symrecover command can only be run with the Perl script shipped with Solutions Enabler.
• The initial group state must be CONSISTENT or SYNCHRONIZED, depending on the target SRDF state, unless the restart_group_on_startup option is specified (not the default).

Consistency protection restrictions

• If consistency protection is desired, it must be enabled prior to starting symrecover.
• A symrecover session must be started on the same site where consistency was enabled via a consistency group.

Gold copy restrictions

• R2 gold copying can be performed with either native clones or Business Continuance Volumes (BCVs).
• BCV-to-STD association for the R2 gold copy is dynamic using the symmir defaults.

Restart restrictions

• A recovery fails if monitoring a leg that has an R22 device when the other SRDF mirror of the R22 is read/write (RW) on the link (such states as synchronized, syncinprog, or consistent).
• The recovery does not start when the -restart_group_on_startup parameters are specified, and an R22 device has another SRDF mirror that is already RW on the link.