Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell EMC Solutions Enabler 9.2 SRDF Family CLI User Guide

SRDF/Metro Smart DR basic control operations

Table 1. Basic symmdr control operations summary
Control operation symmdr argument Description
Operations specific to the SRDF/Metro Smart DR environment
Set up an SRDF/Metro Smart DR environment environment -setup

Creates a SRDF/Metro Smart DR environment.

When the environment setup successfully completes, it includes a second DR leg that allows Smart DR to couple SRDF/A sessions running in the two DR legs so that it can maintain a write-consistent copy of the data at the DR site no matter which side of the SRDF/Metro session might experience a failure.

Remove an SRDF/Metro Smart DR environment environment -remove
The successful removal of a SRDF/Metro Smart DR environment results in the following:
  • the state of the SRDF/Metro session does not change
  • the state of the SRDF/Metro Smart DR session does not change (unless a -force option is required)
  • if the DR mode is Asynchronous at the time of issuing the symmdr env -remove command, the devices remain enabled.

Using the -force option results in the state of the DR changing. This is required for removing a SRDF/Metro Smart DR environment when:

  • the SRDF/Metro state is SyncInProg or ActiveActive, and
  • the DR state is Synchronized, SyncInProg, or Consistent, and
  • MetroR2_DR is Suspended and the MetroR1_DR is being removed.

Example for the -force option:
  • DR mode is adaptive copy disk
  • DR from the MetroR2 will be kept
  • the Metro session state is ActiveActive
  • the SRDF/Metro Smart DR session state is Synchronized

The resulting Smart DR SRDF pair state is Suspended after the symmdr environment -remove command completes successfully.

Recover an SRDF/Metro Smart DR environment recover

Using the recover command, users can attempt to recover an SRDF/Metro Smart DR environment from an Invalid or Unknown state, and transition the environment back to a known state.

Operations specific to the SRDF/Metro session
Establish for the SRDF/Metro session establish

Resumes I/O traffic on the SRDF links and initiates an incremental re-synchronization of data from the MetroR1 to the MetroR2.

Restore for the SRDF/Metro session restore

Resumes I/O traffic on the SRDF links and initiates an incremental re-synchronization of data from the MetroR2 to the MetroR1.

Suspend for the SRDF/Metro session suspend [-keep <R1 | R2>]

Suspends I/O traffic on the SRDF links. By default the MetroR1 remains accessible to the host, while the MetroR2 becomes inaccessible.

Operations specific to the DR session
Establish for the DR session establish Resumes I/O traffic on the SRDF links and initiates an incremental re-synchronization of data from SRDF/Metro to DR.
Restore for the DR session restore Resumes I/O traffic on the SRDF links and initiates an incremental re-synchronization of data from DR to SRDF/Metro.
Suspend for the DR session suspend

Suspends I/O traffic on the SRDF links. By default the MetroR1 remains accessible to the host, while the MetroR2 becomes inaccessible.

Split for the DR session split

Use the split operation when both the SRDF/Metro and the DR side require independent access, such as for testing purposes.

Split stops data synchronization between the SRDF/ Metro and DR sessions and devices are made available for local host operations.

Failover for the DR session failover

Use this when a failure occurs on the SRDF/Metro side.

A failover stops data synchronization between the SRDF/Metro and DR sessions, switching data processing from the SRDF/Metro side to the DR side.

Failback for the DR session failback

After a failover (planned or unplanned), use failback to resume normal operations after resolving the cause of a failure.

Failback switches data processing from the DR side to the SRDF/Metro side.

Update R1 for the DR session update

An update operation initiates an update of the R1 with the new data that is on DR, while the DR remains accessible to the host.

NOTE:Update R1 is not allowed if SRDF/Metro is ActiveActive, ActiveBias, or SyncInProg.
Set mode acp_disk for the DR session

Set mode async for the DR session

set mode <acp_disk | async> Use the set mode operation to set the DR mode to Adaptive copy or Asynchronous disk mode.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\