HPE Primera OS Configuring and Managing Data Replication Using Remote

HPE Primera OS: Configuring and managing data replication using Remote
Copy
Part Number: 20-PRI600-RCCF-ED2

Published: March 2022
Edition: 2
HPE Primera OS: Configuring and managing data replication using Remote Copy
Abstract
This guide is for system and storage administrators to create and manage a data replication configuration between storage systems using HPE
Remote Copy.
Part Number: 20-PRI600-RCCF-ED2
Published: March 2022
Edition: 2
© Copyright 2019, 2022 Hewlett Packard Enterprise Development LP
Notices
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and
services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained
herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR
12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed
to the U.S. Government under vendor's standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is
not responsible for information outside the Hewlett Packard Enterprise website.
Acknowledgments
Intel® , Itanium ® , Optane™, Pentium® , Xeon® , Intel Inside ® , and the Intel Inside logo are trademarks of Intel Corporation or its subsidiaries.
AMD and the AMD EPYC ™ and combinations thereof are trademarks of Advanced Micro Devices, Inc.
Microsoft ® and Windows ® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java® and Oracle® are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

All third-party marks are property of their respective owners.
Revision history
Part number Publication date Edition Summary of changes
20-PRI600-RCCF-ED2 March 2022 2 Updated for HPE Primera OS 4.5
20-PRI600-RCCF-ED1 October 2021 1 Updated for HPE Primera OS 4.4
P36431-002 May 2021 4 Combined Primera OS configuration and management documents

into this single publication
HPE Primera OS 4.3: Added Active Peer Persistence Remote Copy
support
P36431-001 June 2020 3 HPE Primera OS 4.2: Added three data center Peer Persistence
(3DC PP) support with both RCIP and RCFC links
HPE Primera OS 4.2: Added synchronous long distance (SLD)
support with both RCIP and RCFC links
This publication replaces the HPE Primera OS: Configuring data
replication using Remote Copy over IP and the HPE Primera OS:
Configuring data replication using Remote Copy over FC
publications.
Part number Publication date Edition Summary of changes
P26627-001 January 2020 2 HPE Primera OS 4.0: Added synchronous long distance (SLD) with
IP links support
HPE Primera OS 4.1: Added HPE Primera Remote Copy over Fibre
Channel (RCFC) support
P23108-001 September 2019 1 Initial release

Table of contents
1 Determining compatibility for Remote Copy

1.1 Accessing the HPE Primera Support Matrix in SPOCK
1.2 Accessing the HPE Host OS Support Matrix in SPOCK
1.3 Remote Copy over IP (RCIP) network transport requirements
1.4 Remote Copy over FC (RCFC) network transport requirements
2 Preparing the logical Remote Copy links
2.1 Configuring the RCIP links
2.2 Configuring the RCFC links
3 Remote Copy data replication solutions
4 Configuring a 1-to-1 data replication solution
4.1 Creating a 1-to-1 Remote Copy configuration
4.2 Creating a synchronous Remote Copy group
4.3 Creating an asynchronous periodic Remote Copy group
5 Configuring a Peer Persistence data replication solution
5.1 Creating a Classic Peer Persistence configuration
5.2 Creating a Classic Peer PersistenceRemote Copy group
6 Configuring an Active Peer Persistence data replication solution
6.1 Creating an Active Peer Persistence Remote Copy configuration using the CLI
6.2 Creating an Active Peer Persistence Remote Copy Group using CLI
6.3 Creating an Active Peer Persistence Remote Copy configuration using SSMC
6.4 Creating an Active Peer PersistenceRemote Copy group using SSMC
7 Configuring an Active Sync Replication solution
7.1 Creating an Active Sync Replication Remote Copy configuration using the CLI
7.2 Creating an Active Sync Replication Remote Copy Group using the CLI
8 Configuring a synchronous long distance data replication solution
8.1 Creating a synchronous long distance configuration
8.2 Creating a synchronous long distance Remote Copy group
9 Configuring a three data center Peer Persistence data replication solution
9.1 Creating a three data center Peer Persistence configuration
9.2 Creating a three data center Peer Persistence Remote Copy group
10 Configuring a one-to-many data replication solution
10.1 Creating a one-to-many Remote Copy configuration
10.2 Creating synchronous or periodic Remote Copy groups for 1-to-N configurations
11 Configuring a many-to-one data replication solution
11.1 Creating a many-to-one Remote Copy configuration
11.2 Creating synchronous or periodic Remote Copy groups for N-to-1 configurations
12 Managing a Remote Copy group
12.1 Starting a Remote Copy group
12.2 Stopping a Remote Copy group
12.3 Deleting a Remote Copy group
12.4 Adding existing virtual volumes to an existing Remote Copy group
12.5 Creating virtual volumes for an existing Remote Copy group
12.6 Removing virtual volumes from an existing Remote Copy group
12.7 Reversing the direction of data flow in a Remote Copy group
12.8 Performing a transparent switchover for Active Sync Replication, Active Peer Persistence or classic Peer Persistence
12.9 Performing a switchover for 3DC PP
12.10 Changing the policies of a non-Peer Persistence Remote Copy group
12.11 Changing the policies of an Active Peer Persistence, Classic Peer Persistence, or 3DC PP group
12.12 Changing the replication mode for a Remote Copy group
12.13 Growing the size of virtual volumes in a Remote Copy group
12.14 Manually synchronizing a Remote Copy group
13 Managing a Remote Copy configuration
13.1 Adding links to an existing Remote Copy target
13.2 Removing links from an existing Remote Copy target
13.3 Adding a target to a Remote Copy configuration
13.4 Removing a target from a Remote Copy configuration
13.5 Check RCIP link throughput and latency
13.6 Editing throughput and performance tuning on an RCIP target
13.7 Editing the name of a Remote Copy target
13.8 Converting a Peer Persistence configuration to an Active Peer Persistence configuration using SSMC
13.9 Converting a Classic Peer Persistence Remote Copy configuration to Active Peer Persistence using the CLI
13.10 Converting an Active Peer Persistence configuration back to Classic Peer Persistence using CLI
13.11 Converting an existing Peer Persistence configuration to a 3DC PP configuration
13.12 Converting an existing SLD configuration to a 3DC PP configuration
13.13 Adding storage systems to a one-to-one configuration creating a one-to-many configuration
13.14 Adding storage systems to a one-to-one configuration creating a many-to-one configuration
14 Reference
14.1 Remote Copy port on a controller node
14.2 Quorum Witness and automatic transparent failover (ATF)
14.3 Creating a Quorum Witness client configuration
14.4 Remote Copy groups
14.5 Remote Copy group policies
15 Related documentation
16 Websites
17 Support and other resources
17.1 Accessing Hewlett Packard Enterprise Support
17.2 Accessing updates
17.3 Remote support
17.4 Customer self repair
17.5 Warranty information
17.6 Regulatory information
17.7 Documentation feedback
Determining compatibility for Remote Copy
Procedure
1. Review the storage system requirements for your OS version in the Support Matrix. See Accessing the HPE Primera Support Matrix
in SPOCK.
2. If you have a classic Peer Persistence configuration or Active Peer Persistence configuration, see Accessing the HPE Host OS
Support Matrix in SPOCK.
3. Review the requirements for your network transport method. Depending on your selected transport method, review the appropriate
requirements:
Review the transport requirements for Remote Copy over an IP (RCIP) network .
Review the transport requirements for Remote Copy over an FC (RCFC) network .
RCFC is supported in HPE Primera OS 4.1 or later and HPE SSMC version 3.6.1 or later.
TIP:
For three data center solutions, the transport links between the three systems can be IP, FC, or both. See the HPE
Primera Support Matrix for supported configurations.
Determining compatibility for Remote Copy 6

Accessing the HPE Primera Support Matrix in SPOCK
Procedure
1. Use your HPE Passport account to log in to SPOCK.
TIP:
If you do not have an HPE Passport account, create an account from the SPOCK login page.
2. In the left navigation pane, scroll to Other Hardware, and then click HPE Primera.
3. Click the appropriate support matrix.
Accessing the HPE Primera Support Matrix in SPOCK 7

Accessing the HPE Host OS Support Matrix in SPOCK
NOTE: This procedure only applies to classic Peer Persistence, Active Peer Persistence, and Active Sync Replication
configurations.
Procedure
1. Use your HPE Passport account to log in to SPOCK.
TIP:
If you do not have an HPE Passport account, create an account from the SPOCK login page.
2. In the left navigation pane, scroll to Software and click Array SW: Primera.
3. In the Array Software list, scroll to HPE Primera and HPE 3PAR Operating System Software: Array Software and click the
appropriate matrix.
Accessing the HPE Host OS Support Matrix in SPOCK 8

Remote Copy over IP (RCIP) network transport requirements
The physical connections between all storage systems used with Remote Copy over IP (RCIP) are through an IP-capable network. Each
link between a pair of storage systems is a logical link between a controller node on one storage system and a controller node on the
other storage system in the configuration. These links use an Ethernet port from each of the nodes in the storage systems.
To use an IP network for Remote Copy, the following requirements must be met.
A minimum of two storage systems that are supported for Remote Copy over IP. For supported combinations, see the appropriate
support matrix for the storage system available on SPOCK.
A minimum of two links from two different nodes for each storage system in the Remote Copy configuration. You can have a
maximum of two IP links per node.
Utilizing like node pairs (such as 0/1, 2/3) on each storage system is highly recommended, but is not a requirement.
Unique IP addresses for all RCIP ports.
A maximum of two RCIP target connections per port. Do not exceed two RCIP target connections per port.
Do not use network address translation (NAT) over RCIP . Remote Copydoes not support network address translation (NAT) over
RCIP.
A firewall that allows traffic only over the designated RCIP ports, TCP 5785 and 5001.
The Remote Copy subnet can be shared with other I/O traffic, but ensure that you have met these requirements:
Different IP subnets for the RCIP Ethernet port and the management Ethernet port of the system controller node.
A guaranteed amount of bandwidth is dedicated to Remote Copy. To replicate the generated data and to assure the Recovery
Point Objective (RPO) for the solution, size the RCIP network appropriately.
Reviewed the Service Level Agreement with the network provider to determine if the provider can temporarily reduce bandwidth
without notice. Check if there is a minimum bandwidth.
Reviewed performance considerations . When replicating synchronously over RCIP, the bandwidth must be large enough to
ensure that no performance issues arise from replicating data synchronously. For asynchronous periodic replication, the
bandwidth must be large enough to ensure that the RPO can be met.
Remote Copy over IP (RCIP) network transport requirements 9

Remote Copy over FC (RCFC) network transport requirements
The physical connections between all storage systems used with Remote Copy over FC (RCFC) are through an FC-capable network. Each
link between storage systems is a physical link between the controller node on one storage system and the controller node on another
storage system.
To use an FC network for Remote Copy, the following requirements must be met.
A minimum of two storage systems that are supported for Remote Copy over FC. For supported combinations, see the appropriate
support matrix for the storage system available on SPOCK.
A minimum of two links from two different nodes for each storage system in the Remote Copy configuration. You can have multiple
RCFC ports configured per node.
NOTE: Using like node pairs (such as 0/1, 2/3) on each storage system is highly recommended, but is not a
requirement.
A minimum of one pair of FC HBAs for each storage system. There must be enough ports available to accommodate separate port
usage for FC host connectivity and RCFC link connectivity. Ports for RCFC cannot be shared with ports for FC host I/O. The HBA pair
is required for load sharing and fault tolerance. The HBAs in each storage system connect those systems through FC SAN using FC
cable connections.
FC SAN is used to connect the storage systems (direct connect FC is not supported).
Requirements in the SAN Design Reference Guide are met.
Fabric zoning. The RCFC ports on the source and target storage systems must be zoned one-to-one. The zone cannot be shared with
other RCFC ports on the storage systems. Only two ports per zone are allowed. Each zone must contain one port from each storage
system in the Remote Copy array pair.
For example, Zone 1 contains ports 0:3:1 from System1 and System2 . Zone 2 contains ports 1:3:1 from System1 and
System2 . No other ports are configured for these zones.
To verify the zoning, use the following command:

showportdev all <N:S:P>
For example, proper zoning displays as:
showportdev all 0:3:1

PtId LpID Hadr ----Node_WWN---- -Port_WWN/HW_Addr- ftrs svpm bbct flen -----
vp_WWN----- Name
0x10a00 0x00 0x00 xxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx 0x8800 0x0032 n/a 0x0800
xxxxxxxxxxxxxxxx 0:3:1
0x20a00 0x02 n/a xxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx 0x0800 0x0032 0x0014 n/a
xxxxxxxxxxxxxxxx -
-------------------------------------------------------------------------------------------------
--------
2 total
If the port WWNs are not configured as expected, the zoning is incorrect. For example, if you see multiple ports, or only the local
port, or two ports that you did not mean to zone together.
Remote Copy over FC (RCFC) network transport requirements 10

Preparing the logical Remote Copy links
Prerequisites
Obtained access to an instance of SSMC for the storage systems.
Hardware connections for Remote Copy are completed as described in the Installing and configuring the field-integrated HPE
Primera 600 document.
For a diagram of the Remote Copy port, see Remote Copy port on a controller node .
Reviewed Remote Copy configuration options. See HPE Primera OS: Getting started with data replication using Remote Copy .
NOTE: HPE Primera documentation is located at: https://www.hpe.com/info/Primera600-docs
Procedure
1. To configure the logical links, see:
Configure the RCIP links .
Configure the RCFC links .
2. Select a Remote Copy data replication solution.
Preparing the logical Remote Copy links 11

Configuring the RCIP links
If the RCIP ports were not set up during the initial setup of the storage system, assign unique IP addresses to the RCIP ports. If the
source and target systems are on different subnets, assign a gateway.
Prerequisites
Reviewed Remote Copy over IP (RCIP) network transport requirements .
Obtained the N:S:P, IP addresses, subnet mask, gateway (optional), and port speed details for the RCIP ports from your network
administrator.
Procedure
1. On the HPE SSMC main menu, select Ports under STORAGE SYSTEMS.
2. In the list pane, select Port ID (N:S:P) for an RCIP port, and then select Actions > Edit.
TIP:
To quickly locate the RCIP ports, select the Protocol filter and select RCIP.
3. To add the IP address, subnet mask, gateway (if needed), Maximum Transmission Units (MTU), and configured rate, follow the
instructions on the screen.
4. Click OK.
5. Repeat this procedure for each RCIP port on each storage system.
If the ports are not available, see HPE Primera OS: Troubleshooting your Remote Copy configuration at
https://www.hpe.com/info/Primera600-docs.
Configuring the RCIP links 12

Configuring the RCFC links
Prerequisites
Reviewed Remote Copy over FC (RCFC) network transport requirements .
Obtained the N:S:P for the RCFC ports from your network administrator.
Set up one-to-one fabric zoning between the storage systems.
Procedure
1. On the HPE SSMC main menu, select Ports under STORAGE SYSTEMS.
2. Select the Protocol filter and choose RCFC.
3. Determine the Port State for the RCFC ports for your storage systems.
a. If the port state is Free, select Actions > Initialize.
b. If the port state is Offline, select Actions > Enable.
c. If the port shows Ready, go to the next step.
4. Verify that the RCFC ports have been zoned correctly.
a. Review Connected Devices for each RCFC port in your storage systems.
b. If the Port WWN list is not configured as expected, rezone the fabric.
An example of correct zoning: Zone 1 contains ports 0:3:3 from System1 and System2 . Zone 2 contains ports 1:3:3
from System1 and System2 . No other ports are configured for those zones.
If the ports are not ready or zoning is incorrect, see HPE Primera OS: Troubleshooting your Remote Copy configuration at
Configuring the RCFC links 13

Remote Copy data replication solutions
There are several Remote Copy data replication solutions. To create a Remote Copy configuration or Remote Copy group, select the
procedure for your solution.
Procedures to create Remote Copy replication solutions

Configuring a 1-to-1 data replication solution
Configuring a Peer Persistence data replication solution
Configuring an Active Peer Persistence data replication solution
Configuring an Active Sync Replication solution
Configuring a synchronous long distance data replication solution
Configuring a three data center Peer Persistence data replication solution
Configuring a one-to-many data replication solution
Configuring a many-to-one data replication solution
Remote Copy data replication solutions 14

Configuring a 1-to-1 data replication solution
Configuring a 1-to-1 data replication solution 15

Creating a 1-to-1 Remote Copy configuration
Procedure
1. On the HPE SSMC main menu, select Remote Copy Configurations under DATA PROTECTION.
2. Click + Create configuration or select Actions > Create.
3. Create links and targets between the two storage systems:
a. Select each system from the drop-down list.
b. Select a minimum of two RCIP or RCFC ports between each system.
TIP:
To see only RCIP or RCFC ports, you can select IP or FC for Show only these port types .
c. If you selected an incorrect link, select the port and then select Remove link in the Select Action dialog box. Then, click Continue.
As a best practice, ensure all Remote Copy ports used by a target operate at the same speed.
4. (Optional) To enter the geographical location for a system:
a. Under Systems, select the edit icon next to the system you want to update.
b. Enter the location and click OK.
5. (Optional) To update RCIP port settings such as gateway address, Maximum Transmission Units (MTU), or configured rate:
a. Under Port Pairs, select the edit icon next to the port you want to update.
b. Make the necessary changes and click OK.
6. (Optional) To test connectivity between systems with RCIP links:
a. Under Port Pairs, select the edit icon next to the port you want to test.
b. Click Ping.
7. Click Create.
Creating a 1-to-1 Remote Copy configuration 16

Creating a synchronous Remote Copy group
IMPORTANT: For procedures to create Remote Copy groups for Peer Persistence, Active Peer Persistence, three data
center Peer Persistence (3DC PP), and Synchronous Long Distance (SLD), see Remote Copy data replication solutions .
Those procedures provide the proper order of operations and application of correct Remote Copy group policies.
Prerequisites
The virtual volumes for the Remote Copy group are the same size on both the source and target systems and have snapshot space
allocated. Although different volume types are supported, HPE recommends both systems use the same type of volumes from the
same type of media. For example, both systems have thinly provisioned volumes on SSD.
If using virtual domains, virtual volumes for the source and target systems are in domains of the same name. See the HPE SSMC
online help for information about creating virtual volumes.
Procedure
1. On the HPE SSMC main menu, select Remote Copy Groups under DATA PROTECTION.
2. Click + Create group or select Actions > Create.
3. To enter information for the Source system, follow the instructions on the screen.
a. Enter a unique Group name.
b. Do one of the following:
Select Create manually for Remote virtual volumes.
Or, select Create automatically for Remote virtual volumes and enter the User and CPG information.
c. To automatically recover and synchronize the virtual volumes in the Remote Copy group if a failover occurs, select Enable for
Auto synchronize.
IMPORTANT:
Hewlett Packard Enterprise recommends enabling the Auto synchronize and Auto recover policies.
d. To automatically restart the Remote Copy group if links go down and then recover, select Auto recover.
The group restarts automatically after the links are re-established.
4. To enter information for a synchronous Target system, follow the instructions on the screen.
a. Select Synchronous (default) for Mode.
b. If you do not want to automatically start the Remote Copy group, select No for Start group after completion .
Yes is the default.
5. Click Create.
6. To create additional synchronous Remote Copy groups, repeat these steps.
More information
Remote Copy groups
Remote Copy group policies
Creating a synchronous Remote Copy group 17

Creating an asynchronous periodic Remote Copy group
Prerequisites
Procedure
3. To enter information for a periodic Target system, follow the instructions on the screen.
a. Select Periodic for Mode.
b. Select Enabled for Sync period, and then enter the synchronization period (time between start of resynchronizations).
Over period alerts are automatically generated if periodic synchronization does not complete within the specified synchronization
period.
c. If you do not want alerts generated, select Advanced options at the top of the screen. Then select Disabled for Over period alert.
d. If you do not want to automatically start the Remote Copy group, select No for Start group after completion .
Yes is the default.
4. Under Volume Pairs, click Add source volumes, and then follow the instructions on the screen.
a. For each source volume, click the edit icon, select the target volume, and then click Select.
5. Click Create.
6. To create additional asynchronous periodic Remote Copy groups, repeat these steps.
Creating an asynchronous periodic Remote Copy group 18

Configuring a Peer Persistence data replication solution
Configuring a Peer Persistence data replication solution 19

Creating a Classic Peer Persistence configuration
Classic HPE Peer Persistence is a high availability (HA) solution that uses Remote Copy synchronous mode and ensures that the same
data is on both storage systems. Although classic Peer Persistence provides both manual transparent failover (MTF) and automatic
transparent failover (ATF), set up the configuration to allow for ATF. ATF requires HPE Quorum Witness and the auto failover policy to
be enabled on the Remote Copy group.
Procedure
3. Create links and targets between the two storage systems:
TIP:
b. Click Ping.
7. Click Create.
8. If needed, create the Quorum Witness client configuration as described in Creating a Quorum Witness client configuration.
Creating a Classic Peer Persistence configuration 20

Creating a Classic Peer PersistenceRemote Copy group
With a classic Peer Persistence Remote Copy group, both source and target volumes share the same WWNs.
For a single host site, create a unidirectional configuration so that all the primary volumes are on the primary or local storage system. For
multisite host configuration, create a bidirectional configuration so that all the primary volumes associated to a particular host are on the
local storage system.
Procedure
a. Enter Group name.
b. Select Create automatically for Remote virtual volumes to create volumes with a common WWN.
NOTE:
Volumes with a common WWN are required.
c. Select the User CPG for the user volumes and the Copy CPG for the replicated copies (snapshots).
As a best practice, use the same common provisioning group (CPG) for both the user and copy CPG.
d. Hewlett Packard Enterprise recommends selecting Enable for Auto synchronize.
This policy automatically recovers and synchronizes the virtual volumes in the Remote Copy group if a failover occurs.
e. To automatically restart the Remote Copy group if links go down and then recover, select Auto recover.
4. To enter information for the Target system, follow the instructions on the screen.
a. Select Synchronous for Mode.
b. Select the User CPG for the user volumes and the Copy CPG for the replicated copies (snapshots).
As a best practice, use the same CPG for both the user and copy CPG.
c. If you do not want to automatically start the Remote Copy group, select No for Start group after completion .
Yes is the default.
5. Under High Availability Configuration, enter the following:
a. Select Peer Persistence.
b. For an automatic transparent failover (ATF) configuration, make sure HPE Quorum Witness is configured, and then select Auto
failover.
HPE Quorum Witness and Auto failover are required so that the Remote Copy group automatically fails over if a failure occurs.
7. Click Create.
8. For a multisite host configuration, create another group for bidirectional configuration.
More information
Remote Copy groups
Creating a Classic Peer PersistenceRemote Copy group 21

Configuring an Active Peer Persistence data replication solution
Configuring an Active Peer Persistence data replication solution 22

Creating an Active Peer Persistence Remote Copy configuration using the CLI
HPE Active Peer Persistence is a high availability (HA) solution that uses Remote Copy synchronous mode and ensures that the same
data is on both storage systems. Although Active Peer Persistence provides both manual transparent failover (MTF) and automatic
transparent failover (ATF), set up the configuration to allow for ATF. ATF requires HPE Quorum Witness and the auto failover policy to
be enabled on the Remote Copy group.
Procedure
1. To start HPE Remote Copy, issue the following command on both arrays:
cli%
startrcopy
2. Define the target on the first storage system by issuing the following command.
NOTE:
There is a maximum supported limit of two RCIP target connections per port.
For RCIP:
cli%
creatercopytarget <target_name> IP <N:S:P>:<link_IP_addr>
Where:
<target_name> —Name of the target system ( System2 ).
IP —Defines link as an IP link.
<N:S:P> —Location on the current system ( System1 ) that contains the IP connections to the secondary system,
expressed as node:slot:port .
<link_IP_addr> —Link IPv4 or IPv6 address for the corresponding port on the secondary system.
For RCFC:
cli%
creatercopytarget <target_name> FC <node_WWN> <N:S:P>:<WWN> <N:S:P>:<WWN>
Where:
FC —Defines link as an FC link.
<node_WWN> —WWN of the controller node on the target system.
<N:S:P>:<WWN> —Location on the current system ( System1 ) of the FC adapter port, expressed as
node:slot:port , and the WWN of the corresponding port on the target system.
3. Define the target on the second storage system by issuing the following command.
For RCIP:
cli%
Where:
Creating an Active Peer Persistence Remote Copy configuration using the CLI 23
<N:S:P> —Location on the current system ( System2 ) that contains the IP connections to the primary system,
<link_IP_addr> —Link IPv4 or IPv6 address for the corresponding port on the primary system.
For RCFC:
cli%
Where:
4. If needed, create the Quorum Witness client configuration.
Creating an Active Peer Persistence Remote Copy configuration using the CLI 24
Creating an Active Peer Persistence Remote Copy Group using CLI
With an Active Peer Persistence Remote Copy group, both source and target volumes share the same WWNs.
For a single host site, create a unidirectional configuration so that all the primary volumes are on the primary or local storage system. For
multisite host configuration, create a bidirectional configuration so that all the primary volumes associated to a particular host are on the
local storage system.
Procedure
1. To set up a Remote Copy group and autocreate target volumes, issue the following command on the primary storage system.
cli%
creatercopygroup -usr_cpg <cpg_name> <target_name>:<cpg_name> -snp_cpg <cpg_name>
<target_name>:<cpg_name> <group_name> <target_name>:sync
Where:
<group_name> —Name of the Remote Copy group.
<target_name> —Name of the target system.
-user_cpg <cpg_name> <target_name>:<cpg_name>... —The local user CPG and target user CPG that will be
used for volumes that are autocreated.
-snp_cpg <cpg_name> <target_name>:<cpg_name>... —The local snapshot CPG and target snapshot CPG
that will be used for volumes that are autocreated.
IMPORTANT: Hewlett Packard Enterprise recommends that you enable the Auto synchronize policy.
2. To automatically recover and synchronize the virtual volumes in the Remote Copy group if a failover occurs:
cli%
setrcopygroup pol auto_synchronize <group_name>
3. To enable Active Peer Persistence for the Remote Copy group, set the active_active policy on the group:
cli%
setrcopygroup pol active_active <group_name>
NOTE: Setting this policy is required before hosts can be admitted to the Remote Copy group. The group must be
specified as an Active Peer Persistence group before host proximities can be specified using the admitrcopy
host command.
4. Specify the hosts that are local (symmetric configuration) to both Primary and Secondary array for the Remote Copy group.
cli%
admitrcopyhost -proximity all <group_name> <host_name>...
5. Specify the hosts that are local to the Primary array for the Remote Copy group.
cli%
admitrcopyhost –proximity primary <group_name> <host_name>...
6. Specify the hosts that are local to the Secondary array for the Remote Copy group.
cli%
admitrcopyhost –proximity secondary <group_name> <host_name>...
Creating an Active Peer Persistence Remote Copy Group using CLI 25

7. Admit the VVs to the Remote Copy group.
cli%
admitrcopyvv -createvv <VV_name> <group_name> <target_name>:<sec_VV_name>
-createvv —The secondary volumes to be created automatically on the target using the CPG associated with the Remote
Copy group on that target.
<VV_name> —Specifies the name of the existing virtual volume to be admitted to an existing Remote Copy volume group that
was created with the creatercopygroup command.
<group_name> —Specifies the name of the existing Remote Copy volume group created with the creatercopygroup
command, to which the volume will be added.
<target_name>:<sec_VV_name> —The target name associated with the volume group and secondary volume name.
The system verifies that the VV exports are to the same hosts defined in the Remote Copy group host sets. The corresponding VVs
are automatically created on the secondary system. If the Remote Copy group is started, the VVs will also be automatically exported
on the secondary.
8. Start the Remote Copy group if not already started. If you did not previously export the volumes on the secondary during VV admit,
export them now.
NOTE:
Depending on the Host OS type, a device rescan might be required to account for the newly exported secondary
volumes.
Creating an Active Peer Persistence Remote Copy Group using CLI 26

Creating an Active Peer Persistence Remote Copy configuration using SSMC
Remote Copy with HPE Active Peer Persistence allows simultaneous host I/O to both the primary and secondary storage systems in a
Remote Copy synchronous configuration.
Procedure
3. Create links and targets between the primary storage system and each secondary storage system.
To add systems, click +Add a system and then choose the system from the drop-down list.
TIP:
c. To use the same port to connect two systems, select the port again and then select Add a link to this port in the Select Action
dialog box. Then, click Continue.
d. If you selected an incorrect link, select the port and then select Remove link in the Select Action dialog box. Then, click Continue.
b. Click Ping.
7. Click Create.
Creating an Active Peer Persistence Remote Copy configuration using SSMC 27

Creating an Active Peer PersistenceRemote Copy group using SSMC
With an Active Peer Persistence Remote Copy group, both source and target volumes use the same WWNs.
Procedure
NOTE:
4. To enter information for the Target system, follow the instructions on the screen.
c. If you do not want to automatically start the Remote Copy group, select No for Start group after completion .
Yes is the default.
5. Under High Availability Configuration, select Active Peer Persistence.
By default, Auto failover, Auto synchronize, and Auto recover are automatically enabled. Auto failover is required for Active Peer
Persistence and cannot be disabled. Auto synchronize and Auto recover are recommended for Active Peer Persistence.
7. Under Host, click Add Hosts.
8. Select Host or Host Set.
NOTE:
Adding a host set to the group, sets the same proximity for all the hosts in the host set.
a. From the Host Name list or Host Set list, select one or more Hosts or Host Sets.
b. From the Proximity option drop-down, select an option ( All, Primary, or Secondary) for each host in the group.
For symmetric host access to both primary and target arrays, select All.
For a source system local to the host, select Primary.
For a source system remote to the host, select Secondary.
9. Click Add. In the Create Group host panel display, review your selections and adjust any selections as needed. Once confirmed, click
Create.
10. Verify that the virtual volumes are exported from both the primary array and secondary array to the hosts. Verify that the correct
paths are displayed for the hosts. If you added a volume that is not exported to the host, use the Export virtual volume dialog.
Creating an Active Peer PersistenceRemote Copy group using SSMC 28
Creating an Active Peer PersistenceRemote Copy group using SSMC 29
Configuring an Active Sync Replication solution
Configuring an Active Sync Replication solution 30

Creating an Active Sync Replication Remote Copy configuration using the CLI
HPE Active Sync Replication is a Remote Copy synchronous mode solution that adds some automatic failover capabilities to a basic
synchronous replication configuration. Synchronous mode ensures that the same data is on both storage systems.
Active Sync Replication provides both manual transparent failover (MTF) and automatic failover. Automatic failover requires HPE
Quorum Witness and enabling the auto failover policy on the Remote Copy group.
Active Sync Replication differs from Active Peer Persistence in that hosts are not cross-connected between the synchronous Remote
Copy array pair. The Active Sync Replication configuration does not offer the level of High Availability (HA) nor automatic transparent
failover possibilities of Active Peer Persistence. The connected stretched host cluster solution must be configured to accommodate array
failover scenarios to maintain access to host cluster resources.
Procedure
1. To start HPE Remote Copy, issue the following command on both arrays:
cli%
startrcopy
2. Define the target on the first storage system by issuing the following command.
NOTE:
There is a maximum supported limit of two RCIP target connections per port.
For RCIP:
cli%
Where:
<N:S:P> —Location on the current system ( System1 ) that contains the IP connections to the secondary system,
<link_IP_addr> —Link IPv4 or IPv6 address for the corresponding port on the secondary system.
For RCFC:
cli%
Where:
3. Define the target on the second storage system by issuing the following command.
For RCIP:
cli%
Where:
Creating an Active Sync Replication Remote Copy configuration using the CLI 31
<N:S:P> —Location on the current system ( System2 ) that contains the IP connections to the target system, expressed
as node:slot:port .
<link_IP_addr> —Link IPv4 or IPv6 address for the corresponding port on the target system.
For RCFC:
cli%
Where:
4. If needed, create the Quorum Witness client configuration.
Creating an Active Sync Replication Remote Copy configuration using the CLI 32
Creating an Active Sync Replication Remote Copy Group using the CLI
With an Active Sync Replication Remote Copy group, both source and target volumes share the same WWNs. Create a bidirectional
configuration so that all the primary volumes associated to a particular host are on the storage system local to the particular host.
Procedure
1. To set up a Remote Copy group and autocreate target volumes, issue the following command on the primary storage system.
cli%
creatercopygroup -usr_cpg <cpg_name> <target_name>:<cpg_name> -snp_cpg <cpg_name>
<target_name>:<cpg_name> <group_name> <target_name>:sync
Where:
<group_name> —Name of the Remote Copy group.
<target_name> —Name of the target system.
-user_cpg <cpg_name> <target_name>:<cpg_name>... —The local user CPG and target user CPG that will be
used for volumes that are autocreated.
-snp_cpg <cpg_name> <target_name>:<cpg_name>... —The local snapshot CPG and target snapshot CPG
that will be used for volumes that are autocreated.
2. To enable Active Sync Replication for the Remote Copy group, set the active_active policy on the group:
cli%
setrcopygroup pol active_active <group_name>
NOTE: Setting the active_active policy is required before hosts can be admitted to the Remote Copy group. The
group must be specified for use as an Active Sync Replication group by setting the active_active policy before host
proximities can be specified using the admitrcopy host command. Host proximities should be set to all for
Active Sync Replication configurations.
NOTE: The path_management, auto_recover, and auto_synchronize policies are enabled by default as part of
enabling the active_active policy. The path_management policy, however, does not show up as one of the enabled
policies with the Remote Copy group information.
3. Specify the hosts the Remote Copy group along with their proximity settings.
cli%
admitrcopyhost -proximity all <group_name> <host_name>...
NOTE: You must create host definitions on both arrays in the array pair at each site for all of the hosts, even though
only the hosts local to the site are connected to an array.
4. Admit the VVs to the Remote Copy group.
cli%
admitrcopyvv -createvv <VV_name> <group_name> <target_name>:<sec_VV_name>
-createvv —The secondary volumes to be created automatically on the target using the CPG associated with the Remote
Copy group on that target.
<VV_name> —Specifies the name of the existing virtual volume to be admitted to an existing Remote Copy volume group that
was created with the creatercopygroup command.
<group_name> —Specifies the name of the existing Remote Copy volume group created with the creatercopygroup
command, to which the volume will be added.
Creating an Active Sync Replication Remote Copy Group using the CLI 33
<target_name>:<sec_VV_name> —The target name associated with the volume group and secondary volume name.
The system verifies that the VV exports are to the same hosts defined in the Remote Copy group host sets. The corresponding VVs
are automatically created on the secondary system. If the Remote Copy group is started, the VVs will also be automatically exported
on the secondary.
5. Start the Remote Copy group if not already started. If you did not previously export the volumes on the secondary during VV admit,
export them now.
NOTE:
Depending on the Host OS type, a device rescan might be required to account for the newly exported secondary
volumes.
Creating an Active Sync Replication Remote Copy Group using the CLI 34
Configuring a synchronous long distance data replication solution
Configuring a synchronous long distance data replication solution 35

Creating a synchronous long distance configuration
In a synchronous long distance (SLD) configuration, Remote Copy groups from the primary system are replicated to two separate target
systems simultaneously. Data replicates to one target in synchronous mode and to the second in asynchronous periodic mode.
For example, System1 is the primary system and System2 and System3 are the secondary storage systems.
Procedure
3. Create links and targets between storage systems:
For the third system, click +Add a system and then choose the system from the drop-down list.
TIP:
b. Click Ping.
7. Click Create.
Creating a synchronous long distance configuration 36

Creating a synchronous long distance Remote Copy group
With a synchronous long distance (SLD) Remote Copy group, the volumes within the group are replicated to two separate target systems
simultaneously. Data replicates to one target in synchronous mode and to the second in asynchronous periodic mode.
In this example, create a group with synchronous mode between System1 and System2 , and periodic mode between System1
and System3 .
Prerequisites
Procedure
3. To enter information for the Source system ( System1 ), follow the instructions on the screen.
Auto synchronize.
IMPORTANT:
4. Enable Additional target.
5. To enter information for the first Target system ( System2 ), follow the instructions on the screen.
Yes is the default.
6. To enter information for the Second Target system ( System3 ), follow the instructions on the screen.
period.
Yes is the default.
8. Click Create.
Creating a synchronous long distance Remote Copy group 37
9. Create additional Remote Copy groups between the systems.
More information
Remote Copy groups
Creating a synchronous long distance Remote Copy group 38

Configuring a three data center Peer Persistence data replication solution
Configuring a three data center Peer Persistence data replication solution 39

Creating a three data center Peer Persistence configuration
Three data center Peer Persistence (3DC PP) is a combination of a high availability Remote Copy configuration (Peer Persistence) and a
synchronous long distance configuration (SLD).
3DC PP is supported in HPE Primera OS 4.1 and later.
For example, System1 and System2 are set up in a 1-to-1 Peer Persistence configuration. System3 is the tertiary system.
Procedure
3. Create links and targets between storage systems:
For the third system, click +Add a system and then choose the system from the drop-down list.
TIP:
b. Click Ping.
7. Click Create.
Creating a three data center Peer Persistence configuration 40

Creating a three data center Peer Persistence Remote Copy group
A three data center Peer Persistence (3DC PP) group is the same as a Peer Persistence group with a third storage system. Synchronous
targets are between the primary and secondary systems and asynchronous periodic targets are between the primary or secondary
systems and the tertiary system. Both source and synchronous target volumes share the same WWNs.
In this example, create a Peer Persistence group between System1 and System2 , and periodic mode between System1 and
System3 .
Procedure
3. To enter information for the Source system ( System1 ), follow the instructions on the screen.
NOTE:
4. Enable Additional target.
5. To enter information for the first Target system ( System2 ), follow the instructions on the screen.
6. To enter information for the Second Target system ( System3 ), follow the instructions on the screen.
period.
Yes is the default.
7. Under High Availability Configuration, select Multi-target Peer Persistence.
Auto failover is automatically selected. HPE Quorum Witness and Auto failover are required so that the Remote Copy group
automatically fails over if a failure occurs.
8. Click Create.
9. Create additional Remote Copy groups between the systems.
More information
Remote Copy groups
Creating a three data center Peer Persistence Remote Copy group 41

Creating a three data center Peer Persistence Remote Copy group 42

Configuring a one-to-many data replication solution
Configuring a one-to-many data replication solution 43

Creating a one-to-many Remote Copy configuration
A one-to-many (1-to-N) Remote Copy configuration replicates data from one storage system to up to four other storage systems.
Procedure
3. Create links and targets between the primary storage system and each secondary storage system.
TIP:
b. Click Ping.
7. Click Create.
Creating a one-to-many Remote Copy configuration 44

Creating synchronous or periodic Remote Copy groups for 1-to-N configurations
Create either a synchronous or periodic Remote Copy group for the primary storage system and each secondary storage system. For
bidirectional replication, create a Remote Copy group from a secondary storage system to the primary storage system.
Prerequisites
Procedure
Auto synchronize.
IMPORTANT:
Yes is the default.
period.
Yes is the default.
7. Click Create.
8. To create additional Remote Copy groups, repeat these steps.
More information
Creating synchronous or periodic Remote Copy groups for 1-to-N configurations 45

Remote Copy groups
Creating synchronous or periodic Remote Copy groups for 1-to-N configurations 46

Configuring a many-to-one data replication solution
Configuring a many-to-one data replication solution 47

Creating a many-to-one Remote Copy configuration
A many-to-one (N-to-1) Remote Copy configuration replicates data from up to four storage systems to one other storage system.
Procedure
3. Create links and targets between each primary storage system and the secondary storage system.
TIP:
b. Click Ping.
7. Click Create.
Creating a many-to-one Remote Copy configuration 48

Creating synchronous or periodic Remote Copy groups for N-to-1 configurations
Create either a synchronous or periodic Remote Copy group for each primary storage system and the secondary storage system. For
bidirectional configuration, create a Remote Copy group from the secondary storage system to a primary storage system.
Prerequisites
Procedure
Auto synchronize.
IMPORTANT:
Yes is the default.
period.
Yes is the default.
7. Click Create.
8. To create additional Remote Copy groups, repeat these steps.
More information
Creating synchronous or periodic Remote Copy groups for N-to-1 configurations 49

Remote Copy groups
Creating synchronous or periodic Remote Copy groups for N-to-1 configurations 50

Managing a Remote Copy group
Managing a Remote Copy group 51

Starting a Remote Copy group
Starting a Remote Copy group initiates the replication process between the source and target volumes in the group. You might manually
start a group if:
A Remote Copy group was not set to start automatically when it was created.
A Remote Copy group was stopped and did not restart. For example, if Auto recover is disabled and a link goes down, a manual
restart is required after the link is back up.
Procedure
2. In the list pane, select the Remote Copy group, and then select Actions > Start.
3. To start a group with multiple targets, select the target system from the drop-down list.
The default is All.
4. Click Start to confirm.
Starting a Remote Copy group 52

Stopping a Remote Copy group
Stopping a Remote Copy group stops the replication process between the source and target volumes in the group. You might manually
stop a Remote Copy group before changing the volumes in the group.
Procedure
2. In the list pane, select the Remote Copy group, and then select Actions > Stop.
3. To stop a group with multiple targets, select the target system from the drop-down list, and then click Stop.
The default is All.
4. To confirm, select the check box about understanding the implications, and then click Yes, stop.
Stopping a Remote Copy group 53

Deleting a Remote Copy group
Deleting a Remote Copy group removes all the associations configured in the specified group, the group name, and any Remote Copy
synchronization snapshots affiliated with the volumes in the group.
The virtual volumes in the group are not deleted, but they are no longer associated with the Remote Copy group.
NOTE:
Remote Copy automatically stops the group before deleting it.
Procedure
2. In the list pane, select the Remote Copy group, and then select Actions > Delete.
3. Click Delete again to confirm.
Deleting a Remote Copy group 54

Adding existing virtual volumes to an existing Remote Copy group
Procedure
2. In the list pane, select the Remote Copy group, and then select Actions > Edit.
3. Navigate to Volume Pairs, and then click Add source volumes.
4. Select the existing volumes to add to the group, and then click Add.
5. If you are creating virtual volumes on the target system manually, click the edit icon and select the target volume for each source
volume you add.
6. Click OK.
Adding existing virtual volumes to an existing Remote Copy group 55

Creating virtual volumes for an existing Remote Copy group
Procedure
1. On the HPE SSMC main menu, select Virtual Volumes under BLOCK PERSONA.
2. Click + Create virtual volume or select Actions > Create, and then follow the instructions on the screen.
3. (Optional) To create several volumes in the same CPG of the same size:
a. Under Protection And Additional Settings, expand Volume.
b. Enter the Number of volumes.
4. Under Protection And Additional Settings, expand Remote Copy Group.
5. Select the name of the group.
6. Click Create.
Creating virtual volumes for an existing Remote Copy group 56

Removing virtual volumes from an existing Remote Copy group
Procedure
3. Navigate to Volume Pairs, and then click X next to each volume you want to remove from the Remote Copy group.
4. Click OK.
Both the source volume and the replicated volume are removed.
Removing virtual volumes from an existing Remote Copy group 57

Reversing the direction of data flow in a Remote Copy group
Reverse the direction of data flow for non-Peer Persistence configurations. You can reverse direction for a single or multiple Remote
Copy groups. Multiple groups must have the same target.
NOTE:
To reverse the direction of data flow for a classic Peer Persistence, Active Peer Persistence, or Active Sync Replication
Remote Copy group, see Performing a transparent switchover for Active Sync Replication, Active Peer Persistence or
classic Peer Persistence. To reverse the direction of data flow for a three data center Peer Persistence (3DC PP) group,
see Performing a switchover for 3DC PP.
Prerequisites
The DR state is Normal.
Procedure
2. Stop the Remote Copy group.
3. In the list pane, select the Remote Copy group, and then select Actions > Reverse.
4. To reverse a group with multiple targets, select the target system from the drop-down list, and then click Reverse.
5. To confirm the reverse, select the check box about understanding the implications, and then click Yes, reverse.
Reversing the direction of data flow in a Remote Copy group 58

Performing a transparent switchover for Active Sync Replication, Active Peer Persistence
or classic Peer Persistence
Prerequisites
The source and target Active Sync replication, Active Peer Persistence or classic Peer Persistence groups are in synchronous mode.
The source and target Active Sync replication, Active Peer Persistence or classic Peer Persistence groups are synchronized.
All volumes in the Active Sync replication, Active Peer Persistence or classic Peer Persistence groups have the same WWN.
All volumes have been exported to the same host sets from both storage systems.
The DR state is Normal in the Health section of the Remote Copy groups page.
IMPORTANT: To perform this procedure for Active Sync Replication configurations, you must use the CLI. For details,
see the Note after step 4. You can also use the CLI to perform this procedure for Active Peer Persistence and Peer
Persistence configurations.
Procedure
2. In the list pane, select the Active Peer Persistence or classic Peer Persistence group, and then select Actions > Switchover.
3. Click Switchover.
4. To confirm the switchover operation, select the check box about understanding the implications, and then click Yes, switchover.
NOTE: To perform this procedure using the CLI:

To failover or switch to the secondary system when the Remote Copy target links are up and the group is
synchronized, use the switchover command on the primary system to specify the synchronous target:
cli% setrcopygroup switchover –t <sync target>
To failover to the secondary system when the Remote Copy target links are down, use the failover command to
switchover. Issue a failover from the secondary system by specifying the synchronous target:
cli% setrcopygroup failover –t <sync target>
Performing a transparent switchover for Active Sync Replication, Active Peer Persistence or classic Peer Persistence 59
Performing a switchover for 3DC PP
A switchover changes the roles and replication direction of the groups from primary to secondary without impacting the host I/O.
Perform a switchover if service or maintenance must be performed on the source system in the configuration.
Prerequisites
The three data center Peer Persistence (3DC PP) group has a source and target in synchronous mode.
TIP:
HPE SSMC automatically selects the storage system with the synchronous target.
The volumes in the source and target are synchronized.
All volumes in the source and target have the same WWN.
All volumes were exported to the same host from both storage systems.
The DR state is Normal in the Health section of the Remote Copy groups page.
Procedure
2. In the list pane, select the 3DC PP group, and then select Actions > Switchover.
3. Click Switchover.
4. To confirm the switchover operation, select the check box about understanding the implications, and then click Yes, switchover.
Performing a switchover for 3DC PP 60

Changing the policies of a non-Peer Persistence Remote Copy group
The Policies section of the Overview panel displays the current policies for the Remote Copy group.
Procedure
3. Change any of the following policies in the Source section:
a. Auto synchronize - Select Enable to automatically synchronize the group after performing a failover.
In synchronous long distance (SLD), this policy applies to the volumes in the synchronous targets only.
b. Auto recover - Select Enable to automatically restart the group if Remote Copy links go down and then recover.
c. Over period alert - Select Enable to generate alerts when synchronization between periodic Remote Copy groups does not
complete within the specified synchronization period.
The Advanced option at the top of the screen must be selected for this policy to display.
4. Click OK.
Changing the policies of a non-Peer Persistence Remote Copy group 61

Changing the policies of an Active Peer Persistence, Classic Peer Persistence, or 3DC PP
group
The Policies section of the Overview panel displays the current policies for the Active Peer Persistence, classic Peer Persistence, or 3DC
PP group.
Procedure
3. Change any or all the following policies in the Source section:
a. Auto synchronize - Select Enable to automatically synchronize the group after performing a failover.
In three data center Peer Persistence (3DC PP) configurations, this policy applies to the volumes in the synchronous targets only.
b. Auto recover - Select Enable to automatically restart the group if Remote Copy links go down and then recover.
c. Over period alert - Select Enable to generate alerts when synchronization between periodic Remote Copy groups does not
complete within the specified synchronization period.
The Advanced option at the top of the screen must be selected for this policy to display. This policy only applies to 3DC PP.
4. Change any of the High Availability-related policies:
a. Active Peer Persistence - Select to enable Active Peer Persistence.
b. Multi-target Peer Persistence - Select to enable 3DC PP.
c. Peer Persistence - Select to enable classic Peer Persistence.
d. Auto failover - Select to automatically fail over a Remote Copy group if a failure occurs. If Multi-target Peer Persistence is
selected, auto failover is automatically selected.
Auto failover and Quorum Witness are required for an automatic transparent failover (ATF) configuration.
5. Click OK.
Changing the policies of an Active Peer Persistence, Classic Peer Persistence, or 3DC PP group 62
Changing the replication mode for a Remote Copy group
You can change the replication mode from synchronous to periodic or from periodic to synchronous in a 1-to-1 configuration.
NOTE:
If multiple Remote Copy groups have the same target system, the mode must be the same for all the groups. Stop all but
one of the groups before you begin to change the replication mode in each group.
Procedure
NOTE: If you are changing the replication mode of a Peer Persistence Remote Copy group from synchronous to
periodic, ensure that the Peer Persistence volumes on the secondary system have been unexported.
3. In the Target section, change the Mode.
4. Click OK.
Changing the replication mode for a Remote Copy group 63

Growing the size of virtual volumes in a Remote Copy group
Procedure
1. Stop the Remote Copy group.
2. On the HPE SSMC main menu, select Virtual Volumes under BLOCK PERSONA.
3. Select the volume in the list pane, and then select Actions > Edit.
4. Change the size, and then click OK.
5. Start the Remote Copy group.
Growing the size of virtual volumes in a Remote Copy group 64

Manually synchronizing a Remote Copy group
Manually synchronize a Remote Copy group if:
You did not select Initial Sync when you created the Remote Copy group.
The auto synchronize policy on the group is disabled and a failover occurs. Wait until the system completely recovers and the links
are re-established before synchronizing.
The auto synchronize policy on the group is disabled and you perform a switch over.
Procedure
2. In the list pane, select the Remote Copy group, and then select Actions > Sync.
3. To synchronize a group on one target when you have multiple targets, select the target system from the drop-down list.
The default is All.
4. Click Sync to proceed.
5. To view the synchronization activity:
a. Select the Activity view from the drop-down list.
b. Expand the Remote Copy Sync activity.
The start and end time for the synchronization and the duration displays.
6. To view the Sync State, Sync Percent, and the Last Synced date and time, select the Volume Pairs view.
Manually synchronizing a Remote Copy group 65

Managing a Remote Copy configuration
Managing a Remote Copy configuration 66

Adding links to an existing Remote Copy target
Add a link pair (a port on each system) to an existing target.
Procedure
2. Choose a configuration from the list, and then click Actions > Add Links.
3. For Targets, select an existing target where you want to add the links.
4. Select a port on each system.
NOTE:
As a best practice, ensure all Remote Copy ports used by a target operate at the same speed. Consider checking the
Service Level Agreement for the network provider for minimum bandwidth.
5. (Optional) Update port settings such as the gateway address, Maximum Transmission Units (MTU), or configured rate:
a. Under Port Pairs, click the edit icon next to the port you want to update.
b. Make the necessary changes, and then click OK.
6. (Optional) Test connectivity between systems:
a. Under Port Pairs, click the edit icon next to the port you want to test.
b. Click Ping.
7. Click OK.
Adding links to an existing Remote Copy target 67

Removing links from an existing Remote Copy target
Removing a link pair (a port on each system) from a target can reduce availability or disrupt remote replication in the Remote Copy
configuration. You cannot remove the last remaining link pair for a target if a Remote Copy group is using the target. To remove all link
pairs from a target, see Removing a target from a Remote Copy configuration.
Procedure
2. Choose a configuration from the list, and then click Actions > Remove Links.
3. Click to highlight the link pair and then click Remove.
4. To confirm, select the check box about understanding the implications, and then click Yes, remove.
Removing links from an existing Remote Copy target 68

Adding a target to a Remote Copy configuration
A target is a set of link port pairs (a port on each system) defined between two storage systems. You cannot add a target in a
synchronous long distance (SLD) or three data center Peer Persistence (3DC PP) configuration.
Procedure
2. In the list pane, select a Remote Copy configuration, and then select Actions > Add Target.
3. Create a link by clicking a port on the target storage system, and then click a corresponding port on the source storage system.
4. Click Add.
Adding a target to a Remote Copy configuration 69

Removing a target from a Remote Copy configuration
A target is a set of link port pairs (a port on each system) in a Remote Copy configuration. When removing a target, all link port pairs
defined for the target and any Remote Copy groups on the target are also removed.
IMPORTANT:
Removing a target disrupts replication and clears any HPE Quorum Witness configurations. If the Remote Copy
configuration contains only one set of targets, removing the target removes the entire configuration.
Procedure
2. Choose a configuration from the list and then click Actions > Remove Target.
3. With multiple targets, select the target pair that you want to remove.
4. Click Remove.
5. To confirm, select the check box about understanding the implications, and then click Yes, remove.
Removing a target from a Remote Copy configuration 70

Check RCIP link throughput and latency
The client-server program checkrclink can be used to check throughput and latency. checkrclink is used interchangeably on System1 and
System2. checkrclink startserver is used on one system and checkrclink startclient is used on the other
system.
Prerequisites
Firewall settings must allow the Remote Copy systems access to TCP port 5001 (default).
Procedure
1. Ensure that the storage systems for which you are checking links are not displaying signs of saturation.
2. Issue the following command on a system in the Remote Copy pair (for example, System2 ):
cli%
checkrclink startserver [options] <N:S:P> <dest_addr> [<port>]
Where:
The option , -time <sec> —Time in seconds for the test to run. Use an integer from 300 to 172800. For example, if the
command is checkrclink startserver -time 172800 0:2:1 , the Remote Copy link check will run for 172,800
seconds (48 hours). If no time is specified, the default is 172800.
<N:S:P> —Interface from which to check the link, expressed as node:slot:port
<dest_addr> —IP address on the peer system ( System1 )
[<port>] —Optional server TCP port
3. On the other system in the Remote Copy pair (for example, System1 ), issue the following command:
cli%
checkrclink startclient <N:S:P> <dest_addr> <time> [port]
Where:
<N:S:P> —Interface from which to check the link, expressed as node:slot:port
<dest_addr> —IP address on the peer system ( System2 ) for which you are checking the link.
<time> —The number of seconds for the test to run, using an integer from 10 seconds to 172800 (10 seconds to 48 hours).
[<port>] —The TCP port specified in step 2, if any. The port should be specified for FC interfaces.
4. Review the maximum MTU for the specified RCIP links.
If the Max MTU value is 1500 bytes, you cannot increase MTU.
If the Max MTU is 9,000 bytes, you might be able to increase MTU. Check with your network administrator to determine if an
MTU greater than 1500 can be used.
5. Issue the following command on System2 (the system on which you issued the startserver command):
cli%
checkrclink stopserver <N:S:P>
6. Repeat this process for each link in each system.
Check RCIP link throughput and latency 71

Editing throughput and performance tuning on an RCIP target
Procedure
1. Stop all Remote Copy groups using the target.
3. In the list pane, select a Remote Copy configuration, and then select Actions > Edit Target.
4. Click Advanced options.
Link Characteristics displays.
5. (Optional) Change Throughput:
a. Click Enable and enter the maximum throughput limit and size unit within the allowed range.
b. Or, click Disable if you want to remove throughput limits.
6. (Optional) Change Performance tuning:
a. Click Automatic for the system to automatically tune performance.
b. Or, click User defined to manually specify the values or restore to default values.
c. Enter your own bandwidth and latency values, or click Restore default values to allow the system to set the values.
7. Click OK.
The system might show a degraded state momentarily while the changes are being made.
8. Start all Remote Copy groups using the target.
Editing throughput and performance tuning on an RCIP target 72

Editing the name of a Remote Copy target
Changing the Remote Copy target name does not change the name of the storage system.
Procedure
1. Stop all Remote Copy groups using the target.
3. In the list pane, select a Remote Copy configuration, and then select Actions > Edit Target.
4. Select the storage system and enter a new target name.
5. (Optional) Select the Targets view from the drop-down list to view the updated target name.
The updated target name displays in the Name field.
6. Click OK.
7. Start all Remote Copy groups using the target.
Editing the name of a Remote Copy target 73

Converting a Peer Persistence configuration to an Active Peer Persistence configuration
using SSMC
Prerequisites
The virtual volumes associated with the Peer Persistence group are exported to the same host on both storage systems.
The Host I/O path for the primary system Remote Copy group is in Active state and the I/O path for the secondary system is in
Standby state.
Procedure
2. Select the classic Peer Persistence configuration to be converted, and then select Actions > Edit.
3. Under High Availability Configuration, select Active Peer Persistence. To convert to the Active Peer Persistence configuration, click
OK.
If you want to view changes for the converted configuration use:

Remote Copy overview dialog which displays Active Peer Persistence in the Policies section.
Hosts section of the Remote Copy host view drop-down which displays Host, Host OS, Proximity, Local System, and Remote
System.
TIP:
To view changes for the converted configuration, you can select the Remote Copy overview dialog which displays
Active Peer Persistence in the Policies section. The Remote Copy host view drop-down also displays Host, Host OS,
Proximity, Local System, and Remote System.
4. After the conversion completes, the default system host configuration is asymmetric. To achieve the full benefits of Active Peer
Persistence, HPE recommends changing the host configuration to localized or symmetric. To change it, select the Remote Copy
group, and then select Actions > Edit.
5. Scroll to the Hosts section. From the Proximity drop-down list, select one of the following:
For a symmetric host configuration, select All.
For a localized host configuration, select Secondary.
6. Click OK.
Converting a Peer Persistence configuration to an Active Peer Persistence configuration using SSMC 74
Converting a Classic Peer Persistence Remote Copy configuration to Active Peer
Persistence using the CLI
Prerequisites
Fully operational classic Peer Persistence Remote Copy Group.
Remote Copy Group is in a stopped or started state.
Procedure
1. Set the Remote Copy Group policy as follows.
setrcopygroup pol active_active < group_name>
The host information from all Virtual Volumes (VVs) in the group is gathered and the host sets are automatically created.
2. Start the Remote Copy Group if not already started.
3. Export secondary VVs as needed.
IMPORTANT: The default system host configuration is an Asymmetric configuration. To achieve the full benefits of
Active Peer Persistence, Hewlett Packard Enterprise recommends changing to a Symmetric or Localized
configuration during or after the conversion to match the actual hosts' proximity to the arrays.
4. After converting the classic Peer Persistence configuration to an Active Peer Persistence configuration, issue the appropriate
commands to specify host proximity so it matches your environment.
To change to a Symmetric configuration, issue this command on the primary system for all hosts used by the VVs in the RC
Group.
admitrcopyhost –proximity all <group_name > <host_name>
To change to a Localized configuration, issue this command on the primary system for all hosts with proximity to the secondary
system:
admitrcopyhost –proximity secondary <group_name > <host_name>
Converting a Classic Peer Persistence Remote Copy configuration to Active Peer Persistence using the CLI 75
Converting an Active Peer Persistence configuration back to Classic Peer Persistence using
CLI
Prerequisites
Fully operational Active Peer Persistence Remote Copy Group.
Remote Copy Group is in a stopped or started state.
Procedure
1. Set the Remote Copy Group policy to Peer Persistence if not already set.
a. setrcopygroup pol path_management < group_name>
b. setrcopygroup pol auto_failover < group_name>
2. Disable the active_active Remote Copy Group Policy.

setrcopygroup pol no_active_active < group_name>
The host sets for the group are automatically removed and the configuration changes to asymmetric. If the Remote Copy Group is
started, all ALUA Active/Non-Optimized IO paths switch to Standby .
3. Start the Remote Copy Group if not already started.
Converting an Active Peer Persistence configuration back to Classic Peer Persistence using CLI 76
Converting an existing Peer Persistence configuration to a 3DC PP configuration
A three data center Peer Persistence (3DC PP) configuration provides synchronous replication over a metro distance and asynchronous
periodic replication over a continental distance.
For example, SystemA and SystemB are set up in a 1-to-1 Peer Persistence configuration. SystemC is the tertiary system.
Prerequisites
Peer Persistence volumes on the secondary storage system have been unexported before changing the replication mode from
synchronous to periodic.
The tertiary site has met the HPE Primera Remote Copy requirements, the ports have been physically cabled, and the links have been
configured correctly.
Procedure
2. Select the existing classic Peer Persistence configuration.
a. Select Actions > Edit.
b. Check if the Peer Persistence volumes are exported to the same host. Unexport any volumes on the secondary system prior to
changing the replication mode from synchronous to periodic.
3. Click +Add a system and then choose the tertiary system from the drop-down list.
4. Create links and targets between the tertiary system and the other two systems.
a. Select a minimum of two RCIP or RCFC ports between each system.
TIP:
b. To use the same port to connect two systems, select the port again and then select Add a link to the port in the Select Actions
c. If you selected an incorrect link, select the port and then select Remove link in the Select Actions dialog box. Then, click Continue.
5. Create a 3DC PP Remote Copy group .
Converting an existing Peer Persistence configuration to a 3DC PP configuration 77

Converting an existing SLD configuration to a 3DC PP configuration
Change the synchronous long distance (SLD) configuration so that the synchronous targets on the primary and secondary systems are
configured as a 1-to-1 Peer Persistence.
For example, SystemA is the primary system and SystemB and SystemC are the secondary storage systems. SystemB is the
synchronous target and SystemC is the periodic target. SystemA and SystemB will be converted to a Peer Persistence pair with
SystemC as the tertiary storage system.
Prerequisites
HPE Quorum Witness software is installed. See the Installing and updating HPE Quorum Witness for HPE Primera and HPE 3PAR on
Host I/O paths are connected to each storage system such that the source and target volumes are visible to the host.
Procedure
2. Select the existing SLD configuration, and then select Actions > Configure Quroum Witness.
3. Select the System pair that contains the synchronous replication. For example, SystemA and SystemB .
The selected system pair must contain only synchronous Remote Copy groups.
4. Enter the following information:
a. Enter the IP address or the FQDN of the Quorum Witness server.
b. Select Yes for Start.
c. Select Enabled for Secure Connection.
d. Enter the configured port number of the QW server.
Use the default port 8443 if an alternative port was not set up.
5. Click Configure.
After a few minutes, the Quorum Witness client is configured.
6. To verify that the Quorum Witness client configuration is added and started, select the Targets view.
The QW Server field displays the IP address or the FQDN of the Quorum Witness server. The QW Status field displays Started.
8. Select an SLD Remote Copy group, and then select Actions > Edit.
9. Scroll to High Availability Configuration and select Multi-target Peer Persistence.
10. If the remote volumes do not have the same WWN as the source volumes, a dialog box displays. Click Yes, autoset WWN.
11. Click OK.
12. Repeat steps 8-11 for each SLD Remote Copy group you want to convert.
Converting an existing SLD configuration to a 3DC PP configuration 78

Adding storage systems to a one-to-one configuration creating a one-to-many
configuration
A one-to-many (1-to-N) Remote Copy configuration replicates data from one storage system to up to four other storage systems.
Procedure
2. Select the existing configuration, and then select Actions > Add Target.
3. Create links and targets between the primary storage system and each secondary storage system:
a. Select the secondary systems from the drop-down list.
TIP:
b. Click Ping.
7. Click Add.
8. Create Remote Copy groups .
Adding storage systems to a one-to-one configuration creating a one-to-many configuration 79

Adding storage systems to a one-to-one configuration creating a many-to-one
configuration
A many-to-one (N-to-1) Remote Copy configuration replicates data from up to four storage systems to one other storage system.
Procedure
2. Select the existing configuration. To add a target to the existing configuration, select Actions > Add Target.
3. Create links and targets between the primary storage systems and the secondary storage system:
a. Select the primary systems from the drop-down list.
TIP:
b. Click Ping.
7. Click Add.
8. Create Remote Copy groups .
Adding storage systems to a one-to-one configuration creating a many-to-one configuration 80

Reference
Reference 81
Remote Copy port on a controller node
The rear view of a controller node contains the ports for Remote Copy. The controller node has two built-in Ethernet ports. For HPE
Primera OS 4.2 or earlier, only the Slot-1 port is permitted for Remote Copy over IP (RCIP) use. For HPE Primera OS 4.3 or later, both
built-in Ethernet ports can be used for RCIP replication. The built-in RCIP ports have 10Gb optical SFPs installed. The ports do not
support 10-base T, RJ45, CAT5, or CAT6.
Remote Copy over FC (RCFC) ports are on the host adapters installed on the controller nodes. Any available FC port can be used for
RCFC. The FC ports are in Slot-3 and Slot-4 on all models. The HPE Primera 650 and 670 controller nodes also have FC ports in Slot-5.
The following figure shows, as an example, the RCIP and RCFC ports in an HPE Primera 630 controller node.
Figure 1: Remote Copy port in an HPE Primera 630 controller node
Item Port functionality Port description
1 FC ports identified for RCFC 16Gb or 32Gb FC ports for Remote Copy FC connection
2 Ethernet ports for RCIP 10 GbE Ethernet onboard ports for Remote Copy IP connection
Remote Copy port on a controller node 82

Quorum Witness and automatic transparent failover (ATF)
Quorum Witness is required for automatic transparent failover on a Peer Persistence configuration. The storage systems in a classic Peer
Persistence, Active Peer Persistence, Active Sync Replication, or 3DC PP configuration audit Quorum Witness as an alternative path to
the Remote Copy links to determine the operational status of their partner storage system. The storage systems differentiate between a
Remote Copy link failure and a storage system failure.
Are the two storage systems active, but not communicating because of a Remote Copy link failure? Quorum Witness is still receiving
updates from both of the systems. Therefore, no failover is required.
Has one of the storage systems failed? Quorum Witness is not receiving updates from the failed system. The active system cannot
see the failed system through the Remote Copy link. The active system knows that updates are not being received. A failover is
required and occurs automatically.
NOTE: Active Sync Replication provides both manual transparent failover (MTF) and automatic failover. Automatic
Failover is a feature of HPE Active Sync Replication and is not transparent to the host systems.Automatic failover
requires HPE Quorum Witness and the auto failover policy to be enabled on the Remote Copy group.
Quorum Witness and automatic transparent failover (ATF) 83

Creating a Quorum Witness client configuration
Create a secure connection between the Active Peer Persistence, Peer Persistence, and three data center Peer Persistence storage
systems and the Quorum Witness (QW) server.
Prerequisites
Installed HPE Quorum Witness software. See the Installing and updating HPE Quorum Witness for HPE Primera and HPE 3PAR on
Connected Host I/O paths to each storage system such that the source and target volumes are visible to the host.
Created the Active Peer Persistence, Peer Persistence, or three data center Peer Persistence configuration.
Procedure
2. In the list pane, select the Peer Persistence or three data center Peer Persistence configuration.
3. Select Actions > Configure quorum witness .
4. Enter the following information:
a. Enter the IP address or the FQDN of the Quorum Witness server.
b. Select Yes for Start.
c. Select Enabled for Secure Connection.
d. Enter the configured port number of the QW server.
Use the default port 8443 if an alternative port was not set up.
5. Click Configure.
After a few minutes, the Quorum Witness client is configured.
6. To verify that the Quorum Witness client configuration is added and started, select the Targets view.
The QW Server field displays the IP address or the FQDN of the Quorum Witness server. The QW Status field displays Started.
Creating a Quorum Witness client configuration 84

Remote Copy groups
A Remote Copy group is a set of one or more virtual volumes to be replicated to another storage system. I/O consistency is guaranteed
across the virtual volumes in a Remote Copy group.
When you create a Remote Copy group, the virtual volumes in the primary group are replicated to the secondary group. All virtual
volumes that belong to the same application must be added to the same group.
The number of Remote Copy groups and the number of volumes included in the group are based on your business needs and the
maximums defined in the HPE Primera Support Matrix available on SPOCK. You can have multiple volumes and multiple groups.
Remote Copy groups 85

Active Peer Persistence and Active Sync Replication ( active_active )
Enables the possibility of host reads and writes to volumes in either one of, or both, of the primary and secondary in the specified
group. Preferred Read/write access is established using proximity settings.
When this policy is set, the auto_recover and auto_synchronize polices are automatically set and override (take precedence over)
the path_management and auto_failover policies. The HPE Quorum Witness is required for automatic failover of host IO when the
storage system containing the primary groups becomes unavailable.
no_active_active
As the default setting, the no_active_active policy changes the Remote Copy group back to Passive/Active operation as
long as the path_management policy is set. If the path_managment policy is not set, the Remote Copy group operation changes
back to synchronous mode.
Auto failover ( auto_failover )
The auto failover policy, when enabled with HPE Quorum Witness, allows an automatic failover on a classic Peer Persistence
Remote Copy group. If the primary storage system fails, the group fails over to the secondary storage system automatically.
The auto failover policy also enables Remote Copy group failover for a RAID set failure or metadata corruption of a primary
volume in the group. Although the failover does not require a Quorum Witness configuration, it does require the
path_management policy or active_active policy. While restarting the group after the failover, a full synchronization of the volumes
is performed which ensures consistency.
If the auto failover policy is not enabled, if a disaster occurs, the classic Peer Persistence group does not fail over and must be
recovered manually.
NOTE:
The active_active policy takes precedence over this policy. It can be left enabled when enabling Active Peer
Persistence. It can be disabled after conversion to Active Peer Persistence has completed. If left enabled,
subsequent disabling of Active Peer Persistence results in going back to automatic transparent failover for Classic
Peer Persistence groups.
NOTE:
The Primera OS 4.3.x introduces auto failover upon loss of host access to volumes in Remote Copy groups and
when the storage system is shutdown. If all the host IO paths to one or more volumes are down, the primary
Remote Copy groups will automatically failover to the secondary storage system. If the storage system containing
the primary Remote Copy groups is shutdown using the OS shutdown command, and the active_active policy is set,
the primary Remote Copy groups will automatically failover to the secondary storage system.
no_auto_failover
As the default setting, use the no_auto_failover policy to select Remote Copy groups that will not be subject to automatic
failover. This policy setting disables all failover strategies.
Auto recover ( auto_recover )
When enabled, if the Remote Copy links go down, the Remote Copy group is restarted automatically after the links recover.
If you enable the auto recover policy when the links are down and the Remote Copy group is stopped, the group must be manually
started after the Remote Copy links are brought up. If auto recover is set and the links fail, and then you disable the policy, the
Remote Copy group does not restart automatically after the links recover.
The auto recover policy is enabled by default when the active_active policy is enabled. This policy is enabled automatically
when the active_active policy is set. When not enabled, you must restart the Remote Copy group manually after the links recover.
no_auto_recover
As the default setting, the no_auto_recover policy setting disables the automatic recover policy. Therefore, Remote Copy
groups are never automatically restarted.
Auto synchronize ( auto_synchronize )
If a failover occurs and the auto synchronize policy is enabled, all virtual volumes in the Remote Copy group will be automatically
synchronized. Synchronization occurs after system recovery completes and the Remote Copy links recover.
Hewlett Packard Enterprise recommends that setting the auto synchronize policy as a best practice for all configurations.
In synchronous long distance (SLD) and three data center Peer Persistence (3DC PP) configurations, this policy can be set on the
Remote Copy group synchronous targets only.
NOTE:
Remote Copy group policies 86

In SLD configurations, to perform a failover to the synchronous target, the SLD group must be stopped on all
targets, or started on all targets. To perform a failover to the periodic target, the SLD group must be stopped on all
targets.
In 3DC PP configurations, the target links must be down to perform a failover to the synchronous target. To
perform a failover to the periodic target, the groups on the periodic target must be stopped. The links can be up or
down.
The auto synchronize policy is enabled by default when the active_active policy is enabled. When not enabled, you must manually
synchronize the Remote Copy group after the system recovery completes and after the links recover.
no_auto_synchronize
To select Remote Copy groups that will not be subject to automatic synchronization after failover, use the
no_auto_synchronize policy. This policy is the default setting.
Mirror ( mirror_config )
The mirror policy automatically applies actions and settings to the Remote Copy group at the source and target storage systems
simultaneously. For example, if you start or stop a Remote Copy group, the group starts or stops on the source and target systems
simultaneously. You can start or stop the Remote Copy group even if the target storage system is disconnected from HPE SSMC.
The mirror policy option is automatically enabled when you create a Remote Copy configuration.
Over period alert ( over_per_alert )
If periodic synchronization does not complete within the specified synchronization period, the over period alert policy generates
alerts.
The over period alert policy is enabled by default for periodic Remote Copy groups. This policy applies to periodic mode only.
no_over_per_alert
If you do not want to generate slow synchronization alerts for asynchronous periodic Remote Copy groups, use the
no_over_per_alert policy setting.
Peer Persistence ( path_management )
This classic Peer Persistence policy sets the Asymmetric Logical Unit Access (ALUA) path from the host to the primary Remote
Copy group to active (ALUA active-optimized from the host perspective). The path to the secondary Remote Copy group is set to
standby.
If classic Peer Persistence is not enabled, ALUA behavior is not enabled for volumes in the Remote Copy group. In a 3DC PP
configuration, the policy is only applied to the synchronous groups.
The Active Peer Persistence policy takes precedence over this policy. It can be left enabled when enabling Active Peer Persistence.
It can be disabled after conversion to Active Peer Persistence has completed. If left enabled, subsequent disabling of Active Peer
Persistence results in going back to Classic Peer Persistence operation.
IMPORTANT:
You cannot disable the path_management policy on volumes that are presented to hosts from both the primary
and secondary systems in a classic Peer Persistence configuration. The policy can only be disabled after volume
presentation is removed from the secondary system or when Active Peer Persistence is enabled.
no_path_management
Use the no_path_management setting to disable the path management policy for synchronous Remote Copy groups. The
Target Port Group state of volumes in the specified group will be reported as ACTIVE on the primary and secondary
systems.
For example:
cli%
setrcopygroup pol no_path_management <group_name>
This policy is the default setting.

Multi-target Peer Persistence ( mt_pp )
The multi-target Peer Persistence policy enables the primary Remote Copy groups to update the secondary groups synchronously
with a Peer Persistence target and periodically to a tertiary site. The policy must be set on all group targets in a 3DC PP
configuration.
This policy is required for 3DC PP configurations.
no_mt_pp
Use the no_mt_pp policy to remove multi-target replication in a classic Peer Persistence configuration. This policy is the

default setting.

Related documentation
The following guides provide additional information for your Remote Copy solution. The guides are available at:
https://www.hpe.com/info/Primera600-docs
For HPE Primera OS:
Getting started with data replication using Remote Copy
Configuring and managing data replication using Remote Copy
Troubleshooting your Remote Copy configuration
Recovering from disaster using Remote Copy
Additional documentation
Installing and Updating HPE Quorum Witness for HPE Primera and HPE 3PAR located on HPESC.
TIP: To quickly locate a document on HPESC, enter the document title into the HPESC search bar.
HPE Primera Support Matrix located on SPOCK.
HPE Primera Peer Persistence/Active Peer Persistence/Active Sync Replication Host OS Support Matrix located on SPOCK.
Related documentation 89
Websites
General websites
Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix
https://www.hpe.com/storage/spock
Storage white papers and analyst reports
https://www.hpe.com/storage/whitepapers
For additional websites, see Support and other resources.
Websites 90
Support and other resources
Support and other resources 91

Accessing Hewlett Packard Enterprise Support
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
https://www.hpe.com/info/assistance
To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website:
https://www.hpe.com/support/hpesc
Information to collect
Technical support registration number (if applicable)
Product name, model or version, and serial number
Operating system name and version
Firmware version
Error messages
Product-specific reports and logs
Add-on products or components
Third-party products or components
Accessing Hewlett Packard Enterprise Support 92

Accessing updates
Some software products provide a mechanism for accessing software updates through the product interface. Review your product
documentation to identify the recommended software update method.
To download product updates:
Hewlett Packard Enterprise Support Center
https://www.hpe.com/support/hpesc
Hewlett Packard Enterprise Support Center: Software downloads
https://www.hpe.com/support/downloads
My HPE Software Center
https://www.hpe.com/software/hpesoftwarecenter
To subscribe to eNewsletters and alerts:
https://www.hpe.com/support/e-updates
To view and update your entitlements, and to link your contracts and warranties with your profile, go to the Hewlett Packard
Enterprise Support Center More Information on Access to Support Materials page:
https://www.hpe.com/support/AccessToSupportMaterials
IMPORTANT:
Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise
Support Center. You must have an HPE Passport set up with relevant entitlements.
Accessing updates 93
Remote support
Remote support is available with supported devices as part of your warranty or contractual support agreement. It provides intelligent
event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which initiates a fast
and accurate resolution based on the service level of your product. Hewlett Packard Enterprise strongly recommends that you register
your device for remote support.
If your product includes additional remote support details, use search to locate that information.
HPE Get Connected
https://www.hpe.com/services/getconnected
HPE Pointnext Tech Care
https://www.hpe.com/services/techcare
HPE Complete Care
https://www.hpe.com/services/completecare
Remote support 94
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it
will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard
Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider.
Customer self repair 95

Warranty information
To view the warranty information for your product, see the links provided below:
HPE ProLiant and IA-32 Servers and Options
https://www.hpe.com/support/ProLiantServers-Warranties
HPE Enterprise and Cloudline Servers
https://www.hpe.com/support/EnterpriseServers-Warranties
HPE Storage Products
https://www.hpe.com/support/Storage-Warranties
HPE Networking Products

https://www.hpe.com/support/Networking-Warranties
Warranty information 96
Regulatory information
To view the regulatory information for your product, view the Safety and Compliance Information for Server, Storage, Power,
Networking, and Rack Products, available at the Hewlett Packard Enterprise Support Center:
https://www.hpe.com/support/Safety-Compliance-EnterpriseProducts
Additional regulatory information

Hewlett Packard Enterprise is committed to providing our customers with information about the chemical substances in our products as
needed to comply with legal requirements such as REACH (Regulation EC No 1907/2006 of the European Parliament and the Council). A
chemical information report for this product can be found at:
https://www.hpe.com/info/reach
For Hewlett Packard Enterprise product environmental and safety information and compliance data, including RoHS and REACH, see:
https://www.hpe.com/info/ecodata
For Hewlett Packard Enterprise environmental information, including company programs, product recycling, and energy efficiency, see:
https://www.hpe.com/info/environment
Regulatory information 97
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, use
the Feedback button and icons (located at the bottom of an opened document) on the Hewlett Packard Enterprise Support Center portal
(https://www.hpe.com/support/hpesc) to send any errors, suggestions, or comments. All document information is captured by the
process.
Documentation feedback 98

HPE Primera OS Configuring and Managing Data Replication Using Remote

Uploaded by

Copyright:

Available Formats

You might also like

HPE Primera OS Configuring and Managing Data Replication Using Remote

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HPE Primera OS Configuring and Managing Data Replication Using Remote

Uploaded by

Copyright:

Available Formats

HPE Primera OS: Configuring and managing data replication using Remote

Part Number: 20-PRI600-RCCF-ED2

© Copyright 2019, 2022 Hewlett Packard Enterprise Development LP

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

UNIX® is a registered trademark of The Open Group.

Part number Publication date Edition Summary of changes

20-PRI600-RCCF-ED2 March 2022 2 Updated for HPE Primera OS 4.5

20-PRI600-RCCF-ED1 October 2021 1 Updated for HPE Primera OS 4.4

P36431-002 May 2021 4 Combined Primera OS configuration and management documents

P23108-001 September 2019 1 Initial release

1 Determining compatibility for Remote Copy

Determining compatibility for Remote Copy 6

3. Click the appropriate support matrix.

Accessing the HPE Primera Support Matrix in SPOCK 7

1. Use your HPE Passport account to log in to SPOCK.

Accessing the HPE Host OS Support Matrix in SPOCK 8

Unique IP addresses for all RCIP ports.

Remote Copy over IP (RCIP) network transport requirements 9

Requirements in the SAN Design Reference Guide are met.

To verify the zoning, use the following command:

For example, proper zoning displays as:

showportdev all 0:3:1

Remote Copy over FC (RCFC) network transport requirements 10

1. To configure the logical links, see:

Configure the RCIP links .

Configure the RCFC links .

2. Select a Remote Copy data replication solution.

Preparing the logical Remote Copy links 11

Reviewed Remote Copy over IP (RCIP) network transport requirements .

Configuring the RCIP links 12

Set up one-to-one fabric zoning between the storage systems.

2. Select the Protocol filter and choose RCFC.

a. If the port state is Free, select Actions > Initialize.

b. If the port state is Offline, select Actions > Enable.

c. If the port shows Ready, go to the next step.

4. Verify that the RCFC ports have been zoned correctly.

Configuring the RCFC links 13

Procedures to create Remote Copy replication solutions

Configuring a Peer Persistence data replication solution

Configuring an Active Peer Persistence data replication solution

Configuring an Active Sync Replication solution

Configuring a synchronous long distance data replication solution

Configuring a three data center Peer Persistence data replication solution

Configuring a one-to-many data replication solution

Configuring a many-to-one data replication solution

Remote Copy data replication solutions 14

Configuring a 1-to-1 data replication solution 15

2. Click + Create configuration or select Actions > Create.

3. Create links and targets between the two storage systems:

a. Select each system from the drop-down list.

b. Select a minimum of two RCIP or RCFC ports between each system.

4. (Optional) To enter the geographical location for a system:

b. Enter the location and click OK.

b. Make the necessary changes and click OK.

6. (Optional) To test connectivity between systems with RCIP links:

Creating a 1-to-1 Remote Copy configuration 16

2. Click + Create group or select Actions > Create.

a. Enter a unique Group name.