Dell EMC Solutions Enabler 9.2 SRDF Family CLI User Guide

For this sample procedure, the SRDF consistency protection group is enabled at the composite-group level.

This procedure shows the steps to change this setting and enable SRDF consistency protection at the RDFG-name level.

The preceding image shows an R1 and R2 relationship between array 43 and array 90.

After R1 migration, the devices in array 306 will become the source devices for array 90.

Step 1: Querying the sample SRDF/A configuration

Use the symrdf query -detail command to query a configuration with SRDF consistency protection enabled at the composite-group level.

symrdf -cg MigrateRDF query -detailComposite Group Name      :  MigrateRDFComposite Group Type      :  RDF1
Number of Symmetrix Units :  1
Number of RDF (RA) Groups :  1
RDF Consistency Mode      :  MSC

RDFA MSC Consistency Info:{
    Session Status                     : Active
    Consistency State                  : CONSISTENT
    }
Symmetrix ID                      : 000192600043 (Microcode Version: 5876)
Remote Symmetrix ID               : 000192600090 (Microcode Version: 5876)
RDF (RA) Group Number             :   1 (00) 13 (0C)
RDFA Info:
    {
    Cycle Number                       : 29
    Session Status                     : Active - MSC
    Consistency Exempt Devices         : No
    Minimum Cycle Time                 : 00:00:30
    Avg Cycle Time                     : 00:00:30
    Duration of Last cycle             : 00:00:30
    Session Priority                   : 33
    Tracks not Committed to the R2 Side: 0
    Time that R2 is behind R1          : 00:00:42
    R2 Image Capture Time              : Mon Sep 21 13:28:44 2015
    R2 Data is Consistent              : True
    R1 Side Percent Cache In Use       : 0
    R2 Side Percent Cache In Use       : 0
    R1 Side DSE Used Tracks            : 0
    R2 Side DSE Used Tracks            : 0
    Transmit Idle Time                 : 00:00:00
    }

        Source (R1) View             Target (R2) View       MODES
--------------------------------  ------------------------- ----- ------------
               ST                 LI       ST
Standard        A                  N        A
Logical  Sym    T  R1 Inv  R2 Inv  K        T  R1 Inv  R2 Inv       RDF Pair
Device   Dev    E  Tracks Tracks   S Dev    E  Tracks  Tracks MDACE STATE
--------------------------------- -- ------------------------ ----- ------------
DEV001   0005A NR       0       0 RW 00012 WD       0       0 A..X. Consistent
DEV002   000F8 NR       0       0 RW 00029 WD       0       0 A..X. Consistent

Total            ------- -------            ------- -------
Track(s)             0       0                  0       0
  MBs                0.0     0.0                0.0     0.0

Step 2: Changing the SRDF consistency protection setting

To maintain consistency protection after establishing a concurrent SRDF relationship:

• Remove the SRDF consistency protection enabled at the composite-group level, and then
• Enable consistency protection at the RDFG-name level.

In the following example:

• The symcg set -name siteb command sets the SRDF group name to siteb.
• The symcg disable command disables SRDF consistency protection at the composite-group level
• The symcg enable command enables SRDF consistency protection at the RDFG-name level.

symcg -cg MigrateRDF -rdfg 043:13 set -name sitebsymcg -cg MigrateRDF disable

A consistency 'Disable' operation execution is
in progress for composite group 'MigrateRDF'. Please wait...

The consistency 'Disable' operation successfully executed for
composite group 'MigrateRDF'.

symcg -cg MigrateRDF -rdfg name:siteb enable

A consistency 'Enable' operation execution is
in progress for composite group 'MigrateRDF'. Please wait...

The consistency 'Enable' operation successfully executed for
composite group 'MigrateRDF'.

Verifying the changes

Use the symrdf query -detail command to verify that the changes and additions were made to the SRDF/A configuration.

In the following example, SRDF consistency protection is now enabled using the SRDF group name of siteb.

symrdf -cg MigrateRDF query -detail

Composite Group Name      :  MigrateRDF
Composite Group Type      :  RDF1
Number of Symmetrix Units :  1
Number of RDF (RA) Groups :  1
RDF Consistency Mode      :  NONE

RDFG Names:
    {
    RDFG Name                          : siteb
    RDF Consistency Mode               : MSC
    MSC Consistency Info:
        {
        Session Status                 : Active
        Consistency State              : Consistent
        }
    }

Step 3: Pairing devices

Create a device file to pair SRDF devices with the new non-SRDF devices.

Create a device file provides more information.

This pairing is used temporarily to transfer data from the existing R1 devices to the devices that will eventually replace them in an SRDF pair.

In the following example, device file R1MigrateFile contains two pairs:

05A 005
056 006

R1 devices 05A and 056 in array 43 are paired with the new devices 005 and 006 in array 306.

Step 4: Establishing a concurrent SRDF relationship

The symrdf migrate -setup command establishes a concurrent SRDF relationship between the existing R1 devices and the new devices in adaptive copy disk mode, and begins the synchronization of these devices.

The symrdf -migrate -setup -config pair -force command establishes a concurrent SRDF relationship between the R1 devices in array 43 and the new devices in array 306 using SRDF group 17.

This is a temporary relationship to transfer data from the existing R1 to its replacement.

Using the -force option

The -force option is used when SRDF consistency protection is enabled.

symrdf -sid 043 -rdfg 17 -f R1MigrateFile migrate -setup -config pair -force

An RDF 'Migrate Setup' operation execution is
in progress for device file 'R1migrateFile'. Please wait...

    Migrate Setup for R1 device(s) in (043,017)......................Started.
    Create RDF Pair in (0043,017)....................................Started.
    Create RDF Pair in (0043,017)....................................Done.
    Mark target device(s) in (0043,017) for full copy from source....Started.
    Devices: 06F0-06FF in (0043,017)................................ Marked.
    Mark target device(s) in (0043, 017) for full copy from source...Done.
    Merge track tables between source and target in (0043,017).......Started.
    Devices: 06F0-06FF in (0043,017)................................ Merged.
    Merge track tables between source and target in (0043,017).. ....Done.
    Resume RDF link(s) for device(s) in (0043,017)...................Started.
    Resume RDF link(s) for device(s) in (0043,017)...................Done.
    Migrate Setup for R1 device(s) in (0043,017) ....................Done.

The RDF 'Migrate Setup' operation finished successfully
for device file 'R1MigrateFile'.

In the preceding image:

• Devices 05A and 056 are paired with devices 005 and 006 in a concurrent SRDF relationship using SRDF group 17.
• Devices 005 and 006 are made read/write on the SRDF links in adaptive copy disk mode.
• SRDF group 17 is used temporarily to transfer data from the R1 devices to the new devices.

Step 5: Replacing R1 devices with new devices

1. If consistency is enabled, use the symcg disable command to disable it.

   To disable SRDF consistency protection for composite group MigrateRDF:

   symcg -cg MigrateRDF -rdfg name:siteb disable
   
   A consistency 'Disable' operation execution is
   in progress for composite group 'MigrateRDF'. Please wait...
   
   The consistency 'Disable' operation successfully executed for
   composite group 'MigrateRDF'.

2. Terminate any TF/Mirror, TF/Snap, TF/Clone, Open Replicator, and Federated Live Migration sessions.
3. Use the symrdf migrate -replace command to set R1 (R11) device as USR-NR, complete the final synchronization of data between the existing and the new device, and reconfigure the devices into a new SRDF pair.

   The device pairings of the replaced devices are removed. The new devices become R1 devices paired with the existing R2 devices using the original SRDF mode of the replaced pair.

   NOTE:

   The migrate -replace R1 command waits for synchronization to finish and may take a long time. To avoid the locking of the SYMAPI database for this entire time, set the environment variable SYMCLI_CTL_ACCESS=PARALLEL. If you set this variable, you may need to run the symcfg sync command after the R1 migration is complete.

In the following example, the migrate -replace R1 command specifies the new SRDF group 72 to reconfigure and connect the new R1 devices 005 and 006 in array 306 with the R2 devices 012 and 029 in Symmetix 90:

symrdf -sid 043 -rdfg 17 -f R1migrateFile migrate -replace r1 -config pair -new_rdfg 72

An RDF 'Migrate Replace R1' operation execution is
in progress for device file 'R1migrateFile'. Please wait...

    Migrate Replace R1 for new R1 device(s) in (0306, 072)...........Started.
    Waiting for invalid tracks to reach 0 in   (0043, 013)...........Started.
    Waiting for invalid tracks to reach 0 in   (0043, 017)...........Started.
    Waiting for invalid tracks to reach 0 in   (0043, 013)...........Done.
    Waiting for invalid tracks to reach 0 in   (0043, 017)...........915994 remaining.
    Waiting for invalid tracks to reach 0 in   (0043, 017)...........519572 remaining.
    Waiting for invalid tracks to reach 0 in   (0043, 017)...........245889 remaining.
    Waiting for invalid tracks to reach 0 in   (0043, 017)...........107613 remaining.
    Waiting for invalid tracks to reach 0 in   (0043, 017)...........1110 remaining.
    Waiting for invalid tracks to reach 0 in   (0043, 017)...........Done.
    Suspend RDF link(s) for device(s) in (0043,013)..................Started.
    Suspend RDF link(s) for device(s) in (0041,013)..................Done.
    Suspend RDF link(s) for device(s) in (0043,017)..................Done.
    Delete RDF Pair in (0043,013)....................................Started.
    Delete RDF Pair in (0043,017)....................................Started.
    Delete RDF Pair in (0043,013)....................................Done.
    Delete RDF Pair in (0043,017)....................................Done.
    Create RDF Pair in (0306,072)....................................Started.
    Create RDF Pair in (0306,072)....................................Done.
    Resume RDF link(s) for device(s) in (0306,072)...................Started.
    Merge track tables between source and target in (0306,072).......Started.
    Devices: 0690-069F in (0306,072)................................ Merged.
    Merge track tables between source and target in (0306,072).......Done.
    Resume RDF link(s) for device(s) in (0306,072)...................Done.
    Migrate Replace R1 for new R1 device(s) in (0306, 072)...........Done.

The RDF 'Migrate Replace R1' operation finished successfully
for device file 'R1migrateFile'.

After replacing the R1 devices:

• Recreate your device groups and/or composite groups,
• Possibly update your scripts, since the devices are no longer concurrent SRDF.
• Recreate any TF/Mirror, TF/Snap, TF/Clone, Open Replicator, and Federated Live Migration sessions (used on the original R1 devices) on the new R1 devices.

In the following example, the MigrateRDF consistency group is deleted and re-created:

• The symcg delete command deletes the MigrateRDF consistency group.
• The symcg create command recreates MigrateRDF as an RDF1 with consistency.
• The symcg addall dev command add devices MigrateRDF.
• The symcg enable command enables consistency protection.

symcg -force delete MigrateRDF
symcg create MigrateRDF -type rdf1 -rdf_consistency
symcg -cg MigrateRDF -sid 306 -rdfg 72 addall dev
symcg -cg MigratRDF enable

A consistency 'Enable' operation execution is
in progress for composite group 'MigrateRDF'. Please wait...

The consistency 'Enable' operation successfully executed for
composite group 'MigrateRDF'.

When migration is complete (as shown in the following image ):

• SID 306 devices are the R1 devices.
• SID 306 devices are paired with the R2 devices in SID 90.

This new SRDF pair uses the original SRDF mode of the replaced pair.

Step 6: Verifying the new pair and setting changes

Use the symrdf query -detail to verify that:

• The SID 306 devices are now the source devices for SID 90,
• Consistency protection is rebuilt.

symrdf -cg MigrateRDF query -detail

Composite Group Name      :  MigrateRDF
Composite Group Type      :  RDF1
Number of Symmetrix Units :  1
Number of RDF (RA) Groups :  1
RDF Consistency Mode      :  MSC

RDFG MSC Consistency Info:{
	  Session Status                 : Active
	  Consistency State              : CONSISTENT
    }

Symmetrix ID                      : 000190100306 (Microcode Version: 5876)
Remote Symmetrix ID               : 000192600090 (Microcode Version: 5876)
RDF (RA) Group Number             :   3 (02) - siteb
RDFA Info:
    {
    Cycle Number                       : 3
    Session Status                     : Active - MSC
    Consistency Exempt Devices         : No
    Minimum Cycle Time                 : 00:00:30
    Avg Cycle Time                     : 00:00:33
    Duration of Last cycle             : 00:00:30
    Session Priority                   : 33
    Tracks not Committed to the R2 Side: 0
    Time that R2 is behind R1          : 00:00:34
    R2 Image Capture Time              : Mon Sep 21 13:52:03 2015
    R2 Data is Consistent              : True
    R1 Side Percent Cache In Use       : 0
    R2 Side Percent Cache In Use       : 0
    R1 Side DSE Used Tracks            : 0
    R2 Side DSE Used Tracks            : 0
    Transmit Idle Time                 : 00:00:00
    }

        Source (R1) View             Target (R2) View       MODES
--------------------------------  ------------------------- ----- ------------
               ST                 LI       ST
  Standard      A                  N        A
Logical  Sym    T  R1 Inv  R2 Inv  K        T  R1 Inv  R2 Inv       RDF Pair
Device   Dev    E  Tracks Tracks   S Dev    E  Tracks  Tracks MDACE STATE
--------------------------------- -- ------------------------ ----- ------------
DEV001   00005 RW       0       0 RW 00012 WD       0       0 A..X. Consistent
DEV002   00006 RW       0       0 RW 00029 WD       0       0 A..X. Consistent

Total            ------- -------            ------- -------
  Track(s)             0       0                  0       0
  MBs                0.0     0.0                0.0     0.0