3PAR Remote Copy® 2.3.1 User’s Guide 3PAR Inc. 4209 Technology Drive Fremont, CA 94538 U.S.A. Part No.
Revision Notice This is the first release of this manual. A complete revision history is provided at the end of this document. Changes The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, 3PAR Inc. assumes no liability resulting from errors or omissions in this document or from the use of the information contained herein.
InForm OS Version 2.3.1 Remote Copy User’s Guide Table of Contents 1 Introduction 1.1 Audience 1.2 1.2 Related Documentation 1.2 1.3 Organization 1.3 1.4 Typographical Conventions 1.4 1.5 Advisories 1.5 2 Remote Copy Overview 2.1 Overview 2.3 2.2 Remote Copy Terms and Concepts 2.3 2.2.1 Remote Copy Terms 2.3 2.2.2 Remote Copy Concepts 2.4 2.3 Remote Copy Volume Groups 2.6 2.4 Remote Copy Pairs 2.6 2.5 Remote Copy Configuration 2.7 2.5.1 Bidirectional Configurations 2.7 2.5.
Remote Copy User’s Guide InForm OS Version 2.3.1 2.6 Remote Copy Targets 2.15 2.6.1 2.15 Target Definitions 2.7 Remote Copy Links 2.17 2.7.1 Sending Links 2.17 2.7.2 Receiving Links 2.18 2.8 Remote Copy Connections 2.8.1 IP Networks 2.19 2.8.2 Fibre Channel Networks 2.20 2.8.3 Fibre Channel over IP Networks 2.20 2.9 Remote Copy Operation 2.9.1 2.9.2 2.22 2.9.1.1 Synchronous Mode 2.23 2.9.1.2 Asynchronous Periodic Mode 2.24 Synchronization Types 2.25 2.9.2.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.13.2 Double Link Failure 2.36 2.13.2.1 Synchronous Volume Groups 2.36 2.13.2.2 Asynchronous Periodic Groups 2.37 2.13.3 Remote Copy Failure Timeouts 2.37 2.13.4 Storage Server Failures 2.38 2.13.4.1 Failure of a Target 2.38 2.13.4.2 Failure of a Secondary Target 2.38 2.13.5 Write Errors 2.38 2.13.6 Read Errors 2.39 2.14 Requirements and Restrictions 2.41 2.14.1 N-to-1 Restrictions 2.43 2.14.2 1-to-N Restrictions 2.44 2.
Remote Copy User’s Guide InForm OS Version 2.3.1 3.5.2 3.5.1.3 Creating Remote Copy Volume Groups 3.21 3.5.1.4 Start Copying 3.23 3.5.1.5 Setting Up Additional Remote Copy Pairs 3.25 Setting Up Bidirectional Remote Copy 3.6 Synchronous Long Distance Remote Copy Setup 3.25 3.28 3.6.1 Setting Up the Primary Server 3.31 3.6.2 Setting Up the Backup Servers 3.32 3.6.3 Verifying Synchronous Long Distance Remote Copy Setup 3.34 3.6.
InForm OS Version 2.3.1 Remote Copy User’s Guide 5.1.3 Distance 5.2 5.1.4 MTU Size 5.2 5.1.5 Autonegotiation 5.3 5.1.6 Remote Copy Mode 5.3 5.1.6.1 Asynchronous Periodic 5.3 5.1.6.2 Synchronous Mode 5.4 5.2 Performance Notes for RCFC Configuration 5.5 5.2.1 RCFC Links 5.5 5.2.2 Initial Sync 5.5 5.2.3 Distance 5.5 5.2.4 Remote Copy Mode 5.5 5.3 Scripting Notes A 5.5 Quick Setup Guide A.1 Setting Up the Remote Copy Transport Layer for RCIP A.2 A.
Remote Copy User’s Guide InForm OS Version 2.3.1 removercopygroup B.31 removercopytarget B.33 setrcopygroup B.35 setrcopytarget B.43 setvv B.47 showport B.52 showrcopy B.57 showrctransport B.62 startrcopy B.66 startrcopygroup B.67 statport B.69 statrcopy B.74 stoprcopy B.77 stoprcopygroup B.79 syncrcopy B.81 C Example Setup and Disaster Recovery C.1 Remote Copy Setup Examples C.2 C.2 Bidirectional Synchronous Disaster Recovery Example C.4 C.
InForm OS Version 2.3.
Remote Copy User’s Guide x Table of Contents InForm OS Version 2.3.
InForm OS Version 2.3.1 Remote Copy User’s Guide 1 Introduction In this chapter 1.1 Audience 1.2 1.2 Related Documentation 1.2 1.3 Organization 1.3 1.4 Typographical Conventions 1.4 1.5 Advisories 1.5 This guide provides the information you need to configure and use 3PAR Remote Copy. It also discusses special usage scenarios and how to handle problems. 3PAR Remote Copy is a product that allows you to copy virtual volumes from one InServ storage server to another.
Remote Copy User’s Guide InForm OS Version 2.3.1 1.1 Audience This guide is for System and Storage Administrators who monitor and direct system configurations and resource allocation for 3PAR InServ® Storage Systems. 1.
InForm OS Version 2.3.1 Remote Copy User’s Guide 1.3 Organization This guide is organized as follows: ■ Chapter 1, Introduction, (this chapter), provides an overview of this guide, including information on audience, related documentation, and typographical conventions. ■ Chapter 2, Remote Copy Overview, gives an overview of 3PAR Remote Copy, that discusses important terminology and concepts from a theoretical perspective.
Remote Copy User’s Guide InForm OS Version 2.3.1 1.4 Typographical Conventions This guide employs the following typographical conventions: Typeface Meaning Example ABCDabcd Used for dialog elements such as When prompted, click Finish to titles, button labels, and other complete the installation. screen elements. ABCDabcd ABCDabcd Used for paths, file names, and Open the file screen output. \gui\windows\setup.exe Used to differentiate user input # cd /opt/3par/gui from screen output.
InForm OS Version 2.3.1 Remote Copy User’s Guide 1.5 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. NOTE: Notes are reminders, tips, or suggestions that supplement the procedures included in this guide. CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data.
Remote Copy User’s Guide 1.6 Advisories InForm OS Version 2.3.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2 Remote Copy Overview In this chapter 2.1 Overview 2.3 2.2 Remote Copy Terms and Concepts 2.3 2.3 Remote Copy Volume Groups 2.6 2.4 Remote Copy Pairs 2.6 2.5 Remote Copy Configuration 2.7 2.5.1 Bidirectional Configurations 2.7 2.5.2 Unidirectional Configurations 2.8 2.5.3 N-to-1 Configurations 2.9 2.5.4 1-to-N Configurations 2.11 2.5.5 Synchronous Long Distance Configuration 2.12 2.6 Remote Copy Targets 2.15 2.7 Remote Copy Links 2.
Remote Copy User’s Guide 2.9.2 Synchronization Types 2.25 2.9.3 Resynchronization Period 2.28 2.9.4 Manual Resynchronization 2.29 2.9.5 Concurrent Synchronization Limits 2.29 2.9.6 Throughput Limiting Option 2.30 2.9.7 Role Reversal 2.30 2.10 Remote Copy and 3PAR Virtual Domains 2.30 2.11 Use of Virtual Copy Snapshots 2.31 2.11.1 In Synchronous Mode 2.31 2.11.2 In Asynchronous Periodic Mode 2.32 2.12 Remote Copy and Thin Provisioning 2.33 2.12.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.1 Overview 3PAR Remote Copy is a product that allows you to copy virtual volumes from one InServ Storage Server to another. The copy can be used for disaster recovery, for backup, or for data migration. 3PAR Remote Copy requires that you use the InForm CLI. Refer to the InForm OS Command Line Interface Reference and the InForm OS CLI Administrator’s Manual for complete instructions on using the InForm CLI.
Remote Copy User’s Guide InForm OS Version 2.3.1 local or primary server and secondary volume groups reside on the remote or backup server. See Remote Copy Volume Groups on page 2.6 for additional information. NOTE: Cross-volume ordering of writes refers to the preservation of related writes. For example: a A volume group contains volumes V1 and V2. b The host application writes VV1 to V1 and then writes VV2 to V2. c When mirrored with Remote Copy, VV1 is written to first, then VV2.
InForm OS Version 2.3.1 Remote Copy User’s Guide Secondary Group X to Group X.r Volume Group X.r Primary Volume Group X Group Y to Group Y.r Primary Volume Group Y Secondary InServ2 Volume Group Y.r InServ1 Natural direction of data replication Figure 2-1. Relationship of Primary Versus Secondary Volume Groups on Primary and Backup Storage Servers In Figure 2-1, InServ1 and InServ2 act as both primary and backup servers.
Remote Copy User’s Guide InForm OS Version 2.3.1 2.3 Remote Copy Volume Groups Remote Copy operations are performed on groups of virtual volumes called Remote Copy volume groups. A Remote Copy volume group is a group of volumes on the same storage system that are logically related and for which there is a cross-volume ordering of writes. Volume groups are used when data needs to be consistent across a group of volumes in order for database or other applications to process data correctly.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.5 Remote Copy Configuration As stated previously, Remote Copy configurations are based on the relationship between a pair of InServ Storage Servers (Remote Copy pair). The storage servers in the Remote Copy pair play multiple roles at the same time. Both storage servers can function as both the primary and backup servers and can hold primary and secondary volume groups. This configuration is referred to as a bidirectional Remote Copy configuration.
Remote Copy User’s Guide InForm OS Version 2.3.1 2.5.2 Unidirectional Configurations In a unidirectional Remote Copy configuration, each storage server in the pair plays either the role of the primary server or the backup server. In this configuration, the primary storage server or servers holds all primary volume groups and the backup storage server holds all secondary volume groups. Primary to Secondary Group Secondary Volume Group X.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.5.3 N-to-1 Configurations In N-to-1 Remote Copy configurations, a maximum of four primary storage servers use the same secondary (backup) storage server. N-to-1 Remote Copy configurations can operate in either a combination of bidirectional (for one Remote Copy pair) and unidirectional functionality (as shown in Figure 2-4), or in complete unidirectional functionality.
Remote Copy User’s Guide InForm OS Version 2.3.1 Primary Volume Group W Group W to Group W.r Secondary Volume Group Y.r Primary Volume Group Z Group Y to Group Y.r Group Z to Group Z.r Primary Volume Group Y InServ1 Group X to Group X.r Secondary Volume Group W.r InServ3 Primary Volume Group X Secondary Volume Group X.r InServ2 InServ4 Direction of data replication Figure 2-4. N-to-1 Remote Copy 2.10 Remote Copy Configuration Secondary Volume Group Z.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.5.4 1-to-N Configurations In a 1-to-N Remote Copy configuration, a single primary storage server can use multiple InServ Storage Servers as backup servers. For the current release, a 1-to-N Remote Copy configuration has a maximum of two secondary (backup) targets.
Remote Copy User’s Guide InForm OS Version 2.3.1 2.5.5 Synchronous Long Distance Configuration In Synchronous Long Distance Remote Copy configurations, a single volume group is copied directly to volumes on two other servers by admitting the volumes to groups with two targets.
InForm OS Version 2.3.1 1 Prior to InServ2 Failure Remote Copy User’s Guide InServ1 (primary server) Primary Volume Group A Asynchronous Periodic Mode Synchronous Mode InServ3 (backup server) InServ2 (backup server) Secondary Volume Group A1 2 InServ2 Failure (standby link) Secondary Volume Group A2 InServ1 (primary server) Primary Volume Group A Asynchronous Periodic Mode InServ2 (backup server) InServ3 (backup server) Secondary Volume Group A1 Secondary Volume Group A2 Figure 2-6.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTE: Either backup server can be set up to assume the role of the primary server in the event of failover. See Chapter 3, Remote Copy Setup for information.
InForm OS Version 2.3.1 ■ Remote Copy User’s Guide Asynchronous periodic mode Remote Copy is restored between InServ1 and InServ3. Additionally, Synchronous Long Distance Remote Copy can also be used for data migration when replacing an InServ Storage Server in an existing Remote Copy configuration (see Appendix C, Example Setup and Disaster Recovery). 2.6 Remote Copy Targets While using Remote Copy, the relationship between primary and backup storage servers is not always static.
Remote Copy User’s Guide InForm OS Version 2.3.1 Group X Target: InServ2 Group X.r Secondary Target: InServ1 Volume Group X.r Primary Volume Group X Group Y.r Target: InServ2 Secondary Volume Group Y.r Group Y Target: InServ1 Primary Volume Group Y InServ2 InServ1 Direction of data replication Figure 2-8. Target Definitions (Single Pair, Bidirectional) In the previous figure, ■ the Remote Copy target system is InServ2 for the Volume Group X on InServ1.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.7 Remote Copy Links Remote copy links are divided into two main types, sending links and receiving links. Sending links are created manually during the Remote Copy setup by using the creatercopytarget or admitrcopylink commands. Receiving links are automatically created on all nodes that have sending links configured. 2.7.
Remote Copy User’s Guide InForm OS Version 2.3.1 InServ1 Links to Target: InServ2 172.16.1.11 172.16.2.11 Node 6 Node 7 172.16.2.12 172.16.1.12 Network Links to Target: InServ1 172.16.1.11 172.16.2.11 Node 2 Node 3 172.16.1.12 172.16.2.12 InServ2 Figure 2-10. Sending Links for a Remote Copy Pair 2.7.2 Receiving Links While sending links are used to transmit data, receiving links are used to listen.
InForm OS Version 2.3.1 Remote Copy User’s Guide NOTE: Remote Copy over IP (RCIP) configurations can fully utilize both 1Gbps links during the synchronization process. If lower throughput networks are used, throughput between systems running Remote Copy might be capped by the network. Connections between servers in the same room could be provided as direct Gigabit Ethernet (GigE) links or through GigE switches, or through Fibre Channel networks. Longer distances require other topologies.
Remote Copy User’s Guide InForm OS Version 2.3.1 storage servers in the proposed configuration are separated by a large distance and have been placed on different IP subnets. If the storage servers are on different subnets, each storage server must be connected to a gateway router or switch on that subnet and there must be an IP cloud between their gateways. 2.8.
InForm OS Version 2.3.1 Remote Copy User’s Guide NOTE: Although the benefits of using volume groups are considerable, one drawback is that the I/O to all volumes in the group is blocked while taking snapshots. If the number of volumes in the group is very large (the current supported limit is 100 volumes per group), the blocking of the I/O might result in some host writes timing out. For bidirectional configurations, both storage servers can hold primary and secondary volume groups.
Remote Copy User’s Guide InForm OS Version 2.3.1 For unidirectional Remote Copy, each virtual volume in a Remote Copy group on the primary server is mapped to a virtual volume in a corresponding secondary group on the backup storage server (Figure 2-12). InServ1 Target: InServ2 A B C InServ2 Target: InServ1 A B C Volume Group (Primary) Volume Group (Secondary) InServ1 (Primary) InServ2 (Backup) Direction of data replication Figure 2-12.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.9.1.1 Synchronous Mode In synchronous mode, a host-initiated write is performed on both the primary and the backup storage servers before acknowledging the host write. On the primary storage server, data is written to the caches of two nodes. This redundancy is in place in case one node fails before the write can be copied to a disk. Concurrently, the write request is sent to the backup storage server through a communication link.
Remote Copy User’s Guide InForm OS Version 2.3.1 2.9.1.1.1 Latency Synchronous mode adds more latency to the write because the I/O needs to be sent to the backup server over the IP network or SAN and then an acknowledgement must be received from the backup server before acknowledging the host. As the distance between the primary and backup storage servers increases, the latency also increases. For example, a one-way distance of 100 miles adds approximately two milliseconds to the write latency.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.9.2 Synchronization Types There are two types of synchronizations that are performed on volume groups: full synchronizations and resynchronizations. A full synchronization copies the primary volume in its entirety, whereas a resynchronization copies only what has changed after the previously completed synchronization.
Remote Copy User’s Guide InForm OS Version 2.3.1 Backup Storage Server Primary Storage Server Secondary Volume Group Primary Volume Group 3 Snapshots created for all Volumes in the Primary Group Snapshots 1 Snapshots Created For All Volumes in Secondary Group Snapshots New writes blocked on Primary 2 I/O allowed to resume on Primary Group 4 Figure 2-15.
InForm OS Version 2.3.1 Remote Copy User’s Guide If the primary volume has been previously synchronized, and a resynchronization snapshot exists, then a fast resynchronization is performed. The two snapshots (the resynchronization snapshot and the current synchronization snapshot) are compared to determine what changes have occurred between the creation of each snapshot. The system transmits only these changes to the secondary volume (Figure 2-17).
Remote Copy User’s Guide InForm OS Version 2.3.1 2.9.2.2 Synchronous Mode Volume Groups Rather than creating snapshots on the primary volume group for synchronous mode volume groups, the I/O is taken directly from the base volume when synchronization begins. Synchronous mode volume groups resynchronize automatically when they are stopped and restarted. When stopped, the system takes snapshots that are used for resynchronization. 2.9.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.9.4 Manual Resynchronization Additional manual resynchronizations might be initiated for asynchronous periodic or synchronous mode volume groups using the syncrcopy command. When using this command, only the changes to the primary volume group after the last resynchronization point are sent over the network to the backup storage server. Use the syncrcopy -ovrd command to force a synchronous mode volume group to synchronize.
Remote Copy User’s Guide InForm OS Version 2.3.1 2.9.6 Throughput Limiting Option For asynchronous periodic mode Remote Copy (see Asynchronous Periodic Mode on page 2.24), it might be useful to use the throughput limiting option when setting up links over leased lines. This option limits the maximum throughput that Remote Copy will utilize for a link. This is useful, for example, if the leased line charges are based on the bit rate utilized.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.11 Use of Virtual Copy Snapshots Remote Copy uses virtual copy snapshots (point-in-time virtual copies) of a virtual volume to minimize the amount of data that needs to be sent over the network to resynchronize volumes that were previously synchronized. There are several scenarios where snapshots are used. 2.11.1 In Synchronous Mode In synchronous mode, a snapshot is created only under error or recovery situations or when a group is manually stopped.
Remote Copy User’s Guide InForm OS Version 2.3.1 If the primary server fails during a resynchronization and the backup server needs to be used to access data, it is necessary to issue failover commands (such as those promoting the snapshots to the base volumes using the promotesv command) before reversing the targets. If, during disaster recovery or as part of a planned role-reversal, the backup storage server is converted to a primary storage server, a snapshot is also taken on that server.
InForm OS Version 2.3.1 Remote Copy User’s Guide recent snapshot is promoted. To see an example disaster recovery scenario that illustrates this process, see Appendix C, Example Setup and Disaster Recovery. 2.12 Remote Copy and Thin Provisioning Remote Copy makes extensive use of point-in-time snapshots. The main use of these snapshots is to keep track of the updates to the primary volume when the data is not being sent to the secondary volume over the communication links.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTE: While it is possible for a CPG to have up to 4095 volumes, it is strongly recommended that no more than 32 volumes be associated with a single CPG. The reasons for this limit are as follows: ■ Virtual volumes in the same CPG can share the same logical disk. In the unlikely event that the logical disk is damaged (because of multiple simultaneous disk failures, for example), all the volumes associated with that logical disk will be unavailable.
InForm OS Version 2.3.1 Remote Copy User’s Guide NOTE: When a TPVV is configured as a primary Remote Copy volume, the initial synchronization of the primary volume sends only the allocated data pages to the backup storage server.
Remote Copy User’s Guide InForm OS Version 2.3.1 When a link between storage servers is broken, an alert is issued on each storage system as soon as the link failure is detected. If the other link remains active, all data is sent on that remaining link, though a reduction in throughput (bandwidth) might occur. No other noticeable errors should occur. 2.13.2 Double Link Failure When both links between InServ Storage Servers in a Remote Copy pair are broken, the two storage systems cannot communicate.
InForm OS Version 2.3.1 Remote Copy User’s Guide In addition to taking snapshots, the offset and length of the I/O will fail to complete on the secondary volumes because the link failures were recorded in the nonvolatile memory. The failed I/O must be recorded separately because the snapshot is taken after that I/O has been written for the primary volumes but before it was acknowledged and completed on the secondary.
Remote Copy User’s Guide InForm OS Version 2.3.1 When synchronous replication is used, low timeout values are used in an attempt to ensure that replication is stopped before the host I/O begins to time out in case of a network failure. If the network used by Remote Copy has transient problems, the lower timeout values can result in repeated link failure alerts and the stopping of all Remote Copy volume groups.
InForm OS Version 2.3.1 ■ Remote Copy User’s Guide If the no_fail_wrt_on_err policy is enabled for a synchronous volume group (this is the default), the host I/O completes without error. Replication is stopped for the volume group and a snapshot is taken of each volume in the volume group. In addition, the offset and length of the I/O that failed is recorded in nonvolatile memory.
Remote Copy User’s Guide InForm OS Version 2.3.1 As long as you have set the synchronization period using the setrcopygroup command, an asynchronous periodic volume group is automatically resynchronized at the scheduled synchronization interval. When you set the resynchronization period for the primary group, it is automatically mirrored to the secondary. NOTE: There is no default synchronization period.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.14 Requirements and Restrictions Remote Copy requires the use of a minimum of two InServ Storage Servers. ■ For Remote Copy over IP (RCIP), each storage server in the Remote Copy configuration must have two nodes with 3PAR-supported GigE PCI adapters (a maximum of one adapter per node and two adapters per system). Two adapters are required for each storage server in order to support redundant TCP/IPlinks between systems.
Remote Copy User’s Guide InForm OS Version 2.3.1 Systems used by Remote Copy must adhere to the following restrictions: ■ All storage servers in the configuration must be configured at the same InForm OS level. ■ Each storage server is limited to two Remote Copy interfaces. This limitation does not apply to 1-to-N Remote Copy. For 1-to-N Remote Copy, the primary storage server can have four RCIP interfaces; two to one secondary system and two to the other secondary system.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.14.1 N-to-1 Restrictions In addition to those requirements and restrictions described in Requirements and Restrictions on page 2.41, the following also apply to N-to-1 Remote Copy configurations: ■ In an N-to-1 configuration, one remote storage server participates in a maximum of four pairs, one for each primary storage server (Figure 2-19). One of these pairs might also be bidirectional.
Remote Copy User’s Guide InForm OS Version 2.3.1 2.14.2 1-to-N Restrictions In addition to those requirements and restrictions described in Requirements and Restrictions on page 2.41, the following also apply 1-to-N Remote Copy configurations: ■ In a 1-to-N configuration, one primary storage server participates in a maximum of two pairs, one for each backup storage server (Figure 2-20). One of these pairs might also be bidirectional.
InForm OS Version 2.3.1 Remote Copy User’s Guide 2.14.3 Synchronous Long Distance Restrictions For Synchronous Long Distance Remote Copy configurations, a maximum of two storage servers can be used as backup servers for one primary storage server. Additionally, the following restrictions apply to Synchronous Long Distance Remote Copy configurations: ■ All storage servers must have at least four controller nodes each. ■ Only unidirectional functionality allowed between Remote Copy pairs.
Remote Copy User’s Guide 2.46 Requirements and Restrictions InForm OS Version 2.3.
InForm OS Version 2.3.1 Remote Copy User’s Guide 3 Remote Copy Setup In this chapter 3.1 Available Setup Methods 3.2 3.2 Preparing for Setup 3.2 3.3 Gathering Necessary Information 3.3 3.4 Setting the Remote Copy Transport Layer 3.8 3.4.1 Setting Up Remote Copy Over IP 3.8 3.4.2 Setting Up the Remote Copy Interface for RCIP 3.9 3.4.2.1 Setting the Gateway 3.9 3.4.2.2 Verifying Connectivity 3.10 3.4.2.3 Increasing MTU (Optional) 3.11 3.4.3 Setting Up Remote Copy Over Fibre Channel 3.
Remote Copy User’s Guide InForm OS Version 2.3.1 3.7 Initial Synchronization Using Tape Backup 3.38 3.1 Available Setup Methods This chapter explains how to set up and configure 3PAR Remote Copy. Use these instructions if you are setting up Remote Copy for the first time.
InForm OS Version 2.3.1 ■ Remote Copy User’s Guide When configuring the Gigabit Ethernet (GigE) interface, the GigE interface and the management Ethernet port of an InServ Storage Server controller node should be on different IP subnets. If they are configured on the same subnet, Remote Copy packets might go over the management port and will not be available to the Remote Copy software.
Remote Copy User’s Guide InForm OS Version 2.3.1 After the Remote Copy configuration is complete, you can use the InForm CLI showport -rcip command or the showport -rcfc command to confirm the addresses you specified during the setup. Use the following figures to help visualize and organize your desired Remote Copy configuration: Basic Remote Copy Pair Information: System 2 System 1 Active Gateway TCP/IP Network Backup Gateway Figure 3-1.
InForm OS Version 2.3.1 Remote Copy User’s Guide 1. Remote Copy Pair Transport Layer: Speed of Gigabit Interface: System 1: IP Address Gateway IP Netmask N:S:P MTU Left HBA: Right HBA: System 2: Speed of Gigabit Interface: IP Address Gateway IP Netmask N:S:P MTU Left HBA: Right HBA: 2. Remote Copy Pair Link Configuration: Use the information gathered from the previous boxes to populate the following boxes. Node* System 1: Target Name: Target Interface IP (e.g. System 2 Left HBA IP) (e.g.
Remote Copy User’s Guide InForm OS Version 2.3.1 1. Remote Copy Transport Information for Additional Systems: Speed of Gigabit Interface: System 3: IP Address Gateway IP Netmask N:S:P MTU Left HBA: Right HBA: Speed of Gigabit Interface: System 4: IP Address Gateway IP Netmask N:S:P MTU Left HBA: Right HBA: Speed of Gigabit Interface: System 5: IP Address Gateway IP Netmask N:S:P MTU Left HBA: Right HBA: 2.
InForm OS Version 2.3.1 Remote Copy User’s Guide Basic Remote Copy Pair Information: System 2 System 1 Fibre Channel SAN Network 1. Remote Copy Pair Transport Layer: System 1: WWN System 2: N:S:P N:S:P WWN Left HBA Left HBA Right HBA Right HBA 2. Remote Copy Pair Link Configuration: Use the information gathered from the previous boxes to populate the following boxes. N:S:P Target Interface WWN System 1: N:S:P e.g. System 2 Left HBA WNN Target Name: e.g. System 2 Right HBA WWN e.g.
Remote Copy User’s Guide InForm OS Version 2.3.1 3.4 Setting the Remote Copy Transport Layer Prior to setting up Remote Copy, you must set up the Remote Copy transport layer as described in this section. The method for setting the RC transport layer differs depending on whether the configuration uses Remote Copy over IP (RCIP) or Remote Copy over Fibre Channel (RCFC). However, note that this is the only part of the Remote Copy setup that differs between RCIP or RCFC. 3.4.
InForm OS Version 2.3.1 Remote Copy User’s Guide 3.4.2 Setting Up the Remote Copy Interface for RCIP For RCIP, you must set up the Remote Copy GigE interfaces for each storage server in the Remote Copy configuration.
Remote Copy User’s Guide 1 InForm OS Version 2.3.1 Use the following command to set the system gateways for the Ethernet ports on storage server: # controlport rcip gw Are you sure you want to change the gateway for ? select q=quit y=yes n=no: y Remote Copy interface change successful. In order to issue this command on a storage server, you will need the gateway IP address to assign to the local Ethernet port () and the location of a local Ethernet port ().
InForm OS Version 2.3.1 Remote Copy User’s Guide This command performs a ping from the specified interface () to the specified IP address on the target system (). Issue this command twice (once for each interface), for each system in the configuration. NOTE: Because of the spanning tree and MAC address learning, you might need to ping each server several times before all tables are updated and the ping succeeds.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTE: Depending on workload, you might see as much as a 50 percent increase in throughput by using a 9000 byte MTU setting as opposed to a 1500 byte MTU setting. If the MTU value of 9000 is supported by the network, increase the MTU as follows: 1 For the GigE ports on each storage server, increase the MTU size to 9000 as follows: : # controlport rcip mtu 9000 Remote Copy change successful.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide If the pings fail, issue another set of pings without specifying a size. If this second attempt succeeds, the new setting is not supported and you should revert to 1500 MTU before continuing on to Setting Up Remote Copy on page 3.16. 3.4.
Remote Copy User’s Guide InForm OS Version 2.3.1 Node 0 Node 1 Node 0 Node 1 Backup InServ1 Node 2 Node 3 Primary InServ Node 0 Node 1 Backup InServ2 Figure 3-5. Remote Copy over Fibre Channel Dedicated Node Pairs 3.4.3.1 Setting Up the Remote Copy Interface for RCFC For Remote Copy over Fibre Channel (RCFC), you must set up the Remote Copy interface for each storage server in the Remote Copy configuration.
InForm OS Version 2.3.1 3 Remote Copy User’s Guide Verify the Fibre Channel transports are present on the Fibre Channel adaptor ports on each system and the State column displays ready by issuing the showrctransport -rcfc command.
Remote Copy User’s Guide InForm OS Version 2.3.1 3.5 Setting Up Remote Copy The following sections describe the steps involved in configuring the Remote Copy connections between storage servers in a Remote Copy configuration and then starting the Remote Copy function. This setup process differs according to the type of Remote Copy configuration to be used. However, the instructions for setting up a basic unidirectional Remote Copy pair, located in Setting Up Unidirectional Remote Copy on page 3.
InForm OS Version 2.3.1 ■ Remote Copy User’s Guide Follow the instructions in Setting Up Unidirectional Remote Copy on page 3.17, or the instructions in Setting Up Bidirectional Remote Copy on page 3.25 to set up the first pair in the configuration. ■ Repeat the instructions in Setting Up Unidirectional Remote Copy on page 3.17 for the second pair. ■ You can have a maximum of two pairs. Note that all pairs must share the same primary storage server.
Remote Copy User’s Guide ■ InForm OS Version 2.3.1 A virtual volume on InServ2 is called vv1_remote and is the only member of Group1.r112, the secondary group that is automatically created at the same time as Group1. Note that vv1 and vv1_remote must be the same size. InServ1 (Primary) Target: InServ2 Backup Links: 172.16.1.11 172.16.2.11 Node 6 Node 7 Group1 vv1 172.16.2.12 172.16.1.12 Network Active Links: 172.16.1.11 InServ2 (Backup) Target: InServ1 172.16.2.11 Node 2 Node 3 172.16.1.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide is the link IP address for the target system (for example,172.16.1.12 and 172.16.2.12). NOTE: The command for RCFC target creation is: #creatercopytarget FC NOTE: You can only configure one link per target definition per node. All examples in this guide use the first pattern illustrated in Figure 2-9 on page 2.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 is the link IP address for the target system (for example, 172.16.1.11 and 172.16.2.11). 3 Check that the links have come up between the primary and backup storage servers by using the showrcopy command on each storage server: NOTE: For complete details on the showrcopy command, including valid synchronization, link, and group states, see showrcopy on page B.57.
InForm OS Version 2.3.1 Remote Copy User’s Guide returns a Status of Up, the links have come up. Be sure to check that links are up on both systems (the previous example shows output for InServ2 only). NOTE: If there are any problems with the way that the links were created, use the dismissrcopylink : command to remove links and then try again. After all links come up between the Remote Copy pair, you can proceed with creating volume groups on the systems. 3.5.1.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTE: For N-to-1 configurations, only asynchronous periodic mode volume groups are supported. The creatercopygroup command creates a volume group on the primary storage server (InServ1). At the same time, it also creates a corresponding secondary group (Group1.r112) on the target system (InServ2). The corresponding secondary group uses the naming convention .r.
InForm OS Version 2.3.1 3 Remote Copy User’s Guide On the primary storage server, add pre-existing virtual volumes to the newly created volume group, Group1, as follows: On InServ1: # admitrcopyvv is the name of the virtual volume (vv1) to be added to the primary volume group (Group1) specified by the variable.
Remote Copy User’s Guide 2 InForm OS Version 2.3.1 Issue the showrcopy command again to verify that the groups are synchronizing. The groups are completely synchronized after the SyncStatus is Synced. On InServ1: # showrcopy ... Group Information Name Target Status sync_group_1 InServ2 Started LocalVV ID RemoteVV localvv.0 391 remotevv.0 localvv.1 392 remotevv.1 3.
InForm OS Version 2.3.1 Remote Copy User’s Guide 3.5.1.5 Setting Up Additional Remote Copy Pairs For configurations that use multiple Remote Copy pairs (also known as N-to-1 or 1-to-N type configurations), after following the instructions in Setting Up Unidirectional Remote Copy on page 3.17, repeat the entire process for each additional pair, up to a maximum of two (for 1-to-N configurations) or four (for N-to-1 configurations) Remote Copy pairs.
Remote Copy User’s Guide InForm OS Version 2.3.1 Secondary Group: Primary Group: Group1 vv1 Target: InServ2 InServ1 Group2.r125 vv2_remote 172.16.1.11 172.16.2.11 Node 6 Node 7 172.16.1.12 172.16.2.12 Network 172.16.2.11 172.16.1.11 Node 2 Node 3 172.16.1.12 172.16.2.12 InServ2 Secondary Group: Primary Group: Group1.r112 vv1_remote Group2 vv2 Target: InServ1 Figure 3-7.
InForm OS Version 2.3.1 Remote Copy User’s Guide In order to use this command, you must specify a (for example, Group2), the (for example, InServ1) and a mode (sync for synchronous or periodic for asynchronous periodic). The creatercopygroup command creates a primary volume group on the primary storage server, the storage server on which the command is issued (in this case, InServ2). At the same time, it also creates a corresponding secondary group (Group2.
Remote Copy User’s Guide InForm OS Version 2.3.1 The admitrcopyvv command adds the specified volume (vv2) to the primary volume group (Group2). At the same time, it also adds the secondary volume (vv2.remote) to the corresponding secondary volume group on the target system (Group2.r125). 4 Start replication for the volume groups created in step 1: On InServ2: # startrcopygroup where is the name of the primary volume group (Group2).
InForm OS Version 2.3.1 ■ ■ ■ Remote Copy User’s Guide InServB is the backup storage system ◆ Target name: InServA ◆ Links: ◆ Node 2 IP address 10.100.33.96 ◆ Node 3 IP address 10.101.33.96 ◆ Target name: InServC ◆ Links: ◆ Node 0 IP address 10.100.33.63 ◆ Node 1 IP address 10.101.33.63 InServC is the backup storage system ◆ Target name: InServA ◆ Links: ◆ Node 2 IP address 10.100.33.96 ◆ Node 3 IP address 10.101.33.96 ◆ Target name: InServB ◆ Links: ◆ Node 2 IP address 10.100.
Remote Copy User’s Guide ■ InForm OS Version 2.3.1 ◆ Node 0 WWN: 20210002AC0000C3 ◆ Node 1 WWN: 21210002AC0000C3 Asynchronous Periodic Remote Copy is used between InServA and InServC. * Synchronous Remote Copy between InServA and InServB InServA Primary Group: testgroup testvv.A.0 testvv.A.1 testvv.A.2 * Asynchronous periodic Remote Copy between InServA and InServC 10.100.33.96 Node 0 Node 2 10.101.33.96 Targets: InServB InServC Node 3 Node 1 Secondary Group: testgroup.
InForm OS Version 2.3.1 Remote Copy User’s Guide 3.6.1 Setting Up the Primary Server To set up the primary storage server (InServA): 1 Start Remote Copy as follows: On InServA: # startrcopy NOTE: In the following step, the creatercopytarget command must be issued twice, once for InServB and once for InServC.
Remote Copy User’s Guide InForm OS Version 2.3.1 3.6.2 Setting Up the Backup Servers The commands used to set up the backup storage servers (InServB and InServC) are nearly the same as those used to set up the primary server (InServA), except that they create the links in the opposite direction and create a second target for failover purposes.
InForm OS Version 2.3.1 3 Remote Copy User’s Guide Define a second target for InServB: On InServB: # creatercopytarget IP : : ◆ is the name of the Remote Copy target (for example, InServC). ◆ IP states that this is an IP link. ◆ specifies the node that contains the IP connections to the target (for example 2:4:1and 3:4:1). ◆ is the link IP address for the target system (for example, 10.100.33.96 and 10.
Remote Copy User’s Guide InForm OS Version 2.3.1 ◆ IP states that this is an IP link. ◆ specifies the node that contains the IP connections to the target (for example 0:1:1 and 1:3:2). ◆ is the link IP address for the target system (for example, 10.100.33.195 and 10.101.33.195). 3.6.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 4 FC ready 2FF70002AC000060 mirror_config InServC 5 IP ready mirror_config Link Information Target InServA InServA InServC InServC receive receive receive receive ◆ 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 3.6.4 Creating Synchronous Long Distance Remote Copy Volume Groups NOTE: In the following procedure, it is assumed that the volumes testvv.A.x have already been created on InServA, volumes testvv.B.x have already been created on InServB, and volumes testvv.C.x have already been created on InServC. NOTE: In the following procedure, two target are used, InServB and InServC, which define the configuration as Synchronous Long Distance Remote Copy.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServA: # showrcopy groups Group Information Name Target Status testgroup InServB 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 Role Mode Primary Sync ID SyncStatus 200 Synced 201 Synced 202 Synced Name Target Status Role testgroup InServC Started 17:52:17 PDT , over_per_alert LocalVV ID RemoteVV testvv.A.0 100 testvv.C.0 testvv.A.1 101 testvv.C.1 testvv.A.2 102 testvv.C.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServC: # showrcopy groups Group Information Name Target Status testgroup.r96 InServA Started LocalVV ID RemoteVV testvv.C.0 300 testvv.A.0 testvv.C.1 301 testvv.A.1 testvv.C.2 302 testvv.A.2 Role Mode Options Secondary Periodic over_per_alert ID SyncStatus LastSyncTime 100 Synced 2008-09-11 17:52:58 PDT 101 Synced 2008-09-11 17:53:01 PDT 102 Synced 2008-09-11 17:53:00 PDT Name Target Status testgroup.r96 InServB Backup LocalVV ID RemoteVV testvv.
InForm OS Version 2.3.1 Remote Copy User’s Guide To bring the primary and secondary volume groups into synchronization and start Remote Copy operations: 1 Start Remote Copy on InServ1: On InServ1: # startrcopy 2 Define a target for InServ1: On InServ1: # creatercopytarget IP :IP_address... ◆ is the target name (for example, InServ2) ◆ IP states that this is an IP link. ◆ specifies the node that contains the IP connections to the target.
Remote Copy User’s Guide ◆ 4 InForm OS Version 2.3.1 g is the size of the created volume in gigabytes (for example 5g). Start Remote Copy on InServ2: On InServ2: # startrcopy 5 Define a target for InServ2: On InServ2: # creatercopytarget IP :IP_address... ◆ is the target name (for example, InServ1). ◆ IP states that this is an IP link. ◆ specifies the node that contains the IP connections to the target.
InForm OS Version 2.3.1 7 Remote Copy User’s Guide Create a synchronous Remote Copy group on InServ1: On InServ1: # creatercopygroup : ◆ is the name of the created Remote Copy group (for example sync_group_1). 8 ◆ is the Remote Copy target (for example InServ2). ◆ is either synchronous (sync) or periodic (for example sync).
Remote Copy User’s Guide InForm OS Version 2.3.1 10 Stop Remote Copy for the Remote Copy volume group on InServ1: On InServ1: # stoprcopygroup where is the Remote Copy volume group (for example sync_group_1). This command creates a snapshot on the system that is the primary server for this volume group. The snapshot is named rcpy....
InForm OS Version 2.3.1 Remote Copy User’s Guide 13 Start the group on InServ1 to synchronize any changes that were made after the snapshots were created: On InServ1: # startrcopygroup where is the started Remote Copy volume group (for example sync_group_1). Initial Synchronization Using Tape Backup 3.
Remote Copy User’s Guide 3.44 Initial Synchronization Using Tape Backup InForm OS Version 2.3.
InForm OS Version 2.3.1 Remote Copy User’s Guide 4 Using Remote Copy In this chapter 4.1 Management 4.2 4.2 Reversing Target Designations 4.2 4.3 Changing Remote Copy Mode for a Volume Group 4.3 4.4 Setting Remote Copy Volume Group Policies 4.4 4.5 Manual Resynchronization 4.5 4.6 Viewing Synchronization Details 4.5 4.7 Converting Standard Virtual Volumes 4.8 4.8 Modifying Virtual Volumes 4.9 4.9 Limiting Throughput 4.10 4.10 Stopping Remote Copy 4.11 4.11 Remote Copy Commands 4.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTE: When issuing commands that are mirrored from one system to another, there is a five minute timeout limit. After five minutes, if the other system does not respond to a command, the following error message appears: target system could not be contacted 4.1 Management Use the showrcopy command to display information about the system’s configuration and the statrcopy command to display link throughput statistics.
InForm OS Version 2.3.1 Remote Copy User’s Guide 4.3 Changing Remote Copy Mode for a Volume Group Use the setrcopygroup mode command to change the Remote Copy mode of a volume group. This allows you to convert a synchronous volume group to an asynchronous periodic volume group or vice versa. NOTE: Only one mode (synchronous or asynchronous periodic) per target is allowed. Follow these steps to change the Remote Copy mode for an existing volume group.
Remote Copy User’s Guide InForm OS Version 2.3.1 CAUTION: There is no default synchronization period. Therefore, if you do not specify a synchronization period using the setrcopygroup command, automatic resynchronizations will not take place. 4.4 Setting Remote Copy Volume Group Policies In addition to switching the target for a volume group, the setrcopygroup command can also be used to set Remote Copy policies for volume groups. There are four policies that can be applied to volume groups.
InForm OS Version 2.3.1 ■ Remote Copy User’s Guide auto_recover The auto_recover group policy allows a group that was stopped as a result of a double link failure to automatically restart after a connection to its target system is established. In other cases where the group was stopped by the system (for example as a result of I/O errors occurring), groups will still need to be manually restarted.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTE: With asynchronous periodic mode volume groups, the startrcopygroup command starts synchronizations only the first time it is issued because subsequent instances of the command do not initiate resynchronizations. With synchronous mode volume groups, the startrcopygroup command prompts resynchronization each time it is used.
InForm OS Version 2.3.1 ■ ■ Remote Copy User’s Guide Status - The task state. Task states are as follows: ◆ done - The task has completed successfully. ◆ active - The task is still in process. ◆ failed - The task failed to complete because of a reason other than user cancellation. Phase - For Active tasks, indicates the number of completed phases and the total number of phases <#completed_phase>/<#total_phases>. Note that each step is composed of an arbitrary number of phases.
Remote Copy User’s Guide InForm OS Version 2.3.1 Table 4-1 summarizes the InForm CLI task management commands relevant to Remote Copy volume synchronizations. I‘ Table 4-1. Task Management Commands Command Description Domain: Privilege Level removetask Removes information about one or all: Super, Edit, Service more tasks and their details. showtask Displays information about tasks on all: Super, Edit, Browse the system.
InForm OS Version 2.3.1 Remote Copy User’s Guide 4.8 Modifying Virtual Volumes In addition to converting virtual volumes, you can also increase the size and rename virtual volumes in Remote Copy groups. 4.8.1 Growing a Virtual Volume To increase the size of a virtual volume, use the following commands: 1 Stop the Remote Copy group, as specified with , containing the volume to be grown. # stoprcopygroup 2 Issue the growvv command to grow the volume.
Remote Copy User’s Guide InForm OS Version 2.3.1 4.9 Limiting Throughput For asynchronous periodic mode Remote Copy (see Asynchronous Periodic Mode on page 2.24), it might be useful to use the throughput limiting option when setting up links over leased lines. This option limits the maximum throughput that Remote Copy utilizes for a link. This is useful, for example, if the leased line charges are based on the bit-rate utilized.
InForm OS Version 2.3.1 Remote Copy User’s Guide 4.10 Stopping Remote Copy ` If you want to stop using Remote Copy, issue the stoprcopy command as follows: # stoprcopy -stopgroups ` To stop using Remote Copy functionality on all volume groups, delete all Remote Copy configuration data, and release all resources used by Remote Copy, add the -clear option to the stoprcopy command as follows: # stoprcopy -stopgroups -clear NOTE: See Remote Copy and Thin Provisioning on page 2.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTE: As long as you are using 3PAR Remote Copy with the default group policy enabled (see Setting Remote Copy Volume Group Policies on page 4.4), the configuration commands, in the following table, followed by an asterisk (*) need only be issued on the primary storage system, as they are automatically mirrored to the secondary system. Table 4-2. Remote Copy Tasks and Associated Commands Task Command Creates a link to a target system.
InForm OS Version 2.3.1 Remote Copy User’s Guide Table 4-2. Remote Copy Tasks and Associated Commands (continued) Task Command Removes target designation from a Remote removercopytarget Copy system and removes all links affiliated with that target definition. Sets a Remote Copy volume group’s policies, setrcopygroup * data transfer direction, resynchronization period, and mode. Sets a Remote Copy target’s name and policies, setrcopytarget and the target link’s throughput definition.
Remote Copy User’s Guide InForm OS Version 2.3.1 Table 4-2. Remote Copy Tasks and Associated Commands (continued) Task Command Stops Remote Copy functionality for a specified stoprcopygroup * Remote Copy volume group. Synchronizes Remote Copy volume groups. 4.
InForm OS Version 2.3.1 Remote Copy User’s Guide 5 Performance and Scripting Considerations In this chapter 5.1 Performance Notes for RCIP Configuration 5.1 5.2 Performance Notes for RCFC Configuration 5.5 5.3 Scripting Notes 5.5 This chapter discusses performance considerations for using 3PAR Remote Copy. At the end of the chapter, scripting notes are also provided. 5.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTE: This limitation does not apply to 1-to-N Remote Copy. For 1-to-N Remote Copy, the primary storage server can have four RCIP interfaces; two to one secondary system and two to the other secondary system. After sending the I/O over a local GigE link, (which is more efficient than sending over a link in another node), the host writes coming into the nodes with the GigE links are preferentially sent over the local link.
InForm OS Version 2.3.1 Remote Copy User’s Guide Because the MTU needs to be supported by all the switches and routers in the IP network, the default MTU of the GigE interfaces is 1500 bytes, which is supported by all vendor hardware. If your network supports 9000 byte MTU, it is recommended that you set the 3PAR GigE adapter’s MTU to 9000 bytes. See Increasing MTU (Optional) on page 3.
Remote Copy User’s Guide InForm OS Version 2.3.1 5.1.6.2 Synchronous Mode Synchronous mode adds more latency to host writes because the write has to be committed on both primary and backup storage servers. The host service time increases because the write operation has to be sent to the secondary server over the IP network and an acknowledgement must be sent back through this network before the host is acknowledged. 5.
InForm OS Version 2.3.1 Remote Copy User’s Guide 5.2 Performance Notes for RCFC Configuration The following sections contain performance notes for Remote Copy over Fibre Channel (RCFC) configuration. 5.2.1 RCFC Links For Remote Copy over Fibre Channel configurations, each link between a Remote Copy pair is a physical link between a controller node on one storage server and a controller node on the other storage server in the pair.
Remote Copy User’s Guide 5.6 Scripting Notes InForm OS Version 2.3.
InForm OS Version 2.3.1 Remote Copy User’s Guide A Quick Setup Guide This Quick Setup Guide summarizes the commands required to set up storage server pairs for the use of 3PAR Remote Copy. Refer to Chapter 3, Remote Copy Setup or Chapter 4, Remote Copy in Domains for detailed setup instructions and to Appendix B, Remote Copy Commands for command syntax. This guide is divided into four sections: ■ Setting Up the Remote Copy Transport Layer for RCIP on page A.
Remote Copy User’s Guide InForm OS Version 2.3.1 A.1 Setting Up the Remote Copy Transport Layer for RCIP Table A-1 summarizes how to configure the Remote Copy pair for RCIP. Table A-1.
InForm OS Version 2.3.1 Remote Copy User’s Guide A.2 Setting Up the Remote Copy Transport Layer for RCFC Table A-2 summarizes how to configure the Remote Copy pair for RCFC. Table A-2. RCFC Setup Step 1 Reference Primary System Backup System Setting Up the For each Fibre Channel For each Fibre Channel Remote Copy adaptor port: adaptor port: Interface for controlport config controlport config rcfc RCFC on rcfc -ct point -ct point -f page 3.
Remote Copy User’s Guide InForm OS Version 2.3.1 For 1-to-N Remote Copy configurations, follow steps 1 through 10 in Table A-3 to set up ■ the first pair in the configuration. Repeat the entire process for each additional pair up to a maximum of two pairs. NOTE: For 1-to-N Remote Copy, all Remote Copy pairs must share the same primary storage server. For detailed instructions on setting up Remote Copy, refer to Chapter 3, Remote Copy Setup or Chapter 4, Remote Copy in Domains. Table A-3.
InForm OS Version 2.3.1 Remote Copy User’s Guide Table A-3. Remote Copy Setup (continued) Step Reference Primary System 4 “ -- Backup System For RCIP: creatercopytarget IP : For RCFC: creatercopytarget FC 5 6 “ showrcopy showrcopy InForm OS CLI Create virtual Creates virtual volumes the Administrator’s volumes same size as the primary Manual 7 8 servers.
Remote Copy User’s Guide InForm OS Version 2.3.1 Table A-3. Remote Copy Setup (continued) Step 11 (for bidirectional Remote Copy) Reference Setting Up Primary System -- Backup System creatercopygroup Bidirectional Remote Copy on : page 3.25 12 “ -- (optional) setrcopygroup period asynchronous periodic mode only 13 “ -- admitrcopyvv 14 A.
InForm OS Version 2.3.1 Remote Copy User’s Guide A.4 Setting Up Synchronous Long Distance Remote Copy Table A-4 summarizes how to set up Synchronous Long Distance Remote Copy pairs and to then begin using the Remote Copy software. Table A-4.
Remote Copy User’s Guide InForm OS Version 2.3.1 Table A-4.
InForm OS Version 2.3.1 Remote Copy User’s Guide Table A-4.
Remote Copy User’s Guide InForm OS Version 2.3.1 Table A-4. Synchronous Long Distance Remote Copy Setup (continued) Backup System 2 Step 12 Reference * Primary System For each virtual Backup System 1 (asynchronous (synchronous) periodic) -- -- -- -- volume created in step 11: admitrcopyvv : : 13 * startrcopygroup 14 A.
InForm OS Version 2.3.1 Remote Copy User’s Guide B Remote Copy Commands In this appendix admitrcopylink B.3 admitrcopytarget B.5 admitrcopyvv B.7 controlport B.9 creatercopygroup B.18 creatercopytarget B.20 dismissrcopylink B.23 dismissrcopytarget B.25 dismissrcopyvv B.27 growvv B.29 removercopygroup B.31 removercopytarget B.33 setrcopygroup B.35 setrcopytarget B.43 setvv B.47 Remote Copy Commands B.
Remote Copy User’s Guide B.2 InForm OS Version 2.3.1 showport B.52 showrcopy B.57 showrctransport B.62 startrcopy B.66 startrcopygroup B.67 statport B.69 statrcopy B.74 stoprcopy B.77 stoprcopygroup B.79 syncrcopy B.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND admitrcopylink DESCRIPTION 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 ...
Remote Copy User’s Guide InForm OS Version 2.3.1 RESTRICTIONS Functionality of this command requires the 3PAR Remote Copy license. Contact your local service provider for more information. EXAMPLES The following example adds a link on System2 (), using the node, slot, and port information of node 1, slot 1, port 1 of the Ethernet port on the primary system. The IP address 193.1.2.11 specifies the address on the target system: cli% admitrcopylink System2 1:1:1:193.1.2.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND admitrcopytarget DESCRIPTION The admitrcopytarget command adds a target to a Remote Copy volume group. SYNTAX admitrcopytarget [:]... AUTHORITY Service 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 (see page B.20).
Remote Copy User’s Guide InForm OS Version 2.3.1 RESTRICTIONS Functionality of this command requires the 3PAR Remote Copy license. Contact your local service provider for further information. EXAMPLES In the following example, the admitrcopytarget command adds the target target1 in synchronous mode to volume group Group1. cli% admitrcopytarget target1 sync Group1 NOTES None. B.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND admitrcopyvv DESCRIPTION The admitrcopyvv command adds an existing virtual volume to an existing Remote Copy volume group. SYNTAX admitrcopyvv [:] AUTHORITY Service NOTE: You need access to the domain of the specified group () in order to run this command. OPTIONS None.
Remote Copy User’s Guide InForm OS Version 2.3.1 RESTRICTIONS Functionality of this command requires the 3PAR Remote Copy license. Contact your local service provider for further information. EXAMPLES In the following example, the admitrcopyvv command adds the volume vv1 to the primary volume group Group1. At the same time, it adds the volume on the target system InServ1_in to the corresponding secondary volume group Group1.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND controlport DESCRIPTION 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 in 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] .
Remote Copy User’s Guide ■ InForm OS Version 2.3.1 controlport rcip ping [-c |-w |-s |-pf] ... ■ controlport rcfc init [-f] ■ controlport rcfc delete [-f] AUTHORITY Super, Service NOTE: You need access to all domains in order to run this command. SUBCOMMANDS config Sets the specified connection mode and type on FC ports. Also allows setting the unique node WWN option for the port.
InForm OS Version 2.3.1 Remote Copy User’s Guide cl2 Specifies the Fibre Channel Class-2 parameter of the port. The specified port will be reset. Note that this option is deprecated and will be removed in a subsequent release. rate Specifies the data rate of the Fibre Channel port. The specified port will be reset. vcn Sets the VLUN Change Notification (VCN) generation support (enable or disable).
Remote Copy User’s Guide InForm OS Version 2.3.1 rcip mtu Sets the Maximum Transfer Unit (MTU) size for the specified Remote Copy interface(s), overriding the default of 1500. The largest supported value is 9000 and the smallest is 100. Only for RCIP ports. Refer to Specifiers on page B.14 for parameters required to issue this subcommand. rcip state up|down Sets the specified Remote Copy interface(s) as either up or down. Only for RCIP ports. Refer to Specifiers on page B.
InForm OS Version 2.3.1 Remote Copy User’s Guide -l Forces the port to reload firmware. This option can only be used with the rst subcommand and cannot be used with the -i option. -c When used with the lip subcommand: -c If using a private loop topology, a Loop Initialization Primitive (LIP) command is issued from the port. If a cage is specified using the argument, the LIP is issued through the cage controller. If using a point-to-point topology, the link is reset.
Remote Copy User’s Guide InForm OS Version 2.3.1 -pf Prevents fragmentation of the packets when issuing the controlport rcip ping command. -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.
InForm OS Version 2.3.1 Remote Copy User’s Guide slot Specifies the PCI bus slot in the specified node using a number from 0 to 6. port Specifies the Fibre Channel adaptor port number of the PCI card in the specified PCI bus slot using 1 to 4. Specifies the IP address for a Remote Copy interface. Specifies the gateway address for a Remote Copy interface. Specifies the netmask for a Remote Copy interface.
Remote Copy User’s Guide InForm OS Version 2.3.1 EXAMPLES The following example shows how to increase MTU to 9000 on Gigabit Ethernet port 1 in node 6, slot 3: cli% controlport rcip mtu 9000 6:3:1 Remote Copy change successful. The following example shows how to set Remote Copy interface 172.16.1.11 on a GigE port 1 in node 6, slot 3 using a netmask of 255.255.255.0: cli% controlport rcip addr 172.16.1.11 255.255.255.
InForm OS Version 2.3.1 ■ Remote Copy User’s Guide If there are active hosts or physical disks when issuing the controlport rst or offline commands, a warning is returned and you are prompted for confirmation to complete the execution of the commands. ■ When issuing the controlport ct, cl2, rate, or rscn commands, if there are active disks on the port, an error is returned.
Remote Copy User’s Guide InForm OS Version 2.3.1 COMMAND creatercopygroup DESCRIPTION The creatercopygroup command creates a Remote Copy volume group. SYNTAX creatercopygroup [options] [:...] AUTHORITY Super, Edit 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.
InForm OS Version 2.3.1 Remote Copy User’s Guide RESTRICTIONS This command requires the 3PAR Remote Copy license. Contact your local service provider for further information.
Remote Copy User’s Guide InForm OS Version 2.3.1 COMMAND creatercopytarget DESCRIPTION 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 []...
InForm OS Version 2.3.1 Remote Copy User’s Guide []... Specifies the node, slot, port of the Fibre Channel adaptor port on the primary system and World Wide Name (WWN) of the peer port on the target system. This specifier can be repeated. RESTRICTIONS Functionality of this command requires the 3PAR Remote Copy license. Contact your local service provider for more information.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTES ■ IP targets are made up of pairs composed of the node, slot and port of the ethernet port on the local system and an IP address of the peer port on the target system. ■ FC targets are 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. B.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND dismissrcopylink DESCRIPTION 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 Service NOTE: You need access to all domains in order to run this command.
Remote Copy User’s Guide InForm OS Version 2.3.1 ... Specifies the node, slot, and port of the Ethernet port on the local system and an IP address of the peer port on the target system. This specifier can be repeated. ... Specifies the node, slot, and port of the Fibre Channel adaptor port on the primary system and a World Wide Name (WWN) of the peer port on the target system. This specifier can be repeated.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND dismissrcopytarget DESCRIPTION The dismissrcopytarget command removes a Remote Copy target from a Remote Copy volume group. SYNTAX dismissrcopytarget AUTHORITY Service 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.
Remote Copy User’s Guide NOTES None. B.26 dismissrcopytarget InForm OS Version 2.3.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND dismissrcopyvv DESCRIPTION The dismissrcopyvv command removes a virtual volume from a Remote Copy volume group. SYNTAX dismissrcopyvv AUTHORITY Edit, Service 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 removed. Volumes are added to a group with the admitrcopyvv command.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTES ■ The dismissrcopyvv command removes any Remote Copy synchronization snapshots affiliated with the removed volume. ■ 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 volume will be removed from the corresponding secondary group. If the policy is set and the group is a secondary, then this command will fail. B.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND growvv DESCRIPTION The growvv command increases the size of a virtual volume. SYNTAX growvv [g|G|t|T] AUTHORITY Edit, Service 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTES Ensure that there is sufficient space to mirror the grow of the volume on the secondary server before growing the volume on the primary server. B.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND removercopygroup DESCRIPTION The removercopygroup command removes a Remote Copy volume group. SYNTAX removercopygroup AUTHORITY Edit OPTIONS None. SPECIFIERS The name of the group to be removed. RESTRICTIONS ■ This command requires the 3PAR Remote Copy license. Contact local service provider for further information. ■ This is not allowed if Remote Copy is in progress; the system will generate an error.
Remote Copy User’s Guide InForm OS Version 2.3.1 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.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND removercopytarget DESCRIPTION The removercopytarget command removes target designation from a Remote Copy system and removes all links affiliated with that target definition. SYNTAX removercopytarget [options] AUTHORITY Edit 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 EXAMPLES The following example removes targets InServ1 and InServ2 from the primary and backup servers in a Remote Copy pair: cli% removercopytarget InServ1 cli% removercopytarget InServ2 NOTES None. B.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND setrcopygroup DESCRIPTION The setrcopygroup command does the following: ■ Sets the policy of the Remote Copy volume group for dealing with I/O failure and error handling. ■ Switches the direction of transfer between volume groups. ■ Sets a resynchronization period for volume groups in asynchronous periodic mode. ■ Sets the group’s mode.
Remote Copy User’s Guide InForm OS Version 2.3.1 OPTIONS -t Specifies that the setrcopygroup command be applied to all relevant groups of the indicated target. If no group names are specified, then all groups in that target that are in the correct state for the specified subcommand will have it applied to them. For groups with multiple targets, this option must be specified for the recover, restore, reverse, and pol subcommands.
InForm OS Version 2.3.1 Remote Copy User’s Guide Specifies that groups are stopped before running the indicated reverse or restore values of the specifier. setrcopygroup B.
Remote Copy User’s Guide InForm OS Version 2.3.1 -local When issuing the command with reverse as the value of the specifier, only the group’s direction is changed on the system where the command is issued. -natural When issuing the command with the reverse as the value of the specifier, only the natural direction of the groups is reversed, leaving the current direction unchanged.
InForm OS Version 2.3.1 Remote Copy User’s Guide no_auto_recover Specifies that if the Remote Copy is stopped as a result of the Remote Copy links going down, the group must be restarted manually after the links come back up (default). 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 recover Used for groups on which the failover operation has already been run. Changes matching primary volume groups on the backup system to secondary volume groups and then starts and synchronizes all groups. restore Used on groups on which the recover operation has already been run. Returns all groups to their natural direction and starts them.
InForm OS Version 2.3.1 ■ Remote Copy User’s Guide The reverse value of the is not to be used as part of the normal disaster recovery process. EXAMPLES The following example sets the group policy for Group1: cli% setrcopygroup pol fail_wrt_on_err Group1 The following example reverses the current direction of secondary group Group1 on InServ2 (the secondary system) so that I/O might be applied to the group after disaster recovery: cli% setrcopygroup failover Group1.
Remote Copy User’s Guide ■ InForm OS Version 2.3.1 The -nosnap option can be used when making a secondary group take over as the primary after a disaster takes down the primary (setrcopygroup failover -nosnap...). This option indicates that no incremental resynchronization of the primary group is possible while the primary system is coming back online. Without this option, a snapshot is taken when the secondary server takes over as the primary.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND setrcopytarget DESCRIPTION The setrcopytarget command sets the name, policies, or throughput definition for the target’s links.
Remote Copy User’s Guide InForm OS Version 2.3.1 enable|disable Enables or disables the target. OPTIONS None. SPECIFIERS Specifies the target name for the target definition previously created with the creatercopytarget command (see creatercopytarget on page B.20). This specifier can only be used with the pol subcommand.
InForm OS Version 2.3.1 Remote Copy User’s Guide The measured bandwidth of the connection to the target, specified in kilobytes (kB) per second. This specifier can only be used with the tunelinks subcommand. The measured round-trip latency of the connection to the target, specified in milliseconds (ms). This specifier can only be used with the tunelinks subcommand. RESTRICTIONS ■ This command requires the 3PAR Remote Copy license.
Remote Copy User’s Guide ◆ ■ InForm OS Version 2.3.1 setrcopytarget tunelinks Under normal operating conditions the mirror_config policy should never be changed to no_mirror_config. This policy option is included only as a method to correct several unusual error conditions that might occur in the course of operation which result in a mismatch in configuration between the two sides of a Remote Copy pair.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND setvv DESCRIPTION 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 Edit OPTIONS At least one of the following options must be specified: -clrrsv Specifies that all reservation keys (i.e.
Remote Copy User’s Guide InForm OS Version 2.3.1 -retain
InForm OS Version 2.3.1 Remote Copy User’s Guide –pol [,...] Specifies the policy is implemented by a virtual volume. Valid policies are as follows: stale_ss Specifies that invalid (stale) snapshot volumes are permitted. Failures to update snapshot data occur when there is not sufficient administration or snapshot space. Failures to update snapshot data does not affect the write to the base volume. However, the snapshot is considered invalid.
Remote Copy User’s Guide InForm OS Version 2.3.1 no_zero_detect Disables the InServ Storage Server to scan for zeros in the incoming write data to reclaim allocated space on the volume. Multiple policies can be specified and are separated with commas. If a policy is not specified, the policy defaults to stale_ss. The following options can only be used on Thinly Provisioned Virtual Volumes (TPVVs): -usr_aw This option returns a user space allocation warning.
InForm OS Version 2.3.1 Remote Copy User’s Guide SPECIFIERS ... Specifies the virtual volume name or all virtual volumes that match the pattern specified, using up to 31 characters. The patterns are glob-style patterns. Valid characters include alphanumeric characters, periods, dashes, and underscores. RESTRICTIONS At least one option must be specified. EXAMPLES The following example sets the policy of virtual volume vv1 to no_stale_ss.
Remote Copy User’s Guide InForm OS Version 2.3.1 COMMAND showport DESCRIPTION The showport command displays information about ports in the system. SYNTAX The syntax of the showport command can be one of the following: ■ showport [options] [-failed] [-sortcol
[,]] AUTHORITY Super, Service, Edit, Browse OPTIONS -i Shows port hardware inventory information. -c Displays all devices connected to each loop (by position on the loop).InForm OS Version 2.3.1 Remote Copy User’s Guide -iscsiname Displays iSCSI names associated with iSCSI ports. -sfp Displays information about the SFPs attached to ports. -ddm Displays information about the SFPs DDM. This option must be used with the -sfp option. -d Displays detailed information about the SFPs attached to ports. This option is used with the -sfp option. -failed Shows only failed ports. -state Displays the detailed state information. -s Displays the detailed state information.
Remote Copy User’s Guide InForm OS Version 2.3.1 EXAMPLES The following example displays information about all Remote Copy ports: cli% showport –rc N:S:P State HwAddr Rate 5:3:2 ready 25320002AC000006 2Gbps 4:1:1 ready 24110002AC000006 2Gbps 0:5:1 ready 0002B39B2013 100Mbps Type rcip rcip rcip 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.
InForm OS Version 2.3.1 Remote Copy User’s Guide The following example displays information about RCIP ports: cli% showport N:S:P State 0:1:1 offline 0:1:1 offline 1:2:1 offline 1:2:1 offline -rcip ---HwAddr--- IPAddr Netmask Gateway MTU Rate Duplex AutoNeg 000423C21B72 - n/a n/a n/a 000423C21B73 - n/a n/a n/a 000423ADE95E - n/a n/a n/a 000423ADE95F - n/a n/a n/a 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTES For full showport command information and additional usage examples, refer to the InForm OS Command Line Interface Reference. B.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND showrcopy DESCRIPTION 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 targets [] Specifies either all target definitions or a specific target definition by name or by glob-style pattern. RESTRICTIONS This command requires the 3PAR Remote Copy license. Contact your local service provider for further information.
InForm OS Version 2.3.1 Remote Copy User’s Guide ■ unsupported. The target system’s TPD version is not compatible with this system’s version. ■ failing. The target’s links have all failed, but its groups have not been stopped. ■ failed. The target’s links have all failed and its groups have been stopped. The following values can appear in the Link Information Status field: ■ Not Started.
Remote Copy User’s Guide InForm OS Version 2.3.1 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. Currently attempting to start the group. ◆ Started. Group is started (has Remote Copy running). ◆ Stopped. Group was stopped. ■ Role. The role of the group as either Primary or Secondary. ■ Mode.
InForm OS Version 2.3.1 Remote Copy User’s Guide NOTES ■ If the showrcopy command is used with no specifiers, all configuration information is displayed. ■ 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. ■ If showrcopy link|group|target is used without specifying a name, information for all links, groups, or targets is displayed.
Remote Copy User’s Guide InForm OS Version 2.3.1 COMMAND showrctransport DESCRIPTION The showrctransport command shows status and information about end-to-end transport for Remote Copy in the system. SYNTAX showrctransport [options] AUTHORITY Super, Service, Edit, Browse OPTIONS -rcfc Show information about Fibre Channel end-to-end transport. -rcip Show information about Ethernet end-to-end transport. SPECIFIERS None. RESTRICTIONS None.
InForm OS Version 2.3.1 ■ Remote Copy User’s Guide Peer_Address. IP address of the Remote Copy storage server port connected to this Remote Copy port. ■ Address. IP address of the Remote Copy storage server port. ■ State. Remote copy end-to-end transport state. Can include one of the following results: ◆ new. Configuration is not completed on this port. ◆ incomplete. Configuration is not yet completed on the peer port. ◆ ready.
Remote Copy User’s Guide InForm OS Version 2.3.1 ■ IPAddress. IP address of the Ethernet port indicated in the N:S:P column. ■ PeerIPAddress. IP address of the peer Ethernet port to which the port indicated in the N:S:P column is connected. ■ Netmask. Netmask for the IP address. ■ Gateway. Address of the gateway. ■ MTU. Maximum Transfer Unit (MTU) size for the specified Remote Copy interface (default is 1500). The largest supported value is 9000 and the smallest is 100. ■ Rate.
InForm OS Version 2.3.1 Remote Copy User’s Guide NOTES None. showrctransport B.
Remote Copy User’s Guide InForm OS Version 2.3.1 COMMAND startrcopy DESCRIPTION The startrcopy command enables Remote Copy. SYNTAX startrcopy AUTHORITY Super, Edit NOTE: You need access to all domains in order to run this command. OPTIONS None. SPECIFIERS None. RESTRICTIONS This command requires the 3PAR Remote Copy license. Contact your local service provider for further information.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND startrcopygroup DESCRIPTION The startrcopygroup command turns on Remote Copy for the specified Remote Copy volume group. SYNTAX startrcopygroup [options ] AUTHORITY Super, Edit OPTIONS -wait Specifies that the command blocks until the initial synchronization is complete. The system generates an event when the synchronization is complete. -nosync Prevents the initial synchronization and sets the volumes to a synchronized state.
Remote Copy User’s Guide InForm OS Version 2.3.1 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 started. If the policy is set and the group is a secondary, then this command will fail. ■ If the mirror_config policy is not set, then the corresponding secondary group must already be started or this command will fail.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND statport DESCRIPTION The statport command displays read and write (I/O) statistics for ports. SYNTAX statport [options ]|-rcfc|-rcip AUTHORITY Super, Service, Edit, Browse 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 –rw Display reads and writes separately. If this option is not used, then the total of reads plus writes is displayed. –d Sets the interval, in seconds, that statistics are sampled using an integer from 1 through 2147483. If no interval is specified, the option defaults to an interval of two seconds.
InForm OS Version 2.3.1 Remote Copy User’s Guide curs Specifies that only current statistics are displayed. avgs Specifies that only averages are displayed. maxs Specifies that only statics for maximum values are displayed. The operation argument can be specified with one of the following arguments: r Specifies that read-only statistics are displayed. w Specifies that write-only statistics are displayed. t|rw Specifies that statistics for read and write totals are displayed.
Remote Copy User’s Guide InForm OS Version 2.3.1 Specifies the minimum threshold using any integer. The integer can be optionally followed with k or K to indicate a multiple of 1000, m or M to indicate a multiple of 1000000, or g or G to indicate a multiple of 1000000000. An example of this option in use is –filt curs,r,iops,10k that indicates that statistics for a device that has more than 10,000 current read-only I/O operations are displayed. –ni Shows only nonidle devices.
InForm OS Version 2.3.1 ■ I/O per second Cur. The current number of I/O per second. ■ I/O per second Avg. The average number of I/O per second. ■ KBytes per Max. The maximum number of KB per second. ■ KBytes per Cur. The current number of KB per second. ■ KBytes per Avg. The average number of KB per second. ■ Svt ms Max. The maximum service time in milliseconds. ■ Svt ms Cur. The current service time in milliseconds. ■ Svt ms Avg. The average service time in milliseconds. ■ IOSz KB Cur.
Remote Copy User’s Guide InForm OS Version 2.3.1 COMMAND statrcopy DESCRIPTION The statrcopy command displays statistics for Remote Copy volume groups. SYNTAX statrcopy [options ] AUTHORITY Super, Service, Edit, Browse 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.
InForm OS Version 2.3.1 Remote Copy User’s Guide EXAMPLES The following example shows statistics for sending links link0 and link1: cli% statrcopy 17:37:01 05/17/07 -Throughput(KBytes per sec)Target Node Address IPC Total(KBytes) Current Average --------------------------------------------------------------------------amp1 0 10.100.33.96 RCs041 404761.15 4.95 4.95 amp1 1 10.101.33.96 RCs142 404661.63 3.30 3.30 --------------------------------------------------------------------------amp1 809422.78 8.
Remote Copy User’s Guide InForm OS Version 2.3.1 NOTES ■ This command repeats until directed to stop. ■ Within the context of this command, KB is 1000 bytes, MB is 1000KB, and GB is 1000MB. ■ The numbers displayed by this command might be somewhat less than those displayed with statport, as statrcopy output does not include TCP/IP overhead. B.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND stoprcopy DESCRIPTION The stoprcopy command disables the Remote Copy functionality for any started Remote Copy volume groups. AUTHORITY Super, Edit NOTE: You need access to all domains in order to run this command. SYNTAX stoprcopy [options] 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 EXAMPLES The following example disables the Remote Copy functionality of all Remote Copy volume groups: cli% stoprcopy -stopgroups NOTES ■ If the -stopgroups option is not used, all groups must already be stopped. ■ An older version of this command provided specifiers to disable the primary or backup systems. These specifiers were deprecated in InForm OS release 2.2.3.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND stoprcopygroup DESCRIPTION The stoprcopygroup command stops the Remote Copy functionality for the specified Remote Copy volume group. SYNTAX stoprcopygroup [option ] AUTHORITY Super, Edit 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 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.
InForm OS Version 2.3.1 Remote Copy User’s Guide COMMAND syncrcopy DESCRIPTION The syncrcopy command manually synchronizes Remote Copy volume groups. SYNTAX syncrcopy [options ] AUTHORITY Super, Edit 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. NOTE: Using the -n option requires a full synchronization at the next sync.
Remote Copy User’s Guide InForm OS Version 2.3.1 RESTRICTIONS This command requires the 3PAR Remote Copy license. Contact your local service provider for further information. EXAMPLES The following example specifies that Remote Copy volume group Group1 should be synchronized with it’s corresponding secondary volume group: cli% syncrcopy Group1 Synchronization request issued for group Group1 NOTES ■ Mode (synchronous or asynchronous periodic) is set using the creatercopygroup command.
InForm OS Version 2.3.1 Remote Copy User’s Guide C Example Setup and Disaster Recovery In this chapter C.1 Remote Copy Setup Examples C.2 C.2 Bidirectional Synchronous Disaster Recovery Example C.4 C.3 N-to-1 Asynchronous Periodic Disaster Recovery Example C.15 C.4 1-to-N Unidirectional Asynchronous Periodic Disaster Recovery Example C.27 C.5 Synchronous Long Distance Remote Copy Disaster Recovery Example C.38 C.5.1 Synchronous Backup Server Assumes Role of Primary Server C.43 C.5.
Remote Copy User’s Guide InForm OS Version 2.3.1 C.1 Remote Copy Setup Examples The following figures depict supported Remote Copy configurations. For detailed setup instructions for each configuration, refer to Setting Up Remote Copy on page 3.16 in Chapter 3, Remote Copy Setup. Primary to Backup Secondary Volume Group X.r Primary Volume Group X Backup Storage Server (InServ2) Primary Storage Server (InServ1) Direction of data replication Figure C-1. Unidirectional Remote Copy Group X to Group X.
InForm OS Version 2.3.1 Remote Copy User’s Guide Primary Volume Group W Group W to Group W.r Secondary Volume Group Y.r Primary Volume Group Z Group Y to Group Y.r Group Z to Group Z.r Primary Volume Group Y InServ1 Group X to Group X.r Primary Volume Group X InServ2 Secondary Volume Group W.r Secondary Volume Group Z.r InServ3 Secondary Volume Group X.r InServ4 Direction of data replication Figure C-3.
Remote Copy User’s Guide InForm OS Version 2.3.1 C.2 Bidirectional Synchronous Disaster Recovery Example The following example contains a disaster recovery cycle for a bidirectional Remote Copy pair (InServ1/InServ2) with synchronous mode volume groups. The following information applies to this bidirectional disaster recovery example: ■ The members of the Remote Copy pair are an eight-node cluster called InServ1 and a four-node cluster called InServ2.
InForm OS Version 2.3.1 Remote Copy User’s Guide InServ1 Primary Group: sync_group_1 localvv.0, localvv.1 Target: InServ2 Secondary Group: sync_group_2.r11 remotevv.0, remotevv.1 Target: InServ2 172.1.1.96 172.1.2.96 Node 0 Node 1 Network InServ2 Node 0 Node 1 172.1.1.11 172.1.2.11 Secondary Group: Primary Group: sync_group_1.r96 remotevv.0, remotevv.1 Target: InServ1 sync_group_2 localvv.0, localvv.1 Target: InServ1 Figure C-4.
Remote Copy User’s Guide InForm OS Version 2.3.1 The following showrcopy command output displays status for InServ1 and InServ2 under normal operation of bidirectional synchronous mode Remote Copy: On InServ1: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ2 9 IP ready mirror_config Link Information Target Node Address Status Options InServ2 0 10.100.33.11 Up InServ2 1 10.101.33.11 Up receive 0 10.100.33.
InForm OS Version 2.3.1 Remote Copy User’s Guide On InServ2: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 2 IP ready mirror_config Link Information Target Node Address Status Options InServ1 0 10.100.33.96 Up InServ1 1 10.101.33.96 Up receive 0 10.100.33.96 Up receive 1 10.101.33.96 Up Group Information Name Target sync_group_1.
Remote Copy User’s Guide InForm OS Version 2.3.1 For a Remote Copy pair with synchronous mode volume groups, when a failure occurs (for example InServ1 becomes unavailable) such that all links between the storage servers are broken, after 20 seconds the system marks the sending links as Down. After another 20 seconds, the system marks the targets as failed.
InForm OS Version 2.3.1 Remote Copy User’s Guide To initiate disaster recovery for a bidirectional Remote Copy pair with synchronous volume groups: 1 On the failover system, make all secondary groups primary by reversing the direction of the failed targets for each group. Issuing the setrcopygroup failover command switches every secondary group for the specified target. For this example, this is done by reversing the failed target InServ1 for the secondary group sync_group_1.
Remote Copy User’s Guide 2 InForm OS Version 2.3.1 On the failover system, verify the reversal by using the showrcopy command and checking that the Role for the group is now Primary-Rev, as shown in bold in the following example: On InServ2: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 2 IP failed mirror_config Link Information Target InServ1 InServ1 receive receive Node 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.
InForm OS Version 2.3.1 4 Remote Copy User’s Guide Issue the showrcopy command and verify that the target displays ready, the sending links display Up, and that the volumes are Syncing as shown in bold in the following example: On InServ2 : Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 2 IP ready mirror_config Link Information Target InServ1 InServ1 receive receive Node 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.33.96 10.101.
Remote Copy User’s Guide 5 InForm OS Version 2.3.
InForm OS Version 2.3.1 6 Remote Copy User’s Guide Restore the direction of the system by issuing the setrcopygroup restore command on the failover system. On InServ2: # setrcopygroup restore -t InServ1 7 Issue the showrcopy command to verify that the direction of InServ2 has been restored and group sync_group_1.
Remote Copy User’s Guide 8 InForm OS Version 2.3.1 Issue the showrcopy command to verify that the direction of InServ1 has been restored and group sync_group_1 displays as Primary, as shown in bold in the following example: On InServ1: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ2 9 IP ready mirror_config Link Information Target InServ2 InServ2 receive receive Node 0 1 0 1 Address 10.100.33.11 10.101.33.11 10.100.33.
InForm OS Version 2.3.1 Remote Copy User’s Guide C.3 N-to-1 Asynchronous Periodic Disaster Recovery Example The following example contains a disaster recovery cycle for an N-to-1 configuration with two Remote Copy pairs (InServ1/InServ2 and InServ1/InServ3) with asynchronous periodic mode volume groups. Figure C-5 illustrates the relationship between primary servers InServ2 and InServ3 with backup server InServ1.
Remote Copy User’s Guide ◆ ■ InForm OS Version 2.3.1 Remote copy nodes: 0and 1 Information for InServ3 is as follows: ◆ System ID: 11 ◆ Links: IP address 172.100.33.11 IP address 172.101.33.11 ◆ ■ Remote copy nodes: 0and 1 Two virtual volumes on InServ1 called remotevv.0 and remotevv.1 are the members of periodic_group_1.r96, the secondary group that is automatically created at the same time as periodic_group_1. ■ Two virtual volumes on InServ1 called remotevv.2 and remotevv.
InForm OS Version 2.3.1 Remote Copy User’s Guide The following showrcopy command output displays status for InServ1, InServ2, and InServ3 under normal operation of asynchronous periodic mode Remote Copy: On InServ1: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ2 7 IP ready mirror_config InServ3 8 IP ready mirror_config Link Information Target InServ2 InServ2 InServ3 InServ3 receive receive Node 0 1 0 1 0 1 Address 10.100.
Remote Copy User’s Guide InForm OS Version 2.3.1 On InServ2: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 11 IP ready mirror_config Link Information Target InServ1 InServ1 receive receive Node 0 1 0 1 Address 10.100.33.63 10.101.33.63 10.100.33.63 10.101.33.
InForm OS Version 2.3.1 Remote Copy User’s Guide On InServ3: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 4 IP ready mirror_config Link Information Target InServ1 InServ1 receive receive Node 0 1 0 1 Address 10.100.33.63 10.101.33.63 10.100.33.63 10.101.33.
Remote Copy User’s Guide InForm OS Version 2.3.1 The following example displays the showrcopy command output on InServ1 300 seconds after InServ2 has become unavailable: On InServ1: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ2 7 IP failed mirror_config InServ3 8 IP ready mirror_config Link Information Target InServ2 InServ2 InServ3 InServ3 receive receive Node 0 1 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.33.
InForm OS Version 2.3.1 Remote Copy User’s Guide the failed target InServ1 for the secondary group primary_group_1.
Remote Copy User’s Guide 3 InForm OS Version 2.3.1 After the failed system (InServ2) has been restored, issue the setrcopygroup recover command on the failover system to resynchronize the servers.
InForm OS Version 2.3.
Remote Copy User’s Guide InForm OS Version 2.3.1 CAUTION: The group must be started at the time the setrcopygroup restore command is issued. Issue the showrcopy groups command to confirm the group has been started. If it has not been started then issue the startrcopygroup command and wait for any synchronizations that are started to complete before issuing the setrcopygroup restore command. 6 Restore the direction of the system by issuing the setrcopygroup restore command.
InForm OS Version 2.3.1 7 Remote Copy User’s Guide Issue the showrcopy command to verify that the direction of InServ2 has been restored and group periodic_group_1.
Remote Copy User’s Guide 8 InForm OS Version 2.3.1 Issue the showrcopy command to verify that the direction of InServ1 has been restored and group peridic_group_1 displays as Primary, as shown in bold in the following example: On InServ2: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 11 IP ready mirror_config Link Information Target InServ1 InServ1 receive receive Node 0 1 0 1 Address 10.100.33.63 10.101.33.63 10.100.33.
InForm OS Version 2.3.1 Remote Copy User’s Guide C.4 1-to-N Unidirectional Asynchronous Periodic Disaster Recovery Example The following example contains a disaster recovery cycle for a 1-to-N unidirectional configuration with two Remote Copy pairs (InServ1/InServ2 and InServ1/InServ3) with asynchronous periodic mode volume groups. Figure C-6 illustrates the relationship between primary server InServ1 and its two backup servers, InServ2 and InServ3.
Remote Copy User’s Guide InForm OS Version 2.3.1 IP address 172.100.33.96 IP address 172.101.33.96 ◆ ■ Remote Copy nodes: 0and 1 Information for InServ3 is as follows: ◆ System ID: 11 ◆ Links: IP address 172.100.33.11 IP address 172.101.33.11 ◆ ■ Remote Copy nodes: 0and 1 Two virtual volumes on InServ1 called localvv.0 and localvv.1 are the only members of periodic_group_1. ■ Two virtual volumes on InServ1 called localvv.2 and localvv.3 are the only members of periodic_group_2.
InForm OS Version 2.3.1 Remote Copy User’s Guide The following showrcopy command output displays status for InServ1, InServ2, and InServ3 under normal operation of asynchronous periodic mode Remote Copy: On InServ1: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ2 7 IP ready mirror_config InServ3 8 IP ready mirror_config Link Information Target InServ2 InServ2 InServ3 InServ3 receive receive Node 0 1 0 1 0 1 Address 10.100.
Remote Copy User’s Guide InForm OS Version 2.3.1 On InServ2: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 11 IP ready mirror_config Link Information Target InServ1 InServ1 receive receive Node 0 1 0 1 Address 10.100.33.63 10.101.33.63 10.100.33.63 10.101.33.63 Status Options Up Up Up Up Group Information Name Target Status Role Mode Options periodic_group_1.
InForm OS Version 2.3.1 Remote Copy User’s Guide On InServ3: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 4 IP ready mirror_config Link Information Target InServ1 InServ1 receive receive Node 0 1 0 1 Address 10.100.33.63 10.101.33.63 10.100.33.63 10.101.33.63 Status Options Up Up Up Up Group Information Name Target Status Role Mode Options periodic_group_2.
Remote Copy User’s Guide InForm OS Version 2.3.1 The following example displays the showrcopy command output on InServ2 300 seconds after InServ1 has become unavailable: On InServ2: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 7 IP failed mirror_config Link Information Target InServ1 InServ1 receive receive Node 0 1 0 1 Address 10.100.33.61 10.101.33.61 10.100.33.61 10.101.33.
InForm OS Version 2.3.1 2 Remote Copy User’s Guide On the failover system, verify the reversal by issuing the showrcopy command and checking that the Role for the group is now Primary-Rev, as shown in bold in the following example: On InServ2: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 7 IP failed mirror_config Link Information Target InServ1 InServ1 receive receive Node 0 1 0 1 Address 10.100.33.61 10.101.33.61 10.
Remote Copy User’s Guide 4 InForm OS Version 2.3.1 Issue the showrcopy command and verify that the target (InServ1) displays ready, the sending links display Up, and that the volumes are Syncing as shown in bold in the following example: On InServ2: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 7 IP ready mirror_config Link Information Target InServ1 InServ1 receive receive Node 0 1 0 1 Address 10.100.33.61 10.101.33.
InForm OS Version 2.3.
Remote Copy User’s Guide InForm OS Version 2.3.1 After the synchronization is verified, restore the direction of each system. CAUTION: The group must be started at the time the setrcopygroup restore command is issued. Issue the showrcopy groups command to confirm the group has been started. If it has not been started then issue the startrcopygroup command and wait for any synchronizations that are started to complete before issuing the setrcopygroup restore command.
InForm OS Version 2.3.
Remote Copy User’s Guide 8 InForm OS Version 2.3.1 Issue the showrcopy command to verify that the direction of InServ2 has been restored and group peridic_group_1.r96 displays as Secondary, as shown in bold in the following example: On InServ2: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServ1 11 IP ready mirror_config Link Information Target InServ1 InServ1 receive receive Node 0 1 0 1 Address 10.100.33.61 10.101.33.61 10.
InForm OS Version 2.3.1 Remote Copy User’s Guide server to the asynchronous backup server. See Asynchronous Backup Server Assumes Role of Primary Server on page C.59. ■ The primary server goes down and the asynchronous periodic backup server assumes the role of the primary server with no data transferred from the synchronous backup server. See Asynchronous Backup Server Assumes Role of Primary Server - No Data Transfer from the Synchronous Backup Server on page C.
Remote Copy User’s Guide ■ InForm OS Version 2.3.1 On InServA: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServB 58 FC ready 2FF70002AC0000C3 mirror_config InServC 59 IP ready mirror_config Link Information Target InServB InServB InServC InServC 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.
InForm OS Version 2.3.1 ■ Remote Copy User’s Guide On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC ready 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
Remote Copy User’s Guide ■ InForm OS Version 2.3.1 On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP ready mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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 C.
InForm OS Version 2.3.1 Remote Copy User’s Guide C.5.1 Synchronous Backup Server Assumes Role of Primary Server In this scenario, the primary server has gone down and the synchronous backup server is put into failover mode to assume the role of the primary server. InServA (primary) InServB (primary) Asynchronous Periodic InServC (backup) Figure C-8.
Remote Copy User’s Guide ■ InForm OS Version 2.3.1 On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC failed 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
InForm OS Version 2.3.1 ■ Remote Copy User’s Guide On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP failed mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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.
Remote Copy User’s Guide 1 InForm OS Version 2.3.1 Initiate disaster recovery to the synchronous backup server, InServB, by issuing the setrcopygroup failover command on InServB. # setrcopygroup failover -f -t InServA failover started with tasks: 5745 root@xnodee594:~/bin# waittask -v 5745 Id Type Name Status Phase Step -------StartTime------ ------FinishTime------5745 remote_copy_failover multi.1.
InForm OS Version 2.3.1 2 Remote Copy User’s Guide Issue showrcopy on InServB to verify it has become the primary system.
Remote Copy User’s Guide 3 InForm OS Version 2.3.1 Issue showrcopy on InServC to verify it is now the backup server to InServB and its volumes are synchronized with InServB. # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP failed mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB receive receive Node 0 1 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.33.195 10.
InForm OS Version 2.3.1 4 Remote Copy User’s Guide When InServA has recovered, issue the setrcopygroup recover command on InServB. # setrcopygroup recover -f -t InServA recover started with tasks: 5752 root@xnodee594:~/bin# waittask -v 5752 Id Type Name Status Phase Step -------StartTime------- -FinishTime5752 remote_copy_recover multi.1.r96 active 2/4 0/1 2009-06-29 12:30:54 PDT Detailed status: 2009-06-29 12:30:54 PDT 2009-06-29 12:30:54 PDT 2009-06-29 12:30:54 PDT primary to secondary.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 Groups on InServA temporarily switch to secondary mode, thereby promoting the Remote Copy snapshots to bring InServA and InServB to the same starting point. Once completed, Remote Copy is started between InServA and InServB and synchronization of the two system’s groups occurs. 5 When recovery completes, issue the showrcopy command on all systems to verify that InServA appears Up. C.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServA: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServB 58 FC ready 2FF70002AC0000C3 mirror_config InServC 59 IP ready mirror_config Link Information Target InServB InServB InServC InServC 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.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC ready 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP ready mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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 Target Status multi.1.
Remote Copy User’s Guide InForm OS Version 2.3.1 CAUTION: The group must be started at the time the setrcopygroup restore command is issued. Issue the showrcopy groups command to confirm the group has been started. If it has not been started then issue the startrcopygroup command and wait for any synchronizations that are started to complete before issuing the setrcopygroup restore command.
InForm OS Version 2.3.1 Remote Copy User’s Guide In the example above: ◆ Tasks are started for each group that has already been recovered. ◆ A final synchronization is started from InServB to InServC to ensure that InServC has the most recent data. ◆ Groups are then stopped and the primary volumes on InServB are switched to secondary volumes and secondary volumes on InServA are switched to primary volumes.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServA: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServB 58 FC ready 2FF70002AC0000C3 mirror_config InServC 59 IP ready mirror_config Link Information Target InServB InServB InServC InServC 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.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC ready 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP ready mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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 C.
InForm OS Version 2.3.1 Remote Copy User’s Guide C.5.2 Asynchronous Backup Server Assumes Role of Primary Server In this scenario, the primary server has gone down and the asynchronous periodic backup server is put into failover mode to assume the role of the primary server. During failover, the synchronous backup server temporarily assumes the role of the primary server in order to transfer its data to the asynchronous periodic backup server.
Remote Copy User’s Guide ■ InForm OS Version 2.3.1 On InServB: # showrcopy root@xnodee594:~/bin# showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC failed 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
InForm OS Version 2.3.1 ■ Remote Copy User’s Guide On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP failed mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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.
Remote Copy User’s Guide 1 InForm OS Version 2.3.1 Initiate disaster recovery to the asynchronous periodic backup server, InServC, by issuing the setrcopygroup failover command on InServC. # setrcopygroup failover -f -t InServA 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.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide Once completed, InServB and InServC are synchronized. InServC then assumes the role of the primary server and begins copying to InServB. 2 During the process described above, issue the showrcopy command on InServB and InServC to verify that the newer data is being pushed. Synchronous Long Distance Remote Copy Disaster Recovery Example C.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC failed 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP failed mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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 Target Status multi.1.
Remote Copy User’s Guide 3 InForm OS Version 2.3.1 Once the failover operation has completed, issue showrcopy on InServB and InServC to verify that the volumes have synchronized and InServC has assumed the role of the primary server (Primary-Rev). C.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC failed 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP new mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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 Target Status multi.1.
InForm OS Version 2.3.1 4 Remote Copy User’s Guide When InServA has recovered, issue the setrcopygroup recover command on InServC. Synchronous Long Distance Remote Copy Disaster Recovery Example C.
Remote Copy User’s Guide InForm OS Version 2.3.1 # setrcopygroup recover -f -t InServA recover started with tasks: 6747 root@xnodeed08:~/bin# waittask -v 6747 Id Type Name Status Phase Step -------StartTime------- -FinishTime6747 remote_copy_recover multi.1.r96 active 2/4 0/1 2009-06-29 14:52:43 PDT Detailed status: 2009-06-29 14:52:43 2009-06-29 14:52:43 2009-06-29 14:52:44 secondary. 2009-06-29 14:52:44 promotions.
InForm OS Version 2.3.1 Remote Copy User’s Guide In the example above: ◆ Tasks are launched for each group that has already been failed over. ◆ Groups on InServA temporarily switch to secondary mode, thereby promoting the Remote Copy snapshots to bring InServA and InServC to the same starting point. Once completed, Remote Copy is started between InServA and InServB and synchronization of the two system’s groups occurs.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServA: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServB 58 FC ready 2FF70002AC0000C3 mirror_config InServC 59 IP ready mirror_config Link Information Target InServB InServB InServC InServC 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.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC failed 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP ready mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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.
InForm OS Version 2.3.1 Remote Copy User’s Guide CAUTION: The group must be started at the time the setrcopygroup restore command is issued. Issue the showrcopy groups command to confirm the group has been started. If it has not been started then issue the startrcopygroup command and wait for any synchronizations that are started to complete before issuing the setrcopygroup restore command.
Remote Copy User’s Guide InForm OS Version 2.3.1 In the example above: ◆ Tasks are started for each group that has already been recovered. ◆ A final synchronization is started from InServC to InServB and from InServC to InServA to ensure that InServA and InServB have the most recent data. ◆ Groups are then stopped and the primary volumes on InServC are switched to secondary volumes and secondary volumes on InServA are switched to primary volumes.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServA: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServB 58 FC ready 2FF70002AC0000C3 mirror_config InServC 59 IP ready mirror_config Link Information Target InServB InServB InServC InServC 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.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC ready 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP ready mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 C.5.3 Asynchronous Backup Server Assumes Role of Primary Server - No Data Transfer from the Synchronous Backup Server In this scenario, the primary server has gone down. The data on the asynchronous periodic backup server is the most current and put into failover mode to assume the role of the primary server.
InForm OS Version 2.3.1 1 Remote Copy User’s Guide Initiate disaster recovery to the asynchronous periodic backup server, InServC, by issuing the setrcopygroup failover command on InServC. # setrcopygroup failover -f -t -discard InServA 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 this operation. InServC and InServB are synchronized, and InServC assumes the role of the primary server and begins copying to InServB. 2 Once the failover operation has completed, issue showrcopy on InServB and InServC to verify that the volumes have synchronized and InServC has assumed the role of the primary server (Primary-Rev). C.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC failed 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP new mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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 Target Status multi.1.
InForm OS Version 2.3.1 3 Remote Copy User’s Guide When InServA has recovered, issue the setrcopygroup recover command on InServC. NOTE: The groups on InServA may start if auto recover is set. This requires a manual stop of the groups on InServA. Synchronous Long Distance Remote Copy Disaster Recovery Example C.
Remote Copy User’s Guide InForm OS Version 2.3.1 # setrcopygroup recover -f -t InServA recover started with tasks: 6747 root@xnodeed08:~/bin# waittask -v 6747 Id Type Name Status Phase Step -------StartTime------- -FinishTime6747 remote_copy_recover multi.1.r96 active 2/4 0/1 2009-06-29 14:52:43 PDT Detailed status: 2009-06-29 14:52:43 2009-06-29 14:52:43 2009-06-29 14:52:44 secondary. 2009-06-29 14:52:44 promotions.
InForm OS Version 2.3.1 Remote Copy User’s Guide In the example above: ◆ Tasks are launched for each group that has already been failed over. ◆ Groups on InServA temporarily switch to secondary mode, thereby promoting the Remote Copy snapshots to bring InServA and InServC to the same starting point. Once completed, Remote Copy is started between InServA and InServB and synchronization of the two system’s groups occurs.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServA: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServB 58 FC ready 2FF70002AC0000C3 mirror_config InServC 59 IP ready mirror_config Link Information Target InServB InServB InServC InServC 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.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC failed 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP ready mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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.
InForm OS Version 2.3.1 Remote Copy User’s Guide CAUTION: The group must be started at the time the setrcopygroup restore command is issued. Issue the showrcopy groups command to confirm the group has been started. If it has not been started then issue the startrcopygroup command and wait for any synchronizations that are started to complete before issuing the setrcopygroup restore command.
Remote Copy User’s Guide InForm OS Version 2.3.1 In the example above: ◆ Tasks are started for each group that has already been recovered. ◆ A final synchronization is started from InServC to InServB and from InServC to InServA to ensure that InServA and InServB have the most recent data. ◆ Groups are then stopped and the primary volumes on InServC are switched to secondary volumes and secondary volumes on InServA are switched to primary volumes.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServA: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServB 58 FC ready 2FF70002AC0000C3 mirror_config InServC 59 IP ready mirror_config Link Information Target InServB InServB InServC InServC 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.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServB: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 46 FC ready 2FF70002AC000060 mirror_config InServC 47 IP ready mirror_config Link Information Target InServA InServA InServC InServC 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.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServC: # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 42 IP ready mirror_config InServB 44 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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.
Remote Copy User’s Guide InForm OS Version 2.3.1 C.6 Synchronous Long Distance Remote Copy for Data Migration As stated in Synchronous Long Distance Configuration on page 2.12, Synchronous Long Distance Remote Copy can also be used for data migration during the replacement of an InServ Storage Server in an existing Remote Copy configuration. The following data migration example shows the use of Synchronous Long Distance Remote Copy in synchronous mode.
InForm OS Version 2.3.
Remote Copy User’s Guide ■ InForm OS Version 2.3.
InForm OS Version 2.3.1 A) Remote Copy User’s Guide InServA B) InServC InServC InServA Group1 Asynchronous Periodic Synchronous InServB InServB C) InServA D) InServC InServA InServC Synchronous Asynchronous Periodic InServB InServB Figure C-11. Synchronous Long Distance Remote Copy Data Migration - Synchronous Mode NOTE: Prior to beginning data migration, the replacement server, InServC, should already be set up for Remote Copy with targets to both InServA and InServB.
Remote Copy User’s Guide 1 InForm OS Version 2.3.1 Create a new target (InServC) for InServA by issuing the creatercopytarget IP : command on InServA. # creatercopytarget InServC IP 0:3:1:10.100.33.63 1:3:1:10.101.33.63 2 Issue the showrcopy command on InServA to verify InServC has been created.
InForm OS Version 2.3.1 4 Remote Copy User’s Guide Issue the showrcopy command on InServB to verify InServC has been created. # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 61 FC ready 2FF70002AC000060 mirror_config InServC 62 IP ready mirror_config Link Information Target InServA InServA InServC InServC receive receive receive receive ...
Remote Copy User’s Guide 5 InForm OS Version 2.3.1 Issue the showrcopy command on InServC and verify InServA and InServB are targets. # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 60 IP ready mirror_config InServB 61 IP ready mirror_config Link Information Target InServA InServA InServB InServB receive receive 6 Node 0 1 0 1 0 1 Address 10.100.33.96 10.101.33.96 10.100.33.195 10.101.33.
InForm OS Version 2.3.1 7 Remote Copy User’s Guide Issue the showrcopy groups command on InServA and verify that InServC has been added as a target for Group1. # showrcopy groups Remote Copy System Information Status: Started, Normal Group Information Name Group1 LocalVV testvv.0 testvv.1 testvv.2 testvv.3 testvv.4 Target InServB ID 1 2 3 4 5 Status Started RemoteVV testvv.0 testvv.1 testvv.2 testvv.3 testvv.
Remote Copy User’s Guide InForm OS Version 2.3.1 10 When production is switched to InServC all host I/O should be stopped and a final synchronization initiated on InServA using the syncrcopy command. # syncrcopy Group1 Synchronization request issued for group Group1 task ID = ... 11 When the final synchronization has completed, stop Group1 on InServA by issuing the stoprcopygroup command on InServA.
InForm OS Version 2.3.1 ◆ Remote Copy User’s Guide On InServB: # showrcopy groups Remote Copy System Information Status: Started, Normal Group Information Name Group1.r96 LocalVV testvv.0 testvv.1 testvv.2 testvv.3 testvv.4 Target InServA ID 200 201 202 203 204 Status Stopped RemoteVV testvv.0 testvv.1 testvv.2 testvv.3 testvv.
Remote Copy User’s Guide ◆ InForm OS Version 2.3.1 On InServC: # showrcopy groups Remote Copy System Information Status: Started, Normal Group Information C.106 Name Group1.r96 LocalVV testvv.0 testvv.1 testvv.2 testvv.3 testvv.4 Target InServA ID 1 2 3 4 5 Status Stopped RemoteVV testvv.0 testvv.1 testvv.2 testvv.3 testvv.
InForm OS Version 2.3.1 Remote Copy User’s Guide 14 Begin failover on InServC to change the secondary volume group (Group1.r96) to the primary volume group by issuing the setrcopygroup failover command on InServC. # setrcopygroup failover Group1.
Remote Copy User’s Guide InForm OS Version 2.3.1 15 Issue the showrcopy command on InServC to verify that Group1.r96 is displayed with the role of Primary-Rev. # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServA 60 IP ready mirror_config InServB 61 IP ready mirror_config Link Information Target InServA InServA InServB InServB 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.
InForm OS Version 2.3.1 Remote Copy User’s Guide 16 Remove InServA’s target and group affiliations from InServC by issuing the removercopytarget -cleargroups command. # removercopytarget -cleargroups InServA 17 Issue the showrcopy command on InServC to verify that InServA has been removed as a target.
Remote Copy User’s Guide InForm OS Version 2.3.1 19 Issue the showrcopy command on InServB to verify that InServA has been removed as a target. # showrcopy Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Options Policy InServC 62 IP ready mirror_config Link Information Target InServC InServC receive receive ... Node 0:4:1 1:4:1 0:4:1 1:4:1 Address 10.100.33.63 10.101.33.
InForm OS Version 2.3.1 Remote Copy User’s Guide This changes the role of the group on InServC to be permanently marked Primary, rather than Primary-Rev. 21 Switch the mode of InServC to synchronous by issuing the setrcopygroup mode sync command. # setrcopygroup mode sync InServB Group1.r96 22 Start Group1.r96 on InServC. # startrcopygroup Group1.r96 23 On InServC, issue the showrcopy groups command and verify that Group1.r96 is now primary and its mode is synchronous.
Remote Copy User’s Guide C.112 Synchronous Long Distance Remote Copy for Data Migration InForm OS Version 2.3.
InForm OS Version 2.3.1 Remote Copy User’s Guide D Comparing MTU Speeds Depending on workload, you might see as much as a 50 percent increase by using a 9000 byte MTU setting as opposed to a 1500 byte MTU setting.
Remote Copy User’s Guide b InForm OS Version 2.3.1 For both the primary and backup servers, create a 20 GB test virtual volume that belongs to the CPG created in step 2 On InServ1: # createvv 20g On InServ2: # createvv 20g where is the name of the virtual volume to be created. c Create a synchronous volume group on the primary server and assign the test volume to that group.
InForm OS Version 2.3.1 5 Remote Copy User’s Guide Stop the Remote Copy operation on the group. The -nosnap option in the following example prevents Remote Copy from taking a snapshot on the primary storage server: On InServ1: # stoprcopygroup -nosnap 6 Set the MTU to 9000 bytes for each port on both the primary and backup storage servers. # controlport rcip mtu 9000 Remote Copy interface change successful. where is the port location given in Node:Slot:Port format.
Remote Copy User’s Guide InForm OS Version 2.3.1 10 Remove the test CPG, volume group, and virtual volume from both the primary and backup servers as follows: On InServ1: # removercopygroup # removevv -ld Removing Removing Removing Removing Removing vv ld ld ld ld .usr.3 .usr.2 .usr.1 .usr.0 # removecpg -f -ld Removing CPG Removing ld .usr.3 Removing ld .usr.2 Removing ld .usr.
InForm OS Version 2.3.1 Remote Copy User’s Guide Index 1-to-N configurations restrictions 2.43 1-to-N unidirectional disaster recovery asynchronous periodic mode C.27 3PAR InForm operating environment 1.2 InServ Storage Servers 1.2 Remote Copy License 2.3 Thin Provisioning 2.33, 3.3 A add target to group B.5 virtual volume to group B.7 admitrcopy command 3.23, 3.27 admitrcopylink command 4.12, 5.5, B.3 admitrcopytarget command 4.12, B.5 admitrcopyvv command 3.23, 4.12, B.7 alerts 2.36, 2.
Remote Copy User’s Guide controlport 3.8, 3.9, 3.10, 3.11, 3.12, 3.13, 3.14, 4.12, 5.3, B.9 creatercopygroup 3.22, 4.12, B.7, B.18, B.19, B.82 creatercopytarget 4.12, 5.5, B.3, B.4, B.5, B.7, B.18, B.20, B.23, B.44 dismissrcopylink 4.12, B.23 dismissrcopytarget 4.12, B.25 dismissrcopyvv 4.12, B.27, B.28 growvv B.29 promotesv 2.32 removercopygroup 4.12, B.31 removercopytarget 4.13, B.33 removetask 4.8 setrcopygroup 2.28, 2.40, 4.2, 4.3, 4.4, 4.5, B.18, C.9, C.10, C.13, C.20, C.24, C.32, C.
InForm OS Version 2.3.1 display configuration details B.57 statistics for group B.74 documentation, related 1.2 double link failure 2.36 E enable Remote Copy B.66 error handling 2.35 F fail_wrt_on_err group policy 4.4 fail_wrt_on_err policy 2.37, 4.4 failures active storage server 2.38 backup storage server 2.38 command failure due to no mirror config C.8, C.19, C.31 complete network failure 2.36 double link 2.36 newtwork failure (disaster recovery) C.8, C.19, C.31 primary storage server 2.
Remote Copy User’s Guide Gigabit Ethernet (GigE) 2.19 receiving links 2.18 sending 2.17 loss of sync between volume groups 4.4 M maintaining write consistency 2.6 managing Remote Copy 4.2 manual resynchronization 2.24, 2.29, 4.5 maximum transmission unit (MTU) 5.2 comparing speeds D.1 increasing 3.11, 3.13 verifying network support 3.13 metering data sent over Remote Copy links 2.30 minimum synchronization period 2.28 mirror_config policy 2.3 multiple physical links 2.19 I/O statistics B.
InForm OS Version 2.3.1 reversing active and backup server designations C.32 reversing primary and backup server designations 4.2, C.9, C.21 reversing volume group primary and secondary designations 4.2 setting the interface 3.9, 3.14 stop B.79 Synchronous Long Distance overview 2.12 Synchronous Long Distance Remote Copy setup 3.28 Synchronous Long Distance restrictions 2.45 target 2.15 policies 2.3 terms 2.3 turn on for group B.67 unidirectional 2.8 verifying connectivity 3.10 virtual volumes 2.
Remote Copy User’s Guide statport command statport -rcip D.1 statrcopy command 4.2, B.74 stop Remote Copy 4.11 Remote Copy operation B.79, D.3 stoprcopy command 4.11, B.59 stoprcopygroup command B.31, B.79 to B.80 supported number of volumes in a group 2.21 switches Gigabit Ethernet 2.19 Synced 2.40 Synced-stale 2.40 synchronization concurrent synchronization limit 2.29, B.61 initiating 2.25 period 2.28 configuring 2.28 minimum length 2.28 Synchronous Long Distance Remote Copy 2.12 data migration C.
InForm OS Version 2.3.1 drawbacks 2.21 loss of sync between 4.4 maximum supported number of volumes 2.21 preventing volume groups from becoming out of sync 4.4 primary 2.4 secondary 2.4 setting policies 4.4 Remote Copy User’s Guide types 2.22 W waittask command 4.8 write errors 2.38 latency 2.24 IX.
Remote Copy User’s Guide IX.8 InForm OS Version 2.3.
InForm OS Version 2.3.1 Remote Copy User’s Guide Revision History Release level Revision summary 320-200175 Rev A First release of this manual to support product release 2.3.1. October 2009 Revision History RH.
Remote Copy User’s Guide RH.2 InForm OS Version 2.3.
