Converting a HyperSwap consistency group to a 3-site consistency group

Edit online

Before you convert an in-production 2-site HyperSwap® consistency group to a 3-site consistency group, verify the state of the consistency group.

Consider the following information:
  • The HyperSwap consistency group must be in the consistent synchronized state.
  • Ensure that a storage pool is configured with enough capacity on the system at the auxiliary-far site. Typically, the target pools at the auxiliary-far site must have at least as much capacity as the current pools in the 2-site consistency group. If the storage pool at the auxiliary-far site does not have enough capacity, copy operations might fail.

Using the management GUI

To convert a HyperSwap consistency group, complete these steps:
  1. On the 3-Site Partnership page, select the Convert HyperSwap consistency group.
  2. Select the HyperSwap consistency group and select Next.
  3. For Group page, enter the following settings:
    Cycle period
    Enter the number of seconds between replication cycles between the asynchronous source and the auxiliary-far system.
  4. Click Next.
  5. Under Choose a pool, specify the numerical ID for the storage pool on the auxiliary-far site that provides capacity for the target volumes. To verify these details, select Launch the Aux-Far management GUI, and select Pools > Pools. If the selected pool is a data reduction pool, select This is a data reduction pool.
  6. Under Aux-Far pool settings, select the method for saving capacity that this pool uses.
  7. In the Volume base name field, enter a naming convention that identifies the volume as part of the 3-site consistency group. The names are automatically generated to include the specified base name, the name of the 3-site consistency group, and an incremental number.
  8. Click Convert.
  9. After the conversion completes, verify that the HyperSwap relationship is part of the 3-site consistency group. Select the 3-site consistency group and verify that all its relationships display in the list of relationships.

    If the conversion does not complete fully, the 3-site consistency group displays the Partial state (Icon identifies the partial state.). If that occurs, select the 3-site consistency group and select Actions > Resume conversion to 3-site.

Using the command-line interface

  1. Run the lsrcconsistgrp command on the HyperSwap storage system to verify the state of the consistency group. Specify the consistency group. 
    [09:15:08] Master-SVC-Node:~ # lsrcconsistgrp CG0
id 0
name CG0
master_cluster_id 0000010030807F4A
master_cluster_name Master
aux_cluster_id 0000010027007DA0
aux_cluster_name AuxNear
primary master
state consistent_synchronized
relationship_count 3
freeze_time 
status 
sync 
copy_type hyperswap
cycling_mode 
cycle_period_seconds
previous_primary 
channel none
RC_rel_id 0
RC_rel_name rel0
RC_rel_id 1
RC_rel_name rel1
RC_rel_id 2
RC_rel_name rel2
    Note: Run the chrcrelationship command to move a HyperSwap relationship into a consistency group on a HyperSwap system. 
    IBM_Storwize:PR_SITE:tsuser>chrcrelationship -consistgrp cg0 rcel1
  2. Run the convertrcrelationship command on the 3-Site Orchestrator host to convert the first 2-site relationship to a 3-site relationship.
    [root@ORCH-HOST cli]# $convertrcrelationship  -type 3site  -cycleperiod 300 -periodicsrc Site1 -pool 0 -iogrp 0 rel0

    The -periodicsrc parameter specifies the site responsible for replicating data to the auxiliary-far site. If you do not specify a value, the default value Site1 is used.

    Specify volume parameters the same as the attributes of volumes between HyperSwap relationships. Volume parameters include compressed and thin-provisioned. -pool on the auxiliary-far site where the new volume is expected to be created is 0, and -iogrp is 0.

  3. Run the convertrcrelationship command to convert the other relationships to 3-site relationships.
    [root@ORCH-HOST cli]# convertrcrelationship  -type 3site -pool 0 -iogrp 0 rel1
[root@ORCH-HOST cli]# convertrcrelationship  -type 3site -pool 0 -iogrp 0 rel2

    The other relationships in the source consistency group can be converted without specifying the -cycleperiod and -periodicsrc parameters.

  4. Data cycling is automatically started after the relationships in the source consistency group are converted in the 3-site consistency group. 
    [root@ORCH-HOST cli]# ls3sitercconsistgrp
name state primary periodic_copy_source sync_copy_state periodic_copy_state freeze_time
cycle_period status
CG0  3site_inconsistent AuxNear Master  consistent_synchronized  copying  300 online
  5. Run the ls3sitercrelationship command to verify the state of the 3-site relationships. 
    [root@localhost home]# ls3sitercrelationship |grep cg0
name    consistgrp master_vdisk_id auxnear_vdisk_id auxfar_vdisk_id sync_copy_progress periodic_copy_progress status
rcrel0  cg0     1     0    71         complete
rcrel1  cg0     5     4    143        complete
rcrel2  cg0     9     8    187        complete