>>- svctask -- -- startrcrelationship -- -----------------------> >--+--------------------------+-- --+----------+-- -------------> '- -primary --+- master -+-' '- -force -' '- aux ----' >--+----------+-- --+- rc_rel_id ---+-------------------------->< '- -clean -' '- rc_rel_name -'
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:
An invocation example
svctask startrcrelationship rccopy1
The resulting output
No feedback