HP 3PAR Remote Copy Software User s Guide

Transcription

1 HP 3PAR Remote Copy Software User s Guide This guide is for System and Storage Administrators who monitor and direct system configurations and resource allocation for HP 3PAR Storage Systems. HP Part Number: QL Published: February 2012

2 Copyright 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java and Oracle are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group. Documentation For the latest version of this document, go to navigate to your product page, click Support for your product, and then click Manuals.

3 Contents Introduction...10 Related Documentation...10 Typographical Conventions...10 Advisories...11 I Setting the Foundation for Remote Copy Planning Your Remote Copy Setup Strategy...13 Setup Instructions and Resources...13 Remote Copy System Locations...13 Additional Information Deciding on a Remote Copy Configuration...14 Unidirectional 1-to-1 Configuration...14 Bidirectional 1-to-1 Configuration...14 N-to-1 Configuration to-N Configuration...16 Synchronous Long Distance Configuration...17 If a Backup System Fails...18 If the Primary System Fails Choosing Network Connections...21 IP Networks...21 Fibre Channel Networks...22 Fibre Channel over IP Networks...22 General Considerations Considering Requirements and Restrictions...23 General Requirements...23 General System Restrictions...23 General Software Restrictions...24 Transport Layer Considerations...24 Virtual Volume Considerations...25 N-to-1 Considerations to-N Considerations...26 Synchronous Long Distance Considerations Gathering Setup Information...29 RCIP Initial Remote Copy Pair...29 RCIP Initial Remote Copy Pair Worksheet...30 RCIP Additional Remote Copy Pairs Worksheet...31 RCFC Remote Copy Pair Worksheet Setting the Transport Layer...33 Setting Up Remote Copy over IP...33 Configuring Ports for RCIP...33 Setting Up the Remote Copy Interface for RCIP...33 Setting the Gateway...34 Verifying the Servers Are Connected...35 Checking Link Throughput and Latency...36 Increasing MTU (Optional)...37 Setting Up Remote Copy over Fibre Channel...38 Configuring Ports for RCFC...38 Setting Up Dedicated Node Pairs for RCFC...39 Setting Up the Remote Copy Interface for RCFC...39 Contents 3

4 Checking Link Throughput and Latency...40 Setting Up RCFC over an IP Network...41 II Setting Up the Remote Copy Servers Setting Up 1-to-1 Remote Copy Setting Up N-to-1 Remote Copy...45 Example Remote Copy Pair for N-to-1 Setup...46 Verifying Connectivity between Systems...47 Setting Up the Primary System...47 Setting Up the Backup System...48 Checking the Links between Systems...49 Verifying Virtual Volumes Are Created for Remote Copy...50 Creating Remote Copy Volume Groups...50 Deciding on an Initial Replication Method...53 Starting Initial Replication: Copying Data Directly from Primary Volume Groups Setting Up 1-to-N Remote Copy Setting Up Synchronous Long Distance Remote Copy...56 Example Synchronous Long Distance Setup...56 Verifying Connectivity between Systems...58 Setting Up the Primary System...59 Setting Up the Backup Systems...59 Checking the Links between Systems...61 Verifying Virtual Volumes Are Created for Remote Copy...62 Creating Volume Groups for Synchronous Long Distance Remote Copy...62 Starting Initial Replication: Copying Data Directly from Primary Volume Groups Setting Up a Unidirectional Configuration...67 Example Unidirectional Setup...67 Verifying Connectivity between Systems...68 Setting Up the Primary System...68 Setting Up the Backup System...69 Checking the Links between Systems...70 Verifying Virtual Volumes Are Created for Remote Copy...71 Creating Remote Copy Volume Groups...71 Deciding on an Initial Replication Method...74 Starting Initial Replication: Copying Data Directly from Primary Volume Groups Setting Up a Bidirectional Configuration...76 Example Bidirectional Setup...76 Setting Up the Systems for Bidirectional Remote Copy...77 Creating Volume Groups for Bidirectional Remote Copy...78 Deciding on an Initial Replication Method...80 Starting Initial Replication: Copying Data Directly from Primary Volume Groups Using Tape for Initial Synchronization and Backup...82 III Managing Remote Copy Viewing Remote Copy System Information...86 How Remote Copy Tracks Synchronization Details...86 Tracking Synchronous Volume Groups...86 Tracking Asynchronous Periodic Volume Groups...86 Viewing Synchronization Task Information...87 Viewing More Detail for a Synchronization Task...88 Viewing Earlier Synchronization Tasks...88 Task Management Commands for Remote Copy Synchronizations Contents

5 15 Setting Volume Group Policies...89 Automatically Restarting Volume Groups...89 Generating Alerts for Slow Resynchronizations of Asynchronous Periodic Volume Groups Performing Manual Operations...91 Changing the Remote Copy Mode for a Volume Group...91 Manually Resynchronizing Volume Groups...92 Changing Secondary Volume Groups to Primary...93 Changing One Volume Group...93 Changing All Volume Groups on a System...93 Stopping and Starting Remote Copy...94 Removing Remote Copy Completely Modifying Virtual Volumes...95 Converting Standard Virtual Volumes...95 Growing Virtual Volumes...95 Renaming Virtual Volumes Limiting Throughput...97 Limiting Throughput for Asynchronous Periodic Volume Groups...97 Removing Throughput Limits Optimizing Performance...99 Optimizing RCIP Throughput by Increasing MTU Size...99 Avoiding RCIP Throughput Issues during Initial Synchronization...99 Optimizing Synchronization Speed over Distances Troubleshooting RCIP Autonegotiation Issues Considering Additional Impacts on Performance Volume Group Mode Distribution of Host Writes over RCIP GigE Links IV Recovering from Disaster Disaster Recovery for 1-to-1 Configurations System Information during Normal Operation Primary System (System1) Backup System (System2) System Information during Failover Synchronous Mode Asynchronous Periodic Mode Example Output after Primary System Failure Recovering from Disaster Failover Recovery Disaster Recovery for N-to-1 Configurations System Information during Normal Operation Backup System (System1) First Primary System (System2) Second Primary System (System3) System Information during Failover Synchronous Mode Asynchronous Periodic Mode Example Output after Primary System Failure Recovering from Disaster Failover Recovery Contents 5

6 22 Disaster Recovery for 1-to-N Configurations System Information during Normal Operation Primary System (System1) First Backup System (System2) Second Backup System (System3) System Information during Failover Synchronous Mode Asynchronous Periodic Mode Example Output after Primary System Failure Recovering from Disaster Failover Recovery Disaster Recovery for Synchronous Long Distance System Information during Normal Operation Primary System (SystemA) Synchronous Backup System (SystemB) Asynchronous Periodic Backup System (SystemC) System Information during Failover Synchronous Mode Asynchronous Periodic Mode Example Output after Primary System Failure Stages of Disaster Recovery Failing Over to the Synchronous Backup System Failover Recovery Failing Over to the Asynchronous Periodic Backup System (with Data Transfer) Failover Recovery Failing Over to the Asynchronous Periodic Backup System (No Data Transfer) Failover Recovery V Remote Copy Concepts Remote Copy Pairs and Targets Remote Copy Pairs Overview of Targets Target Definitions Remote Copy Target System System Roles and Direction of Data Flow Changing the Direction of Data Flow System Roles and Bidirectional Configurations Remote Copy Links Sending Links One Link per Node per Target Links per Remote Copy Pair Links per Multiple Remote Copy Pairs Receiving Links Virtual Volumes and CPGs Common Provisioning Groups How CPGs Allocate Space for Snapshots How CPGs Allocate Space for Virtual Volumes Basic Information about CPGs Creating a CPG Contents

7 Virtual Volumes Used with Remote Copy Thinly Provisioned Virtual Volumes Fully Provisioned Virtual Volumes Rules for Creating Remote Copy Virtual Volumes Volume Groups Why Use Volume Groups How Volume Groups Work Rules for Forming Volume Groups How Volume Groups Are Named Rules for Adding Snapshots to Volume Groups How Volume Groups Are Organized on the Remote Copy Pair Natural Direction of Replication Linking Virtual Volumes in Volume Groups Unidirectional Volume Groups Bidirectional Volume Groups Volume Group Modes Overview of Volume Group Modes Synchronous Mode Advantages of Synchronous Mode Latency in Synchronous Mode Asynchronous Periodic Mode Advantages of Asynchronous Periodic Mode Synchronization Types and Limits Types of Synchronization Limits on Volumes that Concurrently Synchronize Asynchronous Periodic Mode Volume Groups Full Synchronization Resychronization Setting Up Resynchronization for Asynchronous Periodic Mode How to Set the Synchronization Period Considerations for Setting the Synchronization Period Synchronous Mode Volume Groups Full Synchronization Resynchronization Remote Copy Snapshots Overview of Snapshots Why Use Snapshots Volume Space Considerations Snapshots in Synchronous Mode Snapshots and Initial Synchronization Failure Snapshots and Resynchronization Snapshots and Resynchronization Failure Snapshots Taken before or during Disaster Recovery If the Backup System Fails If the Primary System Fails Snapshots in Asynchronous Periodic Mode Snapshots Taken during Initial Synchronization Snapshots Taken during Resynchronization Snapshots and Resynchronization Failure Snapshots Taken before or during Disaster Recovery Error Handling Timeouts for Remote Copy Failure Contents 7

8 Timeouts and Transient Network Problems Failure of a Single Link Failure of All Links Link Failure and Synchronous Volume Groups Restarting Synchronous Volume Groups after Link Recovery Link Failure and Asynchronous Periodic Volume Groups Resyncing Asynchronous Periodic Volume Groups after Link Recovery Failure of a Storage System Failure of a Primary System Failure of a Backup System Write Errors Write Errors on the Primary System Write Errors on the Backup System Write Errors and Synchronous Volume Groups Restarting Synchronous Volume Groups after Write Errors Read Errors Read Errors during Initial Synchronization Read Errors during Synchronization after Restart of Synchronous Volume Groups Read Errors during Resynchronization of Asynchronous Periodic Volume Groups Sync States VI Appendices A Quick Setup Guide Quick Setup: RCIP Transport Layer Quick Setup: RCFC Transport Layer Quick Setup: Remote Copy Configurations Quick Setup: Unidirectional Remote Copy Quick Setup: Bidirectional Remote Copy Quick Setup: Synchronous Long Distance Remote Copy B Quick Disaster Recovery Guide Quick Recovery: 1-to-1, N-to-1, and 1-to-N Configurations Quick Recovery: Synchronous Long Distance Configurations C About the Remote Copy Commands Issuing Remote Copy Commands D The Remote Copy Commands admitrcopylink admitrcopytarget admitrcopyvv checkrclink controlport creatercopygroup creatercopytarget dismissrcopylink dismissrcopytarget dismissrcopyvv growvv histrcvv removercopygroup removercopytarget setrcopygroup setrcopytarget setvv showport Contents

9 showrcopy showrctransport startrcopy startrcopygroup statport statrcopy statrcvv stoprcopy stoprcopygroup syncrcopy E Remote Copy and Other Features Remote Copy and Virtual Domains Remote Copy Functionality Unavailable on Systems Index Contents 9

10 Introduction This guide provides the information you need to configure and use HP 3PAR Remote Copy Software. Remote Copy allows you to copy virtual volumes from one HP 3PAR Storage System to another. You can use these copies for backup and disaster recovery. To use Remote Copy, you must use the HP 3PAR Command Line Interface (CLI). For more information, see: The HP 3PAR InForm OS Command Line Interface Reference About the Remote Copy Commands (page 222) Related Documentation For Information About: Storage System concepts and terminology CLI commands and their usage Using the HP 3PAR Management Console to configure and administer HP 3PAR Storage Systems Using the HP 3PAR Command Line Interface (CLI) to configure and administer HP 3PAR Storage Systems Storage system hardware configurations, component numbering and layout, and system cabling Identifying storage system components and detailed alert information Platform-specific release levels See: HP 3PAR InForm OS Concepts Guide HP 3PAR InForm OS Command Line Interface Reference HP 3PAR InForm Management Console Help HP 3PAR InForm OS CLI Administrator s Manual HP 3PAR E-Class/F-Class Storage Systems and Third-Party Rack Physical Planning Manual HP 3PAR S-Class/T-Class Storage Systems Physical Planning Manual HP 3PAR InForm OS Messages and Operator s Guide HP 3PAR InForm OS Configuration Matrix To obtain a copy of this documentation, go to navigate to your product page, click Support for your product, and then click Manuals. Typographical Conventions Typeface ABCDabcd ABCDabcd ABCDabcd <ABCDabcd> <ABCDabcd> Meaning Used for dialog elements such as titles, button labels, and other screen elements. Used for paths and file names, and screen output. Used to differentiate user input from screen output. Used for variables in file names, paths, and screen output, and variables in user input. Used for variables in user input. Example When prompted, click Value to complete the installation. Open the file \gui\windows\setup.exe # cd /opt/3par/gui Modify the content string by adding the -P[root@(<x>)root] option after -jar inform.jar #./java -jar inform.jar -P<x> 10

11 Advisories NOTE: The InServ Storage Server has been rebranded as HP 3PAR Storage System. There are instances in this document where screenshots and/or menu items and command output refer to the HP 3PAR Storage System as InServ or InServ Storage Server. To avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. Always be careful when handling any electrical equipment. WARNING! Warnings alert you to actions that can cause injury to people or irreversible damage to data or the operating system. CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data. NOTE: guide. Notes are reminders, tips, or suggestions that supplement the procedures included in this Advisories 11

12 Part I Setting the Foundation for Remote Copy 1. Plan your setup strategy. 2. Decide on the Remote Copy configuration to use. 3. Choose the type of network connection to use. 4. Check the requirements and restrictions to make sure the system is prepared for the Remote Copy setup you are planning. 5. Obtain and organize the information about your network you ll need for the setup. 6. Configure the Remote Copy transport layer. Planning Your Remote Copy Setup Strategy (page 13) Deciding on a Remote Copy Configuration (page 14) Choosing Network Connections (page 21) Considering Requirements and Restrictions (page 23) Gathering Setup Information (page 29) Setting the Transport Layer (page 33) When you have set the foundation for your Remote Copy system, continue to Setting Up the Remote Copy Servers (page 42).

13 1 Planning Your Remote Copy Setup Strategy 1. Decide on a setup methodology. 2. Decide where to locate the HP 3PAR Storage Systems. 3. Review the list of additional resources that can help with setup. Setup Instructions and Resources (page 13) Remote Copy System Locations (page 13) Additional Information (page 13) Setup Instructions and Resources Depending on your comfort level and familiarity with HP 3PAR Remote Copy Software, use the following resources to help you set up your Remote Copy system: New User Established User Expert User If you are setting up Remote Copy for the first time, you can: Follow the setup steps, as relevant to your Remote Copy system, in each chapter of Setting the Foundation for Remote Copy (page 12), and Setting Up the Remote Copy Servers (page 42), of this User s Guide. Use the Remote Copy Setup wizard in the HP 3PAR InForm Management Console. If you are familiar with Remote Copy setup, you can use the Setup Tool appropriate for your Remote Copy transport layer: HP 3PAR Remote Copy Setup Tool for RCIP ( ) HP 3PAR Remote Copy Setup Tool for RCFC ( ) To obtain one of these documents, see HP s Business Support Center (BSC). If you are an expert Remote Copy user, see Quick Setup Guide (page 213). Remote Copy System Locations The backup storage system(s) can reside at the same location as the primary storage system, or the backup system(s) can reside at a remote location. To help ensure that disaster recovery operations are successful, at least one backup system should reside at a location remote from the primary system. Additional Information For more information about: Concepts and components of a Remote Copy system Requirements and restrictions See: Remote Copy Concepts (page 180) Considering Requirements and Restrictions (page 23) Setup Instructions and Resources 13

14 2 Deciding on a Remote Copy Configuration To decide on the best Remote Copy configuration for your system, review illustrations and descriptions of the possible configurations. Unidirectional 1-to-1 Configuration (page 14) Bidirectional 1-to-1 Configuration (page 14) N-to-1 Configuration (page 15) 1-to-N Configuration (page 16) Synchronous Long Distance Configuration (page 17) Remote Copy configurations are based on the relationship between a pair of storage systems, known as the Remote Copy pair. Within a Remote Copy pair, the primary storage system is the system that holds the volumes that are copied to the backup storage system. Unidirectional 1-to-1 Configuration A unidirectional 1-to-1 Remote Copy configuration is composed of one Remote Copy pair. Each storage system in the pair plays only one role: one system is the primary system, and one system is the backup system. In a unidirectional 1-to-1 configuration, the primary storage system holds only primary volume groups, and the backup storage system holds only secondary volume groups. Figure 1 Unidirectional 1-to-1 Remote Copy Bidirectional 1-to-1 Configuration A bidirectional 1-to-1 Remote Copy configuration is composed of one Remote Copy pair. Each storage system in the pair function as both the primary and backup system, and both systems contain both primary and secondary volume groups. Therefore, each system provides backup for the other, according to the direction of replication set for each volume group. 14 Deciding on a Remote Copy Configuration

15 Figure 2 Example bidirectional 1-to-1 Remote Copy N-to-1 Configuration An N-to-1 Remote Copy configuration is composed of multiple Remote Copy pairs. A maximum of four primary storage systems use the same backup storage system. NOTE: Because the backup system participates in one Remote Copy pair for each primary system, the backup system must have four or more controller nodes. You can set up N-to-1 Remote Copy configurations in either of the following arrangements: One bidirectional Remote Copy pair and multiple unidirectional pairs (one, two, or three unidirectional Remote Copy pairs, depending on the number of primary systems) All unidirectional configurations (one, two, three, or four unidirectional Remote Copy pairs, depending on the number of primary systems) NOTE: In an N-to-1 Remote Copy configuration, only one link can be bidirectional. Figure 3 (page 16) illustrates an example N-to-1 configuration in which: Bidirectional Remote Copy is maintained between Remote Copy pair System3 and System4. Unidirectional Remote Copy is maintained between Remote Copy pairs System1 and System4 and Remote Copy pairs System2 and System4. N-to-1 Configuration 15

16 Figure 3 N-to-1 Remote Copy 1-to-N Configuration A 1-to-N Remote Copy configuration is composed of multiple Remote Copy pairs. The single primary storage system can use a maximum of two backup storage systems. Therefore, the primary system participates in two Remote Copy pairs: one for each backup system. You can set up 1-to-N Remote Copy configurations in either of the following arrangements: One unidirectional Remote Copy pair and one bidirectional Remote Copy pair Two unidirectional Remote Copy pairs Figure 4 (page 17) illustrates an example 1-to-N configuration in which: Unidirectional Remote Copy is maintained between Remote Copy pairs System1 and System3. Bidirectional Remote Copy is maintained between Remote Copy pair System1 and System2. 16 Deciding on a Remote Copy Configuration

17 Figure 4 1-to-N Remote Copy Synchronous Long Distance Configuration A Synchronous Long Distance Remote Copy configuration is composed of two Remote Copy pairs. One primary system uses two backup systems and participates in two pairs: one for each backup system. Synchronous Long Distance configurations differ from 1-to-N configurations in that: Not every volume group on the Remote Copy systems that are participating in a Synchronous Long Distance configuration needs to be set up for Synchronous Long Distance replication. Each Synchronous Long Distance primary volume group targets two secondary volume groups. Therefore, the virtual volumes in a single primary volume group on the primary system are copied directly to two secondary volume groups, one on each of the two backup systems. For the Synchronous Long Distance volume groups, one Remote Copy pair must be configured in synchronous mode and the other in asynchronous mode. The Synchronous Long Distance volume groups on the two backup systems are configured with a standby link for additional failover and recovery options. Synchronous Long Distance Remote Copy is set up as follows: Synchronous Long Distance Configuration 17

18 1. Between the primary system and backup system that are physically closer to each other (and therefore share a high bandwidth/low latency connection), Remote Copy is set up in synchronous mode. For more information, see Synchronous Mode (page 194). The synchronous connection must be a Fibre Channel connection. For more information, see Fibre Channel Networks (page 22). 2. Between the primary system and backup system that are physically farther apart (and therefore share a lesser connection), Remote Copy is set up in asynchronous periodic mode. For more information, see Asynchronous Periodic Mode (page 195). The asynchronous periodic connection can be either all IP connections or, if all the Synchronous Long Distance systems are four-node storage systems, all Fibre Channel over an IP network connections. For more information, see Fibre Channel over IP Networks (page 22) and IP Networks (page 21). NOTE: Synchronous Long Distance Remote Copy links must be unidirectional; they cannot be bidirectional. Figure 5 (page 18) illustrates a Synchronous Long Distance Remote Copy configuration. Figure 5 Synchronous Long Distance Remote Copy configuration Because Synchronous Long Distance configurations include a standby link, illustrated in Figure 5 (page 18), this configuration allows for multiple backup and recovery scenarios during a failover. If a Backup System Fails If one backup system in a Synchronous Long Distance Remote Copy configuration fails, Remote Copy can still continue between the primary system and the second backup system. Figure 6 (page 19) illustrates a Synchronous Long Distance configuration in which backup system System2 fails and Remote Copy in asynchronous periodic mode still continues between primary system System1 and second backup system System3. (Likewise, if System3 failed, Remote Copy in synchronous mode would still continue between System1 and System2.) 18 Deciding on a Remote Copy Configuration

19 Figure 6 Synchronous Long Distance Remote Copy - One Backup System Failure In this example, when System2 is restored, Remote Copy transfers data from System1 to System2 and restores synchronous mode Remote Copy between System1 and System2. If the Primary System Fails If the primary system in a Synchronous Long Distance Remote Copy configuration fails, one of the backup systems (typically the backup system that shares a synchronous connection with the primary system) assumes the role of the primary system, and the second backup system serves as the backup system to the temporary primary system. The volume on the temporary primary system is updated periodically on the backup system. Figure 7 (page 20) illustrates a Synchronous Long Distance configuration in which primary system System1 goes down. In this example, System2 becomes the temporary primary system, and System3 becomes the backup system to System2. NOTE: You can set up either backup system to assume the role of the primary system in the event of failover. Synchronous Long Distance Configuration 19

20 Figure 7 Synchronous Long Distance Remote Copy - Primary System Failure In this example, when System1 is restored, Remote Copy: Transfers data from System2 to System1. Restores System1 as the primary system. Restores System2 and System3 as backup systems. Restores synchronous mode between System1 and System2. Restores asynchronous periodic mode between System1 and System3. 20 Deciding on a Remote Copy Configuration

21 3 Choosing Network Connections 1. Review the possible network connections. IP Networks (page 21) Fibre Channel Networks (page 22) Fibre Channel over IP Networks (page 22) 2. Review general network information for Remote Copy. General Considerations (page 22) Storage systems in a Remote Copy pair are connected through a dedicated link or through a network, as illustrated in Figure 8 (page 21). Figure 8 Remote Copy Links IP Networks CAUTION: Remote Copy over IP (RCIP) subnets must be dedicated to Remote Copy. The GigE interface and the management Ethernet port of an HP 3PAR Storage System controller node must be on different IP subnets. If you configure the interface and port on the same subnet, Remote Copy packets might go over the management port and would therefore not be available to the Remote Copy software. Hosts that access the HP 3PAR Storage Systems for management purposes must not be on the same subnet as the RCIP ports. If you add host computers to the Remote Copy subnet, IP packets might arrive through the management interfaces and leave through the RCIP interfaces. Be sure you understand the IP network that will be used to connect the storage systems. When you have more than one storage system at the same location, they could be on the same subnet. However, storage systems connected over an IP network are usually separated by a large distance and are therefore on different IP subnets. If the storage systems are on different subnets: Each storage system must be connected to a gateway router or switch on that subnet. An IP cloud must exist between their gateways. IP Networks 21

22 Fibre Channel Networks Remote Copy over Fibre Channel (RCFC) can only be set up on storage systems that communicate over Fibre Channel Storage Area Networks (FC SAN). Be sure you understand the FC SAN that will be 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 Host Bus Adapters (HBAs) installed for load sharing and fault tolerance. The HBA pair on each system must be dedicated to Remote Copy. The HBAs on each storage system must use Fibre Channel cable connections to connect the systems through the FC SAN. Fibre Channel over IP Networks In a Fibre Channel over IP (RCFC over IP) network setup, all systems use Fibre Channel connections that pass through routers in order to cross an IP network. You can only use RCFC over IP network connections for Remote Copy in asynchronous periodic mode. For more information, see Volume Group Modes (page 194). General Considerations The distance between the systems. Systems in the same room can be connected over direct Gigabit Ethernet (GigE) links or via GigE switches, or through Fibre Channel networks. Longer distances require other topologies. To use Remote Copy for disaster recovery, you should place the backup storage system at a remote site some distance from the primary system. This distance should be great enough that the two sites are unlikely to be affected by the same disaster. The latency of Remote Copy writes increases with distance. The bandwidth of the connection. Remote Copy over IP (RCIP) configurations can fully use all the 1Gbps links during the synchronization process. If you use networks with lower throughput, the throughput between systems running Remote Copy might be capped by the network. The requirements of the connection. For more information, see Considering Requirements and Restrictions (page 23). Data availability and speed. To maintain availability, you must use more than one link to connect storage systems. Remote Copy allows at least two separate network connections between storage systems. For optimal availability, the two connections should be connected to separate network equipment. When there are multiple physical links between the storage systems, Remote Copy uses all the available links to transmit data in parallel. 22 Choosing Network Connections

23 4 Considering Requirements and Restrictions 1. Review the general considerations for all configurations. General Requirements (page 23) General System Restrictions (page 23) General Software Restrictions (page 24) Transport Layer Considerations (page 24) Virtual Volume Considerations (page 25) 2. Review the considerations applicable to your chosen Remote Copy configuration. N-to-1 Considerations (page 25) 1-to-N Considerations (page 26) Synchronous Long Distance Considerations (page 27) General Requirements Remote Copy requires the use of a minimum of two HP 3PAR Storage Systems. You must have Remote Copy licenses for all storage systems participating in Remote Copy replication. For additional information on licensing and features, see the HP 3PAR InForm OS Concepts Guide. The physical connections between all storage systems used with Remote Copy must be through an IP-capable network, an FC SAN network, or point-to-point links. To use Remote Copy to copy virtual volumes and perform backup and disaster recovery, you must use the HP 3PAR Command Line Interface (CLI). For more information about the CLI and the CLI commands used with Remote Copy, see: About the Remote Copy Commands (page 222) HP 3PAR InForm OS Command Line Interface Reference HP 3PAR InForm OS CLI Administrator s Manual HP 3PAR InForm Management Console User's Guide General System Restrictions All storage systems in the configuration must be configured at the same HP 3PAR InForm Operating System Software level unless otherwise specified in the Configuration Matrix. For more information, see: The HP 3PAR InForm OS Configuration Matrix. To obtain a copy of this documentation, go to navigate to your product page, click Support for your product, and then click Manuals. Remote Copy Functionality Unavailable on Systems (page 289) Each storage system is limited to two Remote Copy interfaces with the exception of the following configurations: For 1-to-N Remote Copy, the primary storage system can have up to four RCIP interfaces; two to one backup system and two to the other backup system. For RCIP network setups, each system can have up to four interfaces. For RCFC network setups, each system can have up to four interfaces when configured on a storage system with four or more nodes. General Requirements 23

24 General Software Restrictions Remote Copy does not support self-mirroring configurations. In other words, Remote Copy cannot use a storage system to replicate its own primary volumes. Remote Copy does not support multihop configurations. In other words, Remote Copy cannot replicate a primary volume group to a backup system and then replicate the volume group again from the backup system to a third storage system. For N-to-1 and bidirectional configurations, one system can be the primary system for only one other system. This restriction applies to standard operating conditions and does not apply to disaster recovery operations for which the natural direction of replication must be changed. HP recommends you use synchronous mode replication over distances no greater than a Metropolitan Area Network (MAN). A MAN is a region larger than that covered by a Local Area Network (LAN) but smaller than that covered by a Wide Area Network (WAN). Transport Layer Considerations For Remote Copy over IP (RCIP), each storage system in the Remote Copy configuration should have at least two nodes with HP-supported GigE PCI adapters, up to a maximum of one adapter per node and four adapters per system. At least two adapters are required for each storage system in order to support redundant TCP/IP links between systems. For 1-to-N Remote Copy, the primary storage system can have four RCIP interfaces; two to one backup system and two to the other backup system. For Remote Copy over Fibre Channel (RCFC), each storage system should have a pair of Host Bus Adapters (HBAs) installed. The HBA pair is required for load sharing and fault tolerance. The HBAs in each storage system connect those systems through FC SAN using Fibre Channel cable connections (see Remote Copy Links (page 24)). Figure 9 Remote Copy Links The HBAs used for RCFC links must be reserved for exclusive use by Remote Copy. For RCIP configurations, the management interface cannot reside on the same network as the RCIP network. Remote Copy links must be dedicated links. 24 Considering Requirements and Restrictions

25 RCFC over IP network connections are only allowed for Remote Copy in asynchronous periodic mode. The maximum delay times are as follows: RCIP seconds RCFC milliseconds RCFC over IP - 60 milliseconds Virtual Volume Considerations You must use standard volume-creation commands to create virtual volumes on each system in the Remote Copy configuration before you create Remote Copy volume groups. For more information, see: Virtual Volumes and CPGs (page 187) HP 3PAR InForm OS CLI Administrator s Manual Virtual volumes on the primary system must be the same size as those on the backup system. All virtual volumes used with Remote Copy must be one of the following types: Thinly Provisioned Virtual Volumes (TPVVs) with snapshot space drawn from a Common Provisioning Group (CPG). TPVVs require the use of HP 3PAR Thin Provisioning Software. Fully provisioned virtual volumes For more details about virtual volumes, see the HP 3PAR InForm OS Concepts Guide. Virtual volume limits are as follows: The maximum number of mirrored volumes system-wide in synchronous mode is 800. The maximum number of mirrored volumes system-wide in asynchronous periodic mode is 2,400. The maximum number of volumes per Remote Copy group in synchronous and asynchronous periodic mode is 100. The maximum size of a mirrored volume is 16 TB. N-to-1 Considerations In an N-to-1 configuration, one backup system participates in a maximum of four Remote Copy pairs, one for each primary storage system (see Figure 10 (page 26)). Virtual Volume Considerations 25

26 Figure 10 N-to-1 Maximum Supported Configuration One of the Remote Copy pairs can be bidirectional. All others must be unidirectional. You can use either Remote Copy over IP (RCIP) or Remote Copy over Fibre Channel (RCFC) connections with N-to-1 Remote Copy configurations. The backup storage system must have at least four controller nodes. The backup system in the N-to-1 configuration must use only S-Class (P4) or T-Class controller nodes. The backup system cannot use E-Class or two-node F-Class controller nodes. You can only use asynchronous periodic mode volume groups with N-to-1 Remote Copy configurations. 1-to-N Considerations In a 1-to-N configuration, one primary storage system participates in a maximum of two Remote Copy pairs, one for each backup storage system (see Figure 11 (page 27)). 26 Considering Requirements and Restrictions

27 Figure 11 1-to-N Maximum Supported Configuration One of the Remote Copy pairs can be bidirectional. All others must be unidirectional. You can use both Remote Copy over IP (RCIP) and Remote Copy over Fibre Channel (RCFC) connections with 1-to-N Remote Copy configurations. If using both RCIP and RCFC in a 1 to-n Remote Copy configuration, the node using an RCIP connection must be set up in asynchronous periodic mode and the node using an RCFC connection must be set up in synchronous mode. For RCFC configurations, primary storage systems must have at least four controller nodes. For RCIP configurations, the primary and backup systems must have at least two controller nodes each. Primary systems with only two controller nodes must be HP 3PAR S-, T-, or F-Class Storage Systems. You can only use HP 3PAR E-Class Storage Systems as backup systems in 1-to-N Remote Copy configurations. Synchronous Long Distance Considerations For Synchronous Long Distance configurations, a maximum of two storage systems are used as backup systems for one primary storage system. All HP 3PAR Storage Systems in a Synchronous Long Distance configuration must be running HP 3PAR InForm OS or above. You can configure the Remote Copy pairs only as unidirectional. Any or all of the storage systems in a Synchronous Long Distance configuration can be two-node or four-node systems. You must configure one synchronous mode target system and one asynchronous periodic mode target system. You can only create two target systems. If you are using two-node systems for your Synchronous Long Distance configuration: You can use HP 3PAR T- or F-Class Storage Systems. One node must be set up in asynchronous periodic mode and one node must be set up in synchronous mode. Synchronous Long Distance Considerations 27

28 The node set up in synchronous mode must use Fibre Channel (RCFC), and the node set up in asynchronous periodic mode must use IP links (RCIP). RCFC over an IP network is not supported for two-node Synchronous Long Distance configurations. For more information, see Setting the Transport Layer (page 33). 28 Considering Requirements and Restrictions

29 5 Gathering Setup Information 1. Contact your network administrator to obtain: IP addresses or 64-bit World Wide Name (WWN) address information for the interfaces of the storage 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 port Use the provided worksheets to organize the data. Use multiple copies of the relevant worksheet if the Remote Copy configuration has more than two systems. To organize data for this configuration: Use these worksheets: RCIP RCFC Unidirectional 1-to-1 Bidirectional 1-to-1 N-to-1 1-to-N Synchronous Long Distance Unidirectional 1-to-1 Bidirectional 1-to-1 N-to-1 1-to-N Synchronous Long Distance Figure 13 (page 30) Figure 13 (page 30) and Figure 14 (page 31) as many times as necessary Figure 15 (page 32) Figure 15 (page 32) as many times as necessary RCIP Initial Remote Copy Pair Figure 12 (page 29) illustrates the initial Remote Copy pair in an RCIP configuration. Figure 12 Network and Remote Copy Over IP Setup Information (Initial Pair) RCIP Initial Remote Copy Pair 29

30 RCIP Initial Remote Copy Pair Worksheet Figure 13 Network and Remote Copy Over IP Setup Information (Initial Pair) 30 Gathering Setup Information

31 RCIP Additional Remote Copy Pairs Worksheet Figure 14 Network and Remote Copy Over IP Setup Information (Additional Systems) RCIP Additional Remote Copy Pairs Worksheet 31

32 RCFC Remote Copy Pair Worksheet Figure 15 Network and Remote Copy Over Fibre Channel Setup Information 32 Gathering Setup Information

33 6 Setting the Transport Layer Follow the steps for your chosen transport layer. Setting Up Remote Copy over IP (page 33) Setting Up Remote Copy over Fibre Channel (page 38) Setting Up RCFC over an IP Network (page 41) For more information on the CLI commands in this chapter, see: About the Remote Copy Commands (page 222) HP 3PAR InForm OS Command Line Interface Reference Setting Up Remote Copy over IP Configuring Ports for RCIP For Remote Copy over IP (RCIP) configurations, each link between a Remote Copy pair is a logical link between a controller node on one storage system and a controller node on the other storage system in the pair. These links use a GigE port from each of the nodes in the storage systems that belong to the Remote Copy pair. RCIP configurations can use up to four links between systems; in other words, up to four nodes can have one GigE port each contributing links to an RCIP configuration. If these ports were not set up during the initial setup of the storage system, or if the configuration has changed, reconfigure the ports before you set up the Remote Copy transport layer. To configure the ports, use the CLI command controlport rcip. CAUTION: The GigE interface and the management Ethernet port of an HP 3PAR Storage System controller node must be on different IP subnets. If the interface and port are configured on the same subnet, Remote Copy packets might go over the management port, and would therefore not be available to the Remote Copy software. Setting Up the Remote Copy Interface for RCIP Use the setup information you gathered in the RCIP Initial Remote Copy Pair Worksheet (page 30). If you are configuring multiple systems, use the setup information you gathered in both the RCIP Initial Remote Copy Pair Worksheet (page 30) and the RCIP Additional Remote Copy Pairs Worksheet (page 31). 1. If the IP addresses for RCIP already exist and you are reconfiguring the Remote Copy interface: a. Remove the existing links: # dismissrcopylink <target_name> <N:S:P:IP_address>... <target_name> - The name of the target (for example, System2) <N:S:P> - Node, slot, and port of the Ethernet port on the primary system (for example, on System1) <IP_address> - IP address on the target system (for example, on System2) b. Add the new links: # admitrcopylink <target_name> <N:S:P:IP_address>... Setting Up Remote Copy over IP 33

34 2. Enter the following command for an Ethernet port on one Remote Copy system: # controlport rcip addr <port_ip> <netmask> <N:S:P> <port_ip> - IP address assigned to the Ethernet port <netmask> - Netmask to be assigned <N:S:P> - Location of a primary system Ethernet port, expressed as node:slot:port 3. Enter y to confirm you want to make the gateway change. 4. Repeat Step 1 through Step 3 for each Ethernet port on each HP 3PAR Storage System used in the Remote Copy configuration. 5. Enter the following command on each system: # showport -rcip 6. Compare the IP addresses and netmask with your RCIP worksheet(s). For example: N:S:P State ---HwAddr--- IPAddr Netmask Gateway MTU Rate Duplex AutoNeg 0:3:1 ready CBF68C Gbps Full Yes 1:3:1 ready CBF Gbps Full Yes Problem If the output does not match the information on your worksheet: Solution Repeat from Step 1 to reconfigure the addresses. Setting the Gateway Because the storage systems in the Remote Copy configuration are on different subnets (the required setup), you must set the gateways for each system. 1. Enter the following command for an Ethernet port on one system: # controlport rcip gw <gateway_ip> <N:S:P> <gateway_ip> - Gateway IP address to assign to the local Ethernet port <N:S:P> - Location of a local Ethernet port 2. Enter y to confirm you want to make the gateway change. 3. Repeat Step 1 and Step 2 for each Ethernet port on each storage system used in the Remote Copy configuration. 4. Enter the following command on each system: # showport -rcip 34 Setting the Transport Layer

35 5. Verify that the Gateway column displays the correct gateway IP address: N:S:P State ---HwAddr--- IPAddr Netmask Gateway MTU Rate Duplex AutoNeg 0:3:1 ready CBF68C Gbps Full Yes 1:3:1 ready CBF Gbps Full Yes Problem If the setup does not match the information on your worksheet: Solution Repeat from Step 1 to reconfigure the gateways. Verifying the Servers Are Connected 1. Enter the following command: # controlport rcip ping <IP_address> <N:S:P> <N:S:P> - Interface from which to ping, expressed as node:slot:port <IP_address> - IP address on the target system to ping For example: # controlport rcip ping :3:1 PING ( ) from : 56(84) bytes of data. 64 bytes from : icmp_seq=1 ttl=253 time=0.325 ms ping statistics packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.325/0.325/0.325/0.000 ms Setting Up Remote Copy over IP 35

36 2. Issue this command once for each interface on each system in the configuration. NOTE: Because of the spanning tree protocol and MAC address learning, you might need to ping each system several times before the systems update all tables and the ping succeeds. Problem If the controlport rcip ping command does not work after repeated attempts: Solution 1. Check the setup: Use the controlport rcip ping command to test connectivity between all IP interfaces on all Remote Copy systems. Use the showport -rc command to verify that the GigE cards are all in the ready state. Verify all IP addresses, netmasks, gateways, and physical connections. Verify the MTU settings are correct. For more information, see Increasing MTU (Optional) (page 37). Verify the controlport rcip speed settings. For more information, see controlport in The Remote Copy Commands (page 224). 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 Copy GigE ports on all the storage systems in the Remote Copy configuration. Checking Link Throughput and Latency 1. Ensure the systems for which you are checking links are not pegged. CAUTION: Do not check the links if CPU usage is already close to 100%. The link check temporarily increases CPU usage. 2. Starting with the backup system, enter the following command on a system in the Remote Copy pair (e.g., System2): # checkrclink startserver <N:S:P> <dest_addr> <N:S:P> - Interface from which to check the link, expressed as node:slot:port <dest_addr> - IP address on the target system for which you are checking the link 3. On the target system in the Remote Copy pair (e.g., System1), enter the following command: # checkrclink startclient <N:S:P> <dest_addr> <time> <N:S:P> - Interface from which to check the link, expressed as node:slot:port <dest_addr> - IP address on the target system for which you are checking the link <time> - Duration of the test in seconds 36 Setting the Transport Layer

37 4. Enter the following command on the first target system in the Remote Copy pair (in other words, on the system on which you issued the startserver command; e.g., System2). # checkrclink stopserver <N:S:P> 5. Repeat Step 2 through Step 4 on each link and each system in the configuration. Problem Solution If you are not satisfied with the results, see: Increasing MTU (Optional) (page 37) Remote Copy Concepts (page 180) Increasing MTU (Optional) You can increase the maximum transmission unit (MTU) size if: The results of the link throughput and latency test display a value of 9000 in the Max MTU row. For more information, see Checking Link Throughput and Latency (page 36). The GigE adapters are configured to use jumbo frames (9000-byte frames), and not the default 1500-byte frames. The IP network supports jumbo frames end-to-end (along the entire path between the two storage systems). A 9000-byte MTU setting uses larger fragments to improve link efficiency and results in improved throughput between storage systems. To increase the MTU: 1. Enter the controlport rcip mtu command: # controlport rcip mtu 9000 <N:S:P> <N:S:P> - Location of the GigE port, expressed as node:slot:port 2. Repeat for all Remote Copy GigE ports on each storage system. 3. Verify that the network supports the increased MTU size. From a storage system, enter the controlport rcip ping command: # controlport rcip ping -s pf <IP_address> <N:S:P> Test packet size <IP_address> - IP address on the target system to ping <N:S:P> - Interface from which to ping Setting Up Remote Copy over IP 37