convertrcrelationship

Edit online

Use the convertrcrelationship command to convert an existing 2-site remote copy relationship to a 3-site relationship. You can also use this command to convert one or more 3-site relationships to a 2-site relationship.

Syntax

Parameters

-type site_type: (Required) Specifies the new type for the remote copy relationship group. Valid values include 2site or 3site.
Note: To configure and manage both 3-site configurations, site_type 2site is applicable from IBM Spectrum Virtualize 3-Site Orchestrator 4.0 and later.
-periodicsrc periodic_source_site_name: (Optional) Specifies the source site system name or alias for periodic replication. This parameter is optional for a Hyperswap topology system. The user may chose to provide a value of Hyperswap site_name if a specific site is the periodicsrc. If no value is provided, 3-Site Orchestrator defines the master site as periodicsrc for the 3-site consistency group.
-cycleperiod cycleperiod: (Required) Specifies the cycle period in seconds for periodic replication. This parameter must be specified for the first relationship that is converted within a 2-site consistency group. The value must be greater than or equal to 300 (default).
-pool auxfar_pool_id: (Required) Specifies the storage pool ID for the new volume on the auxiliary-far site.
-iogrp auxfar_iogrp_id: (Optional) Specifies the caching I/O group ID for the new volume on the auxiliary-far site.
-thin: (Optional) Specifies a thin-provisioned volume type. This parameter is mutually exclusive with -compressed. If you do not specify this parameter, the volume is standard-provisioned.
-compressed: (Optional) Specifies a compressed volume type. This parameter is mutually exclusive with -thin. If you do not specify this parameter, the volume is fully allocated.
-deduplicated: (Optional) Specifies a deduplicated volume type. This parameter must be used with -thin or -compressed. If you do not specify this parameter, the volume is standard-provisioned.
-volumename auxfar_volume_name: (Optional) Specifies the name for the new volume with data on the auxiliary-far site.
2site_relationship_name: (Required) Specifies the source 2-site relationship name that you want to convert.
-consistgrpname 3site_consistency_group_name: Specifies the name of the 3-site consistency group to which you are adding a 2-site relationship.
Note: This value is required if you are adding a new relationship with data to the existing 3-site consistency group. It is applicable from IBM Spectrum Virtualize 3-Site Orchestrator 4.0 and later.

Description

In a Metro Mirror and HyperSwap topology system, this command is used to convert an existing 2-site relationship to a 3-site relationship.

A source 2-site remote copy relationship must be present between the master and auxiliary-near sites and in a consistent_synchronized state. When a 2-site relationship is migrated to a 3-site relationship, a new volume is created on the specified auxiliary-far site. When the first 2-site relationship within a 2-site consistency group is converted, a corresponding 3-site relationship with the same name is created. When all of the relationships in the 2-site consistency group are converted to 3-site relationships, 3-site data cycling is started automatically. The first data cycle synchronizes all of the volumes on the auxiliary-far site before incremental synchronization is started. During the first cycle, the newly created 3-site consistency group is in the 3site_inconsistent state.

To convert a stand-alone 2-site remote copy relationship into a 3-site consistency group, it must first be added to a 2-site remote copy consistency group before you convert the resulting 2-site consistency group into a 3-site consistency group.

If you are converting a stand-alone 2-site remote copy relationship that contains data to a 3-site consistency group, ensure that the 3-site consistency group is stopped before converting the 2-site relationship. After you run the convertercrelationship the status of the new relationship is new in the results of the ls3sitercrelationship command. This status means that the 2-site remote copy relationship was added to the consistency group, but has not yet been synchronized on the auxiliary-far site.

To convert a single volume on any of the near sites to a 3-site relationship, the volume must first be converted into a 2-site relationship (within a 2-site consistency group) that is in a consistent_synchronized state before you convert it to a 3-site relationship.

This command fails if change volumes are configured for the near site relationship.

To remove a 3-site relationship from 3-site consistency group, you must ensure that the following condition is met:

The 3-site consistency group must not be in error and all three sites are reachable and online.
The 3-site consistency group state must be stopped.
Only one relationship can be removed and reverted at one time.
The partial state of 3-site consistency group is only supported in case of failure of addnewrelationship command or convertrcrelationship command or failure in removing relationship from 3-site consistency group to 2-site consistency group.
When 3-site consistency group moved to partial state on failure, the error should be fixed. The removal will resume only after fixing the error.

An invocation example with the default parameters (that is, no periodic source provided).


#convertrcrelationship -type 3site -cycleperiod 300 -pool 0 -iogrp 0 rcrel60
3-site RC relationship created with volume id [13].

An invocation example of converting a 2-site relationship with data


# ls3sitercconsistgrp
name       state              primary           periodic_copy_source sync_copy_state         periodic_copy_state freeze_time         cycle_period status
rccstgrp0  stopped            threesite_hs      site1                consistent_synchronized idling              2022/01/04/08/48/12 60           online

# convertrcrelationship -type 3site -periodicsrc site1 -cycleperiod 60 -pool 1 -consistgrpname rccstgrp0 rcrel16
3-site RC relationship created with volume id [48].

# ls3sitercrelationship
name     consistgrp master_vdisk_id auxnear_vdisk_id auxfar_vdisk_id sync_copy_progress periodic_copy_progress status
rcrel0   rccstgrp0  0               1                0                                                         complete
rcrel16  rccstgrp0  64              65               48                                                        new

An invocation example with periodic source defined as site1.

# convertrcrelationship -type 3site -periodicsrc site1 -cycleperiod 300 -pool 0 -iogrp 0 rcrel70
3-site RC relationship created with volume id [15].

An invocation example where the name of the site (for example, Hyperswap site) is used for the periodicsrc value.

ls3siteconfig

The resulting output:

master_name threesite_hyperswap
master_site_name site1
master_site_status online
master_ip1 x.xx.xx.xxx
master_ip1_status reachable
master_ip2
master_ip2_status not_configured
master_port 4488
auxnear_name threesite_hyperswap
auxnear_site_name site2
auxnear_site_status online
auxnear_ip1 x.xx.xx.xxx
auxnear_ip1_status reachable
auxnear_ip2
auxnear_ip2_status not_configured
auxnear_port 4488
auxfar_name threesite_auxfar
auxfar_site_status online
auxfar_ip1 x.xx.xx.xxx
auxfar_ip1_status reachable
auxfar_ip2
auxfar_ip2_status not_configured
auxfar_port 4489
username tsuser
keyfile /root/.ssh/id_rsa
topology hyperswap
orchestrator_version 4.0.220107074304