HP StorageWorks Continuous Access XP Journal user guide Part number: T1723-96002 Second edition: December 2005
Legal and notice information © Copyright 2005 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 About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firmware versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . .
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One-to-one volume copy operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical unit (LU) types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum number of pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Associating primary and remote disk arrays and configuring logical paths (Add DKC) . . . . . . . . . . . . . 80 Changing options for logical paths and disk arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Adding logical paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Deleting logical paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resuming normal operations at the primary site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Command View XP or XP Remote Web Console operations. . . . . . . . . . . . . . . . . . . Continuous Access XP Journal error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 multi-target configurations) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Recovering from primary site and Continuous Access XP (synchronous) secondary site failures . . . . . . 70 Transferring business tasks from Continuous Access XP Journal secondary sites to primary sites . . . .
25 26 27 28 29 30 31 32 8 or COPY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Logical path status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 SVP modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Remote copy I/O statistics . . . . . . . . . . . . . .
About this guide This guide provides information about: • Understanding copy solutions • Understanding Continuous Access XP Journal • Understanding operation requirements and restrictions • Installing hardware • Enabling Continuous Access XP Journal options • Planning journal volumes • Configuring primary and secondary disk arrays • Combining Continuous Access XP Journal with other data management functions • Configuring disk arrays and logical paths • Using journal groups • Performing Continuous Access XP
Firmware versions The recommended firmware versions shown in Table 1 provide the optimal level of support for the features provided with this product. Older firmware versions can be used; however, product features enabled with newer firmware will not appear.
IMPORTANT: NOTE: TIP: Provides clarifying information or specific instructions. Provides additional information. Provides helpful hints and shortcuts. HP technical support Telephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support/.
1 Continuous Access XP Journal This guide covers the following topics: • ”Overview of copy solutions” on page 13 • ”Overview of Continuous Access XP Journal” on page 14 • ”Continuous Access XP Journal operations requirements and restrictions” on page 35 • ”Configuring disk arrays and logical paths” on page 75 • ”Using journal groups” on page 88 • ”Performing Continuous Access XP Journal pair operations” on page 105 • ”Monitoring remote copy operations” on page 124 • ”Viewing history of data volume pair ope
This chapter describes and provides instructions for using the licensed Command View XP or XP Remote Web Console to perform Continuous Access XP Journal operations. You can also use RAID Manager to perform Continuous Access XP Journal operations from the UNIX or PC server host. Business Copy XP and ShadowImage for z/OS You can use Business Copy XP and ShadowImage for z/OS data duplication features to set up and maintain multiple copies of logical volumes within the same local disk array.
reliable data replication systems using journal volumes to reduce the chances of copy operation suspensions. Copy operations can be suspended due to restrictions on data transfers from the primary site to the secondary site. Functionality You can use Continuous Access XP Journal to create duplicate volumes by copying data from primary data volumes in the primary disk array to secondary data volumes in the secondary disk array at the remote location.
command is issued on the primary site. The primary disk array transfers data in the journal volume to the secondary site according to the read journal command if it has journal data that should be sent. If the primary disk array does not have journal data, the information is sent. The secondary disk array stores the journal volume data sent from the primary site in the restore journal volume at the secondary site.
Figure 3 shows Continuous Access XP Journal’s connection configuration for multiple secondary disk arrays. By connecting one primary disk array with more than one secondary disk arrays, you can create a volume pair that has a one-to-one relationship for each journal group. Figure 3 Connection configuration for multiple secondary disk arrays Local disk arrays Continuous Access XP Journal operations involve local disk arrays at the primary and secondary sites.
disk array issues the read journal command to the primary disk array and copies journals. For Command View XP, the secondary management station should be connected to the secondary disk arrays at the secondary site on a separate LAN. The secondary disk arrays should also be attached to a host system to report sense information if a problem with a secondary data volume or secondary disk array occurs and provide disaster recovery capabilities.
communications path between the primary disk array and secondary disk array fails temporarily, remote copy operations continue after the communications path is recovered. If data transfer from hosts to the primary disk array is temporarily faster than data transfer between the primary disk array and secondary disk array, remote copy operations between the primary disk array and secondary disk array continue.
If you add a journal volume when a remote copy operation is in progress (that is, when at least one data volume pair exists for data copying), the journal volume’s metadata area (see ”Journal volume areas” on page 20) is unused, and only the journal data area is used. To make the metadata area usable, split (suspend) all data volume pairs in the journal group, and restore (resynchronize) the pairs.
Figure 4 shows the corresponding numbers of a consistency group and journal group. Figure 4 Corresponding consistency group and journal group numbers Remote copy connections Remote copy connections are the physical paths that primary disk arrays use to communicate with secondary disk arrays. Remote copy connections enable communications between primary and secondary disk arrays. Primary and secondary disk arrays are connected through fibre-channel interface cables.
Initiator ports and RCU target ports Initiator and RCU target ports are required at the primary and secondary disk arrays. The initiator port at the primary disk array is connected to the RCU target port at the secondary disk array through the fibre channel interface. The initiator port at the secondary disk array is connected to the RCU target port at the primary disk array. The initiator port at the secondary disk array issues a read journal command to the primary disk array.
Remote copy operations Figure 5 illustrates the types of Continuous Access XP Journal remote copy operations: initial copy and update copy. Figure 5 Remote copy operations Initial copy operations Initial copy operations synchronize data in the primary data volume and data in the secondary data volume. Initial copy operations are performed independently from host I/Os when you create a data volume pair or resynchronize a suspended pair.
NOTE: If you manipulate volumes (not journal groups) to create or resynchronize two or more data volume pairs within the same journal group, the base journal of one pair is stored in the restore journal volume, and then the base journal of another pair is stored in the restore journal volume. Therefore, the operation for restoring the latter base journal is delayed. NOTE: You can specify None as the copy mode for initial copy operations.
NOTE: To reduce the overhead associated with remote copy activities and maximize data transfer, the local disk array uses a special write command that is allowed only for Continuous Access XP Journal initial and update copy operations. This command transfers control parameters and FBA-format data for consecutive updated records in a track using a single write operation.
Table 3 Metadata information (continued) Type Description Journal sequence number Sequence number assigned when the journal is obtained Timestamp Time when journal data is obtained The journal sequence number indicates the primary data volume write sequence that the primary disk array created for each journal group. Journal data is transferred to the secondary disk array asynchronously with the host I/O.
not arrived yet. The management information of journal data S2 is 0. The secondary disk array waits for journal data S2. When journal data S2 arrives, the secondary disk array selects S2 as the next journal data to be settled. The journal data the secondary disk array selects is marked as “host-dirty” and treated as formal data.
• Cache overflow watch: If journal cache remains full for the time period specified by the cache overflow watch parameter, the journal group is suspended due to a failure. This parameter can be 0 to 90 seconds. If the amount of data in journal cache in the primary disk array reaches the specified journal cache capacity, disk array I/Os are delayed.
primary disk array or secondary disk array changes the status of the primary and secondary data volumes to PSUS (if the path status is normal). When a pair is split from the secondary disk array, the secondary disk array changes the secondary data volume’s status to PSUS, and the primary disk array detects the pair deletion (if path status is normal) and changes the primary data volume’s status to PSUS.
Table 4 Continuous Access XP Journal data volume pair status (continued) Pair status Description Primary data volume access Secondary data volume access PSUS (pair suspended-split) Data volume pair is not synchronized because you split this pair (pairsplit-r) or deleted this pair from the secondary disk array (pairsplit-S). For Continuous Access XP Journal pairs, the primary and secondary disk arrays keep track of any journal data discarded during the pairsplit-r operation.
Table 4 Continuous Access XP Journal data volume pair status (continued) Pair status Description Primary data volume access Secondary data volume access PFUL Continuous Access XP Journal monitors the total amount of data in the journal volume. If the amount of data exceeds the threshold (80%), the pair status changes from COPY or PAIR to PFUL. The write data that inflows is monitored during the specified time (Data Overflow Watch).
When you split a Continuous Access XP Journal pair, the primary and secondary disk arrays ensure synchronization by completing or discarding pending update copy operations according to the user-specified pending update option (purge/flush). The primary and secondary disk arrays keep track of journal data discarded during the pairsplit operation.
Table 6 Consistency status for split/suspended Continuous Access XP Journal secondary data volumes Consistency status (displayed at secondary disk array) Description Volume The Continuous Access XP Journal data volume pair was split or suspended alone. Update sequence consistency between the secondary data volume and other secondary data volume in this journal group is not ensured. You cannot use the secondary data volume for disaster recovery at the secondary site.
Continuous Access XP Journal secondary data volumes (the consistency status is displayed only at the secondary disk array). Table 7 Suspend types (PSUE) Type Applies to Description PSUE, S-VOL Failure Primary data volume, Secondary data volume The primary disk array detected an error during secondary disk array communications or during update copy. In this case, the secondary data volume suspend type is usually PSUE-S-VOL Failure.
Table 8 describes Continuous Access XP Journal suspension conditions and indicates which CU detects the condition and which pairs are suspended. See ”Displaying the History Operation pane” on page 128 for troubleshooting information for Continuous Access XP Journal suspension conditions.
Command View XP or XP Remote Web Console is required for the Continuous Access XP Journal graphical user interface. Continuous Access XP Journal is a component of Command View XP or XP Remote Web Console. The Continuous Access XP Journal license key codes are required to enable Continuous Access XP Journal’s options on the local disk array (see ”Enabling Continuous Access XP Journal options” on page 48). Separate license codes are required for each local disk array.
Table 10 Supported data volumes and journal volumes (continued) Type Support specifications Data volume Journal volume Maximum volume capacity Maximum capacity of volume for each emulation type Minimum volume capacity Minimum capacity of a custom volume. Minimum capacity of a custom volume. NOTE: A journal groups consists of areas containing journal data and an area containing metadata for remote copy. NOTE: • Specify a port in SLPR 0 when you use LUN Manager to define an LU path to a data volume.
RAID5 and RAID1 can coexist in the same journal group. Maximum number of pairs NOTE: The number of pairs that can be created in a disk array is limited. Use the number of cylinders and bitmap areas to calculate the maximum number of pairs that can be created in a disk array. • Number of cylinders The number of pairs of a primary and a secondary data volume is limited. The number of pairs depends on the volume capacity (that is, the number of cylinders in the volumes that form pairs).
Journal groups Continuous Access XP Journal journal groups have the following requirements: • Each Continuous Access XP Journal pair must be assigned to one and only one journal group. • Table 14 lists journal group specifications. Table 14 Journal group specifications Item Support specifications Number of journal groups Up to 256 journal groups (No. 0 - 255) per disk array if all the following conditions are satisfied: • • • • Disk array is an XP12000 (not an XP10000).
CAUTION: When a pair is created, the disk array stores information about the remote disk array and connection paths for the journal group. This information remains stored even after the pair is deleted. Therefore, to delete a pair and then use the journal group to create a new pair with another remote disk array, you must first delete the journal group and then create the same journal group again.
primary site. Also, if you configure a system in a three-data-center (3DC) cascading configuration (see ”Combining Continuous Access XP Journal with Continuous Access XP (3DC cascading configuration)” on page 60) and you use the CL1-A port as an RCU target port in the Continuous Access XP Journal primary site, you must not use the CL1-A or CL5-A port as an RCU target port in the Continuous Access XP secondary site.
Table 16 Illegal port combinations (for FRONT CL1) (continued) Location Illegal port combinations (channel adapter RCU target port number) in Continuous Access XP Journal primary site 1F (Add.
Table 16 Location Illegal port combinations (for FRONT CL1) (continued) Illegal port combinations (channel adapter RCU target port number) in Continuous Access XP Journal primary site 1L (Add.
Table 17 Illegal port combinations (for REAR CL2) Location Illegal port combinations Location Illegal port combinations (channel adapter RCU target port number) in Continuous Access XP Journal primary site Target port in Continuous Access XP Journal primary site, or RCU target port in Continuous Access XP secondary site (channel adapter number) RCU Target port in Continuous Access XP Journal primary site Target port in Continuous Access XP Journal primary site, or RCU target port in Continuous Acc
Table 17 Illegal port combinations (for REAR CL2) (continued) Location Illegal port combinations (channel adapter RCU target port number) in Continuous Access XP Journal primary site 2W (Add.4) 2X (Add.
Table 17 Location Illegal port combinations (for REAR CL2) (continued) Illegal port combinations (channel adapter RCU target port number) in Continuous Access XP Journal primary site Target port in Continuous Access XP Journal primary site, or RCU target port in Continuous Access XP secondary site Location Illegal port combinations (channel adapter number) RCU Target port in Continuous Access XP Journal primary site Target port in Continuous Access XP Journal primary site, or RCU target port in Cont
6. HP Representative: Install Continuous Access XP Journal remote copy connections between the primary and secondary disk arrays. The user supplies this hardware (optical fibre cables, switches, and so on). See ”Remote copy connections” on page 47 for remote copy configurations. Distribute the paths between different storage clusters and switches to provide maximum flexibility and availability.
• Direct connections Figure 8 Direct remote copy connections • Switch connections Figure 9 Switch remote copy connections • Extender connections Figure 10 Extender remote copy connections Enabling Continuous Access XP Journal options To operate Continuous Access XP Journal, a management station is required for Command View XP.
Considerations The following factors affect the speed of writing to and reading from journal volumes, particularly when a temporary communications path failure occurs between the primary and the secondary disk arrays or when the amount of data transferred from hosts to the primary disk array increases: • RAID configuration of the RAID groups that will contain journal volumes • Types of physical volumes in the RAID groups that will contain journal volumes • Frequency of access to non-journal volumes in the R
relatively fewer accesses can be made to journal volumes in the same RAID group, which can cause a drop in the data transfer speed of the journal volumes. To avoid this drop, you should consider, for example, relocating the journal volumes and the frequently accessed non-journal volumes (that is, placing the journal groups in one RAID group and placing the frequently accessed non-journal volumes in another RAID group).
The total capacity of the journal volumes in each journal group must exceed the value illustrated above. Journal volumes in restore journal groups When a failure occurs at a host, one failure recovery measure is to reverse the primary and secondary data volumes (that is, change the copy direction). To reverse the primary and secondary data volumes, you must usually ensure that the data transfer speed is the same before and after you reverse the data volumes.
NOTE: If the journal transfer speed falls short of the desired speed, check the usage rate of channel processors. If the usage rate of some channel processors is high, the journal transfer speed may be increased if you add channel processors. Configuring primary and secondary disk arrays for Continuous Access XP Journal operations After you install the Continuous Access XP Journal hardware and software, you can configure the primary and secondary disk arrays for Continuous Access XP Journal operations. 1.
Combining Continuous Access XP Journal with other data management functions Some types of volumes used by non-Continuous Access XP Journal functions can also be used as Continuous Access XP Journal data volumes and/or journal volumes. Table 18 explains whether non-Continuous Access XP Journal volumes can also be used as Continuous Access XP Journal volumes.
Table 18 Whether non-Continuous Access XP Journal volumes can be used as Continuous Access XP Journal volumes (continued) Functions and volumes Can volumes be used as primary data volumes? Can volumes be used as secondary data volumes? Can volumes be used as journal volumes? P-VOL in COPY status No. No. No. P-VOL in PAIR status Yes. No. No. P-VOL in PSUS status Yes. No. No.
Table 18 Whether non-Continuous Access XP Journal volumes can be used as Continuous Access XP Journal volumes (continued) Functions and volumes Can volumes be used as primary data volumes? Can volumes be used as secondary data volumes? Can volumes be used as journal volumes? Volume with Read Only attribute Yes. Yes. No. Volume that is disabled for use as an S-VOL Yes. No. No. Volume including VMA Yes. Yes. No. No. No. No. No. No. No. Yes. Yes. Yes. Yes. Yes. No. Yes. Yes. No.
Combining Continuous Access XP Journal with LUN Manager LUN Manager operations do not affect Continuous Access XP Journal operations. Volumes under secure ports and/or assigned to host groups can also be assigned to Continuous Access XP Journal pairs. Volumes assigned to Continuous Access XP Journal pairs can also be assigned to secure ports and/or host groups. NOTE: A UNIX or PC server cannot access Continuous Access XP Journal secondary data volumes unless the pair is split.
Table 20 Data currency of a shared Continuous Access XP Journal/Business Copy XP volume (continued) PAIR Not current Not current Not current CURRENT Not current Not current PSUS/PSUE Not current CURRENT CURRENT CURRENT CURRENT Not current Figure 14 through Figure 17 show various Continuous Access XP Journal/Business Copy XP configurations that share volumes.
Figure 16 combines the configurations shown in Table 14 and Table 15. Within a single Continuous Access XP Journal pair, the primary and secondary data volumes function as Business Copy XP P-VOLs, providing multiple copies at the primary and remote sites.
2. Execute the RAID Manager horctakeover command on the Continuous Access XP Journal pair to reverse the copy direction and re-establish the pair (Figure 19). Figure 19 Restoring Business Copy XP P-VOLs, step 2 3. Execute the RAID Manager horctakeover command on the Continuous Access XP Journal pair to change the copy direction to the original direction and re-establish the pair (Figure 20). Figure 20 Restoring Business Copy XP P-VOLs, step 3 4.
6. Execute the RAID Manager pairsplit -S command on the Business Copy XP pair to release the pair (Figure 23). Figure 23 Restoring Business Copy XP P-VOLs, step 6 7. Execute the RAID Manager paircreate command on the Business Copy XP pair to copy in the original direction (see Figure 24). Figure 24 Restoring Business Copy XP P-VOLs, step 7 8. Execute the RAID Manager pairsplit -r command on the Business Copy XP pair to put the pair in PSUS status (see Figure 25).
operations are performed using cascading connections and a three data center (3DC) configuration. In a 3DC configuration, an intermediate site is located between the primary and secondary sites. Figure 27 shows an example of a 3DC cascading configuration in which Continuous Access XP Journal and Continuous Access XP (synchronous) are combined. In this configuration, the volume in the primary site is a Continuous Access XP (synchronous) primary volume (P-VOL).
As explained previously, when the host in the primary site issues an I/O request to the Continuous Access XP (synchronous) P-VOL, data is restored asynchronously to the Continuous Access XP Journal secondary data volume in the secondary site in a remote location. Figure 28 Basic behavior in 3DC cascading configuration If a Continuous Access XP (synchronous) pair is suspended in a 3DC cascading configuration, you can resynchronize the pair using a differential copy.
4. Issue a request for creating a Continuous Access XP Journal pair to the Continuous Access XP Journal primary disk array. When creating a Continuous Access XP Journal pair, ensure that you select a value from 1 to 3 as the mirror ID. 5. Wait until the status of the Continuous Access XP Journal pair becomes PAIR. NOTE: Ensure that the Continuous Access XP (synchronous) pair status changes to PAIR before the Continuous Access XP Journal pair status changes to PAIR.
• Primary site for Continuous Access XP Synchronous and Continuous Access XP Journal • Secondary site for Continuous Access XP Synchronous • Secondary site for Continuous Access XP Journal Figure 29 3DC multi-target configuration (combining Continuous Access XP Journal with Continuous Access XP Synchronous) In this configuration, the primary volume at the primary site is paired with the secondary volume for Continuous Access XP Synchronous.
Hardware configurations A 3DC multi-target configuration requires the following sites: • Primary site for Continuous Access XP Synchronous and Continuous Access XP Journal • Secondary site for Continuous Access XP Synchronous • Secondary site for Continuous Access XP Journal Each site requires one XP10000/XP12000. For Command View XP, a management station is also required. HP recommends that you install RAID Manager in the host computers at each site.
For more information about configuring Continuous Access XP Journal journal groups, see ”Journal group operations” on page 28. For more information about configuring ports, see ”Configuring port attributes” on page 79. Recovering from primary site failures If a disaster or failure occurs only at the primary site in a 3DC multi-target system, use the secondary volume at the Continuous Access XP Synchronous secondary site to enable the secondary site to take over the business tasks.
Continuous Access XP secondary sites to primary sites (in 3DC cascading configurations)” on page 68.
2. If pair resynchronization has not been performed to reverse the Continuous Access XP Synchronous pair’s primary/secondary relationship (that is, if the pair is suspended), use RAID Manager to resynchronize the pair, so the primary/secondary relationship is reversed.
3. Use the primary volume at the primary site to resume the business tasks.
secondary data volume is a volume at the Continuous Access XP Journal secondary site. The system configuration returns to the original 3DC multi-target configuration.
Transferring business tasks from Continuous Access XP Journal secondary sites to primary sites If you follow the instructions in ”Recovering from primary site and Continuous Access XP Synchronous secondary site failures” on page 70 and remove failures from the primary site and Continuous Access XP Synchronous secondary site, you can transfer the business tasks back to the primary site. To transfer the business tasks back to the primary site: 1.
Combining Continuous Access XP Journal and LUN Security XP Extension You can create a Continuous Access XP Journal pair using volumes to which LUN Security XP Extension has assigned an access attribute. However, you cannot specify a volume with the S-VOL Disable attribute as the secondary data volume of the pair. Table 21 shows whether you can specify a volume with an access attribute as a Continuous Access XP Journal pair P-VOL or S-VOL.
Figure 36 shows the process of copying access attributes when you create a pair using volumes with VMA. Figure 36 Copying access attributes In Figure 36, if both primary and secondary data volumes have VMA, the primary data volume’s VMA is copied to the secondary data volume. In Figure 36, the secondary data volume’s access attribute is Read/Write when the pair status is SMPL.
NOTE: If the pair is suspended or deleted during COPY status, the primary data volume’s access attribute is not copied to the secondary data volume. To copy the primary data volume’s access attribute to the secondary data volume, ensure that the pair status is PAIR, and then suspend or delete the pair. NOTE: When the primary data volume is in COPY or PAIR status, two access attributes can be changed and cannot be changed according to the existing access attribute.
Configuring disk arrays and logical paths To introduce Continuous Access XP Journal into your system and configure your system for remote copy operations, consider what data should be copied from which disk array to which disk array. The disk array containing data to be copied to another disk array is referred to as the primary disk array. The disk array to which data is copied from another disk array is referred to as the secondary disk array.
Continuous Access XP Journal has already been started 1. Select the DKC Operation tab. The DKC Operation pane appears. NOTE: DKC is an acronym for disk controller, which controls an entire disk array. Continuous Access XP Journal panes use the word DKC to indicate a disk array. DKC Operation pane components Figure 37 DKC Operation pane, DKC option The DKC Operation pane displays the following: • Switch Display: Changes information in the DKC Operation pane.
NOTE: Information on the DKC Operation pane is updated when you do one of the following: • Select another tab, and reselect the DKC Operation tab. • Click Refresh (top right of Command View XP or XP Remote Web Console pane). • Click Apply. • Select Modify mode when you are in View mode. • Open or close the DKC Status pane. • Click Refresh on the DKC Status pane. Displaying information about remote disk arrays 1. Display the DKC Operation pane. 2. In the Switch Display box, select DKC.
2. Select a remote disk array from below Subsystem in the tree. The list displays logical paths. Each row in the list indicates one logical path. The list displays the following: • Path Gr. ID: Path group ID. The icon indicates the status of the path: The logical path is in a normal status A failure occurred at the logical path • M-R Path: Channel type of the logical paths between the local and remote disk arrays. This column always displays Fibre.
• List: Displays ports on the local disk array. • Port: Port number. • Attribute: Port attribute (initiator, target, RCU target, or external). • PCB Mode: Port mode. The mode is either Standard or High. • CU#: Currently, displays nothing. • Error Code: Error code.
1. Ensure that the Command View XP or XP Remote Web Console main pane is in Modify mode. For more information, see the HP StorageWorks Command View XP User Guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console User Guide for XP12000/XP10000. 2. Ensure that the DKC Operation pane is displayed (see ”Displaying the DKC Operation pane” on page 75). 3. In the Switch Display box, select Port. The tree displays channel adapters in the local disk array and port attributes. 4.
• Remote disk array’s serial number. • Remote disk array’s controller ID. NOTE: The controller ID for an XP10000/XP12000 disk array is 4. • Path group ID. The path group ID is within the range of 1-FF (hexadecimal). Up to 64 path group IDs can be registered per disk array. NOTE: In the current version, the path group IDs always take the default values and cannot be changed. 8. In the Add DKC pane, select a primary and remote disk array port to configure a logical path. 9. Click Option. 10.
NOTE: The controller ID for an XP10000/XP12000 disk array is 4. • Path Gr. ID: Enter the path group ID. Path group IDs are used for identifying groups of logical paths. One path group can contain up to eight logical paths. Path group IDs are within the range of 0-FF (hexadecimal). If you select the Default check box, the default path group IDs is set. NOTE: In the current version, you cannot enter path group IDs. Also, you cannot clear the Default check box.
NOTE: If an error occurs, the right-most column of the Preset list displays the error code. To view detailed information about the error, right-click the error code, and select Error Detail. An error message appears providing detailed information about the error. Figure 40 DKC Option pane The DKC Option pane displays the following: • Minimum Paths: Specify the minimum number of paths required for each remote disk array connected to the local disk array (default = 1).
• In the list, select and right-click a remote disk array, and select Edit Path(s). The list displays information about logical paths. 6. Right-click the list, and select Add Path. The Add Path pane appears. 7. Use the Add Path pane to configure up to eight new logical paths. 8. Click Set to close the Add Path pane. 9. In the Preset list, check the settings you made. • To modify a setting, select and right-click the setting from the Preset list, and select Modify.
Deleting logical paths Before deleting logical paths, ensure that the remaining number of logical paths will be greater than the minimum number of paths setting (see ”Changing options for logical paths and disk arrays” on page 82). The delete path operation fails if the number of remaining paths is equal to or less than the minimum number of paths. The primary and secondary disk array administrators can perform the following procedure: 1.
The primary and secondary disk array administrators can perform the following procedure: 1. Ensure that the DKC Operation pane is displayed. 2. In the Switch Display box, select DKC. 3. In the upper-right list, select and right-click a remote disk array or logical path. • To display remote disk arrays in the list, select Subsystem from the tree. • To display logical paths between the local and remote disk arrays, select the remote disk array from the tree. 4. Select DKC Status. The DKC Status pane appears.
• Last Updated: Date and time when the last operation on a logical path to the remote disk array was performed. • Refresh the DKC Operations tab after this panel is closed: If selected, information in the DKC Operation pane is refreshed after you close the DKC Status pane. • Refresh: Refreshes the information in the DKC Status pane. • Close: Closes the DKC Status pane.
8. Click OK to close the message. 9. In the Preset list, check the settings you made. • The Preset list displays the specified remote disk arrays. One row indicates one remote disk array. • To cancel removal of the relationship, select and right-click the remote disk array in the Preset list, and select Cancel. 10.Click Apply to remove the relationship.
Journal Operation pane components Figure 44 Journal Operation pane The Journal Operation pane displays the following: • Tree: Lists journal groups in the local disk array you are logged into. NOTE: The tree displays journal groups used with Continuous Access XP Journal, and does not display journal groups used with UR390 (Universal Replicator for z/OS). • Journal Groups: Located at the top of the tree. When selected, the upper-right list displays journal groups in the local disk array.
• Display all JNL groups: NOTE: This check box appears only if you are logged onto an XP10000. If this check box is cleared, the list below the check box only displays journal groups numbered 00 to 0F. If this check box is selected, the list below the check box displays journal groups numbered 00 to FF.
HaltAccept An operation for splitting the mirror has been started. The status of the journal group immediately changes to Halting. NOTE: HaltAccept can indicate the status of restore journal groups, but cannot indicate the status of master journal groups. Halting An operation for splitting or deleting the mirror is in progress. The primary and secondary volumes are not synchronized. When you split a mirror, the status changes in the following order: Halting, Halt, Stopping, and finally Stop.
• Operation: Indicates the operation that will occur when you click Apply. • Edit JNL Volumes: Register or delete journal volumes • Change JNL Option: Change journal group options • Delete JNL Groups: Delete journal group • Pairsplit -r: Split a mirror • Pairresync: Restore a mirror • Pairsplit -S: Delete a mirror • Blank: Nothing occurs when you click Apply • Preset: The number to the left of the slash (/) is the number of items displayed in the Preset list.
5. In the Free Volumes list of the Edit JNL Volumes pane, select the volumes you want to register. In the Free Volumes list, one row represents one volume. If you cannot find the volumes you want to register, do one of the following: • Select Parity Group, enter a parity group number in the text boxes to the right, and click Show. The list displays volumes in the specified parity group. Select the volumes you want to register. • Select CU, and select a CU number from the drop-down list to the right.
• JNL Volumes: Information about journal volumes. • Parity Group: Parity group or external volume group where a journal volume belongs. NOTE: If E is displayed at the beginning of a group, the group is an external volume group. Currently, however, the pane does not display external volumes. • CU:LDEV: Journal volume’s CU and LDEV numbers. The CU number is displayed to the left of the colon (:). The LDEV number is displayed to the right of the colon.
• CU: Displays volumes belonging to a CU. If selected, select a CU from the drop-down list to the right. • JNL Group: Journal group’s number. • Current: Number and capacity of journal volumes that currently exist in the journal group. • Total: Estimates the number and capacity of journal volumes after addition or deletion, and displays the estimated number and capacity. • Set: Applies settings in the pane to the Journal Operation pane. • Cancel: Cancels settings.
Displaying detailed information about journal groups To display detailed information about journal groups in the primary disk array, log into the primary disk array. To display detailed information about journal groups in the secondary disk array, log into the secondary disk array. 1. Ensure that the Journal Operation pane is displayed (see ”Displaying the Journal Operation pane” on page 88). 2. Select a journal group in the tree. NOTE: You cannot select more than one journal group. 3.
• Blank: Journal volumes and data volumes are not registered in this journal group. • JNL Volumes: Number of journal volumes registered in the journal group. • JNL Capacity: Total capacity of all registered journal volumes. • Data Volumes: Number of data volumes associated with the journal group. • Data Capacity: Total capacity of all data volumes. • Meta/Data Ratio: Ratio of metadata area to journal data area. For example, if 16 is displayed, the ratio of metadata area to journal data area is 1:16.
• Capacity (GB): Journal volume’s capacity in gigabytes. • Emulation: Journal volume’s emulation type. • CLPR: Number and name of the CLPR where the journal volume belongs. • Mirrors: List of mirrors. • Mirror ID: Mirror ID. This column is blank if the journal group’s attribute is neither Master nor Restore. • Status: Status of a journal group (or a mirror) in the local disk array. A journal group in initial status.
This column is blank if the journal group’s attribute is not Master or Restore. NOTE: The controller ID for an XP10000/XP12000 disk array is 4. • Path Watch Time (min): Time for monitoring blockade of paths to the remote disk array. • Previous: Displays detailed information about the previous journal group. • Next: Displays detailed information about the next journal group. • Close: Closes the JNL Group Detail pane.
NOTE: If an error occurs, the right-most column of the Preset list displays the error code. To view detailed information about the error, right-click the error code, and select Error Detail. An error message appears providing detailed information about the error. Figure 47 Change JNL Option pane The Change JNL Option pane displays the following: • Meta/Data Ratio: Specify the ratio of metadata area to journal data area. For example, if you select 16, the ratio of metadata area to journal data area is 1:16.
• Medium: Speed of initial copy activity is faster than Low and slower than High. To specify Medium, ensure that the amount of update I/Os (that is, write requests from hosts to primary data volumes) is 10 MB/s or less per parity group. If it exceeds 10 MB/s, data volume pairs might become split (suspended). • High: Speed of initial copy activity is faster than Low and Medium. To specify High, ensure that update I/Os (that is, write requests from hosts to primary data volumes) do not occur.
• Forward Path Watch Time: Specifies if the master journal group’s Path Watch Time value is forwarded to the restore journal group. If the Path Watch Time value is forwarded from the master journal group to the restore journal group, the two journal groups have the same Path Watch Time value. • Yes: Path Watch Time value is forwarded to the restore journal group. • No: Path Watch Time value is not forwarded to the restore journal group. No is the default.
• To cancel deleting a journal group, select and right-click the journal group, and select Cancel. • If necessary, repeat step 3 through step 5 to specify other journal groups. 6. Click Apply. NOTE: If an error occurs, the right-most column of the Preset list displays the error code. To view detailed information about the error, right-click the error code, and select Error Detail. An error message appears providing detailed information about the error.
• S-VOL Write: Specify whether hosts can issue read I/O and write I/O to the secondary volume after the mirror is split. • Enable: Hosts can issue read I/O and write I/O to the secondary volume after you split the mirror. • Disable: Hosts cannot issue read I/O and write I/O to the secondary volume after you split the mirror. This is the default. This parameter takes effect only when the selected volume is a master journal group. • Range: Split range. This is always set to Group and cannot be changed.
NOTE: The Range column indicates the unit used for restoring the mirror, and always displays Group. The Base Start column indicates whether copying of base-journal starts after you restore the mirror, and always displays Yes. Deleting data volumes from mirrors (Pairsplit-S: ending copy operations) A mirror is a combination of a master journal group and a restore journal group.
To display the Pair Operation pane, do one of the following. Continuous Access XP Journal has not been started 1. Use your Web browser to display the storage device list. In the storage device list, select the disk array to log into. Enter a user name and the password, and click OK. The Command View XP or XP Remote Web Console main pane appears.
NOTE: LUN Expansion (LUSE) volumes are not displayed. By default, information in the list is arranged in order of port numbers. For volumes with more than one path, each path is displayed in a separate row. The maximum number of rows in the list is 1,024. If the number of volumes exceeds the number of rows, use the Previous and Next buttons to view information about volumes that do not appear in the list currently.
Suspending The primary and secondary volumes are not synchronized. This pair is in transition from the PAIR or COPY status to the PSUS/PSUE status. Deleting The primary and secondary volumes are not synchronized. This pair is in transition from the PAIR, COPY, or PSUS/PSUE status to the SMPL status. • JNLG-MirrorID: Journal group number and mirror ID. The number on the left of the hyphen (-) is a journal group number. The number on the right of the hyphen is a mirror ID.
• If the volume pair is split and, therefore, is in PSUS or PSUE status, this column usually displays synchronization rate (that is, concordance rate) between the secondary data volume before it was split and the secondary data volume after it was split. For example, the synchronization rate is 100 percent if the contents of the secondary data volume is the same before and after the volume pair was split.
2. In the Display Filter pane, specify information you want to display in the list. 3. Click Set to close the Display Filter pane. NOTE: • To restore the list to the default status (that is, the status before filtering), click Reset in the Display Filter pane, and click Set in the same pane. • If you change settings in the Display Filter pane, the changes remain in effect during the Continuous Access XP Journal session until you reset the settings.
NOTE: You can use the snapshot function only while the client file access is enabled. When the client file access is not enabled, the Snapshot button is not displayed on the Pair Operation pane. The following is an example of a snapshot file.
Creating a pair of data volumes (Paircreate) Using the Paircreate pane, the administrator of the primary disk array must create pairs of a primary and secondary volume. When creating a pair, the administrator can specify options for initial copy activities. Before creating one or more pairs, the administrator must make sure that: • Volumes to be used as secondary volumes are offline to all hosts. • Ports have already been configured (see ”Configuring port attributes” on page 79).
• To modify a setting, select and right-click the setting, and select Modify. • To cancel a setting, select and right-click the setting, and select Cancel. 14.Click Apply to start the pair creation and initial copy operations. NOTE: If an error occurs, the right-most column of the Preset list displays the error code. To view detailed information about the error, right-click the error code, and select Error Detail. An error message appears providing detailed information about the error. 15.
NOTE: You can select only one secondary data volume even when two or more primary data volumes are selected in the Pair Operation pane. Continuous Access XP Journal automatically specifies the other secondary data volumes. For more information, see the explanation for the Select Other S-VOL(s) option on page 114. If you selected more than one primary data volume, select the secondary data volume for the primary data volume being displayed.
NOTE: This option cannot be changed after a pair has been created. • DKC: Select the secondary disk array’s serial number and controller ID. You can also specify the path type (for example, channel type). NOTE: The secondary disk array must be the same for all pairs being created during one operation. • Initial Copy: Specify whether to start the initial copy operation after the volume pair is created. • Entire: The initial copy operation starts after the volume pair is created.
5. Click Close to close the Pairdisplay pane. Figure 54 Pairdisplay pane The Pairdisplay pane displays the following: • Status: Status of the pair. If the pair is split (or suspended), the column also displays the suspend type. If the pair is waiting for initial copy, the column also displays Queuing. • Alternative Path: Alternate path. • Prog./Sync.: If the volume in the local disk array is a primary data volume, this column displays an initial copy operation’s progress.
NOTE: The current version does not support LUSE volumes. The second line displays the device emulation type. The third line displays the volume capacity. NOTE: If a logical volume is an external volume, # appears after the LDEV number. For more information about external volumes, see the HP StorageWorks External Storage XP User Guide. • S-VOL: Secondary data volume. The first line displays the secondary volume’s port number, host group ID, and LUN.
NOTE: • The Display Filter settings (see ”Filtering information in the list in the Pair Operation pane” on page 109) can affect how Previous or Next is recognized. • The list displays a maximum of 1,024 rows at once. The Previous and Next buttons on the Pairdisplay pane can only be used for the currently displayed 1,024 rows. • Refresh: Updates the pair status information. • Close: Closes the Pairdisplay pane.
• Error Level: Range used for splitting a pair when a failure occurs. • Group: If a failure occurs with a pair, all pairs in the consistency group where the pair belongs are split. • LU: If a failure occurs with a pair, only the pair is split. When the Change Pair Option pane appears, the pane displays the current option value. • Set: Applies settings to the Preset list in the Pair Operation pane (Figure 49). • Cancel: Discards the settings.
• Enable: Hosts can write data to the secondary data volume while the pair is split. This option is available only when the selected volume is a primary data volume. • Range: Specify the split range. If you select two or more pairs in the same consistency group, the default is LU. Otherwise, the default is Group. • LU: Only the specified pairs are split.
3. If any pair was suspended due to an error condition (use the Pairdisplay pane to view the suspend type), ensure that the error condition has been removed. The primary disk array will not resume the pairs until the error condition has been removed. 4. In the tree, select Subsystem or a port. 5. In the list, select and right-click the pair you want to restore. The pair status must be PSUS or PSUE. 6. Select Pairresync. The Pairresync pane appears. 7.
NOTE: If Range is Group, you cannot change Priority. • DKC: Disk array. • Error Level: Specify the range used for splitting a pair when a failure occurs. • Group: If a failure occurs with a pair, all pairs in the consistency group where the pair belongs are split. • LU: If a failure occurs with a pair, only the pair is split. NOTE: If Range is Group, you cannot change Error Level. • Set: Applies settings to the Preset list in the Pair Operation pane. • Cancel: Discards settings.
NOTE: If a pair is deleted, the deletion might take effect on the secondary data volume later than it takes effect on the primary data volume. Therefore, an error might occur if you reference a pair’s status or manipulate a pair immediately after RAID Manager deletes the pair. If such an error occurs, check the secondary data volume’s status and retry referencing the pair status or manipulating the pair.
• Set: Applies settings in the Preset list in the Pair Operation pane. • Cancel: Discards settings. Creating a Point-in-Time copy of data volumes Use Continuous Access XP Journal to make Point-in-Time (PiT) duplicates of groups of volumes. The term Point-in-Time (PiT) refers the process of copying data immediately when you want to obtain it. Use Continuous Access XP Journal to create a PiT copy of data volumes belonging to a journal group. 1.
Continuous Access XP Journal has already been started 1. Select the Usage Monitor tab. The Usage Monitor pane appears. Figure 59 Usage Monitor pane The Usage Monitor pane displays the following: • Monitoring Switch: Select the usage monitor operation (see ”Starting and stopping usage monitoring” on page 125). • Enable: Displayed when monitoring is on • Disable: Displayed when monitoring is off. NOTE: When monitoring is stopped, the usage monitor graph is closed.
NOTE: If you set 1 minute for Gathering Interval, the sampling data is held one day. If you set 15 minutes for Gathering Interval, the sampling data is held 15 days. When Gathering Interval is changed, data obtained before the change is deleted. 4. To start monitoring, click Apply. Stopping usage monitoring 1. On the connected local disk array, select the Usage Monitor tab. 2. In the Monitoring Switch box, select Disable. 3. To stop monitoring, click Apply.
4. In the Monitor Data box, select the I/O statistics data you want to display on the graph. You must select at least one box. Table 27 describes I/O statistics data. 5. Click Set to close the Display Item pane. The Usage Operations pane now displays a graph showing the selected I/O statistics data for the selected LUs. To enlarge the displayed graph, right-click the graph, and select Large Size. To return the graph to normal size, right-click the graph, and select Normal Size.
Table 27 Remote copy I/O statistics Statistic Host I/O Initial Copy Asynchronous Copy M-JNL R-JNL Description Read Record Count Number of read I/Os per second. Read Hit Record Count Number of read hit records per second. Write Record Count Number of write I/Os per second. Write Hit Record Count Number of write hit records per second. Read Transfer Rate Amount of data read per second. The unit is kilobytes per second. Write Transfer Rate Amount of data written per second.
Continuous Access XP Journal has not been started 1. Use your Web browser to display the storage device list. In the storage device list, select the disk array to log into. Enter a user name and the password, and click OK. The Command View XP or XP Remote Web Console main pane appears. For more information, see the HP StorageWorks Command View XP User Guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console User Guide for XP12000/XP10000. 2.
NOTE: You cannot save the history file while operation history is being updated. Save operation history in a text file after operation history is updated. • List: Displays operation history for data volume pairs in the connected disk array. • Operation Date/Time: Date and time when the operation was completed. • Copy Time: Time taken for the operation. Displayed only for Paircreate Complete and Pairresync Complete operations. • JNL Group: Journal group number. • Mirror ID: Mirror ID.
• Status Change by RCU(PSUS/PSUE to SMPL, Pairsplit-S Start): Operation for deleting a pair was started at the secondary disk array. Status of data volume pair changes from PSUS or PSUE to SMPL. • Status Change by RCU(COPY to SMPL, Pairsplit-S Start): Operation for deleting a pair was started at the secondary disk array. Status of data volume pair changes from COPY to SMPL. • Status Change by RCU(PAIR to SMPL, Pairsplit-S Start): Operation for deleting a pair was started at the secondary disk array.
The following is an example of a snapshot file. Operation Date/Time 2004/07/10 17:20:00 2004/07/10 17:23:39 2004/12/31 23:58:14 (1) Copy Time JNL Group DD DD 002:33:44 DD (2) (3) Mirror ID 03 03 03 (4) VOL Paired VOL Operation 00:00 1F:FF Pair definition 01:01 1E:FE Paircreate Start 02:02 1D:FD Paircreate Complete (5) (6) (7) 1 Data and time when the operation finished. 2 Time taken for copying. This is displayed only when the operation is Paircreate Complete or Pairresync Complete.
Continuous Access XP Journal has already been started 1. Select the Optional Operation tab. The Optional Operation pane appears. Figure 62 Optional Operation pane • Tree: Select disk array. • List: disk array option settings (see ”Changing disk array options” on page 133). Optional Operation pane components • Tree: Select Subsystem or CLPR. • List: Displays one of the following: • Disk array option settings (see ”Changing disk array options” on page 133). • CLPR option settings.
1. Ensure that the Command View XP or XP Remote Web Console main pane is in Modify mode. For more information, see the HP StorageWorks Command View XP User Guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console User Guide for XP12000/XP10000. 2. Ensure that the Optional Operation pane is displayed (see ”Displaying the Optional Operation pane” on page 132). 3. Select Subsystem in the tree. The list displays disk array options (see ”Changing disk array options” on page 133). 4.
1. Identify the journal groups and data volumes containing important files and data for disaster recovery. 2. For Command View XP, install the management station. For Command View XP or XP Remote Web Console, install Continuous Access XP Journal hardware and software, and establish Continuous Access XP Journal operations for the journal groups and data volumes identified in step 1. 3. Establish file and database recovery procedures.
4. At the primary site, locate data volume pairs whose pair status is SMPL, and issue a request for deleting the pairs to the secondary data volumes. 5. Execute the pairresync -swaps command on secondary data volumes whose pair status is SSWS (pairresync is the RAID Manager command for resynchronizing pair and -swaps is a swap option). This reverses primary and secondary data volumes to resynchronize pairs. CAUTION: When executing the pairresync -swaps command, use the -d option to specify a data volume.
For more information about status of data volumes, see ”Continuous Access XP Journal data volume pair status” on page 28. Troubleshooting You are responsible for the operation and normal maintenance of the Command View XP management station. For troubleshooting information on Command View XP, see the Troubleshooting chapter of the HP StorageWorks Command View XP User Guide for XP Disk Arrays.
Table 28 General troubleshooting information for Continuous Access XP Journal (continued) Error Corrective action A Continuous Access XP Journal error message is displayed on the Command View XP management station. Remove the error cause, and retry the Continuous Access XP Journal operation. The status of a logical path is not normal. Check the path status in the DKC Status pane, and see Table 29. The pair status is suspended. Check the pair status in the Pairdisplay pane, and see Table 30.
Table 29 Troubleshooting problems with status of logical paths (continued) Pair status Description Corrective action Resource Shortage (Port) Disk array rejected the request for establishing a logical path because all resources in the local and remote disk arrays are being used for other connections. Delete the failed path and all paths and remote disk arrays not currently in use. The local disk array can be connected to up to 64 remote disk arrays with up to eight paths to each remote disk array.
Table 29 Troubleshooting problems with status of logical paths (continued) Pair status Description Corrective action Pair-Port Number Mismatch Specified port in the remote disk array is physically disconnected from the local disk array. Ensure that you specified the correct remote disk array port. Correct the port number if necessary. Ensure that the local and remote disk arrays are connected by cables to each other. If the disk arrays are not by cables, and retry the operation.
Table 30 Troubleshooting suspended Continuous Access XP Journal pairs Suspend type Applies to Description Corrective action PSUE, by RCU Primary data volume Primary disk array suspended a pair because the primary disk array detected an error condition at the secondary disk array. The suspend type for the secondary data volume is by MCU. Clear the error condition at the secondary disk array or secondary data volume. To access the secondary data volume, delete the pair from the primary disk array.
Table 31 provides troubleshooting instructions for Continuous Access XP Journal pair suspension. Hardware failures affecting cache memory and shared memory of the primary or secondary disk array might also cause Continuous Access XP Journal pairs to be suspended. Table 31 Resolving Continuous Access XP Journal pair suspension Classification Causes of suspension SIM Primary disk array hardware or secondary disk array hardware Hardware redundancy was lost due to DC0x some blockade condition.
Calling the HP Support Center If you need to call the HP Support Center, provide as much information about the problem as possible, including: • Command View XP or XP Remote Web Console configuration information saved on disk using the FD Dump Tool • Circumstances surrounding the error or failure • Exact content of any error messages displayed on the host systems • Continuous Access XP Journal (or other) error codes displayed by Command View XP or XP Remote Web Console • Reference codes and severity levels
When you power off primary disk arrays To power off the primary disk array during remote copy operations, first ensure that all data volume pairs or mirrors (that is, pairs of journal groups) are split and the status of all data volume pairs is PSUS. CAUTION: To power off the primary disk array, contact your HP account support representative and ask them to power off the disk array.
2. After splitting the pairs finishes, confirm that the status of all pairs is changed to PSUS at the primary disk array. 3. Power off the primary disk array as described in ”When you power off primary disk arrays” on page 144. Do not power on the primary disk array yet. 4. Power off the secondary disk array as described in ”When you power off secondary disk arrays” on page 144. 5. Power on the secondary disk array. 6.
3. Format the journal volume using the LDEV format function of Volume Management. For instructions on formatting the volume, see the HP StorageWorks LUN Configuration and Security Manager XP User Guide for the XP10000/XP12000. 4. Register the formatted volume (or another volume that can be used instead of the formatted volume) in the journal group (see ”Registering journal volumes in journal groups” on page 92). • If you do not need to resume copying, the procedure is finished.
Table 32 Typical SIM showing reference code and SIM type (continued) Reference code Byte 22 Byte 23 DC 0X Severity Description SIM generated by SVP log file Serious Volume being used by the primary data volume is suspended. Primary disk array SIM Log Primary disk array SIM Log Primary disk array SIM Log Primary disk array SIM Log Primary disk array SIM Log Primary disk array SIM Log Secondary disk array SIM Log Path recovery is impossible.
Continuous Access XP Journal
Index Numerics 3DC configuration cascading 61 multi-target 63 A Add DKC pane 80 applications, combining with 53 audience, documentation 9 B bandwidth 51 base-journals 23, 25 bitmap areas, number of 38 bitmaps, difference 23, 25 Business Copy XP 14, 56 C cable length, maximum 21, 35, 47 cache journal 27 pinned track recovery 145 requirements 40 cascading configuration 61 CKD-to-FBA conversions 25 combining with other applications 53 Command View XP troubleshooting management station 137 Command View XP or
G graph, Usage Monitor 126 graphical user interface 22 H hardware installation 46 help, obtaining 11 History Operation pane components 129 displaying 128 saving information as snapshot file 131 horctakeover command 135 host failover software 16, 22 HP storage web site 11 Subscriber’s choice web site 11 technical support 11, 143 HP Performance Control XP 56 I I/O statistics 128 initial copy operations 23 initiator ports 22, 79 installing hardware 46 integrity, data 14, 15, 40 interface 22 intermediate site
monitoring displaying Usage Monitor pane 124 graph, displaying 126 I/O statistics 128 saving data 128 starting 125 stopping 126 multiple secondary disk arrays 17 multiple secondary volumes 36 multi-target configuration 63 multivolume files 36 N network relay devices, powering off 143, 145 nonvolatile storage (NVS) 40 NVS (nonvolatile storage) 40 O obtain function 15 one-to-one copy operations 36 operational parameters 17 operations overview 13, 15 optional modes 17 Optional Operations pane components 133
troubleshooting 138 NVS (nonvolatile storage) 40 pair status 28 pinned track recovery 145 ports, configuring 79 powering off 120, 143, 144 read and write I/O operations 24 remote copy connections 47 remote, displaying information about 77 secondary disk arrays, functioning as 18 serial numbers 18 settings 133 storing journals 25 suspension conditions 33, 34 switching back to after disaster recovery 135 target ports 22 temporary path failures 50 update copy operation 24 primary site resuming normal operation
troubleshooting 138 multiple 17 NVS (nonvolatile storage) 40 pair status 28 pinned track recovery 145 ports, configuring 79 powering off 120, 143, 144 primary disk arrays, functioning as 18 read and write I/O operations 24 remote copy connections 47 remote, displaying information about 77 restoring journals 26 serial numbers 18 settings 133 suspension conditions 33, 34 target ports 22 temporary path failures 50 update copy operation 24 write operations 40 secondary site, switching to 135 secondary volumes B
V VMA (volume management area) 37 W web sites HP documentation 10 HP storage 11 HP Subscriber’s choice 11 154
