hit counter script
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 auto lun user guide (av400-96334, 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 Auto LUN User Guide
Abstract
This guide explains how to balance system workloads and improve performance by migrating high-usage volumes to low-usage
and high-performance disks using HP StorageWorks P9000 Auto LUN Software. Topics include how to create and execute
migration plans manually and automatically and how to troubleshoot errors. The intended audience is a storage administrator
with independent knowledge of HP StorageWorks P9000 disk arrays, the HP StorageWorks Remote Web Console, and the
operating system and web browser on the HP StorageWorks Remote Web Console.
HP Part Number: AV400-96334
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 Auto LUN User Guide Abstract This guide explains how to balance system workloads and improve performance by migrating high-usage volumes to low-usage and high-performance disks using HP StorageWorks P9000 Auto LUN Software. Topics include how to create and execute migration plans manually and automatically and how to troubleshoot errors.
  • 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 Overview of Auto LUN................5 Overview of Auto LUN......................5 Limitations of Auto LUN......................5 Source and target volumes......................5 Manual volume migration......................6 When to use manual volume migration..................7 Automatic volume migration.......................7 Migrating volumes to another HDD class.................8 Migrating volumes within the same HDD class.................8 2 Requirements...................10 System requirements........................10 Source and target volume general requirements................10...
  • Page 4 Auto migration general status messages................29 Successful auto migration plan messages................30 Stopped auto migration plan messages.................30 Failed auto migration plan messages ...................31 Migration History messages.....................33 Copy Threshold option......................33 Effects of Auto LUN on other program products................34 Best practices.........................34 6 Troubleshooting..................35 Troubleshooting Auto LUN.......................35 7 Support and other resources..............36 Contacting HP........................36 Subscription service......................36...

  • Page 5: Overview Of Auto Lun

    1 Overview of Auto LUN This is an overview of manual and automatic Auto LUN. 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.

  • Page 6: Manual Volume Migration

    (page 10) for more information on requirements and restrictions when selecting source and target volumes. Manual volume migration In a manual volume migration operation, the data on the source volume is copied to a reserved target volume. Once all data is copied to the target volume, host access is transferred to the target volume to complete the migration.

  • Page 7: When To Use Manual Volume Migration

    Immediately after the source volume and target volume are swapped (that is, the migration is complete), the RAID level before the migration might be displayed, or an internal error might occur in the storage system. If this occurs, try to resolve the issue by updating the display of the window. When to use manual volume migration In the following scenarios, you must perform a manual migration plan instead of an Auto Migration plan:...

  • Page 8: Migrating Volumes To Another Hdd Class

    Figure 3 Auto LUN to Improve Disk Usage Efficiency When parity groups in a higher HDD class run out of reserved volumes, the low-usage volumes in this class are automatically migrated to a lower HDD class parity group in order to maintain an inventory of volumes that may be reserved in the higher HDD class parity groups.
  • Page 9 HDD class and force another volume out of that parity group, the Auto Migration operation requires a minimum of 20 percent difference in estimated disk usage between the two volumes. If the difference in disk usage is less than 20 percent, the migration plan is considered an ineffective strategy, and the volume is not migrated.

  • Page 10: Requirements

    2 Requirements This chapter provides information about Auto LUN requirements. System requirements To use Auto LUN, you need: A P9500 storage system A Remote Web Console client machine Both Performance Monitor and Auto LUN Source and target volume general requirements The source and target volume should satisfy the following conditions: Managed by the same P9500 storage system Have the same emulation type and capacity.
  • Page 11 Table 1 Candidates for Source and Target Volumes by Program Product (continued) Program Product Volume Type/Status Source Volume Candidate? Target Volume Candidate? Continuous Access A volume in PSUS, PSUE, or Synchronous PAIR status Deleted pair volumes from Yes, if volumes are in SMPL status Deleted S-VOL from MCU Yes, if volume is in SMPL...
  • Page 12 Table 1 Candidates for Source and Target Volumes by Program Product (continued) Program Product Volume Type/Status Source Volume Candidate? Target Volume Candidate? Business Copy and Business BC pair volumes Copy for Mainframe A reserved BC volume A P-VOL in an BC pair where the P-VOL to S-VOL ratio is 1:1 or 1:2 A P-VOL in an BC pair...

  • Page 13: Auto Lun With Thin Provisioning Virtual Volumes

    Table 1 Candidates for Source and Target Volumes by Program Product (continued) Program Product Volume Type/Status Source Volume Candidate? Target Volume Candidate? Data Retention A volume having the Read Only or Protect attribute turned on A volume disabled to be used as a secondary volume Volume Security for A volume disabled to be...

  • Page 14: Auto Lun With Continuous Access Synchronous And Continuous Access Journal V-Vols

    Auto LUN with Continuous Access Synchronous and Continuous Access Journal V-VOLs When the selected source volume is a P-VOL or an S-VOL of a Continuous Access Synchronous or Continuous Access Journal pair consisting of internal volumes and/or Thin Provisioning virtual volumes, there are some target volume candidates that should not be considered.

  • Page 15: Auto Lun And Continuous Access Journal

    Figure 7 3DC multi-target configuration Table 4 Pair status when P-VOL of Continuous Access Journal Z delta resync pair is as a source volume Pair Name Status Continuous Access Synchronous Z pair SUSPEND or DUPLEX Continuous Access Journal Z pair Any pair status can be acceptable Continuous Access Journal Z pair for delta resync operation Hold or Hlde...
  • Page 16 Figure 8 3DC multi-target configuration Table 6 Pair status when P-VOL of Continuous Access Journal delta resync pair is a source volume Pair Name Status Continuous Access Synchronous pair PSUS or PAIR Continuous Access Journal pair Any pair status can be acceptable Continuous Access Journal pair for delta resync operation HOLD or HLDE Table 7 Pair status when S-VOL of Continuous Access Journal delta resync pair is a source volume...

  • Page 17: Auto Lun Planning

    3 Auto LUN planning This chapter provides information about Auto LUN planning. Manual migration plans To migrate volumes manually, you must create migration plans. A migration plan is required for each volume that you want to migrate, and each plan includes a source volume and target volume. Up to eight migration plans can be applied each time you click Apply in the Manual Plan window.

  • Page 18: 3390-3 Emulation Type Example

    Table 8 Number of Control Cylinders Based on Emulation Type (continued) Emulation Type Number of Control Cylinders 3390-3, 3390-3A, 3390-3B, 3390-3C, 3390-3R 3390-9, 3390-9A, 3390-9B, 3390-9C 3390-L, 3390-LA, 3390-LB 3390-M, 3390-MA, 3390-MB, 3390-MC 3390-LC NF80–F 3390-3 emulation type example For this example, the emulation type of the mainframe volume is 3390-3. Recall the formula for calculating the required amount of differential tables per migration plan: (X (number of volume cylinders) + Y (number of control cylinders)) ×...

  • Page 19: Differential Tables Calculation For An Open-V Volume

    Differential tables calculation for an OPEN-V volume The following equation is used to calculate the required amount of differential tables for an OPEN-V volume. Total number of differential tables per migration plan = (X ÷ 256) ÷ Z The variables are explained below: X: The capacity of the volume to be migrated (in kilobytes).

  • Page 20: Estimating The Number Of Concurrent Manual Migration Plans

    installed, you may use 104,768 or 209,600 differential tables. You may also use 146,688, or 209,600 differential tables. To install additional shared memory for differential tables, call HP Technical Support. The amount of shared memory available for pair tables. You can install additional shared memory for pair tables.

  • Page 21: Auto Migration Parameters

    NOTE: In a manual migration plan, you can specify a volume in a fixed parity group as a target or a source volume. Auto Migration Parameters The current values of Auto Migration Parameters are initialized each time a change is made to the storage system configuration.

  • Page 22: Auto Lun Operations

    4 Auto LUN operations This chapter contains operations performed in the Auto LUN window. Migrating a volume manually A volume can be migrated manually through the Manual Plan window. Prerequisites The Auto Migration function is disabled. See “Stopping the Auto Migration function” (page 26).

  • Page 23: Deleting A Manual Migration Plan

    The Source LDEV section displays the current usage rate for the source volume’s parity group and an estimated usage rate for the parity group after the proposed migration plan. The Target (Reserved) LDEV section displays the current usage rate for the target volume’s parity group and an estimated usage rate for the parity group after the proposed migration plan.

  • Page 24: Setting Up Auto Migration Plan Parameters

    NOTE: If you delete a manual migration plan that is being processed, the data in the target volume cannot be guaranteed. A migration plan that was created by another program cannot be deleted through Auto LUN. Setting up auto migration plan parameters To enable Auto LUN to create and execute auto migration plans, a sampling term, a migration time, and other parameters must be set up in the Auto Plan window.

  • Page 25: Deleting Auto Migration Plans

    Auto LUN can now create and execute migration plans. Auto LUN creates plans 30 minutes later than the specified Sampling Term (for example, if 13:00 - 15:00 is specified, a plan will be created at 15:30). The migration plans will be executed on the specified day at the specified Migration Time.

  • Page 26: Stopping The Auto Migration Function

    As needed, modify any auto migration plan parameters. For details, see “Setting up auto migration plan parameters” (page 24). Click Make New Plan. All the existing auto migration plans are deleted and new auto migration plans are created based on the new settings. Stopping the Auto Migration function Before creating a manual migration plan, the Auto Migration function must be disabled.

  • Page 27: Fixing A Parity Group

    In the navigation tree, double-click the HDD class in which you would like to reserve a volume. The HDD class folder expands and parity groups in that HDD class can be viewed. In the expanded HDD class folder, select a low-usage parity group. The volumes contained in the selected parity group load in the “Parity Group list”...

  • Page 28: Changing Disk Usage Rate Limit For An Hdd Class

    To “un-fix” a fixed parity group, right-click the fixed parity group and then select Normal PG from the pop-up menu. Changing disk usage rate limit for an HDD class By default, the Max. disk utilization auto migration parameter value is applied to each HDD class. If necessary, you can change the disk usage rate limit for an HDD class.

  • Page 29: Auto Lun Monitoring

    5 Auto LUN monitoring This chapter contains the system messages that appear in Auto LUN history logs. Auto migration messages The next four tables list messages and descriptions related to auto migration plans. NOTE: A timestamp appears at the start of each auto migration message, but the timestamp has been omitted in the tables to avoid repetition.

  • Page 30: Successful Auto Migration Plan Messages

    Table 10 Auto Migration General Status Messages (continued) Message Description Auto migration is not available. All the parity groups cannot This message is output when you start Auto LUN in the be used for auto migration. following conditions: All volumes in the storage system are external volumes All parity groups in the storage system have On-Demand settings An internal logic error occurred.

  • Page 31: Failed Auto Migration Plan Messages

    Table 12 Stopped Auto Migration Plan Messages (continued) Message Description The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) The disk usage rate of the parity group including the source was stopped. The usage rate of the source volume is over volume is over the specified limit. Or, the disk usage rate the specified Max.
  • Page 32 Table 13 Failed Auto Migration Plan Messages (continued) Message Description Failed to create auto migration plans. Failed to obtain Auto LUN failed to obtain specified information or statistics XXXXXXXXXX. which are required for creating auto migration plans. ‘XXXXXXXXXX’ represents the information or statistics that Error location: Class X Group X-X Auto LUN failed to obtain.

  • Page 33: Migration History Messages

    Table 13 Failed Auto Migration Plan Messages (continued) Message Description In Group X-X, there are N invalid samples. These samples There are some invalid samples in the parity group that were not used for creating the auto migration plans. were not used to create auto migration plans. ‘N’ represents the number of invalid samples.

  • Page 34: Effects Of Auto Lun On Other Program Products

    NOTE: Copy operations that are stopped by the Copy Threshold option will resume once the load on the storage system becomes light. Effects of Auto LUN on other program products When differential data is being copied, longer copying time can be expected for the following program products: Auto LUN Business Copy...

  • Page 35: Troubleshooting

    6 Troubleshooting This chapter gives troubleshooting information on Auto LUN. Troubleshooting Auto LUN An error message appears on the Remote Web Console web client when error conditions occur during Auto LUN operations. If you need to call HP Technical Support, make sure to provide as much information about the problem as possible, including the error codes.

  • Page 36: Support And Other Resources

    7 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 Subscription service...

  • Page 37: Conventions For Storage Capacity Values

    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 1 PB (petabyte) = 1,000 bytes...

  • Page 38: 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 39: A Using Raid Manager For Manual Auto Lun

    A Using RAID Manager for manual Auto LUN Use RAID Manager to perform manual migration operations from an open-system host. Auto LUN and RAID Manager commands The following figure illustrates the different states of Auto LUN pairs when using RAID Manager commands.

  • Page 40: Interoperability Of Auto Lun And Raid Manager

    Interoperability of Auto LUN and RAID Manager When you perform a manual Auto LUN plan by using RAID Manager commands, note the following: A volume reserved through Auto LUN cannot be used as a target volume. A migration plan being executed by Auto LUN cannot be canceled using RAID Manager. A migration plan created by Auto LUN cannot be displayed using RAID Manager.
  • Page 41 Table 17 RAID Manager Errors Related to Manual Migration Plans (continued) Error Code Message Required Action (SSB2) 2039 The migration source volume is a quorum disk. The volume cannot be migrated. Check the configuration definition file 203a The migration target volume is a quorum disk. The volume cannot be migrated.
  • Page 42 Table 17 RAID Manager Errors Related to Manual Migration Plans (continued) Error Code Message Required Action (SSB2) 2095 The migration target volume and the migration None. This migration plan cannot be executed. source volume are the Thin Provisioning or Smart Tiers virtual volumes that are associated with the same pool.
  • Page 43 Table 17 RAID Manager Errors Related to Manual Migration Plans (continued) Error Code Message Required Action (SSB2) 231 1 The migration target volume is already reserved Cancel the reservation by Auto LUN, and then by Auto LUN. migrate the volume. 2312 The migration source volume is online with the Make the migration source volume off-line from...
  • Page 44 Table 17 RAID Manager Errors Related to Manual Migration Plans (continued) Error Code Message Required Action (SSB2) 2355 The setting of VLL is different between the migration None. This migration plan cannot be executed. target volume and the migration source volume. 2362 The migration source volume is a primary volume Release the Compatible XRC pair, and then...
  • Page 45 Table 17 RAID Manager Errors Related to Manual Migration Plans (continued) Error Code Message Required Action (SSB2) 2389 Cache Residency is set on the migration source Release the setting of Cache Residency, and then volume. migrate the volume. 238A Cache Residency is set on the migration target Release the setting of Cache Residency, and then volume.

  • Page 46: B Auto Lun Gui Reference

    B Auto LUN GUI reference The GUI elements of Auto LUN windows are summarized. Auto LUN window This section describes the fields in the Auto LUN window.s Figure 1 1 Auto LUN Window Item Type Description Monitoring Switch field Enable: Performance Monitor is monitoring the storage system. Disable: The storage system is not being monitored.

  • Page 47: Common Elements

    Common elements The top-level elements and the four tabs of the Auto LUN window are summarized in the following table. Item Type Description Monitoring Term field The starting and ending times for collecting performance and usage statistics for HDD classes, parity groups, and volumes. Auto LUN analyzes disk usage information collected by Performance Monitor during the monitoring period, and then calculates estimated usage rates of the source and target parity groups after a proposed volume migration.
  • Page 48 The following Auto LUN operations may be performed with the Manual Migration window: “Migrating a volume manually” (page 22) “Deleting a manual migration plan” (page 23) Item Type Description Target button When you select the source volume in the “LDEVs list” (page 50) and click Target, the “Target (Reserved) LDEV list”...

  • Page 49: Manual Migration Plans Navigation Tree

    Manual Migration Plans navigation tree The Manual Migration Plans navigation tree lists the parity groups, external volume groups, and Thin Provisioning virtual volume groups contained in the storage system. Item Type Description icon This icon indicates a fixed parity group when it appears in the Parity Group folder. A fixed parity group cannot be a part of an Auto Migration plan.

  • Page 50: Ldevs List

    LDEVs list The LDEVs list contains IDs, emulation type, capacity, and other statistics of each LDEV in the selected parity group, external volume group, or Thin Provisioning group. The list does not include pool volumes, journal volumes, system disks, and quorum disks. Item Type Description...

  • Page 51: Target (Reserved) Ldev List

    Target (Reserved) LDEV list The Target (Reserved) LDEV list contains IDs, emulation type, capacity, and other statistics of each reserved LDEV in the selected parity group, external volume group, or Thin Provisioning group. The reserved LDEV fields are summarized in the following table. Item Type Description...

  • Page 52: Auto Plan Window

    Item Type Description Capacity field Indicates the capacity of the volume. RAID field Indicates the RAID type of the source volume. Protection field Indicates the data protection level of the source volume. field Indicates the parity group ID or the external volume group ID of the source volume. The number before the hyphen (-) is the frame number.
  • Page 53 The following Auto LUN operations may be performed with the Auto Plan window: “Setting up auto migration plan parameters” (page 24) “Deleting auto migration plans” (page 25) “Recreating auto migration plans ” (page 25) “Stopping the Auto Migration function” (page 26) The Auto Plan window contains Auto Migration Plans and Auto Plan Parameters sections and is used to set up, configure, and manage Auto Migration.
  • Page 54 Item Type Description Source LDEV list The following information is displayed for the Source LDEV: LDEV: the ID of the volume is displayed in the following format: LDKC:CU:LDEV. Emulation: the emulation type of the volume. Capacity: the capacity of the volume. RAID: the RAID type of the volume.

  • Page 55: Attribute Window

    Item Type Description Max. Migration field The time limit for the execution of an auto migration plan is specified duration in the Max. migration duration field. Allowable values range from 10 to 120 minutes. If the auto migration plan is not complete within the specified limit, the remaining migration operation(s) are performed at the next scheduled execution time.

  • Page 56: Attribute Navigation Tree

    The Attribute window is used to reserve target volumes, discover which parity groups belong to which HDD class, and view detailed information about parity groups, external volume groups, and Thin Provisioning virtual volume groups. The Attribute window has several GUI elements which are described in the subsequent sections.

  • Page 57: Parity Group List

    Item Type Description Ave. (%) field Indicates the average usage rate for the parity group. An exclamation mark (!) preceding the percentage value indicates that the reported usage rate is likely to be inaccurate. This can occur when volumes used in Auto LUN are also formatted by Virtual LVI or Open Volume Management.

  • Page 58: External Volume Group List

    Item Type Description CLPR field Indicates the number and name of the CLPR corresponding to the parity group to which the volume belongs. The following convention is used: CLPR-number:CLPR-name Owner field Indicates the program which reserved this volume. If P9500 is displayed, the reserved volume is reserved by Remote Web Console.

  • Page 59: Thin Provisioning Groups List

    Thin Provisioning groups list When you select the Thin Provisioning folder in the navigation tree, the list displays information about Thin Provisioning virtual volume groups. This information is summarized in the following tables. Item Type Description LDEV# field Indicates the ID of the Thin Provisioning virtual volume. Thin Provisioning field Indicates the ID of the Thin Provisioning virtual volume group.

  • Page 60: History Window

    History window Figure 15 History Window The following Auto LUN operations may be performed with the Manual Migration window: “Viewing the migration history logs” (page 28) The History window displays information about successful and failed Auto Migration and Manual Migration plans. The History window contains Auto Migration History and Migration History sections are described in the following table.
  • Page 61 Item Type Description Action field Displays the event type. Source[Parity Gr.] field Displays the source volume and the parity group (or the external volume group if applicable). If the source parity groups and target parity groups are the interleaved parity groups, the parity group ID at the top of the interleaved parity groups appears.
  • Page 62 Disk adapter. Disk controller. Disk Unit. Express Switch Adapter. Fibre Channel arbitrated loop. nce level A method of setting rejection of P9000 or XP Continuous Access write I/O requests from the host according to the condition of mirroring consistency. bre Channel A serial data transport infrastructure and protocol used to implement storage area networks (SANs).
  • Page 63 HP StorageWorks RAID Manager. S-VOL Secondary or remote volume. The copy volume that receives the data from the primary volume. Serial Attached SCSI. State-change-pending. Service information message. SMPL Simplex. Sense byte. Solid State Disk. Service processor. A computer built into a disk array. The SVP, used only by an HP service representative, provides a direct interface to the disk array.

  • Page 64: Glossary

    Glossary AL-PA Arbitrated loop physical address. HP StorageWorks P9000 or XP Business Copy. An HP StorageWorks application that provides volume-level, point-in-time copies in the disk array. BC z This is the version of BC that supports mainframe volumes. See BC for more information. The basic unit of data in a binary numbering system (binary digit), represented by a 0 or a 1.
  • Page 65 LUSE Logical Unit Size Expansion. The LUSE feature is available when the HP StorageWorks LUN Manager product is installed, and allows a LUN, normally associated with only a single LDEV, to be associated with 1 to 36 LDEVs. Essentially, LUSE makes it possible for applications to access a single large pool of storage.
  • Page 66 synchronous Pertaining to computing models that perform tasks in chronological order without interruption. In synchronous replication, the source waits for data to be copied at the destination before acknowledging that it has been written at the source. See also . T-VOL Target volume.

  • Page 67: Index

    Index overview, fixing a parity group, auto LUN window, auto migration help changing disk usage rate limit , obtaining, flow, host name, function, 7, identifying parity groups, technical support, messages, parameters, prerequisites, identifying parity groups, instance number, calculating differential tables for a mainframe volume, LDEV list, candidates for source and target volumes,...
  • Page 68 Subscriber's Choice, HP, symbols in text, target volume, technical support service locator website, text symbols, troubleshooting general, when using RAID Manager, typographic conventions, volume migration automatic , interoperability, limitations, manual, manual with RAID Manager, manual;migrating volu:manually, monitoring, websites HP , HP Subscriber's Choice for Business, product manuals, window...

Table of Contents