HP StorageWorks XP24000 Continuous Access Software User and Reference Guide Part number: T5278–96002 First edition: June 2007
Legal and notice information © Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . Related Documentation . . . . Document Conventions . . . . Conventions for storage capacity Window Illustrations . . . . . HP Technical Support . . . . . Subscription Service . . . . . HP Websites . . . . . . . . Documentation Feedback . . . . . . . . . . . . values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Preparing for Continuous Access Operations . . . . . . . . . . . . System Requirements . . . . . . . . . . . . . . . . . . . . Requirements and Restrictions for Using Continuous Access . . . . One-to-One Volume Copy Operations . . . . . . . . . . Logical Unit (LU) Types . . . . . . . . . . . . . . . . . Consistency Groups . . . . . . . . . . . . . . . . . . Accessing Continuous Access P-VOLs and S-VOLs . . . . . . Cache and Nonvolatile Storage (NVS) . . . . . . . . . . Host Failover Software . . . . . .
Volume List . . . . . . . . . . . . . . . . . . . . . Display Filter . . . . . . . . . . . . . . . . . . . . Snapshot Function . . . . . . . . . . . . . . . . . . Creating Continuous Access Pairs . . . . . . . . . . . . . Initial Copy Options . . . . . . . . . . . . . . . . . Pair Options . . . . . . . . . . . . . . . . . . . . Changing Pair Options . . . . . . . . . . . . . . . . . . Viewing Continuous Access Pair Status . . . . . . . . . . . Splitting Continuous Access Pairs . . . . . . . . . . . . . .
Figures 1 ..Continuous Access Components for Fibre Channel Connection . . . . . . . . . . . . 14 2 ..Remote Copy Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3 ..Selecting and Settling Continuous Access Asynchronous Recordsets at the RCU . . . . . 24 4 ..Shared Continuous Access P-VOL/Business Copy P-VOL . . . . . . . . . . . . . . . 37 5 ..Shared Continuous Access S-VOL/Business Copy P-VOL . . . . . . . . . . . . . . . 37 6 ..
37 ..Example of Continuous Access History File . . . . . . . . . . . . . . . . . . . . . 93 38 ..Option Settings List for the Storage System . . . . . . . . . . . . . . . . . . . . . 93 39 ..System Option Dialog Box 94 . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 ..Option Settings List for the CUs . . . . . . . . . . . . . . . . . . . . . . . . . 95 41 ..CU Option Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 42 ..Pair Operation Window . . . . . . . . . . .
Tables 1 ..Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2 ..RAID Level Configurations of Continuous Access . . . . . . . . . . . . . . . . . . 14 3 ..Relationship between the Additional Shared Memory and the Number of Usable Bitmap Areas of a Storage System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4 ..Sidefile Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 ..Continuous Access Pair Status . . . . . . . . . . . . . . . . . . .
About this Guide This user’s guide describes and provides instructions for performing Continuous Access operations on the HP storage system. The term storage system in this guide refers to an HP StorageWorks XP24000 Disk Array.
• • • • 1 1 1 1 KB (kilobyte) = 1,000 bytes MB (megabyte) = 1,0002 bytes GB (gigabyte) = 1,0003 bytes TB (terabyte) = 1,0004 bytes HP XP storage systems use the following values to calculate logical storage capacity values (logical devices): • • • • • 1 1 1 1 1 KB (kilobyte) = 1,024 bytes MB (megabyte) = 1,0242 bytes GB (gigabyte) = 1,0243 bytes TB (terabyte) = 1,0244 bytes block = 512 bytes Window Illustrations The windows shown in this guide were displayed on a Windows computer with the Internet Exp
Documentation Feedback HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to storagedocsFeedback@hp.com. All submissions become the property of HP.
About this Guide
1 About HP StorageWorks XP Continuous Access Software Operations Continuous Access provides a storage-based hardware solution for disaster recovery that enables fast and accurate system recovery. Once Continuous Access operations are established, duplicate copies of data are automatically maintained for backup and disaster recovery purposes. During normal Continuous Access operations, the primary volumes remain online to all hosts and continue to process both read and write I/O operations.
Figure 1 on page 14 shows the Continuous Access components and their functions: • Storage systems Note: The additional Shared Memory option is required for Continuous Access operations.
To provide greater flexibility and to enable the storage system to be tailored to unique customer operating requirements, additional operational parameters, or optional modes, are available for the storage system. At installation, the storage system modes are set to their default values, so make sure to discuss these settings with your HP service representative. The storage system modes can only be changed by your HP service representative.
Continuous Access supports the basic logical unit (LU) types available on the storage system (for example, OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-L, and OPEN-V). Continuous Access also supports the HP StorageWorks XP LUN Expansion (LUSE), HP StorageWorks XP Virtual LVI/LUN, and HP StorageWorks XP Cache Residency Manager features, ensuring that all user data can be backed up or duplicated. See “Logical Unit (LU) Types” on page 44 for further information on LU requirements and support.
Note: To recover the data from a disaster, you must prepare the RCU-MCU paths in addition to the usual MCU-RCU paths. For more information on the path settings between an MCU and RCU, see “Adding an RCU” on page 71. When you set the RCU-MCU path, you must also specify: • the same combination of CUs when you set the MCU-RCU path if you set the MCU-RCU path when specifying the CU. • CU Free if you set the MCU-RCU path when specifying CU Free.
Host Failover Software Host failover software, which transfers information between host servers at the primary and remote sites, is a critical component of any disaster recovery effort. Host failover is configured using the desired host failover software product for the platform (for example, Microsoft Cluster Server), depending on your installation requirements and standards. The storage system program products do not provide any host failover functions.
When the S-VOL write enable pairsplit option is used, the RCU keeps track of S-VOL updates and sends the S-VOL differential data to the MCU when the split pair is resynchronized. In this case, the MCU merges the P-VOL and S-VOL differential data to identify the out-of-sync tracks.
Access Asynchronous P-VOL with COPY status and the track has already been copied to the S-VOL, the MCU performs an asynchronous update copy operation.
• The number of bitmap areas: To calculate the number of bitmap areas in each volume, use the following formulas: • For OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-L, OPEN-K The number of bitmap areas = ( ↑ ((Number of cylinders × 15) ÷ 122,752) ↑ ) Note: 122,752 is the amount of differential data per bitmap area. The unit for the amount of differential data is bits.
an HP XP12000 Disk Array, the maximum number of pairs that you can create is the lesser number by comparing both numbers. If an HP XP24000 Disk Array is connected with an HP XP12000 Disk Array, you can use both the Remote Web Console software and the RAID Manager software to specify the unit of Difference Management: Auto, Track, and Cylinder. You can also see the setting for Difference Management by using them.
MCU. The RCU ensures that records are applied to the S-VOLs in the correct sequence. This method of remote I/O provides the most efficient use of MCU-to-RCU link resources. Note: The parameter length and detailed specification of the Continuous Access Asynchronous channel command are different than for Continuous Access Synchronous RIOs. You must make sure that your channel extenders are capable of supporting this command. For further details, contact your HP support representative.
* Since the record set has not yet arrived at the RCU, S2 does not have a time stamp now. Figure 3 Selecting and Settling Continuous Access Asynchronous Recordsets at the RCU Types of Recordsets In addition to host update recordsets, the MCU passes control information to the RCU in special non-update recordsets. These special recordsets indicate when pair status changes and when an MCU power-off sequence is initiated, and also maintain sequence numbers in periods of low host activities.
Inflow Control by RCU. When the amount of RCU sidefile cache reaches the user-specified threshold (pending update data rate), the RCU responds with channel-command-retry requests to the RIO commands which transfer the recordsets from the MCU. The only recordset accepted by the RCU is the recordset with the sequence number required to continue settling the pending recordsets.
Group Options Continuous Access provides the following options for each consistency group: Time Out (Copy Pending) and Time Out (RCU Ready). These options are selected when you add a group, and can only be modified if the group does not contain any P-VOLs in the MCU. Time Out (Copy Pending). This group option specifies the maximum delay allowed for Continuous Access Asynchronous copy operations.
Pair Status Continuous Access displays the pair status for each volume in the connected storage system. Table 5 on page 27 lists and describes the Continuous Access pair status descriptions. The MCU maintains the status of the P-VOL and can change the pair status of the P-VOL and S-VOL. The RCU maintains the status of the S-VOL and can change the pair status of the S-VOL but not the P-VOL.
Pair Status Description P-VOL Access S-VOL Access PSUS (pair suspended-split) (see Table 6 on page 30 for split types) This pair is not synchronized, because the user has split this pair (pairsplit-r), or because the user has released this pair from the RCU (pairsplit-S). For Continuous Access Asynchronous pairs, the MCU and RCU keep track of any recordsets that were discarded during the pairsplit-r operation.
Pair Status Description P-VOL Access S-VOL Access Suspending This pair is not synchronized. This pair is in transition from PAIR or COPY to PSUS/PSUE. When the split/suspend pair operation is requested, the status of all affected pairs changes to Suspending. When the split/suspend operation is complete, the status changes to PSUS/PSUE. Read/write Read only Deleting This pair is not synchronized. This pair is in transition from PAIR, COPY, or PSUS/PSUE to SMPL.
Table 6 Split Types (PSUS) Type Applies to Description PSUS, P-VOL by Operator P-VOL (Continuous Access Synchronous only) The user split the pair from the MCU using the P-VOL Failure option. The S-VOL split type is PSUS-by MCU. PSUS, S-VOL by Operator P-VOL, S-VOL The user split the pair from the MCU or RCU using the S-VOL option. PSUS, by MCU S-VOL The RCU received a request from the MCU to split the pair. The P-VOL split type is PSUS-P-VOL by Operator or PSUS-S-VOL by Operator.
When a Continuous Access Synchronous pair is suspended, the MCU stops performing update copy operations to the S-VOL and may or may not continue accepting write I/Os for the P-VOL, depending on the P-VOL fence level pair option. If a synchronous update copy operation fails, the MCU maintains exact synchronization by reporting a unit check and decommitting the P-VOL update, so that the host system and application program regard that write operation to the P-VOL as failed.
suspended, the tracks which contain the following records are marked in the differential data as modified (to be copied during the pairresync operation): • The recordsets that were created by the MCU, but not yet sent to the RCU. After marking these P-VOL tracks as modified, the MCU discards these recordsets. • The recordsets that were sent to the RCU, but not acknowledged by the RCU. The MCU marks these P-VOL tracks as modified and discards these recordsets.
Table 10 Whether Non-Continuous Access and Non-Continuous Access Asynchronous Volumes Can Be Used as Continuous Access and Continuous Access Asynchronous Volumes Functions and Volumes Can the Volumes be Used as Continuous Access P-VOL? Can the Volumes be Used as Continuous Access S-VOL? Can the Volumes be Used as Continuous Access Asynchronous P-VOL? Can the Volumes be Used as Continuous Access Asynchronous S-VOL? Yes Yes Yes Yes LUN Expansion (LUSE) LUSE Volume HP StorageWorks XP Business Copy So
Functions and Volumes Can the Volumes be Used as Continuous Access P-VOL? Can the Volumes be Used as Continuous Access S-VOL? Can the Volumes be Used as Continuous Access Asynchronous P-VOL? Can the Volumes be Used as Continuous Access Asynchronous S-VOL? Target volume No No No No Reserved volume No No No No HP StorageWorks XP Continuous Access Journal Software Primary data volume in COPY status No No No No Yes No However, the volume can be used as an S-VOL only when you restore a Conti
Functions and Volumes Can the Volumes be Used as Continuous Access P-VOL? Can the Volumes be Used as Continuous Access S-VOL? Can the Volumes be Used as Continuous Access Asynchronous P-VOL? Can the Volumes be Used as Continuous Access Asynchronous S-VOL? Secondary data volume in SSWS status Yes No No No Secondary data volume in PSUE status Yes No No No HP StorageWorks XP Data Retention Utility Volume with Read/Write attribute Yes Yes Yes Yes Volume with Read Only attribute Yes Yes Ye
Business Copy Business Copy volumes can be assigned to Continuous Access pairs, and Continuous Access volumes can be assigned to Business Copy pairs. Continuous Access and Business Copy can be used together in the same storage system and on the same volumes to provide multiple copies of data at the primary and/or remote sites. Table 11 on page 36 describes the host pair status reporting for Continuous Access volumes, Business Copy volumes, and Continuous Access/Business Copy shared volumes.
Figure 4 on page 37 through Figure 7 on page 38 show the various Continuous Access/Business Copy configurations which share volumes. Continuous Access supports synchronous and asynchronous operations for shared Continuous Access/Business Copy volumes. • Figure 4 on page 37 shows an example of a Continuous Access P-VOL which is also functioning as a Business Copy P-VOL.
Figure 7 Shared Business Copy S-VOL/Continuous Access P-VOL Caution: When you share a Continuous Access S-VOL with a Business Copy P-VOL as shown in Figure 5 on page 37 or Figure 6 on page 37, the write operation to the Continuous Access P-VOL takes time. Specifically, when the Business Copy pair is in the PSUS(SP) status, the write operation to the Continuous Access P-VOL may takes extra time depending on the time for the copy process of the Business Copy pair.
Table 14 Pair Status and Availability of Data Retention Utility Operation Volume P-VOL S-VOL Volume Data Retention Utility Operations Changing Access Attribute Referencing Access Attribute SMPL OK OK COPY *1 OK PAIR *1 OK PSUS OK OK PSUE OK OK SMPL OK OK COPY No OK PAIR No OK PSUS No*2 OK PSUE No OK *1: See Table 15 on page 39. *2: If the Write option is set to the S-VOL, the access attribute can be changed.
For further information on Virtual LVI/LUN (VLL), see the HP StorageWorks XP24000 Virtual LVI/LUN (VLL) and Volume Shredder User’s Guide. Cache Residency Manager The volumes that are applied using Cache Residency Manager can be assigned to Continuous Access pairs, and Cache Residency Manager operations can be performed on Continuous Access P-VOLs and S-VOLs. For further information on Cache Residency Manager, see the HP StorageWorks XP24000 Cache Residency Manager User’s Guide.
3. After you have disabled LDEV data collection and/or disconnected Performance Monitor, you can connect to the storage system using the Remote Web Console software, launch the Continuous Access software, and perform Continuous Access operations (for example, create pairs, view pair status). 4. When you are finished performing Continuous Access operations, exit the Continuous Access software, and disconnect the Remote Web Console software from the storage system. 5.
About HP StorageWorks XP Continuous Access Software Operations
2 Preparing for Continuous Access Operations System Requirements Continuous Access operations involve the storage system MCUs and RCUs containing the primary and secondary volumes, the remote copy connections between the MCUs and RCUs, the host(s) at the primary and remote sites, and the licensed Continuous Access software. Note: Continuous Access can coexist with TrueCopy for Mainframe (all copy modes) in the same storage system.
Note: You must operate the Remote Web Console software in modify mode to perform Continuous Access operations. Users in view mode can only view Continuous Access information. • About the license of Continuous Access Asynchronous: To use Continuous Access Asynchronous, you must install not only Continuous Access Asynchronous but also Continuous Access. So, you need license codes for both Continuous Access Asynchronous and Continuous Access.
Consistency Groups The Continuous Access Asynchronous consistency groups have the following requirements: • Each Continuous Access Asynchronous pair must be assigned to one and only one consistency group. • The maximum number of pairs in one consistency group is 4,096. • The maximum number of consistency groups established for one MCU-RCU pair is 128 (00-7F). The RCU supports a maximum of 128 groups.
If the Continuous Access S-VOLs and P-VOLs are connected to the same host(s), HP strongly recommends that the S-VOLs be defined to remain offline to avoid this problem.
for Mainframe, and TrueCopy Asynchronous for Mainframe) can share the same remote copy connections. Remote Copy Connections Figure 8 on page 47 shows the remote copy connection configurations for Fibre Channel interface Continuous Access operations. The MCU and RCU of each Continuous Access pair must be connected via multimode shortwave or single-mode longwave optical fibre cables. If you use multimode shortwave optical fibre cables, fibre cables up to 1.
Host (Primary) Host (Secondary) Initiator port NL Port * RCU target port MCU Ordinary fibre-channel interface port (target port) RCU * To set ports, use LUN Manager to set the port topology to: Fab off, FC-AL. Figure 9 Interface Direct Connection (NL_Port) Host (Primary) FL_Port or F Port [1] FL_Port or F Port [1] Host (Secondary) Initiator port E Port RCU target port MCU NL_Port or N Port [2] Ordinary fibre-channel interface port (target port) RCU Switch 1.
Host (Primary) Host (Secondary) Initiator port RCU target port Ordinary fibre-channel interface port (target port) MCU NL_Port or N Port * Switch RCU Channel extender * To set ports, use LUN Manager to set the port topology to: NL/FL port: Fab on, FC-AL F port: Fab on, Point-to-Point Figure 11 Interface Extender Connection Enabling Continuous Access Options You must enable the Continuous Access option(s) (Asynchronous and/or Synchronous) on the storage systems using the Remote Web Console software.
4. Click Go, Continuous Access, and then RCU Operation on the menu bar of the Remote Web Console main window to start the Continuous Access software where the RCU Operation window is displayed. 5. Configure the Fibre Channel ports which are connected to the RCUs as initiator ports (see Figure 12 on page 51) (see “Configuring the Host Interface Ports” on page 70 for instructions). 6.
Figure 12 Configuring the RCU Target and Initiator Ports XP24000 Continuous Access Software User and Reference Guide 51
Figure 13 Adding the RCUs 52 Preparing for Continuous Access Operations
Figure 14 Configuring the RCU Options Figure 15 Setting the Async Options XP24000 Continuous Access Software User and Reference Guide 53
Figure 16 Adding the Consistency Groups 54 Preparing for Continuous Access Operations
3 Using the Continuous Access GUI The Continuous Access main window and its six tabs (see “Continuous Access Windows” on page 55) provide access to all Continuous Access operations: pair operations, RCU operations, asynchronous operations, usage monitor, and history operations. The Continuous Access configuration operations include RCU operations, asynchronous operations, and usage monitor. The Continuous Access pair operations are described in “Performing Continuous Access Pair Operations” on page 99.
2. On the Remote Web Console main window, select modify mode to perform Continuous Access operations. Users in view mode can only view Continuous Access information. 3. Click Go, Continuous Access, and then the window name that you want on the menu bar of the Remote Web Console main window. Continuous Access software starts and the window that you have chosen is displayed.
Menu Command Description Pairsplit - r Allows you to split or suspend Continuous Access pairs. Pairresync Allows you to resynchronize Continuous Access pairs which are split or suspended. Change Pair Option Allows you to change the Continuous Access pair options. RCU Status Displays the RCU status and path status for an RCU. RCU Operation ÆAdd RCU Allows you to add an RCU to the connected storage system. RCU Operation ÆChange RCU Option Allows you to change the RCU options.
Pair Operation Window Please see “Pair Operation Window” on page 99 for detailed information on the Pair Operation window. RCU Operation Window The RCU Operation window (see Figure 18 on page 58) displays the MCU/RCU and port information, and allows you to perform the Continuous Access RCU and port configuration operations (see “RCU Operations” on page 69). To update the information on the RCU Operation window: • • • • • Click another tab, and then click the RCU Operation tab.
• • • • port type to display the port information for that adapter/port type. You can only select one CHA or port type at a time. List: When you select MCU&RCU in the Display box, the list displays the detailed MCU/RCU information (see “MCU&RCU Display on the RCU Operation Window” on page 59) for the LDKC (when selected), the selected CU grouping (grouping each 16 CUs), or the selected CU (CU Free and CU#). The MCU/RCU information can be sorted by column in ascending or descending order.
• Item: SSID or path. • ID: SSID of the other CU of the pair or path group ID. • M-R Path: Path channel type (fibre) between the MCU and RCU (blank when the target CU is the MCU). • Status: Status of the path. • MCU Port: Port number on the MCU side. • RCU Port: Port number on the RCU side.
Figure 20 MCU&RCU Display on the RCU Operation Window showing RCU List Port Display on the RCU Operation Window When the Port button is clicked in the Display box, the RCU Operation window displays the channel adapters (fibre: ) and port types (Target: , RCU Target: , Initiator: , External: Initiator/External: ) in the tree and port information in the list. , Select Subsystem to display all port information.
Figure 21 Port Display on RCU Operation Window Asynchronous Operation Window The Asynchronous Operation window (see Figure 22 on page 63) allows you to perform the Continuous Access Asynchronous configuration operations (see “Asynchronous Operations” on page 83). To update the information on the Asynchronous Operation window: • Click another tab and then click the Asynchronous Operation tab. • Click File, and then Refresh on the menu bar of the Remote Web Console main window. • Click the Apply button.
Figure 22 Asynchronous Operation Window The Asynchronous Operation window presents: • Tree: allows you to display all consistency groups (except groups that are used for Continuous Access) belonging to LDKC#00 (default) or all consistency groups (except groups that are used for Continuous Access) belonging to LDKC#01. For each LDKC, this tree displays the consistency groups that are already in use (Used) and the consistency groups that are available for use (Not Used).
• CLPR: The number and name of the CLPR to which the volumes forming pairs belong. If the consistency group is not in use, this column is blank. For further information on CLPRs, see the HP StorageWorks XP24000 Disk/Cache Partition User’s Guide. • Operation: Indicates the current operation performed on the Asynchronous Operation window. • Preview: Indicates the number of rows in the preview list.
History Window The History window (see Figure 24 on page 65) displays the history information for the Continuous Access pairs and allows you to perform Continuous Access history operations. The history information includes the records for the main status changes (for example, pair creation, and release) of the Continuous Access pairs. See “History Operations” on page 92 for information and instructions on performing Continuous Access history operations.
• The History List displays the history information for the Continuous Access pairs in the connected storage system. Continuous Access history information is saved for seven days, and the maximum amount of information that can be saved is 524,288. By default, the list is in the order in which the information was received from the storage system. The History List displays the following information: • Operation Date/Time: The date and time when the operation was completed.
Figure 25 System Option Window • Tree: Displays Option at the top of the tree. Subsystem Option and CU Option will be displayed below Option. CU Option will be displayed by each LDKC. • List: Displays nothing by default. When you select Subsystem Option or CU Option, the option settings will be displayed. • Preview List: Displays the settings before you click the Apply button for changing or deleting the settings. To change or delete settings, right-click in the preview list.
Using the Continuous Access GUI
4 Performing Continuous Access Configuration Operations RCU Operations The RCUs are the control units which control the S-VOLs of the Continuous Access pairs. The RCUs are connected to the MCUs via the remote copy connections and receive and process commands from the MCUs.
• RCU Target: Allows you to change the selected fibre port(s) to RCU targets. • Target: Allows you to change the selected fibre port(s) to target ports. 5. For the MCU&RCU display, click the menu command for the desired operation. When two or more RCUs are selected, only the RCU Operation command is available. For the add and change operations, use the dialog box to perform the operation, and click Set to close the dialog box. There is no dialog box for the delete operation.
Caution: Limit the number of hosts connected to an RCU target port to 128 or fewer to avoid a mistaken disconnection. If more than 128 hosts are connected to an ordinary target, some hosts may be disconnected after changing the type from target to RCU target. To configure the storage system Fibre Channel ports: 1. 2. 3. 4. 5. 6. Click the RCU Operation tab, and click the Port display button to display the channel adapters and port types for the connected storage system in the tree.
Figure 26 Add RCU Dialog Boxes (Top: for CU Free, Bottom: Other than CU Free) RCU S/N: Allows you to enter the 5-digit serial number of the RCU being added. LDKC: Allows you to enter the LDKC number which the RCU belongs to. Specify 00 or 01. Note: You can specify only 00 for the current microcode version.
Controller ID: Allows you to select the controller ID (storage system family ID) of the RCU being added from the drop-down list. The controller ID for an HP XP24000 Disk Array is 5 and the controller ID for an HP XP12000 Disk Array is 4. Logical Adr. (RCU CU): Allows you to 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 5 (HP XP24000 Disk Array), you can select a CU number from 00 to FE.
9. one or more operations, select the operation(s), right-click the preview list, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. To start the operation(s), click the Apply button. The changes that you set are reflected in the upper list on the window. The preview list is cleared.
: FL-Port Connection Switch Switch : Fibre Channel Interface Port Switch Switch 1C 1D 2C 2D 2E SSID: 0088 Serial #: 05031 RCU SSID: 0244 Serial #: 05033 MCU Add RCU (Fibre) • RCU S# = 05031, SSID = 0088, No.
Figure 28 RCU Option Dialog Box The Minimum Paths option allows you to specify the minimum number of paths required for each RCU connected to the current MCU (default = 1). If you enter a larger number than the number of paths already set on the Add RCU dialog box, or if the number of paths falls below this number (for example, failed path), an error occurs.
following values: the initial copy pace, the maximum number of maximum initial copy VOLs, the speed of the line between the MCU and RCU, and the number of lines. Initial Copy response time (ms) = (1[MB] / “Speed of line between MCU-RCU[MB/ms](*1) ”) x (“initial copy pace”(*2) / 15) x (“max number of maximum initial copy VOLs (*3)” / “Number of lines between MCU-RCU” (*4) ) (*1) When you connect the MCU with the RCU without lines and so on, specify 0.17[MB/ms] in “Speed of line between MCU-RCU”.
5. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. To apply the settings, click the Apply button. Adding and Deleting Logical Paths to an RCU Before adding a path to an RCU, make sure that the remote copy connection is properly installed, the appropriate MCU ports are configured as initiator ports, and the appropriate MCU CU is selected.
5. Click Set to close the Add Path dialog box. The preview list displays the requested add path operation(s). 6. Verify the requested operation(s) displayed in the preview list. To change the add path operation, select the operation from the preview list, right-click, and click Modify. To remove the operation, select the operation, right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 7.
Figure 30 Add SSID Dialog Box To add one or more SSIDs to an existing RCU: 1. Click the RCU Operation tab, and click the MCU&RCU display button. 2. Select and double-click on the desired MCU CU in the tree, and then select the RCU to which you want to add SSID(s). Alternatively, select the RCU in the list, right-click, and click Edit SSID(s) & Path(s). All SSIDs for the selected RCU are listed. 3. Right-click the path/SSID list, and then click Add SSID to open the Add SSID dialog box. 4.
To view the detailed RCU status information: 1. Click the RCU Operation tab, and click the MCU&RCU display button. 2. Select the RCU for which you want to display the status in the list. You may only view status for one RCU at a time. 3. Right-click the RCU, and click RCU Status to open the RCU Status dialog box. Figure 31 RCU Status Dialog Box (Top: for CU Free, Bottom: for the CU excepting CU Free) • Path List: • No.: Path number (path list item number). • Path Status: Path status.
• • • • • • • • • • • • • RCU Port: Port number of the RCU. RCU S/N: Serial number of the RCU. The LDKC number is displayed enclosed in parentheses to the right of the RCU S/N. Controller ID: Controller ID and model name. Path Gr. ID: The user-registered path group ID when an RCU is added to use CU Free. SSID: SSID(s) of the RCU. RCU CU No.: CU number of the RCU. When you select CU Free, Any is displayed. MCU-RCU Path: Type of channel interface between the storage systems (fibre or serial).
reconfigure the remote copy connections to add another RCU to the MCU, or you can remove the remote copy connections and reconfigure the MCU ports (initiator ports to ordinary target ports for fibre) to provide additional host channels for the MCU. Note: If all affected Continuous Access pairs have not been released, the MCU will reject the delete RCU operation to prevent accidental release of Continuous Access pairs. The RCU OperationÆDelete RCU command allows you to delete an RCU from an MCU CU.
• To omit one or more operations, select the operation(s) to be omitted from the preview list, right-click, and click Delete. The operations are removed from the preview list. If all operations are removed, the list returns to its original display. • To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. All operations are removed, and the list returns to its original display. 6.
for async recordsets reaches the specified value of the threshold, the MCU controls the cash inflow. It follows that the delay of I/O time of MCU occurs. The I/O Delay Increase option allows you to specify the threshold (30-70%), which is the maximum amount of cache for starting to strengthen control over the inflow for the asynchronous copy. When the amount of cache that is used for async recordsets reaches the specified value of the threshold, the MCU controls the cash inflow.
Offloading Timer (sec.): Allows you to specify the amount of time for monitoring the transfer of data to a sidefile between 0 and 255 seconds in 1 second increments. The default setting is 90 seconds. Enable Inflow Control: Allows you to enable the inflow control. To enable the inflow control, click the check box. By default, the check box is selected. Before changing this option, you should release or suspend pairs in the selected consistency group. Time Out (Copy Pending) (min.
Figure 34 CT Group Option Dialog Box MCU-RCU Path: Allows you to select the port type for the remote copy connections. You can only change the port type when the group does not contain any pairs. Offloading Timer (sec.): Allows you to specify the amount of time for monitoring to transfer data to a sidefile between 0 and 255 seconds in 1 second increments. The default setting is 90 seconds. Enable Inflow Control: Allows you to enable the inflow control. To enable the inflow control, click the check box.
list, right-click, and click Delete. To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 8. To apply the settings, click the Apply button. 9. When you are finished changing the CT group options, you can resynchronize (resync) all pairs in the group(s) (Pairresync). See “Resynchronizing Continuous Access Pairs” on page 117 for instructions on resynchronizing pairs.
Note: If # is added to the end of an LDEV number (for example, 00:3C#), the LDEV is an external volume. For details on external volumes, see the HP StorageWorks XP24000 External Storage Software User’s Guide. MCU-RCU Path: Type of channel interface between the storage systems (fibre). Offloading Timer (sec.): The amount of time for monitoring the transfer of data to a sidefile. If the CU type is RCU, this parameter is not displayed. Inflow Control: Enable or disable the inflow control.
• Displaying the usage monitor graph (see “Displaying the Usage Monitor Graph” on page 90), and • Exporting the usage monitor data file (see “Exporting the Usage Monitor Data File” on page 92). Starting and Stopping Usage Monitoring To make settings for starting and stopping the monitor, use Performance Monitor. For procedures to start and stop the monitor, see the HP StorageWorks XP24000 Performance Monitor User’s Guide.
Figure 36 Selecting the Data for the Usage Monitor Graph Table 20 Remote Copy I/O Statistics Statistic [1] Description RIO count All RIO count Total number of remote I/Os. All write count Total number of remote write I/Os. RIO error count Number of errors that occur during remote I/O. Initial copy Initial copy RIO count Number of initial copy remote I/Os. Average transfer rate (kB/s) Average transfer rate (kB/sec) for initial copy remote I/Os.
Statistic Description [1] Average response (ms) Average response time (msec) for asynchronous update copy remote I/Os. Number of Scheduling Recordsets Number of recordsets that are scheduled for the settlement of sidefile. Scheduling Miss Count Number of times recordsets do not arrive during the schedule. Number of Remaining Recordsets Number of remaining recordsets when the schedule is completed. Scheduling Attempt Count Number of job activations of consistency manager.
(3) LDKC number, CU number, and LDEV number of the operated volume. (4) This column is not used. (5) LDKC number, CU number, and LDEV number of the paired volume. (6) The time taken for the operation (from the start of the operation to the end). Displayed only for Pairing Complete and Pair Resync. Complete operations.
• To change the settings, right-click the preview list, click Modify, make the desired changes, and close the dialog box. The preview list displays the updated information. • To omit the settings, right-click the preview list, and click Delete. The changes are cancelled. • To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. The changes are cancelled. 6. To apply the settings, click Apply.
Figure 40 Option Settings List for the CUs • CU: Number of CUs in the LDKC that you chose from the tree (00 to FE). • Activities: Number of volumes in concurrent initial copy operations (1 to 16). When you set Disable for the Maximum Initial Copy Activities (CU) option on the System Option dialog box, Disable is shown instead of a number.
Figure 41 CU Option Dialog Box • Maximum Initial Copy Activities: Allows you to specify the number of volumes on which copy operations can be performed at the same time, from 1 to 16 volumes, for the selected CU. Even if you set a value larger than the setting for Maximum Initial Copy Activities on the System Option dialog box, the priority is given to Maximum Initial Copy Activities on the System Option dialog box.
Table 21 Optimizing Continuous Access Operations and Storage System Performance Condition Description Recommendation(s) Write-intensive workloads Write-intensive workloads, such as database logging volumes, can have a significant impact on storage system I/O response times. Spread write-intensive data across several volumes to minimize queuing. Large block size Workloads with large write block sizes, such as DB deferred writes, can impact performance.
Asynchronous pairs, you can use the Delete Range-Group option to release all pairs in a group using just one operation. Verify that the pair status has changed to SMPL for all Continuous Access volumes before continuing. 2. Delete the Continuous Access Asynchronous group(s) from the MCU(s) (see “Deleting Consistency Groups” on page 89). The RCU will automatically delete a group when all pairs in the group have been released. 3. Delete the RCUs (see “Deleting an RCU” on page 82).
5 Performing Continuous Access Pair Operations Preparing for Continuous Access Pair Operations Before starting Continuous Access operations, you must consider the relative importance of storage system I/O performance and disaster recovery preparation. As described in “Other Operations” on page 93, remote copy operations can affect the I/O performance of the MCUs and RCUs.
To update the information on the Pair Operation window, click another tab, and then click the Pair Operation tab again; or click File, and then Refresh on the menu bar of the Remote Web Console main window. The pair information is also updated when you click the Apply button. Figure 42 Pair Operation Window The Pair Operation window presents: • Tree: Displays the connected storage system, LDKC, CU grouping, CUs, ports, and host groups.
The Pair Operation window allows you to perform the Continuous Access pair operations. All operations performed on the Pair Operation window have a common procedure. To perform any operation on the Pair Operation window: 1. 2. 3. 4. 5. 6. Select the desired CU grouping, CU, port, or host group in the tree. Note: When a CU grouping is selected, paircreate operations cannot be performed. Select the desired LU(s) or pair(s) in the list.
Figure 43 List on the Pair Operation Window The detailed volume (LU) information includes: • Volume icon: Indicates the status of volumes. • : SMPL. • : P-VOL. • : S-VOL. • VOL: Displays the port number, host group number, and LU number (LDKC:CU:LDEV) of the local volume in order. These numbers are separated by hyphens. Note: If # is added to the end of an LDEV number (for example, 00:00:3C#), the LDEV is an external volume.
• • • • Diff: The differential data setting (bitmap table managed by cylinder or track). CTG: Consistency group number (00-7F) of the pair (only for Asynchronous pairs). ErrLvl: Error level (group or LU) of the pair (only for Asynchronous pairs). Sync: During the copy process, the percentage of completion of the copy operation is displayed. During the split volume process, the concordance ratio of the specified volume is displayed.
CT Group: Allows you to select the consistency group (or all groups) to be displayed. This applies only to Asynchronous pairs. MCU-RCU Path: Displays the path type. You are not allowed to set this option with the current microcode version. CLPR: Allows you to select the CLPR (or all CLPRs). Internal/External VOL: Allows you to select the volume type, internal or external (or all types), to be displayed.
Vol Status Sub S/N ID Port Gr LUN Vol Port Gr(Name) LUN CTG EL Prio Sync CLPR CL1-A 00(Grp1A00) 001 00:00:00 SMPL : 00:CLPR0 12345 0001 CL1-A 01 001 00:1F:1E CL1-A 00(Grp1A00) 002 00:00:01 PAIR 032 100 01:CLPR1 CL1-B 02(G-0102) 003 00:00:02 PAIR 12345 0001 CL1-A 01 002 00:1F:1D 02:CLPR2 0C GRP (1) (2) (3) (4) (5) (6) (7) (8) (9) (10)(11) (12) (16) (17)(18)(19) (20) Type Fence Sync(P) Data Diff Cylinder Asyn(S) Never Cylinder (13) (14) (15) (1) Port number (8) O
Figure 46 Paircreate Dialog Box for Synchronous Pairs Figure 47 Paircreate Dialog Box for Asynchronous Pairs • P-VOL: Displays the port number, GID, LUN, CLPR number, and CLPR name of the selected LU(s). If you selected more than one P-VOL, the P-VOL with the lowest LUN is displayed.
• • • • • • volume. For details on external volumes, see the HP StorageWorks XP24000 External Storage Software User’s Guide. S-VOL: Allows you to select the S-VOL(s) for the new pair(s). If you selected more than one P-VOL, select the S-VOL for the P-VOL being displayed. The S-VOLs for the rest of the P-VOLs are automatically assigned according to the LUN.
1. At the remote site: a. Make sure that the LU(s) which will be the S-VOL(s) are offline from all hosts. b. Connect to the storage system which will be the RCU for the new pair(s), and log on with Administrator or Continuous Access write access. c. Make sure that the RCU remote copy ports are configured (RCU target port). See “Configuring the Host Interface Ports” on page 70 for instructions on configuring the ports. 2. At the main site: a.
10. To start the operation(s), click the Apply button. The MCU will start the initial copy operations according to the initial copy priority and the maximum initial copy activities setting on the System Option window. If one or more operation(s) did not start normally, the preview list displays only the operation(s) that did not start normally. An error code is displayed on the Error Code column in the preview list. To display an error message, select one LU, right-click, and click Error Detail.
P-VOL of Pair Priority LUN 03 1 LUN 05 2 LUN 00 3 LUN 04 4 LUN 01, 02 5 The MCU will start the initial copy operations for LUNs 003, 005, 000, and 004 immediately; then start LUN 001 when one of the first four initial copy operations is complete; and then start LUN 002 when the next initial copy operation is complete.
Figure 48 Change Pair Option Dialog Box (Synchronous and Asynchronous) • Volume: Port - GID (host group number) - LUN of the selected volume. Note: If # is added to the end of an LDEV number (for example, 00:00:3C#), the LDEV is an external volume. For details on external volumes, see the HP StorageWorks XP24000 External Storage Software User’s Guide. • P-VOL Fence Level: Select the fence level for the new pair(s).
4. Right-click, and click Change Pair Option to open the Change Pair Option dialog box (see Figure 48 on page 111). 5. On the Change Pair Option dialog box, select the desired pair option for the selected pair(s), and click Set to close the Change Pair Option dialog box. The preview list displays the requested change pair option operation(s). 6. Verify the requested operation(s) in the preview list.
Figure 49 Detailed Information Dialog Box P-VOL and S-VOL: • • • • Port - GID - LUN (lowest LDEV number for a LUSE pair). Device emulation type. Capacity in MB (to two decimal places). The number of blocks. Note: If # is added to the end of the number for an LDEV (for example, 00:00:3C#), the LDEV is an external volume. For details on external volumes, see the HP StorageWorks XP24000 External Storage Software User’s Guide.
P-VOL Fence Level (sync only): Never, Data, or Status (see “Pair Options” on page 110). S-VOL Write: Enabled or disabled for this pair (enabled only when the pair is split). Pair Established: Date and time that the pair was created. Last Updated: Date and time that the pair status was last updated. Pair Copy Time: Time that was taken to copy the pairs. Note: The time that is shown in Pair Copy Time differs from the time that is shown in Copy Time on the History window. To create a pair: 1.
Figure 50 Pairsplit-r Dialog Box (Synchronous and Asynchronous) The pairsplit options are: • Volume: Port - GID - LUN of the selected volume. Note: If # is added to the end of an LDEV number (for example, 00:00:3C#), the LDEV is an external volume. For details on external volumes, see the HP StorageWorks XP24000 External Storage Software User’s Guide. • S-VOL Write (default = disabled): • Enable: The S-VOL of this pair will accept read and write I/Os while the pair is split.
• Suspend Range: Group or LU. Default = Group when one pair in each group is selected. Default = Volume when two or more pairs in a group are selected. Group: All pairs in the same consistency group(s) as the selected pair(s) will be split. You must select only one pair in each consistency group. LU: Only the specified pair(s) will be split, even if the error level of the pair is Group.
WARNING: Do not use the P-VOL failure suspend kind option if the P-VOL is required for system operation. Make sure to use the S-VOL suspend kind option, so that the P-VOL continues accepting I/Os. 7. To start the operation(s), click the Apply button. If one or more operation(s) did not start normally, the preview list displays only the operation(s) that did not start normally. An error code is displayed in the Error Code column in the preview list (see Figure 50 on page 115).
Figure 51 Pairresync Dialog Box for Synchronous and Asynchronous The pairresync options are: • P-VOL: Port - GID - LUN of the selected volume. Note: If # is added to the end of an LDEV number (for example, 00:00:3C#), the LDEV is an external volume. For details on external volumes, see the HP StorageWorks XP24000 External Storage Software User’s Guide. • P-VOL Fence Level (Sync only): If desired, you can change the fence level of the pair(s).
estimate whether or not the I/O load is heavy from the rate of sidefile cache (around 30%) or, if you cannot see the sidefile cache rate, from the frequency of host I/O. The resynchronize pair operations should be performed under light I/O load conditions. • Error Level: If desired, you can change the error level of the pair(s). This option is available only when the LU Resume Range option is selected. See “Pair Options” on page 110 for further information on the error level option.
Releasing Continuous Access Pairs A Continuous Access pair should be released from the MCU only when it is no longer necessary to maintain a remote copy of the P-VOL. When a Continuous Access pair is released from the MCU, the MCU stops all update copy operations for that pair and changes the pair status of the P-VOL and S-VOL to SMPL. After a Continuous Access pair is released, the MCU continues to accept all subsequent write I/O operations to the P-VOL and will not keep track of the P-VOL updates.
Figure 52 Pairsplit-S Dialog Box for Synchronous and Asynchronous Pairs Note: If you select a pair from the volume list and change the settings, and if you use a drop-down list to set blank to a parameter, the parameter takes the default value for each pair. If you select the settings from the preview list before applying the changed settings, and if you use a drop-down list to set blank to a parameter in the Pairsplit-S dialog box, the parameter value in the preview list will not be changed.
pair in each consistency group. Caution: Do not use this option when releasing pairs at the RCU during a disaster recovery. Note: If you release (pairsplit-S) the Continuous Access Asynchronous pair from the RCU with the Group option, while the P-VOL continues accepting I/Os, the Continuous Access Asynchronous pair is forcibly suspended. This suspend is due to the S-VOL failure (not user-requested). This status is temporary, and will change to SMPL finally.
Note: To restart a pair which was released from the RCU, first release the pair from the MCU, and then restart the pair using the appropriate initial copy option (Entire Volume or None). Using Continuous Access for Data Migration and Duplication Data Migration Using Continuous Access Synchronous Continuous Access Synchronous can be used for device or workload migration with minimal impact to host applications.
Point-in-Time (PiT) Data Duplication Using Continuous Access Asynchronous Continuous Access Asynchronous enables you to make Point-in-Time (PiT) duplicates of groups of volumes. The Continuous Access Asynchronous Group and Drain pairsplit options can be used together to create a PiT copy, relative to an application, of an entire Continuous Access Asynchronous consistency group of volumes. To produce a PiT duplicate of an existing Continuous Access Asynchronous consistency group: 1.
Planned Outage of the RCU or Remote Copy Connection You must split all affected Continuous Access pairs prior to a planned outage of an RCU or of a remote copy connection component (for example, switch or channel extender). If you do not split the pairs first, the MCU(s) will detect the communications failure, suspend all affected pairs, and generate SIMs reporting the failures. To perform a planned outage of a Continuous Access RCU or remote copy connection component: 1.
3. Perform your usual procedure for recovering data from a pinned track. See the pinned track recovery procedures for your OS, or contact your HP service representative for assistance in recovering the pinned track. 4. Restart the pair using the Paircreate dialog box, and make sure to use the Entire Volume initial copy option. Note: Make sure to specify the pair for which the pinned track recovery operation was performed.
6 Usage Scenarios Using Continuous Access for Disaster Recovery Operations The type of disaster and the status of the Continuous Access pairs will determine the best approach for disaster recovery. For example, if all Continuous Access pairs are in the PAIR state when a total system failure occurs at a single point in time, the S-VOLs are current and recovery is straightforward.
Table 23 Effect of the Fence Level Setting on a Continuous Access P-VOL Write I/O operations to the P-VOL will be (On Each Fence Level Setting): Data Status Never The update copy operation failed, and the MCU was able to change the status of the S-VOL to PSUE. REJECTED Accepted Accepted The update copy operation failed, and the MCU was NOT able to change the status of the S-VOL to PSUE. REJECTED REJECTED Accepted Type of Failure Data.
Data(V) Data(V) Log(V) Log(IV) Primary volume Secondary volume Figure 53 Relationship Between Log File and Data File in PAIR Status Since most UNIX file systems (excluding JFS and VxFS) have no journal files, the P-VOL fence level should be defined as Never. When a takeover by the S-VOL occurs, fsck is executed on the volume and the file system is cleaned up, even if the S-VOL is undefined at the secondary host.
Switching Operations to the Remote Site If a disaster or failure occurs at the primary site, the first disaster recovery activity is to switch your operations to the secondary site. The Continuous Access Synchronous S-VOLs are recovered individually based on the pair status and P-VOL fence level information for each pair. The Continuous Access Asynchronous S-VOLs are recovered based on the pair status and consistency status (at the RCU).
Table 24 Analyzing the Currency of Continuous Access Synchronous S-VOLs Status of S-VOL Fence Level Currency of S-VOL SMPL Data Status Never Inconsistent. This S-VOL does not belong to a Continuous Access pair. (Note: Even if you established a Continuous Access pair for this volume, you must regard this volume as inconsistent.) COPY Data Status Never Inconsistent. This S-VOL is not synchronized because not all tracks have been copied from the P-VOL yet.
Table 25 Analyzing the Consistency of Continuous Access Asynchronous S-VOLs Status of S-VOL PAIR COPY SMPL PSUE-Group PSUE-LU Usable for Recovery? Description No No No These states do not usually occur during Continuous Access Asynchronous disaster recovery because the RCU suspends all Continuous Access Asynchronous S-VOLs when communication with the MCU is lost. Continuous Access Asynchronous S-VOLs in these states should not be used for disaster recovery.
Resuming Normal Operations at the Primary Site Once the Continuous Access pairs have been established in the reverse direction, you are ready to resume normal operations at the primary (main) site. Remember that the Continuous Access terminology is now reversed: the original RCUs and S-VOLs (secondary site) are now the MCUs and P-VOLs, and the original MCUs and P-VOLs (primary site) are now the RCUs and S-VOLs. To resume normal operations at the primary site: 1. 2. 3. 4. 5. 6. 7. 8. 9.
Usage Scenarios
7 Troubleshooting General Troubleshooting Table 26 on page 136 provides general troubleshooting information for Continuous Access. Table 27 on page 137 provides troubleshooting information for RCU paths. Table 28 on page 140 provides troubleshooting information for suspended Continuous Access pairs (Synchronous and Asynchronous). Table 29 on page 141 provides troubleshooting information for Continuous Access Asynchronous suspension conditions.
Table 26 General Continuous Access Troubleshooting Error Corrective Action The Remote Web Console computer hangs, or Continuous Access operations do not function properly. Make sure that the problem is not being caused by the computer or Ethernet hardware or software, and restart the computer. Restarting the Remote Web Console computer does not affect storage system operations. Make sure that all Continuous Access requirements and restrictions are met (for example, same LU type).
Table 27 Troubleshooting RCU Path Status Problems Path Status Initialization Failed Communication Time Out Resource Shortage (MCU/RCU) Serial Number Mismatch Description Corrective Action The link initialization procedure to the RCU failed. Make sure that the MCU and RCU are physically and correctly connected. Make sure that you entered the correct RCU S/N and SSID and path parameters (port, link address, logical address).
Description Corrective Action Invalid Port The specified port is not configured as an initiator port, or this path already exists. Make sure the correct MCU port is configured as an initiator port and the correct RCU port is configured as an RCU target port. Make sure that you entered the correct RCU S/N and SSID and path parameters (port, link address, logical address). Delete the failed path. You may need to change the minimum paths setting or delete the RCU in order to delete the path.
Path Status Logical Blockade Program Error Description Corrective Action The MCU port does not work. Repair the port status on the MCU. The RCU port does not work. Repair the port status on the RCU. And then delete the path with Edit Path or Delete RCU, and add the path again with Edit Path or Add RCU. The path relay equipment does not work. Repair the path relay equipment. And then delete the path with Edit Path or Delete RCU, and add the path again with Edit Path or Add RCU.
Table 28 Troubleshooting Suspended Continuous Access Pairs Description Corrective Action The MCU detected an error condition at the RCU which caused the MCU to suspend the pair. The S-VOL suspend type is by MCU. Clear the error condition at the RCU or S-VOL. If you need to access the S-VOL, split the pair (pairsplit-r) from the MCU using the S-VOL write enable option. Resynchronize the pair (pairresync) from the MCU after the error condition is cleared.
Table 29 Resolving Continuous Access Asynchronous Suspension Conditions Classification Causes of Suspension SIM Recovery procedure MCU/RCU hardware Hardware redundancy has been lost due to some blockade condition. As a result, MCU-RCU communications, creating or receiving recordsets, or the staging or de-staging process could not complete. The pending recordset cannot be retained because one side of cache storage or shared memory has been blocked due to hardware failure.
XP24000 Remote Web Console Error Codes for a list of the error codes displayed on the Remote Web Console computer. The Delete RCU failed because the RCU still contains one or more pairs with the current MCU. Figure 54 Continuous Access Error Message for a Failed Delete RCU Operation SIM Report The storage system generates a SIM when it is necessary to notify the user of a possible service requirement for the storage system.
A Continuous Access Load Balancing and Sidefile Management and Control Asynchronous Remote Copy solutions, as applicable to Disaster Recovery (DR), protect operational environments by assuring data integrity and rapid recovery at an alternate location should the operational environment at the home site be disrupted. As with any implemented application or solution, impact to the operational environment must be minimal.
1. Allow direct control of the host impact metrics using a methodology called Load Balancing. Load balancing allows management of the thresholds for inducing host delay and for the degree of induced delay. 2. Use Business Copy to provide a tertiary Point-in-Time (PiT) copy in support of the DR/BC requirements. The PiT copy may be manually controlled at specified times or be automated on a continuing interval basis using HP NanoCopy.
B Acronyms and Abbreviations Table 30 Acronyms and Abbreviations Adr address ATM asynchronous transfer mode CCI RAID Manager CNT Computer Network Technology Corporation CU control unit DASD direct access storage device DB2 Database 2 DFSMS Data Facility Storage Management Subsystem DR/BC disaster recovery/business continuity DWL duplex write line ExSA extended serial adapters HBA host bus adapter I/O input/output IBM International Business Machines Corporation IMPL initial micro
RCU remote control unit RDC remote dual copy RIO remote IO SIM service information message SMPL simplex S/N serial number (also abbreviated as s#) SNMP simple network management protocol SSB sense byte SSID storage system identification S-VOL secondary volume SVP service processor sync synchronous s# serial number (also abbreviated as S/N) TC Continuous Access TCA Continuous Access Asynchronous TCz Continuous Access for Mainframe TCzA TrueCopy Asynchronous for Mainframe VOL
Index A audience, 9 CU, 15 currency of S-VOLs, 130 C D cache inflow control, 24 requirements for Continuous Access, 45 calling technical support, 142 communication time out (RCU status), 137 components, 14 Concurrent Copy, 25 configuring MCUs and RCUs for Continuous Access, 49 consistency group, 16, 25 operations on groups, 26 options, 26 requirements, 45 consistency status, 30 Continuous Access components, 14 copy modes, 19 data migration, 123 disaster recovery, 127 fibre remote copy connections, 47 pair
installation hardware, 46 requirements, 43 invalid port (RCU status), 138 L LDEV pair See Continuous Access pair LDKC, 15 logical disk controller, 15 logical unit, 44 LU, 44 M MCU powering off/on, 124 migration using Continuous Access, 123 N never (fence level), 128 NVS requirement for Continuous Access, 45 P P-VOL fence level, 127 read/write operations to, 19 pair See Continuous Access pair PAIR (pair status), 27 pair status, 27 COPY, 27 deleting, 29 deleting (Async), 27 PAIR, 27 PDUB, 28 PSUE/PSUS
U update copy operation, 19 W websites HP, 10 HP Subscriber’s Choice for Business, 10 product manuals, 9 XP24000 Continuous Access Software User and Reference Guide 149
