Remote Copy relationships Remote Copy Remote Copy partnerships

A Remote Copy relationship defines the relationship between two virtual disks: a master VDisk and an auxiliary VDisk. In most cases, the master VDisk contains the production copy of the data and is the VDisk that the application normally accesses. The auxiliary VDisk typically contains a backup copy of the data and is used in disaster recovery scenarios.

The master and auxiliary VDisks are defined when the relationship is created, and these attributes never change. However, either VDisk may operate in the primary or secondary role according to the circumstances. The primary VDisk is the one currently receiving updates from the application, analogous to source VDisk . The secondary VDisk receives a copy of any updates to the primary VDisk, because these updates are all transmitted across the Remote Copy link. Therefore, the secondary VDisk is analogous to a continuously updated target VDisk.

Primary
Contains a valid copy of the application data, and it is accessible for application write operations.
Secondary
Might contain a valid copy of the application data, but it is not available for application write operations.

When a relationship is created, the master VDisk is assigned the role of primary VDisk and the auxiliary VDisk is assigned the role of secondary VDisk. Therefore, the initial copying direction is from master to auxiliary. When the relationship is in a consistent state, the copy direction can be reversed by issuing the svctask switchrcrelationship command, and specifying the auxiliary disk as the primary.

The two VDisks in a relationship must be the same size. When the two VDisks are in the same cluster, they must be in the same input/output (I/O) group.

A relationship can be added to a Remote Copy consistency group, for ease of application management (see consistency groups below).

Note:Note: Membership of a consistency group is an attribute of the relationship, not the consistency group. Therefore, the svctask chrcrelationship command is used to add or remove a relationship to or from a consistency group. See IBM TotalStorage SAN Volume Controller: Command-Line Interface User's Guide.

Remote Copy states

When a Remote Copy relationship is created with two virtual disks in different clusters, the distinction between the connected and disconnected states is important. These states apply to both the cluster, relationships, and consistency groups.

Inconsistent (Stopped)
The primary VDisk is accessible for read and write input/output (I/O) operations but the secondary VDisk is not accessible for either. A copy process needs to be started to make the Secondary VDisk consistent.
Inconsistent (Copying)
The primary VDisk is accessible for read and write I/O operations but the secondary VDisk is not accessible for either. This state is entered after a Start command is issued to an consistency group in the InconsistentStopped state. This state is also entered when a Start command is issued, with the force option, to a consistency group in the Idling or ConsistentStopped state.
Consistent (Stopped)
The secondary VDisk contains a consistent image, but it might be out-of-date with respect to the primary VDisk. This state can happen when a relationship was in the ConsistentSynchronized state and experiences an error which forces a freeze of the consistency group. This state can also happen when a relationship is created with the CreateConsistentFlag set to TRUE.
Consistent (Synchronized)
The primary VDisk is accessible for read and write I/O operations. The secondary VDisk is accessible for read-only I/O operations.
Idling
A master VDisk and a auxiliary VDisk operates in the primary role. Consequently the VDisk is accessible for write I/O operations.
Idling (Disconnected)
The VDisk is in this half of the consistency group are all operating in the primary role and can accept read or write I/O operations.
Inconsistent (Disconnected)
The VDisk is in this half of the consistency group are all operating in the secondary role and will not accept read or write I/O operations.
Consistent (Disconnected)
The VDisk is in this half of the consistency group are all operating in the secondary role and will accept read I/O operations but not write I/O operations
Related topics Remote Copy Remote Copy partnerships

(C) Copyright International Business Machines Corporation 2003, 2004