Table 44 Limitations of the migration-only mode (continued)
SRDF operations or features Whether supported during
migration
Failover, failback, domino Not supported
SRDF/Star Not supported
SRDF/A features: (DSE, Consistency Group, ECA,
MSC)
Not supported
Dynamic SRDF operations: (Create/delete/move
SRDF pairs, R1/R2 personality swap)
Not supported
TimeFinder operations Only on R1
Online configuration change or upgrade
l
If online upgrade or configuration
changes affect the group or devices
being migrated, migration must be
suspended prior to the upgrade or
configuration changes.
l
If the changes do not affect the
migration group, they are allowed
without suspending migration.
Out-of-family Non-Disruptive Upgrade (NDU) Not supported
SRDF/Metro
HYPERMAX OS 5977.691.684 introduced SRDF/Metro.
In traditional SRDF, R1 devices are Read/Write accessible. R2 devices are Read Only/
Write Disabled.
In SRDF/Metro configurations:
l
R2 devices are Read/Write accessible to hosts.
l
Hosts can write to both the R1 and R2 side of the device pair.
l
R2 devices assume the same external device identity (geometry, device WWN) as
their R1.
This shared identity causes the R1 and R2 devices to appear to hosts(s) as a single
virtual device across the two arrays.
SRDF/Metro can be deployed with either a single multi-pathed host or with a
clustered host environment.
Remote replication solutions
SRDF/Metro 145
To Next Page
Loading...
