Page 1 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.
Page 2 © Copyright 2010, 201 1 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 1 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Page 3: Table Of Contents
Contents 1 Continuous Access 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.......................11 Main and remote control units ..................11 Pair volumes........................11 Journal volumes.........................11 Journals..........................12 Data path.........................12 Extended consistency groups....................12 Remote Web Console ......................13 Business Continuity Manager....................13...
Page 4 Error reporting communications (ERC)...................33 Sharing volumes with Continuous Access Synchronous Z, other program products......33 Planning for Continuous Access Journal Z with multiple P9500 systems..........33 Establishing connections between multiple secondary systems..........35 Planning extended consistency groups (EXCTG)..............35 Planning for previous models ....................36 Guidelines for preparing systems for Continuous Access Journal Z..........37 System option modes......................37 4 Planning the data path................40...
Page 5 Delete pair volumes from a mirror.....................79 8 Monitoring the system................80 Monitor pair activity, status......................80 Pair status definitions......................80 Suspend types......................83 Suspension conditions from the secondary system..............85 Filtering Information in the List in the Pair Operation window..........86 Saving pair status information into a text file..............87 Monitor copy operations data, I/O ..................88 Select data to be graphed....................89 Manipulate graph, save data..................91...
Page 6 Recovery with Business Copy Z configuration ..............115 1 1 Troubleshooting..................116 General troubleshooting......................116 Troubleshooting logical paths ....................117 Troubleshooting suspended pairs ...................119 Troubleshooting using Remote Web Console................121 Error codes .........................122 Service information messages (SIMs) ..................122 Enabling or disabling SIM reporting...................124 Clearing SIMs.........................125 12 Support and other resources..............126 Contacting HP........................126 Subscription service......................126...
Page 7 Configurations with Business Copy Z secondary volumes ............146 Pair status and data currency....................146 Using At-Time Split function when combining Continuous Access Journal Z with Business Copy Z..147 D Continuous Access Journal Z GUI reference..........151 Journal Operation window ....................151 Journal Detail window ......................154 Change Journal Option dialog box ..................158 Change Mirror Option dialog box ..................158 Edit Journal Volumes dialog box.....................160...
Page 8: Continuous Access Journal Z Overview
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.
Page 9: Hardware And Software Components
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.
Page 10 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 The master journal consists of the primary volume(s) and master journal volume(s).
Page 11: P9500 Storage Systems
P9500 storage systems Continuous Access Journal Z is operated using two P9500 storage systems, one at the primary and one at secondary sites. The primary system consists of the main control unit (MCU) and the SVP . The secondary system consists of the remote control unit (RCU) and the SVP. The primary system communicates with the secondary system over dedicated fibre channel remote copy connections.
Page 12: Journals
For information on planning journal volumes, see “Sizing journal volumes” (page 25). NOTE: If a path is defined from a host to a volume, you cannot register the volume as a journal volume. Journals Journals help you manage data consistency between multiple P-VOLs and S-VOLs. A journal consists of two or more data volumes and journal volumes.
Page 13: Remote Web Console
Remote Web Console Remote Web Console communicates with the SVP of each storage system over defined TCP/IP connections. Remote Web Console must be LAN-attached to the primary system Remote Web Console is not required on the secondary system; however having it available allows you to change Continuous Access Journal Z parameters and access the Continuous Access Journal Z S-VOL for maintenance or disaster recovery.
Page 14: Update Copy Operation
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.
Page 15: Read And Write I/O Operations During Remote Copy Operation
NOTE: Journal data is transferred using special I/O operations initiated by the secondary system (RCU), called RIO (remote I/O). RIO provides the most efficient type of data transfer. Make sure that your channel extenders are capable of supporting RIO. Contact HP Technical Support for more information.
Page 16: Difference Management
The primary system copies the P-VOL VOLSER back to the S-VOL when the pair is resumed. When the S-VOL read option is not enabled and/or the pair is not suspended, the secondary system rejects read and write I/O to a S-VOL. Difference management Differential data (updates during split or suspension) between the P-VOL and S-VOL is stored in a track bitmap.
Page 17: Requirements And Specifications
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.
Page 18 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.
Page 19: Business Continuity Manager Specifications
Table 1 General system requirements (continued) Item Requirement Extended consistency groups A system can have a maximum of four EXCTGs. (EXCTG) An EXCTG can contain a maximum of 16 registered journals. RAID Manager consistency groups An EXCTG can contain journals from a maximum of four systems. when multiple primary and secondary storage system A journal cannot be registered in more than one EXCTG.
Page 20 Table 2 SAID values for PATH LINK (CL1) Package Port SAID Package Port SAID Package Port SAID Package Port SAID Local Local Local Local CL1-A X'0000' CL1-J X'0008' CL9-N X'008C' CL9-E X'0084' (Basic) (Add4) (Add10) (Add14) CL3-A X'0020' CL3-J X'0028' CLB-N X'00AC' CLB-E...
Page 21: Command Device
Table 3 SAID values for PATH LINK (REAR CL2) Package Port SAID Package Port SAID Package Port SAID Package Port SAID Local Local Local Local CL2-A X'0010' CL2-J X'0018' CLA-N X'009C' CLA-E X'0094' (Basic) (Add4) (Add10) (Add14) CL4-A X'0030' CL4-J X'0038' CLC-N X'00BC'...
Page 22 can be configured only from Business Continuity Manager. For details, see the manual of Business Continuity Manager. Requirements and specifications...
Page 23: Planning Volumes, Systems
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.
Page 24: Determining Your Rpo
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.
Page 25: Sizing Journal Volumes
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.
Page 26: Calculating The Journal Size
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.
Page 27: Data Transfer Speed Considerations
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 63). 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.
Page 28: Host I/O Time Stamp
LDEVs that are smaller than standard-size LDEVs. When custom-size LDEVs are assigned to a Continuous Access Journal Z pair, the S-VOL must have the same capacity as the P-VOL. For details about Virtual LVI feature, see HP StorageWorks P9000 Provisioning for Mainframe Systems User Guide.
Page 29: Duplicating Volsers
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...
Page 30: Maximum Number Of Pairs Allowed
system administrator must take precautions to prevent system problems related to duplicate VOLSERs (such as defining Continuous Access Journal Z S-VOLs not to come online automatically). CAUTION: If the volumes that become Continuous Access Journal Z S-VOLs are physically attached to the same system images as the volumes that become the Continuous Access Journal Z P-VOLs, the potential for error increases.
Page 31: Priority Set For Initial Copy Operations And Scheduling Order
Use the following formula Required number of bitmap areas = (ceil((number of cylinders x 15) 122,752) ) where: “number of cylinders x 15” indicates the number of slots 122,752 = the number of slots that a bitmap area can manage To calculate the maximum number of pairs that can be created The maximum number of pairs you can create is defined by the following: The number of LDEVs in the storage system...
Page 32 Table 8 Correspondence relationship between order of starting initial copy and priority set for P-VOLs Order of starting initial copy P-VOL Value set for Priority LDEV 02 LDEV 00 LDEV 01 LDEV 03 In this case, as the setting value of the Maximum Initial Copy Activities is 2, initial copy operations for LDEV 02 and LDEV 00 are started.
Page 33: Disaster Recovery Considerations
Disaster recovery considerations You define a disaster recovery solution when planning the Continuous Access Journal Z system. The following are the main tasks for preparing for disaster recovery: Identify the data volumes that you wand to back up for disaster recovery. Pair the important volumes using Continuous Access Journal Z.
Page 34 A remote command device must be created in the supervisor DKC. For details on secondary systems connections and remote command devices, see the next section and HP StorageWorks P9000 External Storage for Open and Mainframe Systems User Guide. Journal data is updated in the secondary systems based on the same time stamps and sequence numbers issued by the host when the host issues the write requests to the primary system(s).
Page 35: Establishing Connections Between Multiple Secondary Systems
2 and 3. For more information about external ports, see HP StorageWorks P9000 External Storage for Open and Mainframe Systems User Guide. For details on configuring paths, see HP StorageWorks P9000 Provisioning for Open Systems User Guide.
Page 36: Planning For Previous Models
secondary systems. See “Using extended consistency groups” (page 48) for planning and set up information. 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.
Page 37: Guidelines For Preparing Systems For Continuous Access Journal Z
P9500 systems. Make sure that primary and secondary systems are configured for P9500 Remote Web Console operations. See HP StorageWorks P9000 Remote Web Console User Guide for information. Make sure that primary and secondary systems are properly configured for Continuous Access Journal Z operations;...
Page 38 Table 1 1 System option modes (continued) Mode Description Mode 448 ON: If the SVP detects a blocked path, the SVP assumes that an error occurred, and then immediately splits (suspends) the mirror. 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.
Page 39 Table 1 1 System option modes (continued) Mode Description In the configuration where multiple MCUs share an RCU (Continuous Access Journal Z Mx1 configuration), the mirror resynchronization or delta resync operation may fail due to SSB=EB9D. SSB=EB9D is output as SSB log when the parameter of the communication command is not saved in the shared memory.
Page 40: Planning The Data Path
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.
Page 41: Calculating Bandwidth
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. You can size bandwidth and journal size for long-haul data migration, to be used where data consistency is not required.
Page 42: Sizing Bandwidth For Peak Rolling Average Write-Workload
by optimizing or streamlining high-workload processes. Changing the timing of a process may lower workload. With a base bandwidth value established, make adjustments for growth and a safety factor. Projected growth rate accounts for the increase expected in write-workload over a 1, 2, or 3 year period.
Page 43: Latency
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.
Page 44: Planning Ports For Data Transfer
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 send data. RCU target ports receive data. The amount of data each of these ports can transmit is limited. You must know the amount of data that will be transferred during peak periods.
Page 45: On Setting Up Ports
The data transfer speed of your Continuous Access Journal Z ports must be greater than peak write-IOPS. Using peak IOPS and the IOPS threshold of your systems’ port microprocessors, calculate the number of microprocessors (and Fibre Channel ports) the Continuous Access Journal Z system requires.
Page 46: Supported Data Path Configurations
This information is illustrated in Figure 10 (page 46). 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 46).
Page 47 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.
Page 48: Using Extended Consistency Groups
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.
Page 49 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. ◦...
Page 50: Register Journals In An Exctg
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.
Page 51: Split, Restore, Release Pairs 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.
Page 52: Remove Journals From An Exctg
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.
Page 53: Forcibly Remove Journals
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.
Page 54 Figure 16 Journals that can be registered in an EXCTG when previous models (XP24000/XP20000 Disk Array) are the subordinate DKC Using extended consistency groups...
Page 55 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 EXCTGs with P9500...
Page 56: Configuration Operations
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.
Page 57 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. ◦...
Page 58: Configure Storage Systems For Continuous Access Journal Z, Define Logical Paths
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”...
Page 59 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.
Page 60: Configure Additional Logical Paths
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.
Page 61: Specify Number Of Volumes For Initial Copy, Resync
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.
Page 62 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.
Page 63: Register Journal Volumes In A Journal
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.
Page 64 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.
Page 65 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.
Page 66 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.
Page 67: Pair Operations
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.
Page 68 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. For details about Performance Monitor, see HP StorageWorks P9000 Performance for Open and Mainframe Systems User Guide.
Page 69 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.
Page 70 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.
Page 71: Split A Pair
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.
Page 72 Journal data may not be copied to the S-VOL depending on the option you select. During normal Continuous Access Journal Z operations, the secondary system rejects write operations to an S-VOL. However, you can enable write operations to the S-VOL during the pair split operation.
Page 73: Split A Mirror
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.
Page 74: Restore A Pair
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.
Page 75 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.
Page 76: Resynchronize A Mirror
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.
Page 77: Delete A Pair
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.
Page 78 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.
Page 79: Delete Pair Volumes From A Mirror
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.
Page 80: Monitoring The System
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.
Page 81 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.
Page 82 Pair Status Description Hlde An error occurred on the pair in Hold status. When the status of P-VOL is Hlde, incoming write data for the Cnt Ac-S Z S-VOL is not stored in the master journal volume. Operations allowed on pairs in Hlde status are: - Recovering pair status to standby (Hold) - Pair-delete - Changing pair options...
Page 83: Suspend Types
where: ◦ C is total capacity (MB) of the master journal volume. u is the usage rate of data (%) in the master journal volume. ◦ V is data transfer speed (MB/sec) between the primary and the secondary systems. ◦ “Usage Monitor window ”...
Page 84 Table 12 Suspension types Suspend type Applies to Description Secondary data volume P-VOL, S-VOL The user suspended the pair from the primary or secondary by operator system using the S-VOL option. By MCU S-VOL The secondary system received a request from the primary system to suspend the pair.
Page 85: Suspension Conditions From The Secondary System
Table 13 Suspended S-VOL consistency status Consistency status Description Volume This Cnt Ac-J Z volume pair was suspended alone. Update sequence consistency between this S-VOL and other S-VOLs in this mirror is not insured. This S-VOL cannot be used for disaster recovery at the secondary system. This status is indicated when: This volume pair was suspended by a user-initiated suspend pair operation with the Cnt Ac-J Z Suspend option set to Volume.
Page 86: Filtering Information In The List In The Pair Operation Window
The journal data that reached the secondary system but have not yet been settled. After marking these S-VOL tracks as modified, the secondary system discards these journal data. The P-VOL records updated by host-requested write I/Os after the pair was suspended. When a suspended pair is resumed (resynchronized), the contents of the secondary system’s cylinder/track bitmap are sent to the primary system and merged into its bitmap.
Page 87: Saving Pair Status Information Into A Text File
Export is not available on the Pair Operation window. For the further information of the client file access settings, see HP StorageWorks P9000 Remote Web Console User Guide. The following information for pair status is displayed in the exported file:...
Page 88: Monitor Copy Operations Data, I/O
Monitoring window are described in Table 15 (page 88). You start and stop monitoring in Performance Monitor. See HP StorageWorks P9000 Performance for Open and Mainframe Systems User Guide for instructions. Figure 18 Usage Monitor Window Table 15 Fields on the Usage Monitor window...
Page 89: Select Data To Be Graphed
CU number, and LDEV number appear above the graph. - A device ID ending in # (e.g., 00:00:3C #) indicates the LDEV is an external volume (see HP StorageWorks P9000 External Storage for Open and Mainframe Systems User Guide for more information about external drives).
Page 90 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.
Page 91: Manipulate Graph, Save Data
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.
Page 92: Monitor Logical Path Status
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.
Page 93: History Of Operations For Data Volume Pairs
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”.
Page 94: Maintaining The System
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.
Page 95: Journal And Mirror Maintenance
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.
Page 96 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.
Page 97: Change Continuous Access Journal Z Options Used By Mirrors
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.
Page 98 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.
Page 99: Delete Journal Volumes From A Journal
(LDEV) is blocked. To reuse the volume as a data volume, you must format the volume. Unless you format the volume, data in the volume is not guaranteed. For instructions on formatting volumes, see the HP StorageWorks P9000 Provisioning for Mainframe Systems User Guide.
Page 100: Delete A Journal
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.
Page 101: Delete Logical Paths
Prerequisite information Modifying the data-transfer threshold can be performed from the primary or secondary system. The setting is made in the RIO MIH field on the DKC Options dialog box (RIO MIH--remote I/O missing interrupt handler). To change the data-transfer threshold time In Remote Web Console, select Actions >...
Page 102: Delete The Continuous Access Journal Z Relationship
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. Click Apply to apply the settings.
Page 103: When Power Stops Unexpectedly
When power stops unexpectedly This section explains what happens when power is removed from systems or network relay devices due to an unexpected reason. CAUTION: When a system is powered on, you must wait five (5) minutes before performing Continuous Access Journal Z operations; otherwise the pairs could be suspended with a failure. When power is removed from primary or secondary system If power is removed from the primary system during remote copy operations, the primary system assumes that a failure has occurred and splits all pairs.
Page 104: Power-Off Primary And Secondary Systems At The Same Time
Correcting errors made when powering-off If a secondary system remains in Suspending status because you initiated a power-off while the primary system was copying data, delete the pair forcibly in both the primary and secondary systems and then recreate the pair. Power-off primary and secondary systems at the same time The primary system must be powered off before the secondary system is powered off.
Page 105: 10 Disaster Recovery Operations
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.
Page 106: Copy Data Back To The Primary Site
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.
Page 107: Disaster Recovery For Multiple Primary And Secondary Storage Systems
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.
Page 108: Recovery In A 3Dc Cascade Configuration
“Recovering from primary site failures (when delta resync operation is performed)” (page 111) “Recovering from failures in the primary site and the Continuous Access Synchronous Z secondary site” (page 114) “Recovery with Business Copy Z configuration ” (page 115) 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.
Page 109: Recovering From Primary Site Disaster In 3Dc Multi Target Configuration
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...
Page 110 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.
Page 111: Recovering From Primary Site Failures (When Delta Resync Operation Is Performed)
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.
Page 112 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.
Page 113 Use Business Continuity Manager to execute the YKSUSPND FORWARD command on the Continuous Access Synchronous Z pair. Cnt Ac-S Z pair is split and the copy operation stops temporarily 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.
Page 114: Recovering From Failures In The Primary Site And The Continuous Access Synchronous Z Secondary Site
Table 20 Pair status and operation after recovery of the primary site Invalid pair status Do the following before transferring business tasks back to the primary site Primary site: Pending Duplex Make sure that the status of the pair in the primary site is Suspend. Release the Cnt Ac-J Z pair from the primary site.
Page 115: Recovery With Business Copy Z Configuration
Stop business tasks at the Continuous Access Journal Z secondary site. Use Business Continuity Manager to execute the YKSUSPND FORWARD command (a command for splitting a pair and stopping the copy operation temporarily) on the Continuous Access Journal Z pair. Use the primary volume in the primary site to resume your business tasks.
Page 116: 1 Troubleshooting
DKC Operation window, the Pair Operation window, and the Display Filter dialog box. An R-SIM warning appears on your Remote Web Locate the SIM (see HP StorageWorks P9000 Remote Web Console Console computer. User Guide for instructions). For information about Cnt Ac-J Z SIMs, “Service information messages (SIMs) ”...
Page 117: Troubleshooting Logical Paths
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.
Page 118 Table 22 Logical path troubleshooting (continued) Path status Description Corrective action Serial Number The serial number (S/N) of Make sure that you entered the correct secondary system S/N and Mismatch the secondary system does path parameters (for example, primary and secondary system port, not match the specified and controller ID).
Page 119: Troubleshooting Suspended Pairs
Table 22 Logical path troubleshooting (continued) Path status Description Corrective action Logical Blockade A failure occurs at a Repair the port status on the primary system. primary system port. A failure occurs at a Repair the port status on the secondary system. After that, delete the secondary system port.
Page 120 Table 23 Suspended pair troubleshooting (continued) Suspend Type Applies to Description Corrective Action Secondary P-VOL The primary system detected an error Check the path status (see “Troubleshooting Data Volume during communication with the secondary logical paths ” (page 117)). Failure system or detected an I/O error during Clear any error conditions at the secondary update copy.
Page 121: Troubleshooting Using Remote Web Console
Troubleshooting using Remote Web Console The user is responsible for the operation and normal maintenance of Remote Web Console computers. For troubleshooting information on Remote Web Console, see HP StorageWorks P9000 Remote Web Console User Guide. Here are some guidelines for troubleshooting the Remote Web Console computer: Check the cabling and the LAN.
Page 122: Error Codes
) or red ( ), check the status of the storage system on the Status window (see HP StorageWorks P9000 Remote Web Console User Guide). If you are unable to resolve an error condition, contact HP Technical Support. Download the Remote Web Console trace files using the FD Dump Tool. If you are unable to...
Page 123 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.
Page 124: Enabling Or Disabling Sim Reporting
Table 25 SIM reference codes, types, and descriptions (continued) Reference code Severity Description System generating the SVP log file Byte 22 Byte 23 Serious A volume used in a P-VOL that is Primary storage SIM Log configured in a multiple primary and system secondary system combination has been suspended.
Page 125: Clearing Sims
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.
Page 126: 12 Support And Other Resources
HP StorageWorks P9000 Business Copy for Mainframe Systems User Guide HP StorageWorks P9000 Continuous Access Synchronous User Guide HP StorageWorks P9000 External Storage for Open and Mainframe Systems User Guide HP StorageWorks P9000 Performance for Open and Mainframe Systems User Guide...
Page 127: Hp Websites
Conventions for storage capacity values P9000 disk arrays use the following values to calculate physical storage capacity values (hard disk drives): 1 KB (kilobyte) = 1,000 bytes 1 MB (megabyte) = 1,000 bytes 1 GB (gigabyte) = 1,000...
Page 128 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.
Page 129: A Sharing Continuous Access Journal Z Volumes
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.
Page 130 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.
Page 131: Virtual Lvi
When Continuous Access Journal operations are completed, exit Continuous Access Journal and Remote Web Console. Re-enable Performance Monitor data collection. 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.
Page 132 Table 28 Continuous Access Journal pair status and availability of Data Retention Volume Pair status Data Retention operation Changing access attribute Referencing access attribute Primary data volume SMPL COPY PAIR PSUS PSUE Secondary data volume SMPL COPY See the following table PAIR See the following table PSUS...
Page 133: B Continuous Access Journal Z Configurations With Continuous Access Synchronous Z
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.
Page 134: Prerequisite Information For 3Dc Cascade
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.
Page 135: Procedure For Setting Up 3Dc Cascade
Create the Continuous Access Synchronous Z pair on the primary system. See HP StorageWorks P9000 Continuous Access Synchronous for Mainframe Systems User Guide for instructions. When Continuous Access Synchronous Z pair status is Duplex, create the Continuous Access Journal Z pair on the secondary system using the Continuous Access Synchronous Z R-VOL as the Continuous Access Journal Z P-VOL.
Page 136: Prerequisite Information For 3Dc Multitarget
Install and setup Continuous Access Synchronous Z and Continuous Access Journal Z on the required systems. Create a Continuous Access Synchronous Z pair on the primary system. See HP StorageWorks P9000 Continuous Access Synchronous for Mainframe Systems User Guide for instructions. 136 Continuous Access Journal Z configurations with Continuous Access Synchronous Z...
Page 137: Delta Resync Configuration
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.
Page 138: Prerequisite Information For Creating The Delta Resync Pair
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.
Page 139: Procedure For Creating A Delta Resync Pair
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...
Page 140: Configuring Delta Resync Operation Environment To Support Remote Command Devices
Set up and dedicate two external ports and two target ports on each site for the command/remote command devices. Configure paths between external ports and target ports. For detail about the external ports, see HP StorageWorks P9000 External Storage for Open and Mainframe Systems User Guide. For instruction on setting paths, see HP StorageWorks P9000 Provisioning for Open Systems User Guide.
Page 141: Assign Mirrors To Remote Command Devices
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.
Page 142: Release Mirrors
This operation can be executed per mirror: Ensure that the Remote Web Console main window is in Modify mode. For detailed information about how to do this, see HP StorageWorks P9000 Remote Web Console User Guide. Ensure that the Journal Operation window is open.
Page 143: Perform The Delta Resync Operation
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”...
Page 144: C Continuous Access Journal Z Configurations With Business Copy Z
This appendix provides configurations and information for using Business Copy Z with Continuous Access Journal Z. For details about Business Copy Z, see HP StorageWorks P9000 Business Copy for Mainframe Systems User Guide.
Page 145 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.
Page 146: Configurations With Business Copy Z Secondary Volumes
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.
Page 147: Using At-Time Split Function When Combining Continuous Access Journal Z With Business Copy Z
Steady Split functions) of the Business Copy Z pair. For details about split types, see HP StorageWorks P9000 Business Copy for Mainframe Systems User Guide. You can apply up to three split operations to one journal (equivalent to three Business Copy Z consistency groups).
Page 148 Specify the split time by using Business Continuity Manager. 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.
Page 149 After Business Copy Z has completed the split operations, Continuous Access Journal Z resumes the suspended restore operation of the restore journal. CAUTION: When using the At Time Split function when combining Continuous Access Journal Z with Business Copy Z, observe the following cautions: Configure Business Copy Z pairs on all Continuous Access Journal Z S-VOLs.
Page 150 Journal Z S-VOLs. When you use the At-Time Split function on the following pairs, enable the time stamp transferring option of all the Continuous Access Synchronous Z pairs combined with Continuous Access Journal Z pairs. If the time stamp transferring option is not enabled, the data consistency cannot be guaranteed in the Business Copy Z consistency group.
Page 151: D Continuous Access Journal Z Gui Reference
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.
Page 152 “Resynchronize a mirror” (page 76) “Delete pair volumes from a mirror” (page 79) 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.
Page 153 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.
Page 154: Journal Detail Window
Item Description Preview The Preview list shows changes that have been made in the window. When you change settings in the window, the changes appear in the Preview list before the changes are applied to storage systems. If you are sure that information in the Preview list is correct, click Apply to apply the settings that you have made.
Page 155 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.
Page 156 Item Description Use of Cache Indicates whether to store journal data in the restore journal into the cache. Use: Journal data will be stored into the cache. When there is insufficient space in the cache, journal data is also stored into the journal volume. This setting only takes effect on the journal volumes of RAID-5 or RAID-6.
Page 157 Item Description Mirrors A list of mirrors. Information of four mirrors are displayed. If four mirrors include the mirror used by Cnt Ac-J Z pairs or unused mirrors, information of those mirrors are also displayed. - Mirror ID: A mirror ID. - Attribute: indicates the attribute of a mirror ID.
Page 158: Change Journal Option Dialog Box
Change Journal Option dialog box This dialog box lets you change the options that affect pairs in a journal. See “Change Continuous Access Journal Z options used by journals” (page 95) for complete information. Item Description Inflow Control Restrict inflow of update data to the journal volume. Yes restricts inflow, No does not restrict. (slows delay response to hosts Data Overflow Watch Sets number of seconds for the system to monitor write data to the journal volume, after the...
Page 159 Item Description Inflow Control Restrict inflow of update data to the journal volume. Yes restricts inflow, No does not restrict. (slows delay response to hosts Data Overflow Watch Sets number of seconds for the system to monitor write data to the journal volume, after the journal volume threshold (80%) is reached.
Page 160: Edit Journal Volumes Dialog Box
Edit Journal Volumes dialog box This dialog box lets you register or delete journal volumes from a journal. See the following for complete information: “Register journal volumes in a journal” (page 63) “Delete journal volumes from a journal” (page 99) Item Description Journal Volumes and...
Page 161: Pair Operation Window
Item Description Journal Number of the selected journal. Current Number and the capacity of journal volumes currently in the journal. Total Estimated number and the capacity of journal volumes after addition or deletion. Pair Operation window This window lets you view the pairs for the selected port or host group. Information on the Pair Operation window will be updated when you do one of the following: Click Apply.
Page 162 User Guide. A device ID ending in X (e.g., 00:00:3C X) indicates the LDEV is a Thin Provisioning virtual volume. For details on a virtual volume, see HP StorageWorks P9000 Provisioning for Open Systems User Guide. To the right of the icon appears the LDKC number, the CU image number and the LDEV number of the volume.
Page 163 Item Description Pair Operation Hold: A pair for delta resync operation is created. (continued) Hlde: An error occurred with the pair for delta resync operation. Holding: The pair status is changing to Hold while creating a delta resync pair. Suspending: The P-VOL and the S-VOL are not synchronized. This pair is in transition from the Pending or Duplex status to the Suspend status Deleting: The P-VOL and the S-VOL are not synchronized.
Page 164 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.
Page 165: Detailed Information Dialog Box
Item Description Preview The Preview list shows changes that have been made in the window. When you change settings in the window, the changes appear in the Preview list before the changes are applied to storage systems. If you are sure that information in the Preview list is correct, click Apply to apply the settings that you have made.
Page 166 Item Description Status Shows pair status. For status definitions, see “Pair status definitions” (page 80). 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.
Page 167 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.
Page 168: Add Pair Dialog Box
Item Description Other Information May list the following: EstablishedTime, which is the date and time when the volume pair was created. Updated Time, which is the date and time when the volume pair status was last updated. Displays Reverse Resync if reverse resync is performed on the pair. Otherwise, displays nothing.
Page 169 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. For detailed information about external volumes, see HP StorageWorks P9000 External Storage for Open and Mainframe Systems User Guide.
Page 170 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.
Page 171: Suspend Pair Dialog Box
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.
Page 172: Resume Dialog Box
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.
Page 173: Delete Pair Dialog Box
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.
Page 174: Change Pair Option Dialog Box
Item Description Range Specify the release range. The default is Volume if two or more pairs in the same mirror are selected. The default is Mirror if not. Also, if the pair status is Simplex, Range is set to Volume. If the pair status is Deleting or Suspending, Range is set to Mirror.
Page 175: Display Filter Dialog Box
Item Description Error Level Sets whether to split one or all pairs in a mirror—options are Volume and Mirror. Mirror: If a failure occurs with a pair, all pairs in the mirror where the pair belongs are split. Volume: If a failure occurs with a pair, only the pair are split. Sets whether or not to copy cache-fast-write data to the S-VOL—options are Only P-VOL, which does not copy the data, and Copy to S-VOL.
Page 176: Dkc Operation Window
Item Description Internal/External Whether internal volumes or external volumes display. All shows both kinds of volumes Status The pair status or statuses to display. Sub Status The consistency status to display. The volume pair that corresponds in the specified status is displayed in the list.
Page 177: Remote Systems Information
Use the DKC Operation window to: “Configure storage systems for Continuous Access Journal Z, define logical paths ” (page 58) “Configure additional logical paths ” (page 60) View one of the following: ◦ “Remote Systems Information ” (page 177) “Logical Path Information” (page 178) ◦...
Page 178: Logical Path Information
Item Description Tree Lists the remote storage systems of each LDKC in the local storage system. The following information appears to the right of the remote system’s icon : Controller ID of the remote storage system (The model name of the remote storage system). Serial number of the remote storage system.
Page 179: Port Information For The Local System
Item Description Path Gr. ID The path group ID. The icon indicates the status of the path: The logical path is in normal status A failure occurred at the logical path. M-R Path The channel type of the logical paths between the local storage system and the remote storage system.
Page 180: Dkc Status Dialog Box
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.
Page 181 Item Description Number of the row. Path Status DKC Operation window...
Page 182: Add Dkc Dialog Box
Item Description 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.
Page 183: Dkc Option Dialog Box
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.
Page 184: Usage Monitor Window
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.
Page 185 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 %).
Page 186: Operations In History Window
LDEV number). A volume ending in # (e.g., 00:00:3C #) indicates the LDEV is an external volume. For details, see HP StorageWorks P9000 External Storage for Open and Mainframe Systems User Guide. A volume ending in X (e.g., 00:00:3C X) indicates the LDEV is a Thin Provisioning virtual volume.
Page 187 Operation Displayed Description Status Change by MCU(Simplex to Duplex) The status of the pair was changed from Simplex to Duplex because of an operation from the primary system. Status Change by MCU(Pending to Duplex) The status of the pair was changed from Pending to Duplex because of an operation from the primary system.
Page 188: History Window Notes
Operation Displayed Description Status Change to Hold The status of the S-VOL was changed to Hold because of a delta resync operation. 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. Unknown The storage system could not identify the type of the operation.
Page 189: Exctg Operation Window
Click File > Refresh on the menu bar. Select Modify mode when you are in View mode. 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.
Page 190 Use the EXCTG Operation window to: “Register journals in an EXCTG ” (page 50) “Split, restore, release pairs in an EXCTG ” (page 51) “Remove journals from an EXCTG ” (page 52) “Forcibly remove journals” (page 53) “View the EXCTG List ” (page 191).
Page 191: View The Exctg List
Item Description Preview Detailed information about operations that occur when you click Apply. List: Shows changes made in the window before the changes are applied to the storage systems. When the information in the Preview is correct, click Apply to apply the settings. Operation: Indicates the current operation.
Page 192: View Storage Systems In An Exctg
Item Description The consistency time of an EXCTG. For example, if the consistency time is 10:00 a.m., S-VOLs in the EXCTG are synchronized with the P-VOLs that were available as of 10:00 a.m. The consistency time appears in the following format: month/date/year/hour/minute/second For the number of seconds, the number before and after the decimal point appears.
Page 193: Add Journal
In the tree, double-click Registered, then double-click the desired LDKC which displays below Registered. Associated EXCTGs display in the tree below the selected LDKC. Select the desired EXCTG in the tree. Associated storage systems then display in the tree. Select the storage system you want. The storage systems in the EXCTG display as shown in the following figure.
Page 194 Item Description Controller ID The controller ID of a storage system. The controller ID is unchangeable, if journal of the local DKC is used in check box ON is selected. The controller ID for P9500 is 6. Cmd. Dev.(LDKC, In the text box on the left, specify the LDKC number of the remote command device. The list in CU, LDEV) the center, specify the CU number of the remote command device.
Page 195: Glossary
The process that occurs when one device assumes the workload of a failed companion device. Failovers can be planned or unplanned. fence level A method of setting rejection of P9000 or XP Continuous Access write I/O requests from the host according to the condition of mirroring consistency. Fibre Channel A data transfer architecture designed for mass storage devices and other peripheral devices that require high bandwidth.
Page 196 A group of disks configured to provide enhanced redundancy, performance, or both. Specifically, four or eight physical hard disk drives (HDDs) installed in a P9000 or XP disk array and assigned a common RAID level. In an XP disk array this is also referred to as an array group or parity group.
Page 197: Index
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, business requirements, assessing, error reporting communications (ERC), EXCTG on configuring, 48, Cache and Nonvolatile Storage (NVS), specifications, calculating bandwidth,...
Page 198 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 17...
Page 199 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,...

This manual is also suitable for:

Storageworks p9500

HP StorageWorks P9000 User Manual

1 Continuous Access Journal Z Overview

2 Requirements and Specifications

3 Planning Volumes, Systems

4 Planning the Data Path

5 Using Extended Consistency Groups

6 Configuration Operations

7 Pair Operations

8 Monitoring the System

9 Maintaining the System

10 Disaster Recovery Operations

1 Troubleshooting

12 Support and Other Resources

A Sharing Continuous Access Journal Z Volumes

B Continuous Access Journal Z Configurations with Continuous Access Synchronous Z

C Continuous Access Journal Z Configurations with Business Copy Z

D Continuous Access Journal Z GUI Reference

Glossary

Index

Quick Links

Troubleshooting

Related Manuals for HP StorageWorks P9000

Summary of Contents for HP StorageWorks P9000