HP StorageWorks XP24000 Auto LUN Software User's Guide Part number: T5215–96001 First edition: June 2007
Legal and notice information © Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . Related Documentation . . . . . . . . Document Conventions . . . . . . . . Conventions for Storage Capacity Values Window Illustrations . . . . . . . . . HP Technical Support . . . . . . . . . Subscription Service . . . . . . . . . HP Websites . . . . . . . . . . . . Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling HP Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 A Acronyms and Abbreviations . . . . . . . . . . . . . . . . . . . . 51 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 1 ..Performance Management Process Flow Diagram . . . . . . . . . . . . . . . . . . 10 2 ..An Example of Migration Plans Displayed in the Auto LUN Window . . . . . . . . . . 12 3 ..Usage Rate for a Volume Displayed in the Window . . . . . . . . . . . . . . . . . 12 4 ..Classes and Parity Groups that Appear in the Auto LUN Window . . . . . . . . . . . 13 5 ..Parity Group Usage Displayed in the Auto LUN Window . . . . . . . . . . . . . . . 13 6 ..Estimated Usage Rate for Parity Groups . . .
Tables 1 2 3 4 ..Document Conventions . . . . . . . . . . . . . . . . . . . . . ..Non-Cascade Volumes and Auto LUN Source Volumes . . . . . . . ..Cascade Volumes and Auto LUN Source Volumes . . . . . . . . . . ..The capacity of migrated volume and the estimated delay in the copying 5 ..The Number of the Control Cylinders According to the Emulation Types 6 ..The Total Number of the Differential Tables Per Migration Plan . . . . . . . . . . . . . . . . . . 7 . 17 . 17 . 20 . . . . . . . . 22 . . . .
About this Guide This user's guide describes and provides instructions for using the Auto LUN software. The term storage system in this guide refers to an HP StorageWorks XP24000 Disk Array.
• 1 TB (terabyte) = 1,0004 bytes HP XP storage systems use the following values to calculate logical storage capacity values (logical devices): • • • • • 1 1 1 1 1 KB (kilobyte) = 1,024 bytes MB (megabyte) = 1,0242 bytes GB (gigabyte) = 1,0243 bytes TB (terabyte) = 1,0244 bytes block = 512 bytes Window Illustrations The windows shown in this guide were displayed on a Windows computer with the Internet Explorer browser.
1 Overview of HP StorageWorks XP Auto LUN Software Auto LUN lets you balance workload among hard disk drives, volumes (LUs) and processors to remove bottlenecks from your system. If Performance Monitor indicates that a large number of I/Os are made to some hard disk drives, you can use Auto LUN to distribute workloads to other disk drives. For details, see “Overview of Auto LUN” on page 11. Figure 1 on page 10 illustrates and simplifies the performance management process.
Figure 1 Performance Management Process Flow Diagram 10 Overview of HP StorageWorks XP Auto LUN Software
2 About Auto LUN Operations Components To use Auto LUN, you need: • the storage system • the Auto LUN program product (Performance Monitor is required.) • a WWW client computer connected to the storage system via LAN To use Auto LUN, you must use the WWW client computer to log on to the SVP. When you are logged on, the HP StorageWorks XP Remote Web Console program, which is a Java application program, will be downloaded to the WWW client computer.
group or volume usage varies only slightly, or for cases in which overall DKP or DRR usage is relatively high. • From an open-system host, users can also use HP StorageWorks XP RAID Manager to perform manual volume migration by using commands. To perform volume migration by RAID Manager, Auto LUN should be installed on the storage system. For details on manual volume migration by using RAID Manager, see “Using RAID Manager for Manual Volume Migration” on page 45.
To find fast hard disk drives, display the Auto LUN window and check classes (Figure 4 on page 13). Classes indicate disk access speed for parity groups. Fastest parity groups (or groups of fastest disks) belong to class A. Parity groups in class B are not as fast as parity groups in class A, but are faster than parity groups in class C. Parity groups in higher classes (such as class A) provide faster disk access than parity groups in lower classes (such as class C).
Notes: When you use Auto LUN for the first time, you must reserve volumes for migration destinations icon. When you specify a volume in advance. These reserved volumes are marked with the to be migrated, icons of some reserved volumes ( ) that can be used as a migration destination icons. For details on reserving volumes for migration destinations, see will change to the “Reserving Migration Destinations For Volumes” on page 41.
The Auto LUN operation consists of two steps: • Copy the data on the Auto LUN source volume to the Auto LUN target volume (see Figure 7 on page 15). • Transfer host access to the target volume to complete the migration (see Figure 8 on page 16). The Auto LUN source volume can be online to hosts during migration. The target volume is reserved prior to migration to prevent host access during migration. The source and target volumes can be located anywhere within the storage system.
Hosts can access device. Hosts cannot access device. LDEV ID = 0x123 LDEV ID = 0x321 Old Target Volume Old Source Volume Reserved Figure 8 Data Flow after an Auto LUN Operation Note: Immediately after a volume to be migrated and a volume of a migration destination replace each other, RAID level before the replacement might be displayed or an internal error might occur in the storage system. In this case, select the Refresh button to update the display of the window.
TrueCopy for Mainframe: If the status of a TrueCopy for Mainframe volume is suspended or simplex, the volume can be used as a source volume. If not, the volume cannot be used as a source volume. When a TrueCopy for Mainframe volume is deleted from the MCU, the status of both volumes changes to simplex, and both volumes can be used as source volumes.
• TrueCopy for Mainframe operation that changes the volume status to something other than suspended or simplex. • Continuous Access operation that changes the volume status to something other than PSUS, PSUE, or SMPL. • Continuous Access Journal operation or Universal Replicator for Mainframe operation that changes the volume status to COPY. • ShadowImage for Mainframe operation that changes the volume status to SP-Pend or V-Split.
• • • • can be executed concurrently changes depending on the number of differential tables that Auto LUN can use, and depending on the emulation types and sizes of volumes to be migrated. For details on how to calculate the number of migration plans that can be executed concurrently, see “How to Calculate the Number of Concurrent Migration Plans” on page 20.
• ShadowImage for Mainframe • Compatible FlashCopy Table 4 The capacity of migrated volume and the estimated delay in the copying speed Capacity of Migrated Volume (MB) Estimated delay in the copying speed (in minutes) 0 - 1,000 4 1,001 - 5,000 18 5,001 - 10,000 37 10,001 - 50,000 186 50,001 - 100,000 372 100,001 - 500,000 1,860 500,001 - 1,000,000 3,720 1,000,001 - 2,150,400 9,667 The above estimates are calculated based on the assumption that the workload for update I/Os for the migrated
of differential tables and pair tables needed for migrating a mainframe volume, see “Calculating Differential Tables Required for Mainframe Volume Migration” on page 21. For the number of differential tables needed for migrating an open-system volume, see “Calculating Differential Tables Required for Open-System Volume Migration” on page 22.
The following table shows the number of the control cylinders according to the emulation types.
Table 6 The Total Number of the Differential Tables Per Migration Plan Emulation Type OPEN-3 OPEN-8 OPEN-9 OPEN-E OPEN-L Expression Total number of the differential tables per migration plan = ((X) ÷ 48 + (Y) × 15) ÷ (Z) (X): The capacity of the volume to be migrated. (kilobyte)* (Y): The number of the control cylinders. (See Table 7 on page 24) (Z): The number of the slots that can be managed by a differential table. (20,448) Note that you should round up the number to the nearest whole number.
Table 7 The Number of the Control Cylinders According to the Emulation Types Emulation Type Number of the Control Cylinders OPEN-3 OPEN-8 OPEN-9 24 8 (5,760KB) 27 (19,440KB) OPEN-E 19 (13,680KB) OPEN-L 7 (5,040KB) OPEN-V 0 (0KB) About Auto LUN Operations
3 Preparing for Auto LUN Operations System Requirements To use Auto LUN, you need: • Storage system • Auto LUN software (Performance Monitor is required) • A Web client computer (intended for use as a Remote Web Console) connected to storage system via LAN. To use Auto LUN, you use the Web client computer to log on to the SVP (web server). When you are logged on, the Remote Web Console program, which is a Java application program, will be downloaded to the web client computer.
Preparing for Auto LUN Operations
4 Using the Auto LUN GUI Using the Auto LUN Windows Auto LUN can be used to balance workloads among hard disk drives and thus remove bottlenecks from the system. Auto LUN can migrate volumes from the current parity group to another parity group. Volume migrations can be performed manually (by the system administrator) or automatically by Auto LUN. In addition, Auto LUN can also migrate external volumes in external volume groups.
Figure 13 The Manual Plan Window of the Auto LUN The Manual Plan window displays the following: • Monitoring Term: Displays the monitoring period specified in the Performance Management window. Auto LUN analyzes disk usage information collected by Performance Monitor, Performance Control, or Auto LUN during the monitoring period, and then calculates estimated usage rates of the source and target parity groups after a proposed volume migration.
• indicates a RAID-6 parity group. The HDD class for this parity group is C. • indicates a RAID-6 parity group. The HDD class for this parity group is D. c d e cThe parity group ID. The number before the hyphen is the frame number. The number after the hyphen is the parity group number. dThe number before the slash is the average usage rate. The number after the slash is the maximum usage rate.
LDEV indicates the status of the volume. The number on the left of the first colon (:) from the left is the LDKC number. The number on the left of the second colon (:) from the left is the CU image number. The number on the right of the second colon is the LDEV number An icon showing the status of the volume is displayed on the left of the ID. Emulation Indicates the emulation type of the volume (LVI or LUN). Capacity Indicates the capacity of the volume. Ave.
LDEV Indicates the volume ID. The number on the left of the first colon (:) from the left is the LDKC number. The number on the left of the second colon (:) from the left is the CU image number. The number on the right of the second colon is the LDEV number. An icon showing the status of the volume is displayed on the left of the ID. Emulation Indicates the emulation type of the volume (LVI or LUN). Capacity Indicates the capacity of the volume. Ave.
• An estimated usage rate for the parity group after a proposed volume migration. If you specify an external volume as a source volume, Auto LUN cannot calculate the estimated usage rate after migration. In this case, a hyphen (-) appears instead of a value. • Target (Reserved) LDEV lets you specify the target volume (that is, the location to which you want to migrate the source volume).
• RAID indicates the RAID type. • PG indicates the parity group ID or the external volume group ID. The number before the hyphen (-) is the frame number. The number after the hyphen is the group number. • HDD indicates the type of the hard disk drive. • CLPR indicates the number and name of the CLPR corresponding to the parity group in the format CLPR-number:CLPR-name. For details on CLPRs, see HP StorageWorks XP24000 Disk/Cache Partition User’s Guide.
Figure 18 The Attribute Window of the Auto LUN The Attribute window displays the following information: • Monitoring Term displays the monitoring period specified in the Performance Management window. • Gathering Interval displays the collection interval in long range used in Performance Monitor. The interval in long range is fixed to 15 minutes. • Tree: The tree lists HDD classes and external volume groups. On the right of HDD classes, the upper limit (threshold) of the disk usage rate is displayed.
right of an icon, the icon represents the parity group 1-3. If the text 1-3[1-4] appears on the right of an icon, the icon represents two parity groups (that is, 1-3 and 1-4) that are connected together. • List: Information in the list differs depending on the item that you select in the tree. When you select a class in the tree, the list displays information about parity groups in that class. Figure 19 Information about Parity Groups • PG indicates the parity group ID.
indicates a normal volume that can be migrated. If you change the attribute of this volume to a reserved volume ( target volume). ), this volume can be used as a migration destination (that is, (blue) indicates a reserved volume of Auto LUN. This volume is reserved as a migration destination by Auto LUN. A reserved volume cannot be migrated. You can change this volume to a normal volume ( ), and then you can use this volume as a source volume. (green) indicates a reserved volume of other programs.
When you select an external volume group in the tree, the list displays information about external volumes (that is volumes in the external volume groups). Figure 22 Information about External Volumes • ExLDEV indicates the ID of the external volume. The number on the left of the first colon (:) from the left is the LDKC number. The number on the left of the second colon (:) from the left is the CU image number. The number on the right of the second colon is the LDEV number.
Figure 23 The History Window of the Auto LUN Note: Auto Migration History will be supported in a future release. The History window displays the following information: • Monitoring Term displays the monitoring period specified in the Performance Management window. • Gathering Interval displays the collection interval in long range used in Performance Monitor. The interval in long range is fixed to 15 minutes. • Migration History displays logs of all the events about the manual volume migration.
• • • • • • • • • The Source[Parity Gr.] and Target[Parity Gr.] columns also display the information about external volume group migration, though these groups are not parity groups. • If the source parity groups and target parity groups are the concatenated parity groups, the list only displays the ID of the parity group at the top of the concatenated parity groups. The Page drop-down list displays the pages of the history, up to 256 pages. 2,408 or less cases are displayed in one page.
Using the Auto LUN GUI
5 Auto LUN Operations Starting Auto LUN To start Auto LUN, take the following steps: 1. Ensure that the Remote Web Console main window is in Modify mode. The Remote Web Console main window is in Modify mode if the background color of the (pen tip) icon is light yellow. If the background color is gray , the window is in View mode and you must change it to Modify mode by taking the following steps: is blue. a.
5. Select the Apply button. The settings in the window are applied to the storage system. The specified volume is reserved as a migration destination. Tip: If you right-click a volume preceded by the blue icon (reserved volume of Auto LUN) and then and you will not be choose Normal LDEV from the pop-up menu, the selected icon changes to able to use the volume as a migration destination. Notes: • When you click the Apply button one time, up to 64 volumes can be reserved as migration destinations.
A new migration plan, consisting of the specified source and target volumes, is added to the list. The new migration plan is displayed in blue. Note: Throughout the storage system documentation set, the term migration plan is used to refer to a pair of a source volume and the corresponding target volume. 8. To create and execute more than one migration plan, repeat steps 2 through 7 to add migration plans. The newly added migration plan will appear below the existing migration plans. 9.
Table 9 Messages in the Migration Logs (displayed in the Action column) Message Meaning Migration Started The migration operation started. Migration Completed The migration operation completed successfully. Migration Canceled by User The migration operation was canceled by the user. Migration Failed The migration operation failed. Migration Canceled by Controller The migration operation was canceled by Auto LUN (for example, volume usage rate exceeded specified maximum).
6 Using RAID Manager for Manual Volume Migration In the environment where Auto LUN is installed on the storage system, users can use RAID Manager to perform manual volume migration from an open-system host. This appendix explains the procedure and notes for using RAID Manager to perform manual volume migration. Sample Volume Migration This section illustrates with a example the procedure when performing manual volume migration by using commands of RAID Manager.
Pairsplit SMPL -S Pairsplit PSUS PSUE Pairsplit Migration succeeded -S -S Paircreate COPY Migration Failed Figure 25 Status Transition Chart of a Pair during Volume Migration by RAID Manager Volume Migration Errors When you perform volume migration by using RAID Manager, note the following: • A reserved volume of Auto LUN cannot be used when you perform volume migration by using RAID Manager. • A migration plan being executed by Auto LUN cannot be canceled from RAID Manager.
Error Code Cause Measure 2301 Auto LUN is not installed on the storage system. Install Auto LUN, and the perform the volume migration. 2306 The LBA size does not match between the migration target volume and the migration source volume. This volume migration cannot be executed. Check the configuration definition file. 2309 The maximum number of pairs which can be set in the storage system is exceeded. Reduce the number of pairs set in the storage system, and then perform the volume migration.
Error Code Cause Measure 234B The migration target volume is already specified as the source volume of Auto LUN. Release the volume from Auto LUN, and then perform the volume migration. 2355 The setting of VLL is different between the migration target volume and the migration source volume. This volume migration cannot be executed. Check the configuration definition file. 2365 The migration source volume is a primary volume of IBM 3990 Concurrent Copy (CC).
7 Troubleshooting This chapter gives troubleshooting information on Auto LUN. For troubleshooting information on Remote Web Console, see the following documents: • HP StorageWorks XP24000 Remote Web Console User’s Guide • HP StorageWorks XP24000 Remote Web Console Error Codes Troubleshooting Auto LUN • When an error message is displayed on the Remote Web Console computer: The Auto LUN software displays error messages on the Remote Web Console computer when error conditions occur during Auto LUN operations.
Troubleshooting
A Acronyms and Abbreviations Table 11 Acronyms and Abbreviations ACP array control processor CU control unit (logical control unit) DASD direct-access storage device DFW DASD fast write DKA disk adapter DKCMAIN Disk Controller Main ESCON Enterprise System Connection (IBM trademark for optical channels) LAN local-area network LDEV logical device LU logical unit LUN logical unit number NVS nonvolatile storage PC personal computer PDEV physical device P-VOL primary volume RAID re
Acronyms and Abbreviations
Index A audience, 7 Auto LUN system requirements, 25 C class, 13 conventions document, 7 storage capacity values, 7 D document conventions, 7 related documentation, 7 documentation HP website, 7 providing feedback, 8 N normal volume, 41 R related documentation, 7 requirements, 16 reserved volume, 30, 41 S source volume, 14, 29 storage capacity values conventions, 7 storage systems supported models, 7 Subscriber's Choice, HP, 8 T E Expanded LUs, 18 target volume, 14, 30 technical support, 49 H
