Smart DR control operations may be performed using Solutions Enabler SYMCLI 9.2 or Unisphere 9.2 and later. For SYMCLI. In addition to Unisphere, the symmdr command previously described will be used to perform a Smart DR setup, removal, recovery, and specific operations directed to the various Metro and DR components. The Unisphere protection wizard allows the complete creation of a Smart DR environment based on the R1 Storage Group being protected. This will include the setup of Metro and DR array storage groups as well as the creation of devices on these arrays which match the number and size of the initial R1 Storage Group. For Unisphere, see the examples of the Unisphere 9.2 protection wizard and control interface in Appendix E: Unisphere Smart DR walkthrough.
Note: Using the symrdf command to control the Smart DR environment is not allowed. The new symmdr command must be used for all SYMCLI oriented Smart DR control operations.
All control operations may be directed at:
- The Smart DR environment as a whole
- The Metro localized session
- The DR localized session
Note: Control operations which are targeted at the Smart DR environment, require all 3 arrays to be previously discovered and that the Metro, MetroR1 to DR, and MetroR2 to DR SRDF groups to be online.
Operations which are allowed on the Smart DR environment are categorized as follows:
- Setting up and Removing the Smart DR environment
- Monitoring the Smart DR environment
- Recovering the Smart DR environment
Control operations summary
- Environment Setup: An environment setup is required to put a Metro session and a DR session into a MetroDR environment which enables the ability to closely couple the SRDF/A sessions from each side of the Metro session when the DR is in Async mode. See detailed description above for additional information.
- Environment Recover: The recover command will transition the Metro Smart DR environment back to a known state.
- Environment Remove: The result will be a Concurrent RDF setup which has one session that is a Metro session and one session that is either a SRDF/A session or in adaptive copy disk mode.
- Metro Establish: An establish makes the devices in the Metro session RW on the SRDF link and initiates an incremental re-synchronization of data from the Metro R1 to the Metro R2. An establish makes the devices in the DR session RW on the SRDF link and initiates an incremental re-synchronization of data from the Metro to the DR. In the event the user chooses both sessions, the Metro session will be run first, followed by the DR session, two separate API calls will be made, one for each session.
- Metro Suspend: A suspend makes the devices in the Metro session NR on the SRDF link. By default, the Metro R1 will remain accessible to the host, while the Metro R2 will become inaccessible to the host. A suspend makes the devices in the DR session NR on the SRDF link, stopping data synchronization between Metro session and DR.
- Metro Restore: A restore makes the devices in the Metro session RW on the SRDF link and initiates an incremental re-synchronization of data from the Metro R2 to the Metro R1.
- DR Split: A split makes the devices in the DR session NR on the SRDF link, stopping data synchronization between Metro session and DR.
- DR Restore: A restore makes the devices in the DR session RW on the SRDF link and initiates an incremental re-synchronization of data from the DR to the Metro R1.
- DR Failover: A failover makes the devices in the DR session NR on the SRDF link, stopping data synchronization between Metro session and DR and adjusts the DR to allow the application to be started on the DR side. Once the failover command completes successfully: The DR is Ready (RW).
- If the failover command was issued when the DR state was not Partitioned or TransIdle:
- When the MetroR1 is mapped to the host, the MetroR1 will be write disabled (WD)
- The MetroR2 will be inaccessible to the host
- The Metro state will be Suspended
- If the failover command was issued when the DR state was Partitioned or TransIdle:
- MetroR1, MetroR2, and the Metro states will not change
- DR Failback: A failback makes the devices in the DR session RW on the SRDF link and initiates an incremental re-synchronization of data from the DR to the Metro R1. It will also make the devices in the Metro session RW on the SRDF link, initiating an incremental re-synchronization of data from the Metro R1 to Metro R2.
- DR Update R1: An Update R1 makes the Metro R1 to DR devices RW on the SRDF link and initiates an update of the R1 with the new data that is on DR.
- DR Set Mode: A set mode acp_disk sets the DR mode to Adaptive copy disk mode. A set mode async sets the DR mode to Asynchronous mode.
Solutions Enabler SYMCLI control operation syntax
The syntax of the SYMCLI symmdr command for operations targeted against the Smart DR environment as a whole:
symmdr -sid <SID> -name <Env> -metro_rdfg <RDFGroup> -dr_rdfg <RDFGroup>
[-noecho] [-noprompt] [-i <Interval>] [-c <Count>]
environment –setup
symmdr -sid <SID> -name <Env> -dr_rdfg <RDFGroup>
[-noecho] [-noprompt] [-i <Interval>] [-c <Count>] [-force]
environment –remove
symmdr -sid <ArrayID> -name <EnvironmentName> [-noecho] [-noprompt]
[-i <Interval>] [-c <Count>]
Recover
The syntax of the SYMCLI symmdr command for operations targeted against the SRDF/Metro session, specifically:
symmdr -sid <SID> -name <Env> [-noecho] [-noprompt]
[-i <Interval>] [-c <Count>] [-force] [-symforce] -metro
establish
restore
suspend [-keep <R1 | R2>]
The syntax of the SYMCLI symmdr command for operations targeted against the DR session, specifically:
symmdr -sid <SID> -name <Env> [-noecho] [-noprompt]
[-i <Interval>] [-c <Count>] [-force] [-symforce] -dr
establish
failback
failover
restore
split
suspend
update
set mode <acp_disk | async>