hit counter script
HP XP P9500 User Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. HPE XP P9500
  6. User manual
HP XP P9500 User Manual

HP XP P9500 User Manual

Hp p9000 auto lun user guide (av400-96385, october 2011)
Hide thumbs Also See for XP P9500:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual, User Manual
HP
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 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 P9000 disk arrays, the HP Remote Web Console, and the operating system and web browser on the HP
Remote Web Console.
HP Part Number: AV400-96385
Published: September 201 1
Edition: Fifth

Advertisement

Table of Contents
loading

Related Manuals for HP XP P9500

Summary of Contents for HP XP P9500

  • Page 1 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 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 Volumes assigned to resource groups..................10...
  • Page 4 Migration History messages.....................33 Copy Threshold option......................33 Effects of Auto LUN on other program products................33 Best practices.........................34 6 Troubleshooting..................35 Troubleshooting Auto LUN.......................35 7 Support and other resources..............36 Contacting HP........................36 Subscription service......................36 Documentation feedback....................36 Related information.........................36 HP websites........................36 Conventions for storage capacity values..................37 Typographic conventions......................37 A Using RAID Manager for manual Auto LUN..........39 Auto LUN and RAID Manager commands .................39...

  • 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

    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. During the migration, the source volume remains available for read and write operations.

  • Page 7: When To Use Manual Volume Migration

    When to use manual volume migration In the following scenarios, you must perform a manual migration plan instead of an Auto Migration plan: To analyze processor and access path usage To migrate external volumes To migrate Thin Provisioning virtual volumes To run RAID Manager commands from an open-system host Automatic volume migration Automatic volume migration allows you to automate the creation and execution of migration plans.

  • Page 8: Migrating Volumes To Another Hdd Class

    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. The Auto Migration flow of volumes is shown in the following figure.
  • Page 9 Figure 6 Migrating a Volume Automatically Within the Same HDD Class Automatic volume migration...

  • 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 Volumes assigned to resource groups You can create migration plans including volumes that belong to resource groups as source volumes and target volumes.
  • Page 11 Volumes reserved by a migration program other than Auto LUN Volumes undergoing a Quick Format operation Volumes in an abnormal or inaccessible condition (such as, pinned, tracked, or fenced) External Storage Access Manager P-VOLs or S-VOLs The following table lists the volumes and volume types that can and cannot be considered as candidates for source and/or target volumes for an Auto LUN operation.
  • Page 12 Table 2 Candidates for Source and Target Volumes by Program Product (continued) Program Product Volume Type/Status Source Volume Candidate? Target Volume Candidate? A secondary volume in Yes. suspend status NOTE: The target volume must be in the same CLPR. A volume in Pending Duplex or Duplex status Compatible XRC A normal volume...

  • Page 13: Auto Lun With Thin Provisioning Virtual Volumes

    Table 2 Candidates for Source and Target Volumes by Program Product (continued) Program Product Volume Type/Status Source Volume Candidate? Target Volume Candidate? Cache Residency and Cache A volume with data stored Residency Z in cache LUN Expansion (LUSE) Individual LDEV within expanded LU All LDEVs in an expanded Yes.

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

    When you specify a Thin Provisioning virtual volume or an internal volume which is used for the Continuous Access Synchronous pair as a source volume, see the Table 4 (page 14) table for specifying a target volume. The Continuous Access Synchronous pair combination of an internal volume as a P-VOL and a Thin Provisioning virtual volume as an S-VOL is not recommended.

  • Page 15: Auto Lun And Continuous Access Journal

    Figure 7 3DC multi-target configuration Table 5 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 7 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 8 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 9 Number of Control Cylinders Based on Emulation Type (continued) Emulation Type Number of Control Cylinders 3390-9, 3390-9A, 3390-9B, 3390-9C 3390-L, 3390-LA, 3390-LB 3390-M, 3390-MA, 3390-MB, 3390-MC 3390-LC 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 Other Open Emulation Types

    The variables are explained below: X: The capacity of the volume to be migrated (in kilobytes). If the volume is divided by the Virtual LVI function, this value is the capacity of the divided volume. Z: The number of the slots that can be managed by a differential table. The capacity of an OPEN-V volume is 3,019,898,880 kilobytes, and the number of slots that can be managed by a differential table is 20,448.

  • 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

    Auto Migration Parameters The current values of Auto Migration Parameters are initialized each time a change is made to the storage system configuration. For example, the parameter values are initialized when new drives or LDEVs are installed. Keep in mind that changes to Auto Migration Parameters may be required 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

    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. Procedure 3 To set up auto migration plan parameters: Click Actions Other Function Auto LUN to open the Auto LUN window.

  • Page 25: Deleting Auto Migration Plans

    Deleting auto migration plans You can change or cancel auto migration plans before they are executed. If you delete an auto migration plan which is being executed, the data in the target volume is not guaranteed. Procedure 4 To delete auto migration plans: Click Actions Other Function Auto LUN to open the Auto LUN window.

  • Page 26: Stopping The Auto Migration Function

    Stopping the Auto Migration function Before creating a manual migration plan, the Auto Migration function must be disabled. If you perform a manual migration operation, all current Auto Migration plans are canceled. Procedure 6 To stop the Auto Migration function: Click Actions Other Function Auto LUN to open the Auto LUN window.

  • Page 27: Fixing A Parity Group

    In the “Parity Group list” (page 57), right-click a volume with the icon to reserve that volume as a target volume candidate, and then select Reserved LDEV from the pop-up menu. Click Apply to reserve the volume. icon should appear adjacent to the volume. To change a reserved volume to a normal volume, right-click a reserved volume icon and then select Normal LDEV from the pop-up menu.
  • Page 28 Click to change to Modify mode. In the Auto LUN window, click Auto LUN. A different window appears. Click the History tab to open the “History window” (page 60). Auto LUN operations...

  • 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 1 1 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 13 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 14 Failed Auto Migration Plan Messages (continued) Message Description Auto LUN failed to obtain. Check the settings and values specified in the Auto Plan Parameters of the Auto Plan window. Failed to create auto migration plans. Failed to get Auto LUN failed to get specified information required for XXXXXXXXXX.

  • Page 33: Migration History Messages

    Migration History messages The following table contains the messages that appear in Migration History logs. Table 15 Migration History Log Messages Message Description 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.

  • Page 34: Best Practices

    Table 16 Estimated Delay in Copy Time for Auto LUN and Other Program Products Capacity of Migrated Volume (MB) Estimated delay in copying speed (in minutes) 0 - 1,000 1,001 - 5,000 5,001 - 10,000 10,001 - 50,000 50,001 - 100,000 100,001 - 500,000 1,860 500,001 - 1,000,000...

  • 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

    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 38 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. Support and other resources...

  • 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 18 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 18 RAID Manager Errors Related to Manual Migration Plans (continued) Error Code Message Required Action (SSB2) Tiers virtual volumes that are associated with the same pool. 2096 The migration source volume is used by Continuous Release the pair containing the migration source Access Synchronous or Continuous Access Journal.
  • Page 43 Table 18 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 18 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 18 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: Manual Migration Window

    Item Type Description source and target parity groups after a proposed volume migration. The program does not calculate estimated usage rates of external volume groups. Gathering Interval field Displays the data collection interval used in Performance Monitor. The default long range interval is 15 minutes. Manual Migration Click the Manual Migration tab to open the Manual Migration Plans window.
  • 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: Manual Plan List

    Item Type Description LDKC:CU:LDEV Emulation field Indicates the emulation type of the volume (VLVI or LUN). Capacity field Indicates the capacity of the volume. 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.

  • Page 52: Auto Plan Window

    Item Type Description group number. If the indicated parity groups are the interleaved parity groups, this item only displays the ID of the parity group at the top of the interleaved parity groups. field Indicates the type of hard disk drive containing the source volume. CLPR field Indicates the number and name of the CLPR corresponding to the source volume’s parity...
  • Page 53 “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. The following table describes all fields, options, and buttons on this window.
  • Page 54 Item Type Description Target LDEV list The following information is displayed for the Target LDEV: LDEV: the ID of the volume is displayed in the following format: LDKC:CU:LDEV. RAID: the RAID type of the volume. Protection: the data protection level. PG: the parity group ID.

  • Page 55: Attribute Window

    Item Type Description than the specified number of volumes, the remaining volumes will be migrated at the next scheduled execution time. Default button Click Default to restore all Auto Plan Parameters to default values and apply these parameters to the storage system. button Click Set to apply each parameter setting to the storage system.

  • Page 56: Attribute Navigation Tree

    Attribute navigation tree The navigation tree lists the HDD classes (with parity groups), external volume groups, and Thin Provisioning virtual volume groups contained in the storage system. The icons and syntax used for these groups are summarized in the following table. Item Type Description...

  • Page 57: Parity Group List

    Item Type Description Management. A “+0” succeeding the percentage value indicates that the usage rate is between 0 and 1 percent. Total field Indicates the total number of volumes in the parity group. Reserved field Indicates the number of reserved volumes. CLPR field Indicates the number and name of the CLPR corresponding to the parity group.

  • Page 58: External Volume Group List

    Item Type Description by this program. For example, 01 indicates RAID Manager, and 99 indicates Tiered Storage Manager. A hyphen (-) indicates a normal volume that is not reserved. External Volume Group list When you select the External Group folder in the tree, the list displays information about external volume groups.

  • Page 59: Thin Provisioning Virtual Volumes List

    Item Type Description Reserved field Indicates the number of reserved Thin Provisioning virtual volumes. CLPR field Indicates the number and name of the CLPR corresponding to the Thin Provisioning virtual volume group. The following convention is used: CLPR-number:CLPR-name. Thin Provisioning virtual volumes list When you select a Thin Provisioning virtual volume group in the tree, the list displays information about Thin Provisioning virtual volumes in that 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 27) 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 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: Glossary

    Glossary AL-PA Arbitrated loop physical address. A 1-byte value that the arbitrated loop topology uses to identify the loop ports. This value becomes the last byte of the address identifier for each public port on the loop. P9000 or XP Business Copy. An HP application that provides volume-level, point-in-time copies in the disk array.
  • Page 63 Logical unit number. A LUN results from mapping a logical unit number, port ID, and LDEV ID to a RAID group. The size of the LUN is determined by the emulation mode of the LDEV and the number of LDEVs associated with the LUN. LUSE Logical Unit Size Expansion.
  • Page 64 synchronous Describes 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. T-VOL Target volume. User Datagram Protocol. Coordinated Universal Time.

  • Page 65: 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 66 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...

This manual is also suitable for:

Auto lun

Table of Contents