Maintaining the UR system

You can change the maximum number of volumes that can be copied concurrently by adjusting the Maximum Initial Copy Activities setting (range = 1 to 128, default = 64). For example, you can increase this setting when you need to create or resynchronize a large number of pairs concurrently, and you can decrease this setting when you need to limit the impact of initial copy operations on system performance.

For details and instructions, see Setting the maximum initial copy activities option.

Parent Topic

• Pair maintenance

Before you begin

Procedure

1. In the Explorer pane, expand the Storage Systems tree.

2. Expand the target storage system tree, expand Replication, and click Remote Replication.

3. In the UR Pairs tab, select the pair whose options are to be changed.

4. Click More Actions Edit Pair Options.

   NoteWhen you select multiple pairs on the UR Pairs tab, Edit Pair Options values may be blank because the selected pairs have different values.

   When you specify a value, it is set for all selected pairs.

5. In the Edit Pair Options window, for Error Level, specify the system response if a failure occurs in the pair.

   • Mirror: Splits all pairs in the failed pair’s mirror. Mirror is the default.

     However, if a volume failure occurs while the pair status is COPY, only the target pair in the mirror is split, even if Mirror is specified.

   • LU: Splits only the pair that failed.

6. Click Finish.

7. In the Confirm window, review the settings, enter a task name, and click Apply.

Parent Topic

• Pair maintenance

Before you begin

Procedure

1. In the Explorer pane, expand the Storage Systems tree.

2. Expand the target storage system tree, and click Logical Devices.

3. In the LDEVs tab, select the LDEV belonging to the pair that you want to delete forcibly, and then click More Actions Force Delete Pairs (UR Pairs).

4. In the Force Delete Pairs (UR Pairs) window, ensure that the volume you want to forcibly delete is in the Selected LDEV table.

5. Enter a name in the Task Name box.

6. Click Apply to save your settings to the system.

Parent Topic

• Pair maintenance

Procedure

1. Delete all UR pairs that use the V-VOL for which you want to release the pages by using the pairsplit -S command.

2. Make sure that system option mode 755 is set to OFF. When system option mode 755 is set to ON, you cannot reclaim zero pages. For details about setting system option modes, contact your customer support representative.

3. Restore the blocked pool. For details, see the Provisioning Guide for your storage system.

4. Release the V-VOL pages by using the raidcom modify ldev command. Releasing pages might take some time. For details, see the Provisioning Guide for your storage system.

Parent Topic

• Pair maintenance

Procedure

1. Verify that the status for all mirrors in the journal is Stopped.

   If the mirror status is not Stopped, you must split all UR pairs belonging to the journal and then verify that the status for all mirrors in the journal is changed to Stopped.

2. Add a reserve journal volume. For details, see Adding a reserve journal volume.

   NoteIf an unallocated journal volume is not available to become the reserve journal volume, you must delete the journal, restore the blocked journal volume, register the journal volume to the journal again, and then create the UR pair. Allocate a DP-VOL to the journal volume. For details about the restoration procedure when the DP-VOL is blocked, see the Provisioning Guide for your storage system.

3. Verify that the volume you added is a reserve journal volume.

   • Device Manager - Storage Navigator:

     Use the Journal Volumes window (Type: Reserve Journal).

   • CCI:

     Use the raidcom get journal command.

     An LDEV that is not displayed is a reserve journal volume.

4. Delete the first journal volume.

5. Resynchronize the pair, and then restore the UR pair.

Parent Topic

• Pair maintenance

Procedure

1. Resolve the problem with the volume, and then resynchronize the pair and restore the UR pair.

   If the problem with the volume is not resolved, perform the following steps:

   1. Delete the UR pair.

   2. Delete the journal volume.

   3. Re-create the journal using a volume that does not have any problems.

   4. Re-create the UR pair.

Parent Topic

• Pair maintenance

Before you begin

Procedure

1. In the Explorer pane, expand the Storage Systems tree.

2. Expand the target storage system tree, expand Replication, and click Journals.

3. In the Journals tab, select the journal whose options you want to change.

4. Click Edit Journal Options.

5. In the Edit Journal Options dialog box, change the following options as needed.

   • Inflow Control
   • Data Overflow Watch
   • Cache Mode
   For descriptions, see the procedure in Creating journals and adding journal volumes .

6. Click Finish.

7. In the Confirm window, review the settings and enter a task name in the Task Name box.

8. Click Apply to save your settings to the system.

Parent Topic

• Journal and mirror maintenance

Before you begin

Procedure

1. In the Explorer pane, expand the Storage Systems tree.

2. Expand the target storage system tree, expand Replication, and click Remote Replication.

3. In the Mirrors tab, select the mirror whose options you want to change.

4. Click More Actions Edit Mirror Options.

5. In the Edit Mirror Options window, for Path Watch Time, specify the interval from the time when a physical path failure occurs, such as a path disconnection, to the time when the mirror is suspended. Ranges are from 1 to 59 minutes, 1 to 23 hours, or 1 to 30 days. A numeric value is required.

   The interval must be the same for master and restore journals in the same mirror, otherwise the journals suspend at different times. See next step to use this setting for both journals.
   ImportantIf you want a mirror to split immediately after a physical path failure occurs, such as a path disconnection, ask customer support to set advanced system settings No. 15 to ON and set advanced system settings No. 16 to OFF.

6. For Path Watch Time Transfer, specify whether to use the same Path Watch Time value you specified for the master journal for the restore journal. Specify this option in the primary site only.

   • Yes: The Path Watch Time value is also used for the restore journal.

     For a pair in a delta resync configuration, select Yes in the primary site.

   • No (default): The Path Watch Time value is not used for the restore journal.

7. For Copy Pace, specify the pace for initial copy activity per volume. Specify this option in the primary site only.

   • Slower is the default.
   • If specifying Medium, ensure that write I/O is 10 MB/s or less per parity group. If it exceeds 10 MB/s, pairs may be suspended.
   • If specifying Faster, ensure that I/O will not occur. If update I/O occurs, pairs may be suspended.

8. For Transfer Speed, specify data transfer line speed in Mbps (megabits per second). You can specify 256, 100, 10, or 3.

   • Use 3 when the transfer speed is 3 to 9 Mbps.
   • Use 10 when the transfer speed is 10 to 99 Mbps.
   • Use 100 when the transfer speed is 100 to 255 Mbps.
   • Use 256 when the transfer speed is 256 Mbps or higher.
   NoteThis setting does not affect master journals unless the CCI horctakeover command is used to change a master journal into a restore journal.

9. For Delta Resync Failure, specify the processing that takes place when the delta resync operation cannot be performed. Specify this option in the primary site only.

   - Entire Copy (default): the entire P-VOL is copied to the S-VOL. Use Entire if your journals are part of a multiple-journal configuration in a CCI consistency group. - No Copy: No processing occurs: the S-VOL is not updated.

10. Click Finish.

11. In the Confirm window, review the settings and enter a task name in the Task Name box.

12. Click Apply to save your settings to the system.

Parent Topic

• Journal and mirror maintenance

Before you begin

Procedure

1. In the Explorer pane, expand the Storage Systems tree.

2. Expand the target storage system tree, expand Replication, and click Remote Replication.

3. In the Mirrors tab, select the Journal ID link for the journal you want to add journal volumes to.

4. In the Journal Volumes tab, click Assign Journal Volumes.

5. In the Assign Journal Volumes window, from the Unassigned Journal Volumes table, select the journal volume to be added to the journal, and then click Add. The selected journal volume moves to the Assigned Journal Volumes table.

   To remove a volume from the table, select the volume and click Remove.
   NoteOnly OPEN-V volumes are displayed in the Unassigned Journal Volumes table.

6. Click Finish.

7. In the Confirm window, review the settings and enter a task name in the Task Name box.

8. Click Apply to save your settings to the system.

Parent Topic

• Journal and mirror maintenance

You can use the reserve journal volume to restore a disk in a pool or pool volume to which the journal volume belongs.

Before you begin

Procedure

1. Add a reserve journal volume to the journal.

   For details, see Adding a reserve journal volume.

2. Delete the journal volume that is in use.

   For details, see Deleting journal volumes from a journal .

3. Resynchronize the journal.

Parent Topic

• Journal and mirror maintenance

Child Topics

• Replacing a journal volume with a reserve journal volume using CCI
• Replacing a journal volume with a reserve journal volume of a UR pair for delta resync with GAD (VSP E series)

Before you begin

Procedure

1. In the Explorer pane, expand the Storage Systems tree.

2. Expand the target storage system tree, expand Replication, and click Remote Replication.

3. In the Mirrors tab, select the Journal ID link for the journal to which you want to add journal volumes.

4. In the Journal Volumes tab, click Assign Journal Volumes.

5. In the Assign Journal Volumes window, from the Unassigned Journal Volumes table, select the journal volume to be added to the journal, and then click Add. The selected journal volume moves to the Assigned Journal Volumes table.

   To remove a volume from the table, select the volume and click Remove.

6. Click Finish.

7. In the Confirm window, review the settings and enter a task name in the Task Name box.

8. Click Apply to save your settings to the system.

Parent Topic

• Journal and mirror maintenance

Before you begin

Procedure

1. In the Explorer pane, expand the Storage Systems tree.

2. Expand the target storage system tree, expand Replication, and click Remote Replication.

3. In the Mirrors tab, select the Journal ID link for the journal you want to delete journal volumes from.

4. In the Journal Volumes tab, click Assign Journal Volumes.

5. From the Assigned Journal Volumes table, select the volumes to be deleted and click Remove.

6. Click Finish.

7. In the Confirm window, review the settings and enter a task name in the Task Name box.

8. Click Apply to save your settings to the system.

Parent Topic

• Journal and mirror maintenance

Journals can be deleted from either system.

Before you begin

Procedure

1. In the Explorer pane, expand the Storage Systems tree.

2. Expand the target storage system tree, expand Replication, and click Journals.

3. In the Journals tab, select the Journal ID for the journal to be deleted.

4. Click Delete Journals.

5. In the Delete Journals window, make sure the journals you want to delete are listed in the Selected Journals table. To view more information about a journal, select the journal and click Detail. If you need to change the selections, click Cancel.

6. When satisfied, click Finish.

7. In the Confirm window, review the settings and enter a task name in the Task Name box.

8. Click Apply to save your settings to the system.

Parent Topic

• Journal and mirror maintenance

Before you begin

Procedure

1. In the Explorer pane, expand the Storage Systems tree.

2. Expand the target storage system tree, expand Replication, and click Remote Connections.

3. In the Connections (To) tab, select the Remote Storage System with the data-transfer waiting-time to be changed.

4. Click Edit Remote Connection Options.

5. In the Edit Remote Connection Options window, note that Minimum Paths cannot be changed.

6. For RIO MIH Time, specify the amount of time the system waits after data copy between storage systems through the slot where the copy was requested begins before the copy ends. The range is 10 to 100 seconds, and the default is 15 seconds.

7. Click Finish.

8. In the Confirm window, review the settings and enter a task name in the Task Name box.

9. Click Apply to save your settings to the system.

Parent Topic

• Remote path maintenance

Before you begin

Procedure

1. In the Explorer pane, expand the Storage Systems tree.

2. Expand the target storage system tree, expand Replication, and click Remote Connections.

3. In the Connections (To) tab, select the Remote Storage System with the remote path you want to delete.

4. Click More Actions Remove Remote Paths.

5. In the Remove Remote Paths window, in the Remote Paths box, check the Remove box or boxes for the remote paths to be deleted.

6. Click Finish.

7. In the Confirm window, review the settings and enter a task name in the Task Name box.

8. Click Apply to save your settings to the system.

Parent Topic

• Remote path maintenance

Before you begin

Procedure

1. In the Explorer pane, expand the Storage Systems tree.

2. Expand the target storage system tree, expand Replication, and click Remote Connections.

3. In the Connections (To) tab, select the Remote Storage System whose remote connection you want to delete.

4. Click More Actions Remove Remote Connections.

5. In the Remove Remote Connections window, in the Selected Remote Connections box, check the Remove box for the remote connection to be deleted. To view more information about a remote path, select the path and click Detail. If you need to change the selections, click Cancel.

6. Click Finish.

7. In the Confirm window, review the settings and enter a task name in the Task Name box.

8. Click Apply to save your settings to the system.

Parent Topic

• Remote path maintenance

Before you begin

Procedure

1. Verify that both the P-VOL and S-VOL of a UR pair meet the prerequisites.

2. Display the detailed information about the UR pair on CCI.

   Verify whether the current differential data management method is the Shared memory (SM) difference management or the hierarchical difference management by a drive for both the P-VOL and S-VOL of the UR pair. The DM column displayed by the pairdisplay command shows whether the shared memory (S) difference management is applied or the hierarchical (D) difference management is applied.

   # pairdisplay -g oradb -fe -fcx
   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
   oradb dev1 L CL5-A-0 30 0 64568 301 P-VOL PAIR ASYNC 100 303 - 0 8 1 - - - -/- - S N
   oradb dev1 R CL5-A-0 30 2 64568 303 S-VOL PAIR ASYNC 100 301 - 0 1 1 - - - -/- - S N
   oradb dev2 L CL5-A-0 30 1 64568 302 P-VOL PAIR ASYNC 100 304 - 0 8 1 - - - -/- - S N
   oradb dev2 R CL1-A-0 30 3 64568 304 S-VOL PAIR ASYNC 100 302 - 0 1 1 - - - -/- - S N
   

   • If the SM difference management is applied, go to Step 3 to temporarily change to hierarchical difference management.
   • If the hierarchical difference management is applied, go to Step 4.
   • If using HDvM - SN, verify the advanced system settings No.5 and No.6 in the Edit Advanced System Settings window.
     • If both the advanced system settings No.5 and No. 6 are set to Disable, the SM difference management is applied. Go to Step 3.
     • If either or both the advanced system settings No.5 and No.6 are set to Enable, the hierarchical difference management is applied. Go to Step 4.

3. Change the differential data management method to the hierarchical difference management for both the P-VOL and S-VOL of the UR pair.

   1. Change system settings for hierarchical difference management.

      • If using CCI, set the system option mode (SOM) 1198 to ON and 1199 to OFF by using the raidcom modify system_opt command.

        Command example:

        raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode enable

        raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode disable

      • If using HDvM - SN, set the advanced system settings No. 5 to Enable and No.6 to Disable in the Edit Advanced System Settings window. For details, see the System Administrator Guide.

   2. Suspend the UR pair.

   3. Resynchronize the UR pair.

   4. When the pair status changes to PAIR after pair resynchronization, display the detailed information about the UR pair on CCI.

      Verify that the current differential data management method is the hierarchical difference management.

4. After you confirm that the hierarchical difference management is set as the differential data management method for both the P-VOL and S-VOL of the UR pair, suspend the UR pair.

5. Expand the S-VOL capacity in the UR pair.

   • If using CCI, add -request_id auto option to the raidcom extend ldev command to specify the asynchronous command processing.

     Command example

     The following command expands the capacity of LDEV#44:44 by 10 GB.

     raidcom extend ldev -ldev_id 0x4444 -capacity 10G –request_id auto -IH1

   • If using HDvM - SN, expand the capacity in the Expand V-VOLs window.

6. Verify that expanding the S-VOL capacity in the UR pair is finished.

   • If using CCI, raidcom get command_status command to verify that the raidcom extend ldev command is finished processing.

     Command example

     raidcom get command_status -IH1raidcom get ldev -ldev_id 0x4444 -fx -IH1

     Verify the expanded LDEV capacity using the raidcom get ldev command.

   • If using HDvM - SN, select Logical devices from the Storage Systems tree, and then display the LDEV tab. Verify that the capacity with the target LDEV number is correct.

7. Expand the P-VOL capacity in the UR pair in the same way as the S-VOL capacity.

   If the P-VOL capacity in the UR pair cannot be expanded, see Recovering from failure if one volume capacity in Universal Replicator pair cannot be expanded.

8. Verify that expanding the P-VOL capacity in the UR pair is complete in the same way as the S-VOL capacity.

9. Resynchronize the UR pair.

   If the resync operation in the UR pair cannot be performed, see Recovering from failure if one volume capacity in Universal Replicator pair cannot be expanded.

10. Verify that the pair statuses of both the P-VOL and S-VOL in the UR pair have changed to PAIR, and that the volume capacity is not being expanded.

    • If using CCI, check that the P column of the pairdisplay command displays N.

      # pairdisplay -g oradb -fe -fcx
      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
      oradb dev1 L CL5-A-0 30 0 64568 301 P-VOL PAIR ASYNC 100 303 - 0 8 1 - - - -/- - S N
      oradb dev1 R CL5-A-0 30 2 64568 303 S-VOL PAIR ASYNC 100 301 - 0 1 1 - - - -/- - S N
      oradb dev2 L CL5-A-0 30 1 64568 302 P-VOL PAIR ASYNC 100 304 - 0 8 1 - - - -/- - D N
      oradb dev2 R CL1-A-0 30 3 64568 304 S-VOL PAIR ASYNC 100 302 - 0 1 1 - - - -/- - D N
      
      

      The P column in the pairdisplay command displays the status that the volume capacity is being expanded. An N indicates that the volume capacity is not being expanded, an E indicates that the volume capacity is being expanded.

      The E status is displayed after expanding the P-VOL or S-VOL capacity in the UR pair, and before performing the pair resync operation. This status changes to N after the resync operation completes.

    • If using HDvM - SN, check if the Processing Status field in the Remote Replication window is blank.

      Expanding is displayed if the volume capacity is being expanded.

11. If you temporarily changed the differential data management method from SM difference to hierarchical difference (Step 2), restore to the SM difference management.

    1. To restore to the SM difference management:

       • If using CCI, set the system option mode (SOM) 1198 to OFF and 1199 to ON by using the raidcom modify system_opt command.

         Command example:

         raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode disable

         raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode enable

       • If using HDvM - SN, set the advanced system settings No. 5 to Disable and No.6 to Disable in the Edit Advanced System Settings window.

    2. Suspend the UR pair.

    3. Resynchronize the UR pair.

    4. Display the detailed information about the UR pair on CCI, and then verify that the current differential data management method is the SM difference management.

    5. If using CCI, and the settings of SOMs 1198 and 1199 have been changed, set SOM 1198 to OFF and 1199 to OFF by using the raidcom modify system_opt command.

       Command example:

       raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode disable

       raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode disable

Parent Topic

• Expansion of DP-VOL capacity while keeping pair status

You can expand the capacity of DP-VOLs used in a Universal Replicator pair and each software pair when a UR pair shares the same volumes with global-active device (GAD), TrueCopy (TC), ShadowImage (SI), and Thin Image (HTI).

When a UR pair shares the same volumes with other software, the order in which you expand the DP-VOL capacity consists of the following two expansion orders:

• Expansion order in a point to point configuration of the UR pair
• Expansion order in a point to point configuration of each software product

• When a remote replication (TC/UR/GAD) is included, first expand the S-VOL capacity on the end of the remote replication, and then expand the P-VOL capacity. For more information about the specific expansion procedure, see Expanding DP-VOL capacity when TrueCopy pair is used with Universal Replicator.
• When a remote replication (TC/UR/GAD) shares the same volumes with a local replication (SI/HTI), first expand the capacity of the S-VOL group in the remote replication. The S-VOL group consists of the S-VOL in the remote replication and all volumes in the local replication with which the S-VOL shares the same volume. After expanding the capacity of the S-VOL group in the remote replication, expand the capacity of the P-VOL group in the remote replication. The P-VOL group consists of the P-VOL in the remote replication and all volumes in the local replication with which the P-VOL shares the same volume.

  The expansion order in each group follows the expansion order in the local replication. For more information about the specific expansion procedures, see Expanding DP-VOL capacity when UR pair is used with ShadowImage and Expanding DP-VOL capacity when UR pair is used with Thin Image.

• In the local replication (SI/HTI), expand the capacity in the order from the highest layer to the lowest. The expansion order is not specified for the volumes in the same layer.

Parent Topic

• Expansion of DP-VOL capacity while keeping pair status

Child Topics

• Expanding DP-VOL capacity when TrueCopy pair is used with Universal Replicator
• Expanding DP-VOL capacity when UR pair is used with ShadowImage
• Expanding DP-VOL capacity when UR pair is used with Thin Image

1. Verify that each volume of the P-VOLs and the S-VOLs used in the UR pairs meet the prerequisites for each software product.

2. Display the detailed information about the first URpair and the second UR pair on CCI.

   Verify whether the current differential data management method is the SM difference management or the hierarchical difference management by a drive.
   • If the SM difference management is applied, proceed to step 3.
   • If the hierarchical difference management is applied, proceed to step 4.
   • If using HDvM - SN, verify the advanced system settings No.5 and No.6.
     • If both the advanced system settings No.5 and No. 6 are set to Disable, the SM difference management is applied. Go to Step 3.
     • If either or both the advanced system settings No.5 and No.6 are set to Enable, the hierarchical difference management is applied. Go to Step 4.

3. Change the differential data management method to the hierarchical difference management.

   1. Change system settings for hierarchical difference management.

      • If using CCI, set the system option mode (SOM) 1198 to ON and 1199 to OFF by using the raidcom modify system_opt command.

        Command example:

        raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode enable

        raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode disable

      • If using HDvM - SN, set the advanced system settings No. 5 to Enable and No.6 to Disable in the Edit Advanced System Settings window.

   2. Suspend the first UR pair and the second UR pair.

   3. Resynchronize the first UR pair and the second UR pair.

   4. Display the detailed information about first UR pair and the second UR pair on CCI, and then verify that the current differential data management method is the hierarchical difference management.

4. Suspend the first UR pair and the second UR pair.

5. Expand each volume capacity, and then verify that the expansion is complete in the expansion orders as shown in the following figures.

   • 3DC cascade configuration

     

   • 3DC multi-target configuration

     

   After expanding the first volume capacity, if you cannot perform the following operations , make sure to perform the recovery procedure described in Recovering from failure if one volume capacity in Universal Replicator pair cannot be expanded.

   • 3DC cascade configuration
     • Expanding the P-VOL capacity in the UR pair between the intermediate and secondary sites (the S-VOL capacity in the UR pair between the primary and intermediate sites)
     • Expanding the P-VOL capacity in the UR pair between the primary and intermediate sites
     • Resynchronizing each UR pair
   • 3DC multi-target configuration
     • Expanding the S-VOL capacity in the first UR pair
     • Expanding the P-VOL capacity in the first UR pair (the P-VOL capacity in the second UR pair)
     • Resynchronizing each UR pair

6. Resynchronizing each UR pair.

7. Verify that both the pair statuses of the P-VOL and S-VOL in of each UR pair have changed to PAIR.

   In addition, verify that each volume capacity in the UR pairs is not being expanded.

   The following table shows how the expansion process is displayed.

   Expansion status	CCI	HDvM - SN
   	P column in the pairdisplay command	Processing Status field in the Remote Replication window
   Not being expanded	N	Blank
   Being expanded	E*	Expanding*
   * This status has been displayed after expanding the P-VOL or S-VOL capacity in the UR pairs until the pair resync operation is performed. After the resync operation is complete, the status is migrated to the Not being expanded status.

8. In step 2, if the differential data management method is the SM difference management, restore to the SM difference management using the following procedure:

   1. To restore to the SM difference management:

      • If using CCI, set the system option mode (SOM) 1198 to OFF and 1199 to ON by using the raidcom modify system_opt command.

        Command example:

        raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode disable

        raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode enable

      • If using HDvM - SN, set the advanced system settings No. 5 to Disable and No.6 to Disable in the Edit Advanced System Settings window.

   2. Suspend the first UR pair and the second UR pair.

   3. Resynchronize the first UR pair and the second UR pair.

   4. Display the detailed information about first UR pair and the second UR pair on CCI, and then verify that the current differential data management method is the SM difference management.

   5. If using CCI, and the settings of SOMs 1198 and 1199 have been changed, set SOM 1198 to OFF and 1199 to OFF by using the raidcom modify system_opt command.

      Command example:

      raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode disable

      raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode disable

Parent Topic

• Expansion of DP-VOL capacity while keeping pair status

Procedure

1. Verify that each volume of the P-VOLs and the S-VOLs used in the UR pairs meet the prerequisites for each software product.

2. Display the detailed information about the first URpair and the second UR pair on CCI.

   Verify whether the current differential data management method is the SM difference management or the hierarchical difference management by a drive.
   • If the SM difference management is applied, proceed to step 3.
   • If the hierarchical difference management is applied, proceed to step 4.
   • If using HDvM - SN, verify the advanced system settings No.5 and No.6.
     • If both the advanced system settings No.5 and No. 6 are set to Disable, the SM difference management is applied. Go to Step 3.
     • If either or both the advanced system settings No.5 and No.6 are set to Enable, the hierarchical difference management is applied. Go to Step 4.

3. Change the differential data management method to the hierarchical difference management.

   1. Change system settings for hierarchical difference management.

      • If using CCI, set the system option mode (SOM) 1198 to ON and 1199 to OFF by using the raidcom modify system_opt command.

        Command example:

        raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode enable

        raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode disable

      • If using HDvM - SN, set the advanced system settings No. 5 to Enable and No.6 to Disable in the Edit Advanced System Settings window.

   2. Suspend the first UR pair and the second UR pair.

   3. Stop the host operations at the primary site.

   4. Suspend the first UR pair (swap suspend).

   5. Resume the host operations at the secondary site.

   6. Perform the delta resync operation.

   7. Resynchronize the first UR pair (swap resync).

   8. Stop the host operations at the secondary site.

   9. Suspend the first UR pair (swap suspend).

   10. Resume the host operations at the primary site.

   11. Perform the delta resync operation.

   12. Resynchronize the first UR pair (swap resync).

   13. Display the detailed information about first UR pair, the second UR pair, and the UR delta resync pair on CCI, and then verify that the current differential data management method is the hierarchical difference management.

4. Suspend the first UR pair and the second UR pair.

5. Expand each volume capacity, and then verify that the expansion is complete in the expansion order shown in the following figure.

   After expanding the first volume capacity, if you cannot expand the S-VOL capacity in the first UR pair, you cannot expand the P-VOL capacity in the first UR pair (the P-VOL capacity in the second UR pair), or resynchronizing the first UR pair and second UR pair, make sure to perform the recovery procedure described in Recovering from failure if one volume capacity in Universal Replicator pair cannot be expanded. .

6. Resynchronizing the first UR pair and the second UR pair.

7. Verify that both the pair statuses of the P-VOL and S-VOL of each UR pair have changed to PAIR.

   In addition, verify that each volume capacity in the UR pairs is not being expanded.

   The following table shows how the expansion process is displayed.

   Expansion status	CCI	HDvM - SN
   	P column in the pairdisplay command	Processing Status field in the Remote Replication window
   Not being expanded	N	Blank
   Being expanded	E*	Expanding*
   * This status has been displayed after expanding the P-VOL or S-VOL capacity in the UR pairs until the pair resync operation is performed. After the resync operation is complete, the status is migrated to the Not being expanded status. In the UR delta resync pair, the Being expanded status will not be displayed on CCI or HDvM - SN because the expansion in the UR delta resync pair is complete concurrently with the first UR pair and the second UR pair.

8. In step 2, if the differential data management method is the SM difference management, restore to the SM difference management using the following procedure:

   1. To restore to the SM difference management:

      • If using CCI, set the system option mode (SOM) 1198 to OFF and 1199 to ON by using the raidcom modify system_opt command.

        Command example:

        raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode disable

        raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode enable

      • If using HDvM - SN, set the advanced system settings No. 5 to Disable and No.6 to Disable in the Edit Advanced System Settings window.

   2. Suspend the first UR pair (swap suspend).

   3. Resume the host operations at the secondary site.

   4. Perform the delta resync operation.

   5. Resynchronize the first UR pair (swap resync).

   6. Stop the host operations at the secondary site.

   7. Suspend the first UR pair (swap suspend).

   8. Resume the host operations at the primary site.

   9. Perform the delta resync operation.

   10. Resynchronize the first UR pair (swap resync).

   11. Display the detailed information about first UR pair and the second UR pair on CCI, and then verify that the current differential data management method is the SM difference management.

   12. If using CCI, and the settings of SOMs 1198 and 1199 have been changed, set SOM 1198 to OFF and 1199 to OFF by using the raidcom modify system_opt command.

       Command example:

       raidcom modify system_opt -system_option_mode system -mode_id 1198 -mode disable

       raidcom modify system_opt -system_option_mode system -mode_id 1199 -mode disable

Parent Topic

• Expansion of DP-VOL capacity while keeping pair status

1. Expand the volume capacity in the group that includes the S-VOL in the remote replication in the order shown as 1, 2, 3 in the preceding figure.

2. Expand the volume capacity in the group that includes the P-VOL in the remote replication in the order shown as 4, 5, 6 in the preceding figure.

   Expand the volume capacity in the order from the highest layer to the lowest because the expansion order in the local replication is prioritized. Expand the P-VOL capacity in the local replication first, and then the S-VOL capacity in the local replication that shares the same volume with the P-VOL in the remote replication.

   For example, when an S-VOL in SI shares the same volume with a P-VOL in TC or UR as shown in the preceding figure, expand the volume capacity in the following order:

   1. P-VOL in the SI pair shown as 4 in the figure.
   2. S-VOL in the SI pair (P-VOL in the TC or UR pair) shown as 5 in the figure.
   3. Volumes in the same layer as the S-VOL in the SI pair.
   4. Volumes in the lower layer than the S-VOL in the SI pair.

Parent Topic

• Expansion of DP-VOL capacity while keeping pair status

When a 3DC cascade, 3DC multi-target, or 3DC delta resync configuration using remote replications is created, first expand the S-VOL capacity on the end of the remote replication, and then expand the P-VOL capacity as shown in the following figures.

• 3DC cascade configuration

  

• 3DC multi-target configuration

  

• 3DC delta resyc configuration

  

Parent Topic

• Expansion of DP-VOL capacity while keeping pair status

When the remote replications in a 3DC configuration share the same volumes with the local replications (SI/HTI), expand the volume capacity in each following group in the order as shown in the figure.

The expansion order in each group follows the expansion order in the local replication. In a 3DC multi-target or 3DC delta resync configuration, expand the volume capacity in the same way.

Procedure

1. Expand the S-VOL group that consists of the S-VOL in the remote replication and all volumes in the local replication with which the S-VOL shares the same volume.

2. Expand the P-VOL group that consists of the P-VOL in the remote replication and all volumes in the local replication with which the P-VOL shares the same volume.

Parent Topic

• Expansion of DP-VOL capacity while keeping pair status

Procedure

1. Verify that all of the prerequisites are met.

   If the prerequisites are not met, proceed to step 4.

   1. Verify that both the P-VOL and S-VOL in a UR pair meet the prerequisites for expanding the DP-VOL capacity.

      See the prerequisites for Expanding DP-VOL capacity used in Universal Replicator pair .

   2. Verify that all of the volumes meet the prerequisites for expanding the capacity in each of the software products.

      When a UR pair is used with GAD, TC, SI, or HTI, or when a 3DC configuration is created with three UR sites, the capacity of the P-VOLs and the S-VOLs used in all of the used software products must be expanded.

2. When the prerequisites for expanding the DP-VOL capacity are met, retry the expansion and make sure that the capacity of the P-VOL and S-VOL in the UR pair is the same.

   1. If there is not enough free space, increase the free space, and then expand the DP-VOL capacity.

   2. If a UR pair is used with GAD, TC, SI, or HTI, or when a 3DC configuration is created with three UR sites, retry the expansion and make sure that the capacity of the P-VOL and S-VOL in each of the software products is the same.

   • If you can expand the capacity, go to Step 3.
   • If you cannot expand the capacity, go to Step 4.

3. Perform the following operation depending on the configuration:

   • If only UR pairs are used, resynchronize each UR pair.
   • If a 3DC cascade configuration or 3DC multi-target configuration with a UR pair and a TC pair is used, resynchronize the UR pair and the TC pair.
   • If a 3DC multi-target delta resync configuration with a UR pair and a TC pair is used, resynchronize the UR pair and the TC pair.
   • If a 3DC configuration with three UR sites is used, resynchronize the UR pairs.
   • If a 3DCconfiguration with a UR pair and a GAD pair is used, resynchronize the UR pair and the GAD pair.
   As a result, the recovery procedure from the failure is complete.

4. Delete the UR pair, expand the volume capacity in the SMPL status, and then re-create the UR pair.

   • If you want to restore to the conditions before the expansion due to a capacity input error and others, delete the UR pair, and then recreate the LDEV with the correct capacity. After that, recreate the UR pair.
   • If a UR pair is used with GAD or TC, or when a 3DC configuration is created with three UR sites, delete all pairs, expand the volume capacity in the SMPL status, and then restore the configurations by following the procedure for creating the configurations.

     If you want to restore to the conditions before the expansion due to a capacity input error and others, delete all pairs, and then recreate the LDEV with the correct capacity. After that, restore the configurations by following the procedure for creating the configurations.

   • If a UR pair is used with SI or HTI, and the capacity of the P-VOL and S-VOL in a SI pair or HTI pair is not the same, you can only delete the SI pair or HTI pair. You can read the S-VOL data in the SI pair or HTI pair before the expansion. If you want to use the data before the expansion, delete all pairs after the data reading is complete. Expand the volume capacity in the SMPL status, and then restore the configurations by following the procedure for creating the configurations.

     If you want to restore to the conditions before the expansion due to a capacity input error and others, delete all pairs, and then recreate the LDEV with the correct capacity. After that, restore the configurations.

Parent Topic

• Expansion of DP-VOL capacity while keeping pair status

Procedure

1. Start to recover from the failure using one of the UR disaster recovery operations.

   Depending on the operations during the recovery procedure, one or more of the following actions are required:
   • If the operation is resynchronizing a UR pair

     The resynch operation cannot be performed because the capacity of the P-VOL and S-VOL in the UR pair is not the same.

     Complete Steps 2 and 3 before the UR pair resynch operation.

   • If the operation is,
     • Deleting a UR pair
     • Recovering from a volume failure
     • Re-creating a UR pair

     The UR pair cannot be created because the capacity of the target P-VOL and S-VOL is not the same when re-creating the UR pair.

     Complete Steps 2 and 3 immediatelybefore the UR pair resynch operation.

   • If the operation is,
     • Deleting a UR pair
     • Deleting a volume
     • Creating a volume
     • Re-creating a UR pair

     The UR pair cannot be created because the capacity of the target P-VOL and S-VOL is not the same when re-creating the UR pair. Make sure that the capacity of the P-VOL and S-VOL is the same when creating the volumes.

     Skip Steps 2 and 3.

2. Expand the capacity of volumes whose capacity is not expanded, and then make sure that the capacity of the P-VOL and S-VOL in the UR pair is the same.

   When a UR pair is used with other software, the capacity of the P-VOLs and S-VOLs in all of the used software products must be expanded. For more information about the order in which the volume capacity is expanded, see Expansion order policy when UR pair shares the same volumes with other software.

3. Restart the resync operation and the creation of the GAD pair by following one of the UR disaster recovery operations.

Parent Topic

• Expansion of DP-VOL capacity while keeping pair status

Procedure

1. Using the alternate path software, stop I/O from servers to the primary storage system.

   Direct server I/O to the GAD secondary storage system.

2. On the GAD secondary storage system, suspend the GAD pairs by specifying the S-VOL (swap suspension).

   Command example: pairsplit -g oraHA -RS -IH1

3. Confirm that the pair types and the pair statuses are changed as shown in the following table.

   Before the GAD pair suspension			After the GAD pair suspension
   Pair type	Pair status		Pair type	Pair status
   	P-VOL	S-VOL		P-VOL	S-VOL
   GAD pair	PAIR (Mirror(RL))	PAIR (Mirror(RL))	GAD pair	PSUS (Block)	SSWS (Local)
   UR pair	PAIR	PAIR	UR delta resync pair	PSUE1	SSUS2
   UR delta resync pair	PSUS2	SSUS2	UR pair	PAIR	PAIR
   Notes: Device Manager - Storage Navigator displays HOLDING. Device Manager - Storage Navigator displays HOLD.

4. Power off the primary storage system.

Parent Topic

• Planned outage of storage systems in a GAD 3DC delta resync environment (VSP 5000 series)

Procedure

1. Power on the primary storage system.

2. Confirm that the storage systems do not have any blocked parts.

   If any parts are blocked, recover them.

3. Check for SIMs about path blockage, and delete the SIMs.

4. On the GAD secondary storage system, resynchronize the GAD pair by specifying the S-VOL (swap resync).

   Command example: pairresync -g oraHA -swaps -IH1 A volume on the primary storage system changes to an S-VOL, and a volume on the secondary storage system changes to a P-VOL.

5. Confirm that the pair statuses are changed as shown in the following table.

   Pair type	Before the GAD pair resync		After the GAD pair resync
   	P-VOL	S-VOL	P-VOL	S-VOL
   GAD pair	PSUS (Block)	SSWS (Local)	PAIR (Mirror(RL))	PAIR (Mirror(RL))
   UR delta resync pair	PSUE1	SSUS2	PSUE1	SSUS2
   UR pair	PAIR	PAIR	PAIR	PAIR
   Notes: Device Manager - Storage Navigator displays HOLDING. Device Manager - Storage Navigator displays HOLD.

6. Keep updating I/O to the P-VOL or GAD S-VOL for two minutes.

   The information on the system configuration 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. The mirror status of the journal is displayed as PJNS. Confirm that no failure SIMs are displayed.

Next steps

Parent Topic

• Planned outage of storage systems in a GAD 3DC delta resync environment (VSP 5000 series)

Procedure

1. Using the alternate path software, stop I/O from servers to the GAD secondary storage system.

   Direct server I/O to the primary storage system.

2. On the primary storage system, resynchronize the GAD pair by specifying the P-VOL.

   Command example: pairsplit -g oraHA -IH0

3. Confirm that the pair statuses are changed as shown in the following table.

   Pair type	Before the GAD pair suspension		After the GAD pair suspension
   	P-VOL	S-VOL	P-VOL	S-VOL
   GAD pair	PAIR (Mirror(RL))	PAIR (Mirror(RL))	PSUS (Local)	PSUS (Block)
   UR pair	PAIR	PAIR	PAIR	PAIR
   UR delta resync pair	PSUS1	SSUS1	PSUE2	SSUS1
   Notes: Device Manager - Storage Navigator displays HOLD. Device Manager - Storage Navigator displays HOLDING.

4. Power off the GAD secondary storage system.

Parent Topic

• Planned outage of storage systems in a GAD 3DC delta resync environment (VSP 5000 series)

Procedure

1. Power on the GAD secondary storage system.

2. Confirm that the primary and secondary storage systems and the external storage system for the quorum disk do not have any blocked parts.

   If any parts are blocked, recover them.

3. Check for SIMs about path blockage, and delete the SIMs.

4. On the primary storage system, resynchronize the GAD pairs by specifying the P-VOL.

   Command example: pairresync -g oraHA -IH0

5. Confirm that the pair statuses are changed as shown in the following table.

   Pair type	Before the GAD pair resync		After the GAD pair resync
   	P-VOL	S-VOL	P-VOL	S-VOL
   GAD pair	PSUS (Local)	PSUS (Block)	PAIR (Mirror(RL))	PAIR (Mirror(RL))
   UR pair	PAIR	PAIR	PAIR	PAIR
   UR delta resync pair	PSUE1	SSUS2	PSUE1	SSUS2
   Notes: Device Manager - Storage Navigator displays HOLDING. Device Manager - Storage Navigator displays HOLD.

6. Keep updating I/O to P-VOL or GAD S-VOL for two minutes.

   The information on the system configuration 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. The mirror status of the journal is displayed as PJNS. Confirm that no failure SIMs are displayed.

Parent Topic

• Planned outage of storage systems in a GAD 3DC delta resync environment (VSP 5000 series)

Procedure

1. On the primary storage system, suspend the UR pairs by specifying the P-VOL.

   Command example: pairsplit -g oraREMOTE -IH0

2. Confirm that the pair statuses are changed as shown in the following table.

   Pair type	Before the GAD pair suspension		After the GAD pair suspension
   	P-VOL	S-VOL	P-VOL	S-VOL
   GAD pair	PAIR (Mirror(RL))	PAIR (Mirror(RL))	PAIR (Mirror(RL))	PAIR (Mirror(RL))
   UR pair	PAIR	PAIR	PSUS	PSUS
   UR delta resync pair	PSUS1	SSUS1	PSUE2	SSUS1
   Notes: Device Manager - Storage Navigator displays HOLD. Device Manager - Storage Navigator displays HOLDING.

3. Power off the UR secondary storage system.

Parent Topic

• Planned outage of storage systems in a GAD 3DC delta resync environment (VSP 5000 series)

Procedure

1. Power on the UR secondary storage system.

2. Confirm that the primary and secondary storage systems and the external storage system for the quorum disk do not have any blocked parts.

   If any parts are blocked, recover them.

3. Check for SIMs about path blockage, and delete the SIMs.

4. On the primary storage system, resynchronize the UR pairs by specifying the P-VOL.

   Command example: pairresync -g oraREMOTE -IH0

5. Confirm that the pair statuses are changed as shown in the following table.

   Pair type	Before the GAD pair resync		After the GAD pair resync
   	P-VOL	S-VOL	P-VOL	S-VOL
   GAD pair	PAIR (Mirror(RL))	PAIR (Mirror(RL))	PAIR (Mirror(RL))	PAIR (Mirror(RL))
   UR pair	PSUS	PSUS	PAIR	PAIR
   UR delta resync pair	PSUE1	SSUS2	PSUE1	SSUS2
   Notes: Device Manager - Storage Navigator displays HOLDING. Device Manager - Storage Navigator displays HOLD.

6. Keep updating I/O to P-VOL or GAD S-VOL for two minutes.

   The information on the system configuration 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. The mirror status of the journal is displayed as PJNS. Confirm that no failure SIMs are displayed.

Parent Topic

• Planned outage of storage systems in a GAD 3DC delta resync environment (VSP 5000 series)

Procedure

1. Using the alternate path software, stop I/O from servers to the GAD secondary storage system.

   Direct server I/O to the primary storage system.

2. On the primary storage system, resynchronize the GAD pair by specifying the P-VOL.

   Command example: pairsplit -g oraHA -IH0

3. Confirm that the pair statuses are changed as shown in the following table.

   Pair type	Before the GAD pair suspension		After the GAD pair suspension
   	P-VOL	S-VOL	P-VOL	S-VOL
   GAD pair	PAIR (Mirror(RL))	PAIR (Mirror(RL))	PSUS (Local)	PSUS (Block)
   UR pair	PAIR	PAIR	PAIR	PAIR
   UR delta resync pair	PSUS1	SSUS1	PSUE2	SSUS1
   Notes: Device Manager - Storage Navigator displays HOLD. Device Manager - Storage Navigator displays HOLDING.

4. On the primary and GAD secondary storage systems, disconnect the quorum disks.

   Command example: raidcom disconnect external_grp -ldev_id 0x9999 -IH0
   NoteWhen you disconnect a quorum disk, SIM (def0zz) (quorum disk blockade) might be issued (zz: quorum disk ID). If this SIM is issued, delete the SIM after powering on the storage system and reconnecting the quorum disk.

5. Power off the external storage system.

Parent Topic

• Planned outage of storage systems in a GAD 3DC delta resync environment (VSP 5000 series)

Procedure

1. Power on the external storage system.

2. Confirm that the primary and secondary storage systems and the external storage system for the quorum disk do not have any blocked parts.

   If any parts are blocked, recover them.

3. Check for SIMs about path blockage, and delete the SIMs.

4. On the primary and GAD secondary storage systems, establish the connections to the quorum disks.

   Command example: raidcom check_ext_storage external_grp -ldev_id 0x9999 -IH0

5. On the primary and GAD secondary storage systems, confirm that the connections to the quorum disks have been established.

   Command example: raidcom get external_grp -external_grp_id 1-1 -IH0

6. Confirm that the external volumes of the primary and GAD secondary storage systems are recognized as quorum disks.

   Command example: raidcom get ldev -ldev_id 0x9999 -IH0

7. On the primary and GAD secondary storage systems, check for SIMs about quorum disk blockade, and delete the SIMs.

8. Wait for more than 5 minutes after completing step 4, and then resynchronize the GAD pairs on the primary storage system by specifying the P-VOL.

   Command example: pairresync -g oraHA -IH0

9. Confirm that the pair statuses are changed as shown in the following table.

   Pair type	Before the GAD pair resync		After the GAD pair resync
   	P-VOL	S-VOL	P-VOL	S-VOL
   GAD pair	PSUS (Local)	PSUS (Block)	PAIR (Mirror(RL))	PAIR (Mirror(RL))
   UR pair	PAIR	PAIR	PAIR	PAIR
   UR delta resync pair	PSUE1	SSUS2	PSUE1	SSUS2
   Notes: Device Manager - Storage Navigator displays HOLDING. Device Manager - Storage Navigator displays HOLD.

10. Keep updating I/O to P-VOL or GAD S-VOL for two minutes.

    The information on the system configuration 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. The mirror status of the journal is displayed as PJNS. Confirm that no failure SIMs are displayed.

Parent Topic

• Planned outage of storage systems in a GAD 3DC delta resync environment (VSP 5000 series)

Procedure

1. Using the alternate path software, stop I/O from servers to the primary storage system. Direct server I/O to the GAD secondary storage system.

2. On the GAD secondary storage system, suspend the GAD pairs by specifying the S-VOL (swap suspension).

   Command example: pairsplit -g oraHA -RS -IH1

3. Confirm that the pair types and the pair statuses are changed as shown in the following table.

   Before the GAD pair suspension			After the GAD pair suspension
   Pair type	Pair status		Pair type	Pair status
   	P-VOL	S-VOL		P-VOL	S-VOL
   GAD pair	PAIR (Mirror(RL))	PAIR (Mirror(RL))	GAD pair	PSUS (Block)	SSWS (Local)
   UR pair	PAIR	PAIR	UR delta resync pair	PSUE1	SSUS2
   UR delta resync pair	PSUS2	SSUS2	UR pair	PAIR	PAIR
   Notes: Device Manager - Storage Navigator displays HOLDING. Device Manager - Storage Navigator displays HOLD.

4. On the primary and GAD secondary storage systems, disconnect the quorum disks.

   Command example: raidcom disconnect external_grp -ldev_id 0x8888 -IH1
   NoteWhen you disconnect a quorum disk, SIM (def0zz) (quorum disk blockade) might be issued (zz: quorum disk ID). If this SIM is issued, delete the SIM after powering on the storage system and reconnecting the quorum disk.

5. Power off the external storage system.

Parent Topic

• Planned outage of storage systems in a GAD 3DC delta resync environment (VSP 5000 series)

Procedure

1. Power on the external storage system.

2. Confirm that the primary and secondary storage systems and the external storage system for the quorum disk do not have any blocked parts.

   If any parts are blocked, recover them.

3. Check for SIMs about path blockage, and delete the SIMs.

4. On the primary and GAD secondary storage systems, establish the connections to the quorum disks.

   Command example: raidcom check_ext_storage external_grp -ldev_id 0x8888 -IH1

5. On the primary and GAD secondary storage systems, confirm that the connections to the quorum disks have been established.

   Command example: raidcom get external_grp -external_grp_id 1-2 -IH1

6. Confirm that the external volumes of the primary and GAD secondary storage systems are recognized as quorum disks.

   Command example: raidcom get ldev -ldev_id 0x8888 -IH1

7. On the primary and GAD secondary storage systems, check for SIMs about quorum disk blockade, and delete the SIMs.

8. Wait for more than 5 minutes after completing step 4, and then resynchronize the GAD pairs on the GAD secondary storage system by specifying the S-VOL (swap resync).

   Command example: pairresync -g oraHA -swaps -IH1 A volume on the primary storage system changes to an S-VOL, and a volume on the secondary storage system changes to a P-VOL.

9. Confirm that the pair statuses are changed as shown in the following table.

   Pair type	Before the GAD pair resync		After the GAD pair resync
   	P-VOL	S-VOL	P-VOL	S-VOL
   GAD pair	PSUS (Block)	SSWS (Local)	PAIR (Mirror(RL))	PAIR (Mirror(RL))
   UR delta resync pair	PSUE1	SSUS2	PSUE1	SSUS2
   UR pair	PAIR	PAIR	PAIR	PAIR
   Notes: Device Manager - Storage Navigator displays HOLDING. Device Manager - Storage Navigator displays HOLD.

10. Keep updating I/O to P-VOL or GAD S-VOL for two minutes.

    The information on the system configuration 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. The mirror status of the journal is displayed as PJNS. Confirm that no failure SIMs are displayed.

Next steps

Parent Topic

• Planned outage of storage systems in a GAD 3DC delta resync environment (VSP 5000 series)