HP StorageWorks P9000 - Disk Arrays User Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Storage
  5. P9000
  6. User manual
HP StorageWorks P9000 - Disk Arrays User Manual

HP StorageWorks P9000 - Disk Arrays User Manual

Hp storageworks p9000 continuous access journal user guide (av400-96349, january 2011)
Hide thumbs Also See for StorageWorks P9000 - Disk Arrays:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Administrator's Manual, User Manual
HP StorageWorks
P9000 Continuous Access Journal User
Guide
Abstract
This guide explains how to use HP StorageWorks P9000 Continuous Access Journal Software to replicate data between local
and remote HP StorageWorks P9000 disk arrays and to achieve disaster tolerance with maximum application performance.
Topics include setting up remote copy connections, configuring the storage system, creating and monitoring remote copies,
recovering from a disaster, and troubleshooting. The intended audience is a storage system administrator or authorized service
provider with independent knowledge of HP StorageWorks P9000 disk arrays and the HP StorageWorks Remote Web Console.
HP Part Number: AV400-96349
Published: January 201 1
Edition: Third

Advertisement

Table of Contents
loading

Related Manuals for HP StorageWorks P9000 - Disk Arrays

Summary of Contents for HP StorageWorks P9000 - Disk Arrays

  • Page 1 HP StorageWorks P9000 Continuous Access Journal User Guide Abstract This guide explains how to use HP StorageWorks P9000 Continuous Access Journal Software to replicate data between local and remote HP StorageWorks P9000 disk arrays and to achieve disaster tolerance with maximum application performance. Topics include setting up remote copy connections, configuring the storage system, creating and monitoring remote copies, recovering from a disaster, and troubleshooting.
  • Page 2 © Copyright 2010, 201 1 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 1 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

  • Page 3: Table Of Contents

    Contents 1 Continuous Access Journal overview ............8 Continuous Access Journal software ...................8 How Continuous Access Journal works..................8 Hardware and software components...................9 P9500 storage systems.......................10 Main and remote control units ..................10 Pair volumes........................11 Journal volumes.........................11 Journals..........................11 Data path.........................12 Consistency groups and journals..................12 Remote Web Console......................12 RAID Manager........................13 Overview of copy operations....................13...
  • Page 4 System option modes ......................33 4 Planning the data path................35 Data path design workflow .....................35 Sizing bandwidth ........................35 Five sizing strategies ......................35 Calculating bandwidth ......................36 Sizing bandwidth for peak write-workload................36 Sizing bandwidth for peak rolling average write-workload..........37 Latency ........................38 Packet loss ........................38 Planning ports for data transfer ....................39 Determining required number of ports ..................39 On setting up ports ......................40...
  • Page 5 8 Maintaining the system ................82 Pair maintenance—change the pair-split option .................82 Journal and mirror maintenance....................82 Change Continuous Access Journal options used by journals ..........83 Change Continuous Access Journal options used by mirrors ............85 Delete journal volumes from a journal ..................87 Delete a journal ........................88 Logical path maintenance......................88 Modify data-transfer time threshold ..................89...
  • Page 6 1 1 Support and other resources..............126 Contacting HP........................126 Subscription service......................126 Related information.......................126 HP websites........................126 Conventions for storage capacity values..................127 Typographic conventions.......................127 HP product documentation survey...................128 A Sharing Continuous Access Journal volumes ..........129 Volume types that can be shared with Continuous Access Journal..........129 LUN Expansion........................131 Virtual LUN .........................131 Cache Residency........................131...
  • Page 7 D Continuous Access Journal GUI reference..........151 Journal Operation window ....................151 Journal Detail window ......................154 Change Journal Option dialog box ..................157 Change Mirror Option dialog box ..................157 Edit Journal Volumes dialog box.....................158 Pair Operation window ......................160 Detailed Information dialog box ..................164 Paircreate dialog box ......................167 Pairsplit-r dialog box .......................170 Pairresync dialog box ......................171...

  • Page 8: Continuous Access Journal Overview

    1 Continuous Access Journal overview Unless otherwise specified, the term P9000 in this guide refers to the following disk array: P9500 Disk Array The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer browser. Actual windows may differ depending on the operating system and browser used. GUI contents also vary with licensed program products, storage system models, and firmware versions.

  • Page 9: Hardware And Software Components

    Remote replication occurs using journal volumes on the local and remote systems. The journal on the local system is the “master journal”. The journal on the remote system is the “restore journal”. Replication occurs in the following sequence: Journal obtain - When the host sends an update to the primary volume, the system’s journal-obtain function triggers a copy of the update data to the master journal volume.

  • Page 10: P9500 Storage Systems

    A Continuous Access Journal system consists of the following: P-VOLs and S-VOLs on the local and remote P9500 Master and restore journal volumes on the local and remote P9500 Master and restore journals on the local and remote P9500 The master journal consists of the primary volume(s) and master journal volume(s). ◦...

  • Page 11: Pair Volumes

    MCUs control the primary storage volume (P-VOL) and the following operations: Host I/O operations to the P-VOL Master journal operations Initial copy and update copy operations between the P-VOL and secondary volume (S-VOL). RCUs control the secondary storage volume (S-VOL) and the following operations: Issue read-journal commands to the MCU.

  • Page 12: Data Path

    Figure 3 Journals Data path The physical transmission link between the local and remote systems is called the data path. Continuous Access Journal commands and data are transmitted through the fibre channel data path and switches. The data path is connected to the primary and secondary systems through two types of Fibre Channel ports, Initiator and RCU Target ports.

  • Page 13: Raid Manager

    NOTE: Administrator or Continuous Access Journal write access to the Remote Web Console Java applet program is required to perform these operations. Users without Administrator or Continuous Access Journal write access can only view Continuous Access Journal information. If the RAID Manager computer is not installed, contact your HP account team for information on Continuous Access Journal configuration services.

  • Page 14: Update Copy Operation

    NOTE: If you manipulate volumes (not journals) to create or resynchronize two or more data volume pairs within the same journal, the base journal data for these pairs will be stored in the restore journal. Therefore, the operation for restoring the latter base journal will be delayed. You can specify None as the copy mode for initial copy operations.

  • Page 15: Read And Write I/O Operations During Remote Copy Operation

    NOTE: Journal data is transferred using special I/O operations initiated by the secondary system (RCU), called RIO (remote I/O). RIO provides the most efficient type of data transfer. Make sure that your channel extenders are capable of supporting RIO. Contact HP Technical Support for more information.

  • Page 16: Pair Status

    The number of bitmap areas affects the maximum possible number of pairs that can be created in the storage system. Pair status Every pair operation results in a change in pair status. You should monitor pair status to insure that an operation completed successfully. Also, pairs must have a specific status in order for specific operations to be executed.

  • Page 17: Requirements And Specifications

    2 Requirements and specifications This chapter provides system requirements for Continuous Access Journal. System requirements Continuous Access Journal operations are performed between the host(s) and the primary and secondary storage systems containing the P-VOLs and S-VOLs, using the data path. General requirements for the Continuous Access Journal components are listed below.
  • Page 18 Table 1 General system requirements (continued) Item Requirement Volumes P-VOL and S-VOL must be equal in size. P-VOL and S-VOL must be of same emulation type. The maximum volume size of P-VOL and S-VOL is 4,194,304.000MB (8,589,934,592Block). However, when XP12000 Disk Array or XP10000 Disk Array is used as the primary or secondary storage system, the maximum volume size is 2,949,120.00MB (6,039,797,760Block).
  • Page 19 Table 1 General system requirements (continued) Item Requirement RAID Manager consistency groups Up to four journals can be registered in one RAID Manager consistency group. when multiple primary and If there are four storage systems, you must create one journal for each storage secondary storage system system.

  • Page 20: Planning Volumes And Systems

    3 Planning volumes and systems This chapter provides information and instructions for planning Continuous Access Journal volumes, P9500 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.

  • Page 21: Determining Your Rpo

    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.

  • Page 22: Sizing Journal Volumes

    To measure write-workload and IOPS Using your performance monitoring software, collect the following: Disk-write bytes-per-second (MB/s) for every physical volume that will be replicated. Data should be collected over a 3 or 4-week period to cover a normal, full business cycle. Data should be collected at 5 minute intervals.

  • Page 23: Calculating The Journal Size

    where: V is the data transfer speed between a host and the primary storage system. t is the length of time until the delta resync operation starts. CAUTION: The recommended journal volume capacity is 6 GB or more. If the capacity is less than 6 GB, system performance may decrease due to the following: The new data cannot be stored because the journal volume is full.

  • Page 24: Data Transfer Speed Considerations

    To plan journals, see the following: Review journal specifications in “System requirements” (page 17). Review journal configuration in “Register journal volumes in a journal ” (page 50). Data transfer speed considerations The previous sections and the sections later in this chapter on Bandwidth discuss the amount of data that must be stored temporarily in journals and transferred over the data path network.

  • Page 25: Planning Pair Volumes

    Journal volumes consist of two areas: one area is used for storing journal data, and the other area is used for storing metadata. Journal volumes support all RAID configurations that are supported by P9500. Journal volumes also support all physical volumes that are supported by P9500. Customized volumes can be used for journal volumes.

  • Page 26: Calculating Maximum Number Of Pairs

    The maximum number of pairs that can be created, calculated using the number of required bitmap areas. CAUTION: The bitmap areas that are used for Continuous Access Journal are also used for Continuous Access Journal Z, Continuous Access Synchronous Z, and Continuous Access Synchronous.

  • Page 27: Priority Set For Initial Copy Operations And Scheduling Order

    If the calculated maximum number of pairs exceeds the total number of LDEVs of the storage system and the total LDEV number is less than 32,768, the total number of LDEVs in the storage system is the maximum number of pairs that can be created. The maximum number of pairs is limited to 32,768.

  • Page 28: Disaster Recovery Considerations

    Table 6 Order of starting initial copy being performed Order of starting initial copy P-VOL Value set for Priority Remark LUN 02 Data volume pair for which initial copy is already instructed to be performed LUN 00 Data volume pair for which initial copy is already instructed to be performed LUN 01...

  • Page 29: Planning For Continuous Access Journal With Multiple P9500 Systems

    For planning information, see the following: “Continuous Access Journal configurations with Continuous Access Synchronous” (page 134) “Continuous Access Journal configurations with Business Copy” (page 147) “Sharing Continuous Access Journal volumes ” (page 129) for the following program products: LUN Expansion ◦...

  • Page 30: Multiple Journals Per Raid Manager Consistency Group

    Disaster recovery operations are possible. See “Disaster recovery when the system consists of multiple primary and secondary storage systems” (page 95). If an error occurs in a journal, it is possible that all journals may become suspended by the error. See “Suspension among journals ”...

  • Page 31: Planning For Previous Models

    Figure 6 RAID Manager consistency group with multiple journals—2 Figure 7 RAID Manager consistency group with multiple journals—3 Planning for previous models Continuous Access Journal can be used to perform remote copy operations between P9500 and XP24000/XP20000 Disk Array. Data can be copied from P9500 to XP24000/XP20000 Disk Array, or vice versa.

  • Page 32: Guidelines For Preparing Systems For Continuous Access Journal

    You can use the configuration instructions in this guide to set up the system. See “Configuration operations” (page 43) for information. Figure 8 Logical path between LDKC00 of P9500 and XP24000/XP20000 Disk Array P9500 corresponds to one system in the above-mentioned figure. XP24000/XP20000 Disk Array corresponds to the other system in the above-mentioned figure.

  • Page 33: System Option Modes

    Make sure that primary systems are configured to report sense information to the host. Secondary systems should also be attached to a host server to enable reporting of sense information in the event of a problem with a S-VOL or secondary system. If the remote system is not attached to a host, it should be attached to a primary site host server so that monitoring can be performed.
  • Page 34 Table 7 System option modes (continued) Mode Description To create a Continuous Access Journal pair for delta resync operation in the 3DC multitarget configuration, set this mode to ON. Mode 506 ON: The delta resync operation is performed if there are no update I/Os. Mode 506 OFF: The copy processing of all data is performed if there is no update I/Os.

  • Page 35: Planning The Data Path

    4 Planning the data path A data path must be designed to manage your organization’s throughput to the remote site. Appropriate bandwidth, required number of ports, and the Fiber Channel data path configuration you use help insure that your update data arrives at the remote site in a time consistent with your organization’s RPO.

  • Page 36: Calculating Bandwidth

    the journals will be completely emptied to the S-VOL only occasionally. If bandwidth is sized below average write-workload, the journals never fully drain and eventually overflow. You can size bandwidth and journal size for long-haul data migration, to be used where data consistency is not required.

  • Page 37: Sizing Bandwidth For Peak Rolling Average Write-Workload

    by optimizing or streamlining high-workload processes. Changing the timing of a process may lower workload. With a base bandwidth value established, make adjustments for growth and a safety factor. Projected growth rate accounts for the increase expected in write-workload over a 1, 2, or 3 year period.

  • Page 38: Latency

    For another perspective, you can graph the data, as shown in Figure 1 1 (page 38). Figure 1 1 60-minute rolling averages graphed over raw data From the spreadsheet or graph, locate the largest or highest rolling average value. This is the peak rolling average, which indicates the base amount of data that your bandwidth must be able to handle.

  • Page 39: Planning Ports For Data Transfer

    Planning ports for data transfer Updated data is transferred along the data path from the initiator and RCU target ports on the primary and secondary systems. Initiator ports send data. RCU target ports receive data. The amount of data each of these ports can transmit is limited. You must know the amount of data that will be transferred during peak periods.

  • Page 40: On Setting Up Ports

    The data transfer speed of your Continuous Access Journal ports must be greater than peak write-IOPS. Using peak IOPS and the IOPS threshold of your systems’ port microprocessors, calculate the number of microprocessors (and Fibre Channel ports) the Continuous Access Journal system requires.

  • Page 41: Supported Data Path Configurations

    This information is illustrated in Figure 12 (page 41). Figure 12 Data path types, switches, and distances Supported data path configurations The remote data path can be configured in one of the following connection types. But for switch connection, the port should be set to Fabric on, Point-to-Point (F-port). Direct connection, as shown in Figure 13 (page 41).
  • Page 42 Figure 14 Switch connection configuration Figure 15 Extender connection configuration NOTE: When an MCU and RCU are connected using switches with channel extender, and multiple data paths are assembled, the capacity of data to be transmitted may concentrate on particular switches, depending on the configuration and the settings of switch routing.

  • Page 43: Configuration Operations

    5 Configuration operations This chapter provides the configuration tasks that will make your primary and secondary systems ready for Continuous Access Journal pair operations. Configuration workflow You will set up primary and secondary systems for Continuous Access Journal operations as follows. Check the prerequisites for each procedure.
  • Page 44 Before a fiber channel initiator port can be changed to target or RCU target, the following must be performed: All affected data volume pairs must be released. ◦ All logical paths must be deleted from the initiator port to the remote storage system. ◦...

  • Page 45: Configure Storage Systems For Continuous Access Journal, Define Logical Paths

    Configure storage systems for Continuous Access Journal, define logical paths Prerequisite Information This procedure must be performed on both primary and secondary systems. The primary and secondary systems must already be configured for Continuous Access Journal operations. See “System requirements” (page 17) for more information.
  • Page 46 In the S/N box, enter the remote system’s 5-digit serial number. In the LDKC box, select the remote system’s LDKC number. Enter 00 when the remote system is P9500, XP24000/XP20000 Disk Array, or XP12000 Disk Array/XP10000 Disk Array. In the Controller ID box, select the remote system’s controller ID. The controller ID for a P9500 storage system is 6.

  • Page 47: Configure Additional Logical Paths

    1 1. The Minimum Paths box is intended for a future release. Continue to the next step. 12. RIO MIH means “Remote I/O Missing Interrupt Handler”. In the RIO MIH Time box, enter the amount of time from 10 seconds to 100 seconds (15 seconds is the default).

  • Page 48: Specify Number Of Volumes For Initial Copy, Resync

    In the M-R Path box, define the Fibre Channel port used by logical path between local and remote systems: In the Port, select a local system initiator port. In the Pair-Port, select the remote system RCU target port. You may enter port numbers using the keyboard. You may abbreviate the number into two characters.
  • Page 49 To specify number of volumes to copy concurrently In Remote Web Console, select Actions > Remote Copy > Continuous Access Journal > Optional Operation. Click to change the mode from View to Modify. Right-click the value that displays under Activities in the right-side pane, then select Change System Option from the menu.

  • Page 50: Register Journal Volumes In A Journal

    Register journal volumes in a journal You set up journal volumes by registering them in a journal. The procedure is provided below. Prerequisite information The emulation type of the volume that can be registered in the journal is only OPEN-V. For details, see (page 17).
  • Page 51 Click to change the mode from View to Modify. To register journal volumes in an existing journal, select the journal from the Registered tree. To register journal volumes in a new journal, select the journal from the Free tree. The selected journal displays in the upper-right list of the window. The journal volume cannot be registered when there are mirrors other than the following statuses in the journal of the Registered: Status: Initial, Active, Stopped, Hold, Holding, or Hold(Failure).
  • Page 52 Click Set to close the Edit Journal Volumes dialog box. See the Preview list in the Journal Operation window to check the journal volumes that you have added. If you want to add a another volume, select the journal to add a volume in the Preview list and right click and then select Modify.

  • Page 53: Pair Operations

    6 Pair operations This chapter provides procedures and prerequisite information for performing Continuous Access Journal copy operations. Pair operations workflow Basic Continuous Access Journal operations consists of the following. Always check pair status. Each Continuous Access Journal operation requires the pair to be in a specific status.
  • Page 54 If you are creating a Continuous Access Journal pair for delta resync, make sure all requirements are met. See “Creating a delta resync pair ” (page 141). If this program product is running on a primary storage system or secondary storage system, stop Performance Monitor before performing the initial copy to avoid overloading with TCP/IP traffic.
  • Page 55 Data for the selected volume displays in the P-VOL box. The numbers indicate the port, GID, LUN, and volume. One P-VOL displays at a time, even if you selected multiple volumes for pairing. The volume with the lowest number displays first. Specify an S-VOL as follows: Select the port, GID, and LUN from the three S-VOL , left to right.
  • Page 56 If multiple pairs are created at one time, use the Select Other S-VOL(s) list to specify S-VOLs. If you selected multiple volumes as P-VOLs, you can instruct the system to automatically assign S-VOLs for the remainder of P-VOLs. Do this from the Select Other S-VOL(s) list, as follows: - Select Increment to cause Continuous Access Journal to add the secondary system LUN incrementally.

  • Page 57: Split A Pair

    by the CU configuration or a remote copy path error. Review the error, release the pair with the error, and then retry the Paircreate operation. 10. In the Error Level list, select one of the following options to take place in the event a failure occurs during this operation: Mirror, to cause all pairs in the failed pair’s mirror to be split.
  • Page 58 To split one or more pairs In Remote Web Console, select Actions > Remote Copy > Continuous Access Journal > Pair Operation. Click to change the mode from View to Modify. In the tree, select the port or host group. Paired volumes are displayed in the upper-right-side list area.

  • Page 59: Split A Mirror

    See the Preview list to check the settings that you have made. If you want to modify a setting, select and right click the item in the Preview list and then select Modify. If you want to delete a item, select and right click the item in the Preview list and then select Delete.

  • Page 60: Restore A Pair

    Restore a pair If the pair is restored, the suspended data copy from the primary data volumes to the secondary data volumes is resumed. If the delta resync pair is restored, the delta resync processing is performed. This section describes the pair resync operation. Also, the instructions are used when performing the delta resync operation.
  • Page 61 If you used the Continuous Access Journal pair for delta resync operation as the master journal after a power supply error occurred at the primary storage system, resynchronize the pair, and then execute I/O operation from the host. The Continuous Access Journal delta resync S-VOL cannot be used with Business Copy or Thin Provisioning.

  • Page 62: Resynchronize A Mirror

    - The Range column shows Mirror for at least one of the above pairs. To be able to continue processing, do either of the following: - Ensure that the Range column shows LU for all pairs in the same mirror. - In the Preview list, select one pair in one mirror, and then other pairs in the mirror is excluded.

  • Page 63: Delete A Pair

    configuration of multiple journals for one consistency group is allowed only in the system that consists of multiple primary and secondary storage systems (see Figure 4 (page 29)). Because the Remote Web Console does not support the system that consists of multiple primary and secondary storage systems, an error occurs if you try to restore a mirror by using the Remote Web Console in this system configuration.
  • Page 64 In a delta resync configuration, if you release the Continuous Access Synchronous pair, the Continuous Access Journal delta resync pair will be released as well. If you release the Continuous Access Journal pair, the Continuous Access Journal delta resync S-VOL is released. If Continuous Access Journal secondary data volumes are physically attached to the same host server(s) as the Continuous Access Journal primary data volumes, the following problem can occur:...

  • Page 65: Delete Pair Volumes From A Mirror

    - In the Preview list, select one pair in one mirror, and then other pairs in the mirror is excluded. CAUTION: Do not use the Mirror option when deleting pairs from the secondary system during disaster recovery. From the Delete Mode list, select one of the following: Normal, to delete the pair or pairs only if the primary system is able to change the pair status of both P-VOL and S-VOL to SMPL.
  • Page 66 Operate one of the following: In the tree, select a master journal or a restore journal from below Registered. In the tree, select Journals or Registered and then select a master journal or a restore journal from the list to the right. A list of mirrors appears.

  • Page 67: Monitoring The System

    7 Monitoring the system Monitoring pairs, journals, and data paths should be checked frequently to ensure that Continuous Access Journal pairs are operating correctly. Pair status should be checked before performing a Continuous Access Journal operation. Each operation requires specific pair status. Monitor pair activity and status Monitoring the Continuous Access Journal system is an ongoing operation that should be performed frequently to maintain your pairs.
  • Page 68 Pair status Description P-VOL access S-VOL access PSUS The user has split the pair or released the pair; the pair is no Read/Write Read Only, longer synchronized. unless write option is The primary and secondary systems keep track of journal data enabled.
  • Page 69 Pair status Description P-VOL access S-VOL access HOLDING * The pair status is changing to Hold so that the delta resync pair Read/Write can be created. If you execute the delta resync operation on the pair in HOLDING status, the operation may fail. If you set Entire for the field, Delta resync Failure, on the Change Journal Option dialog box, differential data will be copied to a S-VOL.
  • Page 70 Pair status Description P-VOL access S-VOL access SSWS After Takeover, SSWS is the status of the S-VOL. With this status, Read Only Read/Write data can be written to the S-VOL. SSWS is displayed by RAID Manager, from which the horctakover command is issued. Remote Web Console displays this status as PSUS or PSUE.

  • Page 71: Psus Types And Behaviors

    where: ◦ C is total capacity (MB) of the master journal volume. u is the usage rate of data (%) in the master journal volume. ◦ V is data transfer speed (MB/sec) between the primary and the secondary systems. ◦ “Usage Monitor window ”...

  • Page 72: Psue Types And Behaviors

    Consistency status displays on the secondary system only. S-VOL consistency statuses are described below. Table 8 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 insured.

  • Page 73: Filtering Information In The List In The Pair Operation Window

    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.

  • Page 74: Saving Pair Status Information Into A Text File

    Set: Applies the settings in the Display Filter dialog box to the list. Cancel: Discards the settings and closes the dialog box. Saving pair status information into a text file You can use the export function only while the client file access is enabled. When the client file access is not enabled, the Export is not available on the Pair Operation window.

  • Page 75: Monitor Copy Operations Data, I/O

    In the Pair Operation window, click Export. A message appears and asks whether to save volume pair information in a file. Click OK to close the message. A dialog box appears and prompts you to save a file. Enter the name of the file and then click Save. A message appears.

  • Page 76: Select Data To Be Graphed

    Table 9 Fields on the Usage Monitor window (continued) Field Description Update The most recent data sample time of data on the graph. Usage Monitor Graph Remote I/O statistics and status of remote copy monitor. Select data to be graphed The usage monitor graph plots the I/O data that you specify.
  • Page 77 Click Set to close the Display Item dialog box. The Usage Monitor window now shows a graph of the selected I/O statistics data for the selected LU(s). Table 10 Remote copy I/O statistics data Data type Description Host I/O Write Record Count The number of write I/Os per second.

  • Page 78: Manipulate Graph, Save Data

    Table 10 Remote copy I/O statistics data (continued) Data type Description R-JNL Average Transfer Rate The average transfer rate for journals in the secondary storage system. The unit is kilobytes per second. R-JNL Average RIO Response The remote I/O process time on the secondary storage system. The unit is milliseconds.

  • Page 79: Monitor Logical Path Status

    Status Description An operation for splitting or deleting the mirror is in progress. Halting Splitting a mirror changes the status in the following order: Halting, Halt, Stopping, and finally Stopped. Deleting a mirror changes the status in the following order: Halting, Halt, Stopping, Stopped, and finally Initial.
  • Page 80 To see in-depth path status, right-click the remote system and select DKC Status. Item Description Number of the row. Path Status Status of a logical path. Normal. The path is established and ready to use for copy operations. Nothing. An operation for configuring or deleting the path is in progress. Initialization Failed.

  • Page 81: History Of Operations For Data Volume Pairs

    History of operations for data volume pairs The History window provides the history of operations for data volume pairs. For example, the window shows the date and time when data volume pairs are created or released. To open the History window, do either of the following: If Continuous Access Journal has not been started: In Remote Web Console, select Actions >...

  • Page 82: Maintaining The System

    8 Maintaining the system Some maintenance tasks are a response to behavior discovered during system monitoring. However, you can also change certain settings to keep the system in tune with your changing requirements. Pair maintenance—change the pair-split option You can change the option that specifies whether a pair-split operation that is triggered by pair failure is applied to all the pairs in the mirror, or only to the affected pair.

  • Page 83: Change Continuous Access Journal Options Used By Journals

    Change Continuous Access Journal options used by journals Most Continuous Access Journal pair operations are performed on multiple pairs. This is done using journals. You can change the following options that affect the pairs in journals: Inflow Control—allows you to restrict the inflow of data to allow other journals with higher priority data unrestricted inflow Data Overflow Watch—establishes a timeout period Use of Cache—which enables using store journal data in the cache on the secondary system...
  • Page 84 For Inflow Control, specify whether to restrict inflow of update I/Os to the journal volume (slows delay response to hosts). For example, you could have a 100 GB-bandwidth data path with three journals using it. If an important database is saved to a primary volume in one of the journals, with data of lesser importance in the other journals, you may decide to restrict the Inflow Control for the less important journals while not restricting control to the important journal.

  • Page 85: Change Continuous Access Journal Options Used By Mirrors

    Change Continuous Access Journal options used by mirrors Most Continuous Access Journal 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: Unit of Path Watch Time—establishes the unit of path watch time.
  • Page 86 For Copy Pace, specify the pace for initial copy activity per volume. This field cannot be specified on the remote system. Low is the default. When specifying Medium, insure that write I/O is 10 MB/s or less per parity group. If it exceeds 10 MB/s, pairs may be suspended. When specifying High, insure that I/O will not occur.

  • Page 87: Delete Journal Volumes From A Journal

    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. For Delta resync Failure, specify the processing that takes place when the delta resync operation cannot be performed.

  • Page 88: Delete A Journal

    Select and right-click the desired journal. Only one journal can be selected. Click Edit Journal Volumes from the menu that displays. The Edit Journal Volumes dialog box displays. From the Journal Volumes list, select the volumes that you want to delete. Click the Delete.

  • Page 89: Modify Data-Transfer Time Threshold

    Modify 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 Modifying the data-transfer threshold can be performed from the primary storage system or secondary storage system.

  • Page 90: Delete The Logical Path Between Primary And Secondary Storage System

    Locate the desired remote system, right-click, and select Delete Path. A confirmation message appears. Click OK. See the Preview list to check the settings that you have made. If you want to delete a item, select and right click the item in the Preview list and then select Delete.

  • Page 91: When Power Stops Unexpectedly

    When power stops unexpectedly This section explains what happens when power is removed from systems or network relay devices due to an unexpected reason. CAUTION: When a system is powered on, you must wait five (5) minutes before performing Continuous Access Journal operations; otherwise the pairs could be suspended with a failure. When power is removed from primary or secondary system If power is removed from the primary system during remote copy operations, the primary system assumes that a failure has occurred and splits all pairs.

  • Page 92: Power Off The Primary And Secondary Systems At The Same Time

    Power off the primary and secondary systems at the same time The primary system must be powered off before the secondary system is powered off. When you are ready to power the systems on, the secondary system must be powered on before the primary system.

  • Page 93: Disaster Recovery Operations

    9 Disaster recovery operations This chapter provides guidelines for performing disaster recovery operations. Also included are disaster recovery procedures when Continuous Access Journal is configured with Continuous Access Synchronous and Business Copy. Preparing for disaster recovery The major steps for preparing for disaster recovery are: Identify the data volumes that you wand to back up for disaster recovery.

  • Page 94: Copy Data Back To The Primary Site

    Copy data back to the primary site When the disaster recovery procedure is completed and host applications are running at the secondary site, the next activity is to restore the primary site and re-establish the Continuous Access Journal system for copying data from the secondary site to the primary site. The following procedure explains how to re-establish control of the Continuous Access Journal pairs and copy data from the secondary site to the primary site: Procedure 2...

  • Page 95: Disaster Recovery When The System Consists Of Multiple Primary And Secondary Storage Systems

    When all S-VOLs at the primary site are PSUS status, data in P-VOLs and S-VOLs are the same. S-VOLs at the primary site are ready for host read/write activity. Resume applications at the primary site. Execute the pairresync -swaps command, which reverses P-VOLs and S-VOLs and resynchronizes the pairs.

  • Page 96: Recovery Procedures With Shared Volumes

    Figure 17 Flow of the case of transferring the business tasks from the remote to primary site Recovery procedures with shared volumes Restoring operations with shared Continuous Access Journal and Continuous Access Synchronous or Business Copy volumes is a bit more complicated than with a straight Continuous Access Journal pair.

  • Page 97: Recovery In A 3Dc Cascade Configuration

    Recovery in a 3DC cascade configuration If a disaster or failure occurs in the primary site of a 3DC cascade configuration, you transfer business operations to the intermediate Continuous Access Synchronous secondary volume (S-VOL) site. After this is done, the primary site should be corrected and brought back online. Then, you have choices for proceeding: re-create the cascading configuration, or change the Continuous Access Journal/Continuous Access Synchronous configuration to multitarget.
  • Page 98 Check the execution result of the horctakeover command, and then do either of the following: Procedure 3 If the primary/secondary relationship of the Continuous Access Synchronous pair is not reversed (that is, the copy direction is not reversed), use RAID Manager to create a Continuous Access Journal pair.

  • Page 99: Recovering From Primary Site Failures (When Delta Resync Operation Is Performed)

    Transferring business tasks from Continuous Access Synchronous secondary to primary site (in 3DC multitarget configuration) If you remove failures from the primary site and other locations and then the system is changed to 3DC multitarget configuration, you can transfer your business tasks back to the primary site. To transfer your business tasks back to the primary site, follow the procedure below.
  • Page 100 Table 12 Changes of Continuous Access Journal pair status by delta resync operation (when recovering from failures in the primary site) Cnt Ac-J pair Pair status before delta resync operation Pair status after delta resync operation P-VOL S-VOL P-VOL S-VOL Cnt Ac-J pair PAIR, PSUS, or PSUE PAIR, PSUS, or PSUE...

  • Page 101: Recovering From Failures In The Primary Site And The Continuous Access Synchronous Secondary Site

    CAUTION: When transferring business tasks back to the primary site when using delta resync: After you remove failures from the primary site and other locations and then the system is changed to 3DC multitarget configuration (see “Recovering from primary site failures (when delta resync operation is performed)”...

  • Page 102: Recovery In A 2Dc Configuration

    Transferring business tasks from the Continuous Access Journal secondary to the primary Site If you follow the instructions in the previous section and then remove failures from the primary site and the Continuous Access Synchronous secondary site, you can transfer your business tasks back to the primary site.

  • Page 103: Recovery With Business Copy Configuration

    After the new Continuous Access Journal pair is in PAIR status, stop host operations at the remote site, then release the Continuous Access Journal pair. On the intermediate site, if Continuous Access Synchronous or Continuous Access Journal pairs exist, release them. On the intermediate site, create a Continuous Access Journal pair to the Continuous Access Journal remote site, with no data copying (specify None on the Copy Mode option).

  • Page 104: 10 Troubleshooting

    10 Troubleshooting This chapter provides troubleshooting information. General troubleshooting General troubleshooting information for Continuous Access Journal follows. Table 15 General troubleshooting Error Corrective action Remote Web Console hangs, or Cnt Ac-J Make sure that the problem is not being caused by the computer or operations do not function properly.

  • Page 105: Troubleshooting Logical Paths

    Table 15 General troubleshooting (continued) Error Corrective action The pair create or pair resync operation resulted If the timeout error was caused by a hardware failure, a SIM is in a timeout error. generated. See “Service information messages (SIMs) ” (page 123).
  • Page 106 Table 16 Logical path troubleshooting (continued) Path status Description Corrective action Serial Number The serial number (S/N) of Make sure that you entered the correct secondary system S/N and Mismatch the secondary system does path parameters (for example, primary and secondary system port, not match the specified and controller ID).

  • Page 107: Troubleshooting Suspended Pairs

    Table 16 Logical path troubleshooting (continued) Path status Description Corrective action Logical Blockade A failure occurs at a Repair the port status on the primary system. primary system port. A failure occurs at a Repair the port status on the secondary system. After that, delete the secondary system port.
  • Page 108 Table 17 Suspended pair troubleshooting (continued) Suspend type Applies to Description Corrective action PSUE, MCU P-VOL, S-VOL The primary storage system could not find Restore the pair (pairresync) from the IMPL valid control information in its nonvolatile primary storage system. The primary storage memory during the IMPL procedure.

  • Page 109: Troubleshooting Using Remote Web Console

    Table 18 Resolving pair suspension (continued) Classification Causes of suspension Recovery procedure RIO overload or An unrecoverable RIO (remote I/O) DC2x Release failed pairs (pairsplit-S). RIO failure timeout occurred because the system or If necessary, increase resources as needed. network relay devices were overloaded. For example, the amount of cache, the Or, RIO could not be finished due to a number of paths between primary and...
  • Page 110 To identify the error code in the log file, open the RAID Manager log file, and find the error code. Example: 1 1:06:03-37897- 1 0413- SSB = 0xb9a0,2089 Error codes appear on the right of the equal symbol (=). The alphanumeric characters on the left of the comma (,) indicates SSB1 (for example, B901), and on the right of the comma (,) indicates SSB2 (for example, 4A96).
  • Page 111 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content 3720 A request by Cnt Ac-J Paircreate or Pairresync was rejected because the journal volume in the specified master journal was blocked. 3723 The Cnt Ac-J pair cannot be created because the version of the DKCMAIN micro program on the remote storage system does not support the LUSE...
  • Page 112 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content 8F1 1 The Cnt Ac-J pair cannot be created. The processing of volume migration could not be stopped because the P-VOL was being migrated by Auto LUN. 8F14 The Cnt Ac-J pair cannot be created because the specified volume was the reserved volume.
  • Page 113 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content 8F35 The following programs for OPEN systems might not be installed, or the licenses of them might be expired. Please confirm settings for: Continuous Access Synchronous Continuous Access Journal 8F39...
  • Page 114 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content B901/B9E0/B9E1/ B902 Cnt Ac-J Paircreate cannot be performed because the mirror ID is invalid. B9E2/B9E4/D004 B907 The command was rejected because the volume status was SMPL. B90A The S-VOL hide mode is not supported.
  • Page 115 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content DB08 Cnt Ac-J pair status cannot be transited during the power-off processing. DB0C A request of Cnt Ac-J Pairresync (journal resync mode) was rejected because the specification was volume instead of group.
  • Page 116 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content E87B A request of Cnt Ac-J Paircreate was rejected because the specified journal was unregistered. E87C Journal volume is not registered in the specified journal. E87D A request of Cnt Ac-J Pairresync was rejected because the specified volume was not for the Cnt Ac-J pair.
  • Page 117 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content E8A6 The specified journal number is unregistered. E8A7 Journal volume is unregistered on the specified journal. E8A8 A request of Cnt Ac-J suspend pair was rejected because the specified volume was not for a Cnt Ac-J pair or was a volume of another journal.
  • Page 118 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content EA1B A request of Cnt Ac-J Pairresync (suspend transition mode) was rejected because the journal could not execute the suspend transition, that is, the journal was in HLDE or PSUE status.
  • Page 119 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content EA95 A request of Cnt Ac-J Paircreate was rejected because the volume specified for the primary volume was being initialized by Business Copy. EAA2 A request of Cnt Ac-J Paircreate was rejected because the desired capacity exceeded the charging capacity of the primary system’s Cnt Ac-J.
  • Page 120 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content EB28 A request to create or resynchronize a pair in the system that consists of multiple primary and secondary systems was rejected because the Cont Access Journal 3DC &...
  • Page 121 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content EB5E A request of Cnt Ac-J Paircreate was rejected because the state of S-VOL was not SMPL. EB5F A request of Cnt Ac-J Paircreate was rejected because the program product of Cnt Ac-J was not installed in the secondary system.
  • Page 122 Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content EB80 The command was rejected because the specified volume was the V-VOL or the pool-VOL. Please check the status of the volume. EB87 A request of Cnt Ac-J Paircreate was rejected because the path from the secondary system to the primary system was not set, or the S-VOL was in...

  • Page 123: Service Information Messages (Sims)

    Table 19 RAID Manager error codes for Continuous Access Journal (continued) Error code (SSB1) Error code (SSB2) Error content EBCF The Cnt Ac-J Pairresync (journal resync mode that forcibly copies all data) was received because of the Cnt Ac-J Pairresync (journal resync mode) failed.
  • Page 124 severity. The SIM type (byte 28) indicates the component that experienced the error. When the value of byte 22 is 21, the SIM is a control unit SIM. When the value of byte 22 is Dx (where x is an arbitrary character), the SIM is a device SIM. Figure 18 Typical SIM with reference code and SIM type NOTE: The SIMs shown below are reported to the host, except 21 81.

  • Page 125: Miscellaneous Troubleshooting

    Table 20 SIM reference codes, types, and descriptions (continued) Reference code Severity Description System generating the SVP log file Byte 22 Byte 23 Serious A volume being used by S-VOL has been Primary system SIM Log suspended. Path recovery is impossible. Serious A volume being used by S-VOL has been Secondary system...

  • Page 126: 1 Support And Other Resources

    1 1 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions...

  • Page 127: Conventions For Storage Capacity Values

    http://www.hp.com/support/manuals http://www.hp.com/support/downloads http://www.hp.com/storage/whitepapers Conventions for storage capacity values P9000 disk arrays use the following values to calculate physical storage capacity values (hard disk drives): 1 KB (kilobyte) = 1,000 bytes 1 MB (megabyte) = 1,000 bytes 1 GB (gigabyte) = 1,000 bytes 1 TB (terabyte) = 1,000 bytes...

  • Page 128: Hp Product Documentation Survey

    WARNING! Indicates that failure to follow directions could result in bodily harm or death. CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: Provides clarifying information or specific instructions. NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts.

  • Page 129: A Sharing Continuous Access Journal Volumes

    A Sharing Continuous Access Journal volumes This appendix discusses non-Continuous Access Journal volumes that can be shared as Continuous Access Journal volumes. It discusses the volumes of several features that can be used in full or limited ways with Continuous Access Journal. Continuous Access Synchronous and Business Copy volumes can be used extensively with Continuous Access Journal.
  • Page 130 Table 22 Volume types that can be shared with Continuous Access Journal (continued) Volumes types Can the volumes be Can the volumes be Can the volumes be used as P-VOLs? used as S-VOLs? used as journal volumes? Source volume (after volume migration is finished) Reserved volume to which no path is defined Continuous Access Synchronous...

  • Page 131: Lun Expansion

    Table 22 Volume types that can be shared with Continuous Access Journal (continued) Volumes types Can the volumes be Can the volumes be Can the volumes be used as P-VOLs? used as S-VOLs? used as journal volumes? Virtual volume The volume cannot be used as a Cnt Ac-J data volume for delta resync. For information on Auto LUN, contact HP Technical Support.

  • Page 132: Thin Provisioning

    Thin Provisioning You can create a Continuous Access Journal pair by specifying V-VOL (Thin Provisioning virtual volume). V-VOLs can be either the Continuous Access Journal P-VOL or S-VOL, or both P-VOL and S-VOL. V-VOLs cannot be used for Continuous Access Journal journal volumes. You can use V-VOLs that are used by a Business Copy pair or a that are in an Auto LUN's migration plan.

  • Page 133: Performance Monitor

    Table 23 Status, availability of Data Retention operation (continued) Cnt Ac-J Pair status Changing access attribute Referencing access attribute volume S-VOL SMPL COPY PAIR PSUS PSUE *Note: If the Write option is set to the S-VOL, the access attribute can be changed. Table 24 Possible changes to access attribute when Continuous Access Journal P-VOL status is PAIR or COPY Access attribute...

  • Page 134: B Continuous Access Journal Configurations With Continuous Access Synchronous

    B Continuous Access Journal 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 chapter provides planning formation for sharing Continuous Access Journal volumes with Continuous Access Synchronous.

  • Page 135: 3Dc Cascade Configuration

    3DC cascade configuration As illustrated below, the Continuous Access Synchronous P-VOL is the primary production volume in a 3DC cascade configuration. The Continuous Access Synchronous S-VOL is located at an intermediate site that is near the primary site. The host issues an update to the Continuous Access Synchronous primary volume (P-VOL), which is copied synchronously to the S-VOL.

  • Page 136: Procedure For Setting Up 3Dc Cascade

    The remote site requires the following: ◦ Continuous Access Journal ◦ Continuous Access Journal S-VOL Continuous Access Journal remote journal volume ◦ Differential data is used to resynchronize a suspended Continuous Access Synchronous or Continuous Access Journal pair. When the Continuous Access Synchronous pair is recovered, the Continuous Access Journal pair in PAIR or COPY status is automatically split by the system.

  • Page 137: Prerequisite Information For 3Dc Multitarget

    The host issues an update to the production volume and, synchronously, to the Continuous Access Synchronous S-VOL. As with a standalone Continuous Access Journal system, the update data is asynchronously written from the primary volume (P-VOL) to the Continuous Access Journal S-VOL. The benefit of this configuration is that it provides a third copy of the data, helping to insure that business can continue in the event of a failure at the other two sites.

  • Page 138: Delta Resync Configuration

    Create a Continuous Access Synchronous pair on the primary system. See HP StorageWorks P9000 Continuous Access Synchronous User Guide for instructions. When Continuous Access Synchronous pair status is PAIR, create the Continuous Access Journal pair on the primary system. The mirror ID must be set between 1 and 3. Delta resync configuration In a Continuous Access Journal delta resync configuration, you create a second Continuous Access Journal pair in a 3DC multitarget.

  • Page 139: Prerequisite Information For Creating The Delta Resync Pair

    Prerequisite information for creating the delta resync pair A Continuous Access Journal delta resync pair is created in a 3DC multitarget configuration only. Do not include the 3DC multitarget configuration in a system that consists of multiple primary and secondary storage systems. Use Continuous Access Synchronous S-VOL in PAIR status as the primary data volume.
  • Page 140 When the Continuous Access Journal pair status changes to HOLD after the delta resync ◦ operation When you re-create the Continuous Access Journal pair for delta resync operation when ◦ recovering the primary site When the pair recovery operation is performed on the suspended Continuous Access Synchronous pair or Continuous Access Journal pair, allow the 3DC configuration to remain status for at least 5 minutes before you execute any other continuous access-related commands.

  • Page 141: Creating A Delta Resync Pair

    The secondary volume of the Continuous Access Journal pair for delta resync operation is V-VOL. The secondary volume of the Continuous Access Journal pair for delta resync operation is assigned to the primary volume of Business Copy. If the status of the Continuous Access Journal pair for delta resync operation does not change after performing the delta resync operation, some of these requirements may not have been met.

  • Page 142: Assign Mirrors To Remote Command Devices

    Repeat the previous step so that two command devices on each site are mapped to a remote command device on each of the other two sites. Thus: Each site should have two command devices mapped via two target ports to the other two sites.

  • Page 143: Release A Remote Command Device Which Is Assigned To A Mirror

    Assign mirror IDs to remote command devices as follows. On primary site: - Assign mirror ID 00 to the remote command device that is mapped to on the intermediate site. - Assign the mirror ID used for the Continuous Access Journal 3DC multitarget pair to the remote command device that is mapped to on the remote site.

  • Page 144: Perform The Delta Resync Operation

    To release a remote command device which is assigned to a mirror Ensure that the Remote Web Console main window is in Modify mode. For detailed information about how to do this, see HP StorageWorks P9000 Remote Web Console User Guide. Ensure that the Journal Operation window is open.

  • Page 145: Prerequisite Information For 2Dc Configuration

    Prerequisite information for 2DC configuration P9500 must be installed at the local, Continuous Access Synchronous intermediate, and Continuous Access Journal remote sites. RAID Manager is recommended at all sites. If the intermediate site is not connected to a host, a remote command device is required. See HP StorageWorks P9000 RAID Manager User Guide for more information.

  • Page 146: Specifications And Restrictions For Continuous Access Synchronous Pair Operations

    Specifications and restrictions for Continuous Access Synchronous pair operations Specify a volume for the Continuous Access Synchronous P-VOL that is not used in a Continuous Access Journal pair In the 2DC configuration, use the journal that was registered when 2DC Cascade was set to Enable in the Edit Journal Volume dialog box.

  • Page 147: C Continuous Access Journal Configurations With Business Copy

    C Continuous Access Journal 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 primary and secondary sites. This chapter provides configurations and information for using Business Copy with Continuous Access Journal.
  • Page 148 Figure 25 Shared Continuous Access Journal and Business Copy primary volume A Continuous Access Journal secondary volume shared with the Business Copy primary volume is illustrated below. With this configuration, multiple backup copies of the Continuous Access Journal primary volume can be made on the remote system. CAUTION: When you share a Continuous Access Journal S-VOL with a Business Copy P-VOL as shown in the following figure, the write operation to the Continuous Access Journal P-VOL...

  • Page 149: Configurations With Business Copy Secondary Volumes

    Figure 27 Shared Continuous Access Journal primary volume and secondary volume with Business Copy primary volumes Configurations with Business Copy secondary volumes The following figure shows a Business Copy primary volume used as the production volume. A remote Continuous Access Journal backup copy is made of the Business Copy secondary volume. The Business Copy pair must be in PSUS status (Split) to perform the Continuous Access Journal operation.
  • Page 150 lowest LDEV ID. To see status for the pairs with a different secondary volume, direct a host query to the specific secondary volume using the secondary volume’s LDEV ID in the host command. 150 Continuous Access Journal configurations with Business Copy...

  • Page 151: D Continuous Access Journal Gui Reference

    D Continuous Access Journal GUI reference This appendix describes the Continuous Access Journal windows, dialog boxes, fields, and behaviors in Remote Web Console. Journal Operation window This window allows you to view details about journals and volumes. Information on the Journal Operation window will be updated when you do one of the following: Click Apply.
  • Page 152 “Resynchronize a mirror ” (page 62) “Delete pair volumes from a mirror ” (page 65) Item Description Tree Lists journals in the local storage system. The tree shows journals used with Continuous Access Journal, though not Continuous Access Journal Z. Journals: This item is located at the top of the tree.
  • Page 153 Item Description Journal/Mirror Status: Indicates the status of a mirror in the local storage system. (continued) Initial: A mirror in initial status. Journal volumes are registered in this journal, but no data volumes (P-VOLs or S-VOLs) are registered in this journal. If a Cnt Ac-J pair is created, data volumes are registered in a mirror and the status of the mirror changes to Active.

  • Page 154: Journal Detail Window

    Item Description Preview The Preview list shows changes that have been made in the window. When you change settings in the window, the changes appear in the Preview list before the changes are applied to storage systems. If you are sure that information in the Preview list is correct, click Apply to apply the settings that you have made.
  • Page 155 Item Description Journal (LDKC) The number of a journal and the LDKC number. The LDKC number is enclosed in the parentheses following the number of a journal, for example, 001 (00). A journal number ending in [&], indicates the journal is in a 2DC configuration, for example, 001 (00) [&]. Attribute The attribute of the journal.
  • Page 156 Item Description Journal Volumes A list of registered journal volumes. - Parity Group: indicates the parity group where a journal volume belongs. - LDKC:CU:LDEV: Indicates the LDKC number, the CU number and the LDEV number of a journal volume. - Capacity: The capacity of a journal volume in gigabytes. - Emulation: The emulation type of a journal volume.

  • Page 157: Change Journal Option Dialog Box

    Item Description Next Displays detailed information about the next journal. Close Closes the Journal Detail dialog box. Change Journal Option dialog box This dialog box lets you change the options that affect pairs in a journal. See “Change Continuous Access Journal options used by journals ” (page 83) for complete information.

  • Page 158: Edit Journal Volumes Dialog Box

    Item Description Unit of Path Watch Sets unit of time for Path Watch Time—minute, hour, or day. Time Path Watch Time Specify the interval from when a path gets blocked to when a mirror gets split (suspended). This value must be within the range of 1 to 59 minutes, 1 to 23 hours, or 1 to 30 days. You can specify a numeric value in Path Watch Time.
  • Page 159 Item Description Journal Volumes and Information about registered journal and free volumes, which are unregistered: Free Volumes Parity Group: Parity group where a journal volume belongs. LDKC:CU:LDEV: Journal volume’s LDKC number, CU number and LDEV number (# at the end indicates external volume). Capacity: Journal volume’s capacity in gigabytes.

  • Page 160: Pair Operation Window

    Pair Operation window This window lets you view the pairs for the selected port or host group. Information on the Pair Operation window will be updated when you do one of the following: Click Apply Select another tab and then reselect the Pair Operation tab. Update the Display Filter dialog box.
  • Page 161 Pair Operation Shows information about the volumes in the local storage system. One row represents one volume. By default, information in the list is arranged in order of port numbers. For volumes with more than one path, each path appears in a separate row. The maximum number of rows in the list is 2,048. If the number of volumes exceeds the number of rows, click Previous or Next to view information about volumes that do not appear in the list.
  • Page 162 Pair Operation HOLD: A pair for delta resync operation is created. (continued) HLDE: An error occurred with the pair for delta resync operation. HOLDING: The pair status is changing to HOLD while creating a delta resync pair. Suspending: The P-VOL and the S-VOL are not synchronized. This pair is in transition from the PAIR or COPY status to the PSUS/PSUE status Deleting: The P-VOL and the S-VOL are not synchronized.
  • Page 163 Pair Operation Pair JNL: The journal number for the remote storage system. This column is blank if the volume in the (continued) local storage system is neither a P-VOL nor a S-VOL. Err Lv.: The range of pair split on error. Mirror: If an error occurs with this pair, all the pairs in the mirror where this pair belongs will be split.

  • Page 164: Detailed Information Dialog Box

    Operation The operation that will occur when you click Apply. Paircreate: Create pairs. Pairsplit-r: Split pairs. Pairresync: Restore pairs. Pairsplit –S: Release pairs. Change Pair Option: Change pair option(s). Blank: Nothing will occur when you click Apply. Preview The number to the left of the slash (/) indicates the number of items appearing in the Preview list. The number to the right of the slash indicates the maximum number of items that can appear in the Preview list.
  • Page 165 Item Description Status Shows pair status. For status definitions, see “Pair status definitions” (page 67). If the pair is split (or suspended), Status also shows the suspend type. If the pair is waiting for initial copy, Status shows the word “Queuing”. A pair’s status varies between the P-VOL and S-VOL for short periods when the secondary system changes the pair’s status.
  • Page 166 Item Description P-VOL(Port-GID-LUN), Show information about the pair volume. S-V0L(Port-GID-LUN) The first line shows the port number, the GID, the LUN, and LDKC:CU:LDEV. GID is the group number for a host group. If the P-VOL or S-VOL is a LUSE volume, the LUN is the smallest LDEV number in the LUSE volume).

  • Page 167: Paircreate Dialog Box

    Item Description Previous/Next Clicking Previous shows the pair status information for the previous pair in the list (the pair in the row above). Clicking Next shows the pair status information for the next pair in the list (the pair in the row below). The list shows a maximum of 2,048 rows at once. The Previous and Next buttons on the Detailed Information dialog box can be used only for the currently shown 2,048 rows.
  • Page 168 Item Description P-VOL A primary data volume. The numbers indicate the port number, the GID, and the LUN of the primary data volume. The numbers in parentheses indicate the LDKC number, the CU number and the LDEV number. The GID is a group number for a host group. This column shows only one primary data volume even when two or more primary data volumes are selected in the Pair Operation window.
  • Page 169 Item Description Select a S-VOL. When specifying a S-VOL, you must use the three lists to select a port, a GID, and an LUN of the S-VOL. The GID is a group number for a host group. You can select only one S-VOL even when two or more primary data volumes are selected in the Pair Operation window.

  • Page 170: Pairsplit-R Dialog Box

    Item Description Priority Specify priority (scheduling order) of the initial copy operations (1 256). The default setting is If the time out error occurs during the Paircreate operation, the copy operation may not be executed correctly in the order that you have set with the Priority parameter. The time out error may be caused by the CU configuration or a remote copy path error.

  • Page 171: Pairresync Dialog Box

    Item Description S-VOL Write Specify whether to permit hosts to write data to the S-VOL. The default is Disable (that is, do not permit): Disable: Hosts cannot write data to the S-VOL while the pair is split. Enable: Hosts can write data to the S-VOL while the pair is split. This option is available only when the selected volume is a P-VOL.

  • Page 172: Pairsplit-S Dialog Box

    Item Description Range Specify the restore range. If two or more pairs in the same mirror are selected, the default is LU. If not, the default is Mirror. The default setting is Mirror when the pair status is HOLD, HOLDING, or HLDE, and in that case you cannot change the default setting. LU: Only the specified pair(s) is restored.

  • Page 173: Change Pair Option Dialog Box

    Item Description Range Specify the release range. The default is LU if two or more pairs in the same mirror are selected. The default is Mirror if not. Also, if the pair status is SMPL, Range is set to LU. If the pair status is Deleting or Suspending, Range is set to Mirror.

  • Page 174: Display Filter Dialog Box

    Item Description Error Level Sets whether to split one or all pairs in a mirror—options are LU and Mirror. Mirror: If a failure occurs with a pair, all pairs in the mirror where the pair belongs are split. LU: If a failure occurs with a pair, only the pair are split. Applies the settings to the Preview list in the Pair Operation window.

  • Page 175: Dkc Operation Window

    Item Description Applies the settings to the Preview list in the Pair Operation window. Cancel Discards the settings and closes the dialog box. DKC Operation window This window lets you view details about the remote storage systems, logical paths between systems, and ports on the local system.

  • Page 176: Remote Systems Information

    NOTE: DKC is an acronym for disk controller, which controls an entire storage system. Cnt Ac-J windows use the term "DKC" to indicate a storage system. LDKC is an acronym for logical disk controller, and it also may be called logical DKC. LDKC is a controller that controls a logical storage system that exists in P9500.

  • Page 177: Logical Path Information

    Item Description Tree Lists the remote storage systems of each LDKC in the local storage system. The following information appears to the right of the remote system’s icon : Controller ID of the remote storage system (The model name of the remote storage system). Serial number of the remote storage system.

  • Page 178: Port Information For The Local System

    Item Description Path Gr. ID The path group ID. The icon indicates the status of the path: The logical path is in normal status A failure occurred at the logical path. M-R Path The channel type of the logical paths between the local storage system and the remote storage system.

  • Page 179: Dkc Status Dialog Box

    Item Description Tree The channel adapters and ports on the local storage system. The following information appears to the right of the icon: Channel adapter (Fiber Channel interface) Target port RCU target port Initiator port External port Operation The ports on the local storage system: Port: Port number.
  • Page 180 Item Description Number of the row. Path Status 180 Continuous Access Journal GUI reference...

  • Page 181: Add Dkc Dialog Box

    Item Description Status of a logical path. Normal. The path is established and ready to use for copy operations. In Progress. An operation for configuring or deleting the path is in progress. Initialization Failed. An error occurred when the connection between local and remote systems was initializing.

  • Page 182: Dkc Option Dialog Box

    Item Description Remote system 5-digit serial number. LDKC Remote system LDKC number, 00 for XP24000/XP20000 Disk Array. Controller ID Remote system controller ID, 6 for P9500, 5 for XP24000/XP20000 Disk Array, 4 for XP12000 Disk Array/XP10000 Disk Array. Path Gr ID Field intended for a future release.

  • Page 183: Usage Monitor Window

    Item Description Minimum Paths Field intended for a future release. RIO MIH Time Amount of time the system waits before a data transfer operation is flagged as failed. The range is from 10 seconds to 100 seconds; 15 seconds is the default. Usage Monitor window This window lets you monitor remote copy operations data and I/O statistics.
  • Page 184 Use this window to export pair operations history. Item Description Status The current status of operation history: No history file exists: Operation history does not exist. Reading a history file failed: An attempt to read operation history failed. Updating ... n (%): Updating of operation history is now in progress, where "n (%)" indicates the progress (in %).

  • Page 185: Operations In History Window

    Item Description Previous/Next Shows a maximum of 16,384 operations at a time. If the number of operations exceeds 16,384, click Previous or Next to show the remaining operations. History The history of operations on pairs in the connected storage system. The list consists of the following columns: Operation Time: Date and time operation completed.
  • Page 186 Operation Displayed Description Status Change by MCU(COPY to PAIR) The status of the pair was changed from COPY to PAIR because of an operation from the primary storage system. Status Change by MCU(COPY to PSUS/PSUE) The status of the pair was changed from COPY to PSUS or PSUE because of an operation from the primary storage system.

  • Page 187: History Window Notes

    Operation Displayed Description Status Change by RCU(HOLD to SMPL; Pairsplit-S Start) An operation for releasing a pair has been started at the secondary storage system. The status of the pair will change from HOLD to SMPL. Status Change to HOLD The status of the S-VOL was changed to HOLD because of a delta resync operation.
  • Page 188 Click File > Refresh on the menu bar. Select Modify mode when you are in View mode. Item Description Tree Provides access to the storage system. Select Subsystem. Activities Storage system option settings. Preview When you change settings in the Optional Operation window, the Preview list shows the changes.

  • Page 189: Glossary

    Glossary Command-line interface. An interface comprised of various commands which are used to control operating system responses. CLPR cache logical partitions. Cnt Ac-J HP StorageWorks P9000 or XP Continuous Access Journal Software. Cnt Ac-J Z This is the version of Continuous Access Journal that supports mainframe volumes. See Cnt Ac-J for more information.
  • Page 190 port A physical connection that allows data to pass between a host and the disk array. The number of ports on a disk array depends on the number of supported I/O slots and the number of ports available per I/O adapter. The P9000 and XP family of disk arrays supports Fibre Channel (FC) ports as well as other port types.

  • Page 191: Index

    Index in 2DC config;, Symbols in 3DC cascade config, 2 data center configuration, disk arrays 3 DC cascade configuration, supported models, Display Item dialog, DKC Operation window adding logical paths, for defining port attributes, document conventions, basic operation, related information, business requirements, assessing, documentation HP website,...
  • Page 192 sizing, changing journal options, journals, changing mirror options, changing options, changing pair split option, deleting;deleting a journal, defining port attributes, description, deleting a journal, monitoring;monitoring:journals, deleting a journal volume, planning, deleting a pair, specifications, deleting pairs from a mirror, delta resync - create the pair, delta resync - perform the operation, latency, delta resync operation,...
  • Page 193 software overview, splitting a pair, status definitions journal, storage capacity values conventions, strategies for sizing bandwidth, Subscriber's Choice, HP, supervisor DKC, suspended journals, suspension types error related, switch connection, graphic, symbols in text, system option modes, planning, System requirements, target port, technical support service locator website, text symbols,...

Table of Contents