HP XP7 Continuous Access Journal User Guide Abstract This document describes and provides instructions for using Continuous Access Journal to plan, configure, and perform pair operations on 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 overview ............................................................8 Continuous Access Journal software ...........................................................................................8 How Continuous Access Journal works........................................................................................8 Hardware and software components...........................................................................................9 XP7 storage systems.......
Sizing bandwidth for peak write-workload........................................................................34 Sizing bandwidth for peak rolling average write-workload..................................................36 Latency .......................................................................................................................38 Packet loss ...................................................................................................................
Modifying data-transfer time threshold .................................................................................82 Deleting remote paths ........................................................................................................82 Deleting the Cnt Ac-J relationship ........................................................................................83 Managing power-off for systems and network devices .................................................................
Resource Partition.................................................................................................................121 Fast Snap............................................................................................................................121 Configurations with FS volumes..........................................................................................121 External Storage....................................................................................................
Assign Remote Command Device window...........................................................................159 Confirm window..............................................................................................................160 Release Remote Command Devices window.............................................................................160 View Pair Synchronous Rate window.......................................................................................161 View Pair Properties window.
1 Continuous Access Journal overview With Continuous Access Journal (Cnt Ac-J), 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 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.
1. 2. 3. 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. • 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. Journal copy - Data is copied from the master journal to the restore journal.
Management software consists of: • Remote Web Console graphical user interface (GUI) • RAID Manager Continuous Access Journal components are illustrated in the following figure and described in greater detail in the following topics. Figure 2 Continuous Access Journal components XP7 storage systems Continuous Access Journal can be operated using two XP7 systems, one at the local site and one at the remote site. The primary system consists of the main control unit and the .
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. When re-synchronized, changed data is copied to the S-VOL. If a disaster occurs, production operations can be transferred to the S-VOL.
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 requires paths in both directions. More specifically, it requires paths with Initiator ports in the primary system connected to RCU Target ports in the secondary system, and paths with Initiator Ports in the secondary system connected to RCU Target ports in the primary system. One data path connection is required.
Update copy operation When a host has new or changed information, the following occurs in the primary system: • The update is written to the P-VOL • The update is copied to the master journal along with metadata that includes sequence and other consistency information. The secondary system issues the read-journal command (independent of host I/O activity). At this time, the following occurs: ◦ Any data in the master journal is sent to the restore journal. ◦ The updated data is copied to the S-VOL.
resynchronized, the primary system merges the P-VOL and S-VOL bitmaps, and the differential data is copied to the S-VOL. The number of bitmap areas affects the maximum possible number of pairs that can be created in the system. S-VOL write option When splitting a pair, you can set an option allowing write I/O to the S-VOL.
2 Requirements and specifications This chapter provides system requirements for Continuous Access Journal. System requirements Continuous Access Journal operations are performed from the primary system to the secondary system, which contain the Cnt Ac-J 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 components are listed below.
Table 1 General system requirements (continued) Item Requirement Continuous Access Journal • 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 licensing capacity requirements when Cnt Ac-J volumes are shared with other XP7 software volumes, see “Thin Provisioning ” (page 120) • For information on expired licenses or exceeding licensed capacity, see the HP XP7 Remote Web Console User Guide.
Table 1 General system requirements (continued) Item Requirement sample configuration definition files in HP XP7 RAID Manager Installation and Configuration User Guide. • It is recommended that you specify different paths and path groups for Cnt Ac-S and Cnt Ac-J secondary systems when using CU Free. Pair volumes • A P-VOL may be copied to one S-VOL. • The P-VOL and S-VOL must be equal in size. • The P-VOL and S-VOL must be of same emulation type.
Table 1 General system requirements (continued) Item Requirement Host failover software Required for disaster recovery. RAID Manager consistency groups • Up to four journals can be registered in one RAID Manager consistency group when multiple primary and number. If there are four systems, you must create one journal for each system. secondary system • Up to 8,192 pairs. You can register the total number of pairs in the journals within one RAID Manager consistency group.
3 Planning volumes, XP7 systems This chapter provides information and instructions for planning Continuous Access Journal volumes, XP7 systems, and other important requirements and restrictions. Plan and design workflow Planning the Continuous Access Journal 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 20). 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.
• Master and restore journals are managed according to the journal ID. • Review journal specifications in “System requirements” (page 15). • 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. • Volumes in a virtual storage machine cannot be used as journal volume.
You will have two options for specifying how the system matchs S-VOLs to P-VOLs. - Interval: The interval you specify will be skipped between LDEV numbers in the secondary system. For example, suppose you specify LU 01 as the initial (base) S-VOL, and specify 3 for Interval. This results in secondary system LDEV 04 being assigned to the next P-VOL, 07 assigned to the subsequent P-VOL, and so on. To use Interval, you set up secondary system LDEV numbers according to the interval between them.
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. • Number of logical blocks indicates volume capacity measured in blocks.
must be subtracted from 65,536, with the difference used to calculate the maximum number of pairs for Continuous Access Journal. ◦ • If Continuous Access Synchronous and Continuous Access Journal share the same volume, you must use the total number of bitmap areas for both pairs regardless of whether the shared volume is primary or secondary. The maximum number of pairs supported per storage system, which is 65,280. If RAID Manager is used, it is 65,279.
See the step for Priority in the procedure in “Creating the Cnt Ac-J initial copy ” (page 43). Disaster recovery considerations You begin a disaster recovery solution when planning the Cnt Ac-J system. The following are the main tasks for preparing for disaster recovery: • Identify the data volumes that you want to back up for disaster recovery. • Pair the identified volumes using Cnt Ac-J. • Establish file and database recovery procedures.
When data is sent to the secondary systems, the systems check time stamps, which are added when data is written by the hosts to the P-VOLs. The secondary systems then restore the data to the S-VOLs in chronological order (older data are restored earlier). This ensures that the update sequence is maintained. Note the following when planning for multiple systems: 28 • Remote Web Console is required at the primary and secondary sites.
• Restoring data to the secondary system is performed when the time stamp of the copied journal is updated. The recommended interval between time stamps is one second. Consider the following before setting the interval: ◦ I/O response time slows when time stamps are updating among multiple storage systems. If you shorten the interval, more time stamps are issued, resulting in an I/O response time that is slower yet.
• Up to 65,280 volumes can be used for volume pairs. • XP7 and P9500 or XP24000/XP20000 Disk Array can be set up in 3-data-center (3DC) cascade or multi-target configurations. These configurations are used when combining Continuous Access Synchronous and Continuous Access Journal systems. See “Configurations with Continuous Access Synchronous” (page 124) to review these configurations. There are no restrictions for combining primary and secondary sites between XP7 and P9500 or XP24000/XP20000 Disk Array.
The following table lists and describes the SOMs for Continuous Access Journal. For a complete list of SOMs for the XP7, see the HP XP7 Owner Guide. NOTE: The SOM information may have changed since this document was published. Contact your HP representative for the latest SOM information. Table 2 System option modes Mode Description 448 When the SVP detects a blocked path: Mode 448 ON: An error is assumed and the mirror is immediately suspended.
Table 2 System option modes (continued) Mode Description 3. If this mode is not set to ON for both sides, the behavior is as follows: - ON in the primary system/OFF in the secondary system: Cnt Ac-S Sync pair creation fails. - OFF in the primary system/ON in the secondary system: The update data is copied to the S-VOL synchronously. 4.
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. 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 36 Planning the data path
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 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 9 (page 41). 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 10 (page 42).
Figure 10 Switch connection configuration Figure 11 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 Cnt Ac-J pair operations This chapter provides instructions for performing Continuous Access Journal 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 operations. • Check pair status. Each Cnt Ac-J 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.
Procedure 1 To create an initial copy or copies 1. 2. 3. 4. 44 In the Storage Systems tree, click Replication > Remote Replication, and then select the Cnt Ac-J Pairs tab. From the Actions menu, click Remote Replication > Create Pairs. In the Create Pairs window, for Copy Type, select Continuous Access Journal. For Remote Storage System, select the secondary system’s Model/Serial Number and Path Group ID.
5. 6. In the Primary Volume Selection box, in LU Selection select the Port ID and Host Group Name to display the volumes from which you want to select the P-VOL. In the Available LDEVs table, select the volume to be the P-VOL. NOTE: 7. Available LDEVs limitations: • When using a virtual storage machine with XP7, Available LDEVs displays physical LDEV information, not virtual. • Online Migration volumes do not display in Available LDEVs.
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 COPY or PAIR Delta HOLD, HOLDING You can also monitor the progress of the operation by clicking File > Refresh in the menu bar. This updates the information in the list. Splitting Cnt Ac-J pairs When you split a pair, write-data is no longer sent to S-VOL and the pair is no longer synchronized.
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.
Prerequisites for resynchronizing pairs • This operation is performed from the primary system only. • Pair status must be PSUS or PSUE. If pair status is HOLD, HOLDING, or HLDE, use the resynchronizing mirrors operation (see “Resynchronizing mirrors ” (page 50)). • Pairs suspended by the system (PSUE status) can be resynchronized after the error causing the suspension is corrected.
4. 5. 6. 7. 8. For Copy Priority list, specify the scheduling order for resynchronizing selected pairs, between 1 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. • LU: 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.
6. 7. 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 pairs When you delete a pair, the Cnt Ac-J relationship between the P-VOL and S-VOL is released. Only the relationship is affected, the data volumes and their data remain. Prerequisite information • This operation can be performed from the primary or secondary system.
5. For Delete Mode, Normal is used for Cnt Ac-J. CAUTION: 6. 7. 8. Please note the following: • Forced deletion in the primary system results in data that was not yet sent to the secondary system being deleted. • Forced deletion in the secondary system results in data that was not yet restored being deleted. • If pair status has not changed to SMPL five minutes after you forcibly delete the pair, delete it again.
5. 6. 7. 8. For Delete Mode, specify one of the following: • Normal: Mirrors are deleted only if the primary system can change the mirror status to Initial. • Force: Mirrors are forcibly deleted even when the primary system cannot communicate with the secondary system. 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.
6 Cnt Ac-J configuration operations This chapter provides instructions for configuring Continuous Access Journal. Configuration workflow Setup for Continuous Access Journal using Remote Web Console consist of the following operations. You must have Storage Administrator (Remote Copy) role to perform Continuous Access Journal operations. 1. Navigate to Remote Web Console. 2. Define the fibre-channel port attributes. See “Defining fibre-channel port attributes ” (page 54), 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 Open 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) NOTE: With XP7 when using virtual storage machine volumes, make sure to specify the XP7's physical serial number. A virtual storage machine's serial number cannot be specified. 7. 8.
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 ” (page 55). Procedure 11 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 15) ◦ “Planning journals ” (page 22) ◦ “Planning journal volumes ” (page 23) • 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. • Cache Residency settings cannot be defined for the volumes. Procedure 12 To create journals 58 1. 2. 3. 4.
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 standalone pairs and pairs in a 3DC configuration.
NOTE: This setting does not effect master journals unless the RAID Manager horctakeover command is used to change a master journal into a restore journal. 13. Click Finish. 14. In the Confirm window, review the settings and enter a task name in the Task Name box. To review additional information about the journal, select the journal and click Detail. 15. Click Apply to save your settings to the system. Assigning an MP blade to a journal 60 1. 2. 3. 4.
7 Monitoring the Cnt Ac-J system Monitoring pairs, journals, data paths, I/O, and hardware performance is crucial for ensuring that Continuous Access Journal pairs continue to function correctly. This topic provides information and instructions for monitoring a Continuous Access Journal system. Monitoring pair activity, status, license capacity Monitoring the Continuous Access Journal 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 RAID 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 RAID 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. This is noted.
RWC status RAID Manager status Description PSUS SSUS P-VOL access The pair has been split by the user and the P-VOL and Read/Write S-VOL are no longer synchronized. • The primary and secondary systems keep track of journal data discarded during the split operation. S-VOL access Read Only, unless write option is enabled. • When the operation is performed on the primary system, the status of both the P-VOL and S-VOL changes to PSUS.
RWC status RAID Manager status Description HLDE (No parallel RAID Manager status) • An error occurred on a pair in HOLD status. P-VOL access S-VOL access Read/Write - Read /Write Read Only, unless write option is enabled. Read Only Read/Write • When P-VOL status is HLDE, incoming write data for the Cnt Ac-S S-VOL is not stored in the master journal volume.
Additional information on pair status • When a pair is split by the user or suspended by the system, the primary system notifies the host(s) with a service information message (SIM). If SNMP is installed and operational for XP7, this SIM results in an SNMP trap indicating the reason for suspension. • Transitional states occur when a request is accepted to change pair status to PSUS, PSUE, or to delete the pair, but is not yet complete. Transition states are not reported to the host.
PSUS type Volume PSUS type applies Description to RAID Manager displays this PSUS type as SSWS. PSUS, by MCU S-VOL • The secondary system received a request from the primary system to split the pair. • The P-VOL PSUS type is PSUS-S-VOL by Operator. • RAID Manager displays this PSUS type as SSWS. PSUS, by RCU P-VOL, S-VOL • The primary system suspended the pair after detecting an error condition on the secondary system. • The S-VOL suspend type is PSUE-S-VOL Failure.
Table 3 S-VOL consistency statuses Consistency status Description Volume • Only the current pair was split or suspended. • Update sequence consistency between this S-VOL and other S-VOLs in the associated journal is not ensured. • This S-VOL cannot be used for disaster recovery at the remote site. • This status is indicated when: - The pair is split by the user using the Suspend Range-Volume (LU) pairsplit option. - The pair is suspended due to a failure that did not affect the entire journal.
When a pair is suspended, the primary system stops performing journal-obtain operations for the pair. However, the primary system continues the following operations: • Continues accepting write I/Os for the suspended P-VOL • Keeps track of the P-VOL cylinders/tracks that are updated • Keeps track of journal data discarded during the pair suspension. (Both primary and secondary systems do this.
Note the following when viewing histories. • The Description column displays the operation that was run. The Descriptions are explained in the following table. • “LDEV ID” indicates the XP7 physical LDEV ID, even when you use RAID Manager and use pair volumes in a virtual storage machine. Operation descriptions The following table describes the operations shown in the Histories window. Operation Displayed Description Pair definition A pair was defined.
Operation Displayed Description Status Change by RCU(COPY to SMPL; Pairsplit-S Start) An operation for releasing a pair has been started at the secondary system. The status of the pair will change from COPY to unpaired (SMPL). Status Change by RCU(PAIR to SMPL; Pairsplit-S Start) An operation for releasing a pair has been started at the secondary system. The status of the pair will change from PAIR to unpaired (SMPL).
Remote Web Console mirror status definitions Status Description Initial Data volumes are registered in the mirror. Active The mirror has pairs that are synchronized, or the initial copy is in progress. If a mirror in Active status contains pairs that are split, a warning appears. The split pairs must be re-synchronized. Active (Warning) The mirror status is Active; some pairs in the mirror are split. HaltAccept The status at the beginning of a mirror-split operation.
Monitoring Cnt Ac-J remote connections, path status Use the following procedure to navigate to remote connection and remote path status. For remote path status definitions and troubleshooting, see “Remote paths status probelms” (page 97). Procedure 18 To view remote connection status, path information 1. 2. In the Storage Systems tree, click Replication > Remote Connections. Check the Status field. To view more information, click Actions > Remote Replication > View Remote Connection Properties.
8 Maintaining the Cnt Ac-J 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 system. Pair maintenance You must have Storage Administrator (Remote Copy) role to perform Continuous Access Journal maintenance operations.
Procedure 20 To change pair options 1. 2. 3. In the Storage Systems tree, click Replication > Remote Replication. Select the Cnt Ac-J Pairs tab, and then select the pair whos options are to be changed. 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. 6. 7.
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.
6. 7. 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 79). Procedure 25 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.
6. 7. 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.
Remote path maintenance This topic provides the following: • Modifying data-transfer time threshold • “Deleting remote paths ” (page 82) • “Deleting the Cnt Ac-J relationship ” (page 83) Modifying data-transfer time threshold You can modify the threshold for data transfer to complete. If the threshold value is reached, the transfer is flagged as failing by the system. Prerequisite information • This operation can be performed from the primary or secondary system.
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 relationship You can remove the Continuous Access Journal 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.
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 COPY or PAIR. After turning power on or off for both the primary and secondary system at the same time, if pair status at primary system is PSUS and a status of a pair of secondary system is PAIR, use Remote Web Console to suspend the pair of the secondary system.
9 Cnt Ac-J 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 pairs are configured in 3-data-center (3DC) configurations with three Cnt Ac-J sites, and with Continuous Access Synchronous/Cnt Ac-J sites. Recovery when Cnt Ac-J pairs are shared with Business Copy pairs is also included.
You detect and re-create lost updates by checking database log files and other current information at the local site. Design your recovery plan so that detection and retrieval of lost updates is performed after the application is started at the remote site. The detection and retrieval process can take some time. Prepare for file and database recovery using files for file recovery (for example, database log files that have been verified as current).
Resuming host operations at the local site When Cnt Ac-J pairs are established in the reverse direction between the remote and local sites, you can return host operations to the original configuration. This means resuming host operations at the local site and reestablishing the original flow of data from primary to secondary systems. The following procedure explains how to resume normal operations at the local site. 1. At both sites, make sure that Cnt Ac-J components are operational. 2.
Recovery for 3 Cnt Ac-J/Cnt Ac-S DC multi-target configuration The recovery procedure you perform in a 3DC multi-target configuration depends on the location of the failure: • For failure in the local site only — see “Recovering from local site failure ” (page 90).
Recovering from local and remote site failure (3DC multi-target) Host operations are transferred to the Continuous Access Journal S-VOL in the remote site when a disaster or failure occurs in both the primary and Continuous Access Synchronous 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 35 To recover a primary and Cnt Ac-S intermediate site failure 1. 2. 3. 4. 5. 6. 7. 8. 9.
Prerequisite information • For information and illustrations on the configuration covered in this procedure, see “Delta resync configuration ” (page 127). • You can specify options for recovery in the event that the delta resync operation fails. See the Delta resync Failure step in “Changing options used by mirrors ” (page 77). This also provides important information if you share the delta resync S-VOL with Business Copy, Fast Snap, or a THP V-VOL.
Current status Corrective action 3. Make sure that all the pairs belonging to the journal in the local site are released. 4. Create a Cnt Ac-J delta resync pair that extends from the local site to the Cnt Ac-J remote site. Local site: PSUE or PSUS Cnt Ac-J remote site: HOLD Local site: HLDE 1. Release the Cnt Ac-J pair from the local site. 2. Make sure that all the pairs belonging to the journal in the local site are released. 3.
10. On the local site, create a Cnt Ac-S pair between the local site data volume and the intermediate site Cnt Ac-J P-VOL, with no data copying. When this is done, since host operations have not resumed, all three sites have the same data in their respective volumes. 11. Resume host operations at the local site. Synchronous copying will resume between the local site Cnt Ac-S P-VOL and the intermediate site S-VOL. Cnt Ac-J copying will resume from intermediate site to remote site.
10 Cnt Ac-J troubleshooting This chapter provides Continuous Access Journal troubleshooting information. General troubleshooting When an error occurs in a Continuous Access Journal 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 112). If necessary, call HP Technical Support, and retry Cnt Ac-J 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 None required. successfully established and can be used for Cnt Ac-J copy activities. 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 relationship ” (page 83) or “Deleting remote paths ” (page 82). To re-register, see “Configuring primary and secondary systems for Cnt Ac-J ” (page 55).
Troubleshooting hardware problems affecting pairs Hardware failures affecting Continuous Access Journal are described in the following table. Note also that, in addition to the problems described below, hardware failures that affect cache memory and shared memory can cause the pairs to be suspended. Classification Causes of suspension SIM Local or remote system hardware Hardware redundancy has been lost due DC0x to some blockade condition.
To identify the error code in the log file, open the RAID Manager log file, and find the error code. Example: 11:06:03-37897-10413- SSB = 2E31, 3703 Error codes appear on the right of the equal symbol (=). The alphanumeric characters on the left of the comma(,) indicates SSB1 (for example, 2E31), and on the right of the comma (,) indicates SSB2 (for example, 3703). The following tables describe the RAID Manager error codes for Continuous Access Journal.
Error code (SSB2) Description 3729 A request for Cnt Ac-J Paircreate was received. However, the pair could not share the volume with Continuous Access Synchronous because the Cont Access Journal 3DC & 4x4 Open MF program product was not installed in the primary system. 372B A pair cannot be created because the secondary system does not support the combination of multiple primary and secondary systems. 372C The volume is inaccessible because the P-VOL is blocked.
Error code (SSB2) Description 8C1E The pair cannot be created because of the one of following reasons: • The microcode version of the specified primary storage system does not support connection with the specified secondary storage system. • The specified primary storage system does not support connection with the specified secondary storage system 8C1F The pair cannot be created because the virtual ID is not set for the specified S-VOL.
Error code (SSB2) Description 8F46 The pair cannot be created because cache CL2 is in abnormal status. 8F47 The pair cannot be created because cache CL1 is in abnormal status. 8F4D The pair cannot be created or resynchronized due to the following contributing factors: • A journal is not registered in the secondary storage system. • A volume in the journal which is registered in the secondary storage system is blocked.
Error code (SSB2) Description B910 The settings of the journal option could not be updated. B913 The command was rejected because the system configuration does not allow these operations. B912/B9F8 The command was rejected because no journal was registered. B920 The pair cannot be created because the system identifier is not correct (left-most number in the 6-digit serial number).
Error code (SSB2) Description E889 The command was rejected because the specified journal was already used in another Cnt Ac-J's mirror ID. E890 The command was rejected because of one of following: • The specified volume is registered in another journal. • The specified volume is registered in the same mirror of the same journal • The volume specified as the S-VOL is registered in another mirror of the same journal.
Error code (SSB2) Description EA09 The command was rejected because the state of master journal was other than Initial, Active, or Stopped. EA0A The command was rejected because the state of restore journal was invalid. EA12 The command was rejected because the specified S-VOL was not in SSWS status. EA13 The command was rejected because the request was received for the S-VOL as the P-VOL. EA15 The command was rejected because the request was received for the P-VOL as the S-VOL.
Error code (SSB2) Description EAA5 The command was rejected because the desired capacity exceeded the charging capacity of the secondary system's Cnt Ac-J. Check the license capacity as well as the related program product. EAA6 The command was rejected because the desired capacity exceeded the charging capacity of the primary system's Continuous Access Synchronous. Check the license capacity as well as the related program product.
Error code (SSB2) Description EB48 A delta resync pair cannot be created due to one of the following reasons. • P-VOL of the Cnt Ac-J pair is different from P-VOL of the Continuous Access Synchronous pair. • The serial number of the primary system that is recognized by P-VOL and S-VOL is different. EB49 The command was rejected because the secondary system did not support the delta resync function. EB4C A pair cannot be created because the restore journal was not registered.
Error code (SSB2) Description EB6E The command was rejected because the Cnt Ac-J program product was not installed in the primary system. EB70 The command was rejected because the specified S-VOL is assigned to a copy pair of other program products. EB73 The command was rejected because the specified S-VOL is the system disk. EB74 The command was rejected because all mainframe connection CHAs are blockaded. EB78 The command was rejected because the specified data volume is a command device.
Error code (SSB2) Description EBAF The command was rejected because the license capacity of the Data Retention in the secondary system exceeds the setting value. Please check the license capacity setting for Data Retention in the secondary system. EBC6 The command was rejected because the specified Cnt Ac-J S-VOL was used by either Business Copy or Compatible FlashCopy. EBCA The command was rejected because the journal restore operation is in progress in the Cnt Ac-J pair through another mirror ID.
Error code (SSB2) Description F908 The pair cannot be created because of one of the following conditions regarding the specified S-VOL: • Virtual access mode is disabled for the volume registered in the mirror, but is enabled for the specified volume . • Virtual access mode is enabled for the volume registered in the mirror, but is disabled for the specified volume. • The specified volume whose virtual access mode is enabled has an incorrect virtual system serial number or virtual controller ID.
The following is provided for your information when the circumstances above are present: • When an error occurs, the status of the journal changes from normal to PJSE (suspended by error). • For an error caused by overflowing capacity, status changes to PJSF. • When one journal becomes PJSE or PJSF, all other normal journals in PJNN status also become PJSE status. • If you use RAID Manager and if a journal is in the normal status, it will be shown as PJNN.
11 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 5 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: 116 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 volumes This appendix discusses XP7 Storage software volumes that can be shared with Continuous Access Journal volumes. Note that Continuous Access Synchronous and Business Copy volumes can be used extensively with Continuous Access Journal. Information for these configurations is provided in: - “Configurations with Continuous Access Synchronous” (page 124) - “Configurations with Business Copy” (page 137). The following topics are covered in this appendix.
Table 6 Volume types that can be shared with Cnt Ac-J (continued) Volumes types and functions Used as Cnt Ac-J P-VOL? Used as Cnt Ac-J S-VOL? Used as Cnt Ac-J journal volume? P-VOL in COPY(RS-R)/COPY status No No No P-VOL that is also used as a Cnt Ac-S P-VOL or S-VOL Yes Yes No P-VOL (none of the above) Yes Yes7 No S-VOL in PSUS status Yes No No S-VOL (in a status other than PSUS) No No No P-VOL in all statuses except COPY(RS-R)/COPY Yes1 Yes2 No P-VOL in COPY(RS-R)/COPY status
Table 6 Volume types that can be shared with Cnt Ac-J (continued) Volumes types and functions Used as Cnt Ac-J P-VOL? Used as Cnt Ac-J S-VOL? Used as Cnt Ac-J journal volume? 6. The volume cannot be used as the Cnt Ac-J P-VOL if the specified journal was registered when 2DC Cascade was enabled. 7. When a THP V-VOL is used as a pair volume shared by Business Copy and Cnt Ac-J, the Cnt Ac-J create pair operation can fail.
Table 8 Whether access attribute can be changed when Cnt Ac-J P-VOL status is PAIR or COPY Change access attribute from Change access attribute to Read/Write Read Only Protect S-VOL Disable Read/Write - No No Yes Read Only Yes - Yes Yes Protect Yes Yes - Yes S-VOL Disable. Yes No No - Thin Provisioning • You can create a Continuous Access Journal pair by specifying a THP V-VOL (Thin Provisioning virtual volume).
Access Journal pairs. Volumes that are assigned to Continuous Access Journal pairs can be protected by LUN Manager. • Continuous Access Journal S-VOLs cannot be accessed by any UNIX® or PC server host except when the pair is split. Resource Partition You can specify Resource Partition volumes as Cnt Ac-J P-VOL and S-VOL as long as they belong to the same resource group. For journal volumes, use a Res Par OPEN-V virtual volume.
Figure 14 3DC multi-target configuration with FS 122 • You can create either the Cnt Ac-S pair or the local FS pair first. • The Cnt Ac-S pair must be created before the remote FS pair. • You can create either the Cnt Ac-J pair or the local FS pair first. • The Cnt Ac-J pair must be created before the remote FS pair.
Figure 15 Delta Resync configuration with FS • The Cnt Ac-S, Cnt Ac-J, and Cnt Ac-J delta resync pairs must be created before the remote FS pairs. • You can create a local FS pair before or after the delta resync pairs. External Storage You can create Cnt Ac-J pairs using External Storage-configured external volumes. For more information, see the HP XP7 External Storage for Open and Mainframe Systems User Guide.
B Configurations with Continuous Access Synchronous Continuous Access Journal and Continuous Access Synchronous can share the same data volumes. Using Continuous Access Journal and Continuous Access Synchronous can extend disaster recovery options to a third data center. This appendix provides planning and setup information for sharing Continuous Access Journal volumes with Continuous Access Synchronous. It describes four Continuous Access Journal/Continuous Access Synchronous configurations.
Data in the Cnt Ac-J S-VOL is an asynchronous copy of the Cnt Ac-S P-VOL. Depending on RPO and bandwidth, Cnt Ac-J S-VOL data can be very close to P-VOL data. As always with Cnt Ac-J, data consistency is ensured. Figure 16 3-data-center cascade configuration Failure recovery occurs as follows: • If a failure occurs at the Cnt Ac-S P-VOL, business continues because data in the Cnt Ac-J S-VOL is restored to the production system via the intermediate volume, if needed. Update sequence integrity is ensured.
• 3DC cascade is not supported for multiple primary and secondary systems. The Cnt Ac-J or Cnt Ac-S pair in this configuration would be suspended when the status became PAIR or COPY. • The response time for host I/Os will be the response time for Cnt Ac-S 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 and a Cnt Ac-S systems are used independently.
paired with the Cnt Ac-J S-VOL.See “Delta resync configuration ” (page 127) for more information. • If a failure occurs in the Cnt Ac-S system (P-VOL and S-VOL), business is resumed using the Cnt Ac-J 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 system (P-VOL and S-VOL), business is resumed using the Cnt Ac-S S-VOL.
You create the delta resync configuration by adding a second Cnt Ac-J pair to the 3DC multi-target configuration, using the Cnt Ac-S S-VOL and the Cnt Ac-J 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 delta resync pair. See “Creating the delta resync pair” (page 128). 2.
• If you create more than one delta resync pair, the delta resync P-VOLs in the same master journal must use the same mirror ID. • 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.
Figure 18 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.
When performing these functions with a remote command device, the number of registered journals and instances used by RAID Manager are subtracted from the number of mirrors that can be shared. • A maximum of 16 remote command devices can be used for the delta resync operation per DKC. Procedure 42 To assign mirror IDs to remote command devices 1. 2. 3. 4. In the Storage System tree, click Replication > Remote Replication.
8. To check newly assigned remote command devices, see the Journal Volumes window>Remote Command Device field. • If a remote command device is assigned to the mirror, the LDEV number displays. • If a remote command device is not assigned to the mirror, the field is blank. • If a remote command device cannot be assigned to the mirror, a hyphen displays. Releasing remote command device assigned to a mirror This operation is performed on the mirror. Procedure 43 To release a remote command device 1. 2.
For more information, see “Delta resync configuration ” (page 127). • Required pair and volume statuses: ◦ The Cnt Ac-S volume used as the 3DC multi-target P-VOL: PAIR ◦ The Cnt Ac-S S-VOL used as the delta resync P-VOL: SSWS. Check this status after executing the RAID Manager horctakeover command ◦ The Cnt Ac-J delta resync pair: HOLD or HOLDING. If the pair status is HLDE, change to HOLD by performing the pairresync operation.
• When the delta resync P-VOL is updated, and then the journal volume at the Cnt Ac-S remote site exceeds 70%. • 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 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.
• ◦ Cnt Ac-J master journal volume ◦ Use the journal that was registered when 2DC Cascade was set to Enable in the Edit Journal Volumes dialog box. With it you specify whether to write Cnt Ac-S P-VOL data to a shared Cnt Ac-S S-VOL/Cnt Ac-J P-VOL, or to write only to the Cnt Ac-J master journal. Enable — Data will be written only to the Cnt Ac-J master journal volume on the intermediate site for use in the 2DC configuration.
• If you release the Cnt Ac-S pair when the Cnt Ac-J P-VOL is in COPY status, the Cnt Ac-J pair becomes suspended by error. • For Cnt Ac-J, an X at the end of the device ID indicates the LDEV is a Thin Provisioning virtual volume. However, the X does not display when both of the following conditions exist: ◦ The Cnt Ac-S S-VOL is a Thin Provisioning virtual volume. ◦ The Cnt Ac-J S-VOL is not a Thin Provisioning virtual volume.
C Configurations with Business Copy Continuous Access Journal and Business Copy 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 with Continuous Access Journal. For details about Business Copy, see the HP XP7 Business Copy User Guide. Overview Continuous Access Journal’s main function is to maintain a copy of the production volume in a remote location.
Figure 20 Shared Cnt Ac-J and BC primary volume • A Cnt Ac-J secondary volume shared with the BC primary volume is illustrated below. With this configuration, multiple backup copies of the Cnt Ac-J primary volume can be made on the secondary system. CAUTION: When you share a Cnt Ac-J S-VOL with a BC P-VOL as shown in the following figure, the restore operation to the Cnt Ac-J S-VOL takes time.
Figure 22 Shared Cnt Ac-J volumes with BC primary volumes Configurations with Business Copy secondary volumes The following figure shows a BC primary volume used as the production volume. A remote Cnt Ac-J backup copy is made of the BC secondary volume. The BC pair must be in PSUS status to perform the Cnt Ac-J operation. Figure 23 Shared Cnt Ac-J P-VOL with BC secondary volume Pair status and data currency The table below shows whether the data in a shared volume is current, given the combined status.
D Cnt Ac-J GUI reference This appendix describes the Continuous Access Journal 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 70). 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.
Journal Volumes 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. CLPR Journal volume’s CLPR number.
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 Data Overflow Watch Number of seconds the system will monitor write data to the journal volume when the journal volume is full (100%). Range is 0-600 seconds. The Cnt Ac-J default is 60; the Cnt Ac-J Z default is 20. 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.
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 57), and “Adding additional journal volumes to an existing journal” (page 79). 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 152 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.
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 75). 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%).
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 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. Number of Data VOLs Number of volumes associated with the journal.
Item Description MP blade Options for selecting an MP blade, MPB0 thru MPB7. Availability depends on system configuration. Confirm window 156 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).
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. 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.
Assign Remote Command Devices wizard Use this wizard to assign remote command devices. Assign Remote Command Device window Use this window to assign mirrors to remote command devices. For full information, see the procedure in “Assigning mirrors to remote command devices ” (page 130). Item Description Journal ID Journal identifier. Mirror1 Used to assign a Mirror ID to a Remote Command Device (LDKC number, CU number, and LDEV number).
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 Local Storage System Displays the following information about pair volumes in the accessed system. • LDEV ID: LDEV identifier. • LDEV Name: LDEV name. • Pair Position: Identifies the volume as primary or secondary. • Journal ID: Journal identifier.. • Mirror ID: Pair’s mirror ID • CLPR: CLPR number • Virtual storage machine: Virtual storage machine’s model type and serial number. • Virtual LDEV ID: Volume’s virtual LDEV identifier.
For more information, see “Monitoring pair activity, status, license capacity” (page 61). 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.
Item Description Mirror ID Pair’s mirror identifier Remote Storage System box Displays the information about the the system connected to the system you accessed. • LDEV ID: LDEV identifier and name, which displays when you hover the mouse over it. • Port name/Host group ID/LUN ID: System’s port name, host group ID and LUN ID. This information is useful when specifying an LDEV ID at pair creation. It does not change, even if you change path settings.
Split Pair wizard Use this wizard to split pairs. Split Pair window Use this window to split pairs. For full information, see the procedure in “Splitting Cnt Ac-J pairs ” (page 46). 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.
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 identifier. CTG ID Pair’s consistency group identifier Settings Item Description Secondary Volume Write Whether data can be written to the S-VOL while the pair is split.
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. Secondary Volume Write Whether data can be written to the S-VOL when the pair is split. Split Mode Whether update data is written to S-VOLs in the mirror before the split operation. A hyphen displays if performing the split operation from the secondary system, regardless of the option selected.
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.
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 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.
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.
Item Description Path Group ID Path group identifier. CTG ID Pair’s consistency group identifier 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 50). Selected Mirrors table Item Description Journal ID Journal identifier.
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. • 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 • 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. 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.
Item Description LDEV ID The Pair volume LDEV identifier LDEV Name Name of the pair volume LDEV. Emulation Type The volume’s emulation type. Capacity The volume’s Capacity. CLPR The volume’s CLPR 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 52).
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. • Master displays when the P-VOL is paired (initial copy performed).
Item Description 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. • Multi: The consistency group consists of multiple storage systems. Delete Mode Options for deleting pairs • Normal: Delete pairs only when the primary system can change both the P-VOL and S-VOL to unpaired volumes.
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. • 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 Error Level The pairs that are split if an error occurs. • Mirror: All pairs in the mirror are split. • LU (Cnt Ac-J) or Volume (Cnt Ac-J Z): Only the failed pair is split. CFW Cnt Ac-J Z only. 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.
Item Description • Pair Position: Whether the volume is a primary or secondary volume • 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 Error Level The pairs that are split if an error occurs: • Mirror: All pairs in the mirror are split.
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 2 data center configuration, 134 3 data center configurations, 124 A Auto LUN, 123 Auto LUN V2 volumes, 118 B Business Copy volumes, 117, 137 business requirements, assessing, 19 C cables and switches, 40 Cache and Nonvolatile Storage (NVS), 17 cache changes and pair status, 65 Cache Residency, 119 Cache Residency Manager volumes, 117 cache-fast-write, options for, 73 calculating bandwidth, 34 cascade configuration with Cnt Ac-S, 124 Cnt Ac-J set up, 55 Cnt Ac-S removing pair relationship,
J journal copy, 9 journal obtain, 9 journal restore, 9 journal status definitions, 71 journal volumes adding to a journal, 79 deleting from a journal, 80 description, 11 planning considerations, 23 sizing, 21 journals and system option 707, 135 assigning MP blade to, 60 changing options, 75 creating, 57 deleting, 81 description, 11 maintenance, 75 monitoring, 70 planning, 22 specifications, 17 L latency, 38 license capacity exceeded, 16 license capacity, displaying, 62 license expired, 16 local vs remote s
a pair, 48 reverse copy direction to primary site, 88 RIO MIH, 56 role required for operations, 54 rolling averages and cycle time, 37 RPO, 20 S S-VOL, taking over host operations, 88 saving pair information, 70 Service Information Messages, 112 shared memory changes, and pair status, 17, 65 sharing secondary volumes, 139 sharing volumes, 137 SIMs, 112 sizing bandwidth, 33 Smart Tiers volume, 117 splitting a pair, 46 storage capacity values conventions, 115 storage systems using an earlier model, 29 strate
