HP XP7 Auto LUN User Guide Abstract This document describes and provides instructions for using Auto LUN to migrate volumes on the HP XP7 Storage systems. Auto LUN is a part of the Performance Manager software suite.
© Copyright 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 Overview of Auto LUN................................................................................5 Overview of Auto LUN..............................................................................................................5 Limitations of Auto LUN.............................................................................................................5 Source and target volumes.........................................................................................................
Subscription service............................................................................................................29 Documentation feedback....................................................................................................29 Related information.................................................................................................................29 HP websites..............................................................................................................
1 Overview of Auto LUN This is an overview of Auto LUN. Overview of Auto LUN Auto LUN is used to optimize your data storage by balancing resource utilization and resolving bottlenecks of system activity on the storage system. If heavy input/output (I/O) activity occurs on a specific data drive or disk processor, the host might suffer from slower response times. To avoid this situation, Auto LUN lets you migrate high-usage volumes to a low-usage data drive or a fast data drive.
is repeated until all differential data on the source volume is copied. The following figure illustrates the data flow during a migration operation. Figure 1 Data flow during an Auto LUN operation There is an upper limit to the number of times a copy operation is executed, and the limit depends on the capacity of the source volume. The limit increases as the capacity of the source volume increases.
When to use volume migration In the following scenarios, you must perform a migration plan: • To analyze processor and access path usage • To migrate external volumes • To migrate Thin Provisioning or Thin Provisioning Z virtual volumes • To run RAID Manager commands on open-system and mainframe volumes from an open-system host To perform volume migration by RAID Manager, Auto LUN should be installed on the storage system.
2 Requirements This topic provides information about Auto LUN requirements.
Table 1 Information about whether you can create migration plans when using Resource Partition (continued) Resource groups where source volumes belong Resource groups where target volumes belong are assigned to user groups where you are not assigned to user groups where belong you belong No: You cannot create migration plans. CAUTION: When you use mainframe system, you can access only one resource group from a host.
Table 2 Candidates for source and target volumes by program product (continued) Program Product Continuous Access Synchronous Z Volume Type/Status Source Volume Candidate? Target Volume Candidate? Deleted pair volumes from a Yes, if volumes are in SMPL storage system in a primary status site No Deleted secondary volume from a storage system in a primary site Yes, if volume is in SMPL status No Deleted primary volume from Yes, if volume is in SMPL a storage system in a status secondary site No A
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 a BC Yes pair where the primary volume to secondary volume ratio is 1:1, 1:2, or 1:3 No A primary volume in an L1 Yes cascaded BC pair where the primary volume to secondary volume ratio is 1:1 or 1:2 No A primary volume in an L1 No cascaded BC pair where the primary volume to secondary volume ratio is 1:3 No A pri
Table 2 Candidates for source and target volumes by program product (continued) Program Product Remote Web Console Volume Type/Status Source Volume Candidate? Target Volume Candidate? A volume disabled to be No used as a secondary volume No A volume that LU path is set Yes to No *When you specify the capacity of a volume in TB, GB, or MB, you cannot create a volume whose capacity is 4 TB (4,398,046,511,104 byte).
must ensure that the capacity of a Thin Provisioning or Thin Provisioning Z virtual volume is not increasing if you plan on using that virtual volume in an Auto LUN plan. In this manual, Thin Provisioning indicates both Thin Provisioning and Smart Tiers. Thin Provisioning Z indicates Thin Provisioning Z and Smart Tiers Z.
Table 5 Poor target volume candidates for Cnt Ac-S/Cnt Ac-J pair combinations Continuous Access Synchronous or Continuous Access Journal Pair Source Volume Poor Target Volume Candidate Candidate Internal primary volume, Internal secondary Internal primary volume volume Internal secondary volume None Internal primary volume, THP V-VOL secondary volume Internal primary volume Internal volume THP V-VOL secondary volume THP V-VOL THP V-VOL primary volume, Internal secondary volume THP V-VOL primary
Table 6 Pair status when primary volume 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 Table 7 Pair status when secondary volume of Continuous Access Journal Z delta resync pair is a source volume Pair Name Status Continuous Access Synchronous Z pair Any pair statu
Figure 4 3DC multi-target configuration Table 8 Pair status when primary volume 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 9 Pair status when secondary volume of Continuous Access Journal delta resync pair is a source volume Pair Name Status Continuous Access Synchronous
Table 10 Access attributes and permissible Auto LUN operations Access attributes Access attributes of Operations from Remote Web Console Operations from RAID Manager of source volume target volume Performing Auto Stopping Auto paircreate pairsplit-S LUN operation LUN operation Read/Write, Read Only, Protect, and S-VOL Disable Read/Write permissible permissible permissible permissible Read Only not permissible permissible not permissible permissible Protect not permissible permissible not permi
NOTE: A source volume exchanges the role with a target volume by the Auto LUN operation. However, the access attribute of the source volume and the target volume does not exchange. You can set the access attribute to the source volume or the target volume of Auto LUN with Volume Retention. However, if the emulation type of volume is 3390-A, and you set the Read Only attribute or the Protect attribute to the source volume or the target volume, the migration operation may stop or the failure may occur.
3 Auto LUN planning This topic provides information about Auto LUN planning. Migration plans To migrate volumes, 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. Execute multiple migration plans continuously • When you create migration plans, the volume configuration may change for every migration plan execution.
Table 13 Number of control cylinders based on emulation type (continued) Emulation Type Number of Control Cylinders 3390-L, 3390-LA, 3390-LB 23 3390-A, 3390-M, 3390-MA, 3390-MB, 3390-MC, 6588-A 53 3390-LC 23 3390-3 emulation type example For this example, the emulation type of the mainframe volume is 3390-3.
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). 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.
Table 15 The number of differential tables, pair tables and system volumes per additional shared memory type Additional shared memory for Auto LUN the number of differential tables the number of pair tables the number of system volumes Base (no additional shared memory) 57,600 8,192 16,384 Extension 419,200 32,768 65,536 The emulation type and capacity of each volume to be migrated.
4 Auto LUN operations This topic contains operations performed in the Auto LUN window. Migrating a volume A volume can be migrated through the Migration Plan window. Prerequisites • You must have the Storage Administrator (Provisioning) role to perform this task. • The user has permission to access the source and target volume. • The volumes meet all requirements as source and target volume candidates.
Prerequisite • You must have the Storage Administrator (View only) role to perform this task. To view migration plans: Click Actions > Logical Device > Migration > Migrate Volumes. Related information “Auto LUN wizard” (page 39) Deleting a migration plan There may be an occasion when you want to delete a migration plan. You can delete up to eight migration plans in one deleting operation. If you want to delete nine plans or more, repeat the following procedure until all migration plans are deleted.
Prerequisite • You must have the Storage Administrator (Provisioning) role to perform this task. Procedure 3 To delete all history logs: 1. 2. 3. Click Actions > Logical Device > Migration > Delete All Histories. Enter the Task name in the Delete All Histories window. Click Apply. Procedure 4 or: 1. 2. 3. Click Actions > Logical Device > Migration > View Histories. Click Delete All Histories button in the Histories window. Click OK.
5 Auto LUN monitoring This topic contains the system messages that appear in Auto LUN history logs. Migration History messages The following table contains the messages that appear in Migration History logs. Table 16 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.
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 • Business Copy Z • Compatible FlashCopy The following table shows the amount of additional copy time expected for the affected program products.
6 Troubleshooting This topic 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 contact HP Technical Support, make sure to provide as much information about the problem as possible, including the error codes. For information on other error codes displayed on the Remote Web Console web client, see the XP7 Remote Web Console Messages.
7 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 19 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 Using RAID Manager for Auto LUN Use RAID Manager from an open-system host to perform migration operations on open-system and mainframe volumes. Auto LUN and RAID Manager commands The following figure illustrates the different states of Auto LUN pairs when using RAID Manager commands. Figure 5 Auto LUN Pairs and RAID Manager Commands The status of a pair can be checked by using the pairdisplay RAID Manager command.
• If you delete an Auto LUN plan, the volume status changes from SMPL(PD) to SMPL. You can check the status of the volume by viewing the list at the bottom of the window and confirming the existence of the migration plan. You can check the status of a volume by using the pairdisplay command, but you cannot distinguish between the SMPL and SMPL(PD) status.
Table 20 RAID Manager errors related to migration plans (continued) Error Code (SSB2) Message Required Action 2055 The migration target volume is being used with Continuous Access Journal. Release the volume from Continuous Access Journal, and then migrate the volume. 2056 The migration source volume is being used with Continuous Access Journal. Release the volume from Continuous Access Journal, and then migrate the volume.
Table 20 RAID Manager errors related to migration plans (continued) Error Code (SSB2) Message 20A6 The migration target volume is a Thin Provisioning Wait until the capacity increase is completed. or Smart Tiers virtual volume whose capacity is Then, you must specify a source volume which has increasing. the same capacity as the volume whose capacity is increased and migrate the volume.
Table 20 RAID Manager errors related to migration plans (continued) 36 Error Code (SSB2) Message 20F2 If the serial number of the virtual storage machine The volume cannot be migrated. Check the is set to the primary and secondary volume, the configuration definition file. serial number set in the primary volume matches the serial number set in the secondary volume. However, the serial numbers of the physical storage systems and the virtual storage machines do not match.
Table 20 RAID Manager errors related to migration plans (continued) Error Code (SSB2) Message Required Action 2342 The migration target volume is already specified as the target volume of Auto LUN. Release the volume from Auto LUN, and then migrate the volume. 2343 The migration target volume is set as the primary volume of Business Copy. Release the Business Copy pair, and then migrate the volume. 2344 The volume specified by the migration cancellation None.
Table 20 RAID Manager errors related to migration plans (continued) 38 Error Code (SSB2) Message 2373 The migration source volume is a command device. The volume cannot be migrated. Check the configuration definition file. 237C The migration source volume is an external volume Release the Continuous Access Synchronous pair, specified as a primary volume of Continuous and then migrate the volume. Access Synchronous. 2380 The migration target volume is not installed. The volume cannot be migrated.
B Auto LUN GUI reference The GUI elements of Auto LUN windows are summarized.
Selected Source Volume table • Table Item Description LDEV ID Selected LDEV's identifier LDEV Name Selected LDEV's name Parity Group ID ID for the parity group. They are hyphenated numbers. A number before the hyphen shows the frame number and a number after the hyphen shows the group number. Pool Name (ID) Pool name and ID number. Pool Capacity The pool capacity: Total: The total pool capacity. ◦ Used: The amount of pool capacity that is used.
Available Target Volumes table Item Description LDEV ID Selected LDEV's identifier LDEV Name Selected LDEV's name. This field is blank if the LDEV name is not set. Pool Name (ID) Pool name and ID number. Pool Capacity The pool capacity: • Total: The total pool capacity. • Used: The amount of pool capacity that is used. • Remaining: The amount of pool capacity that is not used.
Selected Migration Plans table • Table Item Description Source Volume ◦ LDEV ID: Source volume's LDEV identifier ◦ LDEV Name: Selected LDEV's name. This field is blank if the LDEV name is not set. ◦ Parity Group ID: Indicates the source volume's parity group ID. The number before the hyphen is the frame number and the number after the hyphen is the group number.
• Button Item Description Remove When clicked, removes the migration plan from the table. Select Source Volume window Provisioning Type Types of LDEV which can be selected as the source volume. • Basic: Internal volume • External: External volume • Thin Provisioning: THP volume • External MF: External mainframe volume Available Source Volumes table Item Description LDEV ID Source volume's LDEV identifier LDEV Name Selected LDEV's name. This field is blank if the LDEV name is not set.
Item Description Drive Type/RPM Displays the data drive type and RPM of the source volume. CLPR Indicates the number and name of the CLPR corresponding to the source volume's parity group.
Confirm window Item Description Source Volume • LDEV ID: Source volume's LDEV identifier • LDEV Name: Selected LDEV's name. This field is blank if the LDEV name is not set. • Parity Group ID: Indicates the source volume's parity group ID. The number before the hyphen is the frame number and the number after the hyphen is the group number.
Item Description • RAID Level: The RAID level of the target volume • Emulation Type: The emulation type of the target volume • Capacity: The target volume's capacity • Provisioning Type: Provisioning type of the target volume: Migration Plans window 46 Auto LUN GUI reference ◦ Basic: Internal volume ◦ External: External volume ◦ THP: THP volume ◦ External MF: External mainframe volume
Migration Plans table Migration Plans window 47
• Table Item Description Source Volume ◦ LDEV ID: Source volume's LDEV identifier ◦ LDEV Name: Selected LDEV's name. This field is blank if the LDEV name is not set. ◦ Parity Group ID: Indicates the source volume's parity group ID. The number before the hyphen is the frame number and the number after the hyphen is the group number.
Item Description Target Volume ◦ LDEV ID: Target volume's LDEV identifier ◦ LDEV Name: Selected LDEV's name. This field is blank if the LDEV name is not set. ◦ Parity Group ID: Indicates the target volume's parity group ID. The number before the hyphen is the frame number and the number after the hyphen is the group number.
Delete Migration Plans window 50 Auto LUN GUI reference
Selected Migration Plans table Item Description Source Volume • LDEV ID: Source volume's LDEV identifier • LDEV Name: Selected LDEV's name. This field is blank if the LDEV name is not set. • Parity Group ID: Indicates the source volume's parity group ID. The number before the hyphen is the frame number and the number after the hyphen is the group number.
Histories window Histories (Page.x) table • Table Item Description Date and Time Operation date and time Action The name of the operation Source Volume ◦ LDEV ID: Source volume's LDEV identifier ◦ Parity Group ID: Indicates the source volume's parity group ID. The number before the hyphen is the frame number and the number after the hyphen is the group number. ◦ Normal: The migration type is normal. ◦ Online Data Migration: The data is migrated by Online Migration.
• Button Item Description Delete All Histories When clicked, deletes all histories information. Export When clicked, outputs the history information.
Glossary allocation The ratio of allocated storage capacity versus total capacity as a percentage. Allocated storage refers to those logical devices (LDEVs) that have paths assigned to them. Allocated storage capacity is the sum of the storage of these LDEVs. Total capacity is the sum of the capacity of all LDEVs on the disk array. BC P9000 or XP Business Copy. An HP application that provides volume-level, point-in-time copies in the disk array.
to be associated with 1 to 36 LDEVs. Essentially, LUSE makes it possible for applications to access a single large pool of storage. M-VOL Main volume. MCU Main control unit. OPEN-x A general term describing any of the supported OPEN emulation modes (for example, OPEN-E). There are two types of OPEN-x devices: legacy OPEN-x devices with a fixed size (such as OPEN-3, OPEN-8, OPEN-9, and OPEN-E), and OPEN-V, which has a variable size and is a CVS-based volume.
Index A auto LUN window, 39 C calculating differential tables for a mainframe volume, 19 candidates for source and target volumes, 9 contacting HP, 29 control cylinders, 19 open emulation type, 20 conventions document, 30 storage capacity values, 30 text symbols, 31 copy operation, 5 Copy Threshold option, 26 D deleting manual migration plan, 24, 33 differential data, 5 differential tables OPEN-V volume, 20 document conventions, 30 related information, 29 documentation HP website, 29 providing feedback, 2
