- Notes, cautions, and warnings
- PREFACE
- Revision history
- SRDF CLI overview
- Introduction to SRDF
- SYMCLI for SRDF
- SRDF pair states and links
- Before you begin
- Array access rights
- Device external locks
- SRDF operations and copy sessions
- Mirror R1 to a larger R2 device
- Restrict synchronization
- SRDF software and hardware compression
- Set compression for SRDF
- SRDF/A and the consistency exempt option
- Mixed-mode workloads on an SRDF director
- Set mixed-mode workloads
- FAST VP SRDF coordination
- Basic SRDF Control Operations
- Summary
- SRDF basic control operations
- SRDF modes of operation
- Establish an SRDF pair (full)
- Establish an SRDF pair (incremental)
- Failback to source
- Failover to target
- Invalidate R1 tracks
- Invalidate R2 tracks
- Make R1 ready
- Make R1 not ready
- Make R2 ready
- Make R2 not ready
- Merge track tables
- Move one-half of an SRDF pair
- Move both sides of SRDF device pairs
- Read/write disable target device
- Refresh R1
- Refresh R2
- Restore SRDF pairs (full)
- Restore SRDF pairs (incremental)
- Resume I/O on links
- Split
- Suspend I/O on links
- Swap one-half of an SRDF pair
- Swap SRDF pairs
- Update R1 mirror
- Write disable R1
- Write disable R2
- Write enable R1
- Write enable R2
- Dynamic Operations
- Dynamic operations overview
- Manage SRDF groups
- Device pairing operations
- Create a device file
- Valid device types for SRDF pairs
- Block createpair when R2 is larger than R1
- Creating SRDF device pairs
- symrdf createpair (-file option) syntax
- Create dynamic pairs with -file option
- Create dynamic pairs with the -sg option
- Create pairs with the -establish option
- Create pairs with the -format option
- Create pairs with the -invalidate option
- Create pairs with the -restore option
- Verify host cannot write to target devices with -nowd option
- Create dynamic concurrent pairs
- Deleting dynamic SRDF device pairs
- Group, move and swap dynamic devices
- SRDF/Asynchronous Operations
- SRDF/Asynchronous operations overview
- SRDF/Asynchronous operations
- Transition replication modes
- Set SRDF/A group cycle time, priority, and transmit idle
- Check for R1 invalid tracks
- Consistency for SRDF/A devices
- Add/remove devices with the consistency exempt option
- Adding device pairs to an active SRDF/A session
- Removing device pairs from an active SRDF/A session
- Display checkpoint complete status
- Delta Set Extension management
- DSE SRP capacity management (HYPERMAX OS)
- DSE pool management - Enginuity 5876
- Manage transmit idle
- Manage SRDF/A write pacing
- Devices that cannot be paced in a cascaded SRDF configuration
- Set SRDF/A group-level write pacing attributes
- Activate write pacing
- Simultaneous group-level and device-level write pacing
- Display SRDF/A
- SRDF/Metro Operations
- SRDF/Metro Overview
- SRDF/Metro changes to SYMCLI operations and commands
- Display SRDF/Metro
- Device pairs in SRDF/Metro configurations
- Manage resiliency
- Suspend an SRDF/Metro group
- Deactivate SRDF/Metro (deletepair)
- Example: Setting up SRDF/Metro (Array Witness method)
- SRDF/Metro Smart DR Operations
- SRDF/Metro Smart DR Overview
- SRDF/Metro Smart DR restrictions and dependencies
- SRDF/Metro Smart DR basic control operations
- SRDF/Metro Smart DR changes to SYMCLI operations and commands
- Set up an SRDF/Metro Smart DR environment
- Remove an SRDF/Metro Smart DR environment
- Monitor SRDF/Metro Smart DR
- Control an SRDF/Metro Smart DR environment
- Recover an SRDF/Metro Smart DR environment
- Consistency Group Operations
- Consistency group operations overview
- SRDF consistency group operations
- Enable and disable SRDF consistency protection
- Enable consistency: composite group vs. SRDF group name
- Enabling SRDF consistency protection for concurrent SRDF devices
- Check if device pairs are enabled for consistency protection
- Block symcg enable on R2 side
- Delete an SRDF consistency group
- Suspend SRDF consistency protection
- Composite group cleanup (msc_cleanup)
- Modify consistency groups
- Before you begin consistency group modification
- Consistency group modification restrictions
- Prepare staging area for consistency group modification
- Restrictions: Add devices to SRDF consistency group
- Restrictions: Remove devices from SRDF consistency group
- Restrictions: Device types allowed for add operations to an RDF1 consistency group
- Restrictions: Device types and consistency modes allowed for add operations to a concurrent RDF1 consistency group
- Restrictions: Devices types allowed to add to a cascaded RDF1 consistency group
- Restrictions: Device types allowed for remove operations from an RDF1 consistency group
- Restrictions: Device types allowed for remove operations from a concurrent RDF1 consistency group
- Restrictions: Device types allowed for remove operations from a cascaded RDF1 consistency group
- Recovering from a failed dynamic modify operation
- Consistency groups with a parallel database
- Consistency groups with BCV access at the target site
- Concurrent Operations
- Cascaded Operations
- Cascaded operations overview
- Setting up cascaded SRDF
- R21 device management
- Cascaded SRDF with EDP
- Sample session: planned failover
- Display cascaded SRDF
- SRDF/Star Operations
- SRDF/Star operations overview
- SRDF/Star states and operations
- SRDF/Star operations summary
- Configure and bring up SRDF/Star
- Step 1: Verify SRDF/Star control host connectivity
- Step 2: Verify array settings
- Step 3: Create an SRDF/Star composite group
- Step 4: Create the SRDF/Star options file
- Step 5: Perform the symstar setup operation
- Step 6: Create composite groups on target sites
- Step 7: (Optional) Add BCV devices to the SRDF/Star configuration
- Step 8: Bring up the SRDF/Star configuration
- Displaying the symstar configuration
- Removal of a CG from SRDF/STAR control
- Basic SRDF/Star operations
- SRDF/Star consistency group operations
- Before you begin: SRDF daemon interaction
- SRDF/Star consistency group restrictions
- Prepare staging for SRDF/Star consistency group modification
- Add devices to a concurrent SRDF/Star consistency group
- Add devices to a cascaded SRDF/Star consistency group
- Remove devices from consistency groups
- Recovering from a failed consistency group modification
- Recovery operations: Concurrent SRDF/Star
- Workload switching: Concurrent SRDF/Star
- Planned workload switching: Concurrent SRDF/Star
- Unplanned workload switching: concurrent SRDF/Star
- Unplanned workload switch to synchronous target site: concurrent SRDF/Star
- Unplanned workload switch to asynchronous target site: concurrent SRDF/Star
- Switch back to the original workload site: concurrent SRDF/Star
- Recovery operations: Cascaded SRDF/Star
- Workload switching: Cascaded SRDF/Star
- Reconfiguration operations
- SRDF/Star configuration with R22 devices
- Device Migration Operations
- SRDF/Automated Replication
- SRDF/Automated Replication overview
- SRDF/Automated Replication operations
- Clustered SRDF/AR
- Set symreplicate parameters in the options file
- Manage locked devices
- TimeFinder and SRDF operations
- SRDF Automated Recovery Operations
Dell EMC Solutions Enabler 9.2 SRDF Family CLI User Guide
SRDF/A restrictions
- All SRDF/A-capable devices running in asynchronous mode must be managed together in an SRDF/A session.
- For SRDF/A-capable devices enabled for consistency group protection, consistency must be disabled before attempting to change the mode from asynchronous.
- SRDF Automated Replication (SRDF/AR) control operations are currently not supported for SRDF/A-capable devices running in asynchronous mode.
- All SRDF/A sessions enabled within a consistency group operate in the same mode, multi-cycle or legacy (See
SRDF/A cycle modes for information on cycle modes.). For example, if:
- SRDF group 1 connects Site A and Site B, both running HYPERMAX OS, and
- SRDF group 2 Site A running HYMPERMAX OS and Site C running Enginuity 5876.
- Group 1 can run in multi-cycle mode.
- Group 2 must run in legacy mode.
If both groups are in the same consistency group and are enabled together, then group 1 will transition from multi-cycle to legacy mode as a part of the enable.
- If there are tracks owed from the R2 to the R1, do not set mode to asynchronous.
NOTE:
If tracks are owed to the R1 device, the -force option is required to make SRDF/A-capable devices in asynchronous mode Ready on the link.
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: <>()\