Hp 3PAR Operating System Software Manuale Utente

HP 3PAR Remote Copy® 3.1.1 SoftwareUser’s GuideThis guide is for System and Storage Administrators who monitor and direct system configurations and re

IntroductionThis guide provides the information you need to configure and use HP 3PAR Remote Copy Software.Remote Copy allows you to copy virtual volu

Optimizing Synchronization Speed over DistancesAs the physical distance increases between the systems in the Remote Copy pair, latency canincrease and

Distribution of Host Writes over RCIP GigE LinksWhen copying data from the primary system to the backup system, Remote Copy uses all the RCIPGigE link

Part IV Recovering from DisasterSee:To recover and restore this configuration after theprimary system goes offline:“Disaster Recovery for 1-to-1 Confi

20 Disaster Recovery for 1-to-1 ConfigurationsBefore you begin disaster recovery:Figure 24 (page 104)1. Acquaint yourself with the example Remote Copy

Figure 24 Example Bidirectional 1-to-1 Remote Copy ConfigurationExample backup systemExample primary systemSystem2System1System name1196System IDSyste

Remote Copy System InformationStatus: Started, NormalTarget InformationName ID Type Status Options Policy System2 9 IP ready mirr

localvv.0 385 remotevv.0 423 Syncing (20%) NA localvv.1 386 remotevv.1 424 Syncing (20%) NA System Information during Failo

Recovering from DisasterFailover1. Reverse the role of all volume groups on the system that is still in normal operation (the failoversystem). On the

2. Verify the reversal of volume group roles.a. Issue the showrcopy command on the failover system (for example, System2).b. In the Group Information

a. Issue the showrcopy command on the failover system (System2).b. Verify that:• the Status of the target (recovered) system is ready• the Status of a

NOTE: The InServ Storage Server has been rebranded as HP 3PAR Storage System. There areinstances in this document where screenshots and/or menu items

Link InformationTarget Node Address Status OptionsSystem2 0 10.100.33.11 Up System2 1 10.101.33.11 Up receive 0 1

6. Verify that failback is complete and the natural direction of data flow is restored:a. Issue the showrcopy command on the failover system (System2)

d. Verify that the Role of the primary volume group is Primary.For example, the showrcopy output on System1 shows that group sync_group_1 iscorrectly

21 Disaster Recovery for N-to-1 ConfigurationsBefore you begin disaster recovery:Figure 25 (page 113)1. Acquaint yourself with the example Remote Copy

Example backup systemExample second primarysystemExample first primary systemVirtual volumes and volumegroups:• Two corresponding VVs:remotevv.0 andre

First Primary System (System2)When all systems are up, the showrcopy command output on one of the primary systems (forexample, System2) looks like the

System Information during FailoverSynchronous ModeWhen a failure occurs on systems with synchronous mode volume groups such that all links betweenthe

Recovering from DisasterFailover1. Reverse the role of all volume groups on the system that is still in normal operation (the failoversystem). On the

2. Verify the reversal of volume group roles.a. Issue the showrcopy command on the failover system (System1).b. In the Group Information area, check t

2. When both systems in the Remote Copy pair are ready to resume normal operation, reversethe natural direction of data flow and resynchronize the sys

Part I Setting the Foundation for Remote Copy“Planning Your Remote Copy Setup Strategy” (page 13)1. Plan your setup strategy.“Deciding on a Remote Cop

c. Issue the showrcopy command on the recovered system (System2).d. Verify that:• the Status of the target system (System1) is ready• the Status of al

• <group_name> - Volume group that should be started (for example, periodic_group_1)SolutionProblemIf the volume groups are notstarted:1. On the

6. Verify that failback is complete and the natural direction of data flow is restored:a. Issue the showrcopy command on the failover system (System1)

d. Verify that the Role of the primary volume groups is Primary.For example, the showrcopy output on System2 shows that group periodic_group_1 iscorre

22 Disaster Recovery for 1-to-N ConfigurationsBefore you begin disaster recovery:Figure 26 (page 124)1. Acquaint yourself with the example Remote Copy

Example second backupsystemExample first backup systemExample primary systemVirtual volumes and volumegroups:• Two corresponding VVs:remotevv.0 andrem

First Backup System (System2)When all systems are up, the showrcopy command output on one of the backup systems (forexample, System2) looks like the o

System Information during FailoverSynchronous ModeWhen a failure occurs on systems with synchronous mode volume groups such that all links betweenthe

Recovering from DisasterFailover1. Reverse the role of all volume groups on the system that is still in normal operation (the failoversystem). On the

Recovery1. Recover the failed system.2. When both systems in the Remote Copy pair are ready to resume normal operation, reversethe natural direction o

1 Planning Your Remote Copy Setup Strategy“Setup Instructions and Resources” (page 13)1. Decide on a setup methodology.“Remote Copy System Locations”

d. Verify that:• the Status of the target system (System2) is ready• the Status of all sending links is Up• the Role of the synchronizing volume group

4. Verify that the volume groups are started. On the recovered system (System1), enter:# showrcopy groups <group_name>• <group_name> - Vol

6. Verify that failback is complete and the natural direction of data flow is restored:a. Issue the showrcopy command on the failover system (System2)

Name Target Status Role Mode Optionsperiodic_group_1 System2 Started Primary Periodic Last-Sync Thu De

23 Disaster Recovery for Synchronous Long DistanceBefore you begin disaster recovery:Figure 27 (page 135)1. Acquaint yourself with the example Remote

Figure 27 Example Synchronous Long Distance Remote Copy ConfigurationExample asynchronousperiodic backup systemExample synchronousbackup systemExample

Target Node Address Status OptionsSystemB 0:2:1 20210002AC0000C3 Up SystemB 1:2:1 21210002AC0000C3 Up SystemC 0:3:1 1

testvv.0 200 testvv.0 100 Synced NA testvv.1 201 testvv.1 101 Synced NA testvv.2 202 te

System Information during FailoverSynchronous ModeWhen a failure occurs on systems with synchronous mode volume groups such that all links betweenthe

If the primary system (for example, SystemA) becomes unavailable, the showrcopy output on theasynchronous periodic backup system (for example, SystemC

2 Deciding on a Remote Copy ConfigurationTo decide on the best Remote Copy configuration for yoursystem, review illustrations and descriptions of the

Failing Over to the Synchronous Backup SystemIf the primary system fails or is taken offline, you can failover the storage system to the synchronousba

Failover1. Reverse the role of all volume groups on the synchronous backup system (the failover system).On the failover system (for example, SystemB),

3. Verify the reversal of volume group roles.a. Issue the showrcopy command on the failover system (SystemB).b. In the Group Information area, check t

4. Verify that the asynchronous periodic backup system (SystemC) is now the backup system.a. Issue the showrcopy command on the asynchronous periodic

• <target_name> - Name of the target system with which to synchronize (SystemA)The setrcopygroup recover command:• Switches the volume groups on

b. Verify that for the target system (SystemA):• the Status of the target system is ready• the Status of primary system’s sending links (SystemA) is U

For example, the showrcopy output on SystemA looks like:# showrcopy Remote Copy System InformationStatus: Started, NormalTarget InformationName ID

Target Node Address Status OptionsSystemA 0 10.100.33.96 UpSystemA 1 10.101.33.96 UpSystemB 0 10.100.33.195 Up SystemB 1

CAUTION: The volume groups must be started before you continue to the next step and issuethe setrcopygroup restore command.5. Restore the natural dire

6. Verify that the Synchronous Long Distance setup is restored and operating normally.a. Issue showrcopy on the recovered system (SystemA) and verify

Figure 2 Example bidirectional 1-to-1 Remote CopyN-to-1 ConfigurationAn N-to-1 Remote Copy configuration is composed of multiple Remote Copy pairs. A

# showrcopy Remote Copy System InformationStatus: Started, NormalTarget InformationName ID Type Status Options Policy SystemA 46 FC

c. Issue showrcopy on the asynchronous periodic backup system (SystemC) and verify thatit is in the role of backup system.For example, SystemC looks l

Figure 29 Failing Over to the Asynchronous Periodic System with Data TransferFailover1. Reverse the role of all volume groups on the asynchronous peri

failover started with tasks: 6740root@xnodeeca5:~/bin# waittask -v 6740 Id Type Name Status Phase Step -------StartTime-------

3. Verify that the newer data is being pushed to the failover system.a. While Remote Copy progresses through the failover tasks, issue the showrcopy c

# showrcopy Remote Copy System InformationStatus: Started, NormalTarget InformationName ID Type Status Options Policy SystemA 42 IP failed

4. Verify the reversal of volume group roles.a. Issue the showrcopy command on the failover system (SystemC).b. In the Group Information area, check t

# showrcopy Remote Copy System InformationStatus: Started, NormalTarget InformationName ID Type Status Options Policy SystemA 46 FC

In this example, Remote Copy copies data from the virtual volumes in volume groupmulti.1.r96 on SystemC to multi.1 on SystemA.• Starts Remote Copy on

b. Verify that for the target system (SystemA):• the Status of the target system is ready• the Status of primary system’s sending links (SystemA) is U

Figure 3 N-to-1 Remote Copy1-to-N ConfigurationA 1-to-N Remote Copy configuration is composed of multiple Remote Copy pairs. The single primarystorage

Remote Copy System InformationStatus: Started, NormalTarget InformationName ID Type Status Options Policy SystemB 58 FC ready 2FF

f. Verify that:• the Status of the target system (SystemA) is ready• the Status of the primary system’s sending links (SystemA) is UpFor example, the

4. Verify that the volume groups are started. On the recovered system (SystemA), enter:# showrcopy groups <group_name>• <group_name> - Vol

SystemB.2009-06-29 14:56:56 PDT Waiting Waiting for synchronization of group multi.1.r96 to target SystemA to complete.2009-06-29 14:56:56 PDT Wa

6. Verify that the Synchronous Long Distance setup is restored and operating normally.a. Issue showrcopy on the recovered system (SystemA) and verify

# showrcopy Remote Copy System InformationStatus: Started, NormalTarget InformationName ID Type Status Options Policy SystemA 46 FC

c. Issue showrcopy on the asynchronous periodic backup system (SystemC) and verify thatit has resumed the role of backup system.For example, SystemC l

Failing Over to the Asynchronous Periodic Backup System (No DataTransfer)If the primary system fails or is taken offline, you can failover the storage

Failover1. Reverse the role of all volume groups on the asynchronous periodic backup system (the failoversystem). On the failover system (for example,

3. Verify the reversal of volume group roles.a. Issue the showrcopy command on the failover system (SystemC).b. In the Group Information area, check t

Figure 4 1-to-N Remote CopySynchronous Long Distance ConfigurationA Synchronous Long Distance Remote Copy configuration is composed of two Remote Copy

# showrcopy Remote Copy System InformationStatus: Started, NormalTarget InformationName ID Type Status Options Policy SystemA 46 FC

• <target_name> - Name of the target system with which to synchronize (SystemA)The setrcopygroup recover command:• Switches volume groups on the

multi.15909 rcpy.222.103.59.1 snp vcopy testvv.3 103 RO normal -- -- -- 1024 snapmulti.15915 rcpy.222.103.58 snp vcopy testvv.3 103 RO normal -- -- --

d. Verify that:• the Status of the target systems (SystemB and SystemC) is ready• the Status of all sending links is Up• the Role of the synchronizing

f. Verify that:• the Status of the target system (SystemA) is ready• the Status of the primary system’s sending links (SystemA) is UpFor example, the

4. Verify that the volume groups are started. On the recovered system (SystemA), enter:# showrcopy groups <group_name>• <group_name> - Vol

2009-06-29 14:56:56 PDT Waiting Waiting for synchronization of group multi.1.r96 to target SystemA to complete.2009-06-29 14:56:56 PDT Waiting

6. Verify that the Synchronous Long Distance setup is restored and operating normally.a. Issue showrcopy on the recovered system (SystemA) and verify

# showrcopy Remote Copy System InformationStatus: Started, NormalTarget InformationName ID Type Status Options Policy SystemA 46 FC

c. Issue showrcopy on the asynchronous periodic backup system (SystemC) and verify thatit has resumed the role of backup system.For example, SystemC l

1. Between the primary system and backup system that are physically closer to each other (andtherefore share a high bandwidth/low latency connection),

Part V Remote Copy ConceptsSee the following:For conceptual information on:“Remote Copy Pairs and Targets” (page 181)Remote Copy pairs and targets, ta

24 Remote Copy Pairs and TargetsSee:For more information on:“Remote Copy Pairs” (page 181)The foundational Remote Copy system relationship“Overview of

• This relationship between target definitions and Remote Copy system pairs is true for all validRemote Copy configurations (unidirectional, bidirecti

Specifically, Remote Copy replicates data from the primary volume groups, which you name andwhich reside on the primary system, to the secondary volum

25 Remote Copy LinksSee:For more information on:“Sending Links” (page 184)Rules for creating sending links“Receiving Links” (page 186)How Remote Copy

Figure 32 Supported Sending Link ConnectionsLinks per Remote Copy PairWhen you set up Remote Copy links between a Remote Copy pair, you must create on

Receiving LinksRemote Copy uses receiving links to:• listen for Remote Copy data and commands from the target system in the Remote Copy pair• read the

26 Virtual Volumes and CPGsFor more information, see:To create virtual volumes for Remote Copy:1. Create a Common Provisioning Group (CPG).• “Common P

Basic Information about CPGsCAUTION: For a complete list of warnings and cautions regarding CPGs, refer to the HP 3PARInForm OS Concepts Guide.• CPGs

Rules for Creating Remote Copy Virtual Volumes• The primary and secondary virtual volumes to be linked (for example, vv1 and vv1_remote)must be the sa

Figure 6 Synchronous Long Distance Remote Copy - One Backup System FailureIn this example, when System2 is restored, Remote Copy transfers data from S

27 Volume GroupsSee:For more information on:“Why Use Volume Groups” (page 190)What volume groups are and why Remote Copy uses them“How Volume Groups W

How Volume Groups WorkRemote Copy functions as if the virtual volumes in a volume group are related and therefore ensuresthat the data in the virtual

For more information about snapshot creation, see “Remote Copy Snapshots” (page 203).How Volume Groups Are Organized on the Remote Copy PairPrimary vo

Figure 35 Mapping of Volumes between Bidirectional Primary and Backup SystemsLinking Virtual Volumes in Volume Groups 193

28 Volume Group ModesSee:For information on:“Overview of Volume Group Modes” (page 194)Comparison of the two types of modes“Synchronous Mode” (page 19

6. After the active cache update on the primary system is complete and the primary systemreceives the backup system’s acknowledgement, Remote Copy sen

5. The primary and backup systems are resynchronized periodically:• automatically: according to the schedule specified by the setrcopygroup command• m

29 Synchronization Types and LimitsSee:For more information on:“Types of Synchronization” (page 197)The two types of synchronization Remote Copy perfo

To ensure volume group consistency, Remote Copy maintains all the snapshots for the secondaryasynchronous periodic volume group on the backup system u

4. saves the active snapshot, which enables Remote Copy to perform a fast resynchronizationlater [Figure 40 (page 200)]Figure 39 Full Synchronization

© Copyright 2011 Hewlett-Packard Development Company, L.P.Confidential computer software. Valid license from HP required for possession, use or copyin

Figure 7 Synchronous Long Distance Remote Copy - Primary System FailureIn this example, when System1 is restored, Remote Copy:• Transfers data from Sy

6. saves the newer snapshot for a future resynchronizationCAUTION: Because Remote Copy uses multiple snapshots during resynchronization, youmust ensur

Setting Up Resynchronization for Asynchronous Periodic ModeHow to Set the Synchronization PeriodFor Remote Copy to automatically resynchronize asynchr

Resynchronization• To resynchronize synchronous mode volume groups, Remote Copy copies the I/O directlyfrom the primary base volume.For more informati

30 Remote Copy SnapshotsSee:For information on:“Why Use Snapshots” (page 203)What snapshots are and why Remote Copy uses them“Volume Space Considerati

Snapshots in Synchronous ModeIn synchronous mode, Remote Copy creates snapshots only when:• an error occurs• disaster recovery is in process• a volume

creates snapshots of all the secondary virtual volumes that were previously synchronizeda.b. resynchronizes the secondary virtual volume by sending on

Snapshots and Resynchronization FailureIf the primary system fails during resynchronization, Remote Copy uses the snapshot taken on thebackup system t

31 Error HandlingSee:For more information on:“Timeouts for Remote Copy Failure” (page 207)The timeout periods per type of failure and volume groupmode

Failure of All LinksWhen all links between storage systems in a Remote Copy pair fail, the two systems cannotcommunicate. After failure of all links:•

Link Failure and Asynchronous Periodic Volume GroupsFor asynchronous periodic volume groups, when all links between a Remote Copy pair fail:• Remote C

3 Choosing Network Connections1. Review the possible network connections.• “IP Networks” (page 21)• “Fibre Channel Networks” (page 22)• “Fibre Channel

For more information on volume group modes, see “Volume Group Modes” (page 194).Write Errors and Synchronous Volume GroupsFor synchronous volume group

If this type of read fails, Remote Copy:• cancels the synchronization process• marks the secondary volume as NotSynced• does not stop the volume group

Part VI AppendicesSee the following:For information on:“Quick Setup Guide” (page 213)Quick setup steps for RCIP, RCFC, and Remote Copyconfigurations“Q

A Quick Setup GuideSee:To set up:“Quick Setup: RCIP Transport Layer” (page 214)Transport layer for Remote Copy over IP (RCIP)“Quick Setup: RCFC Transp

Quick Setup: RCIP Transport LayerTable 2 Quick Setup Steps for RCIPBackup SystemPrimary SystemReferenceStepcontrolport rcip addr[-f] <port_IP>&l

Quick Setup: RCFC Transport LayerTable 3 Quick Setup Steps for RCFCBackup SystemPrimary SystemReferenceStepcontrolport configrcfc -ct point -f<N:S:

Quick Setup: Unidirectional Remote CopyTable 4 Quick Setup Steps for Unidirectional Pairs: 1-to-1, N-to-1, and 1-to-N ConfigurationsBackup SystemPrima

Table 4 Quick Setup Steps for Unidirectional Pairs: 1-to-1, N-to-1, and 1-to-N Configurations(continued)Backup SystemPrimary SystemReferenceStepPrimar

Quick Setup: Synchronous Long Distance Remote CopyTable 6 Quick Setup Steps for Synchronous Long Distance ConfigurationsPeriodic SystemSync SystemPrim

Table 6 Quick Setup Steps for Synchronous Long Distance Configurations (continued)Periodic SystemSync SystemPrimary SystemReferenceStep<periodic_ta

Fibre Channel Networks• Remote Copy over Fibre Channel (RCFC) can only be set up on storage systems thatcommunicate over Fibre Channel Storage Area Ne

B Quick Disaster Recovery GuideSee:To recover from primary system downtime for:“Quick Recovery: 1-to-1, N-to-1, and 1-to-N Configurations”(page 220)1-

Quick Recovery: Synchronous Long Distance ConfigurationsTable 8 Quick Recovery Steps for Synchronous Long Distance ConfigurationsBackup SystemFailed/R

C About the Remote Copy CommandsSee this command:In order to:admitrcopylinkCreate a link to a target systemadmitrcopytargetAdd a target system to an H

NOTE: See also showvv -rcopy in the HP 3PAR Inform OS CLI Reference.Issuing Remote Copy Commands• Enter Remote Copy commands using the HP 3PAR Command

D The Remote Copy Commands224 The Remote Copy Commands

admitrcopylinkNAMEadmitrcopylink -- The admitrcopylink command adds one or more links (connections) to aRemote Copy target system.SYNTAX• For Remote C

• For IP targets this list is made up of pairs composed of the node of the Ethernet port on thelocal system and an IP address of the peer port on the

admitrcopytargetNAMEadmitrcopytarget -- The admitrcopytarget command adds a target to a Remote Copyvolume group.SYNTAXadmitrcopytarget <target_name

admitrcopyvvNAMEadmitrcopyvv -- The admitrcopyvv command adds an existing virtual volume to an existingRemote Copy volume group.SYNTAXadmitrcopyvv <

In the following example, the admitrcopyvv command adds all volumes beginning with tpvvto the primary volume group Group1. At the same time, it adds t

4 Considering Requirements and Restrictions1. Review the general considerations for all configurations.• “General Requirements” (page 23)• “General Sy

checkrclinkNAMEcheckrclink -- The checkrclink command performs a connectivity, latency, and throughputtest between two connected Systems.SYNTAX• chec

...============================================================TEST SUMMARY from 0:0:1 -> 10.100.18.164Test Started: Wed Aug 10 10:34:15 PST 20

controlportNAMEcontrolport -- The controlport command controls all aspects of a Fibre Channel or RemoteCopy port, including the port’s connection type

offlineHolds the specified port offline indefinitely. Issue controlport rst to bring the port backonline.lipSpecifies that a Loop Initialization Primi

rcip pingPerforms a ping from the specified interface to the specified address. Only for RCIP ports. See“SPECIFIERS” (page 235) for parameters require

-unique_nwwn enable|disableEnable or disable the use of a unique node WWN on the specified portSPECIFIERS<ctval>Specifies the connection paramet

RESTRICTIONS• See the HP 3PAR InForm OS CLI Reference for a complete list of restrictions.• The controlport rcip addr command is only allowed for node

• The ct, cl2, or rate subcommands automatically reset the port for the changes to takeeffect.• Issue the showport command with either the -i or -par

creatercopygroupNAMEcreatercopygroup -- The creatercopygroup command creates a Remote Copy volumegroup.SYNTAXcreatercopygroup [options] <group_name

mirror_config policy is set and the group is a secondary group, then this command willfail.• The maximum length of the group is 22 characters if the m

General Software Restrictions• Remote Copy does not support self-mirroring configurations.In other words, Remote Copy cannot use a storage system to r

creatercopytargetNAMEcreatercopytarget -- The creatercopytarget command creates a Remote Copy targetdefinition.SYNTAXThe syntax for the creatercopytar

The following example creates a primary target definition named System1 on the backup system,where the node numbers of the backup system’s Ethernet po

dismissrcopylinkNAMEdismissrcopylink -- The dismissrcopylink command removes one or more links(connections) created with the admitrcopylink command to

dismissrcopytargetNAMEdismissrcopytarget -- The dismissrcopytarget command removes a Remote Copy targetfrom a Remote Copy volume group.SYNTAXdismissrc

dismissrcopyvvNAMEdismissrcopyvv -- The dismissrcopyvv command removes a virtual volume from a RemoteCopy volume group.SYNTAXdismissrcopyvv [option] [

growvvNAMEgrowvv -- The growvv command increases the size of a virtual volume.SYNTAXgrowvv <VV_name> <size>[g|G|t|T]AUTHORITYSuper, EditAn

histrcvvNAMEhistrcvv -- The histrcvv command shows a histogram of total Remote Copy service times andbackup system Remote Copy service times in a time

-timecols <fcol> <lcol>For the I/O time histogram, shows the columns from the first column (<fcol>) through the lastcolumn (<lcol

128 256testvv.2 multi.1 amp2 Sync 0 0 0 163 61 16 3 0 0 0 0 224 19 0 0 0 0 0 0 0testvv.3 multi.1 amp2 Sync 0 0 0 138 62

removercopygroupNAMEremovercopygroup -- The removercopygroup command removes a Remote Copy volumegroup or multiple Remote Copy groups that match a giv

• RCFC over IP network connections are only allowed for Remote Copy in asynchronous periodicmode.• The maximum delay times are as follows:RCIP - 150 s

NOTES• If the mirror_config policy is set for this group’s target system and the group is a primarygroup, then this command will be mirrored to the ta

removercopytargetNAMEremovercopytarget -- The removercopytarget command removes target designation froma Remote Copy system and removes all links affi

setrcopygroupNAMEsetrcopygroup -- The setrcopygroup command does the following:SYNTAXThe syntax for the setrcopygroup command can be one of the follow

–nopromoteThis option is only valid for the failover and reverse specifiers. When used with thereverse specifier, specifies that the synchronized snap

• over_per_alert - If a synchronization of a periodic Remote Copy group takes longerto complete than its synchronization period, an alert will be gene

• The period can be set only for groups whose mode is asynchronous periodic (seecreatercopygroup).• Do NOT use the reverse value of the <dr_operati

setrcopytargetNAMEsetrcopytarget -- The setrcopytarget command sets the name, policies, or throughputdefinition for the target’s links.SYNTAXThe synta

NOTE: The no_mirror_config specifier should only be used to allow recovery from anunusual error condition and only used after consulting your HP repre

a group to be created, or a volume to be added to a group, only on one side of the pair ifthe operation is interrupted by a network failure. In such c

setvvNAMEsetvv -- The setvv command changes the properties associated with a virtual volume. Use thesetvv command to modify volume names, volume polic

Figure 10 N-to-1 Maximum Supported Configuration• One of the Remote Copy pairs can be bidirectional. All others must be unidirectional.• You can use e

logical disks are removed from the CPG. This is permitted only when the existing snapshotlogical disks are exclusively used by the volumes specified i

-hpc <heads_per_cylinder>Defines the virtual volume geometry heads per cylinder value that is reported to the hosts thoughthe SCSI mode pages. T

showportNAMEshowport -- The showport command displays information about ports in the system.SYNTAXshowport [options] [-failed] [-sortcol <col>[,

-sortcol <col>[,<dir>][:<col>[,<dir>]...]Sorts command output based on column number (<col>). Columns are numbered from

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

showrcopyNAMEshowrcopy -- The showrcopy command displays details of the Remote Copy configuration. Theshowrcopy command also displays the group’s doma

receive 0 10.100.33.11 Up receive 1 10.101.33.11 Up Group InformationName Target Status Role Mode

Name Target Status Role Mode Optionslisa bf_mirror Started Primary Periodic Last-Sync Tue Jul 18 14:09:44 PDT 200

might notice that 10 volumes do not start synchronizing until the first 20 have completed. Thiscan be seen by monitoring the Sync% column of the showr

showrctransportNAMEshowrctransport -- The showrctransport command shows status and information aboutend-to-end transport for Remote Copy in the system

Figure 11 1-to-N Maximum Supported Configuration• One of the Remote Copy pairs can be bidirectional. All others must be unidirectional.• You can use b

The following example displays status and information about the end-to-end transport for RCIPports:# showrctransport -rcipN:S:P State HwAddr

NOTESNone.271

startrcopyNAMEstartrcopy -- The startrcopy command enables Remote Copy.SYNTAXstartrcopyAUTHORITYSuper, EditAny role granted the rcopy_start right.NOTE

startrcopygroupNAMEstartrcopygroup -- The startrcopygroup command turns on Remote Copy for the specifiedRemote Copy volume group.SYNTAXstartrcopygroup

added to existing asynchronous periodic groups their first sync occurs the next time the entiregroup synchronizes.• You must enter this command on the

statportNAMEstatport -- The statport command displays read and write (I/O) statistics for ports.SYNTAXstatport [options <arg>]|-rcfc|-rcipAUTHOR

–sortcol <col>[,<dir>][:<col>[,<dir>]...]Sorts command output based on column number <col>. Columns are numbered from le

0:0:2 Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0 0:2:1 Data t 0 0 0 0 0 0 0.0 0.0 0.0 0.0 0

statrcopyNAMEstatrcopy -- The statrcopy command displays statistics for Remote Copy volume groups.SYNTAXstatrcopy [options <arg>]AUTHORITYAny ro

Press the enter key to stop...The columns in this example provide the following information:• Target. The system name of the actual link process that

◦ The node set up in synchronous mode must use Fibre Channel (RCFC), and the node setup in asynchronous periodic mode must use IP links (RCIP).◦ RCFC

statrcvvNAMEstatrcvv -- The statrcvv command displays statistics for Remote Copy volumes in a timedloop.SYNTAXstatrcvv [options <arg>] [<VV_n

–sortcol <col>[,<dir>][:<col>[,<dir>]...]Sorts command output based on column number (<col>). Columns are numbered from

EXAMPLESThe following example shows statistics for all synchronous Remote Copy volumes: cli% statrcvv -sync 09:48:45 03/30/10 I/O

• KBytes per second Max. The maximum number of KB per second.• Svt ms Cur. The current Remote Copy service time in milliseconds.• Svt ms Avg. The aver

stoprcopyNAMEstoprcopy -- The stoprcopy command disables the Remote Copy functionality for any startedRemote Copy volume groups.SYNTAXstoprcopy [optio

stoprcopygroupNAMEstoprcopygroup -- The stoprcopygroup command stops the Remote Copy functionality forthe specified Remote Copy volume group.SYNTAXsto

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

syncrcopyNAMEsyncrcopy -- The syncrcopy command manually synchronizes Remote Copy volume groups.SYNTAXsyncrcopy [options <arg>] <group_name&g

The following example specifies that all Remote Copy volume groups that start with the nametestgroup should be synchronized with their corresponding s

E Remote Copy and Other FeaturesSee:For more information on:“Remote Copy and Virtual Domains” (page 289)Virtual domains“Remote Copy Functionality Unav

5 Gathering Setup Information1. Contact your network administrator to obtain:• IP addresses or 64-bit World Wide Name (WWN) address information for th

IndexSymbols1-to-1 Remote Copyillustration, 43setup, 43Aadmitrcopylink command, 215alerts, 208asynchronous periodic modehow Remote Copy operates, 195r

minimum synchronization period, 201NN-to-1 Remote Copyrestrictions, 25natural direction of data flow, 182new consistency groups, 197notes and cautions

volume groupsconfiguring the synchronization period, 201naming, 191reasons to use, 190rules for forming, 191, 203Wwriteerrors, 209latency, 195292 Inde

ContentsIntroduction...10Related Documentation...

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

RCIP Additional Remote Copy Pairs WorksheetFigure 14 Network and Remote Copy Over IP Setup Information (Additional Systems)RCIP Additional Remote Copy

RCFC Remote Copy Pair WorksheetFigure 15 Network and Remote Copy Over Fibre Channel Setup Information32 Gathering Setup Information

6 Setting the Transport LayerFollow the steps for your chosen transport layer.• “Setting Up Remote Copy over IP” (page 33)• “Setting Up Remote Copy ov

2. Enter the following command for an Ethernet port on one Remote Copy system:# controlport rcip addr <port_IP> <netmask> <N:S:P>• &

5. Verify that the Gateway column displays the correct gateway IP address:N:S:P State ---HwAddr--- IPAddr Netmask Gateway MTU Rate D

2. Issue this command once for each interface on each system in the configuration.NOTE: Because of the spanning tree protocol and MAC address learning

4. Enter the following command on the first target system in the Remote Copy pair (in other words,on the system on which you issued the startserver co

4. Enter the controlport rcip ping command for each interface on each system in theconfiguration.NOTE: Because of the spanning tree protocol and MAC a

Setting Up Dedicated Node Pairs for RCFC• Verify that each Fibre Channel interface on each node on the primary Remote Copy systemconnects to a dedicat

Checking Link Throughput and Latency...40Setting Up RCFC over an IP Network.

For example:N:S:P Peer_Node_WWN Peer_Port_WWN State3:2:1 2FF70002AC00005F 23410002AC00005F new1:4:1 2FF70002AC00005F 21510002AC00005F newSolutio

3. On the target system in the Remote Copy pair (e.g., System1), enter the following command:# checkrclink startclient <N:S:P> <dest_addr>

Part II Setting Up the Remote Copy ServersSee:To set up:“Setting Up 1-to-1 Remote Copy” (page 43)1-to-1 Remote Copy“Setting Up N-to-1 Remote Copy” (pa

7 Setting Up 1-to-1 Remote CopyTo set up 1-to-1 Remote Copy in a unidirectional configuration:“Considering Requirements and Restrictions” (page 23)1.

Figure 17 Example Unidirectional 1-to-1 Remote Copy ConfigurationExample backup systemExample primary systemSystem2System1System name125112System IDfo

8 Setting Up N-to-1 Remote Copy“Considering Requirements and Restrictions” (page 23)1. Verify that your setup plan meets the N-to-1requirements.Figure

Figure 18 Example N-to-1 ConfigurationExample Remote Copy Pair for N-to-1 SetupThe setup steps for each Remote Copy pair in the N-to-1 configuration r

Example backup systemExample primary systemIP address 172.16.2.11IP address 172.16.2.12One secondary virtual volume(vv1_remote)One virtual volume (vv1

2. Define a target on the primary storage system (for example, System1).For RCIP:# creatercopytarget <target_name> IP <N:S:P>:<link_IP_

2. Define a target on the backup system (for example, System2).For RCIP:# creatercopytarget <target_name> IP <N:S:P>:<link_IP_addr>&

15 Setting Volume Group Policies...89Automatically Restarting Volume Groups...

Target Node Address Status OptionsSystem1 0 10.100.24.108 UpSystem1 1 10.101.24.108 Upreceive 0 10.100.24.108 Upreceive 1 10.101.24

1. Set up a volume group on the primary storage system (for example, System1):# creatercopygroup <group_name> <target_name>:periodic• <

• <pattern> - Pattern of volume group names (for example, Group*)3. On the primary system (e.g., System1), add the pre-existing virtual volume(s

Deciding on an Initial Replication Method• Decide on the method to use to start replicating the data in the primary volume groups:◦ Direct replication

SolutionProblemRepeat from Step 1.If the initial synchronization fails:4. Repeat the steps in “Starting Initial Replication: Copying Data Directly fro

9 Setting Up 1-to-N Remote Copy“Considering Requirements and Restrictions” (page 23)1. Verify that your setup plan meets the 1-to-Nrequirements.Figure

10 Setting Up Synchronous Long Distance Remote Copy“Considering Requirements and Restrictions” (page 23)1. Verify that your setup plan meets the Synch

Figure 21 Example Synchronous Long Distance Remote Copy ConfigurationExample backup system 2Example backup system 1Example primary systemSystemCSystem

Local Setup(not connected to the FCSAN)SystemASystemBTarget systemRCFC links•• Node WWN:2FF70002AC0000C3Node WWN:2FF70002AC000060• •Node 0 WWN:2011000

Setting Up the Primary System1. Start Remote Copy on the primary storage system (for example, SystemA).# startrcopy2. Define the targets for the synch

22 Disaster Recovery for 1-to-N Configurations...124System Information during Normal Operation...

2. Define a target (for example, the primary system SystemA) on the backup system. On thebackup system (SystemB), enter:• For RCFC:# creatercopytarget

6. Define a second target system (for example, the synchronous backup system SystemB) for thecurrent backup system. On the current backup system (Syst

Link InformationTarget Node Address Status OptionsSystemA 0:2:1 20110002AC000060 Up SystemA 1:2:1 21320002AC000060 Up

1. Create a volume group on the primary system (for example, SystemA):# creatercopygroup <group_name> <target_name>:sync <target_name&g

2. On the primary system (SystemA), add the pre-existing virtual volume(s) to the newly createdvolume group. Enter either:# admitrcopyvv <VV_name&g

Starting Initial Replication: Copying Data Directly from Primary VolumeGroups1. Start replication from the primary volume group to the secondary volum

3. On all three systems, verify that the SyncStatus column in the Group Information area displaysSynced.Example showrcopy groups output on SystemA:Gro

11 Setting Up a Unidirectional Configuration“Considering Requirements and Restrictions” (page 23)1. Verify that your setup plan meets the Remote Copyr

Figure 22 Example Unidirectional Remote Copy PairExample backup systemExample primary systemSystem2System1System name125112System IDfour (only two sho

2. Define a target on the primary storage system (for example, System1).• For RCIP:# creatercopytarget <target_name> IP <N:S:P>:<link_I

Virtual Volumes Used with Remote Copy...188Thinly Provisioned Virtual Volume

2. Define a target on the backup system (for example, System2).• For RCIP:# creatercopytarget <target_name> IP <N:S:P>:<link_IP_addr>

Target Node Address Status OptionsSystem1 0 10.100.24.108 UpSystem1 1 10.101.24.108 Upreceive 0 10.100.24.108 Upreceive 1 10.101.24

1. Set up a volume group on the primary storage system (for example, System1):# creatercopygroup <group_name> <target_name>:<mode>•

• <pattern> - Pattern of volume group names (for example, Group*)3. On the primary system (for example, System1), add the pre-existing virtual v

Deciding on an Initial Replication Method• Decide on the method to use to start replicating the data in the primary volume groups:◦ Direct replication

SolutionProblemRepeat from step 1.If the initial synchronization fails:4. Repeat the steps in “Starting Initial Replication: Copying Data Directly fro

12 Setting Up a Bidirectional Configuration“Considering Requirements and Restrictions” (page 23)1. Verify that your setup plan meets the Remote Copyre

Figure 23 Example Bidirectional Remote Copy PairExample backup systemExample primary systemSystem1System2System name112125System IDSystem2System1Targe

volume groups on the new primary system (for example, System2) and copy them to the newbackup system (for example, System1).• If a unidirectional 1-to

• <period_value>s|m|h|d - Synchronization time period (time between start ofresynchronizations), followed by time unit: s (seconds), m (minutes)

Timeouts and Transient Network Problems...207Failure of a Single Link...

Deciding on an Initial Replication Method• Decide on the method to use to start replicating the data in the primary volume groups:◦ Direct replication

SolutionProblemRepeat from step 1.If the initial synchronization fails:4. Repeat the steps in “Starting Initial Replication: Copying Data Directly fro

13 Using Tape for Initial Synchronization and BackupFor the first data synchronization between systems, it can be faster to back up the primary volume

• <TID> - Internally assigned target ID• <x> - A system-assigned integer4. Verify that the snapshot belongs to the correct volume and is a

• <group_name> - Name of the primary volume group (for example, Group1)or:# setrcopygroup -pat <pattern>• <pattern> - Pattern of vol

Part III Managing Remote CopySee:For information on:“Viewing Remote Copy System Information” (page 86)Viewing configuration and synchronization detail

14 Viewing Remote Copy System InformationFor more information:Issue this command:To view information on:“About the Remote Copy Commands”(page 222)show

Remote Copy does not create a new task for each resynchronization of an asynchronous periodicvolume group. Instead, Remote Copy keeps the initial sync

NOTE: For Remote Copy synchronizations, the Finish Time column for a resynchronizationtask might not match the LastSync column in the showrcopy comman

15 Setting Volume Group PoliciesFor more information:Use this policy:To set volume groups to:“Automatically Restarting VolumeGroups” (page 89)auto_rec

showrcopy ...265showrctransport ...

◦ <pattern> - Pattern of volume group names (for example, Group*)If the volume groups stop for any kind of failure, you must use the startrcopyg

16 Performing Manual OperationsFor more information:Issue this command:To manually:“Changing the Remote Copy Mode fora Volume Group” (page 91)setrcopy

or:# setrcopygroup mode <mode_value> <target_name> -pat <pattern>• <pattern> - Pattern of volume group names (for example, Gro

◦ <pattern> - Pattern of volume group names (for example, Group*)While this command completes, Remote Copy makes changes as a result of host wri

Stopping and Starting Remote CopyTo stop Remote Copy temporarily:# stoprcopy -stopgroupsTo restart Remote Copy:# startrcopyRemoving Remote Copy Comple

17 Modifying Virtual VolumesFor more information:Issue this command:To:“Converting Standard Virtual Volumes”(page 95)setvv -snp_cpgConvert a virtual v

• <VV_name> - Name of the virtual volume you are growing.• <size> - Size (in multiples of 256 MB) to add to the virtual volume’s user spac

18 Limiting Throughput“Limiting Throughput for Asynchronous Periodic VolumeGroups” (page 97)To save on leased-line charges during synchronization,limi

Removing Throughput Limits1. Stop the volume groups.# stoprcopygroup <group_name>or:# stoprcopygroup -pat <pattern>• <pattern> - Pat

19 Optimizing Performance“Optimizing RCIP Throughput by Increasing MTU Size”(page 99)To optimize RCIP throughput, increase MTU size.“Avoiding RCIP Thr