HP StorageWorks P9000 Continuous Access Journal for Mainframe Systems User Guide Abstract This guide explains how to use HP StorageWorks P9000 Continuous Access Journal for Mainframe Software to replicate data between local and remote HP StorageWorks P9000 disk arrays and to achieve disaster tolerance with maximum application performance.
© Copyright 2010, 201 1 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 1 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Contents 1 Continuous Access Journal Z overview ............8 Continuous Access Journal Z software ..................8 How Continuous Access Journal Z works..................8 Hardware and software components...................9 P9500 storage systems.......................10 Main and remote control units ..................11 Pair volumes........................11 Journal volumes.........................11 Journals..........................11 Data path.........................12 Extended consistency groups....................12 Remote Web Console ......................12 Business Continuity Manager....................13...
Establishing connections between multiple secondary systems..........34 Planning extended consistency groups (EXCTG)..............34 Planning for previous models ....................35 Guidelines for preparing systems for Continuous Access Journal Z..........36 System option modes......................36 4 Planning the data path................39 Data path design workflow .....................39 Sizing bandwidth ........................39 Five sizing strategies ......................39 Calculating bandwidth ......................40 Sizing bandwidth for peak write-workload................40...
Saving pair status information into a text file..............85 Monitor copy operations data, I/O ..................86 Select data to be graphed....................87 Manipulate graph, save data..................89 Monitor journal status......................89 Mirror Journal status definitions....................89 Monitor logical path status.......................90 History of operations for data volume pairs................91 9 Maintaining the system ................92 Pair maintenance—change the pair-split option .................92 Journal and mirror maintenance....................93...
12 Support and other resources..............123 Contacting HP........................123 Subscription service......................123 Documentation feedback....................123 Related information.......................123 HP websites........................124 Conventions for storage capacity values..................124 Typographic conventions.......................124 A Sharing Continuous Access Journal Z volumes ...........126 Volume types that can be shared with Continuous Access Journal Z..........126 Virtual LVI ...........................128 Cache Residency........................128 Auto LUN..........................128...
Display Filter dialog box ....................169 DKC Operation window .......................170 Remote Systems Information ....................172 Logical Path Information....................173 Port Information for the local system..................173 DKC Status dialog box ....................174 Add DKC dialog box .......................176 DKC Option dialog box ....................177 Usage Monitor window ......................178 History window ........................178 Operations in History window ..................180 History window notes.......................181...
1 Continuous Access Journal Z overview Unless otherwise specified, the term P9000 in this guide refers to the following disk array: P9500 Disk Array The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer browser.
Remote replication occurs using journal volumes on the local and remote systems. The journal on the local system is the “master journal.” The journal on the remote system is the “restore journal.” Replication occurs in the following sequence: Journal obtain - When the host sends an update to the primary volume, the system’s journal-obtain function triggers a copy of the update data to the master journal volume.
A Continuous Access Journal Z system consists of the following: P-VOLs and S-VOLs on the local and remote P9500 Master and restore journal volumes on the local and remote P9500 Master and restore journals on the local and remote P9500 ◦...
Main and remote control units The primary and secondary systems are often referred to as the MCU (primary system) and RCU (secondary system). MCU is the main control unit, RCU is the remote control unit. MCUs control the primary storage volume (P-VOL) and the following operations: Host I/O operations to the P-VOL Master journal operations Initial copy and update copy operations between the P-VOL and secondary volume (S-VOL).
You use journals to create multiple pairs and to split, resync, and release multiple pairs. Journals are required on the primary and secondary systems. Each data volume and its associated journal volume reside in the same journal. This is illustrated below.
NOTE: Storage Administrator (Remote Copy) role access to the Remote Web Console Java applet program is required to perform operations. Users without Storage (Remote Copy) role write access can only view (Remote Copy) role information. If the RAID Manager computer is not installed, contact HP Technical Support for information on Continuous Access Journal Z configuration services.
NOTE: If you manipulate volumes (not journals) to create or resynchronize two or more data volume pairs within the same journal, the base journal of one of the pairs is stored in the restore journal volume. Then, the base journal of another pair is stored in the restore journal volume. Therefore, the operation for restoring the latter base journal is delayed.
If an update copy operation fails, the remote system suspends the affected pair or all Continuous Access Synchronous Z pairs in the journal. This is dependent on the type of failure. The suspended pair or journal returns to Paired status when the primary and secondary storage systems are resynchronized.
The number of bitmap areas affects the maximum possible number of pairs that can be created in the storage system. Pair status Every pair operation results in a change in pair status. You should monitor pair status to insure that an operation completed successfully. Also, pairs must have a specific status in order for specific operations to be executed.
2 Requirements and specifications This chapter provides system requirements for Continuous Access Journal Z. System requirements Continuous Access Journal Z operations are performed between the host(s) and the primary and secondary storage systems containing the P-VOLs and S-VOLs, using the data path. General requirements for the Continuous Access Journal Z components are listed below.
Table 1 General system requirements (continued) Item Requirement Supported mainframe host platforms OS/390 z/OS z/VM z/Linux Also, please observe the following: Optional error report communications (ERC) function requires MVS/DFP 3.2.0 or later. If the primary and/or secondary systems consist of several CPU complexes, a SYSPLEX timer is required to provide a common time reference for the host I/O time stamping function.
Table 1 General system requirements (continued) Item Requirement RAID Manager consistency groups An EXCTG can contain journals from a maximum of four systems. when multiple primary and A journal cannot be registered in more than one EXCTG. secondary storage system Journals Max.
Table 2 SAID values for PATH LINK (CL1) (continued) Package Port SAID Package Port SAID Package Port SAID Package Port SAID Local Local Local Local CL1-C X'0002' CL1-L X'000A' CL9-Q X'008E' CL9-G X'0086' (Add2) (Add6) (Add8) (Add12) CL3-C X'0022' CL3-L X'002A' CLB-Q X'00AE'...
Table 3 SAID values for PATH LINK (REAR CL2) (continued) Package Port SAID Package Port SAID Package Port SAID Package Port SAID Local Local Local Local CL2-C X'0012' CL2-L X'001A' CLA-Q X'009E' CLA-G X'0096' (Add2) (Add6) (Add8) (Add12) CL4-C X'0032' CL4-L X'003A' CLC-Q...
3 Planning volumes, systems This chapter provides information and instructions for planning Continuous Access Journal Z volumes, P9500 systems, and other important requirements and restrictions. Plan and design workflow Planning the Continuous Access Journal Z system is tied to your organization’s business requirements and production system workload.
To insure that journals can hold the amount of data that could accumulate, they must be sized according to the following: The maximum amount of time that journals could accumulate data. You develop this information by determining your operation’s recovery point objective (RPO). The amount of changed data that your application generates.
To measure write-workload and IOPS Using your performance monitoring software, collect the following: Disk-write bytes-per-second (MB/s) for every physical volume that will be replicated. Data should be collected over a 3 or 4 week period to cover a normal, full business cycle. Data should be collected at 5 minute intervals.
where: V is the data transfer speed between a host and the primary storage system. t is the length of time until the delta resync operation starts. CAUTION: The journal volume capacity is recommended to be over 6 GB. If the capacity is below 6 GB, the system performance is unassured because the following problems may occur.
To plan journals, see the following: Review journal specifications in “System requirements” (page 17). Review journal configuration in “Register journal volumes in a journal” (page 62). Data transfer speed considerations The previous sections and the sections later in this chapter on Bandwidth discuss the amount of data that must be stored temporarily in journals and transferred over the data path network.
Journal volumes support all RAID configurations that are supported by P9500. Journal volumes also support all physical volumes that are supported by P9500. Customized volumes can be used for journal volumes. “Calculating maximum number of pairs” (page 29) for maximum and minimum supported capacity of journal volumes.
Table 4 Data and journal volume specifications Type Support specifications Data volume Journal volume Virtual LVI volume Available Available Cache Residency Z volume Available Unavailable Maximum volume 3380-3 2.377 GB 2.377 GB capacity 3380-E 1.26 GB 1.26 GB 3380-J 0.63 GB 0.63 GB 3380-K 1.890 GB...
Maximum number of pairs allowed P9500 has a limit on the number of pairs that can be created. Therefore, it is necessary to calculate the maximum number of pairs on the P9500 storage system. The maximum number is limited according to the following: The number of cylinders in the volumes, which must be calculated.
Table 6 The relationship between installed additional shared memory and the total number of LDEVs in the storage system Installed additional shared memory for Cnt Ac-J Z Total number of LDEVs in storage system Base(16KLDEV,BC/VM) 16,384 64KLDEV,BC/VM Extension1,FCV2,DP,Snapshot,TPF 65,280 The number of bitmap areas required to create pairs (determined above) The number of bitmap areas of the storage system is 65,536.
The next example explains the assignment of the scheduling order of initial copy operations in cases where initial copy is already performed and two volume pairs are newly added. The P-VOLs of the data volume pairs to be newly added and the Priority are shown in the following table. Table 9 Priority set for P-VOLs of data volume pairs to be added P-VOL Value set for Priority...
Error reporting communications (ERC) Error reporting communications (ERC) transfers information between host processors at the primary and secondary sites. It is a critical component of any disaster recovery effort. You can configure ERC using channel-to-channel communications, NetView technology, or other interconnect technologies, depending on your installation requirements and standards.
Figure 4 Using Continuous Access Journal Z with multiple storage systems When primary hosts write data to P-VOLs, the hosts add a time stamp to the data. Secondary systems check time stamps and then restore data to data volumes in chronological order (older data are restored earlier), so that data update sequence is maintained.
Establishing connections between multiple secondary systems When using more than one primary system and more than one secondary system, connections among the secondary systems must be established by configuring paths and ports. To configure ports and paths between secondary systems Create a command device in each of the secondary systems.
Planning for previous models Continuous Access Journal Z can be used to perform remote copy operations between P9500 and XP24000/XP20000 Disk Array. Data can be copied from P9500 to XP24000/XP20000 Disk Array, or vice versa. To execute remote copy from P9500 to XP24000/XP20000 Disk Array or vice versa, set up the following: Configure a logical path between LDKC00 of the P9500 system and the XP24000/XP20000 Disk Array.
Guidelines for preparing systems for Continuous Access Journal Z Use the following guidelines to insure that your P9500 systems are ready for Continuous Access Journal Z: Identify the locations where your Continuous Access Journal Z primary and secondary data volumes will be located, then install and configure the P9500 systems. Make sure that primary and secondary systems are configured for P9500 Remote Web Console operations.
Table 1 1 System option modes (continued) Mode Description Mode 448 OFF: If the SVP detects a blocked path and the path does not recover within the specified period of time, the SVP assumes that an error occurred, and then splits (suspends) the mirror.
Table 1 1 System option modes (continued) Mode Description Mode 593 ON: The multiprocessing of the communication command issued from MCU to RCU is up to 128 pairs per DKC. Mode 593 OFF: The multiprocessing of the communication command issued from MCU to RCU is up to 1024 pairs per DKC.
4 Planning the data path A data path must be designed to manage your organization’s throughput to the remote site. Appropriate bandwidth, required number of ports, and the Fiber Channel data path configuration you use help insure that your update data arrives at the remote site in a time consistent with your organization’s RPO.
If you cannot determine a “typical” workload, sizing should be to the average or mean workload, plus a small compensation for network overhead. In this scenario, excess data in the journals will be completely emptied to the S-VOL only occasionally. If bandwidth is sized below average write-workload, the journals never fully drain and eventually overflow resulting in the pairs suspending.
workload to abnormally high levels. It is sometimes worthwhile to review the processes that are running. After careful analysis, it may be possible to lower or even eliminate some spikes by optimizing or streamlining high-workload processes. Also, changing the timing of a process may lower workload.
For another perspective, you can graph the data, as shown in Figure 9 (page 42). Figure 9 60-minute rolling averages graphed over raw data From the spreadsheet or graph, locate the largest or highest rolling average value. This is the peak rolling average, which indicates the base amount of data that your bandwidth must be able to handle.
Planning ports for data transfer Updated data is transferred along the data path from the initiator and RCU target ports on the primary and secondary systems. Initiator ports control the specific data link they are part of. RCU target ports respond to commands from Initiator ports. The amount of data a port can transmit is limited.
number of ports for a Continuous Access Journal Z system is two. To determine the required number of initiator and RCU target ports. Measure IOPS for your production system. When you measure write-workload, IOPS is also provided. (See “Measuring write-workload” (page 23)).
This information is illustrated in Figure 10 (page 45). Figure 10 Data path types, switches, and distances Supported data path configurations The remote data path can be configured in one of the following connection types. But for switch connection, the port should be set to Fabric on, Point-to-Point (F-port). Direct connection, as shown in Figure 1 1 (page 45).
Figure 12 Switch connection configuration Figure 13 Extender connection configuration NOTE: When an MCU and RCU are connected using switches with channel extenders, and multiple data paths are assembled, the capacity of data to be transmitted may concentrate on particular switches, depending on the configuration and the settings of switch routing.
5 Using extended consistency groups When performing Continuous Access Journal Z operations between multiple primary and secondary storage systems, the journals must be in extended consistency groups (EXCTGs). This chapter provides information and instructions for setting up and maintaining journals in EXCTGs. Overview An EXCTG is a collection of journals in which data consistency is guaranteed.
Searches for the oldest time stamp from the previous step, then restores data up to that time to the secondary volumes. In the example shown in figure, the oldest time stamp is 15:00. Continuous Access Journal Z restores all data that have a time stamp 15:00 or earlier to the S-VOLs. For Journal 1, Continuous Access Journal Z restores all data up to 15:00.
Data with the time stamp 14:03, and data with the time stamp 15:03 in journal 3. ◦ Data with the time stamp 14:04, and data with the time stamp 15:04 in journal 4. ◦ Register journals in an EXCTG When performing Continuous Access Journal Z copy operations between multiple primary and secondary storage systems, you must register the journals in an EXCTG.
Enter the LDKC number. If the LDKC number is already displayed and unchangeable, you do not need to enter it. Select the Controller ID. Specify the LDKC number, CU number, and the LDEV number of the remote command device. If the LDKC number, CU number, and the LDEV number are already specified and unchangeable, you do not need to specify them.
Figure 15 Multiple systems in EXCTGs Remove journals from an EXCTG You can release journals as follows: Single, multiple, or all journals from an EXCTG or from all EXCTGs. All journals in the storage system or LDKC. You can also forcibly remove journal that could not be removed normally. Prerequisite information You must be logged in to the supervisor DKC to remove a journal.
To remove all journals from a storage system, right-click the storage system in the tree or the list. To remove all journals in an EXCTG belonging to an LDKC, right-click the LDKC from the tree. Click Remove JNL from EXCTG in the menu that displays In the Preview list, check the journal(s) to be removed.
Figure 16 Journals that can be registered in an EXCTG when previous models (XP24000/XP20000 Disk Array) are the subordinate DKC Using EXCTGs with P9500...
Figure 17 Journals that can and cannot be registered in an EXCTG when the previous model (XP24000/XP20000 Disk Array) is the supervisor DKC Using extended consistency groups...
6 Configuration operations This chapter provides the configuration tasks that will make your primary and secondary systems ready for Continuous Access Journal Z pair operations. Configuration workflow You will set up primary and secondary systems for Continuous Access Journal Z operations as follows.
Before a fiber channel initiator port can be changed to target or RCU target, the following must be performed: All affected data volume pairs must be released. ◦ All logical paths must be deleted from the initiator port to the remote storage system. ◦...
Configure storage systems for Continuous Access Journal Z, define logical paths Prerequisite Information This procedure must be performed on both primary and secondary systems. The primary and secondary systems must already be configured for Continuous Access Journal Z operations. See “System requirements”...
In the S/N box, enter the remote system’s 5-digit serial number. In the LDKC box, select the remote system’s LDKC number. Enter 00 when the remote system is a P9500, XP24000/XP20000, or XP12000/XP10000 disk array. In the Controller ID box, select the remote system’s controller ID. The controller ID for a P9500 is 6.
1 1. The Minimum Paths box is intended for a future release. Continue to the next step. 12. RIO MIH means “remote I/O missing interrupt handler.” In the RIO MIH Time box, enter the amount of time to wait before the data transfer operation is flagged as failed by the system.
In the M-R Path box, define the logical path between local and remote systems: In the Port column, select a local system initiator port. In the Pair-Port column, select the remote system RCU target port. This establishes a logical path with the selected initiator port. You may enter port numbers using the keyboard.
To specify number of volumes to copy concurrently In Remote Web Console, select Actions > Remote Copy > Continuous Access Journal Z > Optional Operation. Click to change the mode from View to Modify. Right-click the value that displays under Activities in the right-side pane, then select Change System Option from the menu.
Register journal volumes in a journal You set up journal volumes by registering them in a journal. The procedure is provided below. Prerequisite information A journal volume may be either a 3390 emulation volume (except for data exchange emulations and 3390-A) or it may be an OPEN-V emulation. The number of volumes registered does not have the same between the primary and secondary storage systems.
To register journal volumes In Remote Web Console, select Actions > Remote Copy > Continuous Access Journal Z > Journal Operation. The Journal Operation window is displayed. Click to change the mode from View to Modify. To register journal volumes in an existing journal, select the journal from the Registered tree. To register journal volumes in a new journal, select the journal from the Free tree.
In the Free Volumes list, select the volumes that you want to register. Each row represents a volume in the list. If you cannot find the volumes, select one of the following in the PG/CU change area: PG, then enter a parity group number in the box, and click Show. A list of volumes in the specified parity group displays.
channel (SSCH) at the main host system, and the time stamp is transferred to the primary storage system at the beginning of each I/O operation. Local When the Local timer option is selected, the primary storage system does not acquire time stamp information from the host I/O time stamping function.
7 Pair operations This chapter provides procedures and prerequisite information for performing Continuous Access Journal Z copy operations. Pair operations workflow Basic Continuous Access Journal Z operations consists of the following. Always check pair status. Each Continuous Access Journal Z operation requires the pair to be in a specific status.
If you are creating a Continuous Access Journal Z pair for delta resync, make sure all requirements are met. See “Procedure for creating a delta resync pair ” (page 136). If this program product is running on a primary storage system or secondary storage system, stop Performance Monitor before performing the initial copy to avoid overloading with TCP/IP traffic.
Data for the selected volume displays in the P-VOL box. The numbers indicate the volume LDKC number, CU number, and LDEV number. One P-VOL displays at a time, even if you selected multiple volumes for pairing. The volume with the lowest number displays first. Specify an S-VOL as follows: Select the CU number and LDEV number from the two S-VOL , left to right.
If multiple pairs are created at one time, use the Select Other S-VOL(s) list to specify S-VOLs. If you selected multiple volumes as P-VOLs, you can instruct the system to automatically assign S-VOLs for the remainder of P-VOLs. Do this from the Select Other S-VOL(s) list, as follows: - Select Increment to cause Continuous Access Journal Z to add the secondary system LDEV incrementally.
by the CU configuration or a remote copy path error. Review the error, release the pair with the error, and then retry the Add Pair operation. 10. In the Error Level list, select one of the following options to take place in the event a failure occurs during this operation: Mirror, to cause all pairs in the failed pair’s mirror to be split.
pair split operation. When you do this, then resync the pair, the secondary system sends the S-VOL track bitmap to the primary system to insure proper resynchronization of the pair. This S-VOL Write option is described in the pair-split procedure. To split one or more pairs In Remote Web Console, select Actions >...
See the Preview list in the Journal Operation window to check the settings that you have made. If you want to modify a setting, select and right click the setting in the Preview list and then select Modify. If you want to cancel a setting, select and right click the setting and then select Cancel. 10.
Restore a pair If the pair is restored, the suspended data copy from the primary data volumes to the secondary data volumes is resumed. If the delta resync pair is restored, the delta resync processing is performed. This section describes the pair resync operation. Also, the instructions are used when performing the delta resync operation.
If you are to use the Continuous Access Journal Z pair for delta resync operation as the master journal after a power supply error occurred at the primary storage system, first resynchronize the pair and then execute I/O operation from the host. After the delta resync operation (when pair status has changed to Duplex), the delta resync P-VOL must be updated from the host for longer than five minutes.
To be able to continue processing, do either of the following: Ensure that the Range column displays Volume for all pairs in the same mirror. In the Preview list, select all but one pair in the same mirror, right click the selected pairs, and then select Delete.
To resynchronize a mirror In Remote Web Console, select Actions > Remote Copy > Continuous Access Journal Z > Journal Operation. Click to change the mode from View to Modify. In the tree, expand Registered then select the desired LDKC. Journals display in the tree, Mirrors display in the right-side pane.
volumes and asked which volume should be left offline. This can be confusing and is prone to error. If the Continuous Access Journal Z secondary data volumes and primary data volumes are connected to the same host(s), HP strongly recommend that the secondary data volumes are defined to remain offline to avoid this problem.
See the Preview list in the Journal Operation window to check the settings that you have made. If you want to modify a setting, select and right click the setting in the Preview list and then select Modify. If you want to cancel a setting, select and right click the setting and then select Cancel. Click Apply to apply the settings.
8 Monitoring the system Monitoring pairs, journals, and data paths should be checked frequently to insure that Continuous Access Journal Z pairs are operating correctly. Pair status should be checked before performing a Continuous Access Journal Z operation. Each operation requires specific pair status. Monitor pair activity, status Monitoring the Continuous Access Journal Z system is an ongoing operation that should be performed frequently to maintain your pairs.
Pair Status Description Suspending The pair is not synchronized. The pair is in transition from duplex or pending duplex to suspended. When the suspension is requested (by user, primary storage system, or secondary storage system), the status of all affected pairs changes to suspending. When the suspension is complete, the status changes to suspended.
Pair Status Description Even if the "delta resync operation" without the deferential data is executable, the pair status will change to Hold regardless of the differential data existing if the conditions of the differential data discarding are satisfied as mentioned above.
Suspend types You can suspend a pair after the initial copy operation is complete. When you suspend a pair, the primary and secondary systems insure synchronization by completing or discarding any pending update copy operations. This depends on the Suspend Mode option that you specify in the Suspend Pair operation.
Table 12 Suspension types (continued) Suspend type Applies to Description Initial Copy failed P-VOL, S-VOL The pair was suspended before the initial copy operation was complete. The data on the S-VOL is not identical to the data on the P-VOL. JNL Cache Overflow P-VOL, S-VOL The pair was suspended because it was highly likely that...
The tracks containing the following journal data are marked in the differential bitmap as modified and will be copied during the resume pair operation: Journal data created by the primary system but not yet sent to the secondary system. After marking these P-VOL tracks as modified, the primary system discards these journal data.
SEQCHK Only: Specify whether to display only the volume pairs in SEQCHK status. If this check box is selected, volumes in Simplex status do not appear in the list. Reset: Restores all options in the Display Filter dialog box to the default state. All lists show All and all check boxes are selected.
In the Pair Operation window, click Export. A message appears and asks whether to save volume pair information in a file. Click OK to close the message. A dialog box appears and prompts you to save a file. Enter the name of the file and then click Save. A message appears.
Table 15 Fields on the Usage Monitor window (continued) Field Description Update The most recent data sample time of data on the graph. Usage Monitor Graph Remote I/O statistics and status of remote copy monitor. Select data to be graphed The usage monitor graph plots the I/O data that you specify.
Click Set to close the Display Item dialog box. The Usage Monitor window now shows a graph of the selected I/O statistics data for the selected LU(s). Table 16 Remote copy I/O statistics data Data type Description Host I/O Write Record Count The number of write I/Os per second Write Transfer Rate The amount of data that are written per second.
Table 16 Remote copy I/O statistics data (continued) Data type Description R-JNL Average Transfer Rate The average transfer rate for journals in the secondary storage system. The unit is kilobytes per second. R-JNL Average RIO Response The remote I/O process time on the secondary storage system. The unit is milliseconds.
Status Description An operation for splitting or deleting the mirror is in progress. Halt An operation for splitting or deleting the mirror is in progress. Stopping An operation for splitting or deleting the mirror is finished. Stopped A Cnt Ac-J delta resync pair has been created. It is ready for the delta resync operation. Hold An error occurred with the Cnt Ac-J pair during the delta resync operation.
Item Description Pair-Port Port on the remote system. Serial number and LDKC number of the remote system. Controller ID Controller ID and model name (in parenthesis) for the remote system. Path Gr. ID Path group ID M-R Path Type of channel interface between local and remote systems. Always displays column displays “Fibre”.
9 Maintaining the system Some maintenance tasks are a response to behavior discovered during system monitoring. However, you can also change certain settings to keep the system in tune with your changing requirements. Pair maintenance—change the pair-split option You can change the option that specifies whether a pair-split operation that is triggered by pair failure is applied to all the pairs in the mirror, or only to the affected pair.
Journal and mirror maintenance Maintaining journals and mirror consists of the following operations: Changing journal options Changing mirror options Deleting journal volumes from journals Deleting journals Change Continuous Access Journal Z options used by journals Most Continuous Access Journal Z pair operations are performed on multiple pairs. This is done using journals.
For Inflow Control, specify whether to restrict inflow of update I/Os to the journal volume (slows delay response to hosts). For example, you could have a 100 GB-bandwidth data path with three journals using it. If an important database is saved to a primary volume in one of the journals, with data of lesser importance in the other journals, you may decide to restrict the Inflow Control for the less important journals while not restricting control to the important journal.
See the Preview list in the Journal Operation window to check the settings that you have made. If you want to modify a setting, select and right click the setting in the Preview list and then select Modify. If you want to cancel a setting, select and right click the setting and then select Cancel. 10.
For Copy Pace, specify the pace for initial copy activity per volume. This field cannot be specified on the remote system. Low is the default. When specifying Medium, insure that write I/O is 10 MB/s or less per parity group. If it exceeds 10 MB/s, pairs may be suspended. When specifying High, insure that I/O will not occur.
- None: No processing and the S-VOL is not updated. 10. Click Set when finished. 1 1. See the Preview list in the Journal Operation window to check the settings that you have made. If you want to modify a setting, select and right click the setting in the Preview list and then select Modify.
Click Set when finished. See the Preview list to check the settings that you have made. If you want to modify a setting, select and right click the setting in the Preview list and then select Modify. If you want to cancel a setting, select and right click the setting and then select Cancel. If necessary, repeat steps from 2 to 6 to specify volumes that should be deleted from other journals.
To change the data-transfer threshold time In Remote Web Console, select Actions > Remote Copy > Continuous Access Journal Z > DKC Operation. The DKC Operation window displays. Click to change the mode from View to Modify. Make sure DKC is selected in the Display box. The tree and full list on the right-side display information about the paired secondary systems.
Delete the Continuous Access Journal Z relationship You can remove the Continuous Access Journal Z pair relationship between primary and secondary storage systems. Prerequisite information Removing the relationship between the primary and the secondary systems also removes the logical paths between them. This operation must be performed on both the primary and secondary P9500 systems.
When power is removed from network relay devices If power is removed from a network relay device during remote copy operations, the primary and secondary systems assume that a failure has occurred and split all pairs. Power-off storage systems intentionally This section explains what should be noted when you intentionally power off systems or network relay devices.
Split all pairs that will be affected. For example, if two primary systems and one secondary system are connected to each other and you want to power off one of the primary system and the secondary system, you must split the pairs on all three systems since they are all affected. After the pairs are split, confirm that their status is Suspend at the primary system.
10 Disaster recovery operations This chapter provides guidelines for performing disaster recovery operations. Also included are disaster recovery procedures when Continuous Access Journal Z is configured with Continuous Access Synchronous Z and Business Copy Z. Preparing for disaster recovery The major steps for preparing for disaster recovery are: Identify the data volumes that you wand to back up for disaster recovery.
If such a pair exists, consistency in the S-VOL is suspect. Recovery with guaranteed consistency is impossible. In this case, to use the S-VOL, you must release the pair. If such a pair does not exist, execute the YKSUSPND REVERSE option on the restore journal to split the pairs.
The following procedure explains how to resume normal operations at the primary site by using Business Continuity Manager. At both Continuous Access Journal Z sites, make sure that the Continuous Access Journal Z components are operational and free of failures. Make sure that the pair status of P-VOLs and S-VOLs in all Continuous Access Journal Z pairs is Duplex.
“Recovering from primary site failures (when delta resync operation is performed)” (page 109) “Recovering from failures in the primary site and the Continuous Access Synchronous Z secondary site” (page 112) “Recovery with Business Copy Z configuration ” (page 113) Recovery in a 3DC cascade configuration If a disaster or failure occurs in the primary site of a 3DC cascade configuration, you transfer business operations to the intermediate Continuous Access Synchronous Z secondary volume (S-VOL) site.
10. Use volumes in the primary site to resume your business tasks. 1 1. Execute the YKDELETE command onto journals that make a Continuous Access Synchronous Z pair between the intermediate site and the secondary site. The system returns to the status before the 3DC cascading configuration was set up. Recovering from primary site disaster in 3DC multi target configuration If a disaster or failure occurs only in the primary site in 3DC multi target system, you can use secondary volume in the Continuous Access Synchronous Z secondary site to enable the secondary...
Use Business Continuity Manager to execute the YKRESYNC REVERSE command on the Continuous Access Journal Z pair, in order to reverse the copy direction of the Continuous Access Journal Z pair. YKRESYNC is a command for re establishing a pair. If reversing of the copy direction fails, create a Continuous Access Journal Z pair.
can transfer your business tasks back to the primary site after removing failures from the primary site and other locations. To transfer your business tasks back to the primary site, follow the procedure below. Business Continuity Manager is used in this procedure: Stop business tasks at the Continuous Access Synchronous Z secondary site.
When the Continuous Access Journal Z pair is in Duplex status, use Business Continuity Manager to execute the YKSUSPEND Flash FORWARD command on the Continuous Access Journal Z pair. Use Business Continuity Manager to execute the YKSUSPND REVERSE command on the Continuous Access Synchronous Z pair.
Use the main volume in the primary site to resume your business tasks. Use Business Continuity Manager to execute the YKRESYNC FORWARD command on the Continuous Access Synchronous Z pair. The copy direction of the pair is returned to its original direction. Perform delta resync operation on the volume in the Continuous Access Synchronous Z primary site.
Table 20 Pair status and operation after recovery of the primary site (continued) Invalid pair status Do the following before transferring business tasks back to the primary site Primary site: Hlde Change the status of the Hlde pair back to Hold. Cnt Ac-J Z secondary site: Hold Primary site: Simplex Release the pair in Hold status from the Cnt Ac-J Z secondary site.
Use Business Continuity Manager to execute the YKMAKE command (a command for creating a pair) on the Continuous Access Synchronous Z pair. The system configuration returns to the original 3DC multi target configuration Recovery with Business Copy Z configuration If disaster or failure occurs at the primary site where the Business Copy Z secondary volume is shared with the Continuous Access Journal Z primary volume on the local site, you can continue business operations using the remote Continuous Access Journal Z secondary volume, and then restore data and business operations back to the primary site.
1 1 Troubleshooting This chapter provides troubleshooting information. General troubleshooting General troubleshooting information for Continuous Access Journal Z. Table 21 General troubleshooting Error Corrective action Remote Web Console hangs, or Cnt Ac-J Z Make sure that the problem is not being caused by the computer or operations do not function properly.
Table 21 General troubleshooting (continued) Error Corrective action If a communication error occurs between the Remote Web Console computer and the SVP, see HP StorageWorks P9000 Remote Web Console User Guide for instructions. Although Monitoring Switch is set to Enable, the Because the time setting of SVP is changed, the monitoring data monitoring data is not updated.
Table 22 Logical path troubleshooting (continued) Path status Description Corrective action port, or this path already Make sure that you entered the correct secondary system S/N and exists. path parameters (for example, primary system port, secondary system port, and controller ID). After that, delete the failed path. You may need to change the minimum paths setting or delete the secondary system in order to delete the path.
Table 22 Logical path troubleshooting (continued) Path status Description Corrective action After deletion finishes, add the path and the secondary system by using the Add Path or Add DKC command. Troubleshooting suspended pairs Troubleshooting information for user-suspended and system-suspended pairs is provided in the following two tables.
Table 23 Suspended pair troubleshooting (continued) Suspend Type Applies to Description Corrective Action Restart the initial copy operation by using the Add Pair dialog box. S-VOL The primary system suspended all Cnt Ac-J None. The primary system automatically P/S-OFF Z pairs because it was powered off. restores these Cnt Ac-J Z pairs when it is powered on.
Here are some guidelines for troubleshooting the Remote Web Console computer: Check the cabling and the LAN. Verify that both the computer and LAN cabling are firmly attached. Reboot the computer. Close any programs that are not responding. If necessary, reboot the computer and restart the Remote Web Console program.
Figure 19 Typical SIM with reference code and SIM type NOTE: The SIMs shown below are reported to the host, except 21 81. The following table shows SIMs reference codes, and provides useful information for identifying issues and determining the system experiencing the problem. All SIMs are reported to the host, except 21 80.
Table 25 SIM reference codes, types, and descriptions (continued) Reference code Severity Description System generating the SVP log file Byte 22 Byte 23 A failure has been detected in the secondary system. Serious A volume being used by P-VOL of the Cnt Yes, repeatedly.
Clearing SIMs SIMs that are sent to hosts are also saved in the storage system. The following procedure clears all SIMs from both mainframe and open systems: CAUTION: You cannot delete only Continuous Access Journal Z SIMs. If you follow the procedure below to clear all Continuous Access Journal Z SIMs, Continuous Access Journal SIMs are also cleared at the same time.
12 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions Subscription service...
HP websites For additional information, see the following HP websites: http://www.hp.com http://www.hp.com/go/storage http://www.hp.com/service_locator http://www.hp.com/support/manuals http://www.hp.com/support/downloads http://www.hp.com/storage/whitepapers Conventions for storage capacity values P9000 disk arrays use the following values to calculate physical storage capacity values (hard disk drives): 1 KB (kilobyte) = 1,000 bytes 1 MB (megabyte) = 1,000 bytes 1 GB (gigabyte) = 1,000...
Table 26 Document conventions (continued) Convention Element Monospace text File and directory names System output Code Commands, their arguments, and argument values Monospace, italic text Code variables Command variables Monospace, bold text Emphasized monospace text WARNING! Indicates that failure to follow directions could result in bodily harm or death. CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.
A Sharing Continuous Access Journal Z volumes This appendix discusses non-Continuous Access Journal Z volumes that can be shared as Continuous Access Journal Z volumes. It discusses the volumes of several features that can be used in full or limited ways with Continuous Access Journal Z. Continuous Access Synchronous Z and Business Copy Z volumes can be used extensively with Continuous Access Journal Z.
Table 27 Volume types that can be shared with Continuous Access Journal Z (continued) Functions and volumes Can the volumes be used as Can the volumes be used as Can the volumes be used as P-VOLs? S-VOLs? journal volumes? Source volume (when Yes.
Table 27 Volume types that can be shared with Continuous Access Journal Z (continued) Functions and volumes Can the volumes be used as Can the volumes be used as Can the volumes be used as P-VOLs? S-VOLs? journal volumes? *5: First, create a Cnt Ac-J Z pair and change its status to Suspend. Then, create a Compatible FlashCopy pair by specifying the Cnt Ac-J Z P-VOL as T-VOL.
For further information on Performance Monitor, see HP StorageWorks P9000 Performance for Open and Mainframe Systems User Guide. Data Retention You can create a Continuous Access Journal pair by using volumes to which access attribute is assigned by Data Retention. However, you cannot specify a volume with "S-VOL Disable" attribute as the secondary data volume of the pair.
B Continuous Access Journal Z configurations with Continuous Access Synchronous Z Continuous Access Journal Z and Continuous Access Synchronous Z can share the same data volumes. Using Continuous Access Journal Z and Continuous Access Synchronous Z can extend disaster recovery options to a third data center. This appendix provides planning formation for sharing Continuous Access Journal Z volumes with Continuous Access Synchronous Z.
The host issues an update to the Continuous Access Synchronous Z primary volume (M-VOL), which is copied synchronously to the R-VOL. The Continuous Access Journal Z system copies the synchronous S-VOL data to the Continuous Access Journal Z remote site. Data in the Continuous Access Journal Z S-VOL is an asynchronous copy of the Continuous Access Synchronous Z M-VOL.
When the Continuous Access Synchronous Z pair is recovered, the Continuous Access Journal Z pair in Duplex or Pending status is automatically split by the system. The fence level of the Continuous Access Synchronous Z M-VOL must be Data. 3DC Cascade is not supported for multiple primary and secondary systems. The response time for host I/Os will be the response time for Continuous Access Synchronous Z operation plus the creation time of journal data in the intermediate site.
The benefit of this configuration is that it provides a third copy of the data, helping to insure that business can continue in the event of a failure at the other two sites. Failure recovery occurs as follows: If a failure occurs in the M-VOL, business is resumed using the Continuous Access Synchronous Z R-VOL.
When Continuous Access Synchronous Z pair status is Duplex, create the Continuous Access Journal Z pair on the primary system. The mirror ID must be set between 1 and 3. Delta resync configuration In a Continuous Access Journal Z delta resync configuration, you create a second Continuous Access Journal Z pair in a 3DC multitarget.
Prerequisite information for creating the delta resync pair A Continuous Access Journal Z delta resync pair is created in a 3DC Multitarget configuration only. Do not include the 3DC Multi-target configuration in the system that consists of multiple primary and secondary storage systems. Continuous Access Journal Z delta resync M-VOL = Continuous Access Synchronous Z secondary volume (R-VOL) at the intermediate site.
If any Continuous Access Journal Z pair in the journal group does not meet the above requirements, an error occurs and delta resync operation will fail, even if the specified Continuous Access Journal Z pair meets the requirements. In the following cases, delta resync operation will not be performed because the necessary journal data does not exist: When, after creating the Continuous Access Journal Z pair, the primary data volume in the Continuous Access Journal Z pair for delta resync operation is updated but Continuous Access...
Create a Continuous Access Synchronous Z pair on the primary system, following the information in the following sections: “Prerequisite information for 3DC multitarget” (page 133) “Prerequisite information for creating the delta resync pair” (page 135) After the Continuous Access Synchronous Z pair status is Duplex, create the Continuous Access Journal Z pair on the primary system, following the information in the following sections: “Prerequisite information for 3DC multitarget”...
Figure 24 Remote command device configuration for delta resync When mapping to remote command devices on each site is complete, you must assign mirror IDs to the remote command devices. This is required to enable communication for delta resync operations. Assign mirrors to remote command devices The use of mirrors with remote command devices allows you to determine whether the delta resync operation can be performed.
- Assign the mirror ID used for the Continuous Access Journal Z 3DC multitarget pair to the remote command device that is mapped to on the remote site. On the intermediate site: - Assign mirror ID 00 to the remote command device that is mapped to on the primary site.
Perform the delta resync operation The delta resync operation is performed during disaster recovery. This operation copies differential data from the Continuous Access Synchronous Z R-VOL to the Continuous Access Journal Z S-VOL. The delta resync operation is part of the Resume Pair operation. Follow instructions in “Restore a pair”...
C Continuous Access Journal Z configurations with Business Copy Z Continuous Access Journal Z and Business Copy Z can share the same data volumes to provide multiple copies of data, at both the primary and secondary sites. This appendix provides configurations and information for using Business Copy Z with Continuous Access Journal Z.
Figure 25 Shared Continuous Access Journal Z and Business Copy Z primary volume Business Continuity Manager allows you to set the starting time of the backup copy to journals. In the above configuration, if you set the starting time of the backup copy, the write operations to the P-VOL up to that time are backed up to the S-VOL.
Figure 27 Shared Continuous Access Journal Z primary volume and secondary volume with Business Copy Z primary volumes Configurations with Business Copy Z secondary volumes The following figure shows a Business Copy Z primary volume used as the production volume. A remote Continuous Access Journal Z backup copy is made of the Business Copy Z secondary volume.
Check pair status for shared volumes as follows: For Continuous Access Journal Z, check status of the primary volume or secondary volume. For Business Copy Z, check status of the primary volume. Remote Web Console shows the port, GID, LUN, LDEV ID and Business Copy Z pair status of all secondary volumes associated with a primary volume.
Among the Continuous Access Journal Z restore journals, the journal data created before the split time is restored to Continuous Access Journal Z S-VOLs (Business Copy Z S-VOLs). When Continuous Access Journal Z detects the journal data from the restore journal that has the time stamp later than the split time, restore operations are suspended.
If you use the At-Time Split function when combining Continuous Access Journal Z with Business Copy Z, note the following: The specified split time is enabled even after the split operation has been executed on Business Copy Z pair. When you execute split operation again on Business Copy Z consistency group that has been split before, specify the split time after deleting the split time registered before.
D Continuous Access Journal Z GUI reference This appendix describes the Continuous Access Journal Z windows, dialog boxes, fields, and behaviors in Remote Web Console. Journal Operation window This window lets you view details about journals and volumes. Information on the Journal Operation window will be updated when you do one of the following: Click Apply.
“Resynchronize a mirror” (page 75) “Delete pair volumes from a mirror” (page 78) Item Description Tree Lists journals in the local storage system. The tree shows journals used with Continuous Access Journal, though not Continuous Access Journal Z. Journals: This item is located at the top of the tree. When selected, the Journal Operation list shows journals in the local storage system.
Item Description Journal (continued) Status: Indicates the status of a mirror in the local storage system. Initial: A mirror in initial status. Journal volumes are registered in this journal, but no data volumes (P-VOLs or S-VOLs) are registered in this journal. If a Cnt Ac-J Z pair is created, data volumes are registered in a mirror and the status of the mirror changes to Active.
Item Description When the Preview list shows changes that have been made, you can perform only the same type of operation that you have been doing and cannot perform most of other operations (you can only view detailed information about journals even when the Preview list shows changes). For example, if you are trying to delete journals and the Preview list shows the journals that you want to delete, you are unable to perform any other operations;...
Item Description Journal (LDKC) The number of a journal and the LDKC number. The LDKC number is enclosed in the parentheses following the number of a journal, for example, 01 (00). A journal number ending in [&], indicates the journal is in a 2DC configuration, for example, 01 (00) [&]. Attribute The attribute of the journal.
Item Description Caution: This setting does not take effect on master journals. However, if the Business Continuity Manager YKRESYNC REVERSE command is used to change a master journal into a restore journal, this setting affect the journal. If you set Use, this setting only takes effect on the journal volumes of RAID-5 or RAID-6 that are in the journal.
Item Description [None]: No processing takes place when delta resync operation cannot be performed. Therefore, the S-VOL will not be updated. - Speed of Line: The line speed (in megabits per second) of data transfer. One of the following appears: 256, 100, or 10. This setting does not take effect on master journals.
Item Description Applies the settings in the dialog box to the Journal Operation window Cancel Cancels the settings and closes the dialog box. Change Mirror Option dialog box This dialog box lets you change the options of a mirror. Item Description Inflow Control Restrict inflow of update data to the journal volume.
Item Description Delta resync Failure Sets the processing that takes place when the delta resync operation cannot be performed—entire P-VOL is copied or no processing (S-VOL not updated). Applies the settings in the dialog box to the Journal Operation window Cancel Cancels the settings and closes the dialog box.
Item Description PG/CU change Sets which Free volumes to populate the list with: PG: Shows volumes belonging to a parity group. PG(Ext.): Shows external volumes belonging to a parity group. CU: Shows volumes belonging to a CU. Box: Where you either enter a PG and PG(Ext.) parity group number or select a CU. Timer Type The type of clock used for consistency time.
“Restore a pair” (page 73) “Delete a pair ” (page 76) Item Description Tree Lists LDKCs of the local storage system, with CU groups displaying under the LDKC. The CU images appear under the CU groups. Selecting a CU group or a CU image lists the volumes for the CU group or image.
Item Description Deleting: The P-VOL and the S-VOL are not synchronized. This pair is in transition from the Pending, Duplex, or Suspend status to Simplex status. Sub:Indicates one of the following statuses: SEQCHK: When the S-VOL was using the system timer, the volume received update data without a time stamp from the host computer.
Item Description Pair Operation Pair JNL: The journal number for the remote storage system. This column is blank if the volume in the (continued) local storage system is neither a P-VOL nor a S-VOL. Err Lv.: The range of pair split on error. Mirror: If an error occurs with this pair, all the pairs in the mirror where this pair belongs will be split.
Item Description When the Preview list shows changes that have been made, you can perform only the same type of operation that you have been doing and cannot perform most of other operations (you can only view detailed information about pairs even when the Preview list shows changes). For example, if you are trying to release pairs and the Preview list shows the pairs that you want to release, you are unable to perform any other operations;...
Item Description Status Shows pair status. For status definitions, see “Pair status definitions” (page 79). If the pair is split (or suspended), Status also shows the suspend type. If the pair is waiting for initial copy, Status shows the word “Queuing”. A pair’s status varies between the P-VOL and S-VOL for short periods when the secondary system changes the pair’s status.
Item Description P-VOL, S-V0L Show information about the pair volume. The first line shows the LDKC number, the CU number, and the LDEV number. If the P-VOL exists in the local storage system, the first line also displays the CLPR number and the CLPR name.
Item Description Timer Type, the type of timer used by the data volume: - System—the system clock of the mainframe host is used. - Local—the system clock of the SVP is used. - None—no system clock is used, the SVP time is used. SEQCHK displays if the S-VOL uses the system timer and receives update data without time stamp from the host computer.
Item Description P-VOL Indicates a P-VOL. The numbers are the LDKC number, the CU number and the LDEV number of the P-VOL. This column displays only one P-VOL even when two or more P-VOLs are selected in the Pair Operation window. P-VOL only displays the P-VOL that has the smallest volume number. An LDEV number ending with # indicates the volume is an external volume.
Item Description Select Other S-VOL(s) Specify how Cnt Ac-J Z automatically assigns S-VOLs if two or more P-VOLs are selected in the Pair Operation window. Increment: Cnt Ac-J Z increments volume numbers of the resulting S-VOLs one by one. For example, if you create 3 pairs and specify 1 1 on the LDEV of P-VOL, the LDEVs on the secondary system are incremented at 1 1, 12, and 13.
Item Description Specify whether to copy cache fast write data to the S-VOL. The default is Only P-VOL. Only P-VOL: Does not copy cache fast write data to the S-VOL. Copy to S-VOL: Copies cache fast write data to the S-VOL. M-JNL Information Displays information about the master journal.
Item Description Suspend Mode Specify how to deal with update data that has not been copied to the S-VOL. The default is Flush: Flush: When you split the pair, update data is copied to the S-VOL. When the secondary storage system receives a request for splitting a pair, all the journal data (that is, update data) that the pair retains is written to the S-VOL.
Item Description Resync Mode Indicates the processing after recovery of the pairs. Normal: Split pair whose status is Suspend is recovered. Delta: Delta resync operation is performed. Return to standby: The status of pairs is recovered from Hlde to Hold. Error Level Specify the range used for splitting a pair when a failure occurs.
Item Description In the Preview list, select one pair in one mirror, and then other pairs in the mirror is excluded. Delete Mode Specify whether to release the pair(s) forcibly. When the status of the pair(s) to be released is Simplex or Deleting, the default setting is Force.
Item Description Journal The journal to display. All shows all journals. Mirror Mirrors to display. All shows all mirrors. P-VOL/S-VOL The type of pair volume to display, P-VOL or S-VOL. CLPR The cache logical partition to display. CLPRs are used to segment the cache that is assigned to parity groups.
Close the DKC Status window. Click File > Refresh on the menu bar. Select Modify mode when you are in View mode. Use the DKC Operation window to: “Configure storage systems for Continuous Access Journal Z, define logical paths ” (page 57) “Configure additional logical paths ”...
Item Description Preview Shows changes made in the window before they are applied to the system. You can modify or delete by right-clicking on an item. When the information is correct, click Apply. Operation Indicates the operation in progress in the DKC Operation window. Remote Systems Information The list area on the DKC Operation window shows information about the remote system when you select DKC in the Display box and the LDKC in the tree.
Logical Path Information The list area on the DKC Operation window shows information about logical paths between ports on the local and remote systems when you select DKC in the Display box and the remote system in the tree. Item Description Path Gr.
Item Description Tree The channel adapters and ports on the local storage system. The following information appears to the right of the icon: Channel adapter (Fiber Channel interface) Target port RCU target port Initiator port External port Port in initiator/external mix mode Operation The ports on the local storage system: Port: Port number.
Item Description Number of the row. Path Status Status of a logical path. Normal. The path is established and ready to use for copy operations. In Progress. An operation for configuring or deleting the path is in progress. Initialization Failed. An error occurred when the connection between local and remote systems was initializing.
Item Description Port Port on the local system. Pair-Port Port on the remote system. Serial number and LDKC number of the remote system. Controller ID Controller ID and model name (in parenthesis) for the remote system. Path Gr. ID Path group ID M-R Path Type of channel interface between local and remote systems.
Item Description Remote system 5-digit serial number. LDKC Remote system LDKC number, 00 for XP24000/XP20000 Disk Array. Controller ID Remote system controller ID, 6 for P9500, 5 for XP24000/XP20000 Disk Array, 4 for XP12000 Disk Array/XP10000 Disk Array. Path Gr ID Field intended for a future release.
Item Description Minimum Paths Field intended for a future release. RIO MIH Time Amount of time the system waits before a data transfer operation is flagged as failed. The range is from 10 seconds to 100 seconds; 15 seconds is the default. Usage Monitor window This window lets you monitor remote copy operations data and I/O statistics.
Use this window to export pair operations history. Item Description Status The current status of operation history: No history file exists: Operation history does not exist. Reading a history file failed: An attempt to read operation history failed. Updating ... n (%): Updating of operation history is now in progress, where "n (%)" indicates the progress (in %).
Item Description Provisioning virtual volume. For details on a virtual volume, see HP StorageWorks P9000 Provisioning for Open Systems User Guide. Paired VOL: The volume paired with the manipulated volume. This volume is located in the remote storage system. This number indicates LDKC:CU:LDEV (the LDKC number, the CU number, and the LDEV number).
Operation Displayed Description Status Change by MCU(Suspend to Simplex) The status of the pair was changed from Suspend to Simplex because of an operation from the primary system. Status Change by MCU(Suspend to Pending) The status of the pair was changed from Suspend to Pending because of an operation from the primary system.
If a failure occurred with two or more pairs at the same time, the number of pairs showing Suspend Pair(Failure) or Ready for Delta resync(Failure) may not match the actual number of pairs in which the failure occurs. The copy time might not be shown in the Copy Time column, even though Add Pair Complete or Resume Pair Complete is shown in the Operation column.
Item Description Tree Provides access to the storage system. Select Subsystem. Activities Storage system option settings. Preview When you change settings in the Optional Operation window, the Preview list shows the changes. Here, the changes have not been applied to the storage system. Clicking Apply applies the changes to the storage system.
Use the EXCTG Operation window to: “Register journals in an EXCTG ” (page 49) “Split, restore, release pairs in an EXCTG ” (page 50) “Remove journals from an EXCTG ” (page 51) “Forcibly remove journals” (page 52) “View the EXCTG List ” (page 185).
Item Description Remove Journal from EXCTG: Delete journals from an EXCTG Preview: The number to the left of the slash (/) indicates the number of items (i.e., rows) appearing in the Preview list. The number to the right of the slash indicates the maximum number of items (i.e., rows) that can appear in the Preview list.
Item Description Underflow or Overflow appears in this column if an invalid time stamp is detected. If Underflow appears, the time stamp is below the allowable range. If Overflow appears, the time stamp is above the allowable range. The consistency time is valid only for the updates on the Cnt Ac-J Z pairs in Duplex status. When the data of the Cnt Ac-J Z pair that is in other than Duplex status is updated, the consistency time is not assured.
Item Description : A restore journal. Status Status of a journal. Journal numbers. A journal number is a two-digit hexadecimal number. To determine if a pair in an Active journal is split, navigate to the Journal Operation window and check the status of the journal. If a pair is split, the Journal Operation window displays the status of the journal as Active(Warning).
Item Description Mirror ID Specify a mirror ID. Num of JNLs The number of journals: Current: The number of journals already registered in the storage system. Total in DKC: The number of journals in the storage system after journals are registered or removed.
Glossary P9000 or XP Business Copy. An HP application that provides volume-level, point-in-time copies in the disk array. BC Z The version of Business Copy that supports mainframe volumes. The basic unit of data in a binary numbering system (binary digit), represented by a 0 or a 1. Eight bits equals one byte.
P-VOL Primary volume. parity group A set of hard disk drives that have the same capacity and that are treated as one group. A parity group contains both user data and parity information, which enables user data to be accessed if one or more drives in the group is not available.
Index for defining port attributes, Symbols document 3 data center cascade configuration, conventions, related information, documentation adding logical paths, HP website, providing feedback, basic operation, BCM specifications, error code, 1 19 business requirements, assessing, error reporting communications (ERC), EXCTG on configuring, 47, Cache and Nonvolatile Storage (NVS), specifications, calculating bandwidth,...
planning, deleting pairs from a mirror, specifications, delta resync - create the pair, delta resync - perform the operation, delta resync operation, latency, performing the initial copy, logical paths registering journals, additional, resyncing a mirror, deleting, resyncing a pair, monitoring;monitoring:logical paths, splitting a mirror, troubleshooting;troubleshooting:logical paths, 1 15...
switch connection, graphic, symbols in text, system option modes, planning, System requirements, target port, technical support service locator website, text symbols, time stamp, typographic conventions, VOLSER, requirements, volume max capacity, websites HP , HP Subscriber's Choice for Business, product manuals,...