Remote Copy consistency groups
Certain uses
of Remote Copy require the manipulation of more than one relationship. Remote
Copy provides the facility to group a number of relationships into a Remote
Copy consistency group so that they can be manipulated in unison. A command
issued to the consistency group will be applied to all of the relationships
in the group simultaneously.
For some uses it might be that the relationships share some loose association
and that the grouping simply provides a convenience for the administrator.
But a more significant use arises when the relationships contain VDisks that
have a tighter association. One example is when the data for an application
is spread across more than one VDisk. A more complex example is when multiple
applications run on different host systems. Each application has data on different
VDisks, and these applications exchange data with each other. Both these examples
are cases in which specific rules exist as to how the relationships must be
manipulated, in unison. This ensures that the set of secondary VDisks contains
usable data. The key property is that these relationships be consistent. Hence,
the groups are called consistency groups.
A relationship can be part of a single consistency group or not be part
of a consistency group at all. Relationships that are not part of a consistency
group are called stand-alone relationships. A consistency group can contain
zero or more relationships. All the relationships in a consistency group must
have matching master and auxiliary clusters. All relationships in a consistency
group must also have the same copy direction and state.
Remote Copy consistency
group states
- Inconsistent (Stopped)
- The primary VDisks are accessible for read and write input/output (I/O)
operations but the secondary VDisks are not accessible for either. A copy
process needs to be started to make the Secondary VDisks consistent.
- Inconsistent (Copying)
- The primary VDisks are accessible for read and write I/O operations
but the secondary VDisk are 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 VDisks contain a consistent image, but it might be out-of-date
with respect to the primary VDisks. 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 VDisks are accessible for read and write I/O operations.
The secondary VDisks are accessible for read-only I/O operations.
- Idling
- Master VDisks and Auxiliary VDisks are operating in the primary role.
Consequently the VDisks are accessible for write I/O operations.
- Idling (Disconnected)
- The VDisks 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 VDisks 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 VDisks 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
- Empty
- The consistency group contains no relationships.
Related topics