Skip to main content

We've Moved!

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

Maintaining the UR system

You perform some maintenance tasks in response to conditions discovered during system monitoring, such as pool-full conditions that cause pairs to become suspended. You can also change certain settings as needed to meet changing operational requirements.

Pair maintenance

You must have Storage Administrator (Remote Copy) role to perform Universal Replicator pair maintenance operations.

Changing the maximum initial copy activities option

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.

Note
  • Performance of the primary storage system depends on this setting and the amount of I/O activity. You can limit the impact of initial copy operations on system performance by using the default setting.
  • When you change the maximum initial copy activities setting, the new setting applies to pairs created or resynchronized after the change, not existing pairs.

Changing the pair options

You can change the following pair options:

  • Cache-fast-write (CFW)
  • Error level

Before you begin

  • You can change the pair options only for pairs in PAIR, PSUS, PSUE, HOLD, HOLDING, or HLDE status.

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.

Forcibly deleting pairs

You need to forcibly delete a pair for the following reasons:

  • A currently unpaired volume that was previously in a pair is unusable because previous pair information is still in the volume.
  • The pair cannot be connected to the secondary storage system due to a communication error. In this case, you need to delete the pair forcibly in both the primary storage system and the secondary storage system.
CautionThe following data is discarded:
  • Data which is not sent to the secondary storage system when a pair in the primary storage system is deleted forcibly
  • Data which is not restored when a pair is deleted forcibly in the secondary storage system

In addition, if a pair is deleted forcibly when a journal contains a pair in the PAIR/COPY status, host I/Os to the pair might time out.

Before you begin

  • The volume must be unpaired.

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.

Releasing the differential data managed in a pool

When a UR pair contains a DP-VOL that is larger than 4,194,304 MB (8,589,934,592 blocks), the differential data is managed by the pool to which the pair is related. If differential data management fails due to insufficient pool capacity, you need to release the differential data (pages) managed in the pool. You also need to release pages when you downgrade to a microcode version that does not support UR pairs with volumes larger than 4,194,304 MB.

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.

Restoring a pair by adding a reserve journal volume

Use the following procedure to restore a UR pair that was split due to disk failure of the pool and pool volume to which the journal volume belongs or to replace the journal volume if PIN data occurs in the journal volume. When you use a reserve journal volume, you do not need to delete the UR pair.

You cannot reserve a journal volume using BCM.

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.

Restoring a pair without adding a reserve journal volume

Use the following procedure to restore a UR pair that was split by disk failure of the pool and pool volume to which the journal volume belongs. If you do not recover the volume and do not use a reserve journal volume, the UR pair must be deleted.

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.

Journal and mirror maintenance

This topic describes and provides instructions for the following journal and mirror maintenance tasks:

Changing options used by journals

Most Universal Replicator pair operations are performed on multiple pairs, which share a journal group. You can change options that affect the pairs in journals.

You can control the following aspects of pair operations:

  • Inflow Control: Allows you to restrict the inflow of data to allow other journals with higher priority data unrestricted inflow when the data transfer path accessing two journals is set.
  • Data Overflow Watch: Establishes a timeout period.

    In a 3DC multi-target configuration in which three UR sites are combined, if the status of the two mirrors in the primary site is both Active and the free space in the journal data area or metadata area is less than a certain amount, one of the mirrors in the journal will be suspended by error, regardless of the value in Data Overflow Watch.

  • Cache Mode: Allows you to use journal data in the cache on the secondary storage system.

You can use the Inflow Control and Data Overflow Watch journal options on the primary storage system only. You can use other journal options on both the primary and secondary storage systems.

To perform this task in CCI, use the raidcom modify journal command.

Before you begin

  • To change journal options, one of the following conditions must be satisfied:
    • The attribute of the journal is Initial.
    • The status of the journal in the mirror is one of the following:
      • Initial
      • Stopped
      • Hold(Failure)

      When one journal uses multiple mirrors, whether you can select Change Journal Option depends on the status of the journal whose mirror is not in Hold(Failure) status. For example, if mirrors in the journal are in the Hold(Failure) and Active status, you cannot change the journal option. If mirrors in the journal are in the Hold(Failure) and Stopped status, you can change the journal option.

  • When changing options for multiple journals, you can leave some options unchanged by entering or selecting no value. If you specify a value, it is applied to the selected journals.

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.

Changing options used by mirrors

Most pair operations are performed on multiple pairs. This is done using a journal or mirrors. You can change the following options that affect the pairs in a mirror:

  • Path Watch Time: the interval from the time when a physical path failure, such as disconnection of a path, occurs to the time when the mirror is suspended. This option becomes valid when both advanced system settings No. 16 and No. 15 are set to OFF.
  • Path Watch Time Transfer: forwards the master journal’s Path Watch Time value to the restore journal.
  • Copy Pace: the pace at which data is copied.
  • Transfer Speed: the speed for data transfer.
  • Delta Resync Failure: the processing that takes place in the event of a failure.

To perform this task in CCI, use the raidcom modify journal command.

Before you begin

  • Mirror options can be changed on both primary and secondary storage systems.
  • To change mirror options, the status of the mirror must be one of the following:
    • Initial
    • Active
    • Stopped
    • Hold
    • Holding
    • Hold(Failure)
  • The Transfer Speed option can be changed if the mirror’s status is Active, Hold, or Holding. When the status is Holding, the option can only be changed from the primary storage system.
  • When changing options for multiple mirrors, a changed value is applied to all the mirrors. On the other hand, leave the options unchanged that you do not want to change.

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.

Adding an additional journal volume to an existing journal

You can add one additional journal volume to a journal. The additional volume is not used unless needed for maintenance or to replace the first journal volume. In the event of pair failure, the additional reserve journal volume allows you to reduce the time to recover a blocked journal volume.

Before you begin

  • Review the following:
  • The journal’s mirror status must be Initial, Active, Stopped, Hold, Holding, or Hold(Failure).
  • The journal cannot be in use.
  • Pair operations involving the journal cannot be in progress.
  • Cache Residency Manager settings cannot be defined for the volumes.

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.

Replacing a journal volume with a reserve journal volume

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

When you register two journal volumes in a journal, the second journal volume becomes the reserve journal volume, which is not used for normal operations. For instructions on using CCI to replace a journal volume with a reserve journal volume, see Replacing a journal volume with a reserve journal volume using CCI.

Before you begin

  • Required role: Storage Administrator (Remote Copy)
  • An unallocated journal volume that will be the reserve journal volume must be available.
NoteIf an unallocated journal volume is not available to become the reserve journal volume and the journal volume is blocked, you must delete the journal, restore the blocked journal volume, register the journal volume to the journal again, and then re-create the suspended UR pairs. 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.

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.

Replacing a journal volume with a reserve journal volume using CCI

Before you begin

  • Required role: Storage Administrator (Remote Copy)
  • An unallocated journal volume that will be the reserve journal volume must be available.
  • Specify the CCI instance number by using the –I parameter as needed.

Procedure

  1. Add a reserve journal volume to the journal.

    raidcom add journal -journal_id <journal ID#> -ldev_id <ldev#>
    • <journal ID#>: Specify the journal ID to which the replacement target journal volume is registered.
    • <ldev#>: Specify the LDEV number of the unallocated journal volume that will be the reserve journal volume.
  2. Check the LDEV number of the journal volume that is currently being used.

    raidcom get journal
    • The LDEV number displayed in the LDEV# column of the command output is the LDEV number that is currently being used.
  3. Delete the journal volume to be replaced.

    raidcom delete journal -journal_id <journal ID#> -ldev_id <ldev#>
    • <journal ID#>: Specify the journal ID to which the replacement target journal volume is registered.
    • <ldev#>: Specify the journal volume LDEV number checked in step 2.
  4. Resynchronize the journal.

    pairresync -g <group>
    • <group>: Specify the data volume group name that is using the journal. The group name to be specified here is the group name defined in the CCI configuration definition file.
    • Specify the -IH parameter as needed.

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

You use this procedure when you want to replace a journal volume of a UR pair for delta resync with GAD on the GAD secondary storage system without deleting the UR delta resync pair.

Note
  • If a reserve journal volume is not used, you must delete a UR delta resync pair and a journal volume.
  • If you want to replace a journal volume of a UR delta resync pair on the UR secondary storge system, you must delete the UR pair and the journal volume.

Procedure

  1. Verify that the status of mirrors in the journal is Hold or Holding.

    If the mirror status is Hold(Failure), you can skip the following steps and perform the procedure described in Replacing a journal volume with a reserve journal volume.
  2. Suspend a GAD pair (swap suspend).

    1. Verify that the UR delta resync pair has changed to a normal UR pair, and that the pair status has changed to PAIR or PSUE.

    2. If the status of the UR delta resync pair is Holding before swap suspend, the pair status might change to PSUE after swap suspend.

    3. All data on the P-VOL is copied to the S-VOL by resynchronizing the UR pair in the PSUE status.

  3. Resynchronize the GAD pair (swap resync).

  4. Split the UR pair and verify that the mirror status has changed to Stop.

    If the UR pair status is already PSUE, skip this step.
  5. Add a reserve journal volume.

    For details, see Adding a reserve journal volume.
  6. Verify that the volume you added is a reserve journal volume.

    If you are using Device Manager - Storage Navigator, use the Journal Volumes window (Type: Reserve Journal). If you are using CCI, use the raidcom get journal command (Num: 2).
  7. Delete the journal volume that you want to replace.

  8. Resynchronize the UR pair and verify that the UR pair status has changed to PAIR.

  9. Continue issuing I/Os from the server to the P-VOL or the S-VOL of the GAD pair for about two minutes.

  10. Suspend the GAD pair (swap suspend).

    The UR pair changes to a UR delta resync pair.
  11. Resynchronize the GAD pair (swap resync).

Adding a reserve journal volume

To perform this task in CCI, use the raidcom add journal command.

Before you begin

An unallocated journal volume that will be the reserve journal volume must be available.

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.

Deleting journal volumes from a journal

To perform this task in CCI, use the raidcom delete journal command.

Before you begin

  • A journal volume can only be deleted when one or more of the following conditions exists:
    • If the journal volume to be deleted is a reserve journal volume.
    • If the pair belonging to the mirror in the journal is suspended and a reserve journal volume exists.
    • If the pair belonging to the mirror in the journal is deleted.
    • If the state of every mirror in the journal is Initial, Stopped, or Hold(Failure), and a reserve journal volume exists. If one journal uses more than one mirror, you can delete a journal volume only under the conditions specified in the following table.
      Conditions for deleting a journal volume (when one journal uses two types of mirror IDs)

      Status of journal

      Other conditions

      Mirror ID 1

      Mirror ID 2

      Stopped

      Stopped

      -

      Stopped

      Hold(Failure)*

      When a 3DC configuration of UR and TC or GAD is used.

      When a 3DC configuration in which three UR sites are combined.

      * For VSP E series, if the status of the journal for the UR delta resync pair is not Hold(Failure), delete the UR delta resync pair, and then confirm that the status of the journal becomes Initial. Then, delete the journal volume.
  • If all journal volumes in a journal are deleted (the journal is empty), all journal option data is initialized. To reset the journal’s options, see Changing options used by journals .

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.

Deleting journals

Journals can be deleted from either system.

To perform this task in CCI, use the raidcom delete journal command.

Before you begin

  • Journals can be deleted from the primary or secondary storage system.
  • All mirrors in the journal must be Initial status.
  • Master and restore journals cannot be deleted.
  • Removing a journal volume from a journal that is registered results in the journal volume's LDEVs becoming blockaded. You can release the blockade by formatting the LDEVs.

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.

Remote path maintenance

This topic describes and provides instructions for the following remote path maintenance tasks:

Modifying the data-transfer time threshold

You can modify the threshold for data transfer to complete. If the threshold value is reached, the transfer is flagged as failing by the system.

To perform this task in CCI, use the raidcom modify rcu -rcu_option command.

Before you begin

  • This operation can be performed from the primary or secondary storage system.
  • The setting is made in the RIO MIH field on the DKC Options dialog box (RIO MIH--remote I/O missing interrupt handler). RIO MIH Time is the waiting time from when copy starts until when it ends. This value applies to the slots which received the request of copying data between storage systems.

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.

Deleting remote paths

You can delete remote paths from the primary or secondary storage systems.

To perform this task in CCI, use the raidcom delete rcu_path command or the raidcom delete rcu_iscsi_port command.

Before you begin

  • Before deleting remote paths, make sure that the remaining number of remote paths will be greater than the minimum number of paths setting. You can do this in the View Remote Connection Properties window. The delete path operation will fail if the number of remaining paths is equal to or less than the minimum number of paths.
  • The primary storage system administrator can delete remote paths between the bidirectional port of the primary storage system and the bidirectional port of the secondary storage system. The secondary System administrator can delete remote paths between the bidirectional port of the secondary storage system and the bidirectional port of the primary storage system.

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.

Deleting the UR relationship

You can remove the Universal Replicator pair relationship between primary and secondary storage systems. You do this by removing the remote connection. Removing the relationship between the primary and the secondary storage systems also removes the remote paths between them. This operation must be performed on both the primary and secondary storage systems.

To perform this task in CCI, use the raidcom delete rcu command.

Before you begin

  • Required role: Storage Administrator (Remote Copy).
  • Make sure that all UR pair relationships between the local storage system and the remote storage system are deleted.

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.

Expansion of DP-VOL capacity while keeping pair status

You can expand the capacity of a DP-VOL used in the GAD, TrueCopy, Universal Replicator, ShadowImage, or Thin Image pair created between or on the following storage systems while keeping the pair status in each software product.

  • VSP 5000 series: Microcode version 90-04-04-00/00 or later
  • VSP G1x00, VSP F1500: Microcode version 80-06-82-xx/xx or later
  • VSP G/F350, G/F370, G/F700, G/F900: Microcode version 88-06-02-x0/00 or later
  • VSP E series: Microcode version 93-02-03-x0/00 or later

If only VSP G1x00, VSP F1500 is used and the expansion is only for a GAD pair, the supported microcode version is 80-06-74-xx/xx or later.

Expanding DP-VOL capacity used in Universal Replicator pair

When deciding to expand the capacity of a DP-VOL used as a volume in a UR pair, understand that there are two different procedures, each depending on whether the UR pair shares the same volumes with other software or does not share the same volumes. This procedure describes expanding DP-VOL capacity when the UR pair does not share the volume (a UR pair alone).

NoteOnly the assigned page capacity out of the DP-VOL capacity is counted as the UR license capacity.

Before you begin

Ensure that the following conditions are met:
  • A V-VOL to be expanded is not an external volume
  • The LDEV format is being performed on a V-VOL to be expanded
  • A pool containing a V-VOL to be expanded meets any of the following conditions:
    • Normal condition
    • The used capacity of the pool exceeds the depletion threshold
    • The pool is being shrunk
  • A V-VOL to be expanded is a volume created on the storage systems described in Expansion of DP-VOL capacity while keeping pair status
  • Make sure that there is enough UR license capacity for the page capacity assigned to the expanded volume capacity before the expansion

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. 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.
      • 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 UR pair.

    3. Resynchronize the UR pair.

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

      Verify that the current differential data management method is the hierarchical difference management.
  4. 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

Expansion order policy when Universal Replicator pair shares the same volumes with other software

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
GUID-BBB27B75-3A82-4217-B5FD-79A0BD6426FC-low.png
  • 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.

Expanding DP-VOL capacity when TrueCopy pair is used with Universal Replicator

You can expand the capacity of DP-VOLs used as pair volumes when a UR pair and a TC pair are created in a 3DC cascade configuration, a 3DC multi-target configuration, or a 3DC delta resync configuration.

For the detailed procedures for verifying the differential data management method, expanding the capacity, and verifying the expansion during the following procedures, see Expanding DP-VOL capacity used in Universal Replicator pair .

Expanding DP-VOL capacity in a 3DC cascade configuration or a 3DC multi-target configuration with UR pair and TC pair

Before you begin

  • A V-VOL to be expanded is not an external volume.
  • The LDEV format is being performed on a V-VOL to be expanded.
  • A pool containing a V-VOL to be expanded meets any of the following conditions:
    • Normal condition
    • The used capacity of the pool exceeds the depletion threshold
    • The pool is being shrunk
  • When using GAD, TC, or UR, make sure that there is enough software license capacity for the page capacity assigned to the expanded volume capacity before the expansion.
  • A V-VOL to be expanded is created on a valid storage system. See Expanding DP-VOL capacity while keeping pair status.

Procedure

  1. Verify that each volume of the P-VOLs and the S-VOLs used in a UR pair and a TC pair with which the UR pair shares the same volume meets the prerequisites.

  2. Display the detailed information about the UR pair and the TCpair 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 TC pair and UR pair.

    3. Resynchronize the TC pair and UR pair.

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

  4. Suspend the TC pair and UR pair.

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

    • 3DC cascade configuration

      GUID-E1F91536-351D-4BE8-8782-DF58E5483EE2-low.png

    • 3DC multi-target configuration

      GUID-C5016543-C8F9-4ED9-8CA7-77384707CFAB-low.png

    • 3DC delta resyc configuration

      GUID-A0B28F5B-C749-429B-B086-B61D6A174B1F-low.png

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

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

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

    The following table shows how the expansion process is displayed.

    Expansion statusCCIHDvM - SN
    P column in the pairdisplay commandProcessing Status field in the Remote Replication window
    Not being expandedNBlank
    Being expandedE*Expanding*
    * This status has been displayed after expanding the P-VOL or S-VOL capacity in the TC pair and UR pair 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 TC pair and UR pair.

    3. Resynchronize the TC pair and UR pair.

    4. Display the detailed information about the TC pair and 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
Expanding DP-VOL capacity in a 3DC delta resync configuration with UR pair and TC pair

Before you begin

  • A V-VOL to be expanded is not an external volume.
  • The LDEV format is being performed on a V-VOL to be expanded.
  • A pool containing a V-VOL to be expanded meets any of the following conditions:
    • Normal condition
    • The used capacity of the pool exceeds the depletion threshold
    • The pool is being shrunk
  • When using GAD, TC, or UR, make sure that there is enough software license capacity for the page capacity assigned to the expanded volume capacity before the expansion.
  • A V-VOL to be expanded is created on a valid storage system. See Expanding DP-VOL capacity while keeping pair status.

Procedure

  1. Verify that each volume of the P-VOLs and the S-VOLs used in a UR pair and a TC pair with which the UR pair shares the same volume meets the prerequisites.

  2. Display the detailed information about the TCpair, UR pair, and UR delta resync 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.

    There are two ways to change to the hierarchical difference management. The table shows the advantages and disadvantages for each change procedure. Make sure to perform the change procedure selected by the user.
    ItemChange procedure 1Change procedure 2
    Change to the hierarchical difference by performing delta resync operationChange to the hierarchical difference by re-creating UR delta resync pair
    AdvantageThe volume capacity can be expanded while maintaining the 3DC delta resync configuration because deletion of UR delta resync pair is not required.All of the following operations are not required:
    • Stopping host I/Os.
    • The host failover operation to secondary site.
    • The delta resync operation.
    Disadvantage
    • Stopping host I/Os is required for switching from the primary site to the secondary site.
    • The delta resync operation is required.
    The 3DC delta resync configuration is not restored after the UR delta resync pair is deleted until it is recreated.
    Delta resync operationRequiredNo required
    Host failover to secondary site during delta resync operationRequiredNo required
    Deleting and re-creating UR delta resync pairNo requiredRequired
    Change procedure 1
    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. Stop the host operations at the primary site.

    3. Suspend the TC pair (swap suspend).

    4. Resume the host operations at the secondary site.

    5. Perform the delta resync operation.

    6. Resynchronize the TC pair (swap resync).

    7. Stop the host operations at the secondary site.

    8. Suspend the TC pair (swap suspend).

    9. Resume the host operations at the primary site.

    10. Perform the delta resync operation.

    11. Resynchronize the TC pair (swap resync).

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

    Change procedure 2
    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 UR pair (swap suspend).

    3. Delete the UR delta resync pair.

    4. Create the UR delta resync pair.

    5. Resynchronize the UR pair.

    6. Suspend the TC pair (swap suspend).

    7. Resynchronize the TC pair.

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

  4. Suspend the TC pair and UR pair.

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

    GUID-FD28FD4E-3A5F-4EA1-9EB5-E18EA7861AD4-low.png After expanding the first volume capacity (S-VOL of the UR pair), if you cannot expand the S-VOL capacity in the TC pair, you cannot expand the P-VOL capacity in the TC pair, or resynchronizing the TC pair or 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. Resynchronize the TC pair and the UR pair.

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

    In addition, verify that each volume capacity in the TC pair and the UR pair and SI pair is not being expanded.

    The following table shows how the expansion process is displayed.

    Expansion statusCCIHDvM - SN
    P column in the pairdisplay commandProcessing Status field in the Remote Replication window
    Not being expandedNBlank
    Being expandedE*Expanding*
    * This status has been displayed after expanding the P-VOL or S-VOL capacity in the TC pair and UR pair 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 TC pair and the 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. Stop the host operations at the primary site.

    3. Suspend the TC pair (swap suspend).

    4. Resume the host operations at the secondary site.

    5. Perform the delta resync operation.

    6. Resynchronize the TC pair (swap resync).

    7. Stop the host operations at the secondary site.

    8. Suspend the TC pair (swap suspend).

    9. Resume the host operations at the primary site.

    10. Perform the delta resync operation.

    11. Resynchronize the TC pair (swap resync).

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

    13. 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

Expanding DP-VOL capacity when UR pair is used with ShadowImage

You can expand the capacity of DP-VOLs used as pair volumes when a UR pair is used with SI. This procedure provides an example for expanding the DP-VOL capacity in a configuration where the SI L1 pair and L2 pair are created for each volume of the P-VOL and S-VOL in the UR pair. For the detailed procedures for verifying the differential data management method, expanding the capacity, and verifying the expansion during the following procedure, see Expanding DP-VOL capacity used in Universal Replicator pair .

Before you begin

  • A V-VOL to be expanded is not an external volume.
  • The LDEV format is being performed on a V-VOL to be expanded.
  • A pool containing a V-VOL to be expanded meets any of the following conditions:
    • Normal condition
    • The used capacity of the pool exceeds the depletion threshold
    • The pool is being shrunk
  • When using GAD, TC, or UR, make sure that there is enough software license capacity for the page capacity assigned to the expanded volume capacity before the expansion.
  • A V-VOL to be expanded is created on a valid storage system. See Expanding DP-VOL capacity while keeping pair status.
  • Ensure that the numbers of differential tables and pair tables required after the expansion do not exceed the maximum number allowed on the storage system. For information about calculating the number of tables, see Calculating the numbers of differential and pair tables for each pair.
.

Procedure

  1. Verify that each volume of the P-VOLs and S-VOLs in a UR pair and SI pairs with which the UR pair shares the same volumes meets the prerequisites.

  2. Display the detailed information about the 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 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 hierarchical difference management.

  4. Suspend the UR pair and all SI pairs.

  5. Verify the pair statuses of the SI pairs.

    The SI pair volume capacity can be expanded when the SI pairs are in the PSUS or PSUE status. Verify the current pair statuses of the SI pairs.
  6. Expand each volume capacity, and then verify that the expansion is complete in the expansion order shown in the following figure.

    GUID-96C7FD49-AADA-43AD-820B-53BE3C1C7D33-low.png After expanding the first volume capacity (S-VOL in the UR pair), if you cannot expand the DP-VOL capacity in the SI pair, you cannot expand the P-VOL capacity in the UR pair, or resynchronizing the 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.
  7. Resynchronize the UR pair.

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

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

    The following table shows how the expansion process is displayed.

    Expansion statusCCIHDvM - SN
    P column in the pairdisplay commandProcessing Status field in the Remote Replication or Local Replication window
    Not being expandedNBlank
    Being expandedE*Expanding*
    * This status has been displayed after expanding the P-VOL or S-VOL capacity in the UR pair until performing the pair resync operation. After the resync operation is complete, the status is migrated to the Not being expanded status. In the SI pair, the Being expanded status is displayed for a while (30 seconds or so) after the expansion of the P-VOL and S-VOL capacity is complete. After that, the status is migrated to the Not being expanded status.
  9. 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 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
Calculating the numbers of differential and pair tables for each pair

If a DP-VOL exceeds 4 TB, the differential tables are placed in the hierarchy memory instead of the shared memory, and the differential tables in the shared memory are not used. Therefore, it is not necessary to calculate the number of differential tables for DP-VOLs over 4 TB.

Procedure

  1. Calculate how many differential tables are required for each pair.

    Use the following formulas:
    number-of-differential-tables-for-expansion = number-of-differential-tables-after-expansion - number-of-differential-tables-before-expansion
    number-of-differential-tables-per-pair = ceiling ((volume-capacity [KB] / 256) / 20,448)

    Ensure that the ceiling value enclosed in the parenthesis () is rounded up to the next integer.

  2. Calculate how many pair tables are required for each pair.

    Use the following formulas:
    number-of-pair-tables-for-expansion = number-of-pair-tables-after-expansion - number-of-pair-tables-before-expansion
    number-of-pair-tables-per-pair = ceiling ((number-of-pair-tables-per-pair / 36)

    Ensure that the ceiling value enclosed in the parenthesis () is rounded up to the next integer.

  3. Verify that the following numbers do not exceed the maximum number allowed on the storage system.

    • The total numbers of current pair tables and pair tables required for expanding the capacity
    • The total numbers of current differential tables and differential tables required for expanding the capacity

    You can check the numbers of differential and pair tables in the Local Replication window.

Expanding DP-VOL capacity when UR pair is used with Thin Image

You can expand the capacity of DP-VOLs used as pair volumes when a UR pair is used with HTI. This procedure provides an example for expanding the DP-VOL capacity in a configuration where the HTI L1 pair and L2 pair are created for each volume of the P-VOL and S-VOL in the UR pair. For the detailed procedures for verifying the differential data management method, expanding the capacity, and verifying the expansion during the following procedure, see Expanding DP-VOL capacity used in Universal Replicator pair.

Before you begin

  • A V-VOL to be expanded is not an external volume.
  • The LDEV format is being performed on a V-VOL to be expanded.
  • A pool containing a V-VOL to be expanded meets any of the following conditions:
    • Normal condition
    • The used capacity of the pool exceeds the depletion threshold
    • The pool is being shrunk
  • When using GAD, TC, or UR, make sure that there is enough software license capacity for the page capacity assigned to the expanded volume capacity before the expansion.
  • A V-VOL to be expanded is created on a valid storage system. See Expanding DP-VOL capacity while keeping pair status.
  • A V-VOL to be expanded is not used in a pair with the clone attribute.
  • Ensure that the following numbers required after the expansion do not exceed the maximum number allowed on the storage system:
    • The snapshot estimated manageable capacity
    • The number of cache management devices
    • The subscription limit of the V-VOL capacity

For information about calculating these numbers, see Calculating the snapshot estimated manageable capacity, the numbers of cache management devices, and the subscription limit of the V-VOL capacity.

Procedure

  1. Verify that each volume of the P-VOLs and S-VOLs in a UR pair and HTI pairs with which the UR pair shares the same volumes meets the prerequisites.

  2. Display the detailed information about the 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 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 hierarchical difference management.

  4. Suspend the UR pair.

  5. Verify the pair statuses of the HTI pairs.

    The HTI pair volume capacity can be expanded when the HTI pairs are in the PAIR, PSUS or PSUE status. Verify the current pair statuses of the HTI pairs.
  6. Expand each volume capacity, and then verify that the expansion is complete in the expansion order shown in the following figure.

    GUID-9015F3EC-47AC-42FC-81E3-46BBF2838F99-low.png After expanding the first volume capacity (S-VOL in the UR pair), if you cannot expand the DP-VOL capacity in the HTI pair, you cannot expand the P-VOL capacity in the UR pair, or resynchronizing the 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.
  7. Resynchronize the UR pair.

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

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

    The following table shows how the expansion process is displayed.

    Expansion statusCCIHDvM - SN
    P column in the pairdisplay or raidcom get snapshot commandProcessing Status field in the Remote Replication or HTI pairs window
    Not being expandedNBlank
    Being expandedE*Expanding*
    * This statuses have been displayed after expanding the P-VOL or S-VOL capacity in the UR pair, and before performing the pair resync operation. After the resync operation is complete, the status is migrated to the Not being expanded status. In the HTI pair, the Being expanded status is displayed for a while (30 seconds or so) after the expansion of the P-VOL and S-VOL capacity is complete. After that, the status is migrated to the Not being expanded status.
  9. 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 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
Calculating the snapshot estimated manageable capacity, the numbers of cache management devices, and the subscription limit of the V-VOL capacity

Procedure

  1. Calculate the snapshot estimated manageable capacity required for expanding the capacity of a Thin Image root volume.

    To expand the capacity of a Thin Image root volume, verify that the snapshot estimated manageable capacity is available. Use the following formulas:
    Snapshot-estimated-manageable-capacity-for-root-volume-expansion = Snapshot-estimated-manageable-capacity-after-root-volume-expansion - Snapshot-estimated-manageable-capacity-before-root-volume-expansion
    Snapshot-estimated-manageable-capacity = (Root-volume-capacity [TB] / 2.6 [TB]) x 3,024 [GB] + (168 [GB] x 2 (consumed-shared-memory [GB]))

    Expanding the volumes other than a root volume does not consume the snapshot estimated manageable capacity. You can check the snapshot estimated manageable capacity in the Local Replication window.

  2. Calculate the maximum number of cache management devices required for expanding the capacity of a Thin Image root volume.

    To expand the capacity of a Thin Image root volume, verify that the cache management devices are available.

    Use the following formula:

    number-of-cache-management-devices-for-root-volume-expansion = ceiling ((Root-volume-capacity-after-expansion [TB] / 2.6 [TB])) - ceiling ((Root-volume-capacity-before-expansion [TB] / 2.6 [TB]))

    Ensure that the ceiling value enclosed in the parenthesis () is rounded up to the next integer.

    Expanding the volumes other than a root volume does not consume the cache management devices.

  3. Calculate the V-VOL capacity to be added by expanding the capacity of a Thin Image root volume.

    To expand the capacity of a Thin Image root volume, verify that the capacity after the expansion does not exceed the subscription limit of the V-VOL capacity contained in a DP pool.

    Use the following formula:

    V-VOL-capacity-added-by-root-volume-expansion = Thin Image-pair-capacity-calculated-based-on- root-volume-capacity-after-expansion - Thin Image-pair-capacity-calculated-based-on-root-volume-capacity-before-expansion
    Thin Image-pair-capacity = Σ ceiling ((Root-volume-capacity [MB] × number-of-pairs* × 2  / 42 [MB])) × 42 [MB]+ Σ ceiling ((Root-volume-capacity [MB] × number-of-pairs* × 2 / 2,921,688 [MB])) × 175,434 [MB]

    * Use the maximum number of HTI pairs to be created in the applicable snapshot tree as number-of-pairs instead of the number of pairs currently created in the applicable snapshot tree because the allocated pages are not released if you delete some pairs.

    Ensure that the ceiling value enclosed in the parenthesis () is rounded up to the next integer.

    Expanding the volumes other than a root volume does not add the V-VOL capacity contained in a DP pool in Thin Image.

Expanding DP-VOL capacity in a 3DC cascade configuration or a 3DC multi-target configuration with three UR sites

  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

      GUID-7638E274-E996-4FC5-9DEC-3886E46C9D97-low.png

    • 3DC multi-target configuration

      GUID-4716D4F7-2852-4946-811A-D0A9446D0BFE-low.png

    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 statusCCIHDvM - SN
    P column in the pairdisplay commandProcessing Status field in the Remote Replication window
    Not being expandedNBlank
    Being expandedE*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

Expanding DP-VOL capacity in a 3DC delta resync configuration with three UR sites

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.

    GUID-BBCFC4E8-C3A7-4DB8-B9B3-5468A0AD3B50-low.png 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 statusCCIHDvM - SN
    P column in the pairdisplay commandProcessing Status field in the Remote Replication window
    Not being expandedNBlank
    Being expandedE*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

Expansion order policy in configuration where P-VOL in remote replication shares the same volume with S-VOL in local replication

  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.

Expansion order policy in 3DC cascade, 3DC multi-target, or 3DC delta resync configuration with remote replications

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

    GUID-E1F91536-351D-4BE8-8782-DF58E5483EE2-low.png

  • 3DC multi-target configuration

    GUID-C5016543-C8F9-4ED9-8CA7-77384707CFAB-low.png

  • 3DC delta resyc configuration

    GUID-A0B28F5B-C749-429B-B086-B61D6A174B1F-low.png

Expansion order when remote replications in a 3DC cascade configuration share the same volumes with local replications (ShadowImage/Thin Image)

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.

GUID-0F26984D-4589-428E-B97E-A546C507B91D-low.png

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.

Recovering from failure if one volume capacity in Universal Replicator pair cannot be expanded

If only one volume capacity in a UR pair can be expanded while the other cannot be expanded, the resync operation in the UR pair cannot be performed after the expansion because the capacity of both of the volumes is not the same.

When a UR pair is used with GAD, TC, SI, or HTI, if the capacity of the P-VOL and the S-VOL of one of the software products cannot be expanded, which causes the invalid state that the expansion of the entire volume capacity is not complete. Perform the following operation to recover from the invalid state.

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.

Recovering from failure if one volume capacity in Universal Replicator pair has been expanded

You can recover from a failure if only one volume capacity in a UR pair can be expanded, while a failure occurs on the other volume before the expansion.

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.

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

This topic describes and provides instructions for performing planned outages of storage systems in a GAD 3DC delta resync (GAD+UR) environment. For details about I/O modes, see the Global-Active Device User Guide.

Powering off the GAD+UR primary storage system

Use the following procedure to power off the primary storage system in a GAD 3DC delta resync environment.

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:

    1. Device Manager - Storage Navigator displays HOLDING.
    2. Device Manager - Storage Navigator displays HOLD.
  4. Power off the primary storage system.

Powering on the GAD+UR primary storage system

Use the following procedure to power on the primary storage system in a GAD 3DC delta resync environment.

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:

    1. Device Manager - Storage Navigator displays HOLDING.
    2. 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

The GAD P-VOL and S-VOL are now reversed compared to the original configuration before the planned outage. To restore the original configuration, reverse the GAD P-VOL and S-VOL.

Powering off the GAD secondary storage system

Use the following procedure to power off the GAD secondary storage system in a GAD 3DC delta resync environment.

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:

    1. Device Manager - Storage Navigator displays HOLD.
    2. Device Manager - Storage Navigator displays HOLDING.
  4. Power off the GAD secondary storage system.

Powering on the GAD secondary storage system

Use the following procedure to power on the GAD secondary storage system in a GAD 3DC delta resync environment.

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:

    1. Device Manager - Storage Navigator displays HOLDING.
    2. 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.

Powering off the UR secondary storage system

Use the following procedure to power off the UR secondary storage system in a GAD 3DC delta resync environment.

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:

    1. Device Manager - Storage Navigator displays HOLD.
    2. Device Manager - Storage Navigator displays HOLDING.
  3. Power off the UR secondary storage system.

Powering on the UR secondary storage system

Use the following procedure to power on the UR secondary storage system in a GAD 3DC delta resync environment.

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:

    1. Device Manager - Storage Navigator displays HOLDING.
    2. 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.

Powering off the external storage system, I/O at primary site (GAD+UR)

Use the following procedure to power off the external storage system when server I/O continues to the primary storage system in a GAD 3DC delta resync environment.

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:

    1. Device Manager - Storage Navigator displays HOLD.
    2. 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.

Powering on the external storage system, I/O at primary site (GAD+UR)

Use the following procedure to power on the external storage system when server I/O continues to the primary storage system in a GAD 3DC delta resync environment.

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:

    1. Device Manager - Storage Navigator displays HOLDING.
    2. 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.

Powering off external storage system, I/O at secondary site (GAD+UR)

Use the following procedure to power off the external storage system when server I/O continues to the GAD storage system in a GAD 3DC delta resync environment.

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:

    1. Device Manager - Storage Navigator displays HOLDING.
    2. 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.

Powering on external storage system, I/O at secondary site (GAD+UR)

Use the following procedure to power on the external storage system when server I/O continues to the GAD storage system in a GAD 3DC delta resync environment.

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:

    1. Device Manager - Storage Navigator displays HOLDING.
    2. 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

The GAD P-VOL and S-VOL are reversed compared to the original configuration (before the planned outage). To restore the original configuration, reverse the GAD P-VOL and S-VOL.