startrcrelationship

You can use the startrcrelationship command to start the Remote Copy relationship copy process, set the direction of copy if undefined, and optionally mark the secondary VDisk of the relationship as clean.

Syntax

Read syntax diagramSkip visual syntax diagram>>- svctask -- -- startrcrelationship -- ----------------------->

>--+--------------------------+-- --+----------+-- ------------->
   '- -primary --+- master -+-'     '- -force -'
                 '- aux ----'

>--+----------+-- --+- rc_rel_id ---+--------------------------><
   '- -clean -'     '- rc_rel_name -'

Parameters

-primary master | aux
It specifies the copy direction by defining whether the master or auxiliary will become the primary (source). This parameter is required when the primary is undefined, for example, if the relationship is in the idling state.
-force
Optionally specifies the force parameter. This argument permits the copy operation to resume even if it might lead to a loss of consistency.
-clean
Optionally specifies the clean parameter. The clean flag marks the secondary virtual disk as clean.
rc_rel_id | rc_rel_name
Specifies the ID or name of the relationship that you want to start in a stand-alone relationship only.

Description

This command is used to start a standalone relationship. The command will fail it if it is used to attempt to start a relationship that is part of a consistency group.

This command can only be issued to a relationship that is connected. For a relationship that is idling, this command assigns a copy direction (primary and secondary roles) and begins the copy process. Otherwise this command restarts a previous copy process that was stopped either by a stop command or by some I/O error.

If the resumption of the copy process will lead to a period when the relationship is not consistent, then you must specify the force flag when restarting the relationship. This situation could arise if, say, the relationship had been stopped, and then further writes had been performed on the original primary of the relationship. The use of the force flag here is a reminder that the data on the secondary will not be useful for Disaster Recovery purposes while it is in an inconsistent state.

In the idling state, you must provide the primary argument. In other connected states, you can provide the primary argument, but it must match the existing setting.

The -force flag is required if consistency would be lost by starting a copy operation. This would occur, if write operations on either primary or secondary vdisks have taken place since the ConsistentStopped or idling state was entered. If the command is issued without the -force flag in such circumstances, the command will fail. In general, the -force flag will be required if the relationship is in one of the following states:

The -force flag is not required if the relationship is in one of the following states:

However, the command will not fail if you do specify the -force flag.

The clean flag is used when a Remote Copy relationship is started and the secondary VDisk in this relationship is assumed to be clean. Clean in this sense means that any changes that have been made at the secondary are ignored and only changes made at the primary are considered when synchronising primary and secondary. This flag could be used in the following scenario:

  1. A relationship is created with the synchronized flag. (At this point it does not matter if the primary and secondary contain the same data, even though the use of the synchronized flag implies that this is true).
  2. A stoprcrelationship command is issued with the -allow access flag. This permits access to the secondary. Change recording begins at the primary.
  3. An image of the primary is captured and loaded on to the secondary. It is permissible to allow updates to the primary during the image copy as this image need only be a 'fuzzy' image of the primary.
  4. A startrcrelationship command with primary = master, the force flag and the clean flag is issued. This causes the auxiliary to be marked clean, and changes on the master that have occurred since the relationship was stopped are copied to the auxiliary.
  5. Once the background copy has completed, the relationship will be consistent and synchronized.

Possible failures

Examples

An invocation example

svctask startrcrelationship rccopy1