Preventive Service Planning
Abstract
This document describes software version compatibility for IBM Storage Virtualize systems using Metro Mirror or Global Mirror.
This document was formerly known as Spectrum Virtualize Family of Products Inter-System Metro Mirror and Global Mirror Compatibility Cross Reference.
Content
Note: Global Mirror is not supported by software versions 8.6.1, 8.6.2 or 8.6.3 on the following products:
- SAN Volume Controller
- FlashSystem 9x00
- FlashSystem 7x00
Note: Version 8.7.0 will be the final version that supports Remote Copy, which includes:
- Metro Mirror
- Global Mirror
- HyperSwap
- Volume mobility
Policy-based replication and policy-based high availability will supersede these features.
Refer to the IBM Storage Virtualize Policy-based Replication and High Availability Compatibility Cross Reference document for more details.
Considerations for Metro Mirror and Global Mirror replication
When using Metro Mirror for disaster recovery you need a low latency FC or FCoE network with enough bandwidth to keep up with peak production writes, and a disk system at the auxiliary site that can also keep up with peak writes.
When using Global Mirror for disaster recovery, you need enough bandwidth to keep up with the production writes and a well-performing disk system at the auxiliary site. You need an FC, FCoE, or FCIP network and a well-performing disk system at the auxiliary site.
For every application, you need to establish enough network and auxiliary disk performance to ensure the remote copy relationships can be sustained during peak times.
Refer to the IBM System Storage SAN Volume Controller and Storwize V7000 Replication Family Services Redbook for more details.
In a network of connected systems, the code level of each system must be supported for interoperability with the code level of every other system in the network. This applies even if there is no direct partnership in place between systems. For example, in the figure below, even though system A has no direct partnership with system C, the code levels of A and C must be compatible, as well as the partnerships between A-B and B-C.
When two systems are in a remote copy partnership, and one system has a lower limit on volumes per system, the lower limit applies to both systems. In the example above, the number of volumes on system B would be restricted to the lower of system A's limit and system C's limit. However, system A would not be affected by system C's limit.
When planning an upgrade, refer to the concurrent compatibility references and release notes for the new software level for any additional restrictions that might apply.
Was this topic helpful?
Document Information
Modified date:
27 May 2025
UID
ssg1S1003646