HPE 3PAR Remote Copy Software UserGuideHPE 3PAR OS 3.3.1 MU1

Part Number: QL226-99648Published: August 2017

AbstractThis guide is for system and storage administrators who monitor and direct remote copy systemconfigurations and resource allocation for HPE 3PAR StoreServ Storage systems.

Copyright 2017 Hewlett Packard Enterprise Development LP

NoticesThe information contained herein is subject to change without notice. The only warranties for Hewlett PackardEnterprise products and services are set forth in the express warranty statements accompanying suchproducts and services. Nothing herein should be construed as constituting an additional warranty. HewlettPackard 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 SoftwareDocumentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor's standard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett PackardEnterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprisewebsite.

AcknowledgmentsMicrosoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in theUnited States and/or other countries.

Java and Oracle are registered trademarks of Oracle and/or its affiliates.

Contents

Setting the foundation for HPE 3PAR Remote Copy..............................12

Remote copy setup............................................................................13Remote copy setup methods..................................................................................................13Reviewing 3PAR Remote Copy requirements........................................................................ 14

General requirements.................................................................................................. 14General considerations................................................................................................14System restrictions.......................................................................................................15Software restrictions.................................................................................................... 15Remote copy and virtual domains................................................................................15

3PAR Remote Copy configurations..................................................17M-to-N remote copy configurations.........................................................................................17

Unidirectional 1-to-1 configuration............................................................................... 17Bidirectional 1-to-1 configuration................................................................................. 18N-to-1 configuration..................................................................................................... 181-to-N configuration..................................................................................................... 19M-to-N configuration.................................................................................................... 20

Synchronous long-distance configuration...............................................................................20

Selecting network connections........................................................ 22Network connection types.......................................................................................................22

Fibre Channel networks...............................................................................................22IP Networks..................................................................................................................23Fibre Channel over IP networks...................................................................................23

Gathering setup information.............................................................24

Setting the transport layer................................................................ 25Transport layer considerations................................................................................................25

RCIP............................................................................................................................ 25RCFC...........................................................................................................................25Network address translation........................................................................................ 26

Remote copy over IP.............................................................................................................. 26RCIP initial remote copy pair....................................................................................... 26RCIP port configuration................................................................................................27Setting up the remote copy interface for RCIP............................................................ 27showport -rcip output does not match RCIP configuration settings .....................28Setting the gateway..................................................................................................... 28Gateway address does not match RCIP configuration settings...................................28Verifying that the servers are connected......................................................................29The controlport rcip ping command does not succeed.................................. 29Checking RCIP link throughput and latency................................................................ 30Link throughput and latency are unsatisfactory........................................................... 31

Contents 3

Increasing MTU............................................................................................................31The controlport rcip ping command does not succeed ................................. 32Adding RCIP links........................................................................................................32Removing RCIP links...................................................................................................33

Setting up remote copy over Fibre Channel........................................................................... 33Configuring ports for RCFC......................................................................................... 33Disabling IntCoal...................................................................................................... 34Setting up dedicated node pairs for RCFC.................................................................. 34Setting up remote copy interface for RCFC.................................................................35Checking RCFC link throughput and latency...............................................................37

Setting up RCFC over an IP network......................................................................................37

Setting up the remote copy servers.........................................................39

M-to-N remote copy setup.................................................................40Setting up 1-to-1 remote copy in a unidirectional configuration..............................................40Setting up 1-to-1 remote copy in a bidirectional configuration................................................40

1-to-1 remote copy example........................................................................................ 41Setting up N-to-1 remote copy................................................................................................43Example remote copy pair for N-to-1 setup............................................................................44Setting up 1-to-N remote copy................................................................................................451-to-N remote copy considerations.........................................................................................46Verifying connectivity between remote copy pairs for M-to-N setup.......................................47Setting up the primary system for M-to-N remote copy.......................................................... 47Setting up the secondary system for M-to-N remote copy......................................................48Checking the links between systems for M-to-N remote copy................................................49Verifying that virtual volumes are created for M-to-N remote copy.........................................50Creating volume groups for M-to-N remote copy....................................................................50Selecting an initial replication method for M-to-N remote copy.............................................. 53Starting initial replication for M-to-N remote copy...................................................................53

Setting up SLD remote copy.............................................................55SLD remote copy considerations............................................................................................55Verifying connectivity between remote copy pairs for SLD setup...........................................56Setting up the primary system for SLD remote copy.............................................................. 56Setting up the backup systems for SLD remote copy.............................................................58SLD remote copy example..................................................................................................... 60Checking the links between systems for SLD remote copy....................................................64Verifying that virtual volumes are created for SLD remote copy.............................................66Creating volume groups for SLD remote copy........................................................................67Starting initial replication for SLD remote copy: copying data directly from primaryvolume groups........................................................................................................................ 69Failover and failback behavior of individual remote copy groups in SLD configuration..........70

Normal SLD operation................................................................................................. 70SystemA-to-SystemB failover for an individual remote copy group.............................71SystemA-to-SystemC failover in SLD remote copy configuration................................73Double failover.............................................................................................................76

Setting up a unidirectional configuration........................................77Example unidirectional remote copy setup.............................................................................77Verifying connectivity between remote copy pairs for unidirectional setup.............................79Setting up the primary system for unidirectional remote copy................................................80

4 Contents

Setting up the secondary system for unidirectional remote copy........................................... 81Checking the links between systems for unidirectional remote copy......................................81Verifying that virtual volumes are created for unidirectional remote copy...............................83Creating volume groups for unidirectional remote copy......................................................... 83Selecting an initial replication method for unidirectional remote copy.................................... 86Starting initial replication for unidirectional remote copy: copying data directly fromprimary volume groups........................................................................................................... 86

Setting up a bidirectional configuration.......................................... 88Example bidirectional setup....................................................................................................88Setting up the systems for bidirectional remote copy............................................................. 90Creating volume groups for bidirectional remote copy........................................................... 91Selecting an initial synchronization method for bidirectional remote copy..............................94Starting initial synchronization for bidirectional remote copy: copying data directly fromprimary volume groups........................................................................................................... 94

Remote copy management....................................................................... 96

Stopping, starting, or removing remote copy................................. 98Stopping and restarting remote copy......................................................................................98Stopping and starting remote copy groups.............................................................................98Removing remote copy completely.........................................................................................99

Viewing remote copy system information..................................... 100How remote copy tracks synchronization details..................................................................101

Tracking synchronous volume groups....................................................................... 101Tracking asynchronous streaming volume groups.................................................... 101Tracking asynchronous periodic volume groups........................................................101

Viewing synchronization task information.............................................................................101Viewing more detail for a synchronization task..........................................................102Viewing earlier synchronization tasks........................................................................ 103

Task management commands for remote copy synchronizations........................................103

Remote copy pairs and targets.......................................................105Remote copy pairs................................................................................................................105Remote copy targets.............................................................................................................105Target definitions...................................................................................................................105Remote copy secondary system...........................................................................................107

System roles and direction of data flow..................................................................... 107Changing the direction of data flow............................................................................107System roles and bidirectional configurations............................................................107

Remote copy links........................................................................... 109Sending links........................................................................................................................ 109

Configuring one sending link per node per target......................................................109Configuring sending links for a remote copy pair....................................................... 110Configuring links for multiple remote copy pairs.........................................................111Increasing the number of links for existing remote copy groups................................ 111Decreasing the number of links for existing remote copy groups.............................. 113

Receiving links...................................................................................................................... 115

Contents 5

Converting a 3PAR Remote Copy 1:1 configuration to an SLDconfiguration.................................................................................... 116

Converting an asynchronous periodic remote copy group to an SLD remote copy group....116Converting an SLD remote copy group to an asynchronous periodic remote copy group....117

Working with virtual volumes......................................................... 118Creating remote copy virtual volumes...................................................................................118Growing virtual volumes........................................................................................................119Renaming virtual volumes.................................................................................................... 120Creating CPGs and virtual volumes......................................................................................120

Common provisioning groups.................................................................................... 121Virtual volumes used with remote copy..................................................................... 122

Using remote copy with 3PAR File Persona......................................................................... 123Automatically creating virtual volumes at the remote target................................................. 123

Creating remote copy groups with associated local and remote CPGs.....................123Setting associated local and remote CPGs for remote copy groups......................... 124Automatically creating target volumes on the secondary system.............................. 124Automatically deleting target volumes on the secondary system.............................. 125Coordinated manual grow over remote copy.............................................................125

Working with volume groups..........................................................127Why use volume groups....................................................................................................... 127How volume groups work..................................................................................................... 128Automatic creation of remote copy volume groups...............................................................128Rules for forming volume groups..........................................................................................129How volume groups are named............................................................................................129Adding snapshots to volume groups.....................................................................................129How volume groups are organized on the remote copy pair................................................ 130Natural direction of replication.............................................................................................. 130Linking virtual volumes in volume groups.............................................................................130

Unidirectional volume groups.....................................................................................130Bidirectional volume groups.......................................................................................130

Changing the remote copy mode for a volume group...........................................................131Manually resynchronizing volume groups.............................................................................133Changing secondary volume groups to primary volume groups...........................................133

Changing a single volume group............................................................................... 134Changing all volume groups on a system..................................................................134

Volume group policies...........................................................................................................134auto_recover policy ..............................................................................................134no_auto_recover policy ....................................................................................... 135auto_failover policy ............................................................................................135no_auto_failover policy ..................................................................................... 135auto_failover_ext policy ................................................................................... 135no_auto_failover_ext policy .............................................................................136over_per_alert policy ..........................................................................................136no_over_per_alert policy ................................................................................... 136path_management policy ....................................................................................... 136no_path_management policy .................................................................................136auto_synchronize policy ..................................................................................... 137no_auto_synchronize policy ...............................................................................137mt_pp policy .............................................................................................................137

6 Contents

no_mt_pp policy .......................................................................................................137RemoteCopyHostThrottling policy.....................................................................137Secondary system cannot be contacted....................................................................138Automatically restarting volume groups.....................................................................138Generating alerts for slow resynchronization of asynchronous periodic volumegroups........................................................................................................................139

Volume group replication modes.......................................................................................... 139Synchronous mode....................................................................................................140Asynchronous periodic mode.....................................................................................141Asynchronous streaming mode................................................................................. 142

Synchronization.................................................................................................................... 142Types of synchronization........................................................................................... 143Limits on volumes that concurrently synchronize...................................................... 143Asynchronous periodic mode volume groups............................................................143Synchronous mode volume groups........................................................................... 147Asynchronous streaming mode volume groups.........................................................148Setting snapshot frequency for asynchronous streaming mode................................148

Optimizing RCIP performance........................................................ 150Avoiding RCIP throughput issues during initial synchronization...........................................150Optimizing RCIP synchronization speed over distances...................................................... 150Optimizing RCIP throughput by increasing MTU size...........................................................151Limiting throughput............................................................................................................... 151

Limiting throughput for asynchronous periodic volume groups..................................152Limiting throughput for asynchronous streaming volume groups.............................. 152Removing throughput limits....................................................................................... 152

RCIP remote copy links fail to come up................................................................................153Distribution of host writes over RCIP network adapter (NIC) links....................................... 154

3PAR Peer Persistence with transparent failover......................... 1553PAR Quorum Witness requirements...................................................................................1553PAR Quorum Witness components.................................................................................... 1573PAR Peer Persistence........................................................................................................ 158

Manual transparent failover....................................................................................... 163Automatic transparent failover................................................................................... 167

3PAR Peer Persistence quorum........................................................................................... 167Handling automatic transparent failover.................................................................... 168Link and communication failure scenarios.................................................................169

Path management policies................................................................................................... 174Enabling the path_management policy ............................................................................. 175Disabling the path_management policy ............................................................................ 175Setting a timeout value for automatic failover.......................................................................175Peer Persistence coexistence with other remote copy groups.............................................176VMware vSphere Metro Storage Cluster configuration........................................................ 176Configuring ESX host personas............................................................................................1773PAR Peer Persistence with multiple targets....................................................................... 177

Converting an existing SLD configuration .................................................................177Converting an existing Peer Persistence configuration ............................................ 178

Overriding failsafe state........................................................................................................178

Using tape for initial synchronization and backup.......................180

Contents 7

Error handling.................................................................................. 182Synchronization states..........................................................................................................182Timeouts for remote copy failure.......................................................................................... 183

Link heartbeat timeout............................................................................................... 183Target timeout............................................................................................................ 183

Failure of a single link...........................................................................................................183Target failure.........................................................................................................................184

Target failure and asynchronous streaming volume groups...................................... 184Manually restarting remote copy................................................................................184Target failure and synchronous volume groups......................................................... 184Restarting synchronous volume groups after link recovery....................................... 185Target failure and asynchronous periodic volume groups..........................................185Resynchronizing asynchronous periodic volume groups after link recovery............. 185

Failure of a storage system.................................................................................................. 186Failure of a primary system........................................................................................186Failure of a secondary system...................................................................................186

Write errors........................................................................................................................... 186Write errors on the primary system............................................................................186Write errors on the secondary system....................................................................... 186

Read errors...........................................................................................................................187Read errors during initial synchronization..................................................................187Read errors during synchronization after restart of synchronous volume groups......187Read errors during synchronization after restart of asynchronousstreaming volume groups ......................................................................................188Read errors during resynchronization of asynchronous periodic volume groups...... 188

Recovering from disaster....................................................................... 189

Using 3PAR Peer Persistence for nondisruptive failover in 1-to-1 remote copy in 3PAR Geocluster environments................... 190

Prerequisites: Before you begin nondisruptive failover.........................................................191System information during normal operation........................................................................193System information during failover....................................................................................... 195Performing a nondisruptive failover...................................................................................... 196Troubleshooting nondisruptive failover................................................................................. 198

Disaster recovery for 1-to-1 configurations.................................. 200System information during normal operation........................................................................203System information during failover for 1-to-1 configurations................................................ 204

Synchronous mode for 1-to-1 configurations.............................................................204Asynchronous periodic mode for 1-to-1 configurations..............................................204Asynchronous streaming mode for 1-to-1 configurations.......................................... 204Example output after primary system failure for 1-to-1 configurations.......................205

Recovering from disaster for 1-to-1 configurations...............................................................205Failover in 1-to-1 remote copy configurations............................................................205Recovery in 1-to-1 remote copy configurations......................................................... 207

Disaster recovery for M-to-N configurations.................................214Disaster recovery for N-to-1 configurations.......................................................................... 214

System information during normal operation for N-to-1 configurations......................216

8 Contents

System information during failover for N-to-1 configurations.....................................218Recovering from disaster for N-to-1 configurations................................................... 219

Disaster recovery for 1-to-N configurations.......................................................................... 227System information during normal operation for 1-to-N configurations......................229System information during failover for 1-to-N remote copy configurations................ 232Recovering from disaster for 1-to-N configurations................................................... 233

Disaster recovery for SLD configurations.....................................240System information during normal operation for SLD configurations................................... 241System information during failover for SLD configurations...................................................244

Stages of disaster recovery in SLD remote copy configurations............................... 246Failover to the synchronous target system...........................................................................246

Failing over in an SLD remote copy configuration..................................................... 247Recovering in an SLD remote copy configuration......................................................250

Failover to the asynchronous periodic secondary system (with data transfer).....................260Failing over in asynchronous periodic SLD remote copy configurations................... 261Recovering asynchronous periodic mode in SLD remote copy configurations..........264

Failover to the asynchronous periodic secondary system (no data transfer)....................... 273Failing over to the secondary system........................................................................ 274Recovering the secondary system.............................................................................277

Handling secondary system failure.......................................................................................286Handling primary system failure........................................................................................... 287

Replication recovery from WAN failure..........................................291SLD replication during normal operation.............................................................................. 291SLD operation after WAN failure...........................................................................................291Remote copy manual restart operation.................................................................................291Asynchronous periodic replication during normal operation.................................................292Asynchronous periodic replication during WAN failure.........................................................292Asynchronous streaming replication during normal operation..............................................293Asynchronous streaming replication during WAN failure......................................................293

Disaster Recovery for Peer Persistence configurations..............294

Reference................................................................................................. 295

Quick setup guide............................................................................296Quick setup: RCIP transport layer........................................................................................ 296Quick setup: RCFC transport layer.......................................................................................298Quick setup: remote copy configurations..............................................................................298Quick setup for unidirectional remote copy pairs: 1-to-1, 1-to-N , and N-to-1configurations....................................................................................................................... 299Quick setup for bidirectional remote copy pair: 1-to-1, N-to-1, and 1-to-N configurations....301Quick setup: synchronous long distance remote copy......................................................... 302

Quick disaster recovery guide........................................................306Quick recovery: 1-to-1 and M-to-N remote copy configurations........................................... 306Quick recovery: synchronous long distance configurations..................................................307

Contents 9

3PAR CLI remote copy commands.................................................310Remote copy command descriptions....................................................................................310Issuing remote copy commands........................................................................................... 311

3PAR Quorum Witness deployment...............................................3133PAR Quorum Witness installation.......................................................................................313

Installing the 3PAR Quorum Witness on VMware ESX............................................. 313Installing the 3PAR Quorum Witness on Windows Hyper-V...................................... 314

Configuring the 3PAR Quorum Witness............................................................................... 315Configuring a static IP address.............................................................................................316Enabling IPv6 on Quorum Witness server............................................................................3173PAR CLI quorum witness commands................................................................................. 318

Creating a quorum witness........................................................................................ 318Starting a quorum witness......................................................................................... 319Stopping a quorum witness........................................................................................319Removing a quorum witness......................................................................................320Auto failover policies..................................................................................................320

Quorum troubleshooting....................................................................................................... 320Quorum status qualifier..............................................................................................320Logs........................................................................................................................... 324

Remote copy snapshots..................................................................325Snapshots.............................................................................................................................325

Volume space considerations.................................................................................... 325Snapshots in synchronous mode..........................................................................................326

Snapshots and initial synchronization failure.............................................................326Snapshots and resynchronization..............................................................................326Snapshots and resynchronization failure in synchronous mode................................326Snapshots taken before or during disaster recovery................................................. 326

Snapshots in asynchronous streaming mode.......................................................................327Snapshots in asynchronous periodic mode..........................................................................328

Snapshots taken during initial synchronization..........................................................328Snapshots taken during resynchronization................................................................329Snapshots and resynchronization failure in asynchronous periodic mode................ 329Snapshots taken before or during disaster recovery................................................. 329Snapshot replication in remote copy groups..............................................................330

Support and other resources..........................................................331Accessing Hewlett Packard Enterprise Support................................................................... 331Accessing updates................................................................................................................331HPE 3PAR documentation....................................................................................................332Websites............................................................................................................................... 332Customer self repair............................................................................................................. 333Remote support.................................................................................................................... 333Documentation feedback......................................................................................................333

Glossary................................................................................................... 334A...................................................................................................................................................... 334C......................................................................................................................................................334F...................................................................................................................................................... 334

10 Contents

G......................................................................................................................................................334H......................................................................................................................................................334I........................................................................................................................................................335J.......................................................................................................................................................335K...................................................................................................................................................... 335L.......................................................................................................................................................335M......................................................................................................................................................335O......................................................................................................................................................335P...................................................................................................................................................... 335Q......................................................................................................................................................336R......................................................................................................................................................336S...................................................................................................................................................... 337T...................................................................................................................................................... 337V...................................................................................................................................................... 338W..................................................................................................................................................... 338

Contents 11

Setting the foundation for HPE 3PAR RemoteCopyProcedure

1. Select your setup method.

Remote copy setup methods2. Select a remote copy configuration.

3PAR Remote Copy configurations3. Select a network connection type.

Reviewing 3PAR Remote Copy requirements

See also:

1-to-N remote copy considerations SLD remote copy considerations

4. To make sure that the system is prepared for remote copy configuration, review the requirements andrestrictions.

Gathering setup information5. Configure the remote copy transport layer.

Setting the transport layer

When you have set the foundation for your remote copy system, continue to Setting up the remote copyservers.

12 Setting the foundation for HPE 3PAR Remote Copy

Remote copy setup

Remote copy setup methodsIf you are a new user setting up HPE 3PAR Remote Copy for the first time, use one of the following methods:

Follow the setup steps, as they relate to your remote copy system, in Setting the foundation forHPE 3PAR Remote Copy on page 12 and Setting up the remote copy servers on page 39.

Use the Remote Copy Setup wizard in the HPE 3PAR Management Console. Use the HPE 3PAR Management Console to set up a simple 1-to-1 remote copy configuration between

two storage systems. For more complex 1-to-1 configurations, as well as for N-to-1, M-to-N, and SLDconfigurations, use the HPE 3PAR Command-Line Interface to set up and configure remote copy.

The HPE 3PAR Management Console User Guide is available at the following website:

Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/storage/docs) Use the HPE 3PAR StoreServ Management Console SSMC to manage remote copy features. As of

SSMC 3.0, the SSMC supports all configurations and modes listed in the support matrix for HPE 3PAR OS3.3.1.

The supported configurations include 1-to-1, N-to-M, SLD, and 3PAR Peer Persistence, including 3DC.The supported group modes include synchronous, asynchronous periodic, and asynchronous streaming.

Use the SSMC for the following tasks:

View remote copy configurations (overview, targets, links, groups, alerts, and tasks associated with3PAR Remote Copy)

Create, edit, and remove remote copy configurations, targets, and links View all remote copy group information (overview, volumes, alerts, tasks and a graphical map) Perform remote copy group operations:

Create, edit, delete Start, stop, synchronize Disaster recovery operations

The support matrix is available on SPOCK (http://www.hpe.com/storage/spock).

The HPE 3PAR StoreServ Management Console User Guide is available at the following website:

Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/storage/docs)

If you are an expert HPE 3PAR Remote Copy user:

See Quick setup guide on page 296 Use the HPE 3PAR CLI to set up and configure remote copy, especially for more complex remote copy

configurations, such as M-to-N and SLD. See:

HPE 3PAR Command Line Interface Administrator Guide HPE 3PAR StoreServ Storage Concepts Guide

The documents are available at the following website:

Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/storage/docs)

For more information, search the web for the Hewlett Packard Enterprise technical white paper Disaster-tolerant solutions with HPE 3PAR Remote Copy

Remote copy setup 13

http://www.hpe.com/info/storage/docshttp://www.hpe.com/storage/spockhttp://www.hpe.com/info/storage/docshttp://www.hpe.com/info/storage/docs

Reviewing 3PAR Remote Copy requirementsProcedure

1. Review general considerations for all configurations.

General requirements on page 14 System restrictions on page 15 Software restrictions on page 15 Transport layer considerations on page 25 Creating remote copy virtual volumes on page 118

2. Review considerations applicable to your remote copy configuration.

1-to-N remote copy considerations on page 46 SLD remote copy considerations on page 55

General requirements HPE 3PAR Remote Copy requires the use of a minimum of two HPE 3PAR StoreServ Storage systems. You must have HPE 3PAR Remote Copy licenses for all storage systems participating in remote copy

replication. For more information about licensing and features, see the HPE 3PAR StoreServ StorageConcepts Guide, available at the following website:

Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/storage/docs) The physical connections between all storage systems used with HPE 3PAR Remote Copy must be made

through an IP-capable network or an FC SAN network. Make sure that your firewall is set to allow traffic over the designated RCIP ports, TCP 5785 and 5001. Make sure that all RCIP ports have unique IP addresses. To use remote copy to copy virtual volumes and perform replication and disaster recovery, you can use the

3PAR Management Console or the HPE 3PAR CLI. For more information about the 3PAR ManagementConsole, the HPE 3PAR CLI, and the commands used with remote copy, see:

HPE 3PAR Command Line Interface Reference HPE 3PAR Command Line Interface Administrators Manual HPE 3PAR Management Console User Guide HPE 3PAR StoreServ Management Console User Guide

The documents are available at the following website:

Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/storage/docs)

General considerations Distance between the systems.

Systems in the same room can be connected through network adapter (NIC) switches, or through FCnetworks. Longer distances require other topologies.

To use remote copy for disaster recovery, place the secondary storage system at a remote site, farenough away that the two sites are unlikely to be affected by the same disaster.

In synchronous replication mode, the latency of remote copy writes increases with distance. Bandwidth.

RCIP configurations can fully use all 1 Gbps links during the synchronization process. If you use networkswith lower throughput, the throughput between systems running HPE 3PAR Remote Copy software mightbe capped by the network.

Connection requirements.

For more information, see Setting the transport layer on page 25. Data availability and speed.

14 Reviewing 3PAR Remote Copy requirements

http://www.hpe.com/info/storage/docshttp://www.hpe.com/info/storage/docs

To maintain availability, you must use more than one link to connect storage systems. HPE 3PAR Remote Copy requires at least two separate network connections between storage systems

to ensure availability in case one of the networks fails. For optimal availability, connect the two HPE3PAR StoreServ Storage systems to separate network equipment.

When there are multiple physical links between the storage systems, HPE 3PAR Remote Copy uses allthe available links that are configured for the same replication mode (synchronous or asynchronousperiodic) to transmit data in parallel.

When there are multiple physical links between the storage systems, HPE 3PAR Remote Copy uses allthe available links that are configured for the same replication mode (synchronous, asynchronousperiodic, or asynchronous streaming) to transmit data in parallel.

System restrictions For more information about HPE 3PAR OS support levels, see the HPE 3PAR Operating System Upgrade

Pre-Planning Guide, available at the following website:

Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/storage/docs) Hewlett Packard Enterprise recommends that interrupt coalescing be disabled on the RCFC ports.

To disable interrupt coalescing on the RCFC ports, use the SSMC, or see the controlport command inthe HPE 3PAR Command Line Interface Reference. These guides are available at the following website:

Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/storage/docs)

Software restrictions HPE 3PAR Remote Copy does not support self-mirroring configurations. It cannot use a storage system to

replicate its own primary volumes to itself. HPE 3PAR Remote Copy does not support multi-hop configurations. It cannot replicate a primary volume

group to a secondary system and then replicate the volume group again from the secondary system to athird storage system.

To limit the potential for data loss, Hewlett Packard Enterprise recommends that synchronous modereplication be used whenever the additional write latency induced by the network, plus the write latencyinduced by the target array, will not exceed the maximum write latency tolerable by the application whosedata is being replicated.

Remote copy and virtual domainsHPE 3PAR Remote Copy checks for the presence of HPE 3PAR Virtual Domains (domains) on the secondarysystem to verify that you have mirrored the virtual volume to the same secondary system domain name as theprimary-system domain name.

If a virtual domain is required, define it when you create a remote copy group by using thecreatercopygroup command:cli% creatercopygroup -domain domain1 group_name target:periodic For remote copy to operate, you must name the domain correctly. For instructions on setting up domains, seethe HPE 3PAR Command Line Interface Administrator Guide.

When volumes are admitted to a remote copy group for which a virtual domain has been defined, the volumeson both sides must share the same domain name.

System restrictions 15

http://www.hpe.com/info/storage/docshttp://www.hpe.com/info/storage/docs

If you are using volume autocreation, define the local user CPG and the target user CPG, as well as the localsnapshot CPG and target snapshot CPG, when you create the group. All the CPGs defined must share thesame domain name.

cli% creatercopygroup -domain domain1 -usr_cpg Localcpg target:Targetcpg -snp_cpg Localsnp target:Targetsnp groupname target:periodic

NOTE:

To use HPE 3PAR Virtual Domains, you must have the HPE 3PAR Virtual Domains license.

Additional Information:

For more information about domains and the HPE 3PAR Virtual Domains license, see the HPE 3PARStoreServ Storage Concepts Guide.

For instructions on setting up domains, see the HPE 3PAR Command Line Interface Administrator Guide,the HPE 3PAR StoreServ Management Console User Guide, or the HPE 3PAR Management ConsoleHelp.

These documents are available on the following website:

Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/storage/docs)

16 Remote copy setup

http://www.hpe.com/info/storage/docs

3PAR Remote Copy configurationsRemote copy configurations are based on the relationship between a pair of storage systems, known as theremote copy pair. Within a remote copy pair, the primary storage system is the system that holds the volumesthat are copied to the secondary storage system.

HPE 3PAR Remote Copy supports the following configurations:

M-to-N configurations:

Unidirectional 1-to-1 configuration on page 17 Bidirectional 1-to-1 configuration on page 18 N-to-1 configuration on page 18 1-to-N configuration on page 19

Synchronous long-distance configuration on page 20

Review the remote copy configurations and select the configuration that is best suited for your system.

To learn more about the asynchronous streaming feature, see the following topics:

Asynchronous streaming mode on page 142

Asynchronous streaming mode for 1-to-1 configurations on page 204

Asynchronous streaming mode volume groups on page 148

Asynchronous streaming replication during normal operation on page 293

Asynchronous streaming replication during WAN failure on page 293

Setting snapshot frequency for asynchronous streaming mode on page 148

Snapshots in asynchronous streaming mode on page 327

Tracking asynchronous streaming volume groups on page 101

M-to-N remote copy configurations

Unidirectional 1-to-1 configurationIn a unidirectional 1-to-1 remote copy configuration, each storage system in the pair plays only one role: onesystem is the primary system, and one system is the secondary system.

Figure 1: Unidirectional 1-to-1 remote copy on page 17 illustrates a unidirectional 1-to-1 remote copyconfiguration. The primary storage system holds only primary volume groups, and the secondary storagesystem holds only secondary volume groups.

Primary storage system (System1)

Indicates direction of data replication

Secondary storagesystem (System2)

Secondary volume group X

(groupX.r)

Primary volume group X (groupX)

Primary volume group to secondary volume group

Figure 1: Unidirectional 1-to-1 remote copy

3PAR Remote Copy configurations 17

Bidirectional 1-to-1 configurationIn a bidirectional 1-to-1 remote copy configuration, each storage system in the pair functions as both theprimary and secondary system, and each system contains both primary and secondary volume groups. Eachsystem provides backup for the other, according to the direction of replication specified for each volumegroup.

Figure 2: Bidirectional 1-to-1 remote copy on page 18 illustrates a bidirectional 1-to-1 remote copyconfiguration.

System1

groupX to groupX.r

System2

groupY to groupY.rSecondary volume

group Y (groupY.r)

Primary volume group Y (groupY)

Secondary volume group X

(groupX.r)

Primary volume group X (groupX)

Indicates direction of data replication

Figure 2: Bidirectional 1-to-1 remote copy

N-to-1 configurationAn N-to-1 remote copy configuration is composed of multiple remote copy pairs.

NOTE:

Because the secondary system participates in one remote copy pair for each primary system, asecondary system with one or two primary systems needs only two controller nodes. A secondarysystem with three or more primary storage systems must have four or more controller nodes.

You can set up N-to-1 remote copy with up to four unidirectional or bidirectional remote copy pairs, as long asthe remote secondary system has the minimum number of nodes required to support the number of sourcesystems.

18 Bidirectional 1-to-1 configuration

Figure 3: N-to-1 remote copy on page 19 illustrates an N-to-1 configuration where:

Bidirectional remote copy is maintained between remote copy pair System3 and System4. Unidirectionalremote copy is maintained between System1 and System4 and between System2 and System4.

groupW to groupW.r

groupX to groupX.r

groupY to groupY.r

groupZ to groupZ.r

System1

Primary volume group W (groupW)

System4

Secondary volume group Y

(groupY.r)

Secondary volume group W

(groupW.r)

Secondary volume group X

(groupX.r)

Primary volume group Z (groupZ)

System3

Indicates direction of data replication

System2

Primary volume group Y (groupY)

Secondary volumegroup Z

(groupZ.r)Primary volume group X (groupX)

Figure 3: N-to-1 remote copy

1-to-N configurationA 1-to-N remote copy configuration is composed of multiple remote copy pairs. One primary systemparticipates in four remote copy pairs, one for each secondary system.

You can set up 1-to-N remote copy in any of the following configurations:

Four bidirectional remote copy pairs. Four unidirectional remote copy pairs.

Figure 4: 1-to-N remote copy on page 20 illustrates a 1-to-N configuration, where:

Unidirectional remote copy is maintained between a remote copy pair, System1 and System3. Bidirectional remote copy is maintained between a remote copy pair, System1 and System2.

1-to-N configuration 19

System 3

System1 System2

Primary volume group Z (groupZ)

Secondary volume group Z

(groupZ.r)

groupZ to groupZ.r

Indicates direction of data replication

groupY togroupY.r

Primary volume group Y (groupY)

Secondary volume group Y

(groupY.r)

groupX to groupX.rSecondary volume

group X (groupX.r)

Primary volume group X (groupX)

Figure 4: 1-to-N remote copy

M-to-N configurationIn an M-to-N remote copy configuration, bidirectional data replication takes place in a 4x4 fan-in, fan-outconfiguration.

Data replication occurs without the need for dedicated remote copy pairs.

The transport layer can be RCFC, RCIP, or FCIP, or a mixture of these, with up to five links per node. Onlyone RCIP link per node is provided; the other links may be RCFC or FCIP.

To change the transport layer between the members of a remote copy pair, you must first remove the targetsand set up all the groups again.

Replication modes can be synchronous periodic, asynchronous periodic, asynchronous streaming, or amixture of these.

Synchronous long-distance configurationA synchronous long distance (SLD) remote copy configuration is composed of two targets: one synchronousgroup and one asynchronous periodic group. In SLD remote copy, one primary system uses two backupsystems and participates in two remote copy pairs, one for each secondary system.

In an SLD configuration, remote copy volume groups from the primary system are replicated to the twoseparate target arrays simultaneously. Data is replicated to one target in synchronous mode and to thesecond in asynchronous periodic mode. The target systems must each have appropriate network connectionsto the source systems to support the replication mode being used. There is no requirement that the closer ofthe two secondary systems be replicated to synchronously.

While it is not a requirement, Hewlett Packard Enterprise recommends that remote copy be set up:

Synchronously between the primary system and the closer of the two secondary systems be replicated tosynchronously.

In asynchronous periodic mode between the primary system and the secondary system that is physicallyfarther apart (and therefore likely to share a lesser connection).

SLD configurations differ from 1-to-N configurations as follows:

20 M-to-N configuration

In SLD configurations, remote copy volumes on the primary system are in a remote copy relationship withtwo secondary volume groups. Virtual volumes in the primary system are included in two primary groups,one copied to a secondary system in synchronous mode, and one copied to the other secondary system inasynchronous periodic mode. The two primary groups can be started and stopped independently of eachother.

For the SLD volume groups, one remote copy pair must be configured in synchronous mode and the otherin asynchronous periodic mode.

The SLD volume groups on the two backup systems are configured with a standby link for additionalfailover and recovery options.

To set up SLD remote copy:

1. Remote copy is set up in synchronous mode between the primary system and one secondary system. Formore information, see Synchronous mode on page 140.

2. Remote copy is set up in asynchronous periodic mode between the primary system and secondary systemthat are physically farthest apart (and therefore share a lesser connection). For more information, see Asynchronous periodic mode on page 141.

The asynchronous periodic connection can be either all IP connections or, if all the SLD systems are four-node storage systems, all FC over IP network connections. For more information, see Fibre Channel overIP networks on page 23 and IP Networks on page 23.

NOTE:

SLD remote copy links can be bidirectional between two HPE 3PAR StoreServ Storage systems that arein synchronous relationship with each other. This bidirectional synchronous relationship enablescustomers to configure two SLD configurations among three HPE 3PAR StoreServ Storage systems.

Figure 5: SLD remote copy on page 21 illustrates an SLD remote copy configuration.

Primary system(SystemA)

Secondary system(SystemB)

Secondary system(SystemC)

Asynchronousperiodic mode

(Standby link)

Synchronousmode

Secondary volume group A

(groupA.r1)

Primary volume group A (groupA)

Secondary volume group A

(groupA.r2)

Figure 5: SLD remote copy

Because SLD configurations include a standby link, as illustrated in Figure 5: SLD remote copy on page 21,this configuration allows for an alternate replication path and recovery path during a failover.

3PAR Remote Copy configurations 21

Selecting network connectionsProcedure

1. Review possible network connections.

IP Networks on page 23 Fibre Channel networks on page 22 Fibre Channel over IP networks on page 23

2. Review general network information for remote copy.

Reviewing 3PAR Remote Copy requirements on page 14

Network connection typesStorage systems in a remote copy pair are connected through a dedicated link or through a network, asillustrated in Figure 6: Remote copy links on page 22.

Node pair Node pair

TCP/IP networkor

FC SAN

3PAR

3PAR

3PAR

3PAR

Figure 6: Remote copy links

RCFC uses a proprietary HPE 3PAR Remote Copy protocol that optimizes synchronous replication,eliminating the need to implement proprietary write-acceleration optimization into the network (which mightrequire additional licenses and administration).

RCIP connects two systems over GigE ports. FCIP is RCFC that is extended over a long-distance wide area network (WAN) using FCIP routers. Where

latency and bandwidth are not concerns, and where the anticipated amount of data to be replicated ishigh, FCIP can be a better choice than RCIP over network adapter (NIC). FCIP allows asynchronousperiodic data replication over longer distances, without introducing network adapter (NIC) into the SAN.

Fibre Channel networksRCFC can be set up only on storage systems that communicate over FC SAN.

Be sure that you understand the FC SAN that is used to connect the storage systems. Remote Copy systems must be configured to be in the same FC SAN and zone.

Each storage system should have a pair of HBAs installed for load sharing and fault tolerance.

Before HPE 3PAR OS 3.1.2, an RCFC transport layer required that an HBA on at least two different nodesin the HPE 3PAR StoreServ Storage system be configured for and dedicated to remote copy. In addition,the front-end ports on an HBA had to be entirely configured for RCFC; their use could not be for differenttransport methods.

For HPE 3PAR OS 3.1.2 and later, the 3PAR StoreServ 7000 storage allowed ports on an HBA to beconfigured individually for both host and remote copy support. The HBA can be shared by the host and

22 Selecting network connections

RCFC only; it cannot be shared by RCFC and DISK; by the host and DISK; or by the host, RCFC, andDISK. All other storage platforms still needed the entire front-end HBA to be configured for RCFC.

As of HPE 3PAR OS 3.1.2 MU2, the same HBA port configuration functionality that is allowed on 3PARStoreServ 7000 Storage systems is allowed on 3PAR StoreServ 10000 Storage systems.

For newer storage systems, such as the 3PAR StoreServ 8000 Storage and the 3PAR StoreServ 20000Storage, individual ports can be set either on a front-end HBA for RCFC or for host connectivity.

IP NetworksThe network adapter (NIC) interface and the management Ethernet port of the HPE 3PAR StoreServ Storagesystem controller node must be on different IP subnets. The remote copy subnet can be shared with other I/Otraffic, but a guaranteed amount of bandwidth must be dedicated to remote copy on shared subnet.

If you configure the interface and port on the same subnet, remote copy packets might go over themanagement port and would no longer be available to the HPE 3PAR Remote Copy.

Hosts that access the HPE 3PAR StoreServ Storage systems for management purposes must not be on thesame subnet as the RCIP ports.

If you add host computers to the remote copy subnet, IP packets might arrive through the managementinterfaces and leave through the RCIP interfaces.

NOTE:

Be sure that you understand the IP network that will be used to connect the storage systems. Industry-standard rules governing IP networks apply.

Fibre Channel over IP networksIn a Fibre Channel over IP (RCFC over IP) network setup, on all systems, use FC connections that passthrough routers to cross an IP network.

Synchronous replication mode is not allowed when running RCFC over a SAN fabric extended over IP.

For more information, see Volume group replication modes on page 139.

IP Networks 23

Gathering setup informationProcedure

1. Contact your network administrator to obtain:

IP addresses or 64-bit World Wide Name (WWN) address information for the interfaces of the storagesystems

Gateway IP addresses, netmask, and IP addresses for each link Any additional details about the network connections that might be useful

2. Verify that the firewall settings allow the remote copy systems access to TCP port 5785 and port 5001.

24 Gathering setup information

Setting the transport layerProcedure

1. Review transport layer requirements. See:

Transport layer considerations on page 252. Set the transport layer. See:

Remote copy over IP on page 26 Setting up remote copy over Fibre Channel on page 33 Setting up RCFC over an IP network on page 37

For more information about the CLI commands in this chapter, see:

Remote copy command descriptions on page 310 HPE 3PAR Command Line Interface Reference, available at the following website:

Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/storage/docs)

Transport layer considerations

RCIPFor RCIP, each storage system in the remote copy configuration must have at least two nodes.

For RCIP configurations, the array management interface cannot be on the same subnet as the RCIPnetwork.

For RCIP, each network adapter (NIC) interface must use a unique IP address.

With RCIP, a pair of IP ports on the node pairs in an array may have a remote copy relationship with up to twoother arrays. In other words, a pair of RCIP ports on an array may send data to up to two different remotecopy targets on two different arrays, and may be the remote copy target for those same two arrays.

The network used by RCIP does not have to be dedicated to remote copy, but there should be a guaranteednetwork bandwidth (minimum of 500 KB/s) between any pair of arrays. Guaranteed bandwidth on the networkis especially important when replicating synchronously over RCIP; the bandwidth must be large enough toensure that no performance issues arise from replicating data synchronously. For asynchronous periodicreplication, the bandwidth must be large enough to ensure that the RPO can be met.

RCFCFor RCFC, each storage system should have a pair of HBAs installed. The HBA pair is required for loadsharing and fault tolerance. The HBAs in each storage system connect those systems through FC SAN, usingFC cable connections (see Figure 7: Remote copy links on page 26).

NOTE:

When configuring an RCFC port, ensure the IntCoal attribute is disabled. For instructions on how todisable this attribute, see Disabling IntCoal on page 34.

Setting the transport layer 25

http://www.hpe.com/info/storage/docs

Node pair Node pair

TCP/IP networkor

FC SAN

3PAR

3PAR

3PAR

3PAR

Figure 7: Remote copy links

For HPE 3PAR OS 3.1.1 and earlier, the pair of HBAs used for RCFC links must be reserved for exclusiveuse by HPE 3PAR Remote Copy. For HPE 3PAR OS 3.1.3 and later, individual ports can be configured forRCFC and host-connect on a common HBA, for the following HPE 3PAR StoreServ Storage systems:

3PAR StoreServ 20000 Storage 3PAR StoreServ 10000 Storage 3PAR StoreServ 9000 Storage 3PAR StoreServ 8000 Storage 3PAR StoreServ 7000 Storage

For more information, see Configuring ports for RCFC on page 33.

Network address translationHPE 3PAR Remote Copy does not support network address translation (NAT) over RCIP or FCIP.

Remote copy over IP

RCIP initial remote copy pairFigure 8: Network and RCIP setupexample initial pair on page 26 illustrates the initial remote copypair in an RCIP configuration.

System1 System2

TCP/IP network

3PAR 3PAR

Figure 8: Network and RCIP setupexample initial pair

26 Network address translation

RCIP port configurationFor RCIP configurations, each link between a remote copy pair is a logical link between a controller node onone storage system and a controller node on the other storage system in the pair. These links use a networkadapter (NIC) port from each of the nodes in the storage systems that belong to the remote copy pair.

RCIP configurations can use up to eight links between systems. Up to eight nodes can each have onenetwork adapter (NIC) port contributing links to an RCIP remote copy pair.

If these ports were not set up during the initial setup of the storage system, or if the configuration haschanged, reconfigure the ports before you set up the remote copy transport layer.

CAUTION:

The network adapter (NIC) interface and the management Ethernet port of the HPE 3PAR StoreServStorage controller node must be on different IP subnets.

If the management interface and RCIP ports are configured on the same subnet, remote copy packetsmight go over the management port, and would therefore not be available to the HPE 3PAR RemoteCopy software.

Setting up the remote copy interface for RCIP

Procedure

1. To start remote copy, issue the following command:startrcopy

2. Issue the following command for an Ethernet port on one remote copy system:cli% controlport rcip addr Where:

IP address assigned to the Ethernet port Netmask to be assigned Location of a primary system Ethernet port, expressed as node:slot:port

3. To confirm that you want to make the gateway change, enter y.4. Repeat for each RCIP port on each HPE 3PAR StoreServ Storage used in the remote copy configuration.5. Issue the following command on each system:

cli% showport -rcip

6. Compare the IP addresses and netmask with your RCIP configuration settings. For example:

N:S:P State ---HwAddr--- IPAddr Netmask Gateway MTU Rate Duplex AutoNeg0:3:1 ready 000423CBF68C 10.100.24.107 255.255.255.0 -- 15001Gbps Full Yes1:3:1 ready 000423CBF693 10.101.24.107 255.255.255.0 -- 1500 1Gbps Full Yes

For more information about the showport -rcip command, see:showport -rcip output does not match RCIP configuration settings on page 28

RCIP port configuration 27

showport -rcip output does not match RCIP configuration settingsSymptom

The showport -rcip command output does not match your RCIP configuration settings.

Action

To reconfigure the addresses, repeat the following procedure:

Setting up the remote copy interface for RCIP

Setting the gatewayBecause the storage systems in the remote copy configuration may be on different subnets, you must set thegateways for each system. To set the gateway, follow these steps:

Procedure

1. Issue the following command for an Ethernet port on one system:cli% controlport rcip gw Where:

Gateway IP address to assign to the local Ethernet port Location of a local Ethernet port

2. To confirm that you want to make the gateway change, enter y.3. Repeat 1 on page 28 and 2 on page 28 for each Ethernet port on each storage system used in the remote

copy configuration.4. Issue the following command on each system:

cli% showport -rcip

5. Verify that the Gateway column displays the correct gateway IP address:

N:S:P State ---HwAddr--- IPAddr Netmask Gateway MTU Rate Duplex AutoNeg0:3:1 ready 000423CBF68C 10.100.24.107 255.255.255.0 10.100.24.1 1500 1Gbps Full Yes1:3:1 ready 000423CBF693 10.101.24.107 255.255.255.0 10.101.24.1 1500 1Gbps Full Yes

Gateway address does not match RCIP configuration settings

Symptom

When you issue the showport -rcip command, the gateway address does not match your RCIPconfiguration settings.

Action

To reconfigure the gateway address, repeat the following procedure:

28 showport -rcip output does not match RCIP configuration settings

Setting the gateway

Verifying that the servers are connectedTo verify that the servers are connected, follow these steps:

Procedure

1. Issue the following command:cli% controlport rcip ping Where:

Interface from which to ping, expressed as node:slot:port IP address on the secondary system to ping

For example:

cli% controlport rcip ping 10.101.24.108 0:3:1 PING 10.101.24.108 (10.101.24.108) from 10.100.24.107 : 56(84) bytes of data.64 bytes from 10.101.24.108: icmp_seq=1 ttl=253 time=0.325 ms --- 10.101.24.108 ping statistics ---

1 packets transmitted, 1 received, 0% packet loss, time 0msrtt min/avg/max/mdev = 0.325/0.325/0.325/0.000 ms

2. Issue the command in step 1 on page 29 once for each interface on each system in the configuration.

NOTE:

Because of the STP and MAC address learning, you might need to ping each system several timesbefore the systems update all tables and the ping succeeds.

For more information about the controlport rcip ping command, see:The controlport rcip ping command does not succeed on page 29

The controlport rcip ping command does not succeedSymptom

The controlport rcip ping command does not work after repeated attempts.

Action

1. Check the setup:

Use the showport rcip ping command to test connectivity between all IP interfaces on all remotecopy systems.

Use the controlport -rcip command to verify that the network adapters (NICs) are all in theready state.

Verify all IP addresses, netmasks, gateways, and physical connections. Verify that your firewall is set to allow traffic over the designated RCIP ports (TCP 5785, 5001).

Verifying that the servers are connected 29

Verify with your network administrator that you do not have duplicate IP addresses in your network.

NOTE:

You may need to refer to your server OS for the necessary tools to help you detect duplicate IPaddresses in your network. For more information, see:

How to: Detect Duplicate IP Address With arping command under Linux

http://www.cyberciti.biz/faq/linux-duplicate-address-detection-with-arping/ Detection of duplicate IP addresses by Microsoft TCP/IP

https://support.microsoft.com/en-us/kb/120599

Verify that the MTU settings are correct. For more information, see Increasing MTU. Verify the controlport rcip speed settings. For more information, see controlport in the

HPE 3PAR Command Line Interface Reference, available at the following website:

Hewlett Packard Enterprise Information Library (http://www.hpe.com/info/storage/docs)2. If the pings still do not succeed, seek help from a network administrator.

CAUTION:

Do not proceed with the rest of the remote copy setup until pings succeed between the remote copynetwork adapter (NIC) ports on all the storage systems in the remote copy configuration.

Valid ping tests for the HPE 3PAR StoreServ Storage are gateway ping, remote gateway ping, or target-port ping.

Checking RCIP link throughput and latencyBy default, the checkrclink command uses port 5001. There is, however, an optional parameter that allowsyou to specify a different port number:

cli% checkrclink startclient [] []cli% checkrclink startserver [options] []] Verify that the firewall settings allow the remote copy systems access to TCP port 5001 (default).

NOTE:

It is not advisable to use port 5785 as the TCP port used to run the checkrclink command. Doing socan have an adverse effect on existing remote copy links.

To check link throughput and latency, follow these steps:

Procedure

1. Ensure that the systems for which you are checking links are not displaying signs of saturation.2. Starting with the secondary system, issue the following command on a system in the remote copy pair

(System2):cli% checkrclink startserver [options] [] Where:

30 Checking RCIP link throughput and latency

http://www.cyberciti.biz/faq/linux-duplicate-address-detection-with-arping/https://support.microsoft.com/en-us/kb/120599http://www.hpe.com/info/storage/docs

The option -time , using an integer from 300 to 172800, is the time in seconds for the test torun. For example, if the command is checkrclink startserver -time 172800 0:2:1, theremote copy link check will run for 172,800 seconds (48 hours). If no time is specified, the default is172800.

Interface from which to check the link, expressed as node:slot:port IP address on the secondary system

3. On the secondary system in the remote copy pair (System1), issue the following command:cli% checkrclink startclient [port] Where:

Interface from which to check the link, expressed as node:slot:port IP address or WWN on the secondary system for which you are checking the link The number of seconds for the test to run, using an integer from 300 to 172800 (5 minutes to

48 hours) The TCP port

4. Issue the following command on the first secondary system in the remote copy pair (System2, the systemon which you issued the startserver command):cli% checkrclink stopserver

5. Repeat 2 on page 30 through 4 on page 31 on each link and each system in the configuration.

For information about increasing MTU, see:

Increasing MTU on page 31

Link throughput and latency are unsatisfactory

Symptom

Link throughput and latency are unsatisfactory.

Action

See Increasing MTU.

Increasing MTUIf the result of the checkrclink test shows a value greater than 1500 bytes for Max MTU, you can increasethe MTU size to 9000 bytes (1000 bytes, 1500 bytes, and 9000 bytes are supported options).

To increase the MTU, follow these steps:

Procedure

1. Issue the controlport rcip mtu command:cli% controlport rcip mtu 9000 Where represents the location of the network adapter (NIC) port, expressed asnode:slot:port, and the MTU value specified is the same value returned by the checkrclinkcommand for Max MTU.

2. Repeat the command for all remote copy network adapter (NIC) ports on each storage system.

Link throughput and latency are unsatisfactory 31

3. From a storage system, use the controlport rcip ping command to verify that the network supportsthe increased MTU size:

cli% controlport rcip ping -s 9000 -pf Where:

8972Test packet size IP address on the secondary system to ping Interface from which to ping

4. Use the controlport rcip ping command for each interface on each system in the configuration.

NOTE:

Because of the STP and MAC address learning, you might need to ping each system several timesbefore the server updates all tables and the ping succeeds. See:

The controlport rcip ping command does not succeed on page 32

5. After MTU has been verified, use the following commands to bring the ports up or down:cli% controlport rcip state up cli% controlport rcip state down

The controlport rcip ping command does not succeedSymptom

The pings do not succeed.

Action

1. Issue another set of pings without specifying a size:controlport rcip ping -pf

If this ping command succeeds, the network does not support 9000-byte MTU.2. Revert to 1500 MTU:

controlport rcip mtu 1500 3. If you are setting up remote copy servers, proceed to Setting up the remote copy servers on page 39.

For information about increasing MTU, see Increasing MTU.

Adding RCIP linksTo add RCIP links, follow these steps:

Procedure

1. Issue the following commands on the source HPE 3PAR StoreServ Storage:cli% admitrcopylink target3par 0:3:1:10.X.X.X (Source port target ip )cli% admitrcopylink target3par 1:3:1:10.X.X.X (Source port target ip )

2. Issue the following commands on the target HPE 3PAR StoreServ Storage:cli% admitrcopylink target3par 0:3:1:192.X.X.X (Source port target ip )cli% admitrcopylink target3par 1:3:1:192.X.X.X (Source port target ip )

32 The controlport rcip ping command does not succeed

To change the IP addresses on the RCIP ports, you must first dismiss the remote copy links for the ports withthe dismissrcopylink command. Next, change the IP addresses using the controlport command andre-create the remote copy links using the admitrcopylink command.For information about removing RCIP links, see:

Removing RCIP links on page 33

Removing RCIP linksTo remove RCIP links, follow these steps:

Procedure

1. Issue the following commands on the source HPE 3PAR StoreServ Storage:cli% dismissrcopylink target3parname 0.3.1:10.X.X.X (Source port targer ip )cli% dismissrcopylink target3parname 1.3.1:10.X.X.X (Source port targer ip )

2. Issue the following commands on the target HPE 3PAR StoreServ Storage:cli% dismissrcopylink target3parname 0.3.1:192.X.X.X (Source port targer ip )cli% dismissrcopylink target3parname 1.3.1:192.X.X.X (Source port targer ip )

For information about adding RCIP links, see:

Adding RCIP links on page 32

Setting up remote copy over Fibre ChannelFigure 9: Initial remote copy pair in RCFC setup on page 33 illustrates the initial remote copy pair in anRCFC configuration.

System1 System2

FC SANnetwork

3PAR 3PAR

Figure 9: Initial remote copy pair in RCFC setup

Configuring ports for RCFCFor RCFC configurations, each link between a remote copy pair is a physical link between a controller nodeon one storage system and a controller node on the other storage system in the pair. These links use up tofour 8 Gb/s or 16 Gb/s FC adapter ports from each of the nodes in the storage systems that belong to theremote copy pair.

If these ports were not set up during the initial setup of the storage system, or if the configuration haschanged, reconfigure the ports before you set up the remote copy transport layer.

To configure the ports, use the controlport config rcfc command.

Removing RCIP links 33

CAUTION:

Each pair of RCFC ports that support an RCFC link must exist in an exclusive zone. Fabric zonescannot be shared.

NOTE:

When configuring an RCFC port, ensure the IntCoal attribute is disabled.

More information

Disabling IntCoal on page 34

Disabling IntCoalWhen configuring an RCFC port, ensure the IntCoal attribute is disabled. You can disable IntCoal CLIcommand in the following situations:

Prior to configuring an RCFC port On a newly configured inactive RCFC port On an RC port that is already active

NOTE:

Disabling an RC port that is already active is disruptive. After disabling a host port, wait 5-10 minutesfor the port to stabilize and verify the port is back online prior to taking action on another host port

Procedure

1. Issue the controlport intcoal disable where: is the port, in Node:Slot:Port format, for which you want to disable IntCoal.

Setting up dedicated node pairs for RCFCRCFC requires a dedicated node pair for each secondary system, as shown in Figure 10: RCFC dedicatednode pairs on page 35.

34 Disabling IntCoal

Node 0 Node 1

Primary storagesystem (System1)

Secondary storagesystem (System2)

Secondary storagesystem (System3)

Node 0 Node 1

Node 2 Node 3 Node 0 Node 13PAR 3PAR 3PAR 3PAR

3PAR 3PAR 3PAR 3PAR

Figure 10: RCFC dedicated node pairs

In Figure 10: RCFC dedicated node pairs on page 35:

FC interfaces on nodes 0 and 1 on the primary system connect to FC interfaces on