startrcrelationship
Use the startrcrelationship command to start the Metro Mirror, Global Mirror or migration relationship copy process, set the direction of copy if undefined, and (optionally) mark the secondary volume of the relationship as clean. The relationship must be a stand-alone relationship.
Syntax
Parameters
- -primary master | aux
- (Optional) Specifies the copy direction by defining whether the master or auxiliary disk becomes the primary (source). This parameter is required when the primary is undefined if, for example, the relationship is in the idling state.
- -force
- (Optional) Specifies that you want the system to process the copy operation even if it
might lead to a temporary loss of consistency while synchronization occurs. This parameter is
required if the relationship is in the ConsistentStopped state,
but is not synchronized or in
idling
state - except if consistency protection is configured.Important: Using the force parameter might result in a loss of access. Use it only under the direction of IBM® support personnel. - -clean
- (Optional) Specifies that the volume that is to become a secondary is clean. Any changes
that are made on the secondary volume are ignored, but changes made on the clean primary volume are
considered when synchronizing the primary and secondary disks. The relationship must be in an Idling
(connected) state for this parameter to
work.Attention:
This flag must be used only if all data changed on the secondary volume while the relationship was in the
idling
state matches the state of the primary volume when the relationship was stopped. Otherwise, a relationship that is not consistent is reported as consistent. When this completes, there is no method to determine whether the volume ever reaches a true consistent state until a full background copy can be carried out again. - rc_rel_id | rc_rel_name
- (Required) Specifies the ID or name of the relationship that you want to start in a stand-alone relationship.
Description
The startrcrelationship command starts a stand-alone relationship. The command fails if it is used to start a relationship that is part of a consistency group.
If the FlashCopy mapping is active, the remote copy cannot be started.
stoprcrelationship
-access
but is restarted and the resultant secondary volume (depending on the choice of
primary) is mapped to a host of type hide_secondary
, that volume is not presented
to the host. This is true even though it is mapped for configuration purposes. The mapped volumes
are presented to the host if the: - Host type is changed to a type other than
hide_secondary
- Remote copy relationship is stopped by specifying
stoprcrelationship -access
- Volume ceases to be a secondary volume because the remote copy relationship is being deleted or switched
In the idling state, you must provide the -primary parameter. In other connected states, you can provide the -primary parameter, but it must match the existing setting.
- ConsistentStopped but not synchronized
- Idling but not synchronized
After restarting a relationship in either of these states, the data on the secondary volume is not usable for disaster recovery until the relationship becomes consistent.
A Global Mirror relationship with a cycling_mode
of multi
in
either of these states does not require the -force parameter because a
consistent secondary image is retained. However, if such a relationship is in idling state and
written data is received at the secondary volume, the -force flag is required
because the secondary volume has a divergent image that cannot represent a consistent earlier state.
- InconsistentStopped
- InconsistentCopying
- ConsistentSynchronized
You do not have to specify the -force parameter for relationships with
configured secondary change volumes. If you specify startrcrelationship for an
idling
relationship, consistency protection is disabled if the secondary volume is
written to. This means that you must specify the -force parameter.
- none uses the non-cycling Global Mirror algorithm
- multi must:
- Use a change volume that is configured at the primary volume (or the command fails)
- Use a change volume that is configured at the secondary volume (or the command fails)
- Perform multiple cycles of cycling
After you create a background copy the relationship remains in copying state, wait for the remainder of the period time to expire before you perform a new cycle. If the secondary change volume is unconfigured when the background copy completes, the relationship stops as if there is no cycle period.
An invocation example
startrcrelationship rccopy1
The resulting output:
No feedback