XP7 Continuous Access Journal for Mainframe Systems User Guide Abstract This document describes and provides instructions for using Continuous Access Journal Z to plan, configure, and perform pair operations on the HP XP7 Storage.
© Copyright 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Continuous Access Journal Z overview ..........................................................9 Continuous Access Journal Z software ........................................................................................9 How Continuous Access Journal Z works.....................................................................................9 Hardware and software components.........................................................................................10 XP7 storage systems..........
Establishing connections between multiple secondary systems .................................................34 Multiple journals per RAID Manager consistency group .........................................................35 Planning for previous models ...................................................................................................36 Guidelines for preparing systems for Cnt Ac-J Z .........................................................................37 System option modes ............
Pair status definitions..........................................................................................................80 Additional information on pair status...............................................................................83 Suspend types..............................................................................................................83 Suspension conditions on secondary systems....................................................................
11 Cnt Ac-J Z troubleshooting......................................................................113 General troubleshooting........................................................................................................113 Remote paths status probelms.................................................................................................115 Troubleshooting by suspension type .......................................................................................
Journal Properties window.....................................................................................................160 Create Journals wizard..........................................................................................................161 Create Journals window....................................................................................................161 Select Journal Volumes dialog box.....................................................................................
Confirm window..............................................................................................................202 Glossary..................................................................................................204 Index.......................................................................................................
1 Continuous Access Journal Z overview With Continuous Access Journal Z (Cnt Ac-J Z), you create and maintain a remote copy of a data volume on a HP XP7 Storage system. This guide provides instructions for planning, configuring, operating, maintaining, and troubleshooting a Continuous Access Journal Z system. Important: Procedures in this manual are tailored to the Remote Web Console (RWC) GUI. When using this GUI, “Local Storage System” displays for the system you have accessed on the RWC server.
Replication occurs in the following sequence: 1. Journal obtain - When the host sends an update to the primary volume (P-VOL), the primary system’s journal-obtain function triggers a copy of the updated data to the master journal volume. 2. 3. • The host assigns write-sequence numbers to the data sent to the master journal volume. • Write-sequence numbers and other metadata attached to journal data ensure consistency with the data in the P-VOL.
An error reporting communications (ERC) feature is also required when Continuous Access Journal Z is to be used for disaster recovery. Continuous Access Journal Z processing continues uninterrupted if the SVP reboots, and even if the SVP fails.
◦ Restore journal data copy to the S-VOL ◦ Pair status management and configuration (for example, rejecting write I/Os to the S-VOLs by way of command rejection or intervention request ). Pair volumes Original data is stored in the P-VOL and the remote copy is stored in the S-VOL. The pair can be paired, split, resynchronized, and released. When synchronized, the volumes are paired; when split, new or changed data sent to the P-VOL is not copied to the S-VOL.
Figure 3 Journals Data path The physical transmission link between the primary and secondary systems is called the data path. Continuous Access Journal Z commands and data are transmitted through the fibre-channel data path and switches. The data path is connected to the primary and secondary systems through two types of fibre-channel ports, Initiator and RCU Target ports. Continuous Access Journal Z requires paths in both directions.
Reference Information The following topics describe Cnt Ac-J Z copy operations and other features. Overview of copy operations initial and update copy operations including the underlying operations, such as journal processing and differential data management. Initial copy operation The initial copy is executed when the primary system copies all the data in sequence from the P-VOL directly to the S-VOL.
The secondary system updates the S-VOL according to the write sequence number in the journal data. This maintains data consistency between P-VOL and S-VOL. If the P-VOL write operation fails, the primary system reports a unit check and does not create the journal data for this operation. As mentioned, if the update copy operation fails, the secondary system suspends either the affected pair or all Continuous Access Journal Z pairs in the journal, depending on the type of failure.
2 Requirements and specifications This chapter provides system requirements for Continuous Access Journal Z. System requirements Continuous Access Journal Z operations are performed from the primary system to the secondary system, which contain the Cnt Ac-J Z P-VOLs, S-VOLs, and master and restore journal volumes. Copy operations are carried out via the data path. General requirements for these and all Cnt Ac-J Z components are listed below.
Table 1 General system requirements (continued) Item Requirement Continuous Access Journal Z • Must be installed on primary and secondary XP7 systems. • License keys required. • Cnt Ac-J and Cnt Ac-J Z can coexist in the same storage system. • For information on expired licenses or exceeding licensed capacity, see the HP XP7 Remote Web Console User Guide. Other licenses required • Continuous Access Synchronous Z is required, whether or not Cnt Ac-S Z volumes are shared with Cnt Ac-J Z.
Table 1 General system requirements (continued) Item Requirement Path group Groups of remote paths, which allows you to configure or change the configuration of multiple paths at the same time. • A maximum of eight remote paths can be registered in a path group • A maximum of 64 path groups can be set in a storage system. • The range of values for the path group ID is 0-255.
Table 1 General system requirements (continued) Item Requirement Supported RAID groups • RAID1, RAID5, and RAID6 are supported for both data and journal volumes. • RAID1, RAID5, and RAID6 can co-exist in the same journal. Cache and nonvolatile storage (NVS) Must be operable for primary and secondary systems to ensure pair creation success. The secondary system cache must be configured to adequately support Cnt Ac-J Z remote-copy workloads, as well as local workload activity.
Table 2 SAID values for PATH LINK (CL1) (continued) Packg local Port SAID Packg local Port SAID Packg local Port SAID Packg local Port SAID 1PD CL1-C X'0002' 1PK CL1-L X'000A' 1PB CL9-C X'0082' 1PH CL9-L X'008A' (Add1) CL3-C X'0022' (Add5) CL3-L X'002A' (DKA Add1) CLB-C X'00A2' (DKA Add3) CLB-L X'00AA' CL5-C X'0042' CL5-L X'004A' CLD-C X'00C2' CLD-L X'00CA' CL7-C X'0062' CL7-L X'006A' CLF-C X'00E2' CLF-L X'00EA' CL1-D X'0003' CL1-M X'000B' CL9-D X'008
Table 3 SAID Values for PATH LINK (CL2) (continued) Packg local Port SAID Packg local Port SAID Packg local Port SAID Packg local Port SAID 2PD CL2-C X'0012' 2PK CL2-L X'001A' 2PB CLA-C X'0092' 2PH CLA-L X'009A' (Add1) CL4-C X'0032' (Add5) CL4-L X'003A' (DKA Add1) CLC-C X'00B2' (DKA Add3) CLC-L X'00BA' CL6-C X'0052' CL6-L X'005A' CLE-C X'00D2' CLE-L X'00DA' CL8-C X'0072' CL8-L X'007A' CLG-C X'00F2' CLG-L X'00FA' CL2-D X'0013' CL2-M X'001B' CLA-D X'009
3 Planning volumes, XP7 systems This chapter provides information and instructions for planning Continuous Access Journal Z volumes, XP7 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. This means defining business requirements for disaster downtime and measuring the amount of changed data your storage system produces over time.
To ensure 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. This is done by measuring write-workload.
1. 2. 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. If you use averages, shorter intervals provide more accuracy. At the end of the collection period, convert the data to MB/second, if needed, and import into a spreadsheet tool.
HP recommends a capacity of 6 GB or more. Journal volumes cannot be registered if capacity is lower than 1.5 GB. To calculate journal size 1. Follow the instructions for “Measuring write-workload” (page 23). 2. Use your system’s peak write-workload and your organization’s RPO to calculate journal size. For example: RPO = 2 hours Write-workload = 30 MB/sec Calculate write-workload for the RPO.
• Review journal specifications in “System requirements” (page 16). • A journal can contain a maximum of 2 journal volumes. Planning journal volumes In addition to sizing journal volumes, you must also be aware of the following requirements and restrictions. • Only THP V-VOLs whose emulation type is OPEN-V can be used for journal volumes. • A journal ID can be used in only one virtual storage machine. • Volumes to which a path is set from a host cannot be registered as journal volumes.
Planning pair volumes The following information can help you prepare volumes for configuration. Also, see system requirements and specifications in “Requirements and specifications” (page 16) for more information. • The emulation and capacity for the S-VOL must be the same as for the P-VOL • When the S-VOL is connected to the same host as the P-VOL, the S-VOL must be defined to remain offline. • CU emulation type I-2107 must be used for primary and secondary systems.
Table 4 Data and journal volume specifications Type Support specifications Data volume Journal volume Virtual LVI volume Available Unavailable Cache Residency Z volume Available Unavailable Maximum volume capacity 3390-1 0.964GB Unavailable 3390-2 1.892GB Unavailable 3390-3 2.838GB Unavailable 3390-9 8.510GB Unavailable 3390-A 223.25GB Unavailable 3390-L 27.80GB Unavailable 3390-M 55.60GB Unavailable OPEN-V Cannot be used as data Capacity of OPEN-V volumes can be volume.
Calculating maximum number of pairs NOTE: • In the calculations below, note the following: ceil () indicates that the value between the parentheses should be rounded up to the nearest integer.
The maximum number of pairs is determined by the following: • The number of bitmap areas required for Continuous Access Journal Z (calculated above). • The total number of bitmap areas in the storage system, which is 65,536. Bitmap areas reside in an additional shared memory, which is required for Continuous Access Journal Z. • ◦ Bitmap areas are used not only by Continuous Access Journal Z, but also by Continuous Access Journal, Continuous Access Synchronous, and Continuous Access Synchronous Z.
If you perform a pair operation for multiple pairs (for a specific kind of data, for example), and then perform another operation for multiple pairs (for another specific kind of data, for example), the pairs in the first operation are completed in the order of their assigned priorities. The system begins processing pairs in the second set when the number of pairs left in the first set drops below the maximum number of initial copy-setting. This is shown in the following example.
Sharing volumes with other XP7 software volumes Continuous Access Journal Z volumes can be shared with other product volumes. Sharing pair volumes enhances replication solutions, for example, when Continuous Access Journal Z and Continuous Access Synchronous Z or Business Copy Z volumes are shared.
S-VOLs in chronological order (older data are restored earlier). This ensures that the update sequence is maintained. For details on the time stamping function, see “Host I/O time stamp ” (page 26). The following does not apply to RAID Manager consistency groups with both Cnt Ac-J and Cnt Ac-J Z journals: • The term “arbitration processing" refers to the maintenance of the data update sequence through the execution of the journal restore function based on time stamps.
• The recommended method for executing RAID Manager commands is the in-band (host-based) method. This prevents I/O response from deteriorating, which may occur with the out-of-band (LAN-based) method. • When Cnt Ac-J and Cnt Ac-J Z journals are in the same RAID Manager consistency group, an error in one journal can cause suspension of all journals. See “Suspension among journals ” (page 131) for more information: • It is not possible to register a journal to multiple RAID Manager consistency groups.
By using fibre-channel switches, target ports can also be connected to secondary system target ports on the secondary systems. See “Planning ports for data transfer ” (page 45) for more information. Multiple journals per RAID Manager consistency group This section applies when you include Cnt Ac-J and Cnt Ac-J Z journals in a RAID Manager consistency group. It does not apply to pairs consisting of only Cnt Ac-J Z volumes. Normally, only one journal can be registered in a RAID Manager consistency group.
Planning for previous models You can pair XP7 volumes with P9500 and XP24000/XP20000 Disk Array volumes. Observe the following: • Configure a remote path between LDKC00 of the XP7 system and P9500 and XP24000/XP20000 Disk Array. More than one P9500 or XP24000/XP20000 Disk Array can be connected to XP7. Use configuration instructions in “Configuring primary and secondary systems for Cnt Ac-J Z ” (page 62). • Both systems must be set up as shown in the figure below.
Continuous Access Synchronous Z and Continuous Access Journal Z systems. See “Configurations with Continuous Access Synchronous Z” (page 141) to review these configurations. There are no restrictions for combining primary and secondary sites between XP7 and P9500 or XP24000/XP20000 Disk Array.
Table 6 System option modes Mode Description 20 Mode 20 ON: Enables the read option and VOLSER of the suspended S-VOL to be updated. Mode 20 OFF: Normal operations are performed. 114 Allows dynamic port mode setting (initiator/RCU target for fibre channel) through PPRC CESTPATH and CDELPATH commands. Primary/secondary systems: This SOM applies only to the primary system. Mode 114 ON: Initiator ports automatically change to RCU target ports, and RCU target ports automatically change to initiator ports.
Table 6 System option modes (continued) Mode Description 474 With mode 474 set to ON, improves the initial copy time for a Cnt Ac-J Z pair, by using the Cnt Ac-S Z initial copy operation. This operation requires use of a script with the following operations: • Cnt Ac-J Z initial copy operation, with "None" specified for the Initial Copy parameter. • Split the Cnt Ac-J Z pair. • Cnt Ac-S Z initial copy operation, using the split Cnt Ac-J Z pair volumes. • Delete the Cnt Ac-S Z pair.
4 Planning the data path A data path must be designed to manage your organization’s throughput to the remote site. The bandwidth, number of ports, and fibre-channel data path configuration that you use help ensure that your update data arrives at the remote site in a time consistent with your organization’s RPO. This chapter provides instructions for calculating bandwidth and designing the data path network.
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. In this strategy, you alternate pair status between resync and suspend in order to “batch copy” point-in-time copies. When pairs are suspended, journals are not used to queue write operations.
3. 42 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. • A safety factor adds extra bandwidth for unusually high spikes that did not occur during write-workload measurement but could.
Sizing bandwidth for peak rolling average write-workload Sizing bandwidth 43
1. Using write-workload data imported into a spreadsheet and your RPO, calculate write rolling-averages. For example, if RPO time is 1 hour, then 60-minute rolling averages are calculated. Do this by arranging the values in six 10-minute intervals, as follows: 1. In cell E4 type, =average(b2:b7), and press Enter. (Most spreadsheet tools have an average function.) This instructs the tool to calculate the average value in cells B2 through B7 (six 10-minute intervals) and populate cell E4 with that data.
2. 3. 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. 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.
The secondary system initiator port sends journal query commands to the primary RCU target port. The data is then sent through these ports — that is, from primary side RCU target ports to secondary system initiator ports. Note the following: • An initiator port on one side must have an RCU target port on the other side. • Two or more initiator ports must be configured before you can create the Cnt Ac-J Z relationship with the secondary system and create pairs.
Cable length and switch requirements Multimode or single-mode optical fiber cables are required on primary and secondary systems. The type of cable and number of switches depends on the distance between primary and secondary sites. • 0 to 0.5 km: multimode optical shortwave fiber cables are required. • 0.5 km to 1.5 km (1,640 to 4,920 feet): multimode shortwave fibre-channel interface cables are required; one switch is required, two maximum. • 1.
Supported data path configurations The remote data path can be configured using one of the following connection types. For a switch connection, you must set the port to Fabric on, Point-to-Point (F-port). • Direct connection, as shown in Figure 10 (page 48). Direct connection (loop only) is a direct link between the primary and secondary arrays. NL-port (Node Loop) connections are supported for the data path and host-to-system path. • Switch connection, as shown in Figure 11 (page 49).
Figure 11 Switch connection configuration Figure 12 Extender connection configuration NOTE: When a primary and secondary system are connected using switches with a channel extender, and multiple data paths are configured, the capacity of data to be transmitted may concentrate on particular switches, depending on the configuration and the settings of switch routing. Contact your HP account team for more information.
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.
Consistency time Consistency time. Remote Web Console displays the consistency times of EXCTGs and pairs in the Cnt Ac-J Z windows. • An EXCTG’s consistency time is the latest time stamp of the restored data in the group in which consistency is guaranteed. For example, if the consistency time is set for 10 a.m., the secondary volumes within the extended consistency group are synchronized with the primary volume as at 10 a.m.
Prerequisite information • Primary and secondary EXCTGs can be set up using Business Continuity Manager prior to registering journals, or by using Remote Web Console in the following procedure. • Journals must be in Active or Stopped status. • Register master and restore journals in the separate EXCTGs. • Journals can be deleted from the EXCTG only if the attribute is Master, Restore, or Updating.
Additional journals tables display if the EXCTG contains registered journals. 6. Add Local Storage System Journals is initially set to No, which indicates that you do not intend to add journals from the system you are accessing in Remote Web Console. Select Yes to register journals from the accessed system. 7. 8. Specify a Mirror ID for the EXCTG. If journals were registered in the EXCTG previously, then the Mirror ID field is set and cannot be changed.
The selected journals display in the Journals table on the Add Journals window. Yes indicates the journals can be registered (not previously registered). No indicates that journals were previously registerred and cannot be registered again. 11. For Remote Command Device, select the remote command device CU number and the LDEV number. No selection can be made if a remote command device has already been specified. 12.
Splitting, restoring, releasing pairs in an EXCTG With Business Continuity Manager, you can split, restore, and release all pairs in an EXCTG collectively. Pair-split operation When you perform a pair-split operation in an EXCTG, you have the choice of specifying Flush or Purge for Suspend Mode. • With Flush, the pairs in the EXCTG are split with the consistency of the data update sequence maintained.
Removing 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 system or LDKC. You can also forcibly remove journal that could not be removed normally. Prerequisite information • Journal attributes must be Master, Restore, or Updating. • You must be logged in to the supervisor DKC to remove a journal. • You can remove journals from an EXCTG at any time, regardless of the status of the journals.
Procedure 3 To remove all journals from an EXCTG 1. 2. 3. 4. In the Storage System tree, click Replication > Journal. Select the EXCTGs tab. Click Initialize EXCTG. In the Initialize EXCTG window, enter a Task Name and review the journals in the EXCTG to be deleted. 5. To remove all journals, click Apply. Forcibly removing journals Remove journals using the instructions in “Removing journals from an EXCTG ” (page 56). Use the procedure below when that procedure fails to remove the journals.
in XP7, P9500, and XP24000/XP20000 Disk Array can be specified as EXCTGs. This is shown in Figure 15 (page 58). • When the supervisor DKC is P9500 or XP24000/XP20000 Disk Array, journals of LDKCs other than LDKC00 cannot be registered in the EXCTGs. This is true even if the number of LDKCs is expanded in a future version. This is shown in Figure 15 (page 58). To clarify: ◦ A XP7 (subordinate DKC) journal of LDKC00 can be registered in the EXCTG.
Figure 16 Journals that can be registered when P9500 or XP24000/XP20000 Disk Array is the supervisor DKC Restoring journals manually Normally, Cnt Ac-J Z restores journals within EXCTGs. However, when an error occurs, manual restoration is necessary. The method for restoration differs according to whether the error occurs in the local or remote storage system.
time. In the Figure 13 (page 50) example, journal 2 has the oldest timestamp, 14:02.
6 Cnt Ac-J Z configuration operations This chapter provides instructions for configuring Continuous Access Journal Z. Configuration workflow Setup for Continuous Access Journal Z using Remote Web Console consist of the following operations. You must have Storage Administrator (Remote Copy) role to perform Continuous Access Journal Z operations. 1. Navigate to Remote Web Console. 2. Define the fibre-channel port attributes. See “Defining fibre-channel port attributes ” (page 61), below. 3.
2. 3. 4. 5. 6. 7. 8. Select the Ports tab. In the list, click the port whose attribute you want to change From the Actions menu, click Ports/Host Groups > Edit Ports. In the Edit Ports window, select the Port Attribute: Initiator or RCU Target. If you need to specify other settings, see the HP XP7 Provisioning for Mainframe Systems User Guide. Click Finish. In the Confirm window, review the settings and enter a task name in the Task Name box. Click Apply to save your settings to the system.
5. 6. In the Remote Storage System box, for Model, select the secondary storage system model and number. For Serial Number, enter one of the following secondary system serial numbers. - XP7: 1 to 99999 (5 digits) - P9500 or XP24000/XP20000 Disk Array: 1 to 99999 (5 digits) - HUS VM: 200001 to 265535 (6 digits) 7. 8. For Path Group ID, select the ID for the path group you want to use.
Configuring additional remote paths You can configure additional remote paths as needed. A maximum of eight remote paths are supported. Prerequisite information Review the path-related prerequisites in “Configuring primary and secondary systems for Cnt Ac-J Z ” (page 62). Procedure 7 To configure additional remote paths 1. 2. 3. 4. 5. In the primary XP7 Storage Systems tree, click Replications > Remote Connections. In the Remote Connections window, click the Connections (To) tab.
Prerequisite information • Review the following: ◦ “System requirements” (page 16) ◦ “Planning journals ” (page 25) ◦ “Planning journal volumes ” (page 26) ◦ “Data and journal volume specifications” (page 27) • The journal’s mirror status must be Initial, Active, Stopped, Hold, Holding, or Hold(Failure). • The journal cannot be in use. • Pair operations involving the journal cannot be in progress. • If you will use EXCTGs, make sure to set them up before registering journals.
7. In the Select Journal Volumes dialog box, from the Available LDEVs table, select the journal volumes to be registered to the journal, and click the Add button. The volumes move to the Selected Journal Volumes table. You can remove a volume from the Selected Journal Volumes table by selecting it and clicking Remove. Click OK when finished. 8. In the Create Journals window, select a Journal Type Option. • Select Standard for journals in Cnt Ac-J Z standalone pairs and pairs in a 3DC configuration.
- Disable: Journal data will not be stored in cache but in the journal volume. Disable is the only setting possible for non-RAID-5 or RAID-6 journal volumes and external volumes. NOTE: This setting does not effect master journals unless the Business Continuity Manager YKRESYNC REVERSE command is used to change a master journal into a restore journal. 13. Optional. For Timer Type, specify the type of clock used for consistency time. The specified value must be the same for the primary and secondary system.
7 Cnt Ac-J Z pair operations This chapter provides instructions for performing Continuous Access Journal Z pair operations. Pair operations workflow A typical workflow for pair operations consists of the following. You must have Storage Administrator (Remote Copy) role to perform Continuous Access Journal Z operations. • Check pair status. Each Cnt Ac-J Z operation requires the pair to be in a specific status. • Create the pair, in which the S-VOL becomes a duplicate of the P-VOL.
• You will assign a mirror ID to the pair. This identifies the pair within the journal. A mirror refers to the pair within the journal. • If the mirror ID you will assign to the new pair contains an existing pair or pairs, the new pair’s volumes must belong to the same primary and secondary systems in the mirror. Procedure 9 To create an initial copy or copies 1. 2. 3. In the Storage Systems tree, click Replication > Remote Replication, and then select the Cnt Ac-J Z Pairs tab.
4. 5. 6. For Remote Storage System, select the secondary system’s Model/Serial Number and Path Group ID. • If the mirror contains an existing pair, the same Model/Serial Number as the existing pair’s must be selected. • If the secondary system is XP24000/XP20000 Disk Array, only 0 can be selected for Path Group ID. In the Primary Volume Selection box, from Available LDEVs, select the volume to be the P-VOL.
11. Click Finish. 12. In the Confirm window, review the settings and enter a task name in the Task Name box. 13. Click Apply to save your settings to the system. Based on the initial copy option you selected, you can verify that the pair status is correct in the Remote Replication window. Initial Copy Option Current Pair Status Should Be Entire or None Pending or Duplex Delta Hold, Holding You can also monitor the progress of the operation by clicking File > Refresh in the menu bar.
5. 6. 7. 8. For Secondary Volume Write, specify whether data can be written to the S-VOL while it is split. Available only when performing the split operation from the pair’s primary storage system. • Enable: The host writes data to the S-VOL. • Disable: The host does not write data to the S-VOL. Click Finish. In the Confirm window, review the settings and enter a task name in the Task Name box. Click Apply to save your settings to the system.
5. 6. 7. 8. 9. For Secondary Volume Write, specify whether data can be written to S-VOLs in the mirror while it is split. • Enable: The host writes data to S-VOLs in the mirror. Available only when the selected mirror’s Attribute is Master. If Restore, Disable is used automatically. • Disable: The host does not write data to S-VOLs in the mirror. For Split Mode, specify whether data is written to S-VOLs in the mirror before the split operation runs.
Resynchronizing Cnt Ac-J Z pairs Resynchronizing a pair updates the S-VOL with differential data that accumulated since the pair was split. After the pair is resynchronized, the S-VOL is again updated via the journals. Prerequisites for resynchronizing pairs • This operation is performed from the primary system only. • Pair status must be Suspend. If pair status is Hold, Holding, or Hlde, use the resynchronizing mirrors operation (see “Resynchronizing mirrors ” (page 75)).
4. 5. 6. 7. 8. For Copy Priority list, specify the scheduling order for resynchronizing selected pairs, between 0 and 256 . For Error Level, specify the system response if a failure occurs during this operation. • Mirror: Splits all pairs in the failed pair’s mirror. • Volume: Splits only the specified pair or pairs that failed. Click Finish. In the Confirm window, review the settings and enter a task name in the Task Name box. Click Apply to save your settings to the system.
4. In the Resync Mirrors window, review the mirrors in the Selected Mirrors table. You can remove a mirror from the table by selecting it and clicking Cancel. 5. 6. 7. Click Finish. In the Confirm window, review the settings and enter a task name in the Task Name box. Click Apply to save your settings to the system. Deleting Cnt Ac-J Z pairs When you delete a pair, the Cnt Ac-J Z relationship between the P-VOL and S-VOL is released.
You can estimate whether the I/O load is heavy or not from frequency of host I/Os. This operation should be performed under light I/O load conditions. • In a delta resync configuration, if you release the Cnt Ac-S Z pair, the Cnt Ac-J Z delta resync pair is released as well. If you release the Cnt Ac-J Z pair, the Cnt Ac-J Z delta resync S-VOL is released. Procedure 15 To delete pairs 1. 2. 3. 4. 5.
If a journal includes two mirrors: • If you specify a mirror in Hold, Holding, or Hold(Failure) status, only the Cnt Ac-J Z pairs of the specified mirror are deleted. • If you specify a mirror that is not in Hold, Holding, or Hold(Failure) status, Cnt Ac-J Z pairs of both mirrors (including the mirror that you did not specify) are deleted. Procedure 16 To delete pairs in a mirror 1. 2. 3. 4. In the Storage Systems tree, click Replication > Remote Replication, and then select the Mirrors tab.
8 Monitoring the Cnt Ac-J Z system Monitoring pairs, journals, data paths, I/O, and hardware performance is crucial for ensuring that Continuous Access Journal Z pairs continue to function correctly. This topic provides information and instructions for monitoring a Continuous Access Journal Z system. Monitoring pair activity, status, license capacity Monitoring the Continuous Access Journal Z system and licensed capacity is essential for maintaining your pairs.
5. To review license capacity, see the Summary area in the Replication window. Pair status definitions Both Remote Web Console and Business Continuity Manager pair status names appear in the Remote Web Console Status columns, except when the names are the same. When they are the same, the Business Continuity Manager status does not appear. The following table shows both types of status names and their descriptions. In some cases, a particular status has no exact parallel status in the other interface.
RWC status BCM status Description P-VOL access Suspend SUSPOP (03), SUSPOP (04), SWAPPING (04), SUSPER (07) The pair has been suspended by the user and the P-VOL Read/Write and S-VOL are no longer synchronized. • The primary and secondary systems keep track of journal data discarded during the suspend operation. • In RWC, when the operation is performed on the primary system, the status of both the P-VOL and S-VOL changes to Suspend. S-VOL access SWAPPING (04): Read/Write.
RWC status BCM status Description P-VOL access S-VOL access the primary system continues beyond the backup time for the nonvolatile memory. • SUSPER (50): The pair was split because data mismatch between P-VOL and S-VOL during initial copy operation. The cause of the error is invalid track format. See also “Suspend types” (page 83). Suspending TRANS (60) The pair is in transition to Suspend by user or Suspend Read/Write by system status.
RWC status BCM status Description P-VOL access (No parallel RWC status) NODELTA (74) Although the user performed the data resync, difference data between the master journal and restore journal cannot be copied to the S-VOL in the current status. Running the delta resync in that status may fail. If the delta resync fails when [Entire] is specified for delta resync Failure field in the RWC Change Journal Option dialog box, and all differential data is copied to S-VOL. S-VOL access - 1.
A pair can also be suspended by the primary or secondary system.
Table 8 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 ensured. This S-VOL cannot be used for disaster recovery on 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.
• 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 resynchronized to the primary system and merged into its bitmap. The primary system then performs the resync operation according to the merged bitmap.
Operation Displayed Description Resume Pair Complete Restoring of the pair was finished. Suspend Pair Start Splitting (Suspending) of the pair was started. Suspend Pair Complete Splitting (Suspending) of the pair was finished. Suspend Pair(Failure) The pair was split (suspended) because of a failure. Delete Pair Start Release of the pair was started. Delete Pair Complete Release of the pair was finished.
Operation Displayed Description Status Change by MCU(Hold to Duplex) The status of the pair was changed from Hold to Duplex because of an operation from the primary system. Status Change by MCU(Hold to Pending) The status of the pair was changed from Hold to Pending because of an operation from the primary system. Status Change by MCU(Hold to SMPL) The status of the pair was changed from Hold to unpaired (Simplex) because of an operation from the primary system.
Status Description Stopping An operation for splitting or deleting the mirror is in progress. Stopped An operation for splitting or deleting the mirror is finished. Hold A Cnt Ac-J delta resync pair has been created. It is ready for the delta resync operation. Holding A Cnt Ac-J delta resync pair is being created. Hold(Failure) An error occurred with the Cnt Ac-J Z pair during the delta resync operation.
9 Maintaining the Cnt Ac-J Z 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. This chapter provides information and instructions for maintaining a Continuous Access Journal Z system. Pair maintenance You must have Storage Administrator (Remote Copy) role to perform Continuous Access Journal Z maintenance operations.
3. From the Actions menu, click Remote Replication > Edit Pair Options. NOTE: When you select multiple pairs on the Cnt Ac-J Pairs tab, Edit Pair Options values may be blank because the selected pairs have different values. When you specify a value, it is set for all selected pairs. 4. 5. In the Edit Pair Options window, for Error Level, specify the system response if a failure occurs in the pair. • Mirror: Splits all pairs in the failed pair’s mirror. Mirror is the default.
3. 4. From the Actions menu, select Remote Replication > Force Delete Pairs (Cnt Ac-J Pairs). In the Force Delete Pairs (Cnt Ac-J Pairs) window, ensure that the volume you want to forcibly delete is in the Selected LDEV table. 5. 6. Enter a name in the Task Name box. Click Apply to save your settings to the system.
Please be aware of the following when changing journal options: • Journal options must be changed on both systems, primary and secondary. • To change journal options, one of the following conditions must be satisfied: - The attribute of the journal is Initial.
5. 6. 7. Click Finish. In the Confirm window, review the settings and enter a task name in the Task Name box. Click Apply to save your settings to the system. Changing options used by mirrors Most pair operations are performed on multiple pairs. This is done using a journal or mirrors. You can change the following options that affect the pairs in a mirror: • Path Watch Time—the interval from the time a path becomes blocked to the time when the mirror is suspended.
5. For Path Watch Time Transfer, specify whether to use the same Path Watch Time value you specified for the master journal for the restore journal. Specify this option in the local site only. • Yes: The Path Watch Time value is also used for the restore journal. For a pair in a delta resync configuration, select Yes in the local site. • 6. 7. No: The Path Watch Time value is not used for the restore journal. No is the default. For Copy Pace, specify the pace for initial copy activity per volume.
Adding additional journal volumes to an existing journal You can add one additional journal volume to a journal. The additional volume is not used unless needed for maintenance or to replace the first one. In the event of pair failure, the additional (backup) journal volume allows you to reduce the time to recover a blocked journal volume.
Replacing a journal volume in a journal You can replace an in-use journal volume. The smoothest method is to add a backup journal volume before it is needed. For more information on this, see “Adding additional journal volumes to an existing journal” (page 96). Procedure 29 To replace a journal volume when a backup exists 1. 2. When an additional journal volume exists in a journal, delete the in-use journal volume, Resynchronize the journal.
5. 6. 7. Click Finish. In the Confirm window, review the settings and enter a task name in the Task Name box. Click Apply to save your settings to the system. Deleting journals Journals can be deleted from either system. Prerequisite information • Journals can be deleted from the primary or secondary system. • All mirrors in the journal must be Initial status. • Master and restore journals cannot be deleted.
Forcibly deleting journals from an EXCTG You can forcibly delete journal that could not be deleted normally from an EXCTG. Normal deletion form an EXCTG is done with Business Continuity Manager. For more information about deleting normally, see the Business Continuity Manager User Guide. Procedure 33 To forcibly delete journal from an EXCTG 1. 2. 3. 4. In the Remote Web Console tree, click Replication > Journals. Select the Journals tab. Select the journal you want to remove.
Procedure 34 To change the data-transfer threshold time 1. 2. 3. 4. 5. 6. 7. 8. In the Storage System tree, click Replication > Remote Connections. In the Remote Connections window, click the Connections (To) tab, then select the secondary system with the data-transfer waiting-time to be changed. From the Actions menu, click Remote Connections > Edit Remote Connection Options. In the Edit Remote Connection Options window, note that Minimum Paths cannot be changed.
5. 6. 7. Click Finish. In the Confirm window, review the settings and enter a task name in the Task Name box. Click Apply to save your settings to the system. Deleting the Cnt Ac-J Z relationship You can remove the Continuous Access Journal Z pair relationship between primary and secondary systems. Prerequisite information • Removing the relationship between the primary and the secondary systems also removes the remote paths between them.
5. 6. 7. Click Finish. In the Confirm window, review the settings and enter a task name in the Task Name box. Click Apply to save your settings to the system. Managing power-off for systems and network devices This topic explains power management for systems and network relay devices during copy operations.
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. Powering-off systems intentionally This topic explains what should be noted when you intentionally power off systems or network relay devices. NOTE: To intentionally power off the primary or secondary system, contact your HP account team and ask them to power off the system.
6. When the secondary system is ready to resume copy operations, power on the primary system. CAUTION: Wait five (5) minutes after powering on a system before performing Continuous Access Journal Z operations; otherwise the pairs could be suspended with a failure. 7. When the primary system is ready to resume copy operations, resynchronize the pairs that have been split at the primary system. Confirm that the status of the pairs is changed to Pending duplex or Duplex.
10 Cnt Ac-J Z disaster recovery operations This chapter provides instructions for performing disaster recovery. In addition to general recovery planning and procedures, detailed instructions are included for recovery when Continuous Access Journal Z pairs are configured in 3-data-center (3DC) configurations with Continuous Access Synchronous Z. Recovery when Cnt Ac-J Z pairs are shared with Business Copy Z pairs is also included.
You detect and re-create lost updates by checking database log files and other current information at the local site. Journal log file entries for most DBMS have the same clock information as the TOD clock, which is used for I/O time-stamps (when Timer Type = system). Cnt Ac-J Z group consistency time can be extremely useful when performing this detection and retrieval. You can also use the sense information with system time stamp that is transferred via ERC.
2. 3. 4. Bring up the host servers at the local site. Make sure that all Cnt Ac-J Z components are operational. Do all of the following, as applicable: 1. At the local site, locate P-VOLs whose status is Pending duplex or Duplex. Locate corresponding S-VOLs at the remote site whose status is Suspend, which indicates that data is being written to the S-VOLs. At the local site, split these pairs. 2. At the local site, locate P-VOLs whose status is other than unpaired.
recovery procedures for resuming host operations at a backup site and then restoring the original system and configurations. • “Recovery for 3 Cnt Ac-J Z/Cnt Ac-S Z DC cascade configuration ” (page 108) • “Recovery for 3 Cnt Ac-J Z/Cnt Ac-S Z DC multi-target configuration ” (page 108) • “Recovery in a delta resync configuration” (page 110) Use RAID Manager to perform all procedures.
Depending on the result, proceed as follows: If the original Cnt Ac-S Z data flow reverses 1. Re-create the Cnt Ac-J Z pair using the YKMAKE command from the Cnt Ac-S Z local site to the Cnt Ac-J Z remote site. This results in a 3DC cascade configuration, with the original Cnt Ac-S Z S-VOL as the primary volume. See the lower right configuration in the following figure. 2. Restore the local site or data path, or both. This must be done before proceeding. 3.
Recovering from local and remote site failure (3DC multi-target) Host operations are transferred to the Continuous Access Journal Z S-VOL in the remote site when a disaster or failure occurs in both the primary and Continuous Access Synchronous Z intermediate sites in a 3DC multi-target configuration. Failures are corrected at the two sites and then host operations are transferred back to the local site. Procedure 40 To recover a primary and Cnt Ac-S Z intermediate site failure 1. 2. 3. 4. 5. 6. 7. 8. 9.
the delta resync operation. When the failure at the local site is corrected, host operations are transferred back to the local site and the delta resync configuration is reestablished. Prerequisite information • For information and illustrations on the configuration covered in this procedure, see “Delta resync configuration ” (page 144). • You can specify options for recovery in the event that the delta resync operation fails.
If pair status is not Hold, match the pair’s actual statuses in the following table and then perform the corrective action. Current status Corrective action Local site: Duplex or Pending Duplex 1. Make sure that the status of the pair in the local site is Suspend. 2. Release the Cnt Ac-J Z pair from the local site. 3. Make sure that all the pairs belonging to the journal in the local site are released. 4.
11 Cnt Ac-J Z troubleshooting This chapter provides Continuous Access Journal Z troubleshooting information. General troubleshooting When an error occurs in a Continuous Access Journal Z pair operation with Remote Web Console, an error message displays with a four-digit error code and description. An SVP error code may also be included. See HP XP7 Remote Web Console Messages for details on error codes. You can download Remote Web Console dump files using the Dump tool.
Error Corrective action The pair create or pair resync operation resulted in a timeout error. • If the timeout error was caused by a hardware failure, a SIM is generated. See “Service information messages (SIMs) ” (page 129). If necessary, call HP Technical Support, and retry Cnt Ac-J Z operations after the problem is solved. • If no SIM was generated, wait for a while (5 or 6 minutes), then check the pair status of the pairs being created or resynchronized.
Remote paths status probelms Troubleshooting information for remote paths between storage systems is shown below. Path status Description Corrective action Normal This path has been successfully established and can be used for Cnt Ac-J Z copy activities. None required. Initialization Failed The link initialization • Make sure that the primary and secondary systems are procedure to the secondary physically and correctly connected.
Path status Description Corrective action Serial Number Mismatch The secondary system's S/N does not match the specified S/N. • Make sure that you entered the correct secondary system S/N and Controller ID, and primary and secondary system port numbers. • Make sure the primary and secondary system ports are configured correctly. • Make sure that data path relay equipment is properly configured and functional.
Path status Description Corrective action Program Error A program error is detected. Restore the path*. * To restore a path, delete and then add the path again. It may be necessary to delete and then add the secondary system again. To delete the secondary system or path, see “Deleting the Cnt Ac-J Z relationship ” (page 101) or “Deleting remote paths ” (page 100). To re-register, see “Configuring primary and secondary systems for Cnt Ac-J Z ” (page 62).
Suspend Type Applies to Description Corrective Action ICKDSF. Restart the initial copy operation (Create Pairs window). MCU P/S-OFF S-VOL The primary system suspended all Cnt Ac-J None. The primary system automatically Z pairs because it was powered off. resynchronizes these Cnt Ac-J Z pairs when it is powered on. Troubleshooting hardware problems affecting pairs Hardware failures affecting Continuous Access Journal Z are described in the following table.
Troubleshooting with RAID Manager When an error has occurred in Continuous Access Journal Z pair operation when using RAID Manager, you can identify the cause of the error by referring to the RAID Manager operation log file. The file is stored in the following directory by default: /HORCM/log*/curlog/horcmlog_HOST/horcm.log Where: * is the instance number. HOST is the host name. To identify the error code in the log file, open the RAID Manager log file, and find the error code.
Error code (SSB2) Description 3720 The Paircreate or Pairresync command was rejected because the journal volume in the specified master journal was blocked. 3722 The Paircreate command was rejected because the emulation type of the selected volume is unsupported. 3726 The pair cannot be created because the volume specified as the P-VOL was the system disk. 3728 The Paircreate command was rejected because it was connected with the old model and the specified volume was unsupported.
Error code (SSB2) Description 8F10 The pair cannot be created because the specified P-VOL is one of the following: • A BC Z S-VOL that is not in Split/SUSPOP status • A BC Z volume in Reverse Copy status • A Compatible FlashCopy volume 8F11 The pair cannot be created. The processing of volume migration could not be stopped because the P-VOL was being migrated by Auto LUN. 8F17 The pair cannot be created because the specified volume was in the state of online from the host.
Error code (SSB2) Description 8F53 The pair cannot be created because the status of the configuration could not be transited. 8F58 The pair cannot be created or resynchronized because of the one of following reasons. • The pair status of the specified S-VOL differed from the one of P-VOL. • The state of restore journal differed from the state of master journal. 8F67 The pair cannot be created because the specified secondary system did not support the external volume.
Error code (SSB2) Description DB02 A request for status change was rejected because the status could not be changed (for example: the pair volumes were not unpaired when the Paircreate was requested; or were in a status other than Suspend when the Pairresync was requested.) DB03 A request of Cnt Ac-J Z Pair status transition was rejected because the pair was in the state of Suspending or Deleting. DB07 Cnt Ac-J Z pair status cannot be transited during the power-on processing.
Error code (SSB2) Description E898 The command was rejected because the specified secondary journal is already a secondary journal in another mirror. E89A The command was rejected because the path between the storage devices for the both-way was not defined. Check whether the bidirectional normal path was defined or not. E89B The command was rejected because the specified master journal or the restore journal remembered the state of connection with another system in the past.
Error code (SSB2) Description EA25 The command was rejected because the state of S-VOL was not SSWS. EA29 The command was rejected because the state of master journal was other than Active or Stopped. EA2C The command was rejected because the state of restore journal was other than Active or Stopped. EA33 The command was rejected because the state of mater journal was other than Active. EA36 The command was rejected because the state of restore journal was other than Active.
Error code (SSB2) Description EAE5 The command was rejected because the specified P-VOL or S-VOL is in the process of having the capacity changed by Thin Provisioning Z. EAF6 The command was rejected because the pair was in the state that was unavailable to transit. EB24 The Cnt Ac-J Z pair for the delta resync operation cannot be created because the specified Cnt Ac-J Z S-VOL is in either one of the following statuses: • Cnt Ac-J Z volume for the delta resync operation.
Error code (SSB2) Description EB5B The command was rejected because the access attribute was set to the specified P-VOL or S-VOL by the Data Retention. EB5C The command was rejected because an internal logical error occurred. EB5E The command was rejected because the S-VOL was already paired. EB5F The command was rejected because the program product of Cnt Ac-J Z was not installed in the secondary system. EB60 The command was rejected because the P-VOL capacity is not the same as the S-VOL’s.
Error code (SSB2) Description • Cnt Ac-J Z P-VOL and S-VOL are THP V-VOL, and the specified S-VOL is the source volume of Auto LUN. • Cnt Ac-J Z P-VOL and S-VOL are THP V-VOL, and the specified S-VOL is being used as Fast Snap P-VOL. EB7F The command was rejected because the emulation type of the specified S-VOL was unsupported. EB80 The command was rejected because the specified volume was the V-VOL or the pool-VOL. Please check the status of the volume.
Error code (SSB2) Description EBDC The command was rejected because the processing load of the storage system is heavy. Please execute the command again after a while. EBE0 The command was rejected because the specified S-VOL was already used in the Cnt Ac-J Z pair for delta resync. EBE1 The command was rejected because the all S-VOLs of the specified restore journal were not the another Cnt Ac-J Z's S-VOLs.
Continuous Access Journal Z SIMs are displayed in the Remote Web Console Status window. • SIMs generated by the primary system include the P-VOL device ID (byte 13). • SIMs generated by the secondary system include the S-VOL device ID (byte 13). The figure below shows a typical 32-byte SIM from the system. The six-digit reference code consists of bytes 22, 23, and 13. The reference code identifies the possible error and determines the severity.
Reference code Byte 22 Byte 23 DC 9X Severity Description System generating the SIM SVP log file Serious A delta resync P-VOL has been suspended. Yes, repeatedly. Local A failure has been detected in the primary system. DC AX Serious A volume used in a P-VOL that is Local configured in a multiple primary and secondary system combination has been suspended. SIM Log A failure has been detected in other primary and secondary systems.
12 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
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.
Table 11 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 WARNING! CAUTION: IMPORTANT: NOTE: TIP: 134 Emphasized monospace text Indicates that failure to follow directions could result in bodily harm or death. Indicates that failure to follow directions could result in damage to equipment or data.
A Sharing Cnt Ac-J Z volumes This appendix discusses XP7 Storage software volumes that can be shared with Continuous Access Journal Z volumes. Note that Continuous Access Synchronous Z and Business Copy Z volumes can be used extensively with Continuous Access Journal Z. Information for these configurations is provided in: - “Configurations with Continuous Access Synchronous Z” (page 141) - “Configurations with Business Copy Z” (page 152). The following topics are covered in this appendix.
Table 12 Volume types that can be shared with Cnt Ac-J Z (continued) Volumes types and functions Used as Cnt Ac-J Z P-VOL? Used as Cnt Ac-J Z S-VOL? Used as Cnt Ac-J Z journal volume? P-VOL in Resync-R/REVRSY status No No No P-VOL that is also used as a Cnt Ac-S Z P-VOL or S-VOL Yes Yes No P-VOL (none of the above) Yes Yes6 No S-VOL in Split/SUSPOP status Yes No No S-VOL (in a status other than Split/SUSPOP) No No No P-VOL in Pending status No No No P-VOL in DUPLEX status Yes3
Table 12 Volume types that can be shared with Cnt Ac-J Z (continued) Volumes types and functions Used as Cnt Ac-J Z P-VOL? Used as Cnt Ac-J Z S-VOL? Used as Cnt Ac-J Z journal volume? 5. See the topic on interoperability with other products and functions in the HP XP7 for Compatible FlashCopy Mirroring User Guide for more information. 6. When a THP V-VOL is used as a pair volume shared by Business Copy Z and Cnt Ac-J Z, the Cnt Ac-J Z create pair operation can fail.
• ◦ LDEVs are blocked. ◦ The secondary system does not support FC Z. If the P-VOL of the Cnt Ac-J Z pair in the status of Duplex or the Pending Duplex is assigned to the T-VOL of the relationship of FC Z, the data on FC Z is copied to the P-VOL of Cnt Ac-J Z. When the data copy operation to the Cnt Ac-J Z P-VOL is completed, the initial copy operation to the Cnt Ac-J Z S-VOL will be started.
• When a THP V-VOL is used for a Cnt Ac-J Z P-VOL or S-VOL, the Cnt Ac-J Z of the allocated pages for the THP V-VOL is included in the Cnt Ac-J Z licensed capacity. If the actual licensed capacity exceeds the available licensed capacity, you may use Cnt Ac-J Z for 30 days. After 30 days, Cnt Ac-J Z pairs may only be split or released.
assigned to a Continuous Access Journal Z pair, the S-VOL must have the same capacity as the P-VOL. • To perform Virtual LVI operations on a pair’s P-VOL and S-VOL, the pair must be deleted and the volumes’ status returned to unpaired. Auto LUN You can specify the Continuous Access Journal Z P-VOL or S-VOL as Auto LUN source volumes. However, when Cnt Ac-J Z pair status is Pending or Duplex, do not perform the volume migration operation; otherwise, the operation is stopped.
B 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 and setup information for sharing Continuous Access Journal Z volumes with Continuous Access Synchronous Z.
Figure 18 3-data-center cascade configuration Failure recovery occurs as follows: • If a failure occurs at the Cnt Ac-S Z P-VOL, business continues because data in the Cnt Ac-J Z S-VOL is restored to the production system via the intermediate volume, if needed. Update sequence integrity is ensured. • If a failure occurs at both Cnt Ac-S Z P-VOL and S-VOL, an implemented disaster recovery plan would re-direct host activities to the Cnt Ac-J Z S-VOL.
• The response time for host I/Os will be the response time for Cnt Ac-S Z operation plus the creation time of journal data in the intermediate site. • The utilization rate on the local site with a 3DC cascade configuration is higher than if Cnt Ac-J Z and a Cnt Ac-S Z systems are used independently. • If you perform a Compatible FlashCopy copy operation on the Cnt Ac-S Z pair, the Cnt Ac-S Z pair status becomes Pending Duplex, and the Cnt Ac-J Z pair is suspended.
is paired with the Cnt Ac-J Z S-VOL.See “Delta resync configuration ” (page 144) for more information. • If a failure occurs in the Cnt Ac-S Z system (P-VOL and S-VOL), business is resumed using the Cnt Ac-J Z S-VOL. When the failure is corrected, business tasks are transferred back to the local site. • If a failure occurs in the Cnt Ac-J Z system (P-VOL and S-VOL), business is resumed using the Cnt Ac-S Z S-VOL.
You create the delta resync configuration by adding a second Cnt Ac-J Z pair to the 3DC multi-target configuration, using the Cnt Ac-S Z S-VOL and the Cnt Ac-J Z S-VOL, as illustrated in the following figure. The delta resync operation is performed when the local site fails. The following steps are used to set up and run the delta resync configuration: 1. Create the Cnt Ac-J Z delta resync pair. See “Creating the delta resync pair” (page 145). 2.
• If you plan to create in-system pairs on the remote site sharing the delta resync S-VOL, make sure to perform the delta resync create-pair operation first, then create in-system pairs. • You can set a back-up option in the event that the delta resync operation fails. This is done on the Change Mirror Options window (see the Delta resync Failure step in “Changing options used by mirrors ” (page 94)). Procedure 46 To create a Continuous Access Journal Z pair for delta resync pair 1. 2. 3.
Figure 20 Remote command devices in a delta resync configuration 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. Assigning mirrors to remote command devices You assign the mirror IDs used by the configuration’s journals to the remote command devices.
• On local site: - Assign mirror ID 0 to the remote command device that is mapped to the Cnt Ac-S Z remote site. - Assign the mirror ID used for the Cnt Ac-J Z 3DC multi-target pair to the remote command device that is mapped to the remote site. • On the Cnt Ac-S Z remote site: - Assign mirror ID 0 to the remote command device that is mapped to the local site. - Assign the mirror ID used for the Cnt Ac-J Z delta resync pair to the remote command device that is mapped to the Cnt Ac-J Z remote site.
4. In the Release Remote Command Devices window, review your selection in the Selected Mirrors table. If you need to make a change, select Cancel. 5. 6. 7. When ready, click Finish. In the Confirm window, review the settings and enter a task name in the Task Name box. Click Apply to save your settings to the system. Performing the delta resync operation You perform the delta resync operation using the resynchronize mirrors operation.
◦ The Cnt Ac-J Z delta resync pair: Hold or Holding. If the pair status is Hlde, change to Hold by performing the pairresync operation. This applies to all pairs in the journal in which the Cnt Ac-J Z pair for delta resync resides. ◦ The Cnt Ac-J Z volume used as the 3DC multi-target and the delta resync pair S-VOL and uses two mirror IDs — one for the 3DC multi-target pair and one for the delta resync pair: - 3DC multi-target S-VOL: Duplex or Suspended - Delta resync S-VOL: Hold.
• When the delta resync pair is created and no volumes (including volumes after failover or failback) in the local site are updated. • When the status of the Cnt Ac-J Z pair for delta resync operation becomes Hlde, the journal data necessary for the delta resync operation might be discarded. In this case, all data in the delta resync P-VOL would be copied to the delta resync S-VOL.
C 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 local and remote sites. This appendix provides configurations and information for using Business Copy Z with Continuous Access Journal Z. For details about Business Copy Z, see the HP XP7 Business Copy for Mainframe Systems User Guide.
Figure 21 Shared Cnt Ac-J Z and BC 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. If the above configuration is used in multiple journal volumes in multiple storage system, you can set the same starting time of the backup copy to all the journals.
Figure 23 Shared Cnt Ac-J Z volumes with BC Z primary volumes Configurations with Business Copy Z secondary volumes The following figure shows a BC Z primary volume used as the production volume. A remote Cnt Ac-J Z backup copy is made of the BC Z secondary volume. The BC Z pair must be in Split/SUSPOP status to perform the Cnt Ac-J Z operation.
D Cnt Ac-J Z GUI reference This appendix describes the Continuous Access Journal Z windows, dialog boxes, fields, and behaviors in the Remote Web Console GUI. Important: Procedures in this manual are tailored to the Remote Web Console (RWC) GUI. When using this GUI, “Local Storage System” displays for the system you have accessed on the RWC server. As a result, when you access the remote site’s RWC server, the GUI displays information for the pair’s remote (secondary) system under “Local Storage System”.
Item Description Data Capacity Total capacity of all the associated volumes. If the journal uses multiple mirror IDs, the capacity of volumes in mirrors with Hold, Holding, or Hold(Failure) status is not included. The following columns do not display unless you add them in the Remote Web Console Column Settings window. To open the window, in the Remote Replication window, Cnt Ac-J tab, click Options > Column Settings. MP Blade ID MP Blade identifier.
Item Description Attribute ECXTG attributes, which can be: • Master: Primary system EXCTG • Restore: Secondary system EXCTG • Initializing: Initialization is in progress. • Free: No journal is registered in the EXCTG. • Updating: Registering journals is in process. Number of Storage Systems Number of storage systems registered in the EXCTG. Number of Journals Number of journals registered in the EXCTG. Assigned Mirror ID EXCTG's mirror identifier.
Mirrors tab From this tab, you can review information about the selected journal’s mirrors. Item Description Mirror ID Mirror identifier. Attribute Whether the journal is Master, Restore, or Initial (registered but no pair volumes assigned). Status Mirror’s status. For definitions, see “Monitoring journal (mirror) status” (page 88). Remote Storage System Displays the following information about the system connected to the system you accessed.
Item Description Path Watch Time Interval from the time a path becomes blocked to the time when the mirror is suspended. A hyphen indicates the status of the secondary mirror on the primary system is Hold, Holding or Hold(Failure). Path Watch Time Transfer Whether to assign the master journal’s Path Watch Time value to the restore journal. Yes, No. Copy Pace Pace for copying data during initial copy: Slower is the default, Medium, Faster. A hyphen indicates the journal is a restore journal.
Item Description CLPR Journal volume’s CLPR number. The ID displays before the colon; the CLPR name displays after the colon. Resource Group Name (ID) LDEV’s resource group name and identifier. The ID is enclosed in parentheses. Assign Journal Volumes button Opens the Assign Journal Volumes window. Export button Opens the window for exporting table information Journal Properties window Use this window to view information about the selected journal.
Item Description Cache Mode Whether journal data is stored in cache memory on the remote side (restore journal). Timer Type Cnt Ac-J Z only. Type of clock used for consistency time. Must be the same for primary and secondary systems. Number of Journal VOLs Number of journal volumes registered in the journal. Journal Capacity Total capacity of registered journal volumes.
Settings Item Description System Type Storage system type: Open or Mainframe. Journal ID Identifier for the journal, displayed in ascending order. Blank if no number is available. Journal Volume Selection • Select Journal Volumes: When clicked, opens the Select Journal Volumes dialog box. • Total Selected Journal Volumes: Number of selected journal volumes. • Total Selected Capacity: Capacity of selected journal volumes. Journal Type Option Types of journal options that can be specified.
Item Description Cache Mode Whether to store journal data in cache memory on the remote side. • Enable: Data is stored in cache. • Disable: Data is not stored in cache. Timer Type Cnt Ac-J Z only. Type of clock used for consistency time. Values must be the same on primary and secondary systems. • System: Mainframe system clock. • Local: Host I/O time stamp. • None: Host I/O time stamp. Available only when copy direction is reversed, S-VOL to P-VOL.
Select Journal Volumes dialog box Available LDEVs table Item Description LDEV ID Journal volume’s identifier consisting of the LDKC number, CU number, and LDEV number. Clicking the link opens the LDEV Properties window. LDEV Name Name of the journal volume’s LDEV. Pool Name (ID) Identifier consisting of the pool name and the pool ID. Clicking the link opens a window with pool information. RAID Level Type of RAID implementation for the journal volume. Capacity Journal volume’s capacity.
Item Description CLPR Journal volume’s CLPR number. The ID displays before the colon; the CLPR name displays after the colon. Resource Group Name (ID) LDEV’s resource group name and identifier. The ID is enclosed in parentheses. Confirm window Item Description Journal ID Identifier for the journal LDEV, displayed in ascending order. Blank of no number is available. Journal Type Journal copy type, Cnt Ac-J or Cnt Ac-J Z. If the pair is part of a 2DC cascade configuration, “2DC cascade” displays.
Assign Journal Volumes wizard Use this wizard to assign journal volumes to a journal. Assign Journal Volumes window Use this window to assign journal volumes to a journal. For full information, see “Creating journals and adding journal volumes ” (page 64), and “Adding additional journal volumes to an existing journal” (page 96). Unassigned Journal Volumes table Item Description LDEV ID Journal volume’s LDEV identifier: LDKC number, CU number and LDEV number. LDEV Name Journal volume’s LDEV name.
Item Description Resource Group Name (ID) LDEV's resource group name and ID (in parentheses). Removable Wether the journal volumes can be removed (Yes or No). If the mirror status to which the journals belong is Active, the journal volumes cannot be removed. Confirm window Selected Journal table Item Description Journal ID Journal identifier. Assigned Journal Volumes table Item Description LDEV ID Journal volume’s LDEV identifier: LDKC number, CU number and LDEV number.
Item Description Capacity Journal volume capacity. CLPR Journal volume’s CLPR ID and name. Resource Group Name (ID) LDEV's resource group name and ID (in parentheses). Unassigned Journal Volumes table Item Description LDEV ID Journal volume’s LDEV identifier: LDKC number, CU number and LDEV number. LDEV Name Journal volume’s LDEV name. Pool Name (ID) Journal volume’s pool name and ID. RAID Level Journal volume’s RAID level. Capacity Journal volume capacity.
Item Description Journal ID Journal identifier. Journal Type Journal copy type, Cnt Ac-J or Cnt Ac-J Z. If the pair is part of a 2DC cascade configuration, “2DC cascade” displays. Number of Journal VOLs Number of journal volumes registered in the journal. Journal Capacity Total capacity of the journal’s journal volumes. Detail button When clicked, opens the Journal Properties window for the selected journal.
Item Description Journal ID Journal identifier. Mirror ID Mirror identifier EXCTG Setting • EXCTG ID: EXCTG identifier • Super DKC: Super DKC’s serial number and controller ID. Edit Journal Options wizard Use this wizard to change journal options. Edit Journal Options window Use this window to change journal options. For full information, see the procedure in “Changing options used by journals ” (page 92).
Item Description Inflow Control Whether flow of update data to the journal volume is restricted by slowing the response to hosts. Data Overflow Watch Number of seconds the system will monitor write data to the journal volume when the journal volume is full (100%). The field is blank if Inflow Control is disabled. Cache Mode Whether journal data is stored in cache memory on the remote side (restore journal). Timer Type Cnt Ac-J Z only. Type of clock used for consistency time.
Item Description Number of Journal VOLs Number of journal volumes registered in the journal. Journal Capacity Total capacity of the journal’s journal volumes. Number of Data VOLs Number of volumes associated with the journal. If the journal uses multiple mirror IDs, volumes in mirrors with Hold, Holding, or Hold(Failure) status are not included. Data Capacity Total capacity of all the associated volumes.
Confirm window Item Description Journal ID Journal identifier. Journal Type Journal copy type, Cnt Ac-J or Cnt Ac-J Z. If the pair is part of a 2DC cascade configuration, “2DC cascade” displays. Attribute Whether the journal is Master, Restore, or Initial (registered but no pair volumes assigned). Number of Journal VOLs Number of journal volumes registered in the journal. Journal Capacity Total capacity of the journal’s journal volumes.
Item Description Path Watch Time Interval from the time a path becomes blocked to the time when the mirror is suspended. Path Watch Time Transfer Whether to assign the master journal’s Path Watch Time value to the restore journal. Yes or No. Copy Pace Pace for copying data during initial copy: Slower is the default, Medium, Faster. Transfer Speed Data transfer line speed in Mbps (megabits per second): 10, 100, 256.
Confirm window Item Description Journal ID Journal identifier. Mirror ID Mirror identifier. Journal Type Journal copy type, Cnt Ac-J or Cnt Ac-J Z. If the pair is part of a 2DC cascade configuration, “2DC cascade” displays. Attribute Whether the journal is Master, Restore, or Initial (registered but no pair volumes assigned). Status Mirror’s status. Path Watch Time Interval from the time a path becomes blocked to the time when the mirror is suspended.
Item Description Data Capacity Total capacity of all the associated volumes. If the journal uses multiple mirror IDs, the capacity of volumes in mirrors with Hold, Holding, or Hold(Failure) status is not included. Remote Command Device LDEV number of the remote command device if it is assigned to the mirror. • The column is blank if the remote command device is not assigned to the mirror. • A hyphen (-) indicates the remote command device cannot be assigned to the mirror.
Confirm window Item Description Journal ID Journal identifier. Mirror ID Mirror identifier. Remote Command Device LDKC, CU, and LDEV numbers of the remote command device assigned to the mirror. Release Remote Command Devices window Use this window to release a remote command device from a mirror.
Selected Mirrors table Item Description Journal ID Journal identifier. Mirror ID Mirror identifier. Remote Command Device LDKC, CU, and LDEV numbers of the remote command device assigned to the mirror. Journal Type Journal copy type, Cnt Ac-J or Cnt Ac-J Z. If the pair is part of a 2DC cascade configuration, “2DC cascade” displays. Attribute Whether the journal is Master, Restore, or Initial (registered but no pair volumes assigned). Status Mirror’s status.
Item Description EXCTG ID EXCTG identifier. Attribute ECXTG attributes. • Master: Primary system's EXCTG • Restore: Secondary system's EXCTG • Initializing: Initialization is in progress. • Free: No journal is registered in the EXCTG. • Updating: Registering journals is in process. Consistency Time Consistency time of the extended consistency group. For more information, see “Consistency time” (page 51). Number of Storage Systems Number of storage systems registered in the EXCTG.
Item Description Add Local Storage System’s Journals Whether or not to register the local storage system’s journals to EXCTGs. Mirror ID Mirror identifier for the journal to be registered. EXCTG configuration Item Description Local Model and serial number of the storage system you accessed. Add Clicking allows selection of remote (secondary) system journals for registration in the EXCTG. Local Storage System The accessed storage system model and serial number.
Item Description Journal ID Journal’s identifier. Selected Number of selected journals in relation to the total number of journals.. Confirm window Selected EXCTG table Item Description EXCTG ID EXCTG identifier. Mirror ID Mirror’s identifier. Selected Storage Systems table Item Description Model / Serial Number Storage system’s model and serial number. Remote Command Device Remote command device LDKC number, CU number, and LDEV number. A hyphen (-) displays for a local storage system.
Selected Journals table Item Description EXCTG ID EXCTG identifier. Journal ID Journal’s identifier. Remove Journal wizard Use this wizard to remove journals from an EXCTG. Remove Journal window Use this window to remove journals from an EXCTG. For full information, see the procedure in “Removing journals from an EXCTG ” (page 56). Item Description Mirror ID Mirror identifier for the newly registered journal.
Remote Command Device Item Description Remote Command Device Remote command device LDKC number, CU number, and LDEV number. A hyphen (-) displays for a local storage system. Confirm window Selected Journals table Item Description EXCTG ID EXCTG identifier. Model / Serial Number Storage system’s model and serial number. Journal ID Journal’s identifier. Mirror ID Mirror’s identifier. Total Total number of journals to be removed.
Item Description EXCTG ID EXCTG identifier. Model / Serial Number Storage system’s model and serial number. Journal ID Journal’s identifier. Mirror ID Mirror’s identifier. Total Total number of journals to be removed from the EXCTG. View Pair Synchronous Rate window Use this window to view the percentage of synchronized data between P-VOL and S-VOL. For detailed information, see “Monitoring Cnt Ac-J Z pair synchronous rate” (page 86).
Item Description - Only attributes that are specified display. - “CVS” displays at the end of the device name, if the virtual CVS attribute is specified. - A blank indicates no values are specified. • Virtual SSID: Volume’s virtual SSID. A blank indicates that no virtual SSID is specified. Copy Type Type of pair: • Cnt Ac-J: Continuous Access Journal • Cnt Ac-J Z: Continuous Access Journal Z Status Pair’s status. For information, see “Pair status definitions” (page 80).
Pair Properties Item Description Local Storage System Displays pair information about the storage system you have accessed in Remote Web Console. box • LDEV ID (LDEV name): LDEV identifier and name. “---” displays for long names. Hover the mouse over it to display the complete name. • Number of LUN paths: Number of data paths between primary and secondary systems. Clicking the number displays the path list (Cnt Ac-J only). • Emulation Type, Capacity: System’s emulation type and capacity.
Item Description • Emulation type, Capacity: System's volume emulation type and capacity. • Journal ID: Journal identifier. • Model/Serial number: System’s model, serial number. Pair Detail Item Description Status The pair’s status CTG ID Consistency group identifier Reverse Resync Indicates that a reverse resync has changed the copy direction. Error Level Whether pairs are split if an error occurs. Specified during the create pair procedure. Secondary Volume Written Cnt Ac-J Z only.
For full information, see the procedure in “Splitting Cnt Ac-J Z pairs ” (page 71). Selected Pairs table Item Description Local Storage System Displays the following information about pair volumes in the accessed system. • LDEV ID: Pair volume LDEV identifier. • LDEV Name: Pair volume LDEV name. • Pair Position: Identifies the volume as primary or secondary. • Journal ID: Journal identifier. • Mirror ID: Mirror identifier • Emulation Type: Pair volume emulation type.
Settings Item Description Secondary Volume Write Whether data can be written to the S-VOL while the pair is split. • Enable: Data can be written to the S-VOL. Available only when the selected mirror’s Attribute is Master. If Restore, Disable is used automatically • Disable: The default. Data cannot be written to the S-VOL. Confirm window Selected Pairs table Item Description Local Storage System Displays the following information about pair volumes in the accessed system.
Item Description Split Mode Whether update data is written to S-VOLs in the mirror before the split operation. • Flush: Data is copied to S-VOLs. • Purge: Data is not copied to S-VOLs until resynchronization. Remote Storage System Displays the following information about pair volumes in the system connected to the system you accessed. • Model/Serial Number: Storage system model name and serial number. • LDEV ID: Pair volume LDEV identifier • Journal ID: Journal identifier.
Item Description Journal Type Journal copy type, Cnt Ac-J or Cnt Ac-J Z, plus one of the following journal type options: • Standard, a normal pair • 2DC cascade If Standard is the journal type option, then only the copy type displays. Journal type options are defined in the Create Journals window. Attribute Mirror’s attribute — Master, Restore, or Initial. • Master displays when the P-VOL is paired (initial copy performed). • Restore displays when the S-VOL is paired (initial copy performed).
Confirm window Selected Mirrors table Item Description Journal ID Journal identifier. Mirror ID Mirror’s identifier Journal Type Journal copy type, Cnt Ac-J or Cnt Ac-J Z, plus one of the following journal type options: • Standard, a normal pair • 2DC cascade If Standard is the journal type option, then only the copy type displays. Journal type options are defined in the Create Journals window. Attribute Mirror’s attribute — Master, Restore, or Initial.
Item Description Remote Storage System Displays the following information about pair volumes in the system connected to the system you accessed. • Model/Serial Number: Storage system model name and serial number. • LDEV ID: Pair volume LDEV identifier • Journal ID: Journal identifier. Path Group ID Path group’s identifier. Number of Data VOLs Number of volumes associated with the journal. Data Capacity Total capacity of all the data volumes.
Selected Pairs table Item Description Local Storage System Displays the following information about pair volumes in the accessed system. • LDEV ID: Pair volume LDEV identifier. • LDEV Name: Pair volume LDEV name. • Journal ID: Journal identifier. • Mirror ID: Mirror identifier. • Emulation Type: Pair volume emulation type. • Capacity: Pair volume capacity. • CLPR: CLPR number. Copy Type Type of pair: • Cnt Ac-J: Continuous Access Journal • Cnt Ac-J Z: Continuous Access Journal Z Status Pair status.
Confirm window Item Description Local Storage System Displays the following information about pair volumes in the accessed system. • LDEV ID: Pair volume LDEV identifier. • LDEV Name: Pair volume LDEV name. • Journal ID: Journal identifier. • Mirror ID: Mirror identifier. • Emulation Type: Pair volume emulation type. • Capacity: Pair volume capacity. • CLPR: CLPR number. Copy Type Type of pair: • Cnt Ac-J: Continuous Access Journal • Cnt Ac-J Z: Continuous Access Journal Z Status Pair status.
Resync Mirrors wizard Use this wizard to resynchronize mirrors. Resync Mirrors window Use this window to resynchronize mirrors. For full information, see the procedure in “Resynchronizing mirrors ” (page 75). Selected Mirrors table Item Description Journal ID Journal identifier.
Item Description Number of Data VOLs Number of volumes associated with the journal. Data Capacity Total capacity of all the data volumes. If the journal uses multiple mirror IDs, the capacity of volumes in mirrors with Hold, Holding, or Hold(Failure) status is not included. Remote Command Device LDEV number of the remote command device if it is assigned to the mirror. • The column is blank if the remote command device is not assigned to the mirror.
Item Description • Capacity: Pair volume capacity. • CLPR: CLPR number. Copy Type Type of pair: • Cnt Ac-J: Continuous Access Journal • Cnt Ac-J Z: Continuous Access Journal Z Status Pair status. Delete Mode Options for deleting pairs. Only Normal is available. Remote Storage System Displays the following information about pair volumes in the system connected to the system you accessed. • Model/Serial Number: Storage system model name and serial number.
Delete Mirrors wizard Use this wizard to delete mirrors. Delete Mirrors window Use this window to delete mirrors. For full information, see the procedure in “Deleting pairs in a mirror ” (page 77). Item Description Journal ID Journal identifier. Mirror ID Mirror’s identifier Journal Type Journal copy type, Cnt Ac-J or Cnt Ac-J Z, plus one of the following journal type options: • Standard, a normal pair • 2DC cascade If Standard is the journal type option, then only the copy type displays.
Item Description Remote Command Device LDEV number of the remote command device if it is assigned to the mirror. • The column is blank if the remote command device is not assigned to the mirror. • A hyphen (-) indicates the remote command device cannot be assigned to the mirror. CTG ID Consistency group identifier. CTG Utilization Whether the consistency group is shared by multiple storage systems. • Single: The consistency group consists of a single pair of primary and secondary storage systems.
Item Description Delete Mode Shows whether mirrors are deleted forcibly or not. Remote Storage System Displays the following information about pair volumes in the system connected to the system you accessed. • Model/Serial Number: Storage system model name and serial number. • Journal ID: Journal identifier. Path Group ID Path group identifier. Number of Data VOLs Number of volumes associated with the journal. Data Capacity Total capacity of all the data volumes.
Item Description Whether CFW data is copied to the S-VOL or not. • Primary Volume Only: Data is not copied to the S-VOL. • Secondary Volume Copy: Data is copied to the S-VOL. Confirm window Item Description Local Storage System Displays the following information about pair volumes in the accessed system. • LDEV ID: Pair volume LDEV identifier. • LDEV Name: Pair volume LDEV name. • Pair Position: Whether the volume is a primary or secondary volume • Journal ID: Journal identifier.
Item Description Whether CFW data is copied to the S-VOL or not. • P-VOL Only: Data is not copied to the S-VOL. • Copy to S-VOL: Data is copied to the S-VOL. Remote Storage System Displays the following information about pair volumes in the system connected to the system you accessed. • Model/Serial Number: Storage system model name and serial number. • LDEV ID: Pair volume LDEV identifier • Journal ID: Journal identifier. Path Group ID Path group identifier.
Glossary allocation The ratio of allocated storage capacity versus total capacity as a percentage. Allocated storage refers to those logical devices (LDEVs) that have paths assigned to them. Allocated storage capacity is the sum of the storage of these LDEVs. Total capacity is the sum of the capacity of all LDEVs on the disk array. BC P9000 or XP Business Copy. An HP application that provides volume-level, point-in-time copies in the disk array.
to be associated with 1 to 36 LDEVs. Essentially, LUSE makes it possible for applications to access a single large pool of storage. M-VOL Main volume. MCU Main control unit. OPEN-x A general term describing any of the supported OPEN emulation modes (for example, OPEN-E). There are two types of OPEN-x devices: legacy OPEN-x devices with a fixed size (such as OPEN-3, OPEN-8, OPEN-9, and OPEN-E), and OPEN-V, which has a variable size and is a CVS-based volume.
Index Symbols 3 data center configurations, 141 A Auto LUN, 140 Auto LUN V2 volumes, 136 B BCM specifications, 19 Business Copy Z volumes, 135, 152 business requirements, assessing, 22 C cables and switches, 47 Cache and Nonvolatile Storage (NVS), 19 cache changes and pair status, 83 Cache Residency Manager volumes, 135 Cache Residency Z, 137 cache-fast-write, options for, 90 calculating bandwidth, 41 cascade configuration with Cnt Ac-S Z, 141 Cnt Ac-J Z set up, 62 Cnt Ac-S Z removing pair relationship,
I P initial copy overview, 14 initiator port, 46 packet loss, 45 pair creating, 69 deleting, 77 deleting forcibly, 91 maintenance, 90 operations history, 86 operations workflow, 68 options for system response to failure, 90 resynchronizing, 74 split option, changing, 90 splitting, 71 status and changing cache or shared memory, 19, 83 status definitions, 80 troubleshooting, 117 pair volumes description, 12 planning considerations, 27 Parallel Access Volumes, 135 path group, 18 point-in-time copy, 73 ports
a pair, 74 reverse copy direction to primary site, 106 RIO MIH, 63 role required for operations, 61 rolling averages and cycle time, 44 RPO, 23 S S-VOL, taking over host operations, 106 saving pair information, 88 secondary systems, connecting, 34 Service Information Messages, 129 shared memory changes, and pair status, 19, 83 sharing secondary volumes, 154 sharing volumes, 152 SIMs, 129 sizing bandwidth, 40 Smart Tiers Z volume, 135 splitting a pair, 71 storage capacity values conventions, 133 storage sys
