HP XP24000/XP20000 Continuous Access Software User Guide Abstract This guide explains how to use HP XP Continuous Access Software to protect information stored on HP XP24000/XP20000 disk arrays from local disaster by continuously copying local data across Fibre Channel connections to remote XP disk arrays.
© Copyright 2007, 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Overview of XP Continuous Access Software..................................................7 XP Continuous Access...............................................................................................................7 Feature Highlights.....................................................................................................................7 Business Benefits.......................................................................................................................
3 Preparing for XP Continuous Access Operations...........................................49 System Requirements...............................................................................................................49 Requirements and Restrictions for Using XP Continuous Access......................................................50 One-to-One Volume Copy Operations..................................................................................50 Logical Unit Types.................................
Optimizing XP Continuous Access Operations and Storage System Performance...........................113 Discontinuing XP Continuous Access Operations.......................................................................114 6 Performing XP Continuous Access Pair Operations......................................116 Preparing for XP Continuous Access Pair Operations.................................................................116 Pair Operation Window........................................................
Changing the Status of S-VOL When the RCU is Disconnected....................................................172 Glossary..................................................................................................173 Index.......................................................................................................
1 Overview of XP Continuous Access Software This chapter provides an overview of XP Continuous Access Software.
Business Benefits XP Continuous Access Software provides the following business benefits: • Supports your business continuity and disaster recovery efforts and plans. • Provides distance replication while maintaining application and data integrity. • Improves business resilience by enabling frequent, nondisruptive disaster recovery testing with an online copy of current and accurate production data. • Improves service levels by reducing planned and unplanned downtime of customer-facing applications.
2 About XP Continuous Access Operations This chapter describes XP Continuous Access operations.
Figure 1 XP Continuous Access Components for Fibre Channel Connection Storage Systems XP Continuous Access operations involve the primary (main) storage systems and the secondary (remote) storage systems (MCUs and RCUs). This document covers XP Continuous Access operations in which the main storage system is an XP24000/XP20000 disk array and the remote storage system is an XP24000/XP20000 disk array (or an XP12000/XP10000 disk array).
Table 2 XP Continuous Access Storage System Mode (continued) Mode Description remote I/O (RIO) from the MCU to the RCU and is not completed within 20 seconds. As the relevant pair will transit to the suspend status, the differential management for the subsequent update data to the relevant P-VOL is performed by the P-VOL, and the data is not copied to the S-VOL.
operations between the P-VOLs and S-VOLs. The MCU also manages the XP Continuous Access pair status and configuration information. • The RCU is the CU in the remote storage system that controls the S-VOLs of the XP Continuous Access pairs. The RCU assists in managing the XP Continuous Access pair status and configuration (for example, rejects write I/Os to XP Continuous Access S-VOLs). The RCU executes the remote copy operations issued by the MCU.
Synchronous Consistency Groups An XP Continuous Access Synchronous consistency group is a user-defined set of volume pairs. If you specify a consistency group for XP Continuous Access Synchronous pairs, you can issue a command for each group and can ensure the data consistency of pairs on each of the S-VOLs and the R-VOLs in the same group. XP Continuous Access Synchronous pairs or TrueCopy for Mainframe synchronous pairs can be registered in an XP Continuous Access Synchronous consistency group.
Asynchronous Consistency Groups An XP Continuous Access Asynchronous consistency group is a user-defined set of volume pairs across which update sequence consistency is maintained and ensured at the remote site. Each pair must be assigned to a consistency group. XP Continuous Access allows you to configure up to 128 consistency groups (00-7F) for each MCU and provides group-based operations for consistency groups (for example, split and resync group).
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. For more information on the preparation of disaster recovery, see “Using XP Continuous Access for Disaster Recovery Operations” (page 145).
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 host-failover functions.
NOTE: For further information on cylinder/track difference management, see “Difference Management” (page 19). 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.
the synchronous mode, the MCU starts the update copy operation when it receives any of the following: • A write command whose data length is short enough not to pass the track-end • Write data to the track-end whose total length is long enough to pass the track-end • Write data to the last track for the command No matter how long the write data is, update copy is executed for each track.
Continuous Access Suspend Types” (page 34) for further information on suspended XP Continuous Access Asynchronous pairs. The RCU does not allow an XP Continuous Access S-VOL to be online (mounted) during normal XP Continuous Access operations and rejects all host-requested write I/O operations for an S-VOL. The special XP Continuous Access S-VOL write enable option enables write access to an S-VOL while the pair is split (see “S-VOL Write Option” (page 19)).
◦ For OPEN-V: ( ( ( (Max. LBA ÷ 512) ÷ 15) ) + 1 The … symbols around a value indicate that the value should be rounded up to the next integer. The Max. LBA indicates the capacity of a volume and is measured in blocks.
To calculate the maximum number of pairs that you can create: The maximum number of pairs that you can create = ( ↓ (the total number of bitmap areas in the storage system ÷ Number of bitmap areas) ) The … symbols around a value indicate that the value should be rounded down to the former integer.
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. The parameter length and detailed specification of the XP Continuous Access Asynchronous channel command are different than for XP Continuous Access Synchronous RIOs. Ensure that your channel extenders are capable of supporting this command. For further details, contact your HP service representative.
Figure 3 Selecting and Settling XP Continuous Access Asynchronous Recordsets at the RCU * Since the record set has not yet arrived at the RCU, S2 does not have a time stamp now. 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.
within the user-specified offloading timer value, the RCU suspends all XP Continuous Access Asynchronous pairs and resets the channel-command-retry condition to avoid hanging up the MCU. Table 4 (page 24) describes the sidefile threshold values for XP Continuous Access Asynchronous operations and write pending operations and describes the actions that occur when each threshold is reached.
If an XP Continuous Access Synchronous pair and a TrueCopy for Mainframe synchronous pair are registered in the same group, you can ensure the data consistency between an XP Continuous Access Synchronous pair and a TrueCopy for Mainframe synchronous pair on each of the S-VOLs and the R-VOLs in the same group.
Figure 5 Splitting Processing When the Split Command is Issued and there are Volumes in the Consistency Group in I/O Processing If the split command (Pairsplit-r or YKSUSPND) is issued to a consistency group of XP Continuous Access Sychronous pair and if the I/O processing on some volumes in the consistency group has not finished, the split operation to the TrueCopy for Mainframe volume pair is executed for maintaining the data consistency on each of the S-VOLs and the R-VOLs after the track processing of
An option must be selected in Business Continuity Manager, although it is not necessary to select an option in RAID Manager. However, no options can make an XP Continuous Access volume prohibit Read access. For details of each option, see the HP RAID Manager User Guide or the HP Business Continuity Manager Software User Guide.
Table 7 (page 28) and Table 8 (page 28) show the status of XP Continuous Access Synchronous pairs and TrueCopy for Mainframe Synchronous pairs and the result of the pair splitting operation performed.
Table 8 Status of XP Continuous Access Synchronous Pairs and TrueCopy for Mainframe Pairs When Pair Splitting is Performed (Business Continuity Manager) (continued) Pair Status TrueCopy for Mainframe Synchronous Pairs All pairs are in Duplex status All pairs are in PSUS status Pairs in Duplex and Suspend status All pairs are in Suspend status XP Continuous Access XP Continuous Synchronous pairs: Access Synchronous PSUS pairs: PSUS XP Continuous Access Synchronous pairs: PSUS TrueCopy for Mainframe Sy
Group Options XP 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 XP Continuous Access Asynchronous copy operations.
Pair Status XP Continuous Access displays the pair status for each volume in the connected storage system. Table 9 (page 31) lists and describes the XP 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.
Table 9 XP Continuous Access Pair Status (continued) Pair Status Description Table 10 (page 33) for split types) and RCU record the data in P-VOL and S-VOL tracks that are updated as the differential data. P-VOL Access S-VOL Access Read/write; Read only • When you split a pair from the MCU, the MCU changes the status of the P-VOL and S-VOL to PSUS. When you split a pair from the RCU, the RCU changes the status of the S-VOL to PSUS.
XP Continuous Access Split Types (PSUS) Table 10 (page 33) lists and describes the XP Continuous Access split types. An XP Continuous Access pair can be split by the user at any time after the initial copy operation is complete. The user must split an XP Continuous Access pair to perform media maintenance on the P-VOL or to access the S-VOL (S-VOL write enable).
Table 11 Consistency Status for Split or Suspended XP Continuous Access Asynchronous S-VOLs Consistency Status (displayed at RCU) Description Volume This XP Continuous Access Asynchronous pair was probably split or suspended alone. Update sequence consistency between this S-VOL and other S-VOLs in this consistency group is not ensured. This S-VOL cannot be used for disaster recovery at the secondary site.
Continuous Access Asynchronous pair is resynchronized, the RCU sends the S-VOL differential data to the MCU, and the MCU merges the P-VOL and S-VOL differential data to determine which tracks are out-of-sync. This method ensures that all tracks that contain recordsets that were discarded at the RCU are resynchronized at this time. A suspended (or split) XP Continuous Access Asynchronous S-VOL has an additional status called the consistency status.
• The recordsets that reached the RCU, but have not yet been settled. After marking these S-VOL tracks as modified, the RCU discards these recordsets. • The P-VOL records updated by host-requested write I/Os after the pair was suspended (same function as for XP Continuous Access Synchronous pairs). If a recordset is lost in transmission from the MCU to the RCU, the MCU’s differential data ensures that the missing recordset is marked.
Table 14 Whether Non-XP Continuous Access and Non-XP Continuous Access Asynchronous Volumes Can Be Used as XP Continuous Access and XP Continuous Access Asynchronous Volumes (continued) Functions and Volumes Can the Volumes be Used as XP Continuous Access P-VOL? Can the Volumes be Used as XP Continuous Access S-VOL? Can the Volumes be Used as XP Continuous Access Asynchronous P-VOL? Can the Volumes be Used as XP Continuous Access Asynchronous S-VOL? P-VOL in PSUS status Yes Yes Yes Yes P-VOL in CO
Table 14 Whether Non-XP Continuous Access and Non-XP Continuous Access Asynchronous Volumes Can Be Used as XP Continuous Access and XP Continuous Access Asynchronous Volumes (continued) Functions and Volumes Can the Volumes be Used as XP Continuous Access P-VOL? Can the Volumes be Used as XP Continuous Access S-VOL? Can the Volumes be Used as XP Continuous Access Asynchronous P-VOL? Can the Volumes be Used as XP Continuous Access Asynchronous S-VOL? V-VOL No No No No Pool-VOL No No No No Sour
Table 14 Whether Non-XP Continuous Access and Non-XP Continuous Access Asynchronous Volumes Can Be Used as XP Continuous Access and XP Continuous Access Asynchronous Volumes (continued) Functions and Volumes Can the Volumes be Used as XP Continuous Access P-VOL? Can the Volumes be Used as XP Continuous Access S-VOL? Can the Volumes be Used as XP Continuous Access Asynchronous P-VOL? Can the Volumes be Used as XP Continuous Access Asynchronous S-VOL? Secondary data volume in PSUS status Yes No No No
Table 14 Whether Non-XP Continuous Access and Non-XP Continuous Access Asynchronous Volumes Can Be Used as XP Continuous Access and XP Continuous Access Asynchronous Volumes (continued) Functions and Volumes Can the Volumes be Used as XP Continuous Access P-VOL? Can the Volumes be Used as XP Continuous Access S-VOL? Can the Volumes be Used as XP Continuous Access Asynchronous P-VOL? Can the Volumes be Used as XP Continuous Access Asynchronous S-VOL? Yes Yes Yes Yes Volume to which a path is defined
Table 16 (page 41) shows the currency of the data on a shared XP Continuous Access/XP Business Copy volume based on XP Continuous Access and XP Business Copy pair status. For further information on XP Business Copy, see HP XP24000/XP20000 Business Copy Software User Guide. NOTE: HP recommends XP Business Copy for intra-storage system copy operations. If XP Business Copy is not installed, XP Continuous Access (Synchronous only) can be used to copy within the same storage system.
Figure 7 Shared XP Continuous Access P-VOL/XP Business Copy P-VOL • Figure 8 (page 42) shows an example of an XP Continuous Access S-VOL that also functions as an XP Business Copy P-VOL. This configuration allows you to use XP Business Copy to provide multiple backup copies of a single XP Continuous Access P-VOL.
Figure 9 Shared XP Continuous Access/XP Business Copy P-VOL with Shared XP Continuous Access S-VOL/XP Business Copy P-VOL • Figure 10 (page 43) shows an example of an XP Business Copy S-VOL that is also used as an XP Continuous Access P-VOL. This configuration requires that the XP Business Copy pair be established in duplex mode (PAIR) and then split (PSUS) before the XP Continuous Access pair is created.
Table 17 Access Attribute and Availability as a Volume of an XP Continuous Access Pair Access Attribute Availability as a Volume of an XP Continuous Access Pair P-VOL S-VOL Read/Write OK OK Read Only OK OK Protect OK OK S-VOL Disable OK NO Read Only and S-VOL Disable OK NO Protect and S-VOL Disable OK NO The availability of Data Retention Utility operations for changing the access attribute depends on the XP Continuous Access pair status. For details, see Table 18 (page 44).
For further information on CVS, see HP XP24000/XP20000 Virtual LVI/LUN (VLL) and Volume Shredder User Guide. Cache Residency Manager The volumes that are applied using Cache Residency Manager can be assigned to XP Continuous Access pairs, and Cache Residency Manager operations can be performed on XP Continuous Access P-VOLs and S-VOLs. For further information on Cache Residency Manager, see HP XP24000/XP20000 Cache Residency Manager User Guide.
system usage and performance data collected and displayed by Performance Monitor enables you to: • Identify the optimum timings to perform XP Continuous Access data duplexing operations (for example, during periods of light system I/O activity), • Determine the best locations for the XP Continuous Access S-VOLs (for example, in parity groups with less frequently accessed volumes to avoid bottlenecks of backend activity), • Monitor storage system performance during XP Continuous Access operations and du
volumes, see “Whether Non-XP Continuous Access and Non-XP Continuous Access Asynchronous Volumes Can Be Used as XP Continuous Access and XP Continuous Access Asynchronous Volumes” (page 36).
Restriction for Connecting with Former Model of Storage System When you connect the storage systems with the following combinations, the range you can specify for each model is restricted. • XP24000 and XP1024 disk arrays • XP24000 and XP12000 disk arrays When you connect XP24000 and XP1024 disk arrays, you may specify the range as shown in Table 20 (page 48).
3 Preparing for XP Continuous Access Operations This chapter describes the requirements for using XP Continuous Access Synchronous and provides instructions for installing the XP Continuous Access Synchronous hardware and software, and preparing the storage systems for XP Continuous Access Synchronous operations. Read this chapter before you start the operation of XP Continuous Access Synchronous.
• Remote Web Console software and XP Continuous Access license code(s): ◦ The Remote Web Console software is required for XP Continuous Access operations. The XP Continuous Access software is a component of Remote Web Console product. ◦ The XP Continuous Access license key code(s) are required to enable the XP Continuous Access option(s) on the storage system. Separate license codes are required for each storage system.
Logical Unit Types XP Continuous Access supports the basic LU types that can be configured on the storage system (for example, OPEN-3, OPEN-E, OPEN-8, OPEN-9, OPEN-L, OPEN-V). The XP Continuous Access software displays the LU type of the P-VOLs and S-VOLs. An XP Continuous Access pair must consist of LUs of the same type and capacity (for example, OPEN-3 to OPEN-3). Multiplatform volumes (for example, 3390-3A/B/C) cannot be assigned to XP Continuous Access pairs.
storage system cache should be configured to adequately support the XP Continuous Access remote copy workloads, as well as any local workload activity. Host Failover Software The storage system program products do not provide any host failover functions for disaster recovery. Host failover software is a critical component of any disaster recovery effort. When an MCU fails to maintain synchronization of an XP Continuous Access pair, the MCU generates sense information.
3. 4. 5. 6. HP Technical Support Representative: Make sure that the MCUs and RCUs are properly configured for XP Continuous Access operations (for example, cache and NVS). Make sure that the desired system option modes are enabled. Make sure that adequate cache is installed and available for any asynchronous operations (XP Continuous Access Asynchronous, XRC, and CC). You must also consider the amount of Cache Residency Manager data to be stored in cache when determining the required amount of cache.
Table 22 The Relationship between Link Speed and Maximum Distance for Best Performance Link Speed Maximum Distance for Best Performance 1 Gbps 10 km 2 Gbps 6 km 4 Gbps 3 km 8 GbPS 2 km For best performance of distances that are larger than the distances described in Table 22 (page 54), HP recommends installing FC-SW. Figure 11 Remote Copy Connection Configurations For Fibre Channel interface connections, you can use the same switches as ordinary switch connections.
To properly support the configuration for setting the host mode options, ensure the use of the HP-approved extender. No. Host mode options When to select this option? 49 BB Credit Set Up Option 1*1*2 In XP Continuous Access and in cases where a long distance between M and R (approximately 100km) and a Switch is not used and in other cases, if the number of BB Credits controlling the amount of transfer data on Fibre must be tuned. Use by combining with host mode option 50.
Figure 14 Interface Extender Connection * To set ports, use LUN Manager and set the port topology to: NL/FL port: Fabric on, FC-AL F port: Fabric on, Point-to-Point Adding or removing cache or shared memory When pair status of TC (synchronous/asynchronous/HAM) is COPY, neither cache nor shared memory can be added to or removed from the storage system.
2. 3. 4. 5. 6. the MCUs and RCUs correctly for your desired pairs and async groups. When you create the pairs, you need the port, GID (host group ID), and LUN of each volume. At the RCUs (that is, remote site), use the XP Continuous Access software to configure the Fibre Channel ports which are connected to the MCUs as RCU target ports (see “Configuring the RCU Target and Initiator Ports” (page 58)).
Figure 15 Configuring the RCU Target and Initiator Ports 58 Preparing for XP Continuous Access Operations
Figure 16 Adding the RCUs Configuring the MCUs and RCUs for XP Continuous Access Operations 59
Figure 17 Configuring the RCU Options Figure 18 Setting the Async Options 60 Preparing for XP Continuous Access Operations
Figure 19 Adding the Consistency Groups Configuring the MCUs and RCUs for XP Continuous Access Operations 61
4 Using the XP Continuous Access GUI This chapter describes the XP Continuous Access windows on Remote Web Console. XP Continuous Access Windows The XP Continuous Access windows (see Figure 20 (page 62)) display the XP Continuous Access information for the connected storage system and provide access to all XP Continuous Access functions and operations. The Quorum Disk Operation window is used with XP External Storage Access Manager Software.
The XP Continuous Access windows present six main windows: Pair Operation, RCU Operation, Asynchronous Operation, Usage Monitor, History, and System Option. Table 24 (page 63) shows the operations available for each window. To start the operations that you set on each XP Continuous Access function window, use the Apply button at the lower right of the XP Continuous Access window.
Table 24 XP Continuous Access Functions (continued) Window Menu Command Description Async Option Allows you to change the Async options. Usage Monitor window (see “Usage Monitor Window” (page 75) — Allows you to collect, view, and export I/O statistics using the Remote Copy Monitoring function. History Window (see “History Window” (page 76) — Allows you to view and export the operation history of the XP Continuous Access pairs.
The Pair Operation window displays: Item Description Tree Displays the connected storage system, the LDKC, the CU grouping, the CUs, the ports, and the host groups. Select the desired CU grouping, CU ( ), port ( ), or host group to display the LUs for that CU grouping, CU, port, or host group. You can only select one CU grouping, CU, port, or host group at a time. List Displays the detailed LU information for the selected item (storage system, CU, or port).
The detailed volume (LU) information includes the following: Item Description Volume icon Indicates the status of volumes. VOL Status • : SMPL • : P-VOL • : S-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. : SMPL. The volume is not currently assigned to an XP Continuous Access pair. When the initial copy is started by a paircreate operation, the volume status changes to COPY. : COPY.
Item Description Paired VOL Displays the port number, host group number, and LU number (LDKC:CU:LDEV) of the remote volume in this order. These numbers are separated by hyphens. Paired VOL displays the port number, the host group number, and LUN of the volume that you specified in the remote storage system when creating the pair.
Figure 23 Display Filter Dialog Box The Display Filter Dialog box displays: 68 Item Description Port Allows you to select the port (or all ports) to be displayed or to enter the port number directly. You can specify the port number with two characters. For instance, you can abbreviate CL1-A as 1A. You can also enter the port number in both lowercase and uppercase characters. GID Allows you to select the GID (or all GIDs) to be displayed. GID means host group number.
Item Description When PDUB is selected, simplex volumes are not displayed. Sub Status Allows you to select the consistency status of the Asynchronous pairs. Set button Applies your selections to the volume list and closes the Display Filter dialog box. The Reset button clears your selections and displays the default settings (ALL).
The RCU Operation window displays: Item Description Display buttons Allows you to select either the MCU&RCU display (default) or Port display for the RCU Operation window. Tree When you select the MCU&RCU display with the Display button, the tree displays the CUs of the connected storage system. Select and double-click the desired CU to display the MCU/RCU information for that CU. Select the desired RCU to display the SSID and path information for that RCU.
Select the desired CU to display the MCU/RCU information for that CU (see “MCU&RCU Display on the RCU Operation Window showing CU List” (page 72)). You can select only one CU at a time. The MCU/RCU information includes: Item Description CU CU number that is selected on the tree. If you select CU Free, Any is displayed. Type MCU or RCU. The MCU is displayed when the storage system that you are accessing is used as the RCU of the pair. S/N Serial number of the other CU of the pair (five digits).
Figure 25 MCU&RCU Display on the RCU Operation Window showing CU List Figure 26 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. Select the desired channel adapter to display the port information for that adapter (see Figure 27 (page 73)). Select the desired port type to display the port information for that port type. You can select only one channel adapter or port type at a time. The port information includes: Item Description Port Cluster and port number (CL1-A-CLG-R). Attribute: Port type Port type: initiator, target, RCU target, External, Initiator/External.
Figure 28 Asynchronous Operation Window The Asynchronous Operation window displays: Item Description Tree Allows you to display all consistency groups (except groups that are used for XP Continuous Access) belonging to LDKC#00 (default) or all consistency groups (except groups that are used for XP 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).
Item Description the lowest S/N is displayed). The LDKC number is also displayed next to the S/N. If the consistency group is not in use, this column is blank. • Paired ID: SSID (if there is more than one RCU, the storage system with the lowest SSID is displayed) or path group ID of the paired storage system. If the consistency group is not in use, this column is blank. • Other S/N: Exist: Indicates that there is more than one RCU for the group. If there is only one RCU, this column is blank.
The Usage Monitor window displays: Item Description Monitoring Switch Allows you to see whether monitoring is on or off. Monitoring Switch displays Enable when monitoring is on, and displays Disable when monitoring is off. When monitoring is stopped, the usage monitor graph is closed. The usage monitor graph can only be displayed when monitoring is running. Gathering Interval Allows you to see the data collection interval for usage monitoring.
Figure 30 History Window The History window displays: Item Description Status Displays the current status of the history file: • No history file exists: The history file does not exist. • Reading a history file failed: A failure occurred while referring to the history file. • Updating ... n (%): Updating the history file is now in progress. n (%) indicates the progress (in %) of the update process for the history file. • Complete: Updating the history file has been completed.
Item Description displayed on the History window. For further information on the settings for accessing local files, see the HP XP24000/XP20000 Remote Web Console User's Guide. The dates and times displayed on the History window are the XP24000/XP20000 SVP date/time, which may or may not correspond to the local time or host time. Previous and Next buttons The list displays up to a maximum of 16,384 operations at a time. Use these buttons to display the previous or next 16,384 operations.
NOTE: • For XP Continuous Access pairs consisting of LUN Expansion (LUSE) volumes, the number of Pair Suspend (Failure) rows in the history list does not correspond to the number of LDEVs in the LUSE volume. For LUSE volumes with three or more LDEVs, only two rows showing Pair Suspend (Failure) are displayed. • Even if several errors occur at the same time, only two rows showing Pair Suspend (Failure) are displayed. • History information older than seven days is automatically deleted.
Item Description PreviewList 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. Operation Displays the status of the process in progress. The following statuses of operation are displayed: • No Operation • Set the System Option • Set the CU Option 80 Apply button Applies the settings in the System Option window to the storage system.
5 Performing XP Continuous Access Configuration Operations This chapter provides instructions for performing XP Continuous Access configuration operations.
the appropriate XP Continuous Access settings and options for your operational environment and also by addressing conditions that can affect storage system performance. • Discontinuing XP Continuous Access operations. For “Discontinuing XP Continuous Access Operations” (page 114), you must perform the required operations (for example, pair release, RCU deletion, port re-configuration, etc.) in a specific order to ensure smooth operations and avoid command rejects and error conditions.
For the Port display, the menu commands are: • Initiator: Allows you to change the selected fibre port(s) to initiator ports. • 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. 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.
Access software. For details on the port to which an initiator/external mix mode is set, see the HP XP24000/XP20000 External Storage Software User's Guide. IMPORTANT: Before changing a Fibre Channel port to an initiator port, disconnect the port from the host, release all affected XP Continuous Access pairs, delete all paths from the port to the MCU (if RCU target), and then remove all channel paths to the port.
Figure 32 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.
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 (XP24000/XP20000 disk array), you can select a CU number from 00 to FE. • When the specified controller ID is 4 (XP12000/XP10000 disk array), you can select a CU number from 00 to 3F. SSID: Allows you to enter the SSID(s) of the RCU being added.
8. 9. Verify the requested operation(s) displayed in the preview list. To change one or more operations, select the operation(s), right-click the preview list, and click Modify. To remove 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.
Figure 33 Add RCU Operation − Fibre Channel Interface Changing the RCU Options The RCU Option dialog box (see Figure 34 (page 88)) allows you to set the RCU options for the connected MCU. The RCU options apply to all MCU CUs and to all RCUs connected to the MCU. The RCU Option dialog box is presented during the add RCU process, and can also be opened by right-clicking on the RCUs and clicking the RCU Operation > Change RCU Option command.
number, the MCU suspends all affected XP Continuous Access (and TrueCopy for Mainframe) pairs to prevent hosts from adversely affecting performance due to the inadequate number of paths. If you enter a number larger 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.
The Initial copy response time is the response time required for multiple initial copy operations. You can use the following formula to get the initial copy response time. To get the time, you should use the 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.
To cancel all operations, select all the operations in the preview list, right-click, and click the Delete command, or click the Cancel button. 5. 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.
6. 7. 8. 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. To start the operation(s), click the Apply button.
Figure 36 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.
Viewing RCU Status The RCU Status dialog box (see Figure 37 (page 95)) displays the detailed status information for the selected RCU. “Logical Path Status” (page 97) describes the path status descriptions. See “General Troubleshooting” (page 152) for troubleshooting information for MCU-RCU paths. 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.
Figure 37 RCU Status Dialog Box (Top: for CU Free, Bottom: for the CU excepting CU Free) RCU Operations 95
• 96 Path List: ◦ No.: Path number (path list item number). ◦ Path Status: Path status. “Logical Path Status” (page 97) contains the path status descriptions. ◦ MCU Port: Port number of the MCU. ◦ 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.
• Round Trip Time: Delay time because of remote I/O according to the connection devices and the distance of the line between the MCU and RCU. • Check box, Refresh the RCU Operation window after this dialog box is closed: To refresh the RCU Operation window after closing the RCU Status dialog box, click the check box. By default, the check box is not selected. The Refresh button refreshes the status information. The Close button closes the RCU Status dialog box.
4. 5. 6. Right-click the RCU(s), click RCU Operation, and then click Delete RCU. When a confirmation message appears, click OK to delete the RCU, or click Cancel to cancel your request to delete the RCU. The preview list displays the requested delete RCU operation(s). Verify the requested operation(s) displayed in the preview list. To remove one or more operations, select the operation(s) from the preview list, right-click, and click Delete.
Setting the Asynchronous Copy Options The Async Option dialog box (see Figure 38 (page 99)) allows you to set and modify the XP Continuous Access Asynchronous copy option parameters for the connected storage system. To open the Async Option dialog box, right-click the CT groups, and click the Async Option command. The async options apply to the entire physical control unit, including all XP Continuous Access P-VOLs and S-VOLs behind the control unit.
cache that is used for async recordsets reaches the specified value of the threshold, the MCU controls the cache 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 cache inflow.
Figure 39 Add CT Group Dialog Box MCU-RCU Path: Indicates the path type (fibre) for the remote copy connections. Currently, you cannot change the path type. 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.
7. Verify the requested operation(s) displayed in the preview list. To change one or more operations, select the operation(s) from the preview list, right-click, and click Modify. To remove one or more operations, select the operation(s) from the preview 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 Cancel button. 8. To start the operation(s), click the Apply button.
To change the group options for one or more groups: 1. Make sure that all pairs in the group(s) have been split (Pairsplit-r), so that you can change the group options. See “Splitting XP Continuous Access Pairs” (page 130) for instructions on splitting pairs. 2. Select the LDKC where the desired consistency group belongs, or select Used from the tree in the Asynchronous Operation tab to display the existing consistency groups in the list. 3.
Figure 41 CT Group Status Dialog Box • CT Group: Group number of the selected consistency group. • This CU Type: CU type (MCU or RCU) of the selected consistency group. • LDKC: The number of the LDKC where the consistency group belongs. • CLPR: The number and name of the CLPR to that the volumes forming pairs belong. • S/N, ID: Serial number and SSID of the CUs or Path Gr. of the selected consistency group. The LDKC number is also displayed enclosed in parentheses to the right of the CU number.
group. The Refresh button refreshes the status information. The Close button closes the CT Group Status dialog box. Deleting Consistency Groups A consistency group can be deleted only from the MCU and only if the MCU does not contain any P-VOLs still assigned to the group. Deleting a consistency group from an MCU does not affect the consistency groups registered at other MCUs. The RCU automatically deletes a consistency group when the last pair in the group is released.
on the y-axis exceeds 10,000,000, the value is displayed in exponential notation (for example, 1E7 = 1×107 = 10,000,000; 2E8 = 2×108 = 200,000,000). The Update field displays the most recent data sample time for the data on the graph. To display the usage monitor graph: 1. Make sure that usage monitoring is running (Monitoring Switch = Enable). The usage monitor graph can only be displayed when monitoring is on. 2.
Figure 42 Selecting the Data for the Usage Monitor Graph Table 28 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.
Table 28 Remote Copy I/O Statistics (continued) Statistic 1 Description Update copy Update copy RIO count Number of update copy remote I/Os. Average transfer rate (kB/s) Average transfer rate (kB/sec) for update copy remote I/Os. Average response (ms) Average response time (msec) for update copy remote I/Os. Asynchronous Copy Asynchronous RIO count Number of asynchronous update copy remote I/Os. Total number of recordsets Number of asynchronous recordsets.
Table 28 Remote Copy I/O Statistics (continued) Statistic 1 Description Cache SideFile% Sidefile usage ratio (%). You can select only when you click LU Total or CLPR in the Select LU on the Display Item dialog box. 1 2 The RIO statistics include both XP Continuous Access and TrueCopy for Mainframe remote copy operations (for example, Async RIO Count = XP Continuous Access Asynchronous RIOs + TrueCopy Asynchronous for Mainframe RIOs).
Changing the Option Settings of Storage System The information for the storage system's option settings information is displayed if you select Subsystem Option from the tree on the System Option window. Figure 43 Option Settings List for the Storage System • Activities: Number of volumes in concurrent initial copy operations (1 to 512). • Activities (CU): Shows whether the CU-by-CU setting of concurrent initial copy operations will be enabled or disabled.
Figure 44 System Option Dialog Box The Maximum Initial Copy Activities setting specifies the number of concurrent initial copy and resync operations. You can set a number from 1 to 512. The default setting is 64 volumes. XP Continuous Access initial copy activities can impact the performance of the main site, depending on the amount of I/O activity and the number of pairs being registered at the same time.
Figure 45 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 46 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 29 Optimizing XP 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.
2. 3. 4. 5. 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 XP Continuous Access volumes before continuing. Delete the XP Continuous Access Asynchronous group(s) from the MCU(s) . The RCU automatically deletes a group when all pairs in the group have been released. Delete the RCUs (see “Deleting an RCU” (page 97)). Check each CU of each MCU to make sure that all RCUs have been deleted before continuing.
6 Performing XP Continuous Access Pair Operations This chapter provides instructions for performing XP Continuous Access pair operations • “Preparing for XP Continuous Access Pair Operations” (page 116) • “Pair Operation Window” (page 117) • “XP Continuous Access Snapshot Function” (page 118) • “Creating XP Continuous Access Pairs” (page 119) • “Initial Copy Options” (page 124) • “Pair Options” (page 125) • “Changing Pair Options” (page 125) • “Viewing XP Continuous Access Pair Status” (page
You can start creating the XP Continuous Access pairs as soon as you have: • Identified the volumes (LUs) that will become the XP Continuous Access P-VOLs and S-VOLs • Ensured that all system and XP Continuous Access requirements have been met • Completed hardware and software installation • Configured the MCUs and RCUs for XP Continuous Access operations If you will be using the XP Continuous Access software to perform XP Continuous Access operations, the MCU of each XP Continuous Access pair must
Pairsplit-r: Allows you to split (suspend) pairs. Pairresync: Allows you to resynchronize pairs. Change Pair Option: Allows you to change the pair options. The availability of the commands (enabled/disabled) depends on the status of the LU(s) or pair(s) selected in the list. 4. 5. 6. Click the command for the desired operation, use the dialog box to perform the operation, and close the dialog box. The preview list displays the requested operation(s). Verify the specified pair operation(s).
Example of an XP Continuous Access Snapshot File The following is an explanation of the fields: (1) Port number (2) GID and host group name (3) LU number (4) LDEV number (5) Status of the pair (6) Suspend sub status (7) Serial number of other CU (8) Other CU SSID or Path Group ID (9) Port number of other LU (10) GID of other LU (11) LU number of other LU (12) LDEV number of other LU (13) Pair mode (14) Fence level (15) Differential data setting (16) Consistency group number (17) Error level (18) Copy prio
Figure 48 Paircreate Dialog Box for Synchronous Pairs 120 Performing XP Continuous Access Pair Operations
Figure 49 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. If the pound or gate symbol (#) is added to the end of the device ID (00:00:3C #, for example), the LDEV is an external volume. For details on external volumes, see the HP XP24000/XP20000 External Storage Software User's Guide.
• • P-VOL Fence Level (sync only): Select the fence level for the new pair(s) (default = Never). The fence level determines the conditions under which the MCU will reject write operations to the P-VOL. ◦ Never: The P-VOL will never be fenced. ◦ Data: The P-VOL will be fenced when the MCU cannot successfully execute an update copy operation for any reason. ◦ Status: The P-VOL will be fenced only if the MCU is not able to change the S-VOL status to suspended when an update copy operation fails.
a. b. c. 3. 4. Connect to the storage system that will be the MCU for the new pair(s), and log on with Administrator or XP Continuous Access write access. Make sure that the MCU remote copy ports are configured to the initiator port. Make sure that the correct RCU CU (contains the LUs that will be the S-VOLs) has been added to the correct MCU CU (contains the LUs that will be the P-VOLs).
list. To display an error message, select one LU, right-click, and click Error Detail. After you see the error message, click OK to close the error message. 11. On the Pair Operation window, verify that the paircreate operations are displayed correctly (COPY status) in the list.
LUN 04 4 LUN 01, 02 5 The MCU immediately starts the initial copy operations for LUNs 003, 005, 000, and 004, immediately; starts LUN 001 when one of the first four initial copy operations is complete, and then starts LUN 002 when the next initial copy operation is complete. If more XP Continuous Access pairs are created, the MCU also prioritizes the initial copy operations by the time requested so that all pairs in the first group are started before any pair in the next group is started.
Operation tab, select a CU grouping, CU, port, or host group from the tree, select P-VOL from the list, right-click, and click the Change Pair Option command. Figure 50 Change Pair Option Dialog Box (Synchronous and Asynchronous) • Volume: Port - GID (host group number) - LUN of the selected volume. If the pound or gate symbol (#) is added to the end of the device ID (00:00:3C #, for example), the LDEV is an external volume.
1. 2. 3. Connect to the MCU of the pair(s) for which you want to change the pair option, and open the XP Continuous Access main window. In the tree, select a port, host group, desired CU, or upper CU grouping. In the list, select the pair(s) for which you want to change the pair option. When a port is selected in the tree, the pair(s) can be selected from the current volume list. Select either XP Continuous Access Synchronous pairs or XP Continuous Access Asynchronous pairs (not both).
Figure 51 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. If the pound or gate symbol (#) is added to the end of the device ID (00:00:3C #, for example), the LDEV is an external volume. For details on external volumes, see the HP XP24000/XP20000 External Storage Software User's Guide.
Pair Status: SMPL, COPY, PAIR, PSUE, PSUS, PDUB, Suspending, Deleting, or SSWS. For information on the Pair Status, see “Pair Status” (page 31). SSWS is also relevant to the XP External Storage Access Manager pair. If the pair is split or suspended, the split/suspended type is also displayed. Pair Synchronized: Progress of the initial copy operation (percentage and progress bar). If the pair is split or suspended, the percentage of synchronized data in the corresponding volume is displayed.
• Check box, Refresh the Pair Operation window after this dialog box is closed: To refresh the Pair Operation window after closing the Detailed Information dialog box, click the check box. By default, the check box is not selected. • The Previous button displays the pair status information for the previous pair in the list (the pair in the row above). The Next button displays the pair status information for the next pair in the list (the pair in the row below).
Figure 52 Pairsplit-r Dialog Box (Synchronous and Asynchronous) The pairsplit options are: • Volume: Port - GID - LUN of the selected volume. If the pound or gate symbol (#) is added to the end of the device ID (00:00:3C #, for example), the LDEV is an external volume. For details on external volumes, see the HP XP24000/XP20000 External Storage Software User's Guide.
merged at the MCU. This option is available only when the selected volume is an XP Continuous Access P-VOL. ◦ • • Disable: The S-VOL of this pair only accepts read I/Os while the pair is split. Suspend Kind (default = S-VOL): ◦ S-VOL: The P-VOL accepts all subsequent write I/O operations, and the MCU keeps track of updates while the pair is split. Subsequent write I/O operations to the P-VOL will be accepted or rejected depending on the fence level of the pair.
1. Connect to the MCU or RCU of the pair(s) to be split, open the XP Continuous Access main window, and click the Pair Operation tab. You do not need to vary the P-VOL(s) offline. To use Enable for S-VOL Write option, you must connect to the MCU and select the P-VOL of the pair(s). 2. 3. In the tree, select the port, host group, desired CU, or the upper CU grouping. In the list, select the XP Continuous Access pair(s) that you want to split.
Resynchronizing XP Continuous Access Pairs While an XP Continuous Access pair is split or suspended, the MCU does not perform any update copy operations to the S-VOL. • For a split/suspended XP Continuous Access Synchronous pair, the MCU may or may not continue accepting write I/Os for the P-VOL depending on the P-VOL fence level pair option and suspend kind pairsplit option (if user-requested) .
Figure 53 Pairresync Dialog Box for Synchronous and Asynchronous The pairresync options are: • P-VOL: Port - GID - LUN of the selected volume. If the pound or gate symbol (#) is added to the end of the device ID (00:00:3C #, for example), the LDEV is an external volume. For details on external volumes, see the HP XP24000/XP20000 External Storage Software User's Guide.
If an X mark is added to the end of the device ID (00:00:3C X, for example), the LDEV that the number indicates is a Thin Provisioning virtual volume. For details on virtual volumes, see the HP XP24000/XP20000 Thin Provisioning Software User's Guide. • P-VOL Fence Level (Sync only): If desired, you can change the fence level of the pair(s). See “Pair Options” (page 125) for further information on the fence level pair option.
as modified, so that the MCU will perform the equivalent of an entire initial copy operation when the pairs are resynchronized. 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.
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 an XP 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. An XP Continuous Access pair should be released from the RCU only for disaster recovery (see “Usage Scenarios” (page 144)).
Figure 54 Pairsplit-S Dialog Box for Synchronous and Asynchronous Pairs Volume: Port - GID - LUN of the selected volume. If the pound or gate symbol (#) is added to the end of the device ID for example, 00:00:3C #, the LDEV is an external volume. For details on external volumes, see the HP XP24000/XP20000 External Storage Software User's Guide. If an X mark is added to the end of the device ID for example, 00:00:3C X, the LDEV that the number indicates is a Thin Provisioning virtual volume.
Asynchronous Parameters: • Delete Range: The delete range option simplifies disaster recovery operations for XP Continuous Access Asynchronous consistency groups at the RCU (secondary (remote) storage system). ◦ Group (MCU or RCU): All pairs in the same consistency group(s) as the selected pair(s) will be released, regardless of the pair status and consistency status. You must select only one pair in each consistency group.
6. Verify the requested operation(s) in the preview list. Make sure that the pair release options for each pair are correct. To change one or more operations, select the operation(s) from the preview list, right-click, and click Modify. To remove one or more operations, select the operation(s) from the preview 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. 7.
Planned Outage of the RCU or Remote Copy Connection You must split all affected XP 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 an XP Continuous Access RCU or remote copy connection component: 1.
3. 4. Perform your usual procedure for recovering data from a pinned track. See the pinned track recovery procedures for your OS, or contact your HP Technical Support service representative for assistance in recovering the pinned track. Restart the pair using the Paircreate dialog box, and make sure to use the Entire Volume initial copy option. Make sure to specify the pair for which the pinned track recovery operation was performed.
7 Usage Scenarios This chapter describes several usage scenarios for XP Continuous Access. • “Data Migration Using XP Continuous Access Synchronous” (page 144) • “Point-in-Time (PiT) Data Duplication Using XP Continuous Access Asynchronous” (page 145) • “Using XP Continuous Access for Disaster Recovery Operations” (page 145) Contact your HP service representative for further information on Business Continuity and Disaster Recovery Solutions from HP.
e. (page 124)). If the original P-VOL(s) will be temporarily unavailable for update copy operations, you can split the new pair(s) (pairsplit-r) so that the new MCU keeps track of the changes. Start the applications with the S-VOL(s). When the original P-VOL(s) become available, you can resynchronize the pair(s) (see “Resynchronizing XP Continuous Access Pairs” (page 134)).
3. Use the appropriate combination of XP Continuous Access options for disaster recovery: • XP Continuous Access Asynchronous offloading timer option and Time Out (Copy Pending) group option. The Time Out (Copy Pending) group option can be used to limit the time duration during which updates may be lost. The offloading timer value should be less than the HBA timeout value.
capability is essential if this fence level setting is used. For disaster recovery, the currency of the S-VOL is determined by using the sense information transferred via host failover or by comparing the S-VOL contents with other files confirmed to be current. Setting the Fence Level When a takeover by the S-VOL occurs as shown in Figure 55 (page 147) (two errors have already occurred), Data(V) remains in the rollback process at the secondary host, and full recovery cannot be performed.
The XP Continuous Access Asynchronous consistency status (group or volume) can be useful when performing this detection and retrieval. Since this detection/retrieval process can take a while, your disaster recovery scenario should be designed so that detection/retrieval of lost updates is performed after the application has been started at the secondary system.
of these S-VOLs. The currency of these S-VOLs can be determined by using the sense information transferred via the host failover, or by comparing the contents of the S-VOL with other files that are confirmed to be current (for example, database log files). These S-VOLs should be recovered using the files that are confirmed to be current. Actual data recovery must be done using recovery point data in the database redo log.
Table 33 Analyzing the Consistency of XP Continuous Access Asynchronous S-VOLs Status of S-VOL Consistency Status Usable for Recovery? Description PAIR -- No These states do not usually occur during XP Continuous Access Asynchronous disaster recovery because the RCU suspends all XP Continuous Access Asynchronous S-VOLs when communication with the MCU is lost. XP Continuous Access Asynchronous S-VOLs in these states should not be used for disaster recovery.
8. to send XP Continuous Access remote copy operations to the original MCUs to bring the original P-VOLs up to date. At the remote site, establish the same XP Continuous Access Asynchronous groups and XP Continuous Access pairs in the reverse direction to synchronize the original P-VOLs with the S-VOLs. Make sure to use the Entire Volume initial copy option.
8 Troubleshooting General Troubleshooting Table 34 (page 152) provides general troubleshooting information for XP Continuous Access. “Troubleshooting RCU Path Status Problems” (page 153) provides troubleshooting information for RCU paths. “Troubleshooting Suspended XP Continuous Access Pairs” (page 155) provides troubleshooting information for suspended XP Continuous Access pairs (Synchronous and Asynchronous).
Table 34 General XP Continuous Access Troubleshooting (continued) Error Corrective Action If a communications error between the Remote Web Console computer and SVP occurs, see the HP XP24000/XP20000 Remote Web Console User's Guide for instructions. There is a pinned track on an XP Continuous See “Pinned Track Recovery for XP Continuous Access Access volume. Volumes” (page 142) on page “Pinned Track Recovery for XP Continuous Access Volumes” (page 142) for instructions.
Table 35 Troubleshooting RCU Path Status Problems (continued) Path Status Description Corrective Action the RCU to delete the path. Add the path/RCU using Edit Path or Add RCU. Fibre: Make sure that you entered the correct Controller ID, and that the Fibre Channel topology settings of the MCU and RCU ports are correct. Invalid Port The specified port is not configured as an initiator port, or this path already exists.
Table 35 Troubleshooting RCU Path Status Problems (continued) Path Status Description Corrective Action Program Error A program error is detected. Delete the path with Edit Path or Delete RCU, and add the path again with Edit Path or Add RCU. This path was not established. Delete the failed path. You may need to change the minimum paths setting or delete the RCU to delete the path. Then add the path/RCU using Edit Path or Add RCU.
Table 36 Troubleshooting Suspended XP Continuous Access Pairs (continued) Pair Applies to Description Status/Type Corrective Action transferred within the specified • Decrease the number of Async offloading timer. pairs, or 2. In case the system option mode 549 • Decrease the host I/Os. is ON, the suspend occurred due to the RIO completion waiting TOV. The 2. Eliminate the error factor for the RIO suspend type is Sidefile Overflow.
Table 37 Resolving XP Continuous Access Asynchronous Suspension Conditions (continued) Classification Causes of Suspension SIM Recovery procedure timeout due to overload of the RIO or the RCU itself. RIO failure The RIO (remote I/O) could not complete DB2x due to the failure at the RCU. According to the SIM generated on the RCU, remove the failure. Re-establish failed pairs (pairresync).
To identify the error code using the log displayed on the RAID Manager window, follow the procedure below. For more information, see the HP XP RAID Manager User's Guide. 1. Find the error code from the logs displayed on the RAID Manager window. Figure 57 (page 158) shows an example of a log displayed on the RAID Manager window. Figure 57 Example of a Log Displayed on RAID Manager Window Error codes appear on the right of SSB=.
Table 38 Error Code and Error Contents When Operating RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) B990 Error Content Pair cannot be created because the larger number than the number that is able to be specified for consistency group number is specified. If this error occurs even if you omit to specify the consistency group number, contact HP technical support .
Table 38 Error Code and Error Contents When Operating RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Error Content C22D The command was rejected because the specified volume is the volume other than P-VOL. C22E The command was rejected because the pairsplit command specifying -P option (write protection of P-VOL) was issued to the volume that status is not PAIR. C233 The command was rejected because the S-VOL status is SMPL.
Table 38 Error Code and Error Contents When Operating RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Error Content C305 A request for Paircreate was received. However, the command was rejected because the capacity that is used by XP Continuous Access in RCU exceeds the license capacity. Check the license capacity, including the related program products. C306 A request for Paircreate was received.
Table 38 Error Code and Error Contents When Operating RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Error Content C335 The S-VOL is the P-VOL for XP Continuous Access Asychronous. C336 The S-VOL includes PIN data. C337 The S-VOL is in the reserve status. C338 Copy pair cannot be created because of one of the following reasons: • The S-VOL is in the intervention-required condition, protected, or unusable status.
Table 38 Error Code and Error Contents When Operating RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Error Content C395 The S-VOL cannot be used due to LDEV blockage or collection access, or for other reasons. C3A0 The P-VOL is the device not supported by XP Continuous Access. C3A6 The SSID or CU number for the specified RCU is invalid. C3AB The cache for the RCU is blocked on one side. C3AD The RCU capacity that is used by XP Continuous Access exceeds the license capacity.
Table 38 Error Code and Error Contents When Operating RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Error Content • The capacity of the volume is different from the capacity of the P-VOL. • The volume is initialized by XP Business Copy. 164 Troubleshooting C3DB The S-VOL status is not PSUS or PSUE. CB11 XP Continuous Access Asynchronous program products is not installed in RCU.
Table 38 Error Code and Error Contents When Operating RAID Manager (continued) Error Code (SSB1) Error Code (SSB2) Error Content CBD0 Paircreate cannot be executed because the LUN for P-VOL is the LUSE which is created across the multiple CLPRs. CBD1 Paircreate cannot be executed because the LUN for S-VOL is the LUSE which is created across the multiple CLPRs. CBD8 A copy pair cannot be created because the specified P-VOL is not the P-VOL for XP Continuous Access Journal.
Web Console computer (Status window). During XP Continuous Access operations, the MCU and RCU generate a service SIM each time the pair status of the P-VOL or S-VOL changes for any reason, including normal status transitions (for example, COPY to PAIR). SIMs generated by the MCU include the P-VOL device ID (byte 13), and SIMs generated by the RCU include the S-VOL device ID (byte 13).
9 Support and Other Resources Related Documentation • HP XP24000/XP20000 Disk Array Owner Guide • HP XP24000/XP20000 Remote Web Console User Guide • HP XP24000/XP20000 RAID Manager User Guide • Hitachi TrueCopy™ for Mainframe User's Guide: HP XP24000 Disk Array, HP XP20000 Disk Array • HP XP24000/XP20000 LUN Manager User Guide • HP XP24000/XP20000 Remote Web Console Error Codes • HP XP24000/XP20000 for Compatible Extended Remote Copy (XRC) Software User's Guide You can find these documents on
• Operating system type and revision level • Detailed questions Subscription Service HP recommends that you register your product at the Subscriber’s Choice for Business website: http://www.hp.com/go/e-updates After registering, you will receive email notification of product enhancements, new driver versions, firmware updates, and other product resources. HP Websites For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.
A XP 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. 2. 3. 170 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. Use XP 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 XP RAID Manager.
B Retention of Pair Consistency using the Consistency Group of the XP Continuous Access Synchronous To maintain pair consistency within the storage system, it is possible to do the following: • Automatic Registration for the Consistency Groups When creating an XP Continuous Access Synchronous pair using the Remote Web Console, the created XP Continuous Access Synchronous pair can be registered in a specific consistency group automatically.
Changing the Status of S-VOL When the RCU is Disconnected When RCU detects that all of the connections for MCU are disconnected, all the XP Continuous Access Synchronous S-VOLs registered in CTG Number 127 will be changed to PSUE status. With this operation, the data consistency of pairs on each of S-VOLs in the storage system can be maintained. The following details apply to this feature: 172 • S-VOLs can be changed to PSUE status only when the Function Switch 30 is set on the RCU.
Glossary A ADDR, Adr Address. A data structure or logical convention used to identify a unique entity, such as a particular process or network device. ATM Asynchronous transfer mode. C C/T Consistency time. CHA Channel adapter. A device that provides the interface between the array and the external host system. Occasionally, this term is used synonymously with the term channel host interface processor (CHIP). CKD Check key data. An IBM file structure standard for disk volumes.
N NVS Nonvolatile storage. P P-VOL Primary volume. P/K Package. PCB Printed circuit board. PSUE Pair suspended-error. PSUS Pair suspended-split. R RAID1/5 Specific RAID architectures. RC Reference code. RCU Remote control unit. RDC Remote dual copy. Also known as remote copy. RIO Remote I/O. ROT Rules of Thumb. S S# Serial number. Also known as S/N. S-VOL Secondary or remote volume. The copy volume that receives the data from the primary volume. S/N Serial number.
Index C H cache inflow control, 23 requirements for XP Continuous Access, 51 communication time out (RCU status), 153 components, 9 Concurrent Copy, 24 configuring MCUs and RCUs for XP Continuous Access, 56 consistency group, 14, 29 operations on groups, 30 options, 30 requirements, 51 Consistency Groups automatic registration, 171 consistency status, 34 control units (CUs), 11 conventions storage capacity values, 167 COPY (pair status), 31 copy mode, 17 CTG Number 127, 171 CU, 12 currency of S-VOLs, 148
Performance Monitor, 45 pinned track, 142 point-in-time copy, 145 powering off/on XP Continuous Access components, 141 PSUS, PSUE (pair status), 31 U update copy operation, 17 R RCU powering off/on, 141 RCU port number mismatch (RCU status), 154 RCU ready timeout (group option), 30 RCU target port, 15 read and write I/O operations, 16, 18 recordset operations, 21 related documentation, 167 remote copy connections, 14 remote copy operations initial copy, 16 update copy, 17 remote I/O (RIO) operation, 21 Re