>>- svctask -- -- mkrcrelationship -- --------------------------> >-- -master --+- master_vdisk_id ---+-- ------------------------> '- master_vdisk_name -' >-- -aux --+- aux_vdisk_id ---+-- ------------------------------> '- aux_vdisk_name -' >-- -cluster --+- cluster_id ---+-- ----------------------------> '- cluster_name -' >--+------------------------+-- --------------------------------> '- -name -- new_name_id -' >--+-----------------------------------------+-- ---------------> '- -consistgrp --+- consist_group_id ---+-' '- consist_group_name -' >--+---------+------------------------------------------------->< '- -sync -'
This command creates a new Remote Copy relationship. This relationship persists until it is deleted. The auxiliary virtual disk must be identical in size to the master virtual disk or the command will fail, and if both VDisks are in the same cluster they must both be in the same I/O group. The master and auxiliary cannot be in an existing relationship. Neither disk can be the target of a FlashCopy mapping. This command returns the new relationship (relationship_id) when successful.
You can optionally give the relationship a name. The name must be a unique relationship name across both clusters.
The relationship may optionally be assigned to a Remote Copy consistency group. A consistency group is used to ensure that a number of relationships are managed so that, in the event of a disconnnection of the relationships, the data in all relationships within the group is in a consistent state. This can be important in say a database application where data files and log files are held on separate VDisks, and consequently are being managed by separate relationships. In the event of a disaster, the primary and secondary sites may become disconnected. If the relationships associated with the VDisks are not in a consistency group, then as the disconnection happens, and the Remote Copy relationships stop copying data from the primary to the secondary site, there is no guarantee that updates to the two separate secondary VDisks will stop in a consistent manner.
For proper database operation though it is important that updates to the log files and the database data are made in a consistent and orderly fashion. It is thus crucial in this example that the logfile VDisk and the data VDisk at the secondary site are in a consistent state. This can be achieved by putting the relationships associated with these VDdisks into a consistency group. Remote Copy then ensures that updates to both VDisks at the secondary site are consistent with the updates that have been made at the primary site.
If you specify a consistency group, both the group and the relationship must have been created using the same master cluster and the same auxiliary cluster. The relationship must not be a part of another consistency group.
If the consistency group is not empty, then the consistency group and the relationship must be in the same state. If the consistency group is empty, then it will acquire the state of the first relationship that is added to it. If the state has a copy direction assigned, then the direction of the consistency group and the relationship must match that direction.
If you do not specify a consistency group, a standalone relationship is created.
If you specify the -sync argument, it is taken as a guarantee that the master and auxiliary virtual disks contain identical data at the point when the relationship is created. You must ensure that the auxiliary is created to match the master and that no write operation takes place to either virtual disk before you issue the svctask mkrcrelationship command.
| Note: If you receive an error for this command that indicates that the licensed virtualization capacity has been exceeded, then the command was still effective. However, the return code will indicate the license violation. |
An invocation example
svctask mkrcrelationship -master vdisk1 -aux vdisk2 -name rccopy1 -cluster 0000020063432AFD
The resulting output
RC Relationship, id [28], successfully created