Creating a target GAD pair

Global Active Device for VSP One Block
Version
10.5.x
File Size
25537 KB
Audience
anonymous
Part Number
MK-23VSP1B011-11
ft:lastEdition
2026-06-23

This part of GAD pair data migration using GAD creates the temporary GAD pair on the target primary storage system, sets up the target secondary storage system, and then creates a target GAD pair between the target primary and secondary storage systems.

When you create the target GAD pair, you can use either of VSM auto-configuration or VSM manual configuration.



The volume of the primary storage system used at the migration target is virtualized to the volume of the primary storage system used at the migration source when you created a temporary GAD pair (see Creating a temporary GAD pair used for data migration). Therefore, on the secondary storage system used at the migration target, the resource group must be created with the information about the primary storage system used at the migration source as the virtual information.

When you use VSM auto-configuration, you do not need to perform the procedure of creating a resource group (described in Creating a resource group (VSM manual configuration).

  • The temporary GAD pair created for data migration is in the PAIR or COPY status or was suspended by specifying the S-VOL. In the COPY status, the synchronization rate must be 1% or more. If the synchronization rate of the temporary GAD pair is 0%, the target GAD pair cannot be created.
  • The storage system used at the target secondary site was configured for GAD pair data migration.
  1. Create a GAD pair between the target primary and secondary storage systems (the nocopy option is not available).

    For the P-VOL of the target GAD pair, specify the same volume as used for the S-VOL of the temporary GAD pair. For the mirror ID and the quorum disk ID, specify a different ID from the one of the temporary GAD pair.

    If you are managing the source GAD pair by using a consistency group and want to continue using the consistency group for the target GAD pair, or if you want to switch the pair management to that by using a consistency group for data migration, specify a consistency group with a different consistency group ID from the temporary GAD pair

    Note:

    The same quorum disk ID and the same consistency group ID used for the operating source GAD pair can be used for the target GAD pair.

  2. Verify that the target GAD pair has been created.
    Command example:
    pairdisplay -g oraHA02 -fcxe -IH2
Group PairVol(L/R) (Port#,TID, LU),Seq#, LDEV#.P/S,
Status,Fence,%, P-LDEV# M CTG JID AP EM E-Seq# E-LDEV# R/W
QM DM P PR
oraHA02 dev02(L) (CL1-C-0, 0, 0)833333 1111.P-VOL COPY
NEVER , 55 2222 - - 2 1 - - - L/M - D
N D
oraHA02 dev02(R) (CL1-C-0, 0, 0)844444 2222.S-VOL COPY
NEVER ,----- 1111 - - 2 1 - - - B/B - D
N D

    The pair status remains COPY and is not migrated to PAIR, even after the copy operation is completed after the target GAD pair is created.

    If the temporary GAD pair is suspended by specifying the S-VOL, the target GAD pair is migrated from the COPY to PAIR status after the copy operation for the target GAD pair is completed. The synchronization rate of the temporary GAD pair in the COPY status might decrease depending on the I/O status.