6/3/2019

HPE Support Center

HPE 3PAR Remote Copy Software - Creating Volume Groups for Bidirectional
Remote Copy
Creating volume groups for bidirectional remote copy
Link to the list of available documents

Creating volume groups for bidirectional remote copy

Procedure

1. Verify that the virtual volumes user plan to replicate from the new primary system to the new backupalready exist. For more
information, see Verifying that virtual volumes are created for unidirectionalremote copy.
2. On the new primary system (System2), create a primary volume group:

NOTE: User can create groups and add volumes to groups without disrupting host access to volumes byissuing the following command:
cli% creatercopygroup <group_name> <target_name>:<mode>

Where:
<group_name> - Name of the primary volume group (Group2)
<target_name>> - Name of the secondary system (System1)
<mode> - sync for synchronous mode, or periodic for asynchronous periodic mode.
The creatercopygroup command creates the following:
A primary volume group (Group2) on the primary system (the system on which user issue the ,command, System2).
A name for the corresponding secondary volume group using the convention:
<primary_group_name>.r<sys_ID>
(of the primary system)
In this example, the secondary volume group is named Group2.r125.
The corresponding secondary volume group (Group2.r125) on the secondary system (in this case,the secondary system,
System1).

NOTE: If the secondary system cannot be contacted during execution of the creatercopygroup command, the following
message is returned immediately:
Target <target_name> is not ready for commands
Ensure that links are up on both systems, and then reissue the creatercopygroup command. Formore information, see
Checking the links between systems for unidirectional remote copy.

3. (Optional). If user are creating a volume group that uses periodic mode, user can set up automatic synchronization.

1/3
6/3/2019

CAUTION: Do not set a resynchronization period at this point if user plan to perform the initial synchronizationand backup
using tape. For more information, see Using tape for initial synchronization andbackup.

To specify a resynchronization period for a primary volume asynchronous periodic group, on the primarysystem (System2), issue
either of the following commands:
cli% setrcopygroup period <period_value>{s|m|h|d} <target_name> <group_name>
Where:
<period_value>s|m|h|d - Synchronization time period (time between start of resynchronizations), followed by time unit: s
(seconds), m (minutes), h (hours), or d (days)
<target_name> - Name of the secondary system (System1)
<group_name> - Name of the primary volume group (Group2)
The setrcopygroup period command for async periodic and async streaming modes:
Specifies that groups that are in asynchronous periodic mode should be periodically synchronized inaccordance with the
specified <period_value>
Groups that are in asynchronous streaming mode will transition to Logging state when replicationresources drop below
sustainable limits. The <period_value> is used to define the order that thesegroups will be stopped and restarted
automatically, as well as the minimum elapsed time each specificgroup will be restarted once the replication resources are
restored.
Groups with the largest <period_value> will be stopped first and restarted last. A <period_value> of 0 will prevent
automatic restarting of the group; these groups will need to be started manually. <period_value> s|m|h|d specifies the
time period in units of seconds (s), minutes (m), hours (h), ordays (d), for automatic resynchronization (for example, 14h for 14
hours). The time can be a minimumof 30 seconds and up to a maximum of one year, or set to zero. This specifier can be used
only with theperiod subcommand.
For asynchronous periodic mode, this value is used to specify the time period for automaticresynchronization. The time can be
a minimum of 5 minutes and up to a maximum of one year, or set tozero. A <period_value> of 0 will prevent automatic
resynchronization.
For asynchronous streaming mode, the <period_value> parameter is used to define the order inwhich these groups will be
stopped and restarted automatically. The <period_value> parameter alsodefines the minimum elapsed time after which
each specific group will be restarted once the replicationresources are restored.
Or:
cli% setrcopygroup period -pat <pattern> <period_value>s|m|h|d <target_name>
Where <period_value> represents the pattern of volume group names (for example, Group*).
The setrcopygroup snap_freq command for async streaming mode (bidirectionalconfiguration):
Usage:
setrcopygroup snap_freq [option] [<pattern>]<freq_value>
<target_name>[<group_name>]
snap_freq
Specifies the interval at which Remote Copy takes coordinated snapshots. Only applicable inasynchronous streaming mode.
The interval can be a minimum of five minutes and up to a maximum ofone year.
<freq_value>s|m|h|d
Specify the time period in units of seconds (s), minutes (m), hours (h), or days (d), for automaticcoordinated snapshots taken
on both local and remote systems. The time must be longer than or equalto five minutes and not more than one year in
duration. If the value is set to zero, automatic coordinatedsnapshots are turned off. The default value is 1 hour. Applicable only
in asynchronous streaming mode.
4. On the primary system (System2), add one or more pre-existing virtual volumes to the newly createdvolume group (Group2) by
issuing either of the following commands:
cli% admitrcopyvv <VV_name> <group_name> <target_name:sec_VV_name>
Where:
<VV_name> - Name of the virtual volume (vv2) to add to the primary volume group on the primarysystem
2/3
6/3/2019
<group_name> - Name of the primary volume group (Group2) on the primary system
<target_name> - Name of the secondary system (System1)
<sec_VV_name> - Name of the corresponding virtual volume on the secondary system (vv2_remote)
Or:
cli% admitrcopyvv -pat <pattern> <group_name> <target_name:sec_VV_name>
Where <pattern> represents the pattern of virtual volume names (for example, vv*).

NOTE: A full synchronization is not necessary, provided that the volumes being admitted are new on boththe primary and
secondary storage systems.
The admitrcopyvv command provides a -nosync option that specifies that the volume shouldskip the initial
synchronization. This option is for the admission of volumes that have beenpresynchronized with the target volume. By
default, a full synchronization is performed on addedvolumes unless the -nosync option is specified.

CAUTION: Using the -nosync option is not recommended. Use this option with care. To prevent data frombecoming
unavailable or inconsistent, do not run any I/O during the operation.

The admitrcopyvv command:

Adds the specified virtual volume (vv2) to the primary volume group (Group2) on the primary system (System2).
Adds the specified virtual volume (vv2_remote) to the corresponding secondary volume group on thesecondary system
(System1).
Because HPE 3PAR Remote Copy created this secondary volume group (Group2.r125) when usercreated the primary
volume group, HPE 3PAR Remote Copy automatically adds vv2_remote to Group2.r125.

NOTE: To redo volume groups:

a. Use the removercopygroup command.
b. Repeat the setup from 1

To redo virtual volume placement:

a. Use the dismissrcopyvv command.
b. Repeat the setup from 4

top

Link to the list of available documents

Click here to view a list of documents available for the HPE 3PAR Remote Copy Software .

top

3/3