Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

GAD 3DC delta resync (GAD UR) operations

You can use CCI commands to implement a GAD 3DC delta resync (GAD+UR) configuration.

For a quorum disk, a volume in an external storage system or a disk in a server is used. Descriptions are based on the assumption that a volume in an external storage system is used as the quorum disk.

GAD 3DC delta resync system configuration

The following figure shows a sample GAD 3DC delta resync (GAD+UR) configuration.

The examples and procedures in this chapter describe this sample GAD+UR configuration.

GUID-1019D8D4-81DD-499D-BC68-DC463435A325-low.png

Sites

The GAD+UR configuration spans the following four sites:

  • Primary site: Site at which the primary storage system operates.
  • GAD secondary site: Site at which the GAD secondary storage system operates.
  • UR secondary storage system site: Site at which the UR secondary storage system operates.
  • Quorum site: Site at which the external storage system containing the GAD quorum disk operates.

Storage systems

The GAD+UR configuration includes the following storage systems:

  • Primary storage system: Contains the P-VOL, UR journal volume (JNL VOL), command device (CMD), and external volume for the quorum disk. The P-VOL and the JNL VOL are virtual volumes of HDP and are assigned capacities from different HDP pools.
  • GAD secondary storage system: Contains the GAD S-VOL, delta UR journal volume, command device, external volume for the quorum disk, and the virtual storage machine (VSM). The GAD S-VOL must have the same virtual LDEV ID as the P-VOL. Therefore it is registered to the VSM. The GAD secondary storage system must be the same model as the primary storage system.
  • UR secondary storage system: Contains the UR S-VOL, UR/delta UR shared journal volume, command device, and external volume for the quorum disk. If the primary storage system is VSP 5000 series, the UR secondary storage system can be VSP 5000 series, VSP G1x00 , VSP F1500, or VSP G/F900 . If the primary storage system is VSP E990, the UR secondary storage system can be VSP E990, VSP E790, VSP E590, VSP G/F370, VSP G/F700, VSP G/F900, VSP G200, G400, G600, G800, VSP F400, F600, F800, or VSP 5000 series.
    Note In a 3DC delta resync (GAD+UR) configuration, VSP 5100 and VSP 5500 can be connected to:
    • VSP G800 and VSP F800
    • VSP G/F370, VSP G/F700, VSP G/F900
    • VSP E series
    • VSP 5000 series

    VSP 5200 and VSP 5600 can be connected to:

    • VSP 5000 series
    • VSP E series: all microcode versions
  • External storage system: Contains the GAD quorum disk.
    NoteIn this example the quorum disk resides in a separate external storage system. If desired, the quorum disk can reside in the UR secondary storage system.

Servers

There are two servers in this sample GAD+UR configuration. One server is connected to the primary storage system and the GAD secondary storage system. The other server is connected to the UR secondary storage system. The servers have the following components:

  • CCI: Manages the configuration of the GAD/UR/delta UR pairs.
  • Configuration definition file: Text file that contains the configuration information for the command device and the GAD/UR/delta UR pairs. It is used by CCI to manage the GAD/UR/delta UR pair configuration.
  • Multi-path software: Controls the alternate paths from the host to the P-VOL or S-VOL.
  • Cluster software at the primary site and GAD secondary site*: Provides clustering of the active-active configuration between the primary host and the GAD secondary host. In addition, the cluster software on the UR secondary host provides clustering of the active-passive configuration in which the primary/GAD secondary hosts are active between the primary/GAD secondary hosts and the UR secondary host.

    * This item does not apply to the sample configuration described in this chapter. In the sample in this chapter the primary host and GAD secondary host are combined.

  • Cluster software at the UR secondary site: Provides clustering of the active-passive configuration in which the remote host becomes the standby host between the primary/secondary host and the remote host.
  • Application (Active) at the primary site and GAD secondary site: Active application. Both primary and secondary hosts are active.
  • Application (Standby) at the UR secondary site: Standby application.

Networks

The GAD+UR configuration has the following network configurations:

  • Network between servers: All servers are connected to the same LAN.
  • Networks between storage systems: There are two types of networks, both of which are connected using FC, between the storage systems:
    • Remote connection (primary-to-GAD secondary storage system, primary-to-UR secondary storage system, GAD secondary storage system-to-UR secondary storage system): Establish a bi-directional connection between the Initiator port and the RCU Target port in the primary, GAD secondary, and UR secondary storage systems.
    • External storage connection (primary-to-external storage, GAD secondary storage system-to-external storage system): Establish a connection between the external port in the primary/GAD secondary storage system and the Target port in the external storage system.
  • Networks between servers and storage: The servers and storage systems are connected using FC. There are two types of networks between the servers and the storage systems:
    • Connection between the server and the primary/GAD secondary storage system: The server is connected to the primary storage system and GAD secondary storage system.
    • Connection between the server and the UR secondary storage system: The server is connected only to the UR secondary storage system.

GAD+UR pairs

When you create a GAD+UR configuration, the GAD pairs must already be registered to a consistency group.

With GAD+UR, when the statuses of the GAD pair (P-VOL and GAD S-VOL) and the UR pair (P-VOL and UR S-VOL) are PAIR and the UR delta resync pair (GAD S-VOL and UR S-VOL) is in the standby status, the operation is performed normally. When the UR delta resync pair status is HOLD, the pair status of the P-VOL is displayed as PSUS, and the journal mirror status is displayed as PJNS in CCI.

Primary storage system settings

The following tables list the settings for the sample primary storage system used in the examples and procedures in this chapter.

Primary storage system

Model

Serial number

VSP 5000 series 11111

VSP G900

411111

Primary volume

Actual LDEV ID

HDP pool ID

Capacity

Port attribute

Port name

LU number

22:22

0

1,024,000 blocks

Target

CL1-A

1

HDP pool volume

Actual LDEV ID

Parity group ID

Capacity

aa:aa

1-1

100 GB

99:99

2-1

100 GB

HDP pool

Pool ID

Pool name

Pool volume

Use

0

PDP_POOL

aa:aa

P-VOL

1

PJNL_POOL

99:99

Journal

Host group

Host group ID

Host group name

Use

CL1-A-1

PVOL_HG1

P-VOL

Journal volume

Actual LDEV ID

HDP pool ID

Capacity

88:88

1

30 GB

Ports for connection between storage systems

Port name

Port attribute*

Target storage system

Use

CL3-A

Bidirectional

GAD secondary storage system

GAD

CL4-A

Bidirectional

GAD secondary storage system

GAD

CL6-A

Bidirectional

UR secondary storage system

UR

CL7-A (VSP 5000 series)

Bidirectional

UR secondary storage system

UR

CL5-C

External

External storage

Quorum disk

*You do not need to set the port attributes on the VSP Gx00 models and VSP Fx00 models and VSP E series.
Pair

Pair type

Pair group name

Device name (LDEV ID)

Mirror ID

CTG ID

GAD

oraHA

dev1(22:22)

0

1

UR

oraREMOTE

dev2(22:22)

1

0

Quorum disk

Quorum disk ID

0

GAD secondary storage system settings

The following tables list the settings for the sample GAD secondary storage system used in the examples and procedures in this chapter.

Primary storage system

Model

Serial number

VSP 5000 series

22222

VSP G900

422222

HDP pool volume

LDEV ID

Parity group ID

Capacity

77:77

13-4

100 GB

99:99

2-1

100 GB

HDP pool

Pool ID

Pool name

Pool volume

Use

0

HA_POOL

77:77

GAD S-VOL

1

LJNL_POOL

99:99

Journal

GAD S-VOL

Actual LDEV ID

HDP pool ID

Capacity

Port attribute

Port name

LU number

44:44

0

1,024,000 block

Target

CL1-C

0

Host group

Host group ID

Host group name

Use

CL1-C-1

1C-G00

GAD S-VOL

CL1-B-1

LVOL_HG2

GAD S-VOL

Journal volume

Actual LDEV ID

HDP pool ID

Capacity

88:88

1

30 GB

Ports for connection between storage systems

Port name

Port attribute*

Target storage system

Use

CL3-C

Bidirectional

Primary storage system

GAD

CL4-C

Bidirectional

Primary storage system

GAD

CL6-C

Bidirectional

UR secondary storage system

UR delta resync

CL7-C (VSP 5000 series)

Bidirectional

UR secondary storage system

UR delta resync

CL5-C

External

External storage

Quorum disk

*You do not need to set the port attributes on VSP G/F350, G/F370, G/F700, G/F900 models, VSP E series.
Pair

Pair type

Pair group name

Device name (LDEV ID)

Mirror ID

CTG ID

GAD

oraHA

dev1(44:44)

0

1

UR delta resync

oraDELTA

dev3(44:44)

2

0

Quorum disk

Quorum disk ID

0

Resource group

Resource group ID

Resource group name

Virtual storage machine (VSM)

Model

Serial number

1

HAGroup1

VSP 5000 series

11111

411111

VSP G900

UR secondary storage system settings

The following tables list the settings for the sample UR secondary storage system used in the examples and procedures in this chapter.

Primary storage system

Model

Serial number

VSP 5000 series 44444

VSP G900

444444

HDP pool volume

LDEV ID

Parity group ID

Capacity

77:77

13-4

100 GB

99:99

2-1

100 GB

HDP pool

Pool ID

Pool name

Pool volume

Use

0

VOL_POOL

77:77

UR S-VOL

1

RJNL_POOL

99:99

Journal

UR S-VOL

Actual LDEV ID

HDP pool ID

Capacity

Port attribute

Port name

LU number

66:66

0

1,024,000 blocks

Target

CL1-A

1

Host group

Host group ID

Host group name

Use

CL1-A-1

REMOTE

UR S-VOL

Journal volume

Actual LDEV ID

HDP pool ID

Capacity

88:88

1

30 GB

Ports for connection between storage systems

Port name

Port attribute*

Target storage system

Use

CL6-A

Bidirectional

Primary storage system

UR

CL7-A (VSP 5000 series)

Bidirectional

Primary storage system

UR

CL6-C

Bidirectional

GAD secondary storage system

UR delta resync

CL7-C (VSP 5000 series)

Bidirectional

GAD secondary storage system

UR delta resync

*You do not need to set the port attributes on VSP G/F350, G/F370, G/F700, G/F900 models, VSP E series.
Pair

Pair type

Pair group name

Device name (LDEV ID)

Mirror ID

CTG ID

UR

oraREMOTE

dev2(66:66)

1

1

UR delta resync

oraDELTA

dev3(66:66)

2

0

CCI server configuration

The following tables list the CCI configuration settings for the pair management server used in the examples and procedures in this chapter.

CCI settings for the pair management server for the primary and GAD secondary storage systems

Instance number

Configuration definition file

Use

0

horcm0.conf

GAD and UR

100

horcm100.conf

Operation in terms of VSM (serial number 11111) of primary storage system

1

horcm1.conf

GAD and UR delta resync

101

horcm101.conf

Operation in terms of VSM (serial number 11111) of GAD secondary storage system

CCI settings for the pair management server at the UR secondary site

Instance number

Configuration definition file

Use

2

horcm2.conf

UR and UR delta resync

Workflow for creating a GAD 3DC delta resync environment

Replication pairs are created in the following order when you set up a GAD 3DC delta resync (GAD+UR) environment:

  1. GAD pair
    NoteWhen you create a GAD+UR configuration, the GAD pairs must already be registered to a consistency group.
  2. UR delta resync pair
  3. UR pair

Workflow for creating a GAD+UR environment:

  1. Preparing the UR secondary site
  2. Installing the software products
  3. Creating command devices
  4. Creating the UR delta resync pairs
  5. Starting GAD+UR operations

Initial state

This chapter describes and provides instructions for using CCI to add a UR delta resync pair and a UR pair to a system that has a GAD pair. In the initial state before configuration, the necessary devices are installed at the primary site and GAD secondary site, the network required for the connections among the devices is physically connected, and the GAD pairs have already been created.

GUID-CA919448-4065-477B-AC77-1B61CACD6F4D-low.png

Preparing the UR secondary site

Workflow
  1. Install the storage system and server at the UR secondary site.
  2. Install the following software on the server:
    • CCI
    • Alternate path software
    • Cluster software
  3. Connect the storage system to the server.
  4. Connect the storage system to the GAD storage systems with physical paths.
GUID-40A1FB1B-6B1A-4291-A6DC-2A8E93413BDC-low.png

Installing the software products

Install the licenses for the following software products on the primary, GAD secondary, and UR secondary storage systems. For details, see the System Administrator Guide.

  • Dynamic Provisioning
  • TrueCopy
  • Remote Replication Extended
  • Global-active device
  • Universal Replicator

Creating command devices

Create a CCI command device in Resource Group 0 in the UR secondary storage system, and make sure that the server recognizes it. Command devices should already exist in the primary and GAD secondary storage systems. You can use HDvM - SN or the raidcom modify ldev command to create a command device.

The following shows the flow of creating a command device. For details, see the Command Control Interface Installation and Configuration Guide.GUID-4583B9DC-D99D-4F79-B886-DBEBE9A19DA6-low.png

NoteThis section describes the procedure for the in-band method using Device Manager - Storage Navigator. The environment can also be set up by using the out-of-band method.
  1. Create the volume for the command device in the UR secondary storage system.
  2. Format the created volume.
  3. Define the created volume on the port connected to the server.
  4. Enable the command device attribute of the created volume, and then enable user authentication of the new command device. For details about creating a command device, see the Provisioning Guide for the storage system.
  5. If necessary, change the topology and fabric settings for the ports defined to the command devices.

Creating the UR delta resync pairs

This section describes the procedure for creating the UR delta resync pairs in your GAD 3DC delta resync (GAD+UR) configuration.

Creating the configuration definition file

Create the CCI configuration definition file in the server at the UR secondary site. The following shows the description example of the configuration definition file.

horcm2.conf
HORCM_MON
#ip_address    service    poll(10ms)     timeout(10ms)
localhost        31002      -1                    3000

HORCM_CMD
\\.\CMD-544444-52733

Starting CCI

Start the CCI instance in the server at the UR secondary site. The following shows the example of command execution for Windows.

NoteThe configuration definition file created when the GAD pair was created is used for instance 1.

Procedure

  1. Start CCI instances 1 and 2.

    • Server connected to the GAD secondary storage system
      horcmstart 1
      starting HORCM inst 1
      HORCM inst 1 starts successfully.
    • Server connected to the UR secondary storage system
      horcmstart 2
      starting HORCM inst 2
      HORCM inst 2 starts successfully.
  2. Enter the user name and the password to authenticate the user.

    • Server connected to the GAD secondary storage system
      raidcom -login <username> <password> -IH1
    • Server connected to the UR secondary storage system
      raidcom -login <username> <password> -IH2
    The -IH option in this example is used for each command to specify an instance. You can also perform the operation using a shell for each instance. To start the shell, specify an instance number to the environment variable HORCMINST, and then execute the command.

Connecting the GAD secondary system and the UR secondary system

To connect the GAD secondary storage system and the UR secondary storage system, set the port attributes and then add the remote connection between the two storage systems.GUID-17795C3D-9204-4BD1-8E6C-18096B922DFF-low.png

Setting the port attributes

To establish the bi-directional remote connections between the GAD secondary storage system and the UR secondary storage system, first set the port attributes on each storage system. The following shows the example of command execution for Windows.

Procedure

  1. Set the attributes of the Bidirectional ports in the GAD secondary storage system and the UR secondary storage system.

    • Server connected to the GAD secondary storage system
    raidcom modify port -port CL6-C -port_attribute ALL -IH1
    raidcom modify port -port CL7-C -port_attribute ALL -IH1
    • Server connected to the UR secondary storage system
    raidcom modify port -port CL6-C -port_attribute ALL -IH2
    raidcom modify port -port CL7-C -port_attribute ALL -IH2
    NoteUse the same procedure to change the port attributes for the alternate paths.
  2. Check the setting of the port attribute.

    • Server connected to the GAD secondary storage system
    raidcom get port -IH1
    PORT   TYPE   ATTR  SPD  LPID  FAB  CONN  SSW  SL  Serial#  WWN               PHY_PORT
    (Omitted)
    CL6-C  FIBRE  MCU   AUT  E8    N    FCAL  N    0   522222   50060e8008000300  -
    (Omitted)
    CL7-C  FIBRE  RCU   AUT  97    N    FCAL  N    0   522222   50060e8008000320  -
    (Omitted)
    • Server connected to the UR secondary storage system
    raidcom get port -IH2
    PORT   TYPE   ATTR  SPD  LPID  FAB  CONN  SSW  SL  Serial#  WWN              PHY_PORT
    (Omitted)
    CL6-C  FIBRE  RCU   AUT  E8    N    FCAL  N    0   544444   50060e8008000300  -
    (Omitted)
    CL7-C  FIBRE  MCU   AUT  97    N    FCAL  N    0   544444   50060e8008000320  -
    (Omitted)

Adding remote connections

After setting the port attributes, you can add the bidirectional remote connections between the GAD secondary storage system and UR secondary storage system. Use the same path group ID for the bidirectional remote connections.

The following shows the example of command execution for Windows.

Note
  • When the secondary storage system is VSP 5000 series, specify 5 + serial number (6 digits in total) in CCI, or specify the serial number only (5 digits in total) in Device Manager - Storage Navigator.
  • When the secondary storage system is VSP G1x00 or VSP F1500, specify 3 + serial number (6 digits in total) in CCI, or specify the serial number only (5 digits in total) in Device Manager - Storage Navigator.
  • To specify the VSP 5000 series, enter R900.
  • The VSP 5000 series is displayed as R9 in command output.
  • To specify VSP G350, G370, G700, G900 and VSP F350, F370, F700, F900, enter M800.
  • VSP G350, G370, G700, G900 and VSP F350, F370, F700, F900 are displayed as M8 in command output.

Procedure

  1. Add a bi-directional remote connection between the GAD primary storage system and UR secondary storage system.

    Add a remote connection whose path group ID is 1 from port CL6-C in the GAD secondary storage system to port CL6-C in the UR secondary storage system, and add a remote connection whose path group ID is 1 from port CL6-C in the UR secondary storage system to port CL6-C in the GAD secondary storage system. Specify the same path group ID to the bidirectional remote connections. After executing the command, confirm that the asynchronous command processing ended normally.

    • Server connected to the GAD secondary storage system
    raidcom add rcu -cu_free 544444 R900 1 -mcu_port CL6-C -rcu_port CL6-C -IH1
    raidcom get command_status -IH1
    HANDLE   SSB1    SSB2    ERR_CNT    Serial#    Description
    00c3     -       -       0          522222     -
    • Server connected to the UR secondary storage system
    raidcom add rcu -cu_free 522222 R900 1 -mcu_port CL7-C -rcu_port CL7-C -IH2
    raidcom get command_status -IH2
    HANDLE    SSB1    SSB2    ERR_CNT    Serial#    Description
    00c3      -       -       0          544444     -
    After adding the initial connections between the storage systems using the raidcom add rcu command, add the alternate paths between the storage systems using the raidcom add rcu_path command.
  2. Check the settings of the remote connection.

    • Server connected to the GAD secondary storage system
    raidcom get rcu -cu_free 544444 R900 1 -IH1
    Serial# ID PID  MCU  RCU  M/R  T  PNO  MPORT RPORT STS_CD SSIDs
    544444  R9   0    -    -  RCU  F    1  CL6-C CL6-C NML_01     -
    • Server connected to the UR secondary storage system
    raidcom get rcu -cu_free 522222 R900 1 -IH2
    Serial# ID PID  MCU  RCU  M/R  T  PNO  MPORT RPORT STS_CD SSIDs
    522222  R9   0    -    -  RCU  F    1  CL7-C CL7-C NML_01     -

Setting up the GAD secondary storage system

To set up the GAD secondary storage system, you must create a pool volume of HDP pool for journal, create an HDP pool for journal, create a journal volume, and create a journal. The following shows the example of command execution for Windows.GUID-AE69F13A-57B8-4745-8996-BF7FFE068C85-low.png

Procedure

  1. Create a pool volume. Specify Parity group 2-1 and create volume 100 GB whose LDEV ID is 0x9999. After executing the command, confirm that the asynchronous command processing ended normally.

    raidcom add ldev -ldev_id 0x9999 -parity_grp_id 2-1 -capacity 100G -IH1
    raidcom get command_status -IH1
    HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
    00c3       -     -        0   522222            -
  2. Perform quick format of the created volume. After executing the command, confirm that the asynchronous command processing ended normally.

    raidcom initialize ldev -operation qfmt -ldev_id 0x9999 -IH1
    raidcom get command_status -IH1
    HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
    00c3       -     -        0   522222            -
  3. Create a pool. Specify the created volume 0x9999 in the pool volume and create an HDP pool whose pool ID is 1 and pool name is LJNL_POOL. After executing the command, confirm that the asynchronous command processing ended normally.

    raidcom add dp_pool -pool_id 1 -pool_name LJNL_POOL -ldev_id 0x9999 -IH1
    raidcom get command_status -IH1
    HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
    00c3       -     -        0   522222            -
  4. Confirm that the volume (LDEV ID: 0x9999) is set in the pool volume in the pool (Pool ID: 1).

    raidcom get ldev -ldev_id 0x9999 -fx -IH1
    Serial# : 522222
    LDEV : 9999
    (Omitted)
    F_POOLID : 1
    VOL_ATTR : CVS : POOL
    (Omitted)
  5. Check the pool capacity.

    raidcom get dp_pool -IH1
    PID  POLS  U(%)  AV_CAP(MB)  TP_CAP(MB)  W(%)  H(%)  Num  LDEV#  LCNT  TL_CAP(MB)
    001	 POLN	    0	     98196		     98196	  	70   	80	   1	 39321	    0	         	0
  6. Check the pool name.

    raidcom get pool -key opt -IH1
    PID  POLS	 U(%) 	POOL_NAME 	 Seq#	 Num 	LDEV#	 H(%) 	VCAP(%) 	TYPE 	PM
    001	 POLN	    0	 LJNL_POOL	522222   	1	 39321	   80	       - 	OPEN  	N
  7. Create a journal volume. Create a virtual volume (DP-VOL) whose capacity is 30 GB and LDEV ID is 0x8888 in HDP pool ID 1. After executing the command, confirm that the asynchronous command processing ended normally.

    raidcom add ldev -pool 1 -ldev_id 0x8888 -capacity 30G -IH1
    raidcom get command_status -IH1
    HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
    00c3       -     -        0   522222            -
  8. Check the created volume.

    raidcom get ldev -ldev_id 0x8888 -fx -IH1
    Serial# : 522222
    LDEV : 8888
    (omitted)
    VOL_ATTR : CVS : HDP
    (omitted)
  9. Create a journal. Specify the volume whose LDEV ID is 0x8888 to create a journal whose journal ID is 0. After executing the command, confirm that the asynchronous command processing ended normally.

    raidcom add journal -journal_id 0 -ldev_id 0x8888 -IH1
    raidcom get command_status -IH1
    HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
    00c3       -     -        0   522222            -
  10. Confirm that the volume (LDEV ID: 0x8888) is registered to the journal (journal ID: 0) and check the journal capacity.

    raidcom get journal -IH1
    JID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK)   Seq# Num LDEV#
    000  0   1 PJNN  4   21 43216fde    30  62914560 522222 1   34952

Setting up the UR secondary storage system

To set up the UR secondary storage system, you must create a pool volume of HDP pool for journal, create an HDP pool for journal, create a journal volume, create a journal, create a pool volume of HDP pool for the UR S-VOL, create an HDP pool for the UR S-VOL, create a UR S-VOL, create a host group, and add an LU path. The following figure provides an overview of creating a journal and the UR secondary volume in the UR secondary storage system.GUID-73C85DEC-648A-4229-8A29-77CFBE1CED0C-low.png

The following shows the example of command execution for Windows.

NoteThis example uses a pool volume of HDP pool for the UR S-VOL. This is not a requirement.

Procedure

  1. Use the following parameters and procedure to create pool volumes of HDP pool for journal, create HDP pool for journal, create journal volume, and create journal in the UR secondary storage system:

    Parameters:
    • RM instance ID: 2
    • Parity group : 2-1
    • Pool volume LDEV ID: 0x9999
    • Pool volume LDEV capacity : 100 GB
    • Pool ID: 1
    • Pool name : RJNL_POOL
    • Journal volume LDEV ID: 0x8888
    • Journal volume LDEV capacity: 30 GB
    • Journal ID: 0
    1. Create a pool volume. Specify Parity group 2-1 and create volume 100 GB whose LDEV ID is 0x9999. After executing the command, confirm that the asynchronous command processing ended normally.

      raidcom add ldev -ldev_id 0x9999 -parity_grp_id 2-1 -capacity 100G -IH2
      raidcom get command_status -IH2
      HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
      00c3      -      -        0   544444  -
    2. Perform quick format of the created volume. After executing the command, confirm that the asynchronous command processing ended normally.

      raidcom initialize ldev -operation qfmt -ldev_id 0x9999 -IH2
      raidcom get command_status -IH2
      HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
      00c3      -      -        0   544444  -
    3. Create a pool. Specify the created volume 0x9999 in the pool volume and create an HDP pool whose pool ID is 1 and pool name is RJNL_POOL. After executing the command, confirm that the asynchronous command processing ended normally.

      raidcom add dp_pool -pool_id 1 -pool_name RJNL_POOL -ldev_id 0x9999 -IH2
      raidcom get command_status -IH2
      HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
      00c3      -      -        0   544444  -
    4. Confirm that the volume (LDEV ID: 0x9999) is set in the pool volume in the pool (Pool ID: 1).

      raidcom get ldev -ldev_id 0x9999 -fx -IH2
      Serial# : 544444
      LDEV : 9999
      (Omitted)
      F_POOLID : 1
      VOL_ATTR : CVS : POOL
      (Omitted)
    5. Check the pool capacity.

      raidcom get dp_pool -IH2 
      PID POLS U(%) AV_CAP(MB) TP_CAP(MB) W(%) H(%) Num LDEV# LCNT TL_CAP(MB)
      001 POLN	  0	 98196      98196	     70  	80	  1	  39321	0		  0
    6. Check the pool name.

      raidcom get pool -key opt -IH2
      PID POLS U(%) POOL_NAME Seq#   Num LDEV# H(%) VCAP(%) TYPE	 PM
      001 POLN 0    RJNL_POOL 544444 1	  39321 80   -       OPEN	 N
    7. Create a journal volume. Create a virtual volume (DP-VOL) whose capacity is 30 GB and LDEV ID is 0x8888 in HDP pool ID 1. After executing the command, confirm that the asynchronous command processing ended normally.

      raidcom add ldev -pool 1 -ldev_id 0x8888 -capacity 30G -IH2
      raidcom get command_status -IH2
      HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
      00c3      -      -        0   544444  -
    8. Check the created journal volume.

      raidcom get ldev -ldev_id 0x8888 -fx -IH2
      Serial# : 544444
      LDEV : 8888
      (omitted)
      VOL_ATTR : CVS : HDP
      (omitted)
    9. Create a journal. Specify the volume whose LDEV ID is 0x8888 to create a journal whose journal ID is 0. After executing the command, confirm that the asynchronous command processing ended normally.

      raidcom add journal -journal_id 0 -ldev_id 0x8888 -IH2
      raidcom get command_status -IH2
      HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
      00c3      -      -        0   544444  -
    10. Confirm that the volume (LDEV ID: 0x9999) is registered to the journal (journal ID: 0) and check the journal capacity.

      raidcom get journal -IH2
      JID   MU   CTG   JNLS   AP   U(%)   Q-Marker   Q-CNT   D-SZ(BLK)   Seq#    Num   LDEV#
      000   0    1     PJNN   4    21     43216fde   30      62914560    522222  1     34952
  2. Use the following parameters and procedure to create pool volumes of HDP pool for the UR S-VOL and create an HDP pool for the UR S-VOL in the UR secondary storage system:

    • RM instance ID: 2
    • Parity group : 13-4
    • Pool volume LDEV ID: 0x7777
    • Pool volume LDEV capacity : 100 GB
    • Pool ID: 0
    • Pool name : VOL_POOL
    1. Create a pool volume. Specify Parity group 13-4 and create volume 100 GB whose LDEV ID is 0x7777. After executing the command, confirm that the asynchronous command processing ended normally.

      raidcom add ldev -ldev_id 0x7777 -parity_grp_id 13-4 -capacity 100G -IH2
      raidcom get command_status -IH2
      HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
      00c3      -      -        0   544444  -
    2. Perform quick format of the created volume. After executing the command, confirm that the asynchronous command processing ended normally.

      raidcom initialize ldev -operation qfmt -ldev_id 0x7777 -IH2
      raidcom get command_status -IH2
      HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
      00c3      -      -        0   544444  -
    3. Create a pool. Specify the created volume 0x7777 in the pool volume and create an HDP pool whose pool ID is 0 and pool name is VOL_POOL. After executing the command, confirm that the asynchronous command processing ended normally.

      raidcom add dp_pool -pool_id 0 -pool_name VOL_POOL -ldev_id 0x7777 -IH2
      raidcom get command_status -IH2
      HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
      00c3      -      -        0   544444  -
    4. Confirm that the volume (LDEV ID: 0x7777) is set in the pool volume in the pool (Pool ID: 0).

      raidcom get ldev -ldev_id 0x7777 -fx -IH2
      Serial# : 544444
      LDEV : 7777
      (Omitted)
      F_POOLID : 0
      VOL_ATTR : CVS : POOL
      (Omitted)
    5. Check the pool capacity.

      raidcom get dp_pool -IH2
      PID	POLS	U(%)	AV_CAP(MB)	TP_CAP(MB)	W(%)	H(%)	Num	LDEV#	LCNT	TL_CAP(MB)
      000	POLN	0	   98196		    98196		    70	  80	  0	  30583	0		  0
    6. Check the pool name.

      raidcom get pool -key opt -IH2
      PID	POLS	U(%)	POOL_NAME	Seq#	  Num	LDEV#	H(%)	VCAP(%)	TYPE	PM
      001	POLN	0	   VOL_POOL	 544444	0	  30583	80	  -	      OPEN	N
  3. Create the UR S-VOL. Create a virtual volume (DP-VOLs) whose capacity is 1,024,000 blocks and LDEV ID is 0x6666 in HDP pool 0. After executing the command, confirm that the asynchronous command processing ended normally.

    raidcom add ldev -pool 1 -ldev_id 0x6666 -capacity 1024000 -IH2
    raidcom get command_status -IH2
    HANDLE  SSB1  SSB2  ERR_CNT  Serial#  Description
    00c3      -      -        0   544444  -
  4. Check the information of the volumes (LDEV ID: 0x6666).

    raidcom get ldev -ldev_id 0x6666 -fx -IH2
    Serial# : 544444
    LDEV : 6666 VIR_LDEV : 6666
    (Omitted)
    VOL_Capacity(BLK) : 41943040
    (Omitted)
    VOL_ATTR : CVS : HDP
    B_POOLID : 0
    (Omitted)
  5. Create a host group. In port CL1-A, create a host group whose host group ID is 1 and host group name is REMOTE. Set the host mode for the host group as necessary.

    Note

    A host group with host group ID 0 exists by default. Perform this procedure only if you want to create a host group with host group ID 1 or greater.

    raidcom add host_grp -port CL1-A-1 -host_grp_name REMOTE -IH2
    raidcom modify host_grp -port CL1-A-1 -host_mode WIN -IH2
  6. Check the information of the host group set in the port (CL1-A).

    raidcom get host_grp -port CL1-A -IH2
    PORT   GID  GROUP_NAME  Serial#  HMD    HMO_BITs
    CL1-A   0   1C-G00      544444   WIN    
    CL1-A   1   REMOTE      544444   WIN
  7. Add an LU path to the UR S-VOL. When adding an LU path to UR S-VOL 0x6666, specify host group CL1-A-1 and LU 1.

    raidcom add lun -port CL1-A-1 -lun_id 1 -ldev_id 0x6666 -IH2
  8. Check the LU path information defined in host group CL1-A-0.

    raidcom get lun -port CL1-A-1 -fx -IH2
    PORT	 GID	HMD	LUN	NUM	LDEV	CM	Serial#	HMO_BITs
    CL1-A	1	  WIN	1	  1	  6666	-	 544444

Updating the CCI configuration definition files

Update the CCI configuration definition file to create a UR delta resync pair. The following shows an example of command execution for Windows and the description example of the configuration definition file for Windows.

Procedure

  1. Stop the CCI instances at the GAD secondary site and UR secondary site.

    • Server connected to the GAD secondary storage system
      horcmshutdown 1
      inst 1:
      horcmshutdown inst 1 !!!
    • Server connected to the UR secondary storage system
      horcmshutdown 2
      inst 2:
      horcmshutdown inst 2 !!!
  2. Edit the configuration definition files at the GAD secondary site and UR secondary site. Add the underlined parts below to the configuration definition files at the GAD secondary site and UR secondary site.

    NoteMake sure to specify the actual LDEV IDs for the GAD pair volumes, not the virtual LDEV IDs.
    • Example of editing the configuration definition file at the GAD secondary site: horcm1.conf
      HORCM_MON
      #ip_address	service	poll(10ms)	timeout(10ms)
      localhost		31001	-1		3000
      
      HORCM_CMD
      \\.\CMD-522222-52734
      
      HORCM_LDEV
      #GRP      DEV   SERIAL  LDEV#  MU#
      oraHA     dev1  522222  44:44  h0
      oraDELTA  dev3  522222  44:44  h2
                                  
      HORCM_INST
      #GPR      IP ADR     PORT#
      oraHA     localhost  31000
      
      HORCM_INSTP
      #dev_group   ip_address   service      pathID
      oraDELTA     localhost    31002        1
    • Example of editing the configuration definition file at the UR secondary site: horcm2.conf
      HORCM_MON
      #ip_address	service	poll(10ms)	timeout(10ms)
      localhost		31002	-1		3000
      
      HORCM_CMD
      \\.\CMD-522222-52733
      
      HORCM_LDEV
      #GRP      DEV   SERIAL  LDEV#  MU#
      oraDELTA  dev3  522222  66:66  h2
      
      HORCM_INSTP
      #dev_group   ip_address   service      pathID
      oraDELTA     localhost    31001        1
  3. Start the CCI instances at the GAD secondary site and UR secondary site.

    • Server connected to the GAD secondary storage system
      horcmstart 1
      starting HORCM inst 1
      HORCM inst 1 starts successfully.
    • Server connected to the UR secondary storage system
      horcmstart 2
      starting HORCM inst 2
      HORCM inst 2 starts successfully.

Creating the UR delta resync pairs

Create a UR delta resync pair. The following shows the example of command execution for Windows.GUID-8BDD7CBA-DB53-4A59-B5CB-308918351864-low.png

NoteSpecify a different mirror ID for the GAD pair and the UR pair sharing a volume.

Procedure

  1. Create a UR delta resync pair from the GAD secondary storage system. Specify the group name oraDELTA, journal ID 0 of the GAD secondary site (delta UR P-VOL), journal ID 0 of the UR secondary site (delta UR S-VOL), and the UR delta resync pair creation option (-nocsus).

    paircreate -g oraDELTA -f async -vl -jp 0 -js 0 -nocsus -IH1
  2. Confirm that the UR delta resync pair creation is completed. In CCI, the pair status of P-VOL is displayed as PSUE, and the mirror status of the journal is displayed as PJNS.

    pairdisplay -g oraDELTA -fxce -IH1
    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
    oraDELTA	dev3(L)		    (CL1-A-1, 0, 1)  522222 4444.P-VOL PSUE    ASYNC , 0  6666	   -	0	  0	  -	 -	 -	     -	      -/-
    oraDELTA	dev3(R)		    (CL1-A-1, 0, 1)  544444 6666.S-VOL SSUS    ASYNC , 0  4444	   -	0	  0	  -	 -	 -	     -	      -/-
    pairdisplay -g oraDELTA -v jnl -IH1
    JID	MU	CTG	JNLS	AP	U(%)	Q-Marker	Q-CNT	D-SZ(BLK)	Seq#	 Num	LDEV#
    000	1	 1  	PJNS	4	 21	  43216fde	30	   512345	   62500	1	  39321

Creating the UR pairs in a GAD+UR configuration

This section describes the procedure for creating the UR pair in a GAD+UR configuration.

Setting port attributes

You can establish the bi-directional remote connections between the primary storage system and UR secondary storage system by first setting the port attributes on each storage system.

The following shows the example of command execution for Windows.

Procedure

  1. Set the attributes of the Bidirectional ports in the primary storage system and UR secondary storage system.

    • Server connected to the primary storage system
      raidcom modify port -port CL6-A -port_attribute ALL -IH0
      raidcom modify port -port CL7-A -port_attribute ALL -IH0
    • Server connected to the UR secondary storage system
      raidcom modify port -port CL6-A -port_attribute ALL -IH2
      raidcom modify port -port CL7-A -port_attribute ALL -IH2
    Use the same procedure to change the port attributes for the alternate paths.
  2. Check the setting of the port attribute.

    • Server connected to the primary storage system
      raidcom get port -IH0
      PORT  TYPE  ATTR SPD LPID FAB CONN SSW SL Serial# WWN              PHY_PORT
      (Omitted)
      CL6-A FIBRE MCU  AUT E8   N   FCAL N   0  511111  50060e8008000340 -
      (Omitted)
      CL7-A FIBRE RCU  AUT 97   N   FCAL N   0  511111  50060e8008000360 -
      (Omitted)
    • Server connected to the UR secondary storage system
      raidcom get port -IH2
      PORT  TYPE  ATTR SPD LPID FAB CONN SSW SL Serial# WWN              PHY_PORT
      (Omitted)
      CL6-A FIBRE RCU  AUT E8   N   FCAL N   0  544444  50060e8008000340 -
      (Omitted)
      CL7-A FIBRE MCU  AUT 97   N   FCAL N   0  544444  50060e8008000360 -
      (Omitted)
      

Adding remote connections

After setting the port attributes, add the remote connections between the primary storage system and UR secondary storage system. The following shows the example of command execution for Windows.

Note
  • When the secondary storage system is VSP 5000 series, specify 5 + serial number (6 digits in total) in CCI, or specify the serial number only (5 digits in total) in Device Manager - Storage Navigator.
  • When the secondary storage system is VSP G1x00 or VSP F1500, specify 3 + serial number (6 digits in total) in CCI, or specify the serial number only (5 digits in total) in Device Manager - Storage Navigator.
  • To specify the VSP 5000 series, enter R900 or XP8.
  • The VSP 5000 series is displayed as R9 in command output.
GUID-7A40A393-663F-4EA8-97FE-45FEB964A02F-low.png

Procedure

  1. Add a bi-directional remote connection between the GAD primary storage system and UR secondary storage system. Add a remote connection whose path group ID is 2 from port CL6-A in the primary storage system to port CL6-A in the UR secondary storage system, and add a remote connection whose path group ID is 2 from port CL7-A in the UR secondary storage system to port CL7-A in the primary storage system. After executing the command, confirm that the asynchronous command processing ended normally.

    • Server connected to the primary storage system
      raidcom add rcu -cu_free 544444 R900 2 -mcu_port CL6-A -rcu_port CL6-A -IH0
      raidcom get command_status -IH0
      HANDLE	SSB1	SSB2	ERR_CNT	Serial#	Description
      00c3	  -	   -	   0	      511111 	-
    • Server connected to the UR secondary storage system
      raidcom add rcu -cu_free 511111 R900 2 -mcu_port CL7-A -rcu_port CL7-A -IH2
      raidcom get command_status -IH2
      HANDLE	SSB1	SSB2	ERR_CNT	Serial#	Description
      00c3  	-	   -	   0	      544444 	-
    Add the alternate paths between the storage systems using the raidcom add rcu_path command.
  2. Check the settings of the remote connection.

    • Server connected to the primary storage system
      raidcom get rcu -cu_free 544444 R900 2 -IH0
      Serial#	ID	PID	MCU	RCU	M/R	T	PNO	MPORT	RPORT	STS_CD	SSIDs
      544444	 R9	0	  -	  -	  RCU	F	2	  CL6-A	CL6-A	NML_01	-
    • Server connected to the UR secondary storage system
      raidcom get rcu -cu_free 511111 R900 2 -IH2
      Serial#	ID	PID	MCU	RCU	M/R	T	PNO	MPORT	RPORT	STS_CD	SSIDs
      511111	 R9	0	  -	  -	  RCU	F	2	  CL7-A	CL7-A	NML_01	-

Setting up the primary storage system

On the primary storage system, create a pool volume of HDP pool for journal, create an HDP pool for journal, create a journal volume, and create a journal. The following shows the example of command execution for Windows. GUID-F30AFC03-0925-4AD8-B85E-5B937CD0C6D5-low.png

Procedure

  1. Create a pool volume. Specify Parity group 2-1 and create a volume whose capacity is 100 GB and whose LDEV ID is 0x9999. After executing the command, confirm that the asynchronous command processing ended normally.

    raidcom add ldev -ldev_id 0x9999 -parity_grp_id 2-1 -capacity 100G -IH0
    raidcom get command_status -IH0
    HANDLE	SSB1	SSB2	ERR_CNT	Serial#	Description
    00c3	  -	   -	   0	      511111 	-
  2. Perform a quick format of the created volume. After executing the command, confirm that the asynchronous command processing ended normally.

    raidcom initialize ldev -operation qfmt -ldev_id 0x9999 -IH0
    raidcom get command_status -IH0
    HANDLE	SSB1	SSB2	ERR_CNT	Serial#	Description
    00c3	  -	   -	   0	      511111 	-
  3. Create a pool. Specify the created volume 0x9999 in the pool volume and create an HDP pool whose pool ID is 1 and whose pool name is PJNL_POOL. After executing the command, confirm that the asynchronous command processing ended normally.

    raidcom add dp_pool -pool_id 1 -pool_name PJNL_POOL -ldev_id 0x9999 -IH0
    raidcom get command_status -IH0
    HANDLE	SSB1	SSB2	ERR_CNT	Serial#	Description
    00c3	  -	   -	   0	      511111 	-
  4. Confirm that the volume (LDEV ID: 0x9999) is set in the pool volume in the pool (Pool ID: 1).

    raidcom get ldev -ldev_id 0x9999 -fx -IH0
    Serial# : 511111
    LDEV : 9999
    (Omitted)
    F_POOLID : 1
    VOL_ATTR : CVS : POOL
    (Omitted)
  5. Check the pool capacity.

    raidcom get dp_pool -IH0
    PID	POLS	U(%)	AV_CAP(MB)	TP_CAP(MB)	W(%)	H(%)	Num	LDEV#	LCNT	TL_CAP(MB)
    001	POLN	0	   98196		    98196		    70	  80	  1	  39321	0		  0
  6. Check the pool name.

    raidcom get pool -key opt -IH0
    PID	POLS	U(%)	POOL_NAME	Seq#	  Num	LDEV#	H(%)	VCAP(%)	TYPE	PM
    001	POLN	0   	PJNL_POOL	511111	1	  39321	80	  -	      OPEN	N
  7. Create a journal volume. Create a virtual volume (DP-VOL) whose capacity is 30 GB and whose LDEV ID is 0x8888 in HDP pool ID 1. After executing the command, confirm that the asynchronous command processing ended normally.

    raidcom add ldev -pool 1 -ldev_id 0x8888 -capacity 30G -IH0
    raidcom get command_status -IH0
    HANDLE	SSB1	SSB2	ERR_CNT	Serial#	Description
    00c3	  -	   -	   0	      511111 	-
  8. Check the created volume.

    raidcom get ldev -ldev_id 0x8888 -fx -IH0
    Serial# : 511111
    LDEV : 8888
    (omitted)
    VOL_ATTR : CVS : HDP
    (omitted)
  9. Create a journal. Specify the volume whose LDEV ID is 0x8888 to create a journal whose journal ID is 0. After executing the command, confirm that the asynchronous command processing ended normally.

    raidcom add journal -journal_id 0 -ldev_id 0x8888 -IH0
    raidcom get command_status -IH0
    HANDLE	SSB1	SSB2	ERR_CNT	Serial#	Description
    00c3	  -	   -	   0	      511111 	-
  10. Confirm that the volume (LDEV ID: 0x8888) is registered to the journal (journal ID: 0) and check the journal capacity.

    raidcom get journal -IH0
    JID	MU	CTG	JNLS	AP	U(%)	Q-Marker	Q-CNT	D-SZ(BLK)		Seq#	  Num	LDEV#
    000	0	 1	  PJNN	4	 21	  43216fde	30	   62914560		 511111	1	  34952

Updating the CCI configuration definition files

You can update the configuration definition file to create a UR pair. The following shows the example of command execution for Windows and description example of the configuration definition file for Windows.

Procedure

  1. Stop the CCI instances at the primary and UR secondary sites.

    • Server connected to the primary storage system
      horcmshutdown 0
      inst 0:
      horcmshutdown inst 0 !!!
    • Server connected to the UR secondary storage system
      horcmshutdown 2
      inst 2:
      horcmshutdown inst 2 !!!
  2. Edit the configuration definition files at the primary and UR secondary sites.

    Add the bold parts below to the configuration definition files at the primary and UR secondary sites. The following information is important to know as you edit configuration definition files:
    • Make sure to specify the actual LDEV IDs for the GAD pair volumes, not the virtual LDEV IDs.
    • If you use CCI to operate a GAD pair created by Device Manager - Storage Navigator, the MU# in the configuration definition file of CCI must be the same as the mirror ID you specified when creating the GAD pair by Device Manager - Storage Navigator.

      If the MU# does not match the mirror ID, you cannot operate the GAD pair using CCI.

    Example of editing the configuration definition file at the primary site: horcm0.conf

    HORCM_MON
    #ip_address	   service	poll(10ms)	   timeout(10ms)
    localhost		 31000	  -1		       3000
    
    HORCM_CMD
    \\.\CMD-511111-52735
    
    HORCM_LDEV
    #GRP      DEV   SERIAL     LDEV#     MU#
    oraHA     dev1  511111     22:22     h0
    oraREMOTE dev2  511111	 22:22	 h1
                                
    HORCM_INST
    #GPR      IP ADR     PORT#
    oraHA     localhost  31001
    
    HORCM_INSTP
    #dev_group   ip_address   service      pathID
    oraREMOTE    localhost    31002        2

    Example of editing the configuration definition file at the UR secondary site: horcm2.conf

    HORCM_MON
    #ip_address	     service	     poll(10ms)  	   timeout(10ms)
    localhost		      31002	       -1       	         3000
    
    HORCM_CMD
    \\.\CMD-544444-52733
    
    HORCM_LDEV
    #GRP         DEV      SERIAL     LDEV#     MU#
    oraDELTA	 dev3	 544444	 66:66	 h2
    oraREMOTE	dev2	 544444	 66:66	 h1
    
    HORCM_INST
    #GPR            IP ADR              PORT#
    oraDELTA	       localhost		         31001
    
    HORCM_INSTP
    #dev_group      ip_address      service         pathID
    oraREMOTE       localhost       31000           2
  3. Start the CCI instances at the GAD secondary site and UR secondary site.

    • Server connected to the primary storage system
      horcmstart 0
      starting HORCM inst 0
      HORCM inst 0 starts successfully.
    • Server connected to the UR secondary storage system
      horcmstart 2
      starting HORCM inst 2
      HORCM inst 2 starts successfully.

Creating the UR pairs

Create a UR pair. The following shows the example of command execution for Windows.

Procedure

  1. Create a UR pair. Specify the group name URGPR, journal ID 0 of the GAD secondary site (UR P-VOL), and journal ID 0 of the UR secondary site (UR S-VOL).

    paircreate -g oraREMOTE -f async -vl -jp 0 -js 0 -IH0
  2. Confirm that UR pair creation is completed.

    pairdisplay -g oraREMOTE -fxce -IH0
    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
    oraREMOTE	dev2(L)		    (CL1-A-1, 0, 1)  511111 2222.P-VOL 
    PAIR    ASYNC, 0  6666	   -	0	  0	  -	 -	 -	     -	      -/-
    oraREMOTE	dev2(R)		    (CL1-A-1, 0, 1)  544444 6666.S-VOL 
    PAIR    ASYNC, 0  2222	   -	0	  0  	- 	- 	-     	-      	-/-
    The following figure shows the configuration after UR pair creation is completed.GUID-137D479A-60C5-4D89-ADC7-622DB0D48778-low.png

Starting GAD+UR operations

This section describes the procedure for starting operations to have the normal operation status of GAD+UR (UR delta resync pair status changes from PSUE to PSUS) after each pair of GAD+UR is created. After the following procedure, the GAD+UR configuration is ready for normal operation as shown in GAD 3DC delta resync system configuration.

Procedure

  1. Issuing update I/O to P-VOL/GAD S-VOL: To have the normal GAD+UR operation status, keep updating I/O to P-VOL or GAD S-VOL and wait for two minutes.

    If update I/O is issued to P-VOL or GAD S-VOL, the status information of GAD+UR is reported among the primary, GAD secondary, and UR secondary storage systems. At the time, the UR delta resync pair status is changed from PSUE to PSUS.
  2. Checking UR delta resync pair status and mirror status: Confirm in the GAD secondary storage system the UR delta resync pair status and the mirror status of the journal. Confirm that the UR delta resync pair status is HOLD. In CCI, the pair status of the P-VOL is displayed as PSUS, and the mirror status of the journal is displayed as PJNS.

    pairdisplay -g oraDELTA -fxce -IH1
    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
    oraDELTA dev3(L)      (CL1-A-1, 0, 1)  522222 4444.P-VOL 
    PSUS    ASYNC, 100 6666    -  0   0   -  -  -      -       L/M
    oraDELTA dev3(R)      (CL1-A-1, 0, 1)  544444 6666.S-VOL 
    SSUS    ASYNC, 100 4444    -  0   0   -  -  -      -       L/M
    pairdisplay -g oraDELTA -v jnl -IH1
    JID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq#  Num LDEV#
    000 1  1   PJNS 4  21   43216fde 30    512345    62500 1   39321
    NoteWhen checking the pair status in Device Manager - Storage Navigator, make sure to refresh the screen (select Refresh All in the File menu) to update the information being displayed. The status of the UR delta resync pairs changes from HOLDING to HOLD.
  3. Confirm that no failure SIMs are displayed.