HP 3PAR Remote Copy® 3.1.1 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.
© Copyright 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Introduction................................................................................................10 Related Documentation............................................................................................................10 Typographical Conventions......................................................................................................10 Advisories........................................................................................................................
Checking Link Throughput and Latency.............................................................................40 Setting Up RCFC over an IP Network....................................................................................41 II Setting Up the Remote Copy Servers............................................................42 7 Setting Up 1-to-1 Remote Copy...............................................................43 8 Setting Up N-to-1 Remote Copy..............................................
15 Setting Volume Group Policies...............................................................89 Automatically Restarting Volume Groups...............................................................................89 Generating Alerts for Slow Resynchronizations of Asynchronous Periodic Volume Groups.............90 16 Performing Manual Operations.............................................................91 Changing the Remote Copy Mode for a Volume Group..................................................
22 Disaster Recovery for 1-to-N Configurations..........................................124 System Information during Normal Operation......................................................................125 Primary System (System1).............................................................................................125 First Backup System (System2).......................................................................................126 Second Backup System (System3).................................
Virtual Volumes Used with Remote Copy.............................................................................188 Thinly Provisioned Virtual Volumes.................................................................................188 Fully Provisioned Virtual Volumes...................................................................................188 Rules for Creating Remote Copy Virtual Volumes..................................................................189 27 Volume Groups......................
Timeouts and Transient Network Problems......................................................................207 Failure of a Single Link.....................................................................................................207 Failure of All Links............................................................................................................208 Link Failure and Synchronous Volume Groups..................................................................
showrcopy .....................................................................................................................265 showrctransport ..............................................................................................................269 startrcopy ......................................................................................................................272 startrcopygroup ......................................................................................................
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).
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. Advisories 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.
Part I Setting the Foundation for Remote Copy 1. Plan your setup strategy. “Planning Your Remote Copy Setup Strategy” (page 13) 2. Decide on the Remote Copy configuration to use. “Deciding on a Remote Copy Configuration” (page 14) 3. Choose the type of network connection to use. “Choosing Network Connections” (page 21) 4. Check the requirements and restrictions to make sure the system is prepared for the Remote Copy setup you are planning. “Considering Requirements and Restrictions” (page 23) 5.
1 Planning Your Remote Copy Setup Strategy 1. Decide on a setup methodology. “Setup Instructions and Resources” (page 13) 2. Decide where to locate the HP 3PAR Storage Systems. “Remote Copy System Locations” (page 13) 3. Review the list of additional resources that can help with “Additional Information” (page 13) setup.
2 Deciding on a Remote Copy Configuration To decide on the best Remote Copy configuration for your • “Unidirectional 1-to-1 Configuration” (page 14) system, review illustrations and descriptions of the possible • “Bidirectional 1-to-1 Configuration” (page 14) configurations.
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.
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.
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.
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.
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.
Figure 7 Synchronous Long Distance Remote Copy - Primary System Failure In this example, when System1 is restored, Remote Copy: 20 • 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.
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).
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.
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.
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.
• RCFC over IP network connections are only allowed for Remote Copy in asynchronous periodic mode. • The maximum delay times are as follows: ◦ RCIP - 150 seconds ◦ RCFC - 1.5 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.
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.
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.
◦ 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).
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 5785. 3. Use the provided worksheets to organize the data.
RCIP Initial Remote Copy Pair Worksheet Figure 13 Network and Remote Copy Over IP Setup Information (Initial Pair) 30 Gathering Setup Information
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
RCFC Remote Copy Pair Worksheet Figure 15 Network and Remote Copy Over Fibre Channel Setup Information 32 Gathering Setup Information
6 Setting the Transport Layer Follow the steps for your chosen transport layer.
2. Enter the following command for an Ethernet port on one Remote Copy system: # controlport rcip addr 3. 4. 5. • - IP address assigned to the Ethernet port • - Netmask to be assigned • - Location of a primary system Ethernet port, expressed as node:slot:port Enter y to confirm you want to make the gateway change. Repeat Step 1 through Step 3 for each Ethernet port on each HP 3PAR Storage System used in the Remote Copy configuration.
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 000423CBF68C 10.100.24.107 255.255.255.0 10.100.24.1 1500 1Gbps Full Yes 1:3:1 ready 000423CBF693 10.101.24.107 255.255.255.0 10.101.24.1 1500 1Gbps Full Yes Problem Solution If the setup does not match the information on your worksheet: Repeat from Step 1 to reconfigure the gateways. Verifying the Servers Are Connected 1.
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 Solution If the controlport rcip ping command does not 1. Check the setup: work after repeated attempts: • Use the controlport rcip ping command to test connectivity between all IP interfaces on all Remote Copy systems.
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 5. Repeat Step 2 through Step 4 on each link and each system in the configuration.
4. Enter the controlport rcip ping command 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 server updates all tables and the ping succeeds. Problem Solution If the pings do not succeed: 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.
Setting Up Dedicated Node Pairs for RCFC • Verify that each Fibre Channel interface on each node on the primary Remote Copy system connects to a dedicated Fibre Channel interface on each node on the backup Remote Copy system. RCFC requires a dedicated node pair per target.
For example: N:S:P Peer_Node_WWN Peer_Port_WWN State 3:2:1 2FF70002AC00005F 23410002AC00005F new 1:4:1 2FF70002AC00005F 21510002AC00005F new Problem Solution If the ports do not match the ports you recorded on your Repeat the interface setup steps starting at Step 1. worksheet: 6. To initialize the Fibre Channel adaptor port, enter the controlport rcfc init command on one system: # controlport rcfc init -f • 7.
3. On the target system in the Remote Copy pair (e.g., System1), enter the following command: # checkrclink startclient
Part II Setting Up the Remote Copy Servers To set up: See: 1-to-1 Remote Copy “Setting Up 1-to-1 Remote Copy” (page 43) N-to-1 Remote Copy “Setting Up N-to-1 Remote Copy” (page 45) 1-to-N Remote Copy “Setting Up 1-to-N Remote Copy” (page 55) Synchronous Long Distance Remote Copy “Setting Up Synchronous Long Distance Remote Copy” (page 56) Additional Information: • “Setting Up a Unidirectional Configuration” (page 67) • “Setting Up a Bidirectional Configuration” (page 76) • “Using Tape for Ini
7 Setting Up 1-to-1 Remote Copy To set up 1-to-1 Remote Copy in a unidirectional configuration: 1. Verify that your setup plan meets the Remote Copy requirements. “Considering Requirements and Restrictions” (page 23) 2. Acquaint yourself with the basic 1-to-1 setup and with the example Remote Copy pair used to illustrate unidirectional setup. Figure 17 (page 44) (basic 1-to-1 setup) 3.
Figure 17 Example Unidirectional 1-to-1 Remote Copy Configuration Example primary system Example backup system System name System1 System2 System ID 112 125 Nodes eight (only two shown) four (only two shown) Nodes dedicated to Remote Copy 6 and 7 2 and 3 Links Node 6: IP address 172.16.1.11 Node 2: IP address 172.16.1.12 Node 7: IP address 172.16.2.11 Node 3: IP address 172.16.2.12 Target system System2 System1 Target Interface IP Node 6: 172.16.1.12 Node 2: 172.16.1.
8 Setting Up N-to-1 Remote Copy 1. Verify that your setup plan meets the N-to-1 requirements. “Considering Requirements and Restrictions” (page 23) 2. Acquaint yourself with the basic N-to-1 setup and with Figure 18 (page 46) (basic N-to-1 setup) the example Remote Copy pair used to illustrate setup. “Example Remote Copy Pair for N-to-1 Setup” (page 46) 3. Verify connectivity between the Remote Copy pair you plan to configure. “Verifying Connectivity between Systems” (page 47) 4.
Figure 18 Example N-to-1 Configuration Example Remote Copy Pair for N-to-1 Setup The setup steps for each Remote Copy pair in the N-to-1 configuration refer to the example setup illustrated in Figure 19 (page 46): Figure 19 Example Remote Copy Pair 46 Example primary system Example backup system System name System1 System2 System ID 112 125 Nodes eight (only two shown) four (only two shown) Nodes dedicated to Remote Copy 6 and 7 2 and 3 Target system System2 System1 Links IP address 172
Virtual volumes and volume groups Example primary system Example backup system IP address 172.16.2.12 IP address 172.16.2.11 One virtual volume (vv1) One secondary virtual volume One primary volume group (Group1) (vv1_remote) One secondary volume group (Group1.r112) Verifying Connectivity between Systems Verify the connectivity for the Remote Copy pair you are configuring.
2. Define a target on the primary storage system (for example, System1).
2. Define a target on the backup system (for example, System2). For RCIP: # creatercopytarget IP : : • - Name of the target system (for example, System1) • IP - Defines link as an IP link • - Location on the current system (System2) that contains the IP connections to the target system, expressed as node:slot:port • - Link IP address for the corresponding port on the target system (for example, 172.16.1.
Target System1 System1 receive receive 3. Node 0 1 0 1 Address 10.100.24.108 10.101.24.108 10.100.24.108 10.101.24.108 Status Options Up Up Up Up Repeat Step 1 and Step 2 on the primary system (System1). Problem Solution If you encounter any problems with the links: 1. Use the dismissrcopylinkcommand to remove the links: • RCIP: dismissrcopylink : • RCFC: dismissrcopylink 2. Repeat the setup from “Setting Up the Primary System” (page 68).
1. Set up a volume group on the primary storage system (for example, System1): # creatercopygroup :periodic • - Name of the volume group (for example, Group1) • - Name of the target system (for example, System2) • periodic - Specifies asynchronous periodic mode NOTE: N-to-1 configurations support only asynchronous periodic mode volume groups. For more information, see “Volume Group Modes” (page 194).
• 3. - Pattern of volume group names (for example, Group*) On the primary system (e.g., System1), add the pre-existing virtual volume(s) to the newly created volume group: # admitrcopyvv • - Name of the virtual volume (for example, vv1) to add to the primary volume group on the primary system • - Name of the primary volume group (e.g.
Deciding on an Initial Replication Method • Decide on the method to use to start replicating the data in the primary volume groups: ◦ Direct replication Copy data directly from the virtual volumes in the primary volume group to the virtual volumes in the secondary volume group. ◦ “Deciding on an Initial Replication Method” (page 53) Via tape. Using tape for the initial backup can be faster if you are copying very large volumes. 1.
4. 54 Problem Solution If the initial synchronization fails: Repeat from Step 1. Repeat the steps in “Starting Initial Replication: Copying Data Directly from Primary Volume Groups” (page 53) for all primary volume groups on the primary system.
9 Setting Up 1-to-N Remote Copy 1. Verify that your setup plan meets the 1-to-N requirements. “Considering Requirements and Restrictions” (page 23) 2. Acquaint yourself with the basic 1-to-N setup and with Figure 20 (page 55) (basic 1-to-N setup) the example Remote Copy pair used to illustrate setup. “Example Unidirectional Setup” (page 67) 3.
10 Setting Up Synchronous Long Distance Remote Copy 1. Verify that your setup plan meets the Synchronous Long “Considering Requirements and Restrictions” (page 23) Distance requirements. 2. Acquaint yourself with the Synchronous Long Distance setup. “Example Synchronous Long Distance Setup” (page 56) 3. Verify connectivity between the Remote Copy pairs you “Verifying Connectivity between Systems” (page 58) plan to configure. 4.
Figure 21 Example Synchronous Long Distance Remote Copy Configuration Example primary system Example backup system 1 Example backup system 2 System name SystemA SystemB SystemC Nodes four four four System ID 96 195 63 Three secondary virtual volumes: Three secondary virtual volumes: • testvv.B.0 • testvv.C.0 • testvv.B.1 • testvv.C.1 • testvv.B.2 • testvv.C.2 One secondary volume group (testgroup.r96) One secondary volume group (testgroup.
Local Setup Target system SystemB SystemA RCFC links • Node WWN: 2FF70002AC000060 • Node WWN: 2FF70002AC0000C3 • Node 0 WWN: 20110002AC000060 • Node 0 WWN: 20210002AC0000C3 • Node 1 WWN: 21320002AC000060 • Node 1 WWN: 21210002AC0000C3 Mode (not connected to the FC SAN) Synchronous Backup system 2 (SystemC) is located far from the primary system and backup system 1, and therefore must use an IP network. • An IP network connects all systems.
Setting Up the Primary System 1. Start Remote Copy on the primary storage system (for example, SystemA). # startrcopy 2. Define the targets for the synchronous backup system (SystemB) on the primary system. On the primary system (SystemA) enter: • For RCFC: # creatercopytarget FC : : • ◦ - Name of the Remote Copy target system (SystemB). ◦ FC - Specifies a Fibre Channel link.
2. Define a target (for example, the primary system SystemA) on the backup system. On the backup system (SystemB), enter: • For RCFC: # creatercopytarget FC : : • ◦ - Name of the Remote Copy target system (SystemA). ◦ FC - Specifies a Fibre Channel link. ◦ - WWN of the target node (node 2FF70002AC000060 on SystemA).
6. Define a second target system (for example, the synchronous backup system SystemB) for the current backup system. On the current backup system (SystemC), enter: # creatercopytarget IP : : • - Name of the Remote Copy target system (SystemB). • IP - Specifies an IP link.
Link Information Target SystemA SystemA SystemC SystemC receive receive receive receive 4. Node 0:2:1 1:2:1 2:4:1 3:4:1 0:2:1 1:2:1 2:4:1 3:4:1 Address 20110002AC000060 21320002AC000060 10.100.33.63 10.101.33.63 20110002AC000060 21320002AC000060 receive receive Status Options Up Up Up Up Up Up Up Up Repeat Step 1 and Step 2 on the other backup system (for example, SystemC).
1. Create a volume group on the primary system (for example, SystemA): # creatercopygroup :sync :periodic • - Name of the volume group (for example, testgroup). • - Name of the target systems (for example, SystemB and SystemC). • sync | periodic - sync for synchronous mode and periodic for asynchronous periodic mode.
2. On the primary system (SystemA), add the pre-existing virtual volume(s) to the newly created volume group. Enter either: # admitrcopyvv • - Name of the virtual volume (for example, testvv.A.0) to add to the primary volume group on the primary system • - Name of the primary volume group (e.g.
Starting Initial Replication: Copying Data Directly from Primary Volume Groups 1. Start replication from the primary volume group to the secondary volume groups on SystemB and SystemC. From the primary system (SystemA), enter: # startrcopygroup • - Name of the primary volume group (testgroup) The startrcopygroup command, when run on a group for the first time: 2.
3. On all three systems, verify that the SyncStatus column in the Group Information area displays Synced. Example showrcopy groups output on SystemA: Group Information Name Target Status testgroup SystemB Started LocalVV ID RemoteVV testvv.A.0 100 testvv.B.0 testvv.A.1 101 testvv.B.1 testvv.A.2 102 testvv.B.2 Name Target Role Mode Primary Sync ID SyncStatus 200 Synced 201 Synced 202 Synced Status testgroup SystemC Started PDT , over_per_alert LocalVV ID RemoteVV testvv.A.0 100 testvv.C.0 testvv.A.
11 Setting Up a Unidirectional Configuration 1. Verify that your setup plan meets the Remote Copy requirements. “Considering Requirements and Restrictions” (page 23) 2. Acquaint yourself with the basic unidirectional setup. “Example Unidirectional Setup” (page 67) 3. Verify connectivity between the Remote Copy pair you plan to configure. “Verifying Connectivity between Systems” (page 68) 4. Set up the primary and backup systems (the Remote Copy pair) and check the links.
Figure 22 Example Unidirectional Remote Copy Pair Example primary system Example backup system System name System1 System2 System ID 112 125 Nodes eight (only two shown) four (only two shown) Nodes dedicated to Remote Copy 6 and 7 2 and 3 Target system System2 System1 Links IP address 172.16.1.12 IP address 172.16.1.11 IP address 172.16.2.12 IP address 172.16.2.
2. Define a target on the primary storage system (for example, System1).
2. Define a target on the backup system (for example, System2). • For RCIP: # creatercopytarget IP : : • ◦ - Name of the target system (for example, System1) ◦ IP - Defines link as an IP link ◦ - Location on the current system (System2) that contains the IP connections to the target system, expressed as node:slot:port ◦ - Link IP address for the corresponding port on the target system (for example, 172.
Target System1 System1 receive receive 3. Node 0 1 0 1 Address 10.100.24.108 10.101.24.108 10.100.24.108 10.101.24.108 Status Options Up Up Up Up Repeat step 1 and step 2 on the primary system (System1). Problem Solution If you encounter any problems with the links: 1. Use the dismissrcopylink command to remove the links: • RCIP: dismissrcopylink : • RCFC: dismissrcopylink 2. Repeat the setup from “Setting Up the Primary System” (page 68).
1. Set up a volume group on the primary storage system (for example, System1): # creatercopygroup : • - Name of the volume group (for example, Group1) • - Name of the target system (for example, System2) • - sync for synchronous mode or periodic for asynchronous periodic mode For more information, see “Volume Group Modes” (page 194).
• 3.
Deciding on an Initial Replication Method • Decide on the method to use to start replicating the data in the primary volume groups: ◦ Direct replication Copy data directly from the virtual volumes in the primary volume group to the virtual volumes in the secondary volume group. ◦ “Starting Initial Replication: Copying Data Directly from Primary Volume Groups” (page 74) Via tape. Using tape for the initial backup can be faster if you are copying very large volumes. 1.
4. Problem Solution If the initial synchronization fails: Repeat from step 1. Repeat the steps in “Starting Initial Replication: Copying Data Directly from Primary Volume Groups” (page 74) for all primary volume groups on the primary system.
12 Setting Up a Bidirectional Configuration 1. Verify that your setup plan meets the Remote Copy requirements. “Considering Requirements and Restrictions” (page 23) 2. Acquaint yourself with the basic bidirectional setup. “Example Bidirectional Setup” (page 76) 3. Set up the unidirectional configuration for the Remote Copy pair. “Setting Up a Unidirectional Configuration” (page 67) 4. Set up the bidirectional configuration for the Remote Copy pair: a. Ensure the primary and backup systems are set up.
Figure 23 Example Bidirectional Remote Copy Pair Example primary system Example backup system System name System2 System1 System ID 125 112 Target system System1 System2 Virtual volumes and volume groups • Unidirectional setup • Unidirectional setup (System1 —> System2): (System1 —> System2): One secondary volume group (Group1.
volume groups on the new primary system (for example, System2) and copy them to the new backup system (for example, System1). • If a unidirectional 1-to-1 configuration is not yet set up, follow the steps in“Setting Up a Unidirectional Configuration” (page 67) to set up the first primary system (for example, System1). Creating Volume Groups for Bidirectional Remote Copy 1. 2. Verify that the virtual volumes you plan to replicate from the new primary system to the new backup already exist.
• s|m|h|d - Synchronization time period (time between start of resynchronizations), followed by time unit: s (seconds), m (minutes), h (hours), or d (days) • - Name of the target system (for example, System1) • - Name of the primary volume group (for example, Group2) or: # setrcopygroup period s|m|h|d -pat • 4.
Deciding on an Initial Replication Method • Decide on the method to use to start replicating the data in the primary volume groups: ◦ Direct replication Copy data directly from the virtual volumes in the primary volume group to the virtual volumes in the secondary volume group. ◦ “Starting Initial Replication: Copying Data Directly from Primary Volume Groups” (page 80) Via tape. Using tape for the initial backup can be faster if you are copying very large volumes. 1.
4. Problem Solution If the initial synchronization fails: Repeat from step 1. Repeat the steps in “Starting Initial Replication: Copying Data Directly from Primary Volume Groups” (page 80) for all primary volume groups on the primary system.
13 Using Tape for Initial Synchronization and Backup For the first data synchronization between systems, it can be faster to back up the primary volume group(s) to tape and then copy data from the tape to the secondary volume group(s). CAUTION: To use the tape backup method for the initial synchronization of your Remote Copy data, you must use block-based backup software. File-system-based backup software does not correctly back up Remote Copy data. 1. 2.
• - Internally assigned target ID • - A system-assigned integer 4. Verify that the snapshot belongs to the correct volume and is a read-only (RO) snapshot: a. Issue the showvv command. b. Check that the copy of field displays the volume group (for example, Group1) to which the snapshot should belong. c. Check that the Rd column displays RO. 5. Ensure your block-based backup software is set up to create the backup from the beginning of the volume.
• - Name of the primary volume group (for example, Group1) or: # setrcopygroup -pat • - Pattern of volume group names to start (for example, Group*) 11. Repeat from step 1 for each primary volume group you are synchronizing to tape. 84 Problem Solution If initial synchronization fails: Repeat from step 1.
Part III Managing Remote Copy For information on: See: Viewing configuration and synchronization details, statistics, and recovery progress after failover “Viewing Remote Copy System Information” (page 86) Setting the policies for automatic restarts and synchronization alerts “Setting Volume Group Policies” (page 89) Changing modes, synchronizing, changing secondary groups “Performing Manual Operations” (page 91) to primary, stopping and restarting, and removing Remote Copy Using volumes with Remote C
14 Viewing Remote Copy System Information To view information on: Issue this command: For more information: Configuration details showrcopy Link throughput and latency statistics “About the Remote Copy Commands” (page 222) statrcopy Virtual volume statistics (such as I/O number, size, and completion time) statrcvv Historical volume statistics histrcvv Problem Solution If the mirror system does not respond to a command after 5 minutes (the timeout limit), an error message appears: Ensure links
Remote Copy does not create a new task for each resynchronization of an asynchronous periodic volume group. Instead, Remote Copy keeps the initial synchronization task active for as long as the group is in the Started state, and updates the task details as resynchronizations occur. Viewing Synchronization Task Information To see a list of the tasks that were active on a system within the last 24 hours, use the showtask command.
NOTE: For Remote Copy synchronizations, the Finish Time column for a resynchronization task might not match the LastSync column in the showrcopy command output for the system that contains the primary volumes. This discrepancy results from the differences in the times recorded: ◦ A task’s Finish Time is recorded by the task subsystem when the task is marked as done. ◦ The LastSync time is recorded when Remote Copy completes the synchronization.
15 Setting Volume Group Policies To set volume groups to: Use this policy: For more information: Automatically restart after certain types auto_recover of failure Never automatically restart (default) “Automatically Restarting Volume Groups” (page 89) no_auto_recover Generate alerts when synchronization over_per_alert between asynchronous periodic volume groups is slow (default) Not generate slow synchronization alerts for asynchronous periodic volume groups “Generating Alerts for Slow Resynchronizat
◦ - Pattern of volume group names (for example, Group*) If the volume groups stop for any kind of failure, you must use the startrcopygroup command to manually restart the volume groups. Generating Alerts for Slow Resynchronizations of Asynchronous Periodic Volume Groups By default, Remote Copy generates an alert if asynchronous periodic volume groups do not complete resynchronization within the synchronization period specified by the setrcopygroup period command.
16 Performing Manual Operations To manually: Issue this command: For more information: Change the mode of a volume group setrcopygroup mode “Changing the Remote Copy Mode for a Volume Group” (page 91) Synchronize primary and secondary volume groups syncrcopy “Manually Resynchronizing Volume Groups” (page 92) Change volume group roles for disaster recovery purposes setrcopygroup failover “Changing Secondary Volume Groups to Primary” (page 93) Stop and restart Remote Copy stoprcopygroup “Stopping
or: # setrcopygroup mode -pat • 3. - Pattern of volume group names (for example, Group*) Start the primary volume group. # startrcopygroup or: # startrcopygroup -pat • 4. - Pattern of volume group names to start (for example, Group*) If the volume group’s new mode is asynchronous periodic, set a synchronization period.
◦ - Pattern of volume group names (for example, Group*) While this command completes, Remote Copy makes changes as a result of host writes only on the primary volume (because the syncrcopy command sends the last resynchronization points over the network to the backup storage system).
Stopping and Starting Remote Copy To stop Remote Copy temporarily: # stoprcopy -stopgroups To restart Remote Copy: # startrcopy Removing Remote Copy Completely WARNING! reversible. Removing the Remote Copy setup erases all Remote Copy configuration and is not If you decide to use Remote Copy after removing it completely, you must set up and configure Remote Copy from the beginning.
17 Modifying Virtual Volumes To: Issue this command: For more information: Convert a virtual volume for Remote Copy use and assign it to a CPG setvv -snp_cpg “Converting Standard Virtual Volumes” (page 95) Increase virtual volume size growvv “Growing Virtual Volumes” (page 95) Rename a virtual volume setvv -name “Renaming Virtual Volumes” (page 96) Additional Information: “Virtual Volumes and CPGs” (page 187) Problem Solution If the mirror system does not respond to a command after 5 minutes (
3. • - Name of the virtual volume you are growing. • - Size (in multiples of 256 MB) to add to the virtual volume’s user space. If the increase is in gigabytes or terabytes, specify g, G, t, or T, respectively. In the secondary volume group that contains the copy of the virtual volume you are growing, grow the copy of the virtual volume to the exact same size as the original virtual volume. # growvv [g|G|t|T] 4. Start the volume groups.
18 Limiting Throughput To save on leased-line charges during synchronization, limit throughput. “Limiting Throughput for Asynchronous Periodic Volume Groups” (page 97) To send as much data as possible, remove throughput limits. “Removing Throughput Limits” (page 98) By default, Remote Copy sends data as fast as it can on all links between a Remote Copy pair.
Removing Throughput Limits 1. Stop the volume groups. # stoprcopygroup or: # stoprcopygroup -pat • 2. - Pattern of volume group names to stop (for example, Group*) Specify a throughput value of 0 (zero) and a valid size unit. # setrcopytarget tput 0{g|G|m|M|k|K} 3. Start the volume groups.
19 Optimizing Performance To optimize RCIP throughput, increase MTU size. “Optimizing RCIP Throughput by Increasing MTU Size” (page 99) To optimize RCIP throughput during initial synchronization, “Avoiding RCIP Throughput Issues during Initial use tape. Synchronization” (page 99) To optimize synchronization with a remote system, balance “Optimizing Synchronization Speed over Distances” bandwidth and latency.
Optimizing Synchronization Speed over Distances As the physical distance increases between the systems in the Remote Copy pair, latency can increase and throughput can decrease for both RCIP and RCFC configurations.
Distribution of Host Writes over RCIP GigE Links When copying data from the primary system to the backup system, Remote Copy uses all the RCIP GigE links simultaneously in order to achieve the maximum throughput (MB/s) possible. A single host write I/O is sent on a single link, but different I/Os can be sent on different links. • If host writes come over a node configured with Remote Copy GigE links, Remote Copy attempts to use the local GigE link to send the data to the backup system.
Part IV Recovering from Disaster To recover and restore this configuration after the See: primary system goes offline: 1-to-1 Remote Copy “Disaster Recovery for 1-to-1 Configurations” (page 103) N-to-1 Remote Copy “Disaster Recovery for N-to-1 Configurations” (page 113) 1-to-N Remote Copy “Disaster Recovery for 1-to-N Configurations” (page 124) Synchronous Long Distance Remote Copy “Disaster Recovery for Synchronous Long Distance” (page 134) Additional Information: “Quick Disaster Recovery Guide” (p
20 Disaster Recovery for 1-to-1 Configurations Before you begin disaster recovery: 1. Acquaint yourself with the example Remote Copy pair used to illustrate 1-to-1 disaster recovery. Figure 24 (page 104) 2. Familiarize yourself with system information for 1-to-1 configurations. “System Information during Normal Operation” (page 104) 3. Understand the system information to look for during a “System Information during Failover” (page 106) failover. Recover the systems: 1. 2. 3. 4.
Figure 24 Example Bidirectional 1-to-1 Remote Copy Configuration Example primary system Example backup system System name System1 System2 System ID 96 11 System1 = primary: • Two VVs: localvv.0 and localvv.1 Virtual volumes and volume groups • One primary volume group: sync_group_1 • Two corresponding VVs: remotevv.0 and remotevv.1 Data flow: • One secondary volume group: sync_group_1.
Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy System2 9 IP ready mirror_config Link Information Target System2 System2 receive receive Node 0 1 0 1 Address 10.100.33.11 10.101.33.11 10.100.33.11 10.101.33.11 Status Options Up Up Up Up Group Information Name Target Status sync_group_1 System2 Started LocalVV ID RemoteVV localvv.0 413 remotevv.0 localvv.1 414 remotevv.
localvv.0 localvv.1 385 386 remotevv.0 remotevv.1 423 424 Syncing (20%) NA Syncing (20%) NA System Information during Failover Synchronous Mode When a failure occurs on systems with synchronous mode volume groups such that all links between the systems are broken: • After 15 seconds, the system marks the sending links as Down. • After another 15 seconds, the system marks the targets as failed.
Recovering from Disaster Failover 1. Reverse the role of all volume groups on the system that is still in normal operation (the failover system). On the failover system (for example, System2), enter: # setrcopygroup failover -t • - Name of the target system that failed (System1) The setrcopygroup failover -t command: • Changes all secondary volume groups on the failover system (sync_group_1.
2. Verify the reversal of volume group roles. a. Issue the showrcopy command on the failover system (for example, System2). b. In the Group Information area, check that the Role column for the reversed volume group displays Primary-Rev (primary as a result of reversal). For example, the showrcopy output on System2 shows that the role of sync_group_1.
a. b. Issue the showrcopy command on the failover system (System2).
Link Information Target System2 System2 receive receive Node 0 1 0 1 Address 10.100.33.11 10.101.33.11 10.100.33.11 10.101.33.11 Status Options Up Up Up Up Group Information Name Target Status sync_group_1 System2 Started LocalVV ID RemoteVV localvv.0 413 remotevv.0 localvv.1 414 remotevv.1 Role Mode Options Secondary-Rev Sync ID SyncStatus LastSyncTime 375 Syncing Thu Dec 14 17:58:25 PST 2006 376 Syncing Thu Dec 14 17:58:25 PST 2006 Name Target Status Role Mode Options sync_group_2.
6. Verify that failback is complete and the natural direction of data flow is restored: a. Issue the showrcopy command on the failover system (System2). b. Verify that the Role of the secondary volume group is Secondary. For example, the showrcopy output on System2 shows that group sync_group_1.
d. Verify that the Role of the primary volume group is Primary. For example, the showrcopy output on System1 shows that group sync_group_1 is correctly restored to Primary: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy System2 9 IP ready mirror_config Link Information Target System2 System2 receive receive Node 0 1 0 1 Address 10.100.33.11 10.101.33.11 10.100.33.11 10.101.33.
21 Disaster Recovery for N-to-1 Configurations Before you begin disaster recovery: 1. Acquaint yourself with the example Remote Copy pair used to illustrate N-to-1 disaster recovery. Figure 25 (page 113) 2. Familiarize yourself with system information for N-to-1 configurations. “System Information during Normal Operation” (page 114) 3. Understand the system information to look for during a “System Information during Failover” (page 116) failover. Recover the systems: 1. 2. 3. 4.
Example first primary system Example second primary system Virtual volumes and volume • Two VVs: localvv.0 and groups: localvv.1 System2 = primary • One primary volume group: periodic_group_1 Data flow: Example backup system • Two corresponding VVs: remotevv.0 and remotevv.1 • One secondary volume group: periodic_group_1.r96 System2 —> System1 Virtual volumes and volume groups: • Two VVs: localvv.0 and localvv.
First Primary System (System2) When all systems are up, the showrcopy command output on one of the primary systems (for example, System2) looks like the output for this example N-to-1 configuration: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy System1 11 IP ready mirror_config Link Information Target System1 System1 receive receive Node 0 1 0 1 Address 10.100.33.63 10.101.33.63 10.100.33.63 10.101.33.
System Information during Failover Synchronous Mode When a failure occurs on systems with synchronous mode volume groups such that all links between the systems are broken: • After 15 seconds, the system marks the sending links as Down. • After another 15 seconds, the system marks the targets as failed.
Recovering from Disaster Failover 1. Reverse the role of all volume groups on the system that is still in normal operation (the failover system). On the failover system (for example, System1), enter: # setrcopygroup failover -t • - Name of the target system that failed (for example, System2) The setrcopygroup failover -t command: • Changes all secondary volume groups on the failover system (periodic_group_1.
2. Verify the reversal of volume group roles. a. Issue the showrcopy command on the failover system (System1). b. In the Group Information area, check that the Role column for the reversed volume group displays Primary-Rev (primary as a result of reversal). For example, the showrcopy output on System1 shows that the role of periodic_group_1.
2. When both systems in the Remote Copy pair are ready to resume normal operation, reverse the natural direction of data flow and resynchronize the systems. a. Stop I/O to the reversed volume groups on the failover system. b.
c. d. Issue the showrcopy command on the recovered system (System2).
• - Volume group that should be started (for example, periodic_group_1) Problem Solution If the volume groups are not started: 1. On the recovered system, issue: startrcopygroup or: startrcopygroup -pat • -pat - Pattern of volume group names (for example, periodic*) 2. Wait for the synchronizations to complete before continuing. CAUTION: The volume groups must be started before you continue to the next step and issue the setrcopygroup restore command. 5.
6. Verify that failback is complete and the natural direction of data flow is restored: a. Issue the showrcopy command on the failover system (System1). b. Verify that the Role of the secondary volume group is Secondary. For example, the showrcopy output on System1 shows that group periodic_group_1.
d. Verify that the Role of the primary volume groups is Primary. For example, the showrcopy output on System2 shows that group periodic_group_1 is correctly restored to Primary: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy System1 11 IP ready mirror_config Link Information Target System1 System1 receive receive Node 0 1 0 1 Address 10.100.33.63 10.101.33.63 10.100.33.63 10.101.33.
22 Disaster Recovery for 1-to-N Configurations Before you begin disaster recovery: 1. Acquaint yourself with the example Remote Copy pair used to illustrate 1-to-N disaster recovery. Figure 26 (page 124) 2. Familiarize yourself with system information for 1-to-N configurations. “System Information during Normal Operation” (page 125) 3. Understand the system information to look for during a “System Information during Failover” (page 127) failover. Recover the systems: 1. 2. 3. 4.
Example primary system Virtual volumes and volume • Two VVs, localvv.0 and groups: localvv.1, belong to primary volume group Data flow: periodic_group_1 System1 —> System2 • Two VVs, localvv.2 and System1 —> System3 localvv.3, belong to primary volume group periodic_group_2 Example first backup system Example second backup system • Two corresponding VVs: remotevv.0 and remotevv.1 • One secondary volume group: periodic_group_1.
First Backup System (System2) When all systems are up, the showrcopy command output on one of the backup systems (for example, System2) looks like the output for this example 1-to-N configuration: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy System1 11 IP ready mirror_config Link Information Target System1 System1 receive receive Node 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.33.96 10.101.33.
System Information during Failover Synchronous Mode When a failure occurs on systems with synchronous mode volume groups such that all links between the systems are broken: • After 15 seconds, the system marks the sending links as Down. • After another 15 seconds, the system marks the targets as failed.
Recovering from Disaster Failover 1. Reverse the role of all volume groups on the system that is still in normal operation (the failover system). On the failover system (for example, System2), enter: # setrcopygroup failover -t • - Name of the target system that failed (System1) The setrcopygroup failover -t command: • Changes all secondary volume groups on the failover system (periodic_group_1.
Recovery 1. 2. Recover the failed system. When both systems in the Remote Copy pair are ready to resume normal operation, reverse the natural direction of data flow and resynchronize the systems. a. Stop I/O to the reversed volume groups on the failover system. b.
d.
4. Verify that the volume groups are started. On the recovered system (System1), enter: # showrcopy groups • - Volume group that should be started (periodic_group_1) Problem Solution If the volume groups are not started: 1. On the recovered system, issue: startrcopygroup or: startrcopygroup -pat • -pat - Pattern of volume group names (for example, periodic*) 2. Wait for the synchronizations to complete before continuing.
6. Verify that failback is complete and the natural direction of data flow is restored: a. Issue the showrcopy command on the failover system (System2). b. Verify that the Role of the secondary volume group is Secondary. For example, the showrcopy output on System2 shows that group periodic_group_1.
Name Target Status Role Mode Options periodic_group_1 System2 Started Primary Periodic Last-Sync Thu Dec 14 18:39:03 PST 2006 , over_per_alert LocalVV ID RemoteVV ID SyncStatus LastSyncTime localvv.0 21 remotevv.0 413 Stale Thu Dec 14 18:40:14 PST 2006 localvv.1 22 remotevv.1 414 Stale Thu Dec 14 18:39:03 PST 2006 Name Target Status Role Mode Options periodic_group_2 System3 Started Secondary Periodic over_per_alert LocalVV ID RemoteVV ID SyncStatus LastSyncTime remotevv.2 23 localvv.
23 Disaster Recovery for Synchronous Long Distance Before you begin disaster recovery: 1. Acquaint yourself with the example Remote Copy pair used to illustrate synchronous long distance disaster recovery. Figure 27 (page 135) 2. Familiarize yourself with system information for synchronous long distance configurations. “System Information during Normal Operation” (page 135) 3.
Figure 27 Example Synchronous Long Distance Remote Copy Configuration Example primary system Example synchronous backup system Example asynchronous periodic backup system System name SystemA SystemB SystemC System ID 96 195 63 Virtual volumes and volume • Four VVs, testvv.0 groups: testvv.3, belong to primary volume group Data flow: multi.1 SystemA —> SystemB SystemA —> SystemC mode sync —> SystemB • Four corresponding VVs: • Four corresponding VVs: testvv.0 - testvv.3 testvv.0 - testvv.
Target SystemB SystemB SystemC SystemC receive receive receive receive Node 0:2:1 1:2:1 0:3:1 1:3:1 0:2:1 1:2:1 0:3:1 1:3:1 Address 20210002AC0000C3 21210002AC0000C3 10.100.33.63 10.101.33.63 20210002AC0000C3 21210002AC0000C3 receive receive Status Options Up Up Up Up Up Up Up Up Group Information Name multi.1 LocalVV testvv.0 testvv.1 testvv.2 testvv.3 Target Status SystemB Started ID RemoteVV 100 testvv.0 101 testvv.1 102 testvv.2 103 testvv.
testvv.0 testvv.1 testvv.2 testvv.3 Name multi.1.r96 LocalVV testvv.0 testvv.1 testvv.2 testvv.3 200 201 202 203 testvv.0 testvv.1 testvv.2 testvv.3 Target Status SystemC Backup ID RemoteVV 200 testvv.0 201 testvv.1 202 testvv.2 203 testvv.
System Information during Failover Synchronous Mode When a failure occurs on systems with synchronous mode volume groups such that all links between the systems are broken: • After 15 seconds, the system marks the sending links as Down. • After another 15 seconds, the system marks the targets as failed.
If the primary system (for example, SystemA) becomes unavailable, the showrcopy output on the asynchronous periodic backup system (for example, SystemC) looks like: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemA 42 IP failed mirror_config SystemB 44 IP ready mirror_config Link Information Target SystemA SystemA SystemB SystemB receive receive Node 0 1 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.33.195 10.101.33.
Failing Over to the Synchronous Backup System If the primary system fails or is taken offline, you can failover the storage system to the synchronous backup system if this system: • is still functioning properly • is not affected by the situation that took the primary system offline (in other words, is not in danger of failing as well) When the synchronous backup system becomes the failover system, the synchronous backup system temporarily assumes the role of the primary system.
Failover 1. Reverse the role of all volume groups on the synchronous backup system (the failover system). On the failover system (for example, SystemB), enter: # setrcopygroup failover -f -t • - Name of the target system that failed (for example, SystemA) The setrcopygroup failover -f -t command: • Changes all secondary volume groups on the failover system (multi.1.
3. Verify the reversal of volume group roles. a. Issue the showrcopy command on the failover system (SystemB). b. In the Group Information area, check that the Role column for the reversed volume group displays Primary-Rev (primary as a result of reversal). For example, the showrcopy output on SystemB shows that the role of multi.1.
4. Verify that the asynchronous periodic backup system (SystemC) is now the backup system. a. Issue the showrcopy command on the asynchronous periodic backup system (SystemC). b. In the Group Information area, verify that: • The volume groups on the asynchronous periodic backup system (SystemC) for which the target is the synchronous backup system (SystemB) are Started.
• - Name of the target system with which to synchronize (SystemA) The setrcopygroup recover command: • Switches the volume groups on the recovered system (SystemA) to secondary mode • Copies data from the reversed volume groups on the failover system (SystemB) to the corresponding volume groups on the recovered system (SystemA) The data used to synchronize the systems includes the snapshots taken when the recovered system (SystemA) went down as well as recent I/O to the failover system (S
b.
For example, the showrcopy output on SystemA looks like: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemB 58 FC ready 2FF70002AC0000C3 mirror_config SystemC 59 IP ready mirror_config Link Information Target SystemB SystemB SystemC SystemC receive receive receive receive Node 0:2:1 1:2:1 0:3:1 1:3:1 0:2:1 1:2:1 0:3:1 1:3:1 Address 20210002AC0000C3 21210002AC0000C3 10.100.33.63 10.101.33.
Target SystemA SystemA SystemB SystemB receive receive Node 0 1 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.33.195 10.101.33.195 receive receive Status Options Up Up Up Up Up Up Group Information Name multi.1.r96 LocalVV testvv.0 testvv.1 testvv.2 testvv.3 Target Status SystemA Backup ID RemoteVV 300 testvv.0 301 testvv.1 302 testvv.2 303 testvv.
CAUTION: The volume groups must be started before you continue to the next step and issue the setrcopygroup restore command. 5. Restore the natural direction of data flow to the Remote Copy system.
6. Verify that the Synchronous Long Distance setup is restored and operating normally. a. Issue showrcopy on the recovered system (SystemA) and verify that it has resumed the role of primary system.
# showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemA 46 FC ready 2FF70002AC000060 mirror_config SystemC 47 IP ready mirror_config Link Information Target SystemA SystemA SystemC SystemC receive receive receive receive Node 0:2:1 1:2:1 0:4:1 1:4:1 0:2:1 1:2:1 0:4:1 1:4:1 Address 20210002AC000060 21210002AC000060 10.100.33.63 10.101.33.
c. Issue showrcopy on the asynchronous periodic backup system (SystemC) and verify that it is in the role of backup system. For example, SystemC looks like: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemA 42 IP ready mirror_config SystemB 44 IP ready mirror_config Link Information Target SystemA SystemA SystemB SystemB receive receive Node 0 1 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.33.195 10.101.33.
Figure 29 Failing Over to the Asynchronous Periodic System with Data Transfer Failover 1. Reverse the role of all volume groups on the asynchronous periodic backup system (the failover system). On the failover system (for example, SystemC), enter: # setrcopygroup failover -f -t • - Name of the target system that failed (for example, SystemA) The setrcopygroup failover -f -t command: 2.
failover started with tasks: 6740 root@xnodeeca5:~/bin# waittask -v 6740 Id Type Name Status Phase Step -------StartTime------- -FinishTime6740 remote_copy_failover multi.1.r96 active 1/3 0/1 2009-06-29 14:43:44 PDT - Detailed status: 2009-06-29 14:43:44 PDT Created task. 2009-06-29 14:43:44 PDT Begin Failover operation on group multi.1.r96 started. 2009-06-29 14:43:47 PDT Pushing Pushing newer data from target SystemB to group multi.1.r96.
3. Verify that the newer data is being pushed to the failover system. a. While Remote Copy progresses through the failover tasks, issue the showrcopy command on the synchronous backup system (SystemB).
# showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemA 42 IP failed mirror_config SystemB 44 IP ready mirror_config Link Information Target SystemA SystemA SystemB SystemB receive receive Node 0 1 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.33.195 10.101.33.195 receive receive Status Options Down Down Up Up Up Up Group Information Name multi.1.r96 LocalVV testvv.0 testvv.1 testvv.2 testvv.
4. Verify the reversal of volume group roles. a. Issue the showrcopy command on the failover system (SystemC). b. In the Group Information area, check that: • the Role column for the reversed volume group displays Primary-Rev (primary as a result of reversal) • the SyncStatus column of the virtual volumes displays Synced For example, the showrcopy output on SystemC shows that the role of multi.1.
# showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemA 46 FC failed 2FF70002AC000060 mirror_config SystemC 47 IP ready mirror_config Link Information Target SystemA SystemA SystemC SystemC receive receive receive receive Node 0:2:1 1:2:1 0:4:1 1:4:1 0:2:1 1:2:1 0:4:1 1:4:1 Address 20210002AC000060 21210002AC000060 10.100.33.63 10.101.33.
In this example, Remote Copy copies data from the virtual volumes in volume group multi.1.r96 on SystemC to multi.1 on SystemA. • Starts Remote Copy on the recovered system (SystemA) For example, the list of tasks launched by the setrcopygroup recover command on SystemC looks like: # setrcopygroup recover -f -t SystemA recover started with tasks: 6747 root@xnodeed08:~/bin# waittask -v 6747 Id Type Name Status Phase Step -------StartTime------- -FinishTime6747 remote_copy_recover multi.1.
b.
Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemB 58 FC ready 2FF70002AC0000C3 mirror_config SystemC 59 IP ready mirror_config Link Information Target SystemB SystemB SystemC SystemC receive receive receive receive Node 0:2:1 1:2:1 0:3:1 1:3:1 0:2:1 1:2:1 0:3:1 1:3:1 Address 20210002AC0000C3 21210002AC0000C3 10.100.33.63 10.101.33.
f.
4. Verify that the volume groups are started. On the recovered system (SystemA), enter: # showrcopy groups • - Volume group that should be started (for example, multi.1) Problem Solution If the volume groups are not started: 1. On the recovered system, issue: startrcopygroup or: startrcopygroup -pat • -pat - Pattern of volume group names (for example, multi*) 2. Wait for the synchronizations to complete before continuing.
SystemB. 2009-06-29 14:56:56 PDT Waiting SystemA to complete. 2009-06-29 14:56:56 PDT Waiting SystemB to complete. 2009-06-29 14:57:14 PDT Stopped 2009-06-29 14:57:15 PDT Switched secondary to primary. 2009-06-29 14:57:16 PDT Switched 2009-06-29 14:57:16 PDT Waiting snapshot promotions. 2009-06-29 14:57:17 PDT Starting 2009-06-29 14:57:25 PDT Started SystemA. 2009-06-29 14:57:25 PDT Completed Waiting for synchronization of group multi.1.r96 to target Waiting for synchronization of group multi.1.
6. Verify that the Synchronous Long Distance setup is restored and operating normally. a. Issue showrcopy on the recovered system (SystemA) and verify that it has resumed the role of primary system.
# showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemA 46 FC ready 2FF70002AC000060 mirror_config SystemC 47 IP ready mirror_config Link Information Target SystemA SystemA SystemC SystemC receive receive receive receive Node 0:2:1 1:2:1 0:4:1 1:4:1 0:2:1 1:2:1 0:4:1 1:4:1 Address 20210002AC000060 21210002AC000060 10.100.33.63 10.101.33.
c. Issue showrcopy on the asynchronous periodic backup system (SystemC) and verify that it has resumed the role of backup system. For example, SystemC looks like: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemA 42 IP ready mirror_config SystemB 44 IP ready mirror_config Link Information Target SystemA SystemA SystemB SystemB receive receive Node 0 1 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.33.195 10.101.33.
Failing Over to the Asynchronous Periodic Backup System (No Data Transfer) If the primary system fails or is taken offline, you can failover the storage system to the asynchronous periodic backup system without a final data transfer from the synchronous backup system if: • The asynchronous periodic backup system is functioning properly. • The asynchronous periodic backup system contains the most current data. • The synchronous backup system also failed or was brought down.
Failover 1. Reverse the role of all volume groups on the asynchronous periodic backup system (the failover system). On the failover system (for example, SystemC), enter: # setrcopygroup failover -f -discard -t • - Name of the target system that failed (for example, SystemA) The setrcopygroup failover -f -discard -t command: 2.
3. Verify the reversal of volume group roles. a. Issue the showrcopy command on the failover system (SystemC). b. In the Group Information area, check that: • the Role column for the reversed volume group displays Primary-Rev (primary as a result of reversal) • the SyncStatus column of the virtual volumes displays Synced For example, the showrcopy output on SystemC shows that the role of multi.1.
# showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemA 46 FC failed 2FF70002AC000060 mirror_config SystemC 47 IP ready mirror_config Link Information Target SystemA SystemA SystemC SystemC receive receive receive receive Node 0:2:1 1:2:1 0:4:1 1:4:1 0:2:1 1:2:1 0:4:1 1:4:1 Address 20210002AC000060 21210002AC000060 10.100.33.63 10.101.33.
• - Name of the target system with which to synchronize (SystemA) The setrcopygroup recover command: • Switches volume groups on the recovered system (SystemA) to secondary mode • Copies data from the reversed volume groups on the failover system (SystemC) to the corresponding volume groups on the recovered system (SystemA) The data used to synchronize the systems includes the snapshots taken when the recovered system (SystemA) went down as well as recent I/O to the failover system (Syste
multi.1 5909 rcpy.222.103.59.1 snp vcopy testvv.3 103 RO normal -- -- -- 1024 snap multi.1 5915 rcpy.222.103.58 snp vcopy testvv.3 103 RO normal -- -- -- 1024 snap multi.1 3. Verify that the primary system is up and the Remote Copy pairs are synchronized: a. Issue the showrcopy command on the failover system (SystemC). b.
d.
f.
4. Verify that the volume groups are started. On the recovered system (SystemA), enter: # showrcopy groups • - Volume group that should be started (for example, multi.1) Problem Solution If the volume groups are not started: 1. On the recovered system, issue: startrcopygroup or: startrcopygroup -pat • -pat - Pattern of volume group names (for example, multi*) 2. Wait for the synchronizations to complete before continuing.
2009-06-29 14:56:56 PDT Waiting SystemA to complete. 2009-06-29 14:56:56 PDT Waiting SystemB to complete. 2009-06-29 14:57:14 PDT Stopped 2009-06-29 14:57:15 PDT Switched secondary to primary. 2009-06-29 14:57:16 PDT Switched 2009-06-29 14:57:16 PDT Waiting snapshot promotions. 2009-06-29 14:57:17 PDT Starting 2009-06-29 14:57:25 PDT Started SystemA. 2009-06-29 14:57:25 PDT Completed 176 Waiting for synchronization of group multi.1.r96 to target Waiting for synchronization of group multi.1.
6. Verify that the Synchronous Long Distance setup is restored and operating normally. a. Issue showrcopy on the recovered system (SystemA) and verify that it has resumed the role of primary system.
# showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemA 46 FC ready 2FF70002AC000060 mirror_config SystemC 47 IP ready mirror_config Link Information Target SystemA SystemA SystemC SystemC receive receive receive receive Node 0:2:1 1:2:1 0:4:1 1:4:1 0:2:1 1:2:1 0:4:1 1:4:1 Address 20210002AC000060 21210002AC000060 10.100.33.63 10.101.33.
c. Issue showrcopy on the asynchronous periodic backup system (SystemC) and verify that it has resumed the role of backup system. For example, SystemC looks like: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy SystemA 42 IP ready mirror_config SystemB 44 IP ready mirror_config Link Information Target SystemA SystemA SystemB SystemB receive receive Node 0 1 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.33.195 10.101.33.
Part V Remote Copy Concepts For conceptual information on: See the following: Remote Copy pairs and targets, target definitions, target systems, “Remote Copy Pairs and Targets” (page 181) and data flow between pairs Sending and receiving links “Remote Copy Links” (page 184) Virtual volumes supported by Remote Copy and basics about using CPGs “Virtual Volumes and CPGs” (page 187) Rules for forming volume groups, volume group organization on “Volume Groups” (page 190) the servers, and naming conventions
24 Remote Copy Pairs and Targets For more information on: See: The foundational Remote Copy system relationship “Remote Copy Pairs” (page 181) Why Remote Copy uses targets “Overview of Targets” (page 181) How to determine the target definition for a system or volume group “Target Definitions” (page 181) The target system, and data flow between systems under various circumstances “Remote Copy Target System” (page 182) Remote Copy Pairs Remote Copy configurations and operations are based on the Remo
• This relationship between target definitions and Remote Copy system pairs is true for all valid Remote Copy configurations (unidirectional, bidirectional, N-to-1, 1-to-N, and synchronous long distance). • For the system that contains the primary volume groups (the primary system), the target system is the same as the backup system. For the system that contains the secondary volume groups (the backup system), the target system is the same as the primary system.
Specifically, Remote Copy replicates data from the primary volume groups, which you name and which reside on the primary system, to the secondary volume groups, which Remote Copy names and which reside on the backup system. For more information, see “Creating Remote Copy Volume Groups” (page 71).
25 Remote Copy Links For more information on: See: Rules for creating sending links “Sending Links” (page 184) How Remote Copy uses receiving links “Receiving Links” (page 186) Remote Copy links are divided into two main types: sending links and receiving links. • You create sending links during Remote Copy setup (using the creatercopytarget or admitrcopylink command). For more information, see “Setting Up a Unidirectional Configuration” (page 67).
Figure 32 Supported Sending Link Connections Links per Remote Copy Pair When you set up Remote Copy links between a Remote Copy pair, you must create one set of sending links on the primary system and one set of sending links on the backup system [Figure 33 (page 185)].
Receiving Links Remote Copy uses receiving links to: • listen for Remote Copy data and commands from the target system in the Remote Copy pair • read the incoming data and commands • send the data and commands to the appropriate Remote Copy process Unlike sending links, there is only a single link of a given type per node, regardless of the number of sending links of that type.
26 Virtual Volumes and CPGs To create virtual volumes for Remote Copy: For more information, see: 1. Create a Common Provisioning Group (CPG). • “Common Provisioning Groups” (page 187) • HP 3PAR InForm OS CLI Administrator’s Manual 2. Create virtual volumes that draw space from that CPG and that adhere to the rules for Remote Copy virtual volumes.
Basic Information about CPGs CAUTION: For a complete list of warnings and cautions regarding CPGs, refer to the HP 3PAR InForm OS Concepts Guide. • CPGs require careful planning and monitoring to prevent them from becoming so large that they set off the system's built-in safety mechanisms. These safety mechanisms are designed to prevent a CPG from consuming all free space on the system, but they only work properly on systems that are planned carefully and monitored closely.
Rules for Creating Remote Copy Virtual Volumes • The primary and secondary virtual volumes to be linked (for example, vv1 and vv1_remote) must be the same size. • Volumes can have different RAID levels and availability levels (Cage, Magazine, and so on). • Volumes must be one of the following: • ◦ TPVVs ◦ Fully provisioned virtual volumes You can save read/write (RW) snapshots to Remote Copy volume groups. For more information, see “Rules for Adding Snapshots to Volume Groups” (page 191).
27 Volume Groups For more information on: See: What volume groups are and why Remote Copy uses them “Why Use Volume Groups” (page 190) How Remote Copy operates on virtual volumes in a volume “How Volume Groups Work” (page 191) group Volumes you can add to volume groups “Rules for Forming Volume Groups” (page 191) “Rules for Adding Snapshots to Volume Groups” (page 191) How Remote Copy names the secondary volume group “Natural Direction of Replication” (page 192) Where primary and secondary volume grou
How Volume Groups Work Remote Copy functions as if the virtual volumes in a volume group are related and therefore ensures that the data in the virtual volumes within a volume group maintain write consistency. • When you start or stop Remote Copy operations, Remote Copy starts and stops operations for the whole volume group.
For more information about snapshot creation, see “Remote Copy Snapshots” (page 203). How Volume Groups Are Organized on the Remote Copy Pair Primary volume groups store the virtual volumes to be copied. Under normal operating conditions: • The data in the volumes in the primary volume groups is the most up-to-date. • Primary volume groups reside on the primary system. Secondary volume groups store the copied virtual volumes.
Figure 35 Mapping of Volumes between Bidirectional Primary and Backup Systems Linking Virtual Volumes in Volume Groups 193
28 Volume Group Modes For information on: See: Comparison of the two types of modes “Overview of Volume Group Modes” (page 194) How Remote Copy volume groups operate in synchronous “Synchronous Mode” (page 194) mode How Remote Copy volume groups operate in asynchronous “Asynchronous Periodic Mode” (page 195) periodic mode Overview of Volume Group Modes Volume Group Mode Description synchronous (in output: sync) Synchronous mode volume groups stay synchronized at all times.
6. After the active cache update on the primary system is complete and the primary system receives the backup system’s acknowledgement, Remote Copy sends an acknowledgement of the write to the host. Synchronization is complete. Figure 36 Remote Copy in Synchronous Mode Advantages of Synchronous Mode • Even if the primary system, the backup system, or the communication links go down, Remote Copy retains all I/O that has already been acknowledged.
5. The primary and backup systems are resynchronized periodically: • automatically: according to the schedule specified by the setrcopygroup command • manually: when you issue the syncrcopy command Figure 37 Remote Copy in Asynchronous Periodic Mode Advantages of Asynchronous Periodic Mode If one area of a volume is written to multiple times between two resynchronizations, Remote Copy only needs to send the last write to the backup system.
29 Synchronization Types and Limits For more information on: See: The two types of synchronization Remote Copy performs “Types of Synchronization” (page 197) The number of virtual volumes that Remote Copy synchronizes at the same time “Limits on Volumes that Concurrently Synchronize” (page 197) How Remote Copy synchronizes asynchronous periodic mode volume groups “Asynchronous Periodic Mode Volume Groups” (page 198) Considerations for resynchronizing asynchronous periodic “Setting Up Resynchronizati
To ensure volume group consistency, Remote Copy maintains all the snapshots for the secondary asynchronous periodic volume group on the backup system until all of the virtual volumes in that volume group are synchronized. For more information, see “Remote Copy Snapshots” (page 203). Asynchronous Periodic Mode Volume Groups For asynchronous periodic mode volume groups: 1. The initial synchronization (a full synchronization) creates snapshots on the backup system. 2.
4. saves the active snapshot, which enables Remote Copy to perform a fast resynchronization later [Figure 40 (page 200)] Figure 39 Full Synchronization Using Primary Volume Snapshots (Asynchronous Periodic Mode) Resychronization Remote Copy performs a resynchronization if both: • The primary volume was previously synchronized, and • A valid (up-to-date) resynchronization snapshot exists. When performing a resynchronization (Figure 40 (page 200)), Remote Copy: 1.
6. saves the newer snapshot for a future resynchronization CAUTION: Because Remote Copy uses multiple snapshots during resynchronization, you must ensure that the space available to virtual volumes is adequate. For more information, see “Virtual Volumes and CPGs” (page 187).
Setting Up Resynchronization for Asynchronous Periodic Mode How to Set the Synchronization Period For Remote Copy to automatically resynchronize asynchronous periodic mode volume groups, you must configure the synchronization period for the volume group. There is no default synchronization period. • To set the synchronization period, use the setrcopygroup command. For more information, see “The Remote Copy Commands” (page 224).
Resynchronization • To resynchronize synchronous mode volume groups, Remote Copy copies the I/O directly from the primary base volume. For more information, see “Volume Group Modes” (page 194). • When synchronous mode volume groups are stopped, Remote Copy creates snapshots of the volume groups. When these volume groups are restarted, Remote Copy uses the snapshots to resynchronize the primary and secondary volume groups. For more information, see “Remote Copy Snapshots” (page 203).
30 Remote Copy Snapshots For information on: See: What snapshots are and why Remote Copy uses them “Why Use Snapshots” (page 203) Ensuring virtual volumes have enough space to create the “Volume Space Considerations” (page 203) necessary snapshots In synchronous mode, when Remote Copy takes snapshots “Snapshots and Initial Synchronization Failure” (page 204) and what it does with them “Snapshots and Resynchronization” (page 204) “Snapshots and Resynchronization Failure” (page 204) “Snapshots Taken befor
Snapshots in Synchronous Mode In synchronous mode, Remote Copy creates snapshots only when: • an error occurs • disaster recovery is in process • a volume group is manually stopped Snapshots and Initial Synchronization Failure If a failure occurs during the initial (and therefore full) synchronization of a virtual volume: • Remote Copy does not create a snapshot of that volume.
a. b. creates snapshots of all the secondary virtual volumes that were previously synchronized resynchronizes the secondary virtual volume by sending only the differences between the resynchronization snapshot and the current data in the primary virtual volume. • If a resynchronization snapshot does not exist, Remote Copy performs a full synchronization.
Snapshots and Resynchronization Failure If the primary system fails during resynchronization, Remote Copy uses the snapshot taken on the backup system to recover the backup system’s consistent state before the resync operation began: • If a volume did not resynchronize, Remote Copy automatically promotes the snapshot to the secondary base volume. • The duration of the promotion operation is proportional to the amount of data changed before the resynchronization failed.
31 Error Handling For more information on: See: The timeout periods per type of failure and volume group mode “Timeouts for Remote Copy Failure” (page 207) The effect of one link failing “Failure of a Single Link” (page 207) What happens when all links in a Remote Copy pair fail “Failure of All Links” (page 208) How Remote Copy handles system failures “Failure of a Storage System” (page 209) Different types of write errors “Write Errors” (page 209) Different types of read errors “Read Errors” (
Failure of All Links When all links between storage systems in a Remote Copy pair fail, the two systems cannot communicate. After failure of all links: • Both systems declare the other system to be down. • Both systems generate alerts regarding the other system’s failure. The system handles complete link failure differently depending on whether the links are used for synchronous or asynchronous periodic mode volume groups.
Link Failure and Asynchronous Periodic Volume Groups For asynchronous periodic volume groups, when all links between a Remote Copy pair fail: • Remote Copy stops replication on both storage systems. • Remote Copy does not create any new snapshots. • If a resynchronization was in progress when the failure occurred, Remote Copy automatically promotes the pre-existing snapshots on the secondary volume group—but only for those volumes that did not complete resynchronization.
For more information on volume group modes, see “Volume Group Modes” (page 194). Write Errors and Synchronous Volume Groups For synchronous volume groups, when a write error occurs on the backup system: • The host I/O completes without error. • Remote Copy stops replication for the volume group. • Remote Copy creates snapshots of each virtual volume in the volume group.
If this type of read fails, Remote Copy: • cancels the synchronization process • marks the secondary volume as NotSynced • does not stop the volume group To synchronize the volume group, issue the syncrcopy command. Read Errors during Resynchronization of Asynchronous Periodic Volume Groups As long as you have set a synchronization period, asynchronous periodic volume groups are automatically resynchronized at the scheduled synchronization interval.
Part VI Appendices For information on: See the following: Quick setup steps for RCIP, RCFC, and Remote Copy configurations “Quick Setup Guide” (page 213) Quick disaster recovery steps for Remote Copy “Quick Disaster Recovery Guide” (page 220) CLI commands relevant to Remote Copy “About the Remote Copy Commands” (page 222) Remote Copy support for other features “Remote Copy and Other Features” (page 289)
A Quick Setup Guide To set up: See: Transport layer for Remote Copy over IP (RCIP) “Quick Setup: RCIP Transport Layer” (page 214) Transport layer for Remote Copy over Fibre Channel (RCFC) “Quick Setup: RCFC Transport Layer” (page 215) Remote Copy configurations and scripts “Quick Setup: Remote Copy Configurations” (page 215) Unidirectional Remote Copy “Quick Setup: Unidirectional Remote Copy” (page 216) Bidirectional Remote Copy “Quick Setup: Bidirectional Remote Copy” (page 217) Synchronous Long
Quick Setup: RCIP Transport Layer Table 2 Quick Setup Steps for RCIP Step Reference Primary System Backup System 1. On all RCIP ports, set up “Setting Up the Remote the interface. Copy Interface for RCIP” (page 33) controlport rcip addr [-f] controlport rcip addr [-f] 2. Verify IP addresses and netmask. showport -rc showport -rc 3. On all RCIP ports, set the “Setting the Gateway” gateways.
Quick Setup: RCFC Transport Layer Table 3 Quick Setup Steps for RCFC Step Primary System Backup System 1. On all RCFC ports, set up “Setting Up the Remote the interface. Copy Interface for RCFC” (page 39) controlport config rcfc -ct point -f controlport config rcfc -ct point -f 2. On all RCFC ports, get RCFC port positions. “ showport -rcfc showport -rcfc 3. Verify links. “ showrctransport -rcfc showrctransport -rcfc 4. On each RCFC port, initialize port.
Quick Setup: Unidirectional Remote Copy Table 4 Quick Setup Steps for Unidirectional Pairs: 1-to-1, N-to-1, and 1-to-N Configurations Step Reference Primary System 1. Start Remote Copy. “Setting Up the Primary System” (page 68) startrcopy — RCIP: creatercopytarget IP : — 2. Define a target. “ Backup System RCFC: creatercopytarget FC 3. Start Remote Copy. 4. Define a target.
Table 4 Quick Setup Steps for Unidirectional Pairs: 1-to-1, N-to-1, and 1-to-N Configurations (continued) Step Reference Primary System Backup System Primary Volume Groups” (page 74) 11. Verify synchronization. showrcopy Quick Setup: Bidirectional Remote Copy Table 5 Quick Setup Steps for the Bidirectional Pair: 1-to-1, N-to-1, and 1-to-N Configurations Step Reference Primary System Backup System 1. Verify that a unidirectional Remote Copy pair is already set up.
Quick Setup: Synchronous Long Distance Remote Copy Table 6 Quick Setup Steps for Synchronous Long Distance Configurations Step Reference Primary System Sync System Periodic System 1. Start Remote Copy. “Setting Up the Primary System” (page 59) startrcopy — — 2. Define target for sync backup system. “ Assuming RCFC: creatercopytarget FC : — — 3. Define target for periodic backup system.
Table 6 Quick Setup Steps for Synchronous Long Distance Configurations (continued) Step Reference Primary System Sync System Periodic System : 14. Start replication. 15. Verify sync.
B Quick Disaster Recovery Guide To recover from primary system downtime for: See: 1-to-1 “Quick Recovery: 1-to-1, N-to-1, and 1-to-N Configurations” (page 220) N-to-1 1-to-N Synchronous Long Distance “Quick Recovery: Synchronous Long Distance Configurations” (page 221) Additional Information: • “Disaster Recovery for 1-to-1 Configurations” (page 103) • “Disaster Recovery for N-to-1 Configurations” (page 113) • “Disaster Recovery for 1-to-N Configurations” (page 124) • “Disaster Recovery for Syn
Quick Recovery: Synchronous Long Distance Configurations Table 8 Quick Recovery Steps for Synchronous Long Distance Configurations Step Failover System 1. Change secondary volume groups to primary. setrcopygroup failover -f -t Failed/Recovered System Backup System (of failed system) OR (no data transfer): setrcopygroup failover -f -t -discard (possible data loss) 2. Verify group reversal. Verify that failover tasks complete successfully. 3. Back up data.
C About the Remote Copy Commands In order to: See this command: Create a link to a target system admitrcopylink Add a target system to an HP 3PAR Storage System admitrcopytarget Add an existing virtual volume to an existing Remote Copy admitrcopyvv volume group Perform a connectivity, latency, and throughput test between two connected systems checkrclink Set Remote Copy interface information controlport Create a Remote Copy volume group (can be run by users creatercopygroup with Edit privileges) S
NOTE: See also showvv -rcopy in the HP 3PAR Inform OS CLI Reference. Issuing Remote Copy Commands • Enter Remote Copy commands using the HP 3PAR Command Line Interface (CLI). For more information, see the HP 3PAR CLI Reference Guide.
D The Remote Copy Commands 224 The Remote Copy Commands
admitrcopylink NAME admitrcopylink -- The admitrcopylink command adds one or more links (connections) to a Remote Copy target system. SYNTAX • For Remote Copy over IP (RCIP), the syntax for the admitrcopylink command is as follows: admitrcopylink ... • For Remote Copy over fibre channel (RCFC), the syntax for the admitrcopylink command is as follows: admitrcopylink ... AUTHORITY Super, Edit Any role granted the rcopylink_admit right.
• For IP targets this list is made up of pairs composed of the node of the Ethernet port on the local system and an IP address of the peer port on the target system. • For FC targets this list is made up of sets with the node, slot, and port of the FC port on the local system and WWN of the peer port on the target system. • The specifier has been deprecated.
admitrcopytarget NAME admitrcopytarget -- The admitrcopytarget command adds a target to a Remote Copy volume group. SYNTAX admitrcopytarget [:]... AUTHORITY Super, Edit Any role granted the rcopytarget_admit right. NOTE: You need access to all domains in order to run this command. OPTIONS None. SPECIFIERS Specifies the name of the target that was previously created with the creatercopytarget command.
admitrcopyvv NAME admitrcopyvv -- The admitrcopyvv command adds an existing virtual volume to an existing Remote Copy volume group. SYNTAX admitrcopyvv :... admitrcopyvv -pat :... AUTHORITY Super, Edit Any role granted the rcopyvv_admit right. NOTE: You need access to the domain of the specified group () in order to run this command.
In the following example, the admitrcopyvv command adds all volumes beginning with tpvv to the primary volume group Group1. At the same time, it adds the secondary volumes, which are named the same as the primary virtual volumes (as specified by @vvname@), on the target system System2 to the corresponding secondary volume group (Group1.r). # admitrcopyvv -pat tpvv* Group1 System2:@vvname@ NOTES • A secondary volume mapping must be provided for each target in the group.
checkrclink NAME checkrclink -- The checkrclink command performs a connectivity, latency, and throughput test between two connected Systems. SYNTAX • checkrclink startclient
. . . ============================================================ TEST SUMMARY from 0:0:1 -> 10.100.18.164 Test Started: Wed Aug 10 10:34:15 PST 2011 Test Finished: Wed Aug 10 10:34:26 PST 2011 ============================================================ Latency: Lost pings: Through-put: Max MTU: Tx TCP Segs: Rx TCP Segs: TCP retrans: Errored Segs: 0.
controlport NAME controlport -- The controlport command controls all aspects of a Fibre Channel or Remote Copy port, including the port’s connection type and data rate. The controlport rcip and controlport rcfc commands are required for setting up Remote Copy interfaces. SYNTAX The syntax for the controlport rcip and rcfc commands can be one of the following: • controlport config [-ct ][-unique_nwwn enable|disable] [-f] ...
offline Holds the specified port offline indefinitely. Issue controlport rst to bring the port back online. lip Specifies that a Loop Initialization Primitive (LIP) command is issued from the port if there is a private loop topology. If the -c option is specified, then the LIP command is issued through the specified drive cage. If there is a point-to-point topology, then the link is reset.
rcip ping Performs a ping from the specified interface to the specified address. Only for RCIP ports. See “SPECIFIERS” (page 235) for parameters required to issue this subcommand. Use with the –pf option to prevent fragmentation of packets (see “OPTIONS” (page 234)). rcfc init Initializes the Fibre Channel interface on the specified port. Refer to “SPECIFIERS” (page 235) for parameters required to issue this subcommand. rcfc delete Deletes the Fibre Channel interface on the specified port.
-unique_nwwn enable|disable Enable or disable the use of a unique node WWN on the specified port SPECIFIERS Specifies the connection parameter of the port. Parameters can be loop, or point. The loop parameter sets the port to arbitrated loop mode, the point parameter sets the port to point-to-point mode. This specifier must be provided when issuing the ct subcommand. Specifies the Fibre Channel Class-2 parameter of the port. Parameters can be one of ack0, ack1, or disable.
RESTRICTIONS • See the HP 3PAR InForm OS CLI Reference for a complete list of restrictions. • The controlport rcip addr command is only allowed for node/slot/port combinations where there is an interface installed. EXAMPLES The following example shows how to increase MTU to 9000 on Gigabit Ethernet port 1 in node 6, slot 3: # controlport rcip mtu 9000 6:3:1 Remote Copy change successful. The following example shows how to set Remote Copy interface 172.16.1.
• The ct, cl2, or rate subcommands automatically reset the port for the changes to take effect. • Issue the showport command with either the -i or -par options to verify the success of the controlport command. • Resetting a port causes a momentary dip in throughput, but no loss of connectivity. • Use caution when changing modes for ports in LSI Fibre Channel adapters.
creatercopygroup NAME creatercopygroup -- The creatercopygroup command creates a Remote Copy volume group. SYNTAX creatercopygroup [options] [:...] AUTHORITY Super, Edit Any role granted the rcopygroup_create right. OPTIONS -domain Creates the Remote Copy group in the specified domain. The volume group must be created by a member of a particular domain with Super or Edit privileges.
mirror_config policy is set and the group is a secondary group, then this command will fail. • The maximum length of the group is 22 characters if the mirror_config option policy is set for the specified target. If it is not set, the maximum length is 31 characters. • For multiple target Remote Copy groups, when creating a group with multiple targets, the groups created on those targets will also be created with a backup target between the secondary groups.
creatercopytarget NAME creatercopytarget -- The creatercopytarget command creates a Remote Copy target definition. SYNTAX The syntax for the creatercopytarget command can be one of the following: • Syntax for Remote Copy over IP (RCIP) is as follows: creatercopytarget [options] IP []... • Syntax for Remote Copy over Fibre Channel (RCFC) is as follows: creatercopytarget [options] FC []...
The following example creates a primary target definition named System1 on the backup system, where the node numbers of the backup system’s Ethernet ports are located at 2:3:1 and 3:3:1 and the corresponding IP addresses on the primary system are 10.1.1.96 and 10.1.2.96: # creatercopytarget System1 IP 2:3:1:10.1.1.96 3:3:1:10.1.2.
dismissrcopylink NAME dismissrcopylink -- The dismissrcopylink command removes one or more links (connections) created with the admitrcopylink command to a target system. SYNTAX • Syntax for Remote Copy over IP (RCIP) is as follows: dismissrcopylink ... • For Remote Copy over Fibre Channel (RCFC): dismissrcopylink ... AUTHORITY Super, Edit Any role granted the rcopylink_dismiss right.
dismissrcopytarget NAME dismissrcopytarget -- The dismissrcopytarget command removes a Remote Copy target from a Remote Copy volume group. SYNTAX dismissrcopytarget AUTHORITY Super, Edit Any role granted the rcopylink_dismiss right. NOTE: You need access to all domains in order to run this command. OPTIONS None. SPECIFIERS The name of the target to be removed. The name of the group that currently includes the target.
dismissrcopyvv NAME dismissrcopyvv -- The dismissrcopyvv command removes a virtual volume from a Remote Copy volume group. SYNTAX dismissrcopyvv [option] [] AUTHORITY Super, Edit Any role granted the rcopyvv_dismiss right. NOTE: You need access to the domain of the specified group () in order to run this command. OPTIONS -f Does not ask for confirmation for the dismissrcopyvv command.
growvv NAME growvv -- The growvv command increases the size of a virtual volume. SYNTAX growvv [g|G|t|T] AUTHORITY Super, Edit Any role granted the vv_grow right. NOTE: You need access to the domain of the specified group () in order to run this command. OPTIONS None. SPECIFIERS The name of the volume to be grown. [g|G|t|T] The size to be added to the volume’s user space. The size is specified in multiples of 256 MB.
histrcvv NAME histrcvv -- The histrcvv command shows a histogram of total Remote Copy service times and backup system Remote Copy service times in a timed loop. SYNTAX histrcvv [options ][|]... AUTHORITY Any role in the system. OPTIONS -d Specifies the interval in seconds that statistics are sampled from using an integer from 1 through 2147483. If no count is specified, the command uses a 2-second default interval.
-timecols For the I/O time histogram, shows the columns from the first column () through the last column (). The available columns range from 0 through 31. • must be equal to or greater than 0. The default value of is 6. • must be: ◦ greater than ◦ less than or equal to 31 The default value of is 15. -pct Shows the number of times the service time appears in each bucket as a percentage.
128 256 testvv.2 multi.1 amp2 Sync 0 0 0 163 61 16 3 0 0 0 0 224 19 0 0 0 0 0 0 0 testvv.3 multi.1 amp2 Sync 0 0 0 138 62 37 4 2 0 0 0 224 19 0 0 0 0 0 0 0 testvv.8 sync.2 amp3 Sync 0 0 0 0 0 4 13 11 5 4 0 0 0 0 4 12 12 7 1 1 testvv.4 multi.1 amp2 Sync 0 0 0 54 132 52 17 2 0 0 0 252 5 0 0 0 0 0 0 0 testvv.0 multi.1 amp2 Sync 0 0 0 59 138 57 17 2 0 0 0 258 15 0 0 0 0 0 0 0 testvv.9 sync.2 amp3 Sync 0 0 0 0 1 0 14 8 6 3 0 0 0 0 2 7 14 4 4 1 testvv.1 multi.
removercopygroup NAME removercopygroup -- The removercopygroup command removes a Remote Copy volume group or multiple Remote Copy groups that match a given pattern. SYNTAX removercopygroup |... AUTHORITY Super, Edit Any role granted the rcopygroup_remove right. OPTIONS -f Specifies that the command is forced. If this option is not used, the command requires confirmation before proceeding with its operation.
NOTES • If the mirror_config policy is set for this group’s target system and the group is a primary group, then this command will be mirrored to the target and the corresponding secondary group will also be removed. If the policy is set and the group is a secondary group, then this command will fail. • The removercopygroup command removes all the associations configured in the specified group and removes the group name and any Remote Copy synchronization snapshots affiliated with volumes in the group.
removercopytarget NAME removercopytarget -- The removercopytarget command removes target designation from a Remote Copy system and removes all links affiliated with that target definition. SYNTAX removercopytarget [options] AUTHORITY Super, Edit Any role granted the rcopytarget_remove right. NOTE: You need access to all domains in order to run this command. OPTIONS -cleargroups Remove all groups that have no other targets or dismiss this target from groups with additional targets.
setrcopygroup NAME setrcopygroup -- The setrcopygroup command does the following: SYNTAX The syntax for the setrcopygroup command can be one of the following: • setrcopygroup pol [options] |... • setrcopygroup period |... • setrcopygroup mode |... • setrcopygroup [options] |...
–nopromote This option is only valid for the failover and reverse specifiers. When used with the reverse specifier, specifies that the synchronized snapshot of the volume groups that are switched from primary to secondary is not to be promoted to the base volume.
• over_per_alert - If a synchronization of a periodic Remote Copy group takes longer to complete than its synchronization period, an alert will be generated. This is the default behavior. • no_over_per_alert - If a synchronization of a periodic Remote Copy group takes longer to complete than its synchronization period then an alert will not be generated. Specifies the operation of the group(s). Valid operations are: • reverse - Reverses volume group roles.
• The period can be set only for groups whose mode is asynchronous periodic (see creatercopygroup). • Do NOT use the reverse value of the as part of the normal disaster recovery process.
setrcopytarget NAME setrcopytarget -- The setrcopytarget command sets the name, policies, or throughput definition for the target’s links.
NOTE: The no_mirror_config specifier should only be used to allow recovery from an unusual error condition and only used after consulting your HP representative. The new name for the indicated target. This specifier can only be used with the name subcommand. Specifies the maximum throughput for the indicated target's links, and is used to limit the total throughput of the links.
a group to be created, or a volume to be added to a group, only on one side of the pair if the operation is interrupted by a network failure. In such cases it might be necessary to temporarily change the policy to no_mirror_config in order to bring the configurations into alignment. After being corrected the mirror_config policy should be immediately restored. Such operations should generally only be undertaken on the advice of a HP representative.
setvv NAME setvv -- The setvv command changes the properties associated with a virtual volume. Use the setvv command to modify volume names, volume policies, allocation warning and limit levels, and the volume’s controlling common provisioning group (CPG). SYNTAX setvv [options ] ... AUTHORITY Super, Edit Any role granted the vv_set right can edit the properties of base volumes. Any role granted the vvcopy_set right can edit the properties of physical copies of volumes.
logical disks are removed from the CPG. This is permitted only when the existing snapshot logical disks are exclusively used by the volumes specified in this option. -snp_aw Indicates a snapshot space allocation warning. Through this option you can generate a warning alert when the snapshot space of the virtual volume exceeds the indicated percentage of the virtual volume size. -snp_al Indicates a snapshot space allocation limit.
-hpc Defines the virtual volume geometry heads per cylinder value that is reported to the hosts though the SCSI mode pages. The valid range is from 1 to 1024. The default value is 8. The following option can only be used on fully provisioned volumes: -usr_cpg Specifies that the volume user space that is to be provisioned from the specified CPG. This option moves all the logical disks currently contained in the user space for these volumes into the CPG.
showport NAME showport -- The showport command displays information about ports in the system. SYNTAX showport [options] [-failed] [-sortcol
[,]] AUTHORITY Any role in the system. OPTIONS -i Shows port hardware inventory information. -c Displays all devices connected to each loop (by position on the loop). Position 0 is the cage connected directly to the node on this loop. Position n is the (n + 1) cage on the loop.-sortcol
[,][:[,]...] Sorts command output based on column number (). Columns are numbered from left to right, beginning with 0. At least one column must be specified. In addition, the direction of sorting () can be specified as follows: • inc - Sort in increasing order (default). • dec - Sort in decreasing order. Multiple columns can be specified and separated by a colon (:).The columns in the previous example are identified as follows: • N:S:P. The physical position of the port, in the syntax node:slot:port. • State. State of the port. ◦ ready. The port is online and ready for use. ◦ loss_sync. The port is not physically connected to anything. ◦ config_wait. Firmware has yet to be initialized. ◦ login_wait. Fibre Channel adapter is attempting port and process logins with all loop ports. ◦ error. Fibre Channel adapter has experienced an unrecoverable error.
showrcopy NAME showrcopy -- The showrcopy command displays details of the Remote Copy configuration. The showrcopy command also displays the group’s domain names if the global -listdom option is used or if the TPDLISTDOM environment variable is set.
receive 0 receive 1 10.100.33.11 Up 10.101.33.11 Up Group Information Name Target Status sync_group_1 System2 Started LocalVV ID RemoteVV localvv.0 391 remotevv.0 localvv.1 392 remotevv.1 Role Mode Options Primary Sync ID SyncStatus LastSyncTime 351 Syncing (25%) Thu Dec 14 17:37:40 PST 2006 352 Syncing (40%) Thu Dec 14 17:37:40 PST 2006 Name Target Status Role Mode Options sync_group_2.r11 System2 Started Secondary Sync LocalVV ID RemoteVV ID SyncStatus LastSyncTime remotevv.0 401 localvv.
Name Target Status Role Mode Options lisa bf_mirror Started Primary Periodic Last-Sync Tue Jul 18 14:09:44 PDT 2006 , Period 30m, over_per_alert LocalVV ID RemoteVV ID SyncStatus LastSyncTime lisa-ws 2 lisa-ws 3922 Synced Tue Jul 18 14:10:32 PDT 2006 In the example above: • Name. The name of the group. • Target. The target to which the group is mirrored. • Status. The following values can appear in the group Status field: ◦ New. Group that has not yet been started. ◦ Starting.
might notice that 10 volumes do not start synchronizing until the first 20 have completed. This can be seen by monitoring the Sync% column of the showrcopy command output. • A Domain column may be included by using the setclienv command to set the listdom option to 1. The listdom option is also set to 1 if the CLI was started with the -listdom option or if the CLI was started with the TPDLISTDOM environment variable set.
showrctransport NAME showrctransport -- The showrctransport command shows status and information about end-to-end transport for Remote Copy in the system. SYNTAX showrctransport [options] AUTHORITY Any role in the system. OPTIONS -rcfc Show information about Fibre Channel end-to-end transport. -rcip Show information about Ethernet end-to-end transport. SPECIFIERS None. RESTRICTIONS None.
The following example displays status and information about the end-to-end transport for RCIP ports: # showrctransport -rcip N:S:P State HwAddr 0:1:1 new 000423C21B72 0:1:1 new 000423C21B73 1:2:1 new 000423ADE95E 1:2:1 new 000423ADE95F IPAddress PeerIPAddress 192.168.25.226 192.168.25.226 192.168.25.227 192.168.25.227 - Netmask Gateway MTU Rate Duplex 255.255.255.0 - 1500 1Gbps Full 255.255.255.0 - 1500 n/a Half 255.255.255.0 - 1500 1Gbps Full 255.255.255.
NOTES None.
startrcopy NAME startrcopy -- The startrcopy command enables Remote Copy. SYNTAX startrcopy AUTHORITY Super, Edit Any role granted the rcopy_start right. NOTE: You need access to all domains in order to run this command. OPTIONS None. SPECIFIERS None. RESTRICTIONS This command requires the HP 3PAR Remote Copy Software license. Contact your local service provider for further information.
startrcopygroup NAME startrcopygroup -- The startrcopygroup command turns on Remote Copy for the specified Remote Copy volume group. SYNTAX startrcopygroup [options ] |... AUTHORITY Super, Edit Any role granted the rcopygroup_start right. OPTIONS -wait Specifies that the command blocks until the initial synchronization is complete. The system generates an event when the synchronization is complete.
added to existing asynchronous periodic groups their first sync occurs the next time the entire group synchronizes. 274 • You must enter this command on the backup system before entering it on the primary if the mirror_config policy is not set. • When a secondary group says that it is in the started state, it does not necessarily mean that the group is receiving data from the primary system. The primary group might be stopped, or its system might even be down.
statport NAME statport -- The statport command displays read and write (I/O) statistics for ports. SYNTAX statport [options ]|-rcfc|-rcip AUTHORITY Any role in the system. OPTIONS –data|–ctl|–both Show data transfers only (–data), control transfers only (–ctl), or both data and control transfers (–both). If no option is included on the command line, the command shows data transfers only. –nodes Displays statistics for ports attached to the nodes from the node_list.
–sortcol
[,][:[,]...] Sorts command output based on column number . Columns are numbered from left to right, beginning with 0. You must specify a column number. In addition, you can specify the direction of sorting as follows: • inc - Sort in increasing order (default). • dec - Sort in decreasing order. Multiple columns can be specified separated by a colon (:), and rows that have the same earlier columns will be sorted by the values in the later columns.0:0:2 Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0 0:2:1 Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0 0:2:2 Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0 0:3:1 Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0 0:3:2 Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0 1:0:1 Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0 1:0:2 Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0 1:3:1 Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0 1:3:2 Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0 -----------------------------------------------------------------------total Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.
statrcopy NAME statrcopy -- The statrcopy command displays statistics for Remote Copy volume groups. SYNTAX statrcopy [options ] AUTHORITY Any role in the system. OPTIONS -d Specifies the interval, in seconds, in which statistics are sampled using an integer from 1 to 2147483. If no interval is specified, the option defaults to an interval of two seconds.
Press the enter key to stop... The columns in this example provide the following information: • Target. The system name of the actual link process that is running. • Node. The node that the link is running on. • Address. The IP address of the remote node. • IPC. The mode of the Remote Copy link (r) Receive or (s) Send. • Total KBytes. The amount of data that has been transmitted since the link was started, in KB. • Throughput(KBs). The throughput on the link after the last iteration.
statrcvv NAME statrcvv -- The statrcvv command displays statistics for Remote Copy volumes in a timed loop. SYNTAX statrcvv [options ] [|]... AUTHORITY Any role in the system. OPTIONS –d Specifies the interval in seconds that statistics are sampled from using an integer from 1 through 2147483. If no count is specified, the command defaults to 2 seconds.
–sortcol
[,][:[,]...] Sorts command output based on column number (). Columns are numbered from left to right, beginning with 0. You must specify a column number. In addition, you can specify the direction of sorting (): • inc - Sort in increasing order (the default). • dec - Sort in decreasing order. -filt Specifies that statistics that fall below the threshold specified by the argument are filtered out and not displayed.EXAMPLES The following example shows statistics for all synchronous Remote Copy volumes: cli% statrcvv -sync 09:48:45 03/30/10 I/O per sec KBytes per sec Svt ms Rmt Svt ms IOSz KB VVname RCGroup Target Mode Port Type Cur Avg Max Cur Avg Max Cur Avg Cur Avg Cur Avg testvv.0 multi.1 amp2 Sync 0:2:1 FC 32 45 50 4181 5839 6534 11.5 11.6 1.3 1.3 131.1 131.1 testvv.0 multi.1 amp2 Sync 1:2:1 FC 49 35 49 6456 4555 6456 9.3 10.4 1.3 1.5 131.1 131.1 testvv.1 multi.1 amp2 Sync 0:2:1 FC 37 38 39 4796 4952 5093 10.0 10.
• KBytes per second Max. The maximum number of KB per second. • Svt ms Cur. The current Remote Copy service time in milliseconds. • Svt ms Avg. The average Remote Copy service time in milliseconds. • Rmt Svt ms Cur. The current service time in milliseconds to complete I/O on the Remote Copy backup system. • Rmt Svt ms Avg. The average service time in milliseconds to complete I/O on the Remote Copy backup system. • IOSz KB Cur. The current I/O size in KB. • IOSz KB Avg.
stoprcopy NAME stoprcopy -- The stoprcopy command disables the Remote Copy functionality for any started Remote Copy volume groups. SYNTAX stoprcopy [options] AUTHORITY Super, Edit Any role granted the rcopy_stop right. NOTE: You need access to all domains in order to run this command. OPTIONS –f Specifies that any started copy will not ask for confirmation for the -clear option. -stopgroups Specifies that any started Remote Copy volume groups are stopped.
stoprcopygroup NAME stoprcopygroup -- The stoprcopygroup command stops the Remote Copy functionality for the specified Remote Copy volume group. SYNTAX stoprcopygroup [option ] |... AUTHORITY Super, Edit Any role granted the rcopygroup_stop right. OPTIONS -nosnap In synchronous mode, this option turns off the creation of snapshots. This is useful if removercopygroup is to be run to remove Remote Copy.
NOTES • If a group’s target has the mirror_config policy set and the group is a primary group, then this command will be mirrored to that target and the corresponding secondary group will be stopped. If the mirror_config policy is set and the group is a secondary, then this command will fail. • If the mirror_config policy is not set and this command is issued on a secondary group, then the corresponding primary group will also be stopped as a result of this command.
syncrcopy NAME syncrcopy -- The syncrcopy command manually synchronizes Remote Copy volume groups. SYNTAX syncrcopy [options ] |... AUTHORITY Super, Edit Any role granted the rcopy_sync right. OPTIONS -w Wait for synchronization to complete before returning to a command prompt. -n Do not save resynchronization snapshot. This option is only relevant for asynchronous periodic mode volume groups.
The following example specifies that all Remote Copy volume groups that start with the name testgroup should be synchronized with their corresponding secondary volume group: # syncrcopy -pat testgroup* NOTES • Mode (synchronous or asynchronous periodic) is set using the creatercopygroup command. • For information about setting targets, see the creatercopytarget command.
E Remote Copy and Other Features For more information on: See: Virtual domains “Remote Copy and Virtual Domains” (page 289) Using Remote Copy 3.1.1 on systems running 2.3.1 “Remote Copy Functionality Unavailable on 2.3.1 Systems” (page 289) Remote Copy and Virtual Domains Remote Copy checks for the presence of HP 3PAR Virtual Domains Software (domains) on the backup system to verify that you have mirrored the virtual volume to the same backup system domain name as the primary system domain name.
Index Symbols CPGs maximum volumes, 188 1-to-1 Remote Copy illustration, 43 setup, 43 D A admitrcopylink command, 215 alerts, 208 asynchronous periodic mode how Remote Copy operates, 195 resynchronization, 196 snapshot utilization, 205 synchronization types, 197 volume group synchronization, 198 volume groups, 210 audience for this guide, 1 automatic resynchronizations, 201 autonegotiation troubleshooting, 100 B backup storage system connect to primary storage system, 21 base volume, 199 bidirectional,
minimum synchronization period, 201 N N-to-1 Remote Copy restrictions, 25 natural direction of data flow, 182 new consistency groups, 197 notes and cautions, 11 NotSynced, 210 P performance considerations, 100 ports controller node, install and configure, 33, 116 primary storage system connect to backup storage system, 21 failure of, 209 primary volume, 192 promoting, 206 R RCFC setup, 215 read-only snapshot, 210 read/write snapshots rules for adding to volume groups, 191 receiving links, 184 redundancy,
volume groups configuring the synchronization period, 201 naming, 191 reasons to use, 190 rules for forming, 191, 203 W write errors, 209 latency, 195 292 Index
