Page 1 Mainframe Systems User Guide Abstract This guide describes and provides instructions for using HP StorageWorks P9000 Continuous Access Synchronous Software to configure and perform Continuous Access Synchronous operations on the HP StorageWorks P9500 disk array. The intended audience is a storage system administrator or authorized service provider with independent knowledge of HP StorageWorks P9000 disk arrays and the HP StorageWorks Remote Web Console.
Page 2 © Copyright 2010, 201 1 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 1 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Page 3: Table Of Contents
Contents 1 Continuous Access Synchronous Z overview...........8 How Continuous Access Synchronous Z works ................8 Typical components .........................9 Disk arrays..........................9 Main (MCU), remote (RCU) disk arrays.................10 Volume pairs .........................10 Data path ..........................11 Consistency groups ........................11 Interfaces ..........................11 Failover software ........................11 Error reporting communications ....................12 Overview of initial, update copy operations ................12 Initial copy ........................12 Update copy ........................12...
Page 4 Amount of bandwidth required....................36 Fibre Channel requirements....................36 Supported data path configurations..................37 Planning ports........................38 Port requirements......................39 Error reporting communications....................39 4 Sharing Continuous Access Synchronous Z volumes........40 Volume types that can be shared with Continuous Access Synchronous Z........40 Continuous Access Journal Z....................41 Business Copy Z........................42 Configurations with Business Copy Z S-VOLs.................42 Configurations with Business Copy Z T-VOLs................43...
Page 5 Delete Continuous Access Synchronous Z................70 Managing power-off for disk arrays and network devices.............70 General information......................70 Planned outage of the main disk array..................71 Planned outage of the remote disk array or data path.............71 Planned outage of the main and remote systems..............71 Miscellaneous maintenance.....................72 ICKDSF maintenance......................72 8 Data migration..................73...
Page 6 B Continuous Access Synchronous Z scripting..........103 Scripting overview........................103 Scripting syntax........................105 Syntax overview.......................105 Script file requirements......................106 Script symbols.........................106 Execute a script........................107 Delete script files........................108 Export script trace files......................108 Operation macro commands....................109 Create pairs........................110 Release pairs........................112 Suspend pairs.........................113 Resynchronize pairs......................114 Change pair options......................115 Start a pair........................116 Get pair status.........................116 Select devices........................117...
Page 7 Add SSID dialog box......................149 Usage Monitor window......................150 History window........................151 History window notes.......................152 Export operations history....................152 System Option window......................153 Glossary....................155 Index.......................157 Contents...
Page 8: Continuous Access Synchronous Z Overview
1 Continuous Access Synchronous Z overview Unless otherwise specified, the term P9000 in this guide refers to the following disk array: P9500 Disk Array The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer browser.
Page 9: Typical Components
To plan and implement a Continuous Access Synchronous Z installation, an understanding of its components is required. This is provided in the following sections. Typical components A typical configuration consists of the following elements. Many but not all require user set up. A P9500 system—on the local side connected to a host.
Page 10: Main (Mcu), Remote (Rcu) Disk Arrays
Main (MCU), remote (RCU) disk arrays The main disk array manages the M-VOL and the following operations: Host I/O operations to the M-VOL Initial copy and update copy operations between the M-VOL and R-VOL. Pair status and configuration information The remote disk array manages the R-VOL and the following operations: Remote copy operations issued by the main system Assists in managing pair status and configuration (for example, rejects write I/Os to the R-VOL).
Page 11: Data Path
specified for the R-VOL. Then, write I/O is allowed to the R-VOL while the pair is suspended. In this instance, R-VOL and M-VOL track maps keep track of differential data and are used to resynchronize the pair. Volumes on the local and remote systems must be defined and formatted prior to pairing. Data path Continuous Access Synchronous Z operations are carried out between local and remote disk arrays connected by a Fibre Channel interface.
Page 12: Error Reporting Communications
Continuous Access Synchronous Z does not provide host-failover functions. Use the failover software most suitable for your platform and requirements. Error reporting communications Error reporting communications (ERC) transfers information between host processors at the main and remote sites. It is a critical component of a disaster recovery effort. Overview of initial, update copy operations When you perform the initial copy operation, all the data in the M-VOL is copied into the R-VOL.
Page 13 Update copy has a higher priority than initial copy. However, if an initial copy is in progress when updates are sent by the host, the update copy must wait until the initial copy’s copy pace completes. For example, if the copy pace is 15 tracks, the update copy may wait up to 15 tracks (1 cylinder). Overview of initial, update copy operations...
Page 14: Requirements And Specifications
2 Requirements and specifications This chapter provides basic system requirements, along with specifications for BCM, PPRC, and other mainframe-related interfaces and functions. In addition to the information in this chapter, “Planning for Continuous Access Synchronous Z” (page 27) provides many specifications, recommendations, and restrictions for the elements of a Continuous Access Synchronous Z system that require attention before setting up and using Continuous Access Synchronous Z.
Page 15: Bcm Specifications
Table 2 General system requirements (continued) Item Requirement Logical paths Maximum of eight from main disk array to remote disk array. Logical paths are established for main and remote disk array CUs separately. Maximum number of logical paths allowed for a disk array is 32 (8 paths per remote system X 4 remote systems per main system).
Page 16 The following tables show the correspondence between the LINK parameters (ports) and (system adapter ID) values. For more information on BCM, see the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. Also see Table 6 (page 20) for corresponding PPRC functionality.
Page 17 Table 3 SAID values for PATH LINK (CL1) (continued) Package Port SAID Package Port SAID Package Port SAID Package Port SAID Local Local Local Local CL1-G X'0006' CL1-Q X'000E' (Add3) (Add7) CL3-G X'0026' CL3-Q X'002E' CL5-G X'0046' CL5-Q X'004E' CL7-G X'0066' CL7-Q X'006E'...
Page 18: Command Device
Table 4 SAID values for PATH LINK (CL2) (continued) Package Port SAID Package Port SAID Package Port SAID Package Port SAID Local Local Local Local CL2-G X'0016' CL2-Q X'001E' (Add3) (Add7) CL4-G X'0036' CL4-Q X'003E' CL6-G X'0056' CL6-Q X'005E' CL8-G X'0076' CL8-Q X'007E'...
Page 19: Pprc Specifications, Restrictions
PPRC specifications, restrictions Most Continuous Access Synchronous Z operations can be performed using PPRC TSO or ICKDSF PPRCOPY commands from the host system console. All P9500 systems support IBM PPRC host software functions. Continuous Access Synchronous Z operations performed with PPRC Using PPRC commands, you can perform the following operations: Create, suspend, resynchronize, and delete Continuous Access Synchronous Z pairs Suspend, resynchronize, and delete Continuous Access Synchronous Z consistency groups...
Page 20: Pprc, Bcm Command Comparison
PPRC Support = Yes ◦ Service SIM of Remote Copy = Not Report ◦ Initial copy priority, the CFW (cache fast write) Data option, and DFW (DASD fast write) to R-VOL option. If CESTPAIR is used to create a pair, the following values are used for these options.
Page 21: P/Das Support, Restrictions
Table 6 Corresponding PPRC, BCM commands (continued) PPRC command Parameter BCM command Support type CSUSPEND DEVN YKSUSPND config PRIM config config PRIMARY Not supported QUIESCE Not supported CDELPAIR DEVN YKDELETE config PRIM CRECOVER DEVN YKRECOVER config PRIM CQUERY DEVN YKQUERY config FORMAT/UNFORMAT Not supported...
Page 22: Gdps Support
Contact your HP account team for the latest information on P/DAS support. GDPS support Continuous Access Synchronous Z provides remote copy support for IBM’s Geographically Dispersed Parallel Sysplex® (GDPS) facility. GDPS is an IBM service for mirroring data and balancing workload on disk arrays spread across two or more sites up to 40 km (20 miles) apart.
Page 23 Table 7 SAID values for Link-path statistical Information (CL1) (continued) Package Port SAID Package Port SAID Package Port SAID Package Port SAID Local Local Local Local CL1-C X'0010' CL1-L X'0030' CL9-C X'0050' CL9-L X'0070' (Add1) (Add5) (DKA (DKA CL3-C X'001 1' CL3-L X'0031' CLB-C...
Page 24: Tpc-R Cooperation Support
Table 8 SAID values for Link-path statistical Information (CL2) (continued) Package Port SAID Package Port SAID Package Port SAID Package Port SAID Local Local Local Local CL2-C X'0090' CL2-L X'00b0' CLA-C X'00d0' CLA-L X'00f0' (Add1) (Add5) (DKA (DKA CL4-C X'0091' CL4-L X'00b1' CLC-C...
Page 25: Cache Failure
If Basic HyperSwap is performed from TPC-R, the MIH value of the host I/O and host operation needs to be approximately one second. If the Basic HyperSwap function is performed from TPC-R, the resources in the host system must be ensured sufficiently.
Page 26 Table 9 Unregistered error code for TPC-R Error code Operation Description Recovery procedure 0F0E Pair creation The Cnt Ac-S Z pair creation failed because Remove the failure on the it was executed when a failure occurred in cache, and then retry the Cnt the cache.
Page 27: Planning For Continuous Access Synchronous Z
Remote Web Console must be LAN-attached for the main and remote disk arrays. See the HP StorageWorks P9000 Remote Web Console User Guide for information. The main and remote disk arrays must be set up for Continuous Access Synchronous Z operations.
Page 28: Using Dasd Fast Write
Using DASD fast write DASD fast write (DFW) is required at the main and remote system only when Required is specified for the PPRC DFW to R-VOL option. If DFW to an R-VOL is blocked but the pair was established with the Required option specified, the main system detects DFW OFF at the R-VOL and suspends the pair.
Page 29 Table 1 1 Option modes for Continuous Access Synchronous Z Option mode Description R-VOL read-only function (RCU only). Selects function of CRIT=Y(ALL) or CRIT=Y(PATHS). Mode 36 ON: CRIT=Y(ALL) => equivalent to Fence Level = Data. Mode 36 OFF: CRIT=Y(PATHS) => equivalent to Fence Level = Status. Allows you to change the volume that is suspended when the FREEZE command is issued from the host.
Page 30: Planning For System Performance
Planning for system performance Remote copy operations can affect I/O performance on the host as well as the main and remote disk arrays. Continuous Access Synchronous Z provides several options for minimizing the impact of synchronous operations on performance, or maximize the effectiveness of copy operations to ensure the best level of backup data integrity.
Page 31: Planning Volume Pairs
Table 12 Conditions affecting performance, recommendations (continued) Condition Description Recommendation Capacity of remote The remote system’s performance directly affects Distribute Continuous Access Synchronous Z system the performance of the main system. If a remote remote copy operations among several remote system becomes overloaded with heavy update systems to avoid overloading any one system.
Page 32: Handling Duplicate Volsers
The CCHH (logical cylinder address and logical head address) of R0 must be identical ◦ to the physical cylinder address and physical head address of the track. The CCHH of each user record in a track must be unique. ◦ Continuous Access Synchronous Z operates on volumes rather than on datasets;...
Page 33: Planning I/O To The R-Vol
Your HP representative can obtain the information about online paths from SSBLOG of the SVP. Planning I/O to the R-VOL The remote system rejects I/O to the R-VOL, unless the R-VOL-read option is enabled. The R-VOL read option allows read-only access to an R-VOL while the pair is suspended. The R-VOL read option (mode 20) must be enabled by an HP representative.
Page 34 Table 13 Shared memory and number of LDEVs Additional shared memory for Continuous Access Total number of LDEVs Synchronous Z Base(16KLDEV,SI/VM) 16,384 64KLDEV,SI/VM Extension1,FCV2,DP, CoW Snapshot,TPF 65,280 The number of cylinders in the volumes, which must be calculated. The number of bitmap areas required for Continuous Access Synchronous Z data. This must be calculated using the number of cylinders.
Page 35: Priority Set For Initial Copy Operations And Scheduling Order
Priority set for initial copy operations and scheduling order For performing more initial copy operations than the setting value of the Maximum Initial Copy Activities set on the System Option dialog box, the scheduling order (Priority) can be set for the initial copy operations to be performed.
Page 36: Planning Data Paths
Table 17 Order of starting initial copy being performed Order of starting initial M-VOL Value set for Priority Remarks copy LDEV 02 Cnt Ac-S Z pair for which initial copy is already instructed to be performed LDEV 00 Cnt Ac-S Z pair for which initial copy is already instructed to be performed LDEV 01 Cnt Ac-S Z pair for which initial copy...
Page 37: Supported Data Path Configurations
For distances from 10 km to 30 km (6.2 to 18.6 miles), single-mode longwave Fibre Channel interface cables with up to two switches are required. For distances greater than 30 km. Approved third-party channel extender products and telecommunications lines are required. Continuous Access Synchronous Z operations typically do not extend past 30 km.
Page 38: Planning Ports
Set port topology to the following: NL port: Fab on, FC-AL N port: Fab on, Point-to-Point Some switch vendors require F port (for example, McData ED5000). Extender connection—channel extenders and switches are used to connect the devices across large distances, as shown below. Figure 6 Extender connection Set port topology to the following: NL/FL port: Fab on, FC-AL...
Page 39: Port Requirements
Continuous Access Synchronous Z. This attribute cannot be changed by the Continuous Access Synchronous Z software. For details on the port to which an initiator/external mix mode is set, see the HP StorageWorks P9000 External Storage for Open and Mainframe Systems User Guide.
Page 40: Sharing Continuous Access Synchronous Z Volumes
4 Sharing Continuous Access Synchronous Z volumes This chapter helps you plan Continuous Access Synchronous Z pair volumes when they are shared with non-Continuous Access Synchronous Z volumes. It discusses all of the program products that can be used with Continuous Access Synchronous Z. Volume types that can be shared with Continuous Access Synchronous Z The following table indicates whether non-Continuous Access Synchronous Z volumes can also be used as Continuous Access Synchronous Z M-VOLs and R-VOLs.
Page 41: Continuous Access Journal Z
Virtual LVI volume #1: The volume performs differently according to the type of difference management. For details, see the HP StorageWorks P9000 for Compatible FlashCopy Mirroring User Guide. #2: For more information, contact HP Technical Support. #3: If you use Continuous Access Synchronous Z with Compatible FlashCopy, the Continuous Access Synchronous Z pairs must be created without using the consistency groups.
Page 42: Business Copy Z
Sharing Continuous Access Synchronous Z and Business Copy Z volumes provides multiple copies of data at the local and/or remote sites. For information about Business Copy Z, see the HP StorageWorks P9000 Business Copy for Mainframe Systems User Guide. NOTE: Business Copy Z is recommended for in-system copy operations.
Page 43: Configurations With Business Copy Z T-Vols
Figure 7 Shared Cnt Ac-S Z M-VOL with BC Z S-VOL In the following figure, the Continuous Access Synchronous Z R-VOL also functions as a Business Copy Z S-VOL. In this configuration, Business Copy Z provides another (or several more) backup copies of a Continuous Access Synchronous Z M-VOL.
Page 44: Status Reporting, Data Currency
When performing Virtual LVI/LUN operations on an existing Continuous Access Synchronous Z M-VOL or R-VOL, you must release the pair first to return the volume to Simplex status. For further information on Virtual LVI/LUN, see the HP StorageWorks P9000 Provisioning for Mainframe Systems User Guide.
Page 45: Cache Residency
Cache Residency volumes that can be assigned to Continuous Access Synchronous Z pairs, and Cache Residency operations can be performed on Continuous Access Synchronous Z M-VOLs and R-VOLs. For more information, see the HP StorageWorks P9000 Cache Manager User Guide. Compatible XRC and CC P9500 is functionally compatible with the IBM Extended Remote Copy (XRC) function and IBM 2105, and 2107 Concurrent Copy function.
Page 46: Configuration Operations
5 Configuration operations This chapter provides instructions and information for setting up a Continuous Access Synchronous Z system that is ready for pair operations. Configuration workflow Configuration tasks consist of the following: Check prerequisites for each procedure. In the production system, identify the production volume or volumes that will become Continuous Access Synchronous Z M-VOLs.
Page 47: Configure Disk Arrays And Define Logical Paths
Procedure 1 To define port attributes On the menu bar, click Actions > Remote Copy > Continuous Access Synchronous for Mainframe > RCU Operation. The RCU Operation window opens. Change to Modify mode by clicking the icon. In the Switch Display box, select Port. The ports associated with the local storage system are listed.
Page 48 This procedure adds an RCU, a remote system to the main system. This configures the main and remote system for Continuous Access Synchronous Z. On the menu bar, click Actions > Remote Copy > Continuous Access Synchronous for Mainframe > RCU Operation. The RCU Operation window opens. Change to Modify mode by clicking the icon.
Page 49 In the RCU S/N box, enter the remote CU’s 5-digit serial number. In the Controller ID box, select the remote system’s controller ID. In the Logical Adr. (RCU CU) box, enter the CU number of the RCU being added. The CU number differs by the specified controller ID, as follows: When the specified controller ID is 6 (P9500) or 5 (XP24000/XP20000 Disk Array), you can select a CU number from 00 to FE.
Page 50 12. In the Minimum Paths box, enter the minimum number of paths necessary for operations to continue. If the number of paths in Normal status falls below the Minimum Paths value you set, the main system suspends Continuous Access Synchronous Z pairs. This is done to prevent a performance drop on the host because of low overall bandwidth between main and remote system.
Page 51 If the difference between the two is insignificant, for example, 1ms : 5 ms, initial copying is allowed to run at the specified pace. To determine Round Trip Time value The value of Round Trip Time = round trip time between MCU-RCU x 2(*) + initial copy response time (ms) (*) A data transfer between main and remote system involves two response sequences in one command issuance.
Page 52: Configure Additional Logical Paths
Table 24 Sample settings Round Trip Time Line Speed b/w Number of Lines Initial Copy Pace Number of Maximum Round Trip between MCU MCU/RCU b/w MCU/RCU Initial Copy VOLs Time RCU[ms] [MB/ms] Specified[ms] If using XP12000 Disk Array/XP10000 Disk Array: Set the following parameters using use the System Option window.
Page 53: Set Number Of Volumes To Be Copied Concurrently, Path Watch Time
In the M-R Path box, define the logical path between local and remote systems: In the Port column, select a local system initiator port. In the Pair-Port column, select the remote system RCU target port. This establishes a logical path with the selected initiator port. You can abbreviate the number to two characters.
Page 54 Procedure 3 To change concurrently copied volumes, path watch time, related SIMs (system-wide) On the menu bar, click Actions > Remote Copy > Continuous Access Synchronous for Mainframe > System Option. The System Option window opens. Change to Modify mode by clicking the icon.
Page 55 In the PPRC support by host box, select the status of PPRC support for the host. In the SCP Time(sec.) box, select the State change pending (SCP) time. In the Maximum Initial Copy Activities box, enter the number of volumes that can be copied concurrently during an initial copy operation.
Page 56: Pair Operations
6 Pair operations This chapter provides prerequisite information and the instructions for performing Continuous Access Synchronous Z operations. Pair operations workflow Basic Continuous Access Synchronous Z operations consists of the following. Check prerequisites for each procedure. Always check pair status. Each Continuous Access Synchronous Z operation requires the pair to be in a specific status.
Page 57 Synchronous Z pair is suspended due to an error. You will select one of the following fence level settings: Data – the M-VOL is fenced if an update copy operation fails. “Data” ensures that the R-VOL remains identical to the M-VOL. This is done by preventing the host from writing to the M-VOL during a failure.
Page 58 In the Initial Copy list, select one of the following: Entire Volume – to create the Continuous Access Synchronous Z pair relationship and copy the data from main to remote volumes immediately. (Default) None – to create the Continuous Access Synchronous Z pair relationship but copy no data from main to remote volumes.
Page 59: Suspend Pairs
Suspend pairs You can suspend a pair, which suspends data copying to the R-VOL. The following takes place when a pair is suspended: I/O writes from the host continue to the M-VOL, but stop to the R-VOL. Any current update copy operation completes to the R-VOL, ensuring data consistency to the point of the suspend operation.
Page 60: Resynchronize Pairs
Resynchronize pairs While a Continuous Access Synchronous Z pair is suspended, the main system does not perform update copy operations to the R-VOL. Resynchronizing a pair updates the R-VOL with differential data accumulated since the suspension, so that its data is again identical with the M-VOL’s data. Update copy operations begin again to the R-VOL.
Page 61: Change Fence Level, Other Pair Options
NOTE: When you release a pair from the remote system, remember that the R-VOL and M-VOL are identical (for example, same volume label). Make sure to take appropriate precautions to prevent a system problem due to duplicate volumes. Procedure 8 To delete a pair On the menu bar, click Actions >...
Page 62: Monitoring And Maintenance
7 Monitoring and maintenance This chapter provides information and instructions for monitoring and maintaining the Continuous Access Synchronous Z system. Monitor pair status Monitoring the Continuous Access Synchronous Z system is an ongoing operation that should be performed frequently to keep track of and maintain your pairs. When you want to perform a pair command, first check the pair’s status.
Page 63: Suspend Types
Table 25 Pair status descriptions Status Description Access to M-VOL Access to R-VOL Simplex This volume is not currently assigned to a Continuous Read/write Read/write Access Synchronous Z pair. Pending Duplex The initial copy operation for this pair is in progress. Read/write Read only This pair is not yet synchronized.
Page 64: System Behavior
Suspended types appear on the Detailed Information dialog box. The following lists the Suspended types and descriptions. Table 26 Suspended types Types Applies to Description M-VOL by Operator M-VOL The user split the pair from the main system using the M-VOL Failure in the Suspend Type option in the Suspend Kind field.
Page 65: Export Pair Information
OK . Monitor copy operations, I/O Start and stop monitoring in Performance Monitor. See the HP StorageWorks P9000 Performance for Open and Mainframe Systems User Guide for instructions. In Remote Web Console, click Actions > Remote Copy > Continuous Access Synchronous for Mainframe >...
Page 66: Select Data To Be Graphed
Table 27 Usage Monitor fields Item Description Monitoring Switch Enable: Monitoring is on. Graph displays. Disable: Monitoring is off. Graph is disabled. Gathering Interval The data collection interval. When monitoring is stopped, the default value (1) is displayed. Update The most recent data sample time on the graph. Usage Monitor Remote I/O statistics and status of remote copy monitor.
Page 67: Resize Graph, Save Data
CU number, and LDEV number appear above the graph. - A device ID ending in # (e.g., 00:00:3F #) indicates the LDEV is an external volume. For more information, see the HP StorageWorks P9000 External Storage for Open and Mainframe Systems User Guide.
Page 68: Logical Path Status Definitions
Procedure 13 To monitor logical path status On the menu bar, click Actions > Remote Copy > Continuous Access Synchronous for Mainframe > RCU Operation. The RCU Operation window opens. Select MCU&RCU in the Display box. Select the RCU you want, right-click, then click RCU Status. The RCU Status dialog box displays. Logical path status definitions Status descriptions are provided below.
Page 69: Rcu Maintenance
In the tree, select the local system then select the desired remote system (RCU). In the right-side list, select and right-click the paths you want to delete then click Delete Path. A confirmation message appears. Click OK. Review your selections in the Preview list. To modify, right-click an item and select Modify. To delete in item, right-click and select Delete.
Page 70: Delete Continuous Access Synchronous Z
In the list area, right-click the Path and then click Delete SSID. When the confirmation message appears, click OK to delete the SSID. Click Apply. Delete Continuous Access Synchronous Z You can delete the Continuous Access Synchronous Z relationship between the main and remote system.
Page 71: Planned Outage Of The Main Disk Array
communications are fully restored (all paths have normal status) before beginning I/O operations to the M-VOL. If the main system accepts an I/O for a M-VOL before this, all communications are restored, the main system will suspend the pair and change M-VOL status to suspended-by RCU. The main system cannot change the pair status of the R-VOL.
Page 72: Miscellaneous Maintenance
Power on the main systems, and make sure that they are ready to resynchronize operations. If you suspend any pairs in Step 2, you can also resynchronize (Resume Pair) those pairs now. Miscellaneous maintenance This section provides miscellaneous maintenance information and procedures. ICKDSF maintenance A pair must be suspended before performing ICKDSF maintenance on the M-VOL.
Page 73: Data Migration
8 Data migration This chapter discusses using Continuous Access Synchronous Z to migrate data from one storage system to another. Migrate data Continuous Access Synchronous Z can be used to move data from one system to another. Data is typically migrated for the following reasons: To load data onto new or scratch volumes (for example, to a new or upgraded storage system) To temporarily move data from an LDEV to accommodate other activities (for example, to make repairs)
Page 74 If the original M-VOL is temporarily unavailable for update copy operations, suspend the new pair so that the new main system keeps track of changes. Data migration...
Page 75: Planning And Procedures For Disaster Recovery
9 Planning and procedures for disaster recovery This chapter provides instructions for using Continuous Access Synchronous Z for disaster recovery. Disaster recovery overview The major steps in preparing for disaster recovery follow: Identify the volumes and groups that contain important files and data for disaster recovery. Create Continuous Access Synchronous Z pairs, paying special attention to the options in M-VOL Fence Level Settings to ensure that the system responds the way you want in the event of a failure (see prerequisites in...
Page 76: Csuspend/Quiesce Tso Command
You should prepare for file and database recovery using files for file recovery (for example, database log files that have been verified as current). You can also use the sense information with system timestamp that is transferred via ERC. CSUSPEND/QUIESCE TSO command See the IBM documents SG24–2595, SC35–0355, and SC35–0169 for important information on the optional QUIESCE parameter for the CSUSPEND TSO command.
Page 77: Analyze R-Vol Currency
Clear the remote copy SIMs from the RCUs before OS IPL. Connect to each RCU, open the Continuous Access Synchronous Z System Option window, and click Clear SIM. Perform an IPL of the remote host system. Wait until the IPL is complete, and then vary the R-VOLs online (if they did not come online automatically).
Page 78 Procedure 23 To transfer operations to the main site At the local site, bring up the host server(s). Make sure that Continuous Access Synchronous Z components are operational. At the local site, release all Continuous Access Synchronous Z pairs on the main system. Use the Deleting Mode All option to release all Continuous Access Synchronous Z pairs in each CU.
Page 79: 10 Troubleshooting
Because the time setting of SVP is changed, the monitoring data Monitoring Switch option is set to Enable. might not be updated. Disable Monitoring Switch, then enable again. For more information on Monitoring Switch, see the HP StorageWorks P9000 Performance for Open and Mainframe Systems User Guide. General troubleshooting...
Page 80 Table 32 Troubleshooting secondary path status problems Path status Description Corrective action Initialization Failed The link initialization Make sure that the main and remote system are physically procedure to the remote and correctly connected. system failed. Make sure that you entered the correct remote system S/N, SSID, and path parameters (port, link address, logical address).
Page 81 Table 32 Troubleshooting secondary path status problems (continued) Path status Description Corrective action RCU Port Number The specified port in the Make sure that you entered the correct remote system port Mismatch remote system is physically number. Correct the port number if necessary. disconnected from the main Make sure that the main and remote system are physically system, or the port is not...
Page 82: Error Codes And Messages
Table 33 Troubleshooting suspended Continuous Access Synchronous Z pairs (continued) Pair status/type Applies to Description Corrective action Suspended (pair M-VOL, The main system detected an error Clear the error condition at the remote system or suspended-error)/ R-VOL condition at the remote system, R-VOL, then resynchronize the pair from the main by RCU which caused the main system to...
Page 83: Service Information Messages (Sims)
R-VOL status, or the capacity of the paired volume in the RCU exceeds the licensed capacity of Volume Retention. Figure 1 1 SIM example For further information on the SIMs, see the HP StorageWorks P9000 Remote Web Console User Guide, or call HP Technical Support for assistance. Pinned track recovery To recover a pinned track The following procedure ensures the pair’s full data integrity while recovering the pinned track.
Page 84: 1 Support And Other Resources
HP StorageWorks P9000 Cache Partition User Guide HP StorageWorks P9000 Continuous Access Journal for Mainframe Systems User Guide HP StorageWorks P9000 External Storage for Open and Mainframe Systems User Guide HP StorageWorks P9000 for Business Continuity Manager Software User Guide...
Page 85: Hp Websites
Conventions for storage capacity values P9000 disk arrays use the following values to calculate physical storage capacity values (hard disk drives): 1 KB (kilobyte) = 1,000 bytes 1 MB (megabyte) = 1,000 bytes 1 GB (gigabyte) = 1,000...
Page 86 Table 35 Document conventions (continued) Convention Element Monospace text File and directory names System output Code Commands, their arguments, and argument values Monospace, italic text Code variables Command variables Monospace, bold text Emphasized monospace text WARNING! Indicates that failure to follow directions could result in bodily harm or death. CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.
Page 87: A Using Pprc Commands For Continuous Access Synchronous Z
A Using PPRC commands for Continuous Access Synchronous Z This appendix describes how to use PPRC commands to perform Continuous Access Synchronous Z operations. Overview of PPRC commands The P9500 supports IBM Peer to Peer Remote Copy (PPRC) TSO and ICKDSF commands to enable you to perform Continuous Access Synchronous Z operations from the zSeries and S/390 host system.
Page 88 Table 36 Continuous Access Synchronous Z operations versus PPRC TSO and ICKDSF commands (continued) Continuous ICKDSF Command Description Access command command issued to: Synchronous Z operation RCU Status CQUERY/ PATHS PPRCOPY M-VOL Displays the status of all paths for the CU QUERY/ specified by the DEVN parameter.
Page 89: Cgroup (Freeze/Run) Support
as initiator ports or RCU target ports before the CESTPATH and CDELPATH commands are issued. PPRC TSO command parameter support depends on the CU emulation (2105, or 2107). PPRC command extensions are supported when running with 2105 or 2107 emulation. The PPRC TSO and ICKDSF commands have required and optional parameters that are not described in detail in this document.
Page 90: Requirements
Therefore, do not use the Business Continuity Manager Freeze/Run commands and the CGROUP command at the same time. For further information and instructions on Business Continuity Manager, see the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. Requirements The CGROUP command can only be issued to a Continuous Access Synchronous Z M-VOL or a simplex volume in the MCU.
Page 91: Using The Cgroup Command
FREEZE: When CGROUP is issued with the FREEZE option, the MCU: ◦ Blocks the logical path(s) between the specified MCU CU and RCU CU to stop all Continuous Access Synchronous Z update copy operations to the R-VOLs in the specified RCU.
Page 92: Using Pprc Tso Commands With Cgroup Support
Figure 12 Overview of GDPS operations Figure key: Read/write I/Os are issued from the host. A failure occurs on a Continuous Access Synchronous Z M-VOL, and the MCU suspends the pair. Suspend and extended long busy state are reported to the host. Host reports IEA494I with extended long busy state.
Page 93 Figure 13 Output to MCU: 2105 and 2107 controller emulations Figure 14 Output to RCU: 2105 and 2107 controller emulations: Figure 15 (page 93) show the output of the CQUERY command issued to a CQUERY/VOLUME. Continuous Access Synchronous Z M-VOL that has been suspended by the CGROUP/FREEZE command.
Page 94: Iea494I And Iea491E Console Messages
Figure 16 Output to R-VOL: 2105 and 2107 controller emulations IEA494I and IEA491E console messages When a Continuous Access Synchronous Z pair is suspended, whether user requested or due to failure, the MCU generates sense information to notify the host(s). If the PPRC ERP PTF is installed and PPRC Support = Yes is selected on the RCU option dialog box, this notification results in an IEA494I system console message as well as an IEA491E message.
Page 95: Iea491E Message
IEA491E message When a Continuous Access Synchronous Z pair is suspended due to a failure, the MCU reports SCI as well as unit check status and sense bytes with F/M = FB. In response to the F/M=FB sense bytes, the IEA491E system console message is generated (if supported by the host). Example 2 “IEA491E message”...
Page 96 Table 38 P9500 response characteristics to failure conditions Failure condition Continuous Expected messages FREEZE function Access Synchronous Z pairs suspended? Failure of all channel interfaces No IEA480, IEA491, or IEA494 messages are Not activated on the MCU displayed. Failure of a Failure of one (1) IEA480 message (SIM for physical dev.
Page 97 Table 38 P9500 response characteristics to failure conditions (continued) Failure condition Continuous Expected messages FREEZE function Access Synchronous Z pairs suspended? Failure of a Failure of one (1) The RCU reports IEA480 message (SIM for Not activated disk on the physical device physical device blocked or port of physical device in a parity...
Page 98: Gdps Continuous Access Synchronous Z Compatible Xrc Matrix
Table 38 P9500 response characteristics to failure conditions (continued) Failure condition Continuous Expected messages FREEZE function Access Synchronous Z pairs suspended? Both sides of RCU cache (1) No IEA480 (SIM of cache blocked) is Activated if the blocked due to failure displayed.
Page 99 NOTE: The information shown in Table 39 (page 99) may not be current. Please contact your HP account team for the latest GDPS Continuous Access Synchronous Z Compatible XRC matrix information. Table 39 GDPS Continuous Access Synchronous Z Compatible XRC matrix Feature IBM 3990 6E P9500...
Page 100 Table 40 GDPS Continuous Access Synchronous Z Compatible XRC matrix (continued) Feature IBM 3990 6E P9500 XP24000/XP20000 Disk Array, XP12000 Disk Array/XP10000 Disk Array Maximum pairs 32,768 XP12000 Disk Array/XP10000 Disk Array 16,384 XP24000/XP20000 Disk Array 32,768 Maximum paths between 8 per logical control unit 8 per logical control unit storage systems...
Page 101 Table 41 GDPS Continuous Access Synchronous Z Compatible XRC matrix (continued) Feature IBM 3990 6E P9500 XP24000/XP20000 Disk Array, XP12000 Disk Array/XP10000 Disk Array RCU-to-MCU SIM reporting Not supported per IBM doc To any host or only to RCU To any host or only to RCU Planning for IBM Remote host host...
Page 102 Table 43 GDPS Continuous Access Synchronous Z Compatible XRC matrix (continued) Feature IBM 3990 6E P9500 XP24000/XP20000 Disk Array, XP12000 Disk Array/XP10000 Disk Array Secondary storage system Parallel or ESCON FICON XP12000 Disk interface Array/XP10000 Disk Array Parallel or ESCON or FICON XP24000/XP20000 Disk Array...
Page 103: B Continuous Access Synchronous Z Scripting
B Continuous Access Synchronous Z scripting This appendix describes how to use script files to perform Continuous Access Synchronous Z operations. Scripting overview An added benefit of the Continuous Access Synchronous Z feature is its support for scripting operations. This capability provides the user with additional flexibility in managing their Continuous Access Synchronous Z environment.
Page 104 This section assumes that the user is familiar with batch files and does not provide instructions for writing or editing batch files. The macro commands and parameters listed in this section are the only commands recognized by the scripting function. CAUTION: The user is responsible for testing the scripting function before running any scripts.
Page 105: Scripting Syntax
Table 45 Internal macro commands for Continuous Access Synchronous Z scripting Type Macro Description For lists SetList Set (define) a list of items. AddList Add items to a list. For non-lists Start Declares the beginning of a script. Declares the end of a script. Delay Suspends script execution for the specified length of time.
Page 106: Script File Requirements
Table 47 Script components Component Description Macro name Either an internal macro or a functional macro. Parameter list Parameter identification name (defined in each macro format) = non-list type expression. Expression List, constant, and work variable. List In a list description, a constant is enclosed in braces “{}”. A comma “,” is inserted between constants.
Page 107: Execute A Script
Table 49 Script symbols (continued) Symbol Unequal sign Used as an operator in the If statement when used alone. When the equal sign follows, nothing changes. Equal sign Used as a substitute sign when used alone. When the equal sign follows, it becomes an operator in the If statement.
Page 108: Delete Script Files
12. When the confirmation message appears, click OK. Delete script files Procedure 25 To delete script files Click File Operation on the Script Operation window to open the File Operation dialog box Select the file from the list in Script File that you want to delete. You can select multiple files at the same time.
Page 109: Operation Macro Commands
Table 50 Macro trace file information (continued) Item Description The Continuous Access Synchronous Z scripting error code (0000 = no error). See the error trace file, except when "0000" is displayed. The executed macro is displayed. If the macro was completed successfully, the status is End.
Page 110: Create Pairs
Change pair options Start pairs Get pair status Select pair devices Create pairs The CreateHrcPair command allows you to establish new pairs. The CreateHrcPair command only creates the pair. You must run the StartHrcPair command after establishing the pair to start the remote copy process. The CreateHrcPair parameters are: CreateHrcPair∆$Dev= M-VOL device list ,$RcuSn= Serial number list...
Page 111 Fence level list (string): “N” or “Never” = never; “S” or “Status” = status; “D” or “Data” = data; default = “Never”. For async pairs you must either specify N (never) or omit this parameter. CFW flag list (numeric): 0 = copy CFW data to R-VOL; 1 = only M-VOL; default = 1. DFW flag list (numeric): 0 = DFW not required;...
Page 112: Release Pairs
Example 5 CreateHrcPair command (Part 1) Start $Script="HRC",$Svr="64002"// $Dev SetList $D =_ilDevA, $S = {0x000100,0x000101,0x000102,0x000103,0x000104,0x000105,0x000106, 0x000107} AddList $D =_ilDevA, $S = {0x000108,0x000109,0x00010A,0x00010B,0x00010C,0x00010D,0x00010E, 0x00010F} // $Rdev SetList $D =_ilDevB, $S = {0x001F00,0x001F01,0x001F02,0x001F03,0x001F04,0x001F05,0x001F06, 0x001F07} AddList $D =_ilDevB, $S = {0x001F08,0x001F09,0x001F0A,0x001F0B,0x001F0C,0x001F0D,0x001F0E, 0x001F0F} // $Priority SetList $D =_ilWorkA, $S = {1,2,3,4,16.32} // $Fence SetList $D =_slWorkB, $S = {"D","S","S","N"}...
Page 113: Suspend Pairs
Release range list (string): To maintain interchangeability with the script made with the model before XP12000 Disk Array/XP10000 Disk Array, this parameter has been left. Do not use this parameter with P9500. Time-Saving Mode flag: “Yes” = The Use Time-Saving Mode option is enabled; “No” = The Use Time-Saving Mode option is disabled;...
Page 114: Resynchronize Pairs
Example 8 SuspendHrcPair command Start $Script="HRC",$Svr="64002" // $Dev SetList $D =_ilDevA, $S = {0x000100,0x000101,0x000102,0x000103} AddList $D =_ilDevA, $S = {0x000104,0x000105,0x000106,0x000107,0x000108} // $SusReport SetList $D = _ilWorkA, $S = {0, 1, 0} // $SusMode SetList $D = _slWorkA, $S = {"R-VOL","M", "R", "M-VOL"} SuspendHrcPair $Dev = _ilDevA, $SusMode = _slWorkA, $SusReport = _ilWorkA // $Dev...
Page 115: Change Pair Options
The following example shows the pair macro commands needed to resynchronize the specified pair in synchronous mode with fence level = never and priority = 1. After resynchronizing pairs, you must run the StartHrcPair command to begin remote copy activity. Example 9 ResumeHrcPair command Start $Script="HRC",$Svr="64002"...
Page 116: Start A Pair
Example 10 ChangeHrcOption command Start $Script="HRC",$Svr="64002" // $Dev SetList $D =_ilDevA, $S = {0x000100,0x000101,0x000102,0x000103,0x000104} AddList $D =_ilDevA, $S = {0x000117,0x000118,0x000119} // $OptCfwSetList $D = _ilWorkA, $S = {1, 1, 0} // $Fence SetList $D = _slWorkA, $S = {"D", "S", "N", "Data", "Status"} ChangeHrcOption $Dev = _ilDevA, $Fence = _slWorkA, $OptCfw = _ilWorkA // $Dev...
Page 117: Select Devices
Example 12 GetHrcStatus command GetHrcStatus $Dev=0x00004a _sMsgB=_HrcStatus_Fence _sMsgC=_HrcStatus_Sync _sMsgD=_HrcStatus_Sn _iNumB=_HrcStatus_Ssid _iNumC=_HrcStatus_DeviceR Select devices The SelectHrcDevice command allows you to search for pairs whose status matches the specified parameters. The SelectHrcDevice parameters include: SelectHrcDevice∆$DevList= Output list ,$Dev= Device list [,$RcuSn= Serial number list] [,$RcuSsid= SSID number list] [,$Fence= Fence level list] [,$Sync= Sync level list]...
Page 118: Internal Macro Commands
CT group list (numeric): To maintain interchangeability with the script made with the model before XP12000 Disk Array/XP10000 Disk Array, this parameter has been left. Do not use this parameter with P9500. SEQCHK flag list (string): To maintain interchangeability with the script made with the model before XP12000 Disk Array/XP10000 Disk Array, this parameter has been left.
Page 119: Internal Macro Command Definitions
Table 54 Internal macro commands Type Macro Description For lists SetList Set (define) a list of items. AddList Add items to a list. For non-lists Start Declares the beginning of a script. Declares the end of a script. Delay Suspends script execution for the specified length of time. Executes a script conditionally.
Page 120: Makestring
statements will not be completed. When IF/EndIf statements are used, several conditions must be met. You must end an If statement with an IF/EndIf statement. The execution statement cannot be defined on the same line as the If statement. The If statement must contain one conditional decision statement within parentheses.
Page 121: Message
Example 15 MakeString $D= output buffer ,$Fmt= expression 1,$Item= expression 2 Table 57 MakeString expression definitions Expression 1 Expression 2 Expression 1 is one of three format control strings ($Fmt): Expression 2 is any expression not containing a list reserved variable (must be constant or work variable). %d Converts a 16-bit numeric expression to a decimal number (0 - 65535).
Page 122: Work Variables
If the S/N of the connected storage system is less than a 5-digit number (for example, 00102), input the valid digits only. Start $Script= HRC”,$Svr=102 If you want to execute the script without checking the S/N of connected storage system, do not input any numbers for $Svr between double-quotation marks ("").
Page 123: Reserved Result Variables
Reserved result variables When a functional macro is executed (for example, CreateHrcPair), a result value (_Result) is issued. Figure 19 (page 123) illustrates the result statement format, and Table 59 (page 123) lists and defines the valid result values. When a new macro is initiated, the result value automatically resets to 0x0000.
Page 124: Optional Script Parameters
Table 60 Reserved status variables (continued) Variable Type Description _HrcStatus _Sync String Stores the synchronous level: “Synchronous0” = sync; “Undefined” = undefined. _HrcStatus _TimeOfUpdate String Stores the pair status update time: “MM/DD/YYYY hh:mm:ss” = MM: month, DD: day, YYYY: year, hh: hour, mm: minute, ss: second.
Page 125 Table 61 Syntax requirements for optional parameters (continued) Parameter Syntax requirements Start The number of phrases is not fewer than the minimum count. Duplicate parameter identification names are not specified. The required parameter identification name is defined. The equal sign is described between the right side and $Script. Specifying the right side is correct.
Page 126: Error Reporting
Table 61 Syntax requirements for optional parameters (continued) Parameter Syntax requirements Functional macro (except for The number of phrases is not less than the minimum count. StartHrcPair) Duplicate parameter identification name is prohibited. The required parameter for the identification name is defined. The equal sign is described between the right side and the parameter identification name.
Page 127 Table 62 Error messages (continued) Message Conditions to verify Corrective action Rejection The result of the execution is checked on each If you want to terminate the script or display a target device. If failed, the last error status is message of error occurrence and indication displayed and error flag is set in the reserved following steps, check that _Result is not 0 in script.
Page 128 Table 63 Continuous Access Synchronous Z scripting error codes (continued) Message ID Internal code Error message Error description 2351 220b,2303 Syntax error. Line = nnnn An illegal word is included in script line nnnn. 2351 27xx Syntax error. Line = nnnn The syntax in the parameter description for script line nnnn is invalid.
Page 129 Table 63 Continuous Access Synchronous Z scripting error codes (continued) Message ID Internal code Error message Error description 2362 5109 Parameter value error A functional macro parameter error is found in setting ($OptSusDfwBlk). $OptSusDfwblk. 2362 51 10 Parameter value error A functional macro parameter error was found in setting ($RcuSn).
Page 130 Table 63 Continuous Access Synchronous Z scripting error codes (continued) Message ID Internal code Error message Error description 2362 513A Parameter value error A functional macro parameter error is found in the ($TimeSave). $TimeSave parameter. 2362 513B Parameter value error A functional macro parameter error is found in the $Diff ($Diff).
Page 131 The operation is interrupted according to the modify mode timeout. * ErrorCode = 6005 xxxx corresponds to error codes of Remote Web Console. For details about Remote Web Console error codes, see the HP StorageWorks P9000 Remote Web Console Messages. Error reporting...
Page 132: C Continuous Access Synchronous Z Gui Reference
C Continuous Access Synchronous Z GUI reference This appendix describes the Continuous Access Synchronous Z windows, dialog boxes, fields, and behaviors in Remote Web Console. Continuous Access Synchronous Z windows Continuous Access Synchronous Z information and pair operations are seen and initiated in the following GUI windows: Pair Operation RCU Operation...
Page 133: Pair Operation Window
Window Context menu command Description RCU Operation RCU Status Displays remote system status and path status. window RCU Operation > Add RCU Used to add a remote system to the main system in a Continuous Access Synchronous Z relationship. RCU Operation > Change Used to change remote system options.
Page 134 Use this window to: “Create pairs” (page 56) “Suspend pairs” (page 59) “Resynchronize pairs” (page 60) “Delete pairs” (page 60) “Check pair status” (page 56) “Change fence level, other pair options” (page 61) Item Description Tree Displays the connected storage system, LDKC, CU grouping (grouping each 16 CUs), and the CUs that contain LVIs (CUs without LVIs are not displayed).
Page 135: Detailed Information Dialog Box
Whether or not the host I/O timestamp is transferred from M-VOL to R-VOL is indicated. CLPR The CLPR number and name for the pair volumes. See the HP StorageWorks P9000 Cache Partition User Guide for more information on CLPR. Used Volume Displays the used capacity and the licensed capacity (in parenthesis) for all pairs.
Page 136 This dialog box lets you view details for a selected Continuous Access Synchronous Z pair. Item Description M-VOL and R-VOL areas The following displays in the order shown: LDKC number, CU number, and device ID Emulation type Capacity (number of cylinders) CLPR Local volume’s cache logical partition number and name.
Page 137: Add Pair Dialog Box
Item Description CFW Data Copy Indicates whether CFW data is copied to the R-VOL or not. The Only M-VOL setting is recommended because copying CFW data impacts storage system performance and it is typically used for temporary files (for example, sort work datasets), which are not usually required for disaster recovery.
Page 138 This dialog box lets you create a pair. See “Create pairs” (page 56) for complete information. Item Description M-VOL Shows the M-VOL LDKC number, CU number, LDEV number, and CLPR number and name. R-VOL Where the R-VOL is defined: device ID. Where the remote system is defined.
Page 139: Suspend Pair Dialog Box
Suspend Pair dialog box This dialog box lets you suspend a pair. See “Suspend pairs” (page 59) for complete information. Item Description Volume Shows the selected volume’s LDKC number, CU number, LDEV number. SSB [F/M=FB] When this option is enabled (and PPRC Support = Yes), the MCU will notify all attached hosts (IEA494I message) that the pair was suspended.
Page 140: Resume Pair Dialog Box
Resume Pair dialog box This dialog box lets you resynchronize a pair. See “Resynchronize pairs” (page 60) for complete information. Item Description M-VOL Shows the selected volume’s LDKC number, CU number, LDEV number. M-VOL Fence Level Where the option is defined for rejecting write operations to the M-VOL. Copy Pace Where maximum number of tracks to be copied is defined: 3 or 15.
Page 141: Change Pair Option Dialog Box
This dialog box lets you delete a pair. See “Delete pairs” (page 60) for complete information. Item Description Volume Shows the selected volume’s LDKC number, CU number, LDEV number. Deleting Mode Where the option is defined to delete the pair forcibly. Change Pair Option dialog box This dialog box lets you change the M-VOL Fence Level and CFW Data for an existing pair.
Page 142: Display Filter Dialog Box
Display Filter dialog box This dialog box lets you filter the information displayed on the Pair Operation window. Item Description Type Select the pair type: synchronous, synchronous-C, or all types. M-VOL/R-VOL Select the volume type, M-VOL or R-VOL or all types. CT Group Select the consistency group.
Page 143 “Monitor, maintain logical paths” (page 67) View the following: ◦ Information related to Continuous Access Synchronous Z storage systems in: “RCU Operations list when “MCU&RCU” selected ” (page 144) ◦ Information related to ports in: “RCU Operations list when “Port” selected ” (page 145) Item Description Tree...
Page 144: Rcu Operations List When "Mcu&Rcu" Selected
RCU Operations list when “MCU&RCU” selected List field descriptions when MCU&RCU is selected in the Display box are shown below. The fields vary according to the selections you make in the tree: “When LDKC, a CU group, or CU is selected in tree” (page 144) “When an MCU or RCU is selected in tree”...
Page 145: When An Mcu Or Rcu Is Selected In Tree
When an MCU or RCU is selected in tree The following columns are displayed in the list area when MCU&RCU is selected in Display, and an MCU or an RCU is selected in the tree. Column Description Item SSID or path SSID SSID of the paired CU M-R Path...
Page 146: Rcu Status Dialog Box
RCU Status dialog box This dialog box lets you view status and other information for the selected RCU. Right-click an RCU (MCU&RCU in Display), then select RCU Status. Item Description List Paths on this system. No. The paths are listed in numbered order. Path Status.
Page 147: Add Rcu Dialog Box
Item Description Last Update Time Date and time when the RCU was last updated. FREEZE Option Support for the CGROUP (FREEZE/ RUN) PPRC TSO command. Round Trip Time The time limit for data to travel from M-VOL to R-VOL. Check box, "Refresh the To refresh the RCU Operation window after closing the RCU Status dialog box, click the RCU Operation window check box.
Page 148: Rcu Option Dialog Box
RCU Option dialog box This dialog box lets you change data path parameters: the minimum number of paths, RIO MIH, FREEZE Option, and Round Trip Time options. See the procedure “Configure disk arrays and define logical paths” (page 47) for complete information.
Page 149: Add Path Dialog Box
Add Path dialog box This dialog box lets you configure additional logical paths. See “Configure additional logical paths” (page 52) for complete information. Item Description M-R Path Where the logical path is defined between local and remote systems. MCU Port Where local system initiator port is defined.
Page 150: Usage Monitor Window
This dialog box lets you add an SSID. See “Add, delete SSIDs for an RCU” (page 69) for complete information. Item Description SSID (1st) Existing SSID. SSID (2nd), (3rd), (4th) Where additional SSIDs are defined. Usage Monitor window This window lets you monitor and use copy-operations data and I/O statistics. See “Monitor copy operations, I/O ”...
Page 151: History Window
History window This window lets you view the history of operations performed on pairs, and the data associated with each operation. Information about field behavior is shown in “History window notes” (page 152). Field Description Status The current status of operation history: No history file exists: Operation history does not exist.
Page 152: History Window Notes
Field Description Previous/Next Shows a maximum of 16,384 operations at a time. If the number of operations exceeds 16,384, click Previous or Next to show the remaining operations. History list The history of operations on pairs in the connected storage system. The list consists of the following information: Operation Time: Date and time operation completed.
Page 153: System Option Window
The following example shows an exported text file. Explanations follow. 2002/07/25 20:26:43,Pairing Start,00:1a:80,-----,00:1a:85 2002/07/25 20:25:30,Pair Delete,00:00:84,-----,00:00:86 2002/07/25 17:01:33,Suspend Operation,00:00:85,-----,00:00:87 2002/07/19 20:01:58,Pair Resync. Complete,00:1a:80,-----,00:1a:9e,000:00:02 2002/07/19 20:01:56,Pair Resync. Start,00:1a:8a,-----,00:1a:a8 2002/07/18 09:36:22,Pairing Complete,00:1a:80,-----,00:1a:85,000:00:10 (1) (2) (3) (4) (5) (6) (1) Data and time when the operation finished. (2) Status (3) LDKC, CU, and LDEV numbers of the accessed volume (LDKC:CU:LDEV).
Page 154 Field Description Preview List When you change settings in the System Operation window, the Preview list shows the changes. Here, the changes have not been applied to the storage system. Click Apply to save changes. Operation Indicates the operation that will occur when you click Apply. Change System Option: Change storage system options.
Page 155: Glossary
FC-FP Fibre Channel Framing Protocol fence level A method of setting rejection of P9000 or XP Continuous Access write I/O requests from the host according to the condition of mirroring consistency. Fibre Channel A data transfer architecture designed for mass storage devices and other peripheral devices that require high bandwidth.
Page 156 I/O slots and the number of ports available per I/O adapter. The P9000 and XP family of disk arrays supports Fibre Channel (FC) ports as well as other port types. Ports are named by port group and port letter, such as CL1-A.
Page 157: Index
Index about, planning, Add Pair dialog box, exporting history of pair operations, Add Path dialog box, exporting pair information, Add RCU dialog box, external port, Add SSID dialog box, F/M=FB message, bandwidth, failover software bitmap areas, about, Business Continuity Manager failure conditions and PPRC, about, feature comparison, storage systems,...
Page 158 Resume Pair dialog box, resynchronizing pairs, non-volatile storage (NVS), planning considerations, RMF, round trip time, changing, overview, scheduling order for initial copies, script errors, P/DAS, scripts, Pair Operation window, sharing volumes, pair operations SIMs, exporting history of, SSIDs, adding and deleting, history, storage capacity values with PPRC,...

HP StorageWorks P9000 User Manual

1 Continuous Access Synchronous Z Overview

2 Requirements and Specifications

3 Planning for Continuous Access Synchronous Z

4 Sharing Continuous Access Synchronous Z Volumes

5 Configuration Operations

6 Pair Operations

7 Monitoring and Maintenance

8 Data Migration

9 Planning and Procedures for Disaster Recovery

10 Troubleshooting

1 Support and Other Resources

A Using PPRC Commands for Continuous Access Synchronous Z

B Continuous Access Synchronous Z Scripting

C Continuous Access Synchronous Z GUI Reference

Glossary

Index

Quick Links

Related Manuals for HP StorageWorks P9000

Summary of Contents for HP StorageWorks P9000

Table of Contents