guide hpe 3par remote copy software user...selecting an initial synchronization method for...

HPE 3PAR Remote Copy Software UserGuide

Part Number: QL226-10559Published: January 2019

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

© Copyright 2019 Hewlett Packard Enterprise Development LP

NoticesThe information contained herein is subject to change without notice. The only warranties for HewlettPackard Enterprise products and services are set forth in the express warranty statements accompanyingsuch 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 containedherein.

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, ComputerSoftware Documentation, and Technical Data for Commercial Items are licensed to the U.S. Governmentunder vendor'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 PackardEnterprise website.

AcknowledgmentsGoogle™ is a trademark of Google Inc.

Linux® is a trademark of Linus Torvalds in the U.S. and other countries.

Microsoft®, Windows®, and Hyper-V® are either registered trademarks or trademarks of MicrosoftCorporation in the United States and/or other countries.

Mozilla® and Firefox® are trademarks of Mozilla Incorporated.

Red Hat® is a trademark of Red Hat, Inc. in the United States and other countries.

UNIX® is a registered trademark of The Open Group.

VMware®, VMware® ESX®, VMware®ESXi™, VMware®vCenter™, and VMware vSphere® are U.S.registered trademarks of VMware, Inc.

Contents

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

Remote copy setup....................................................................... 13System access to set up Remote Copy........................................................................... 13Reviewing 3PAR Remote Copy requirements..................................................................13

Prerequisites for setting up Remote Copy.............................................................13Best practices for Remote Copy............................................................................14System restrictions................................................................................................ 14Software restrictions..............................................................................................15Remote copy and virtual domains......................................................................... 15

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

Unidirectional 1-to-1 configuration.........................................................................16Bidirectional 1-to-1 configuration...........................................................................17N-to-1 configuration...............................................................................................171-to-N configuration...............................................................................................18M-to-N configuration..............................................................................................19

Synchronous long-distance Remote Copy configuration................................................. 19

Selecting network connections....................................................21Network connection types................................................................................................ 21

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

Gathering setup information........................................................ 23

Setting the transport layer............................................................24Transport layer considerations......................................................................................... 24

RCIP......................................................................................................................24RCFC.....................................................................................................................24Network address translation..................................................................................25

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

3

Increase Maximum Transmission Unit (MTU)....................................................... 31Add RCIP links...................................................................................................... 32Remove RCIP links............................................................................................... 33

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

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

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

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......................................................................................... 461-to-N remote copy considerations.................................................................................. 47Verifying connectivity between remote copy pairs for M-to-N setup................................ 48Setting up the primary system for M-to-N remote copy....................................................48Setting up the secondary system for M-to-N remote copy............................................... 49Checking the links between systems for M-to-N remote copy......................................... 50Verifying that virtual volumes are created for M-to-N remote copy.................................. 51Creating volume groups for M-to-N remote copy............................................................. 52Selecting an initial replication method for M-to-N remote copy........................................55Starting initial replication for M-to-N remote copy............................................................ 55

Setting up SLD remote copy........................................................ 57SLD remote copy considerations..................................................................................... 57Verifying connectivity between Remote Copy pairs for SLD............................................ 58Setting up the primary system for SLD remote copy........................................................58Setting up the backup systems for SLD remote copy...................................................... 60SLD remote copy example...............................................................................................62Checking the links between systems for SLD remote copy............................................. 66Verifying that virtual volumes are created for SLD remote copy...................................... 68Creating volume groups for SLD remote copy................................................................. 69Starting initial replication for SLD remote copy: copying data directly from primaryvolume groups..................................................................................................................71Failover and failback behavior of individual remote copy groups in SLD configuration... 72

Normal SLD operation...........................................................................................72SystemA-to-SystemB failover for an individual remote copy group...................... 73SystemA-to-SystemC failover in SLD remote copy configuration......................... 75Double failover.......................................................................................................78

Setting up a unidirectional configuration................................... 79Example unidirectional remote copy setup...................................................................... 79Verify connectivity between unidirectional Remote Copy pairs........................................81Setting up the primary system for unidirectional remote copy......................................... 82Setting up the secondary system for unidirectional remote copy.....................................83

4

Checking the links between systems for unidirectional remote copy............................... 84Verifying that virtual volumes are created for unidirectional remote copy........................ 85Creating volume groups for unidirectional remote copy...................................................85Selecting an initial replication method for unidirectional remote copy..............................88Starting initial replication for unidirectional remote copy: copying data directly fromprimary volume groups.....................................................................................................89

Setting up a bidirectional configuration......................................90Example bidirectional setup............................................................................................. 90Setting up the systems for bidirectional remote copy.......................................................92Creating volume groups for bidirectional remote copy.....................................................93Selecting an initial synchronization method for bidirectional remote copy....................... 96Starting initial synchronization for bidirectional remote copy: copying data directlyfrom primary volume groups.............................................................................................97

Remote copy management.................................................................. 98

Stopping, starting, or removing remote copy...........................100Stopping and restarting remote copy............................................................................. 100Stopping and starting remote copy groups.................................................................... 100Removing remote copy completely................................................................................ 101

Viewing remote copy system information................................ 102How remote copy tracks synchronization details........................................................... 103

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

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

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

Remote copy pairs and targets..................................................107Remote copy pairs......................................................................................................... 107Remote copy targets...................................................................................................... 107Target definitions............................................................................................................ 108Remote copy secondary system.................................................................................... 109

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

Remote copy links....................................................................... 111Sending links.................................................................................................................. 111

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

Receiving links................................................................................................................117

5

Converting a 3PAR Remote Copy 1:1 configuration to anSLD configuration........................................................................118

Converting an asynchronous periodic remote copy group to an SLD remote copygroup.............................................................................................................................. 119Converting an SLD remote copy group to an asynchronous periodic remote copygroup.............................................................................................................................. 119

Working with virtual volumes.....................................................120Creating remote copy virtual volumes............................................................................120Growing virtual volumes.................................................................................................122Renaming virtual volumes..............................................................................................122Creating CPGs and virtual volumes............................................................................... 123

Common provisioning groups..............................................................................123Virtual volumes used with remote copy...............................................................124

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

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

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

Unidirectional volume groups.............................................................................. 132Bidirectional volume groups................................................................................ 133

Changing the remote copy mode for a volume group.................................................... 134Manually resynchronizing volume groups...................................................................... 135Changing secondary volume groups to primary volume groups.................................... 136

Changing a single volume group.........................................................................136Changing all volume groups on a system........................................................... 137

Volume group policies.................................................................................................... 137auto_recover policy ....................................................................................... 137no_auto_recover policy .................................................................................137auto_failover policy ..................................................................................... 138no_auto_failover policy ...............................................................................138auto_failover_ext policy .............................................................................138no_auto_failover_ext policy ...................................................................... 139over_per_alert policy ................................................................................... 139no_over_per_alert policy .............................................................................139path_management policy .................................................................................139no_path_management policy .......................................................................... 139auto_synchronize policy ...............................................................................140

6

no_auto_synchronize policy ........................................................................ 140mt_pp policy .......................................................................................................140no_mt_pp policy ................................................................................................ 140RemoteCopyHostThrottling policy.............................................................. 140Secondary system cannot be contacted............................................................. 141Automatically restarting volume groups.............................................................. 141Generating alerts for slow resynchronization of asynchronous periodicvolume groups.....................................................................................................142

Volume group replication modes....................................................................................142Synchronous mode............................................................................................. 143Asynchronous periodic mode.............................................................................. 144Asynchronous streaming mode...........................................................................145

Synchronization..............................................................................................................146Types of synchronization for Remote Copy.........................................................146Limits on volumes that concurrently synchronize................................................147Asynchronous periodic mode volume groups..................................................... 147Synchronous mode volume groups.....................................................................151Asynchronous streaming mode volume groups.................................................. 152Setting snapshot frequency for asynchronous streaming mode......................... 153

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

Limiting throughput for asynchronous periodic volume groups........................... 156Limiting throughput for asynchronous streaming volume groups........................156Removing throughput limits.................................................................................157

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

3PAR Peer Persistence with transparent failover.................... 159Peer Persistence requirements......................................................................................1593PAR Peer Persistence..................................................................................................160

Manual transparent failover.................................................................................164Automatic transparent failover.............................................................................170

Quorum Witness operations...........................................................................................170Handling automatic transparent failover..............................................................171Link and communication failure scenarios.......................................................... 172

Path management policies.............................................................................................177Enabling the path_management policy .......................................................................178Disabling the path_management policy ......................................................................178Setting a timeout value for automatic failover................................................................ 178Peer Persistence coexistence with other remote copy groups...................................... 1793PAR Peer Persistence with multiple targets.................................................................179

Converting an existing SLD configuration .......................................................... 179Converting an existing Peer Persistence configuration ......................................180

Overriding failsafe state................................................................................................. 180

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

Error handling..............................................................................184

7

Synchronization states................................................................................................... 184Timeouts for remote copy failure....................................................................................185

Link heartbeat timeout.........................................................................................185Target timeout......................................................................................................185

Failure of a single link.................................................................................................... 186Target failure...................................................................................................................186

Target link failure on asynchronous streaming volume groups........................... 186Manually restarting remote copy......................................................................... 186Target link failure on synchronous volume groups.............................................. 187Restarting synchronous volume groups after link recovery.................................187Target failure on asynchronous periodic volume groups..................................... 188Resynchronizing asynchronous periodic volume groups after link recovery.......188

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

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

Read errors.................................................................................................................... 190Read errors during initial synchronization........................................................... 190Read errors during synchronization after restart of synchronous volumegroups..................................................................................................................190Read errors during synchronization after restart of asynchronous streamingvolume groups.....................................................................................................191Read errors during resynchronization of asynchronous periodic volumegroups..................................................................................................................191

Recovering from disaster...................................................................193

Nondisruptive failover in 1-to-1 Remote Copy using PeerPersistence (3PAR GeoCluster environments).........................194

VMware vSphere Metro Storage Cluster configuration..................................................194Prerequisites: Before you begin nondisruptive failover.................................................. 195System information during normal operation................................................................. 198System information during failover.................................................................................199Performing a nondisruptive failover................................................................................200Troubleshooting a Peer Persistence nondisruptive failover........................................... 202

Disaster recovery for 1-to-1 configurations..............................204System information during normal operation................................................................. 207System information during failover for 1-to-1 configurations..........................................208

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

Recovering from disaster for 1-to-1 configurations........................................................ 210Failover in 1-to-1 remote copy configurations..................................................... 210Recovery in 1-to-1 remote copy configurations................................................... 211

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

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

8

System information during failover for N-to-1 configurations.............................. 222Recovering from disaster for N-to-1 configurations.............................................223

Disaster recovery for 1-to-N configurations....................................................................230System information during normal operation for 1-to-N configurations............... 232System information during failover for 1-to-N remote copy configurations..........234Recovering from disaster for 1-to-N configurations.............................................235

Disaster recovery for SLD configurations................................ 242System information during normal operation for SLD configurations.............................244System information during failover for SLD configurations............................................ 247

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

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

Failover to the asynchronous periodic secondary system with data transfer.................262Failing over in asynchronous periodic SLD remote copy configurations.............263Recovering asynchronous periodic mode in SLD remote copy configurations... 266

Failover to the asynchronous periodic secondary system (no data transfer).................275Failing over to the secondary system..................................................................276Recovering the secondary system...................................................................... 279

Handling secondary system failure................................................................................ 288Handling primary system failure.....................................................................................289

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

Disaster Recovery for Peer Persistence configurations......... 296

Reference.............................................................................................298

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

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

9

3PAR CLI remote copy commands............................................314Remote copy command descriptions............................................................................. 314Issuing remote copy commands.................................................................................... 316

HPE 3PAR Quorum Witness client.............................................317Create a quorum witness client configuration................................................................ 317Start the quorum witness client...................................................................................... 319Stop the quorum witness client...................................................................................... 320Remove the quorum witness client configuration...........................................................321Auto failover policies...................................................................................................... 322Quorum troubleshooting.................................................................................................322

Quorum status qualifier....................................................................................... 322Quorum Witness and other logs..........................................................................326

Remote copy snapshots.............................................................327Snapshots...................................................................................................................... 327

Volume space considerations..............................................................................327Snapshots in synchronous mode................................................................................... 328

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

Snapshots in asynchronous streaming mode................................................................ 329Snapshots in asynchronous periodic mode................................................................... 331

Snapshots taken during initial synchronization................................................... 331Snapshots taken during resynchronization......................................................... 331Snapshots and resynchronization failure in asynchronous periodic mode..........332Snapshots taken before or during disaster recovery...........................................332Snapshot replication in Remote Copy groups..................................................... 333

Support and other resources..................................................... 334Accessing Hewlett Packard Enterprise Support.............................................................334Accessing updates......................................................................................................... 334HPE 3PAR documentation............................................................................................. 335Websites.........................................................................................................................335Customer self repair.......................................................................................................336Remote support..............................................................................................................336Documentation feedback............................................................................................... 336

Glossary...............................................................................................337A................................................................................................................................................337C................................................................................................................................................337F................................................................................................................................................337G............................................................................................................................................... 337H................................................................................................................................................337I................................................................................................................................................. 338J................................................................................................................................................ 338K................................................................................................................................................338L................................................................................................................................................ 338M............................................................................................................................................... 338

10

O............................................................................................................................................... 338P................................................................................................................................................338Q............................................................................................................................................... 339R................................................................................................................................................339S................................................................................................................................................339T................................................................................................................................................340V................................................................................................................................................340W...............................................................................................................................................341

11

Setting the foundation for HPE 3PAR RemoteCopy

Procedure

1. Select your setup method.

Remote copy setup methods

2. Select a remote copy configuration.

3PAR Remote Copy configurations

3. 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 information

5. 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 remotecopy servers.

12 Setting the foundation for HPE 3PAR Remote Copy

Remote copy setupSystem access to set up Remote Copy

To set up Remote Copy, you must have access to one of the following tools:

• HPE 3PAR StoreServ Management Console SSMC where you can use the Remote Copy Setupwizard.

• HPE 3PAR CLI commands as described in the HPE 3PAR Remote Copy Software User Guide.

NOTE: As of SSMC 3.2, the SSMC supports all configurations and modes listed in the support matrix forHPE 3PAR OS 3.3.1. However, SSMC is recommended for basic 1-to-1 configurations. CLI commandsare recommended for more complex Remote Copy configurations, such as M-to-N and SLD.

Reviewing 3PAR Remote Copy requirementsProcedure

1. Review general considerations for all configurations.

• Prerequisites for setting up Remote Copy on page 13

• System restrictions on page 14

• Software restrictions on page 15

• Transport layer considerations on page 24

• Creating remote copy virtual volumes on page 120

2. Review considerations applicable to your remote copy configuration.

• 1-to-N remote copy considerations on page 47

• SLD remote copy considerations on page 57

Prerequisites for setting up Remote CopyEnsure the following requirements are met before setting up your Remote Copy system:

• At least two HPE 3PAR StoreServ Storage systems. You have access to a minimum of two HPE3PAR StoreServ Storage systems which are supported for Remote Copy.

See the HPE 3PAR Support Matrix and the HPE 3PAR Operating System Upgrade Planning Guidebased on your HPE 3PAR OS version.

• HPE 3PAR All-inclusive Multi-System Software License for all storage systems participating inRemote Copy replication.

See the HPE 3PAR StoreServ Storage Concepts Guide.

• IP or Fibre Channel networks. The physical connections between all storage systems used withRemote Copy are through an IP-capable network or a Fibre Channel (FC) SAN network.

See the SAN design Reference Guide at HPE Support: www.hpe.com/support/hpesc.

Remote copy setup 13

• Firewall allows traffic. Your firewall allows traffic over the designated Remote Copy over IP (RCIP)only ports, TCP 5785 and 5001.

• Unique IP addresses. All RCIP ports have unique IP addresses. For example: 10.100.32.0,10.100.32.1, 09.101.90.45.

• SSMC or the HPE 3PAR CLI. You have access to SSMC or the HPE 3PAR CLI.

This guide covers CLI commands. For SSMC, see the HPE 3PAR StoreServ Management Console3.1 User Guide.

Best practices for Remote CopyConsider the following best practices before setting up your Remote Copy system.

• Distance between the systems◦ Storage systems in the same room can be connected through IP switches, or through FC networks.

Longer distances require other topologies.

◦ For disaster recovery purposes, the distance between storage systems depends on the disasterfrom which you need to recover (for example, a local power outage verses a widespread naturaldisaster).

◦ In synchronous replication mode, the latency of Remote Copy writes increases with distance.

• Bandwidth

RCIP configurations can fully use all 1 Gbps or 10Gbs links during the synchronization process. If youuse networks with lower throughput, the throughput between systems running Remote Copy softwaremight be capped by the network speed.

• Connection requirements

Network connections (or transport methods) can be IP or FC.

• Data availability and speed◦ To maintain data availability, you must use at least two links to connect storage systems.

◦ Remote Copy requires at least two separate network connections between storage systems toensure 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, Remote Copy uses all theavailable links that are configured for the same Remote Copy target to transmit data in parallel.

◦ To limit the potential for data loss, Hewlett Packard Enterprise recommends that synchronous modereplication be used whenever the additional write latency will not exceed the maximum writelatency tolerable by the application whose data is being replicated.

System restrictions

• For more information about HPE 3PAR OS support levels, see the HPE 3PAR Operating SystemUpgrade 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.

14 Remote copy setup

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

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


Software restrictions

• HPE 3PAR Remote Copy does not support self-mirroring configurations. It cannot use a storagesystem to replicate its own primary volumes to itself.

• HPE 3PAR Remote Copy does not support multi-hop configurations. It cannot replicate a primaryvolume group to a secondary system and then replicate the volume group again from the secondarysystem to a third 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 writelatency induced by the target array, will not exceed the maximum write latency tolerable by theapplication whose data is being replicated.

Remote copy and virtual domainsHPE 3PAR Remote Copy checks for the presence of HPE 3PAR Virtual Domains (domains) on thesecondary system to verify that you have mirrored the virtual volume to the same secondary systemdomain name as the primary-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,see the HPE 3PAR Command Line Interface Administrator Guide.

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

If you are using volume autocreation, define the local user CPG and the target user CPG, as well as thelocal snapshot CPG and target snapshot CPG, when you create the group. All the CPGs defined mustshare the same 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 AdministratorGuide, the HPE 3PAR StoreServ Management Console User Guide, or the HPE 3PAR ManagementConsole Help.

These documents are available on the following website:


Remote copy setup 15

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

3PAR Remote Copy configurationsRemote copy configurations are based on the relationship between a pair of storage systems, known asthe remote copy pair. Within a remote copy pair, the primary storage system is the system that holds thevolumes that 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 16

◦ Bidirectional 1-to-1 configuration on page 17

◦ N-to-1 configuration on page 17

◦ 1-to-N configuration on page 18

• Synchronous long-distance Remote Copy configuration on page 19

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 145

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

Asynchronous streaming mode volume groups on page 152

Asynchronous streaming replication during normal operation on page 295

Asynchronous streaming replication during WAN failure on page 295

Setting snapshot frequency for asynchronous streaming mode on page 153

Snapshots in asynchronous streaming mode on page 329

Tracking asynchronous streaming volume groups on page 103

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:one system 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.

16 3PAR Remote Copy configurations

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

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.Each system provides backup for the other, according to the direction of replication specified for eachvolume group.

Figure 2: Bidirectional 1-to-1 remote copy on page 17 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)


(groupX.r)



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 secondary systemwith 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, aslong as the remote secondary system has the minimum number of nodes required to support the numberof source systems.

3PAR Remote Copy configurations 17

Figure 3: N-to-1 remote copy on page 18 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)


(groupX.r)

Primary volume group Z (groupZ)

System3


System2


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


System 3

System1 System2

Primary volume group Z (groupZ)

Secondary volume group Z

(groupZ.r)

groupZ to groupZ.r


groupY togroupY.r


Secondary volume group Y

(groupY.r)

groupX to groupX.rSecondary volume

group X (groupX.r)


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.Only one 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 thetargets and set up all the groups again.

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

Synchronous long-distance Remote Copy configurationA synchronous long distance (SLD) Remote Copy configuration is composed of three systems: twosystems in a synchronous Remote Copy configuration and the two synchronous systems in anasynchronous periodic relationship with the third system.

In an SLD configuration, Remote Copy volume groups from the primary system are replicated to the twoseparate target systems simultaneously. Data replicates to one target in synchronous mode and to thesecond in asynchronous periodic mode. The target systems must each have appropriate networkconnections to the source systems to support the replication mode being used.

Any or all storage systems in an SLD configuration can be two-node or four-node systems.

While it is not a requirement, Hewlett Packard Enterprise recommends that an SLD Remote Copy isconfigured:

3PAR Remote Copy configurations 19

• In synchronous mode between the primary system and the closer of the two secondary systems. Thechosen systems must be within supported network latency limitations for synchronous Remote Copy.

• In asynchronous periodic mode between the primary system and the secondary system that isphysically farther apart (and therefore likely to share a slower connection).

NOTE: SLD Remote Copy links can be bidirectional between two storage systems using synchronousmode. This bidirectional synchronous relationship enables customers to configure two SLD configurationsamong three storage systems.

Figure 5: SLD Remote Copy


Selecting network connectionsProcedure

1. Review possible network connections.

• IP Networks on page 22

• Fibre Channel networks on page 21

• Fibre Channel over IP networks on page 22

2. Review general network information for remote copy.

Reviewing 3PAR Remote Copy requirements on page 13

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

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 (whichmight require 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 bereplicated is high, FCIP can be a better choice than RCIP over network adapter. FCIP allowsasynchronous periodic data replication over longer distances, without introducing network adapter intothe 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.

Selecting network connections 21

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 differentnodes in the HPE 3PAR StoreServ Storage system be configured for and dedicated to remote copy. Inaddition, the front-end ports on an HBA had to be entirely configured for RCFC; their use could not befor different transport 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 andRCFC 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 on3PAR StoreServ 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 StoreServ20000 Storage, 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 StoreServStorage system controller node must be on different IP subnets. The remote copy subnet can be sharedwith other I/O traffic, but a guaranteed amount of bandwidth must be dedicated to remote copy on sharedsubnet.

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 onthe same 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.

22 Selecting network connections

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 thestorage systems

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

Gathering setup information 23

Setting the transport layerProcedure

1. Review transport layer requirements. See:

Transport layer considerations on page 24

2. Set the transport layer. See:

• Remote copy over IP on page 25

• Setting up remote copy over Fibre Channel on page 34

• Setting up RCFC over an IP network on page 38

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

• Remote copy command descriptions on page 314

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


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 totwo other arrays. In other words, a pair of RCIP ports on an array may send data to up to two differentremote copy targets on two different arrays, and may be the remote copy target for those same twoarrays.

The network used by RCIP does not have to be dedicated to remote copy, but there should be sufficientbandwidth to replicate the data being generated. Guaranteed bandwidth on the network is especiallyimportant when replicating synchronously over RCIP; the bandwidth must be large enough to ensure thatno 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.

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,using FC cable connections (see Figure 7: Remote copy links on page 25).

NOTE: When configuring an RCFC port, ensure the IntCoal attribute is disabled. For instructions onhow to disable this attribute, see Disabling IntCoal on page 34.

24 Setting the transport layer

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 configuredfor RCFC and host-connect on a common HBA, for the following HPE 3PAR StoreServ Storage systems:

• 3PAR StoreServ 20000 Storage





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

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 setup—example initial pair on page 25 illustrates the initial remote copypair in an RCIP configuration.

System1 System2

TCP/IP network

3PAR 3PAR

Figure 8: Network and RCIP setup—example initial pair

Setting the transport layer 25

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

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 HPE3PAR StoreServ Storage controller node must be on different IP subnets.

If the management interface and RCIP ports are configured on the same subnet, remote copypackets might go over the management port, and would therefore not be available to the HPE 3PARRemote Copy 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 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 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 setthe gateways 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 and 2 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:

Setting the gateway

Verifying that the storage systems are connectedIf the RCIP ports are not in a ready state after issuing the showport -rcip command, checkconnectivity between the storage systems.

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 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 severaltimes before 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 28

The controlport rcip ping command does not succeedSymptom


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

Solution 1

Action

1. Issue startrcopy and creatercopytarget commands and then try the controlport rcipping command.

2. Check the setup:

• Use the showport -rcip command to verify that the RCIP ports are all in the ready 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).

• 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 detectduplicate IP addresses 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 theHPE 3PAR Command Line Interface Reference, available at the following website:


3. If the pings still do not succeed, seek help from a network administrator.

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

Solution 2

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 configuring your Remote Copy system, continue with your configuration.

More information


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

• Verifying connectivity between remote copy pairs for M-to-N setup on page 48

• Verifying connectivity between Remote Copy pairs for SLD on page 58

• Verify connectivity between unidirectional Remote Copy pairs on page 81

• Increase Maximum Transmission Unit (MTU) on page 31

Check RCIP link throughput and latencyThe client-server program checkrclink can be used to check throughput and latency. checkrclink is usedinterchangeably on System1 and System2. checkrclink startserver is used on one system andcheckrclink 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 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] [] Where:

• The option, -time —Time in seconds for the test to run. Use an integer from 300 to172800. 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, thedefault is 172800.

• —Interface from which to check the link, expressed as node:slot:port• —IP address on the peer system (System1)• []—Optional server TCP port

3. On the other system in the Remote Copy pair (for example, System1), issue the following command:cli% checkrclink startclient [port] Where:

• —Interface from which to check the link, expressed as node:slot:port• —IP address on the peer system (System2) 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 specified in step 2, if any.

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 startservercommand):

cli% checkrclink stopserver

6. Repeat this process for each link in each system.

If the RCIP link throughput and latency is unsatisfactory, see:

Increase Maximum Transmission Unit (MTU) on page 31

Link throughput and latency are unsatisfactory

Symptom

Link throughput and latency are unsatisfactory.

Action

See Increasing MTU.

Increase Maximum Transmission Unit (MTU)The supported MTU settings are: 1000 bytes, 1500 bytes, and 9000 bytes. By default, RCIP connectionsuse a 1500 byte MTU setting because all vendor hardware supports this MTU size. Check with yournetwork administrator to determine the maximum MTU that can be set for your RCIP connections.

If the RCIP link throughput and latency is unsatisfactory (the result of the checkrclink test shows avalue greater than 1500 bytes for Max MTU), you can increase the MTU size to 9000 bytes.

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.

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

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


• 8972—Test 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.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. If the pings do not succeed:

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

b. Revert to 1500 MTU:controlport rcip mtu 1500

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

Add RCIP linksAdd one or more RCIP links to a remote copy target.

Procedure

1. Issue the following commands on the primary HPE 3PAR StoreServ Storage:cli% admitrcopylink :cli% admitrcopylink : Where:

• —specifies the name of the target created from the primary system with thecreatercopytarget command. For example, System2.

• :—specifies the node, slot, and port of the Ethernetport on the primary system and an IP address of the peer port on the secondary system.

For example:

cli% admitrcopylink System2 0:3:1:192.0.1.2


2. Issue the following commands on the secondary HPE 3PAR StoreServ Storage:cli% admitrcopylink :cli% admitrcopylink :


Where:

• —specifies the name of the target from the secondary system created with thecreatercopytarget command. For example, System1.

• :—specifies the node, slot, and port of the Ethernetport on the secondary system and an IP address of the peer port on the primary system.

For example:



Remove RCIP linksRemove one or more RCIP links created by the admitrcopylink command.

Procedure

1. Issue the following commands on the primary HPE 3PAR StoreServ Storage:cli% dismissrcopylink :cli% dismissrcopylink : Where:

• —specifies the name of the target created from the primary system with thecreatercopytarget command.

• :—specifies the node, slot, and port of the Ethernetport on the primary system and an IP address of the peer port on the secondary system.

For example:

cli% dismissrcopylink System2 0:3:1:192.0.1.2


2. Issue the following commands on the secondary HPE 3PAR StoreServ Storage:cli% dismissrcopylink :cli% dismissrcopylink : Where:

• —specifies the name of the target created from the secondary system with thecreatercopytarget command.

• :—specifies the node, slot, and port of the Ethernetport on the secondary system and an IP address of the peer port on the primary system.

For example:




Setting up remote copy over Fibre ChannelFigure 9: Initial remote copy pair in RCFC setup on page 34 illustrates the initial remote copy pair inan RCFC 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 controllernode on one storage system and a controller node on the other storage system in the pair. These linksuse up to four 8 Gb/s or 16 Gb/s FC adapter ports from each of the nodes in the storage systems thatbelong to the 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.

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

CAUTION: Each pair of RCFC ports that support an RCFC link must exist in an exclusive zone.Fabric zones cannot 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-10minutes for the port to stabilize and verify the port is back online prior to taking action on another hostport


Procedure

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 RCFCFor RCFC, use a dedicated node pair for each secondary system. Each FC interface on each node onthe primary Remote Copy system must connect to a dedicated FC interface on each node on the backupRemote Copy system. Utilizing like node pairs (node 0 and 1 is an example of a node pair) on eachstorage system is recommended, but is not a requirement.

Procedure

1. Connect FC interfaces on nodes 0 and 1 on the primary system to FC interfaces on backup System1nodes 0 and 1.

2. Connect FC interfaces on nodes 2 and 3 on the primary system to FC interfaces on backup System2nodes 0 and 1.

Node 0 Node 1

Primary storagesystem (System1)



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

Setting up remote copy interface for RCFC

Procedure

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


startrcopy2. Issue the following command for an FC adapter port on one storage system:

cli% controlport offline Where:

—FC adapter port, expressed as node:slot:port

Issuing this command will take the port offline, as shown in the following example:

cli% controlport offline 3:2:1Are you sure you want to run controlport offline on port 3:2:1?select q=quit y=yes n=no: y

3. Issue the following command:cli% controlport config rcfc -ct point -f Where:

• -ct point—point-to-point mode• —FC adapter port, expressed as node:slot:port

4. Record the port positions by issuing the showport -rcfc command .5. Repeat steps 2 through 4 for each port on each system in the remote copy configuration.

6. To verify that the FC communication links have been established, issue the following command:cli% showrctransport -rcfcThe FC adapter ports should appear, and the State column should display new. For example:

N:S:P Peer_Node_WWN Peer_Port_WWN State3:2:1 2FF70002AC00005F 23410002AC00005F new1:4:1 2FF70002AC00005F 21510002AC00005F new

NOTE: If the ports do not match the ports you recorded on your worksheet, then the wrong ports werespecified in step 3 .

Repeat the interface setup steps starting at 3, using the correct port IDs.

7. To initialize the FC adapter port, issue the controlport rcfc init command on one system:cli% controlport rcfc init -f Where: represents the location of the FC adapter port, expressed as node:slot:port.

8. To verify that the FC adapter port is ready to begin setting up the remote copy systems, issue thefollowing command:

cli% showrctransport -rcfcThe State column should display ready. For example:


cli% showrctransport -rcfcN:S:P Peer_Node_WWN Peer_Port_WWN State3:2:1 2FF70002AC00005F 23410002AC00005F ready1:4:1 2FF70002AC00005F 21510002AC00005F ready

NOTE: If the State column displays incomplete or new, then repeat 7 and 8 until the port is in aready state.

9. Repeat steps 7 through 8 for each RCFC port on each remote copy system.

Checking RCFC link throughput and latencyThe client-server program checkrclink can be used to check throughput and latency. checkrclink is usedinterchangeably on System1 and System2. checkrclink startserver is used on one system andcheckrclink 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 systems 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] Where:

• The [option], -time , is the time in seconds for the test to run. Use an integer from 300to 172,800, For example, if the command is checkrclink startserver -time 1728000:2:1, the Remote Copy link check will run for 172,800 seconds (48 hours). If no time is specified,the default is 172800.

• —Interface from which to check the link, expressed as node:slot:port.

For example:

System2 cli% checkrclink startserver 0:2:1Starting ServerTest length (secs): 172800Time now (secs): 1544720051Min run time (secs): 1544892851Running link test on: 0:2:1Local IP Addr: 12x.xxx.xxx.xxLocal Device name: FCNET

3. Make note of the Local IP Addr as it will be used in the next step.4. On the other system in the Remote Copy pair (for example, System1), issue the following command:

cli% checkrclink startclient Where:


• —Interface from which to check the link, expressed as node:slot:port• —Local IP address on the peer system (System1) from the previous step• —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 linkcheck will run for 172,800 seconds (48 hours).

5. Issue the following command on System2, (the system on which you issued the startservercommand):

cli% checkrclink stopserver

6. Repeat these steps on each link and each system in the configuration.

Setting up RCFC over an IP networkNOTE: You can configure only RCFC connections to communicate over an IP network for remote copy inasynchronous periodic mode. For more information, see Volume group replication modes on page142.

Procedure

1. Set up FC over IP on you

guide hpe 3par remote copy software user...selecting an initial synchronization method for...

Documents