IBM Support

Spectrum Virtualize Family of Products Inter-System Metro Mirror and Global Mirror Compatibility Cross Reference

Preventive Service Planning


Abstract

This document provides a compatibility table for Metro Mirror and Global Mirror relationships between the Spectrum Virtualize Family of Products system software versions.

Content

Key:

Supported
* Supported for:
- partnerships between SAN Volume Controller systems
- partnerships between Storwize systems

Partnerships between a SAN Volume Controller and a Storwize family system require both systems to be running software version 6.3.0 or later.
Not supported

 

 

Inter-system Metro Mirror and Global Mirror support:

System code level
5.1.0
6.1.0
6.2.0
6.3.0
6.4.0
6.4.1
7.1.0
7.2.0
7.3.0
7.4.0
7.5.0
7.6.0
7.6.1
7.7.0
7.7.1
7.8.0
7.8.1
8.1.0
8.1.1
8.1.2
8.1.3
8.2.0
8.2.1
5.1.0
*
*
*
*
*
*
6.1.0
*
*
*
*
*
*
*
*
*
6.2.0
*
*
*
*
*
*
*
*
*
6.3.0
*
*
*

Note 1
6.4.0
*
*
*

Note 1
6.4.1
*
*
*

Note 1
7.1.0
*
*
*

Note 1

Note 1

Note 1

Note 1

Note 1

Note 1

Note 1

Note 1

Note 1

Note 1

Note 1

Note 1

Note 1
7.2.0
*
*
7.3.0
*
*
7.4.0
7.5.0

Note 1

Note 1

Note 1

Note 1
7.6.0

Note 1
7.6.1

Note 1
7.7.0

Note 1
7.7.1

Note 1
7.8.0

Note 1
7.8.1

Note 1
8.1.0

Note 1
8.1.1

Note 1
8.1.2

Note 1
8.1.3

Note 1
8.2.0

Note 1
8.2.1

Note 1

 

Note 1: Global Mirror with Change Volume (GMCV) relationships are not supported between 7.1.0 or earlier levels and 7.5.0 or later levels. This restriction does not affect Metro Mirror or Global Mirror (cycling mode set to 'none') relationships. A concurrent upgrade path is available by upgrading the downlevel system to 7.2.0 or later first.

 

When using Metro Mirror for disaster recovery you will 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 will need enough bandwidth to keep up with the production writes and a well-performing disk system at the auxiliary site. You will need an FC, FCoE, or FCIP network and a well-performing disk system at the auxiliary site.

For every application you will need to establish enough network and auxiliary disk performance to ensure the remote copy relationships can be sustained during peak times.

Please 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 planning an upgrade, refer to the concurrent compatibility references and release notes for the new software level for any additional restrictions that may apply.

 

 

 


Cross reference information
Product Component Platform Version Edition
IBM Storwize V3700 (2072) Not Applicable
IBM Storwize V5000 Not Applicable
IBM Storwize V7000 (2076) Not Applicable
Flex System V7000 Not Applicable Platform Independent All Versions
IBM FlashSystem 9100 family Not Applicable Platform Independent All Versions

Document information

More support for: SAN Volume Controller

Component: Not Applicable

Version: Version Independent

Operating system(s): Platform Independent

Reference #: S1003646

Modified date: 03 January 2019