HP XP P9000 Replication Manager Software 7.6.1-00 User Guide

Defining copy groups
This module discusses information about copy groups and tasks for defining copy groups:
• About copy groups, page 162
• About assigning CTGID/JNLGID for copy pairs, page 162
• Configuring open and mainframe consistency groups, page 163
• About HORCM instances, page 164
• Creating copy groups, page 164
• Changing copy group names, page 166
• Associating pair groups with copy groups, page 166
About copy groups
A copy group consists of a number of copy pairs that have been grouped for management purposes.
By grouping the copy pairs of volumes that are used for the same operations and purposes, you can
perform batch operations on all the copy pairs in that copy group. For example, by performing an
operation such as changing the copy pair status on a copy group, you can change the copy pair
status of all copy pairs in the copy group in a single operation.
Mainframe copy pairs can be grouped into two types of copy groups for maintaining data consistency
during replication. Copy groups can be defined without a container, in which case data consistency
is maintained per copy group. Copy groups can also be defined with a container, where each
container consists of multiple copy groups. In the latter case, data consistency is maintained per
container. There are limitations on the permitted combinations of copy group and container. For
details on these limitations, see “Supported copy group and container combinations” on page 168.
Related topics
• Creating copy groups, page 164
• Supported copy group and container combinations, page 168
Copy group requirements for pair configuration (mainframe systems)
The following copy group requirements must be satisfied when creating or editing mainframe pair
configurations:
• The copy group must contain the DADIDs of both the primary and secondary volumes for the created
pair group.
• The primary and secondary volumes of all pairs in the pair group to be added must belong to the
same storage system as the primary and secondary volumes of the existing copy group. If the
storage systems are different, the CTG of an existing group should be set.
• The instance of BCM that owns the copy group must have access permissions.
• The copy group must be a primary host copy group.
• The copy group must be one for which the pair association has not been executed yet.
About assigning CTGID/JNLGID for copy pairs
Consistency groups and Journal groups can be configured for any asynchronous copy pair. Replication
Manager allows you to assign CTGID/JNLGID for copy pairs during pair creation (when associating
a pair group to a copy group). In order to change a CTGID/JNLGID, it is necessary to delete and
recreate the copy pair.
Managing pair life cycle162