HP XP P9000 External Storage Access Manager User Guide Abstract This manual provides instructions and information for setting up, using, and maintaining External Storage Access Manager on the P9500 storage systems.
© Copyright 2011, 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 External Storage Access Manager overview...................................................7 How ESAM works.....................................................................................................................7 ESAM components....................................................................................................................8 P9500 storage systems.........................................................................................................
Workflow..........................................................................................................................24 Configuring the quorum disks...................................................................................................24 Prerequisites......................................................................................................................24 Procedure..........................................................................................................
Options for performing the planned outages.....................................................................46 The procedures for performing planned outages................................................................47 Performing planned outages (quorum disk only) ...............................................................47 Performing planned outages (primary storage system and quorum disk)................................48 Performing planned outages (secondary storage system and quorum disk)...
Configuring the system............................................................................................................69 Disaster recovery in a cluster system..........................................................................................69 Restrictions ............................................................................................................................70 8 Troubleshooting........................................................................................
1 External Storage Access Manager overview ESAM ensures high availability of host applications used in P9500 (P9500) storage systems. ESAM provides protection against the loss of application availability when input and output (I/O) failures occur in the primary storage system by automatically switching host applications from the primary storage system to the secondary storage system and by enabling recovery from the failures that caused the I/O failure.
ESAM components A typical configuration consists of two P9500 storage systems installed at the primary and secondary sites. In addition, the ESAM system consists of the following components: • ESAM and Continuous Access Synchronous software, which are installed on both systems. • A host server running a multipath software solution, qualified with ESAM software, that is connected to both storage systems.
Main and remote control units Like Continuous Access Synchronous, ESAM replication relationships exist at the Logical Control Unit (LCU) level within the storage systems. • Primary storage system LCUs containing the production volumes to be replicated are called MCUs (main control units). • Secondary storage system LCUs containing the copy volumes are called remote control units (RCUs). Normally the MCU contains the P-VOLs and the RCU contains the S-VOLs.
Remote Web Console GUI You perform ESAM tasks using the RWC graphical user interface. RWC is installed on a management computer. It communicates with the SVP of each storage system over defined TCP/IP connections. RAID Manager (RAID Manager) You can run commands using RAID Manager to perform pair tasks, which is installed on the host. You run commands from a command device on the host. Disaster recovery operations use a mix of RWC and RAID Manager.
2 System implementation planning and system requirements Understanding the system planning process and the various requirements of ESAM enables you to plan a system that functions properly and can be configured to meet your business needs over time. The workflow for planning External Storage Access Manager implementation The process for planning your ESAM implementation involves these two main tasks: • Plan and configure the volume pairs, data path configurations, bandwidth sizing, RAID configuration.
Multipath software A multipath software package qualified with ESAM is required on each host platform for failover support. Hitachi's multipath software, Dynamic Link Manager, supports the following host platforms: • AIX • Linux • Solaris • Windows. Requires host mode option 57 on the host group where Windows resides. • VMware. Requires host mode option 57 on the host group where VMware resides. Dynamic Link Manager manages I/O through a disk driver.
ESAM volumes that may be replicated. Review the Continuous Access Synchronous license installed on your system to verify that it meets your requirements. For example, when the license capacity for Continuous Access Synchronous is 10GB, the volume capacity that can be used for ESAM is up to 10GB. When 2GB out of 10GB of license capacity for Continuous Access Synchronous is used, the volume capacity that can be used for ESAM is up to the remaining 8GB.
Paircreate dialog box, the remaining S-VOLs will be assigned incrementally by LUN (for example, LUN002 and LUN003). - Make sure that all S-VOLs to be assigned automatically are available, are numbered in an order that will pair them properly, and that they correspond in size to the P-VOLs. - If an S-VOL is not available for a P-VOL, the pair must be created individually.
• Direct and switch connections are supported. • Use target ports in the primary and secondary storage systems to connect with the host Fibre Channel ports. Initiator ports cannot be used for host connections. For more information about port attributes, see the topic on configuring host interface ports in the HP XP P9000 Continuous Access Synchronous User Guide. • The following table shows maximum, minimum, and recommended number of data paths, logical paths, and ports for ESAM. Category Item Min.
When using external storage systems with ESAM, please observe the following: • Optional external storage systems may be used to store pair data. For supported external systems, see the HP XP P9000 External Storage for Open and Mainframe Systems User Guide. • You can connect one external system per ESAM P-VOL, and one per S-VOL. • The maximum number of external systems that can be connected depends on the number of the external ports that can be defined for a storage system.
It is possible that maintenance operations require both storage systems to be powered off at the same time. In this case, the health checking periods would be shortened to prevent unexpected failover while both systems are powered off. After failover, when a failure is corrected, you may continue operations on the S-VOL, though HP recommends switching them back to the P-VOL.
Table 2 Volume types that can be shared with ESAM volumes Product Volumes Used as ESAM P-VOL? Used as ESAM S-VOL? LUN Manager Volume where an LU path is defined Yes Yes Volume where no LU path is defined No No Volume where LUN security is applied Yes Yes Open Volume Management Customized Volume volume Yes Yes System disk No No LUN Expansion LUSE volume Yes Yes Volume Shredder N/A No No Thin Provisioning THP V-VOL (virtual volume) Yes Yes Pool volume No No External Storage
Cache Residency With Cache Residency, you can improve data access performance by storing the ESAM data in the storage system's cache memory. Performance Monitor • Performance Monitor is used to monitor usage or performance of the storage system. You can also show statistical I/O data of ESAM and Continuous Access Synchronous pairs. • When Performance Monitor data collection results in a large amount of data, significant traffic on the P9500 internal LAN can occur.
Configurations with Continuous Access Journal volumes You can use the ESAM S-VOL as a Continuous Access Journal (Cnt Ac-J) P-VOL. This configuration benefits the ESAM pair if data in the P-VOL and S-VOL become inconsistent due to a disaster. In this case, you can recover the data from the split Cnt Ac-J S-VOL. Configuring ESAM with Continuous Access Journal You perform this configuration by creating an ESAM pair and a Cnt Ac-J pair. 1. Create the ESAM pair. Make sure that the pair status becomes PAIR. 2.
3 System configuration The ESAM system configuration process is the first main task in the process of setting up the ESAM system. It follows the planning of the system implementation and is based on the outcome of the system implementation planning effort. All of the configuration procedures must be completed before you can begin using the system.
Prerequisites Before you begin, make sure you have: • Completed the system implementation (see “System implementation planning and system requirements ” (page 11)). The workflow for connecting the hardware components Use the following process to connect the hardware components for a ESAM system: 1. If you have external storage for storing pair data, connect the external systems to the external ports on the P9500 systems. 2.
Additional documentation To ensure that you use the correct steps to install the software, refer to the installation instructions in the following documentation during the installation process: • The documentation for the multipath software. • The HP XP P9000 Remote Web Console User Guide. • The HP XP P9000 RAID Manager Installation and Configuration User Guide.
• Details about mapping the primary and secondary storage systems to the external system that contains the in the HP XP P9000 Provisioning for Open Systems User Guide and HP XP P9000 External Storage for Open and Mainframe Systems User Guide. • Details about CLPR in the HP XP P9000 Cache Partition User Guide. • Details about external path groups in the HP XP P9000 External Storage for Open and Mainframe Systems User Guide.
- Number of LDEVs: 1. - Cache mode: This parameter is not used for quorum disks. Either Enable or Disable can be specified. - Inflow control: Select Disable. Data will be written in the cache memory. - CLPR: If you partition cache memory, specify the CLPR that the quorum disk uses. - LDKC:CU:LDEV number: The number is used to identify the quorum disk for the primary and secondary storage systems. 5.
8. 9. Verify your settings. To make a correction, select the setting, right-click, and click Modify. Click Apply to save your changes. Configuring host mode options Configuring host mode options is the last main task in the system configuration. Completion of this task ensures that the host mode option setting are correct. The settings vary depending on the whether the system is a standard or cluster implementation.
4 Working with volume pairs A number of tasks must be performed on volume pairs as part of your normal ESAM system maintenance activities, when troubleshooting system issues, or when taking action to recover from failure. Workflow for ESAM volume pairs You perform several different types of tasks with volume pairs as part of your system maintenance and recovery activities. The different types of tasks include: • Checking pair status. • Creating pairs. • Releasing pairs. • Resynchronizing pairs.
1. 2. 3. 4. 5. 6. 7. 8. 9. When a volume is not in an ESAM pair, its status is SMPL. When you create an ESAM pair using SMPL volumes, the status of the P-VOL and the S-VOL changes to COPY while the system copies the data. A stable synchronized pair has the status PAIR. When you split a pair, the status of the P-VOL and the S-VOL changes to PSUS (pair suspended-split, split by command).
Where to find the information You can view all information about pairs in the GUI. If you configured the system to send email notifications, you can monitor those particular events remotely. When a pair is in PSUS, SSWS, or PSUE status, the primary storage system generates SIMs (service information messages). You can check SIMs in RWC’s Alerts window. How hosts see volume pairs When you create an ESAM pair, the host sees the primary and secondary volumes as the same volume.
Pair status values When checking pair status in RWC, click File/Refresh to verify that the data is current. In RWC, the pair status is shown in the [pair status in Remote Web Console/pair status in RAID Manager] format. If the pair status name in RWC and the pair status name in RAID Manager are the same, the pair status name in RAID Manager is not shown. The following table lists ESAM pair status and whether the volumes can be accessed.
Pair Status VOL Access Description Access to -PVOL S-VOL P-VOL S-VOL Blank Blank Blank Access (Lock) Blank Access (Lock) The ESAM pair is not synchronized Not because a failover has occurred. The accessible data on S-VOL is the latest. Read/write Blank Blank The user has performed a swap and Not suspend operation (pairsplit-RS). Data accessible on S-VOL may be old.
The following table describes pair status in RAID Manager. Item Description SMPL The volume is not assigned to an ESAM pair. COPY The initial copy for an ESAM pair is in progress, but the pair is not synchronized yet. PAIR The initial copy for an ESAM pair is completed, and the pair is synchronized. PSUS Although the paired status is retained, the user split the ESAM pair, and update of S-VOL is stopped. This status only applies to SVOL.
The primary storage system suspends a pair when the following conditions occur: • The user has released the pair from the secondary storage system. • An error condition related to the secondary storage system, the S-VOL, or the update copy operation. • Communications with the secondary storage system have stopped. When a pair is suspended, the primary storage system stops sending updates to the S-VOL, even though host applications may continue updating the P-VOL.
• The initial copy parameters you specify during the procedure cannot be successfully changed after a pair is created. If you attempt to change or delete them, the Pair Operation window and Detailed Information dialog box shows misleading and inaccurate information. • If you are creating multiple pairs in one operation, all pairs are assigned the same parameters and the same quorum disk ID. Access the MCU in RWC, then click Actions > Remote Copy >Continuous Access Synchronous > Pair Operation.
number, such as 15, copying is faster, but I/O performance of the storage system may decrease. If you specify a small number, such as 3, copying is slower, but the impact on I/O performance is lessened. 10. From the Priority drop-down menu, select the scheduling order for the initial copy operations. You can enter between 1-256. The highest priority is 1, the lowest priority is 256. The default is 32.
How multipath software shows storage serial number for pairs How multipath software shows storage serial number for pairs Multipath software shows the serial number of the primary storage system for both the P-VOL and the S-VOL. However, the storage system model shown for both P-VOL and S-VOL is the earliest model used in your configuration, regardless of its location, primary or secondary site.
track of updates while the pair is split. Choose this setting if the P-VOL is required for system operation and you need to keep the P-VOL online while the pair is split. 6. 7. 8. Click Set. The settings are shown in the Preview area. In the Preview list, check the settings. To change a setting, right-click and select Modify. When satisfied, click Apply.
Reverse resynchronization After a failover, when the S-VOL is receiving updates from the host instead of the P-VOL, you can resynchronize the P-VOL with the S-VOL by running the RAID Manager pairresync-swaps command. Copy direction is from S-VOL-to-P-VOL. The P-VOL and S-VOL are swapped in this operation: the secondary storage system S-VOL becomes the P-VOL; the primary storage system P-VOL becomes the S-VOL. The pairresync -swaps command is the only supported method for reverse resynchronizing ESAM pairs.
operation, it detects that S-VOL status as SMPL and changes P-VOL status to PSUS. The suspend type is Delete pair to RCU. TIP: Best Practice: Release a pair from the P-VOL. If the pair has a failure and cannot be released from the P-VOL, then release it from the S-VOL. 1. 2. 3. 4. 5. 6. 7. Verify that the P-VOL has the latest data using one of the following methods: • On the secondary storage system, open the Pair Operation window.
Requirements Make sure that the following requirements are met to ensure the pair can be changed correctly without errors or failures: • ESAM system requirements must be met. • The microcode version of the primary and secondary storage systems must be DKCMAIN 70-01-62-XX/XX or later. • A quorum disk ID must be registered. • The Continuous Access Synchronous pair must not be registered to a consistency group.
Comparison of the RAID Manager commands and Remote Web Console You can perform many ESAM pair tasks using the RAID Manager. The following list compares RAID Manager commands and RWC functionality for operations that can be performed on ESAM pairs: • Though the host recognizes the ESAM volumes as a single volume, RAID Manager views the P-VOL and S-VOL as separate volumes. • RAID Manager shows the ESAM pair, the Continuous Access Synchronous pair, and the UR pair, according to the following table.
Type of task Task RAID Manager command RWC window or dialog box Delete the quorum disk ID. N/A Delete Quorum Disk ID button Note the following: • You cannot run the pairresync command on a pair when the storage system cannot access the quorum disk due to a failure. • To resynchronize an ESAM pair, the fence level must be Never. • After you run the pairsplit -RS command, the write command to the P-VOL will fail.
5 System maintenance To ensure that the ESAM system function properly and is able to provide robust and reliable high-availability protection for host applications, it is essential for you to be able to perform ESAM system maintenance tasks. Applications used to perform maintenance tasks All of the typical maintenance tasks can be completed using RWC or RAID Manager. Required Remote Web Console settings You must be in Modify Mode in RWC.
NOTE: During the procedure, you must delete the external volume mapping of the quorum disk. If the ESAM pair is still connected to the disk, you cannot delete the mapping. To ensure you can delete the mapping, before you delete the mapping, make sure you disconnect the quorum disk by running the Disconnect External Volumes command. 1. 2. 3. Using multipath software, vary the non-owner path to offline. Release all ESAM pairs from the primary storage system.
3. 4. In the quorum ID list, right-click the quorum disk ID that you want to delete, then click Delete Quorum Disk ID. Confirm the operation in the Preview list, then click Apply. If the quorum disk ID cannot be deleted, a failure might have occurred in the quorum disk. Do one of the following: • Recover from the failure, then try to delete the ID again using this procedure. • Forcibly delete the quorum disk (see “Deleting quorum disk IDs by system attribute (forced deletion)” (page 45)).
4. 5. 6. On the primary and secondary storage system, add the quorum disk ID. On the primary storage system, create the ESAM pair. On both the primary and secondary storage systems, make sure that Type shows ESAM. Recovering the disk when the S-VOL was receiving host I/O at deletion Use this procedure to recovery a disk that was accidentally deleted when the secondary volume was receiving host I/O at the time of deletion. 1. Stop the I/O from the host. 2.
You can use a single procedure to perform a planned outage on: • A quorum disk • A primary storage system and the quorum disk connected to it • A secondary storage system and the quorum disk connected to it • A primary and secondary storage system and the disk connected to them The procedures for performing planned outages The following procedures contain all of the steps required to perform a planned outage. Use the procedure that fits the requirements for the planned outage.
Performing outages when the S-VOL is receiving host I/O Use this procedure when the S-VOL is receiving host I/O updates. If you also need to power off and on the primary or secondary storage system connected to the disk, use one of the other procedures (see “The procedures for performing planned outages” (page 47)). 1. On the secondary storage system, split the pair. 2. On the secondary storage system, make sure the P-VOL is in PSUS status. 3.
9. On the secondary storage system, complete the following: 1. Run the following External Storage command on the quorum disk: Reconnect External Volumes 2. Run the following command on the S-VOL: pairresync -swaps 3. Make sure that P-VOL and S-VOL status is PAIR. 10. Using the multipath software, complete the following: 1. Vary the owner path online. 2. Vary the non-owner path offline. 11. On the primary storage system, make sure that S-VOL status (original P-VOL) is SSWS. 12.
8. Using multipath software, vary the non-owner path online. Performing planned outages (both storage systems and quorum disk) Use this procedure to perform a planned outage of the primary storage system, the secondary storage system, and the disk connected the systems. 1. On the primary storage system, complete the following: 1. Split the pair. 2. Make sure that P-VOL status is PSUS. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Stop host I/O. Using multipath software, vary the non-owner path offline.
6 Disaster recovery On-site disasters, such as power supply failures, can disrupt the normal operation of your ESAM system. Being able to quickly identify the type of failure and recover the affected system or component helps to ensure that you can restore high-availability protection for host applications as soon as possible.
NOTE: You need to determine the type of failure before you can determine which recovery procedure to use. For more information, see “Using system messages to check for failures”.
Determining which basic recovery procedures to use Determining which basic recovery procedures to use involves analyzing the information in the system information messages (SIM) and path failure system messages to identify the type of failure, then selecting the correct procedure based on the type of failure.
Recovery from blocked pair volumes In most cases, a blocked volume pair results in automatic failover. This helps to ensure that host I/O continues and host applications remain available. The process used to recover pair volumes from this failure varies depending on: • Whether the volume is a primary or secondary volume. • Whether the volume is in the primary or secondary storage system.
3. 4. 5. 6. On the primary storage system, run the Pairsplit-S RAID Manager command on the P-VOL to release the ESAM pair. Clear the failure in the primary storage system P-VOL. On the secondary storage system, create a Continuous Access Synchronous pair from the original S-VOL to the P-VOL. Data flow is from the secondary to primary storage systems. Continue by either changing the Continuous Access Synchronous pair to a ESAM pair (below) or recreating the ESAM pair (next steps).
5. 6. 7. On the primary storage system, make sure that no other failures exist and that it is ready to accept host I/O. On the secondary storage system, create a Continuous Access Synchronous pair from the original S-VOL to the P-VOL. The data flow is from the secondary to primary storage system. Continue by changing the Continuous Access Synchronous pair to a ESAM pair (below) or recreating the ESAM pair (next step).
Recovering from secondary volume failure on the RCU When this failure occurs, automatic system failover switches host I/O to the primary volume on the RCU. Recovering the volume from this failure involves releasing the pair, clearing the failure, recreating the pair, and restarting host I/O. Unlike the other types of pair volume failures, host I/O is not interrupted and failover does not occur.
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. Use the multipath software to vary the non-owner path offline. On the primary storage system, release the pair by running the pairsplit-S RAID Manager command on the P-VOL. On the primary storage system, make sure that P-VOL status is SMPL. On the primary storage system, delete the quorum disk ID. If a failure in the quorum disk prevents deletion, forcibly delete it. On the secondary storage system, delete the quorum disk ID.
6. On the primary storage system, delete the quorum disk ID. If the quorum disk ID cannot be deleted due to a disk failure, forcibly delete the quorum disk. 7. 8. On the secondary storage system, delete the quorum disk ID. On both systems, run the Disconnect External Volumes command on the quorum disk. If the connection to the quorum disk cannot be released due to the failure of the quorum disk, skip the Disconnect External Volumes operation. 9. 10. 11. 12. Replace the quorum disk.
1. 2. 3. 4. 5. 6. 7. 8. Verify that the S-VOL has the latest data and is being updated. Open the Pair Operation window on the secondary storage system and check that the VOL Access column shows Access (Lock). Stop I/O from the host. On the secondary storage system, release the ESAM pair. On the secondary storage system, delete the quorum disk ID. On the secondary storage system, create a Continuous Access Synchronous pair. The data flow is from secondary to primary sites. Format the quorum disk.
5. On the primary storage system, register the ESAM secondary storage system to the primary storage system. 6. On the primary and secondary storage systems, add the quorum disk. 7. On the primary storage system, create the ESAM pair. 8. On both the primary and secondary storage systems, make sure that Type shows ESAM. 9. Vary the owner and non-owner paths online using the multipath software. 10. Restart host I/O.
3. 4. 5. 6. 7. On the primary storage system, delete the quorum disk ID. On the secondary storage system, register the ESAM primary storage system to the secondary storage system. On the secondary storage system, create a Continuous Access Synchronous pair. The data flow is from secondary to primary sites. Format the quorum disk. Continue by changing the Continuous Access Synchronous pair to a ESAM pair (below) or recreating the ESAM pair (next steps).
You select the procedure to use based on a number of factors, including the continuation of host I/O, failover, and the status of the secondary volume. Prerequisites Make sure you have identified the type of failure that occurred by using the system information messages (SIM) and path failure system messages. For more information, see “Using system messages to check for failures”. NOTE: 1. 2. 3. The procedures for RAID Manager and RWC are the same.
4. 5. If a pair is shared by multiple hosts with VMWare, see important recovery information regarding the horctakeover or pairresync –swaps command in “Recovery for pairs shared by multiple hosts with VMware” (page 66). If a pair is shared by multiple hosts with VMWare, see important recovery information regarding failover in “Recovery for pairs shared by multiple hosts with VMware” (page 66). Procedure 1. 2.
Journal pair after you resynchronize the ESAM P-VOL that accepts host I/O or after you resynchronize the pair in the opposite direction. Prerequisites Make sure you have analyzed the failure messages to determine if all of the conditions required to use resynchronization exist. For more information, see “Determining which resynchronization recovery procedure to use” (page 62). Procedure 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. Using multipath software, vary the owner path offline.
The following table lists whether failover or failback will occur based on the order in which you restore the paths (owner path first or non-owner path first). Volume receiving host I/O Order for restoring paths Will failover or failback occur? Primary system P-VOL 1. Owner path No. 2. Non-owner path 1. Non-Owner path 2. Owner path Secondary system P-VOL 1. Owner path (original S-VOL) 2. Non-owner path 1.
4. 5. Reboot hosts that were shut down in the Step 2. Return the guest OSs that were moved in the Step 1 to the original hosts. Procedure 2 When using Hitachi Dynamic Link Manager v. 7.6.0 or later 1. 2. 3. Change the status of all HDLM owner paths accessing the pair to Online(D). Change Online(D) status to the Online status. Some paths may have changed from Online(D) to Online automatically. If non-owner paths status has changed to Offline(E), change the status to Online.
7 Using ESAM in a cluster system There are specific software and configuration requirements for using ESAM in a cluster system. Cluster system architecture The following diagram shows the architecture of a typical implementation of a cluster system. You connect an executing node and a standby node to MCU and RCU so that the nodes can access both MCU and RCU. A heartbeat network must be set up between the nodes.
Configuration requirements To ensure that ESAM functions properly, make sure that: • Both the MCU and RCU are be P9500s. • The same version of Hitachi Dynamic Link Manager are used in the MCU and RCU. • If using MSFC, specify Node and File Share Majority in Quorum Mode. • If using MSFC, use only basic disks. • If using PowerHA (HACMP), use enhanced concurrent volume groups. Configuring the system Use the following workflow for setting up and creating an ESAM pair.
Restrictions The following restrictions apply when using ESAM in a cluster system: • You cannot use ESAM pair volumes for SAN boot. • You cannot store OS page files in ESAM pair volumes. • For Windows Server® 2008 R2, ESAM does not support Hyper-V function and Cluster Shared Volumes (CSV) function.
8 Troubleshooting ESAM is designed to provide you with error messages so that you can quickly and easily identify the cause of the error and take corrective action. Many types of errors you encounter can be resolved by using fairly simple troubleshooting procedures.
The following table lists the general errors that can occur and the corrective action to take for each error. Error Corrective action The RWC computer hangs, or ESAM does • Make sure that the problem is not being caused by the RWC computer not function properly. or Ethernet hardware or software. Restart the RWC computer—this does not affect storage system operations. • Make sure that ESAM requirements and restrictions are met.
Suspended volume pair troubleshooting A suspended volume pair is a pair in which normal data replication is not occurring between the primary and secondary volumes. Until the failure or condition that caused the suspension is resolved, production data on the primary volume is not copied to the secondary volume.
Suspend type VOL Type Error Corrective action resynchronize the pair from the MCU (Pairresync). • Because of the quorum disk failure, the multipath software will show that the S-VOL is offline. Resynchronize the pair as described above, and then make the path to the S-VOL online with the multipath software. PSUE, P-VOL S-VOL Failure S-VOL The settings for host mode option 52 differ between ports on the primary and secondary storage systems.
The following table lists the codes for the errors that can occur when using RAID Manager and the steps involved in troubleshooting the errors. Error code Error code Description (SSB1) (SSB2) 2E31 9100 You cannot run the command because the user was not authenticated. B90A B901 An ESAM pair cannot be created or resynchronized because ESAM does not support the option, or the command cannot be accepted in the current pair status.
Related topics For more information about troubleshooting other types of errors, see the HP XP P9000 Continuous Access Synchronous User Guide. Recovery of data stored only in cache memory When a hardware failure occurs while the storage system is running, data in cache memory may not be written to data drives. In this case, the data stored only in cache memory is referred to as a pinned track. Pinned tracks can occur on volume pair drives and on quorum disks. You can recover pinned tracks.
9 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
HP websites For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/service_locator • http://www.hp.com/support/manuals • http://www.hp.com/support/downloads • http://www.hp.
Table 3 Document conventions (continued) Convention Element Monospace text • File and directory names • System output • Code • Commands, their arguments, and argument values Monospace, italic text • Code variables • Command variables Monospace, bold text WARNING! CAUTION: IMPORTANT: NOTE: TIP: Emphasized monospace text Indicates that failure to follow directions could result in bodily harm or death. Indicates that failure to follow directions could result in damage to equipment or data.
A Conventions This appendix describes phrases in this manual that correspond to phrases in the Remote Web Console windows and messages. Business Copy and Snapshot volumes Business Copy and Snapshot volumes displayed in the Remote Web Console windows and messages differ between Remote Web Console main windows and secondary windows. The differences are shown below.
B ESAM GUI reference This topic describes ESAM windows, dialog boxes, items, and behaviors in RWC. In addition, information related to ESAM systems also shown in the following windows and is documented in the HP XP P9000 Continuous Access Synchronous User Guide: - The RCU Operation window - The Usage Monitor window - The History window - The System Option window - The Quorum Disk Operation window Pair Operation window Use this window to view ESAM and Continuous Access Synchronous pairs.
Item Description Tree Shows the connected storage system, the LDKC, the CU grouping, the CUs, ports, and host groups. Select the desired CU grouping, CU( ), port ( ), or host group ( Only one CU grouping, CU, port, or host group can be selected. List ) to shows related LUs. Shows detailed pair information about the local storage system. To sort the items that are shown in ascending/descending order, click the column heading.
Item Description Navigator and the pair status name in RAID Manager are the same, the pair status name in RAID Manager is not shown. For more information, see the table of “Pair status values” (page 30). S/N(LDKC) Serial number of the paired storage system. ID SSID of the paired storage system, or Path group ID that you entered when registering the RCU.
P-VOL status1 S-VOL status1 VOL access of P-VOL VOL access of S-VOL Online volume PAIR Access (Lock) Blank P-VOL SSWS Access (No Lock) Blank Any2 Access (Lock) Blank Any2 Access (No Lock) Blank Any2 Access (Lock) Blank Any2 Access (Lock) Blank P-VOL PSUS PDUB PDUB 1. Remote Web Console pair statuses are shown in the format, RWC status/RAID Manager status. If the two statuses are the same, the RAID Manager status is not shown.
Item Description P-VOL and S-VOL • Port - GID – LUN(LDKC number: CU number: LDEV number). The following symbols might appear at the end of the LDEV number: - # (e.g., 00:00:3C #): Indicates the volume is an external volume. For more information about external volumes, see the HP XP P9000 External Storage for Open and Mainframe Systems User Guide. - X (e.g., 00:00:3C X): Indicates the volume is a Thin Provisioning virtual volume.
Item Description 1. MCU receives a request to create a pair. 2. MCU receives a request to start the paircreate operation. 3. The paircreate operation is started according to the conditions of initial copy priority and maximum initial copy activities. 4. The paircreate operation is completed (the progress of the operation reaches 100%). Difference Management The unit of measurement used for storing differential data. Values: Cylinder or Track Quorum Disk ID The quorum disk ID assigned to the ESAM pair.
Item Description P-VOL Shows the port number, host group number (GID), LUN(LDKC number: CU number: LDEV number), CLPR number, and CLPR name of the selected LU. This item shows the P-VOL with the lowest LUN when you create multiple pairs at a time. The following symbols might appear at the end of the LDEV number: • # (e.g., 00:00:3C #): Indicates the volume is an external volume. For more information about external volumes, see the HP XP P9000 External Storage for Open and Mainframe Systems User Guide.
Item Description ESAM Parameters Quorum Disk ID The quorum disk ID to be assigned to the ESAM pairs. The list shows the quorum disk ID and the RCU information such as the serial number, controller ID, and model name. Pairsplit-r dialog box Use this dialog box to split a pair. For instructions, see “Splitting pairs ” (page 36). Item Description Volume Port - GID – LUN (LDKC number: CU number: LDEV number) of the selected volume.
Item Description P-VOL Port - GID – LUN (LDKC number: CU number: LDEV number) of the selected volume. The following symbols might appear at the end of the LDEV number: • # (e.g., 00:00:3C #): Indicates the volume is an external volume. For more information about external volumes, see the HP XP P9000 External Storage for Open and Mainframe Systems User Guide. • X (e.g., 00:00:3C X): Indicates the volume is a Thin Provisioning virtual volume.
Item Description Volume Port - GID – LUN (LDKC number: CU number: LDEV number) of the selected volume. The following symbols might appear at the end of the LDEV number: • # (e.g., 00:00:3C #): Indicates the volume is an external volume. For more information about external volumes, see the HP XP P9000 External Storage for Open and Mainframe Systems User Guide. • X (e.g., 00:00:3C X): Indicates the volume is a Thin Provisioning virtual volume.
Item Description Tree Shows the connected Storage System, LDKC, and Used and Not Used. • When Storage System or LDKC is selected, the associated quorum disk IDs show in the list area. • When Used or Not Used is selected, the used and unused quorum disk IDs in the system is shown in the list area. List The quorum disk ID list shows quorum disk information. You can sort the list by column in ascending or descending order. The list contains the following items: • Quorum Disk ID: Quorum disk ID.
Item Description Quorum Disk Where the external volume to be used as a quorum disk is selected. RCU Where the paired CU is selected. The list shows the RCU information registered in CU Free. Multiple RCUs with the same serial number and controller ID, but different path group IDs, appear as one RCU.
Glossary BC P9000 or XP Business Copy. An HP application that provides volume-level, point-in-time copies in the disk array. CLPR Cache logical partition. Cnt Ac-J P9000 or XP Continuous Access Journal software. Cnt Ac-S P9000 or XP Continuous Access Synchronous software. command device A volume in the disk array that accepts Continuous Access, Business Copy, or P9000 for Business Continuity Manager control operations, which are then executed by the array. CTGID Consistency group ID.
path A path is created by associating a port, a target, and a LUN ID with one or more LDEVs. Also known as a LUN. 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 and other port types. Ports are named by port group and port letter, such as CL1-A.
Index A Add Quorum Disk dialog box, 91 B Business Copy and ESAM, 19 C Cache Partition Manager, sharing volumes with, 18 capacity, 12 changing Continuous Access Synchronous pair to ESAM, 39 components, 8 configuration hardware order, 21 P9500, 23 quorum disk, 24 software order, 22 with Business Copy, 19 with Continuous Access Journal, 20 with ShadowImage, 19 with Universal Replicator, 20 contacting HP, 77 Continuous Access Journal and ESAM, 20 Continuous Access Synchronous, changing pair to ESAM, 39 conven
Paircreate(ESAM) dialog box, 86 pairs create, 33 max.
