The following restrictions and dependencies apply to SRDF/Metro configurations. For information regarding additional code-specific restrictions, see the SRDF/Metro support matrix located at: E-Lab Navigator.
- Both the R1 and R2 side must be running HYPERMAX OS 5977.691.684 or greater
- SRDF/Metro license must be installed on both arrays to be managed
- Only non-SRDF devices can become part of an SRDF/Metro configuration with HYPERMAX OS 5977.811.784 and earlier
- Concurrent and cascaded SRDF/A configurations are only supported with the HYPERMAX OS Q3 2016 SR and later
- Concurrent and cascaded SRDF/A configurations support Single Session Consistency only (no MSC)
- Concurrent (R11) SRDF/A target must be a VMAX running HYPERMAX OS 5977 Q3 2016 SR or later
- The R1 and R2 must be identical in size
- Devices cannot have Geometry Compatibility Mode (GCM) set on code prior to PowerMaxOS Q2 2018 SR
- Devices cannot have User Geometry set
- Online device expansion is not supported
- createpair -establish, establish, restore, and suspend operations must apply to all devices in the SRDF group
- Control of devices in an SRDF group which contains a mixture of R1s and R2s is not supported
- vWitness configurations require Embedded Element Management (EEM or eMgmt) on each SRDF/Metro paired array
- vWitness vApp requires VMware ESXi 4.0 or higher, and Solutions Enabler or Unisphere 8.3 or greater
- Consistency Exempt Status Restrictions:
- Restore operations will be blocked while one or more devices in an SRDF/Metro group are in an ‘exempt’ status
- At least one device within the SRDF/Metro session must be non-exempt
- Management software will not allow all devices in the SRDF/Metro session to be removed with exempt deletepair or movepair
- If the devices added to the SRDF/Metro configuration are, or will be, concurrent SRDF devices, they must meet the criteria required of concurrent devices in an SRDF/Metro configuration:
The non-Metro RDF mirror cannot be in Synchronous mode
A device cannot have 2 Metro RDF mirrors
The non-Metro RDF mirror of the SRDF/Metro devices must be an R1.
The R1 device in an SRDF/Metro configuration can be an R11 device, but it cannot be an R21 device, and
The R2 device in an SRDF/Metro configuration can be an R21 device, but it cannot be an R22 device
A device cannot simultaneously be both RW on the RDF link on the Metro RDF mirror and the target of data copy from the non-Metro RDF mirror
A device cannot be WD to the host if the device’s Metro SRDF mirror is RW on the RDF link
- Other Movepair Exempt support restrictions:
- The SRDF R1/R2 ‘polarity’ of the source SRDF device pairs must match that of the target SRDF group.
- For example, R2 devices on one side of the link may not be moved into a group where the devices have R1 personalities
- As with ‘createpair –exempt’, movepair can only be used if the active SRDF/Metro group does not contain exempt devices
- If any of the SRDF device pairs being added have the SyncInProg SRDF pair state, then the ‑symforce option is required
- Device pairs being added will be suspended during the movepair operation
- Source device pairs which have Suspended or SyncInProg SRDF pair states cannot have invalids owed from R2 to R1
- Online Device Expansion (ODE) Restrictions:
- Requires PowerMaxOS 5978 Q2 2019 SR and Solutions Enabler/Unisphere for PowerMax 9.1 or greater
- SRDF N-X environments will not be supported (PowerMaxOS 5978 Q2 2019 SR or later only)
- No device expansion will be allowed when SRDF/Metro pair is Partitioned
- Expansion of a larger R2 is not supported, R1/R2 same initial sizes only
- No support for NDM migrations or devices actively being migrated
- For SRDF/Metro DR (w/Async leg) support:
Configuration with a third site will require multiple steps rather than a single operation/command
Will need to expand DR site first and then expand SRDF/Metro pair
It will be necessary to suspend DR during the expansion operation
- Metro RDF, MetroR1 to DR RDF and MetroR2 to DR SRDF groups are online
- All 3 Arrays must be PowerMaxOS 5978 Q3 2020 SR (Hickory) or greater
- All 3 Arrays must be discoverable through SE and must be in the symapi_db.bin
- All of the MetroR1 devices must be in the same SRDF/A session
- All of the SRDF/A R1 devices on the MetroR1 array must be in the same Metro session
- All of the MetroR2 devices must be in the same SRDF/A session
- All of the SRDF/A R1 devices on the MetroR2 array must be in the same Metro session
- The MetroR1, Metro R2, DR devices must be the same size
- Online Device Expansion (ODE) is not supported. Remove/ODE/Setup is required
- Devices cannot be: BCV, Encapsulated, RP, Data Domain, PPRC, CKD, Part of a STAR configuration, Part of a SQAR configuration, Enabled for MSC, Part of a Data Migration session