HP XP P9500, Auto LUN User Manual

Page 1

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 2011 Edition: Fifth

Page 2

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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Acknowledgements

Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.

Export Requirements

You may not export or re-export this document or any copy or adaptation in violation of export laws or regulations.

Without limiting the foregoing, this document may not be exported, re-exported, transferred or downloaded to or within (or to a national resident of) countries under U.S. economic embargo, including Cuba, Iran, North Korea, Sudan, and Syria. This list is subject to change.

This document may not be exported, re-exported, transferred, or downloaded to persons or entities listed on the U.S. Department of Commerce Denied Persons List, Entity List of proliferation concern or on any U.S. Treasury Department Designated Nationals exclusion list, or to parties directly or indirectly involved in the development or production of nuclear, chemical, biological weapons, or in missile technology programs as specified in the U.S. Export Administration Regulations (15 CFR 744).

Revision History

DescriptionDateEdition

Applies to microcode version 70-01-01-00/00 or later.October 2010First

Applies to microcode version 70-01-24-00/00 or later.November 2010Second

Applies to microcode version 70-01-62-00/00 or later.January 2011Third

Applies to microcode version 70-02-01-00/00 or later.May 2011Fourth

Applies to microcode version 70-02-5x-00/00 or later.September 2011Fifth

Page 3

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

Source and target volume general requirements..........................................................................10

Supported and prohibited source and target volumes..................................................................10

Auto LUN with Thin Provisioning virtual volumes..........................................................................13

Auto LUN with Continuous Access Synchronous and Continuous Access Journal V-VOLs...................14

Auto LUN and Continuous Access Journal Z...............................................................................14

Auto LUN and Continuous Access Journal..................................................................................15

3 Auto LUN planning...................................................................................17

Manual migration plans..........................................................................................................17

Estimating differential tables.....................................................................................................17

Calculating the required amount of differential tables for a mainframe volume................................17

Control cylinders by mainframe emulation type......................................................................17

3390-3 emulation type example..........................................................................................18

Calculating the required amount of differential tables for an open-system volume............................18

Control cylinders by open emulation type..............................................................................18

Differential tables calculation for an OPEN-V volume..............................................................18

Differential tables calculation for other open emulation types...................................................19

Running concurrent manual migration plans...............................................................................19

Estimating the number of concurrent manual migration plans...................................................20

Fixed parity groups.................................................................................................................20

Auto Migration Parameters.......................................................................................................21

4 Auto LUN operations................................................................................22

Migrating a volume manually...................................................................................................22

Deleting a manual migration plan.............................................................................................23

Setting up auto migration plan parameters.................................................................................24

Deleting auto migration plans...................................................................................................25

Recreating auto migration plans ..............................................................................................25

Stopping the Auto Migration function........................................................................................26

Reserving a volume.................................................................................................................26

Fixing a parity group..............................................................................................................27

Changing disk usage rate limit for an HDD class........................................................................27

Viewing the migration history logs............................................................................................27

5 Auto LUN monitoring................................................................................29

Auto migration messages.........................................................................................................29

Auto migration general status messages................................................................................29

Successful auto migration plan messages..............................................................................30

Stopped auto migration plan messages.................................................................................30

Failed auto migration plan messages ...................................................................................31

Contents 3

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

Migrating volumes manually with RAID Manager........................................................................39

Interoperability of Auto LUN and RAID Manager........................................................................40

Troubleshooting when using RAID Manager...............................................................................40

B Auto LUN GUI reference............................................................................46

Auto LUN window..................................................................................................................46

Common elements..................................................................................................................46

Manual Migration window......................................................................................................47

Manual Migration Plans navigation tree................................................................................49

LDEVs list..........................................................................................................................50

Target (Reserved) LDEV list..................................................................................................50

Manual Plan list.................................................................................................................51

Auto Plan window..................................................................................................................52

Attribute window....................................................................................................................55

Attribute navigation tree......................................................................................................56

HDD Class list...................................................................................................................56

Parity Group list.................................................................................................................57

External Volume Group list..................................................................................................58

External volume list............................................................................................................58

Thin Provisioning groups list.................................................................................................58

Thin Provisioning virtual volumes list.....................................................................................59

History window......................................................................................................................60

Glossary....................................................................................................62

Index.........................................................................................................65

4 Contents

Page 5

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. Actual windows may differ depending on the operating system and browser used. GUI contents also vary with licensed program products, storage system models, and firmware versions.

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 hard disk 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 hard disk drive or a fast hard disk drive.

Migrating volumes with Auto LUN is completely non-disruptive as the data being migrated can remain online to all hosts for read and write operations throughout the entire migration process.

Auto LUN operations can be performed manually or set up to run automatically at specified times. In manual migration, the system administrator specifies the source volume and the target volume, and then executes the manual migration plan. In an “Auto” migration, the Auto LUN software determines source and target parity groups based on Auto Plan settings and executes the migration plan automatically at a specified interval and time.

Limitations of Auto LUN

You should keep in mind that Auto LUN operations can improve performance in one area while decreasing performance in another. Consider the following scenario:

• Parity Group A has an average usage value of 20%

• Parity Group B has an average usage value of 90%

Through Auto LUN, it is estimated that if one volume from Parity Group B is migrated to Parity Group A, the usage values of both parity groups become 55%. In this scenario, the I/O response

time for Parity Group B will most likely decrease, while the I/O response time for Parity Group A will most likely increase. Overall, the throughput may increase or decrease.

Auto LUN should only be performed when you can expect a large improvement in storage system performance. Auto LUN operations may not provide significant improvement for cases in which parity group or volume usage varies only slightly, or for cases in which the overall MP or DRR usages is relatively high.

When an error condition exists in the P9500 storage system, resource usage can increase or become unbalanced. Do not use data collected during an error condition as the basis for planning Auto LUN operations.

Source and target volumes

The Auto LUN source volume is the volume whose data will be migrated, and this data is migrated to the Auto LUN target volume. For Auto Migration plans to be executed successfully, a sufficient amount of target volume candidates must be reserved in each HDD class and parity group. In a manual migration, the actual target volume must be reserved or the migration will fail. Theoretically, the source and target volumes can be located anywhere in the storage system, however, there are some restrictions for selecting source and target volumes in a manual migration. See “Requirements”

(page 10) for more information on requirements and restrictions when selecting source and target

volumes.

Overview of Auto LUN 5

Page 6

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.

The volume migration copy operation copies the content of the source volume to the target volume cylinder by cylinder (24 tracks at a time, not including the diagnostic and unassigned alternate tracks). If the source volume is updated by write operations during the copy operation, the updates will be recorded on the cylinder map of a volume. If differential data are created by the update, the differential data are copied from the source volume to the target volume. This process is repeated until all differential data on the source volume is copied. The following figure illustrates the data flow during a manual 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 differential data still exists after copy operations are repeated to the upper limit, the migration fails. Before attempting the migration again, the workload between the host and the storage system should be adequately reduced (especially write operations), preferably to a value below 50 IOPS (input/output operations per second).

Once the volumes are fully synchronized (that is, there is no differential data on the source volume), the P9500 storage system completes the migration by swapping the Reserve attribute (from target volume to source volume) and redirecting host access to the target volume. The status of the target volume becomes normal, and the status of the source volume becomes reserved. The following figure illustrates the state of the volumes after a manual migration operation.

Figure 2 Data Flow after an Auto LUN Operation

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.

6 Overview of Auto LUN

Page 7

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. If you automate the creation and execution of migration plans, you do not need to analyze the usage rates of storage system resources or the speed of hard disk drives. These tasks are performed automatically by Auto LUN at a specified interval and time.

Auto migration plans are performed to balance the load of I/O activity in each HDD class and across parity groups (groups of disks with similar speeds) within the same HDD class. The fastest parity groups belong to class A. The maximum disk usage rate is specified for each HDD class in the P9500 storage system. The maximum disk usage rate for an HDD class applies to all parity groups within that class. When a parity group exceeds the threshold, the Auto Migration function will initiate one of the following two plans:

• Migrate one or more volumes in this parity group to another parity group in a higher HDD

class

• Migrate one or more volumes in this parity group to a parity group with lower utilization in

the same HDD class

Auto LUN does not perform an Auto Migration operation which might result in the target parity group exceeding the maximum disk usage rate.

NOTE: The default maximum disk usage rates are rough estimates only, and may not provide

the best results.

By default, each HDD class is assigned a certain limit on disk usage rate. Disk usage rate limit affects Auto Migration performance. If the disk usage rate limit for one class is high, many volumes might be migrated to parity groups in that class. If the disk usage rate limit for one class is low, fewer volumes might be migrated to parity groups in that class. If necessary, you can change the disk usage rate limit for an HDD class.

The following figure illustrates how the Auto Migration function identifies parity groups that exceed the disk usage rate limit, and then selects high-usage volumes in these parity groups as the source volumes to be migrated to a parity group in a higher HDD class, or to another parity group in the same HDD class with lower utilization.

Figure 3 Auto LUN to Improve Disk Usage Efficiency

When to use manual volume migration 7

Page 8

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.

Figure 4 Auto Migration Flow

If the distance between classes of the high-usage parity group that is to be a candidate for the source volume and the low-usage parity group that is to be target is more than one class, a volume cannot be moved. If you want to use the Auto Migration function effectively, we recommend that you provide one or more reserved volumes per class.

Migrating volumes to another HDD class

The Auto Migration operation requires a minimum of five percent difference in estimated disk usage between the two volumes. If the difference in disk usage is less than five percent, the migration plan is considered an ineffective strategy, and the volume is not moved. The following figure illustrates this Auto Migration operation.

Figure 5 Migrating a Volume Automatically to a Lower HDD Class

Migrating volumes within the same HDD class

The Auto Migration operation can also move a volume from one parity group to another parity group within the same HDD class. To be able to move one volume into a parity group of the same 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. The following figure illustrates this Auto Migration operation.

8 Overview of Auto LUN

Page 9

Figure 6 Migrating a Volume Automatically Within the Same HDD Class

Automatic volume migration 9

Page 10

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. You may be unable to create migration plans depending on the use of Resource Partition.

Table 1 Information about whether you can create migration plans when using Resource Partition

Resource groups where target volumes belongResource groups where source

volumes belong

Resource groups are not assigned to user groups where you belong

Resource groups are assigned to user groups where you belong

No — you cannot create migration plans

Yes — you can create migration plansResource groups are assigned to user

groups where you belong

No — you cannot create migration plans

Resource groups are not assigned to user groups where you belong

CAUTION: When you use the mainframe system, you can access one resource group from a

host. HP recommends that you specify volumes that are assigned to the resource group that can be accessed from the host as source volumes and target volumes.

For details about resource groups, see the HP P9000 Provisioning for Open Systems User Guide or the HP P9000 Provisioning for Mainframe Systems User Guide.

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. If the emulation type is not OPEN-V, both the

source and target volumes must be custom-sized (CV) volumes or normal volumes.

• The LDEV IDs (LDKC:CU:LDEV) must have values between 00:00:00 and 00:FE:FF

• Must be specified by LDEV ID, not VOLSER or port/TID/LUN

Supported and prohibited source and target volumes

The following list includes volumes and volume types that cannot be used as source or target volumes for Auto LUN:

• System disks

• Quorum disks

• Volumes being used by the host as command devices

• IBM 3390 Concurrent Copy volumes

10 Requirements

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. The table is categorized by program product.

Table 2 Candidates for Source and Target Volumes by Program Product

Target Volume Candidate?Source Volume Candidate?Volume Type/StatusProgram Product

Yes, but the target volume may not be associated with

Yes

NOTE: The maximum

capacity is 4 TB.

V-VOLThin Provisioning

the same Thin Provisioning pool as the source volume

NOTE: The maximum

capacity is 4 TB.

NoNoPool volume

NoYesA volume in PSUS, PSUE, or

PAIR status

Continuous Access Synchronous

NoYes, if volumes are in SMPL

status

Deleted pair volumes from MCU

NoYes, if volume is in SMPL

status

Deleted S-VOL from MCU

NoYes, if volume is in SMPL

status

Deleted P-VOL from RCU

NoYesA volume in suspended,

simplex, or duplex status

Continuous Access Synchronous Z

NoYes, if volume is in

suspended status

An external M-VOL

NoYes, if volume is in simplex

status

An external R-VOL

NoYes.

NOTE: The target volume

must be in the same CLPR.

A data volume pairContinuous Access Journal and Continuous Access Journal Z

NoNoA journal volume

NoYes.

NOTE: The target volume

must be in the same CLPR.

A primary volume in any

status

Continuous Access Journal

NoYes.

NOTE: The target volume

must be in the same CLPR.

A secondary volume in PSUS

status

NoNoA volume in COPY or PAIR

status

NoYes.

NOTE: The target volume

must be in the same CLPR.

A primary volume in any

status

Continuous Access Journal Z

Supported and prohibited source and target volumes 11

Page 12

Table 2 Candidates for Source and Target Volumes by Program Product (continued)

Target Volume Candidate?Source Volume Candidate?Volume Type/StatusProgram Product

NoYes.

NOTE: The target volume

must be in the same CLPR.

A secondary volume in suspend status

NoNoA volume in Pending Duplex

or Duplex status

Yes, but only if the volume is in suspended status

NoA normal volumeCompatible XRC

NoNoA virtual volumeSnapshot

NoNoA pool volume

NoYesSS pair volumes

NoYes, if in PAIR statusP-VOL

NoNoS-VOL

NoYesBC pair volumesBusiness Copy and Business

Copy for Mainframe

NoYesA reserved BC volume

NoYesA P-VOL in an BC pair where the P-VOL to S-VOL ratio is 1:1 or 1:2

NoNoA P-VOL in an BC pair where the P-VOL to S-VOL ratio is 1:3

NoYesAn S-VOL in an BC pair where the P-VOL to S-VOL ratio is 1:1, 1:2, or 1:3

NoYesA P-VOL in an L1 cascaded BC pair where the P-VOL to S-VOL ratio is 1:1 or 1:2

NoNoA P-VOL in an L1 cascaded BC pair where the P-VOL to S-VOL ratio is 1:3

NoYesA P-VOL in an L2 cascaded BC pair where the P-VOL to S-VOL ratio is 1:1

NoNoA P-VOL in an L2 cascaded BC pair where the P-VOL to S-VOL ratio is 1:2

NoYesAn S-VOL in an L1 cascaded BC pair where the P-VOL to S-VOL ratio is 1:1, 1:2, or 1:3

NoNoAn S-VOL in an L2 cascaded BC pair where the P-VOL to S-VOL ratio is 1:1 or 1:2

NoNoA volume in COPY (SP) or PSUS (SP) status

Business Copy

NoNoA volume in SP-Pend or V-Split status

Business Copy Z

12 Requirements

Page 13

Table 2 Candidates for Source and Target Volumes by Program Product (continued)

Target Volume Candidate?Source Volume Candidate?Volume Type/StatusProgram Product

NoNoA volume with data stored

in cache

Cache Residency and Cache Residency Z

NoYesIndividual LDEV within

expanded LU

LUN Expansion (LUSE)

NoYes. If all LDEVs are used,

make sure that an adequate

All LDEVs in an expanded LU

amount of target volumes are reserved.

NoNoA volume undergoing an Auto LUN operation via RAID Manager

RAID Manager

NoNoA volume having the Read Only or Protect attribute turned on

Volume Retention

NoNoA volume having the Read Only or Protect attribute turned on

Data Retention

NoNoA volume disabled to be used as a secondary volume

Auto LUN with Thin Provisioning virtual volumes

You can perform a manual migration plan on a Thin Provisioning virtual volume or an external volume. However, you cannot examine the estimated usage rate after the migration because the usage rate of an external volume cannot be collected.

The following table summarizes the internal volume and Thin Provisioning virtual volume (V-VOL) combinations under which a volume migration plan can be created.

Table 3 Permissible Internal and V-VOL Combinations

V-VOL in Normal State as Target Volume

Internal Volume as Target VolumeSource Volume

A migration plan can be created. If operations change the configuration of the storage system after the initial

A migration plan can be created.Internal Volume

volume migration, any subsequent volume migration must be executed at an interval which is calculated by the following formula:

(Pool_Capacity x 3 (seconds)) + 40 (minutes)

A migration plan can be created. A warning message appears if there is a

A migration plan can be created.V-VOL in Normal state

possibility that the data size may exceed the pool threshold after migration.

A migration plan can be created. A warning message appears if there is a

A migration plan can be created.V-VOL in Blocked state due to full

capacity

possibility that the data size may exceed the pool threshold after migration.

The migration plan might not be executed if the storage system is experiencing a heavy workload.

Auto LUN with Thin Provisioning virtual volumes 13

Page 14

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.

If the capacity of a Thin Provisioning virtual volume is increasing, this volume cannot be specified as the source or target volume in an Auto LUN plan. It will also be impossible to reserve or remove the reserve attribute for a virtual volume whose capacity is increasing. You must ensure that the capacity of a Thin Provisioning virtual volume is not increasing if you plan on using that virtual volume in an Auto LUN plan.

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. The following table lists the possible Internal/V-VOL - Continuous Access Synchronous/Continuous Access Journal pair combinations, and tells which type of volume should not be considered as a target volume based on the Continuous Access Synchronous/Continuous Access Journal pair combination and the selected source volume.

Table 4 Poor Target Volume Candidates for Cnt Ac-S/Cnt Ac-J Pair Combinations

Poor Target Volume CandidateSource VolumeContinuous Access Synchronous or

Continuous Access Journal Pair

Candidate

NoneInternal P-VOLInternal P-VOL, Internal S-VOL

V-VOLInternal S-VOL

Internal volumeInternal P-VOLInternal P-VOL, V-VOL S-VOL

V-VOLV-VOL S-VOL

NoneV-VOL P-VOLV-VOL P-VOL, Internal S-VOL

NoneInternal S-VOL

Internal volumeV-VOL P-VOLV-VOL P-VOL, V-VOL S-VOL

NoneV-VOL S-VOL

Auto LUN and Continuous Access Journal Z

You cannot select a volume in Pending Duplex or Duplex status as a source volume. Also, the source and target volumes must belong to the same CLPR. If you create a Continuous Access Journal Z pair for a delta resync operation in a 3DC multi-target

configuration, the primary volume or the secondary volume of the delta resync pair can be used as a source volume. To use the primary or secondary volume as a source volume, you must ensure that the status of each pair in the 3 DC multi-target configuration is as shown in Table 5 (page 15) and Table 6 (page 15).

14 Requirements

Page 15

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

StatusPair Name

SUSPEND or DUPLEXContinuous Access Synchronous Z pair

Any pair status can be acceptableContinuous Access Journal Z pair

Hold or HldeContinuous Access Journal Z pair for delta resync operation

Table 6 Pair status when S-VOL of Continuous Access Journal Z delta resync pair is a source volume

StatusPair Name

Any pair status can be acceptableContinuous Access Synchronous Z pair

SUSPENDContinuous Access Journal Z pair

Hold or HldeContinuous Access Journal Z pair for delta resync operation

Also, the source and target volumes must belong to the same CLPR.

Auto LUN and Continuous Access Journal

You cannot select a volume in COPY or PAIR status as a source volume. If you create a Continuous Access Journal pair for a delta resync operation in a 3DC multi-target

Also, the source and target volumes must belong to the same CLPR.

Auto LUN and Continuous Access Journal 15

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

StatusPair Name

PSUS or PAIRContinuous Access Synchronous pair

Any pair status can be acceptableContinuous Access Journal pair

HOLD or HLDEContinuous Access Journal pair for delta resync operation

Table 8 Pair status when S-VOL of Continuous Access Journal delta resync pair is a source volume

StatusPair Name

Any pair status can be acceptableContinuous Access Synchronous pair

PSUSContinuous Access Journal pair

HOLD or HLDEContinuous Access Journal pair for delta resync operation

16 Requirements

Page 17

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. If you want more than eight migration plans, you must click Apply multiple times. The number of migration plans that can be executed concurrently might be restricted based on emulation types and sizes of the migrated volumes, and on the resources being used by other programs.

Be careful not to perform manual migration operations while the Auto Migration function is enabled. If you do perform manual migration plans while the Auto Migration function is enabled, all auto migration plans in progress will be canceled. A manual migration operation is not allowed when the current write pending rate for the storage system is 60 percent or higher.

Estimating differential tables

Differential tables are resources shared by Auto LUN, Snapshot, Business Copy, Business Copy Z, and Compatible FlashCopy. Because an Auto LUN source volume still accepts I/O write operation during an Auto LUN operation, differential tables are used to track and copy the differential data to the target volume, which ultimately becomes the migrated volume. The subsequent sections provide formulas for estimating the amount of differential and pair tables that you will need per migration plan.

Calculating the required amount of differential tables for a mainframe volume

When you migrate mainframe volumes, you must determine the total number of required differential tables and pair tables per migration plan. Use the following equation to calculate the required amount of differential tables. Figures are rounded up to the nearest whole number.

Total number of the differential tables per migration plan = (X + Y) × 15 ÷ Z The variables are explained below:

• X: The number of volume cylinders to be migrated. If the volume is divided by the Virtual LVI

function, this value is the number of cylinders in the divided volume.

• Y: The number of control cylinders.

• Z: The number of slots that can be managed by a differential table.

Control cylinders by mainframe emulation type

Before you can calculate the required amount of differential tables per migration plan, you must know the number of control cylinders contained by the mainframe volume. The following table shows the number of control cylinders based on the emulation type.

Table 9 Number of Control Cylinders Based on Emulation Type

Number of Control CylindersEmulation Type

73380-3, 3380-3A, 3380-3B, 3380-3C

223380-F

73380-K, 3380-KA, 3380-KB, 3380-KC

63390-3, 3390-3A, 3390-3B, 3390-3C, 3390-3R

Manual migration plans 17

Page 18

Table 9 Number of Control Cylinders Based on Emulation Type (continued)

Number of Control CylindersEmulation Type

253390-9, 3390-9A, 3390-9B, 3390-9C

233390-L, 3390-LA, 3390-LB

533390-M, 3390-MA, 3390-MB, 3390-MC

233390-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)) × 15 ÷ Z (number of slots that can be managed by a differential table)

The number of volume cylinders for the 3390-3 emulation type is 3,339. The number of control cylinders for the 3390-3 emulation type is 6 (see the preceding table). The number of slots that can be managed by a differential table is 20,448. The formula is calculated below:

(3,339 + 6) x 15 / (20,448) = 2.453785211 When you round up 2.453785211 to the nearest whole number, it becomes 3. Therefore, the

total number of required differential tables for each migration plan is 3 when the emulation type is 3390-3.

One pair table can be used for 36 differential tables. Therefore, the number of pair tables for one migration plan is 1 when the emulation type is 3390-3.

Calculating the required amount of differential tables for an open-system volume

When you migrate open-system volumes, you must determine the total number of required differential tables and pair tables per migration plan. The equation to calculate the required amount of differential tables will vary based on the emulation type. Figures are rounded up to the nearest whole number.

Control cylinders by open emulation type

Before you can calculate the required amount of differential tables per migration plan, you must know the number of control cylinders contained by the open-system volume. The following table shows the number of control cylinders based on the emulation type.

Table 10 Number of Control Cylinders and Capacity Based on Emulation Type

Control Cylinders (Capacity)Emulation Type

8 (5,760 KB)OPEN-3

27 (19,440 KB)OPEN-8, OPEN-9

19 (13,680 KB)OPEN-E

7 (5,040 KB)OPEN-L

0 (0 KB)OPEN-V

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

18 Auto LUN planning

Page 19

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. The formula is calculated below:

(3,019,898,880 ÷ 256) ÷ 20,448 = 576.9014085 When you round up 576.9014085 to the nearest whole number, it becomes 577. Therefore, the

total number of required differential tables for each migration plan is 577 when the emulation type is OPEN-V.

One pair table can be used for 36 differential tables. Therefore the number of pair tables for one migration plan is 17 when the emulation type is OPEN-V.

Differential tables calculation for other open emulation types

The following equation is used to calculate the required amount of differential tables for OPEN-3, OPEN-8, OPEN-9, OPEN-E, and OPEN-L volumes.

Total number of the differential tables per migration plan = (X ÷ 48 + Y × 15) ÷ 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. The Virtual LVI function is not available for OPEN-L volumes.

• Y: The number of control cylinders.

• Z: The number of the slots that can be managed by a differential table.

If the emulation type of a volume is OPEN-3, the capacity is 2,403,360 (in kilobytes) and the number of control cylinders is 8. Both of these figures are provided in the preceding table. The number of slots that can be managed by a differential table is 20,448. The formula is calculated below:

(2,403,360 ÷ 48 + 8 × 15) ÷ 20,448 = 2.454518779 When you round up 2.454518779 to the nearest whole number, it becomes 3. Therefore, the

total number of required differential tables for each migration plan is 3 when the emulation type is OPEN-3.

One pair table can be used for 36 differential tables. Therefore the total number of the pair tables for one migration plan is 1 when the emulation type is OPEN-3.

Running concurrent manual migration plans

The number of manual migration plans that can be executed concurrently depends on the following conditions:

• The amount of shared memory available for differential tables. You can install additional

shared memory for differential tables. If additional shared memory for differential tables is

Running concurrent manual migration plans 19

Page 20

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. You may use 16,384 pair tables if additional shared memory for pair tables is installed.

To install additional shared memory for pair tables, call HP Technical Support.

• The emulation type and capacity of each volume to be migrated.

The number of differential tables and pair tables needed to migrate one volume differs based on the emulation type and size of the volume. For the number of differential tables and pair tables needed for migrating a mainframe volume, see “Calculating the required amount of

differential tables for a mainframe volume” (page 17). For the number of differential tables

needed for migrating an open-system volume, see “Calculating the required amount of

differential tables for an open-system volume” (page 18).

Estimating the number of concurrent manual migration plans

The following conditional expression can be used to estimate the maximum number of migration plans that can be executed concurrently:

Σ(α) ≤ (β) and Σ(γ) ≤ (δ) The variables are explained below:

• Σ (α): total number of differential tables needed for migrating all volumes.

• (β): total number of differential tables available in the storage system.

• Σ (γ): total number of pair tables needed for migrating all volumes.

• (δ): total number of pair tables available in the storage system.

As calculated in “Differential tables calculation for an OPEN-V volume” (page 18), the number of differential tables required for each migration plan for an OPEN-3 volume is 3, and the number of required pair tables for each migration plan is 1. If you want to create 20 migration plans of OPEN-3 volumes, 60 differential and 20 pair tables are required. These numbers are plugged into the original equation:

[ (3 x 20) = 60 ] ≤ 26,176 and [ (1 x 20) = 20 ] ≤ 8,192 Because this expression is true, you can create all 20 migration plans for the OPEN-3 volumes. In the preceding calculation, it is assumed that only Auto LUN is running. However, as mentioned

earlier, differential tables are resources that are also shared by Snapshot, Business Copy, Business Copy for Mainframe, and Compatible FlashCopy. The total number of pair tables used by Business Copy, Business Copy for Mainframe, Compatible FlashCopy and Auto LUN should be within the value of (β) and (δ). For details on how to calculate the number of differential tables and pair tables used by the programs other than Auto LUN, see the manuals of the corresponding products.

Fixed parity groups

If the Auto Migration function is enabled, some volumes and parity groups might experience degraded I/O speeds. For example, if volume 00:00:01 is migrated from the parity group Grp1-1 of class A to the parity group Grp-2-1 of class B, volume 00:00:01 is migrated to a lower-speed hard disk drive and might suffer a delay in I/O speed. If you specify Grp1-1 as a fixed parity group, volumes in Grp1-1 will not be migrated to any other parity group, and no volumes will be migrated to Grp1-1. This action protects a parity group from degraded I/O speeds.

NOTE: In a manual migration plan, you can specify a volume in a fixed parity group as a target

or a source volume.

20 Auto LUN planning

Page 21

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.

Auto LUN allows you to automate the creation and execution of migration plans. If you automate creation and execution of migration plans, Auto LUN analyzes usage rates of storage system resources and the speed of hard disk drives at specified intervals, and then auto migration plans are performed at the specified migration time.

Auto Migration Parameters 21

Page 22

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).

• The user has permission to access the source and target volume

• The volumes meet all requirements as source and target volume candidates

Procedure 1 To migrate a volume manually:

1. Click Actions→Other Function→Auto LUN.

2. Click to change to Modify mode.

3. In the Monitoring Term section, specify the starting time and ending time to collect performance and usage statistics, and click Apply.

In a later step, a graph will be created based on this specified period.

NOTE: Do not include the period when an error occurred. Resource usage can become

unbalanced when the storage system experiences an error.

4. In the Auto LUN window, click Auto LUN. A different window appears.

5. Click the Manual Plan tab to display the “Manual Migration window” (page 47).

6. In the navigation tree, click the parity group that contains the volume you want to migrate. To display the usage rate of the parity groups, click Display usage rate.

The volumes contained in the selected parity group load in the “LDEVs list” (page 50).

7. In the “LDEVs list” (page 50), select the volume you want to migrate and then click Target. The “Target (Reserved) LDEV list” (page 50) displays the reserved volumes that can be used

as a target volume.

8. In the “Target (Reserved) LDEV list” (page 50), select the target volume.

9. Click Graph to check the estimated results after the migration plan is executed. The Graph window opens.

22 Auto LUN operations

Page 23

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.

The line graph illustrates the past usage rates of the source volume and the target volume.

10. If the estimate shows acceptable disk performance, click Close and go to the next step. If not,

restart at the beginning of this task and select a different source and/or target volume.

11. Click Set to add the new migration plan.

12. Click Apply to apply the settings to the storage system. The migration process starts and the % column displays the progress. A completed migration

plan disappears from the list.

Deleting a manual migration plan

There may be an occasion when you want to delete a manual migration plan.

Procedure 2 To delete a manual migration plan:

1. Click Actions→Other Function→Auto LUN to open the Auto LUN window.

2. Click to change to Modify mode.

3. In the Auto LUN window, click Auto LUN. A different window appears.

4. Click the Manual Plan tab to display the “Manual Migration window” (page 47).

5. Select a manual migration plan and click Delete.

6. Click Apply.

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.

Deleting a manual migration plan 23

Page 24

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:

1. Click Actions→Other Function→Auto LUN to open the Auto LUN window.

2. Click to change to Modify mode.

3. In the Auto LUN window, click Auto LUN. A different window appears.

4. Click the Auto Plan tab to display the “Auto Plan window” (page 52).

5. Set the Auto Refresh option to Enable or Disable. If Auto Refresh is enabled, the progress of

migration plans are updated in real time, and if a new plan is created, the new plan will automatically be added to the list. If Auto Refresh is disabled, information in the list will not be updated automatically.

6. In the Sampling Term section, select one of the following Date options:

• None: migration plans will not be created

• Every day: migration plans are created daily

• Once every X days: migration plans are created every X days. An integer value for ‘X’

is specified in the drop-down list

• Once a week: migration plans are created once a week on the day specified in the

drop-down list

• Once a month: migration plans are created once a month on the day specified in the

drop-down list

7. In the Sampling Term section, specify values in the From and To fields to set the time range

for which to collect disk usage rate statistics.

8. In the Number of Sampling Points section, select the All sampling points option to analyze all

average usage rates collected during the sampling term. To analyze only the X highest average usage rates in the sampling term, select the X highest sampling points and then set the value of X from the drop-down list.

9. In the Migration Time section, use the drop-down lists to specify the time to start auto migration operations. The Migration Time must be at least 60 minutes later than the specified Sampling Term end time and 15 minutes plus the Max. Migration duration value earlier than the Sampling Term start time. The Max. Migration duration value can range from 10 to 120 minutes. It is recommended that you specify a time when disk usage rates are low because volume migrations might impose heavy workloads on hard disk drives.

10. Optionally, edit the following values in the Auto Migration Conditions section:

• Max. migration duration: the time limit for auto migrations. If the time limit is reached,

Auto LUN cancels all incomplete operations.

• Max. disk utilization: the global disk usage limit for parity groups. If a parity group’s disk

usage rate exceeds this limit, all auto migration plans involving this parity group are cancelled.

• Max. number of vols for migration: the maximum number of volumes that can be migrated

through auto migration at the same time.

11. If not already enabled, set the Auto Migration function to Enable.

12. Click Set to apply the settings to the storage system.

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.

24 Auto LUN operations

Page 25

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:

1. Click Actions→Other Function→Auto LUN to open the Auto LUN window.

2. Click to change to Modify mode.

3. In the Auto LUN window, click Auto LUN. A different window appears.

4. Click the Auto Plan tab to display the “Auto Plan window” (page 52).

5. To delete one or more auto migration plans, select an auto migration plan in the list and click

Delete. All auto migration plans below the selected auto migration plan are also deleted. Click Delete All to delete all auto migration plans in the list.

6. Click Apply.

Recreating auto migration plans

If auto migration operations did not produce enough improvements in disk access performance, you can discard the current auto migration plans and make new auto migration plans.

Procedure 5 To make new auto migration plans:

1. If necessary, change the disk usage rate limit for an HDD class. For details, see “Changing

disk usage rate limit for an HDD class” (page 27).

2. Click Actions→Other Function→Auto LUN to open the Auto LUN window.

3. Click to change to Modify mode.

4. In the Auto LUN window, click Auto LUN. A different window appears.

5. Click the Auto Plan tab to display the “Auto Plan window” (page 52).

6. As needed, modify any auto migration plan parameters. For details, see “Setting up auto

migration plan parameters” (page 24).

7. Click Make New Plan. All the existing auto migration plans are deleted and new auto migration plans are created

based on the new settings.

Deleting auto migration plans 25

Page 26

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:

1. Click Actions→Other Function→Auto LUN to open the Auto LUN window.

2. Click to change to Modify mode.

3. In the Auto LUN window, click Auto LUN. A different window appears.

4. Click the Auto Plan tab to display the “Auto Plan window” (page 52).

5. Click Delete All to stop all current auto migration plans.

6. Set the Auto Migration function to Disable.

7. Click Set to apply the settings to the storage system.

Reserving a volume

To perform manual or auto migration, volumes in a HDD class must be in Reserve status to be considered as target volume candidates. Auto LUN cannot take place when no volumes are reserved.

Prerequisites

• The volume meets all requirements as a target volume candidate

Procedure 7 To reserve a volume:

1. Click Actions→Other Function→Auto LUN to open the Auto LUN window.

2. Click to change to Modify mode.

3. In the Auto LUN window, click Auto LUN. A different window appears.

4. Click the Attribute tab to display the “Attribute window” (page 55).

5. 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.

6. 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 57).

26 Auto LUN operations

Page 27

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

8. Click Apply to reserve the volume.

An 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.

Fixing a parity group

If you specify a parity group as fixed, the parity group will not experience degraded I/O speeds as auto migration will not be possible to or from this parity group.

NOTE: A volume in a fixed parity group can be selected as a target or source volume for a

manual migration plan.

Procedure 8 To fix a parity group

1. Click Actions→Other Function→Auto LUN to open the Auto LUN window.

2. Click to change to Modify mode.

3. In the Auto LUN window, click Auto LUN. A different window appears.

4. Click the Attribute tab to display the “Attribute window” (page 55).

5. In the navigation tree, double-click an HDD class folder to view parity groups.

6. Fixed parity groups are indicated with a icon, so select a parity group without this icon that you want to exclude from auto migration operations.

7. Right-click the parity group and select Fixed PG from the pop-up menu.

8. Click Apply.

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.

Procedure 9 To change the disk usage rate limit for an HDD class:

1. Click Actions→Other Function→Auto LUN to open the Auto LUN window.

2. Click to change to Modify mode.

3. In the Auto LUN window, click Auto LUN. A different window appears.

4. Click the Attribute tab to display the “Attribute window” (page 55).

5. In the navigation tree, right-click an HDD class folder and then select Change Class Threshold from the pop-up menu.

The Change Threshold window appears.

6. From the Threshold list, select the value for the disk usage rate limit and then click OK. In the navigation tree, the threshold value appears to the right of the HDD class.

7. Click Apply to apply the specified limit to the storage system.

Viewing the migration history logs

The History window displays logs of auto migration operations and manual migration operations.

Procedure 10 To view migration logs:

1. Click Actions→Other Function→Auto LUN to open the Auto LUN window.

Fixing a parity group 27

Page 28

2. Click to change to Modify mode.

3. In the Auto LUN window, click Auto LUN. A different window appears.

4. Click the History tab to open the “History window” (page 60).

28 Auto LUN operations

Page 29

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. The timestamp is in the following format: yyyy/mm/dd hh:min.

Auto migration general status messages

Table 11 (page 29) lists general status messages related to current auto migration plans.

Table 11 Auto Migration General Status Messages

DescriptionMessage

The parameters for creating auto migration plans were initialized.

Auto LUN failed to initialize the parameters for creating auto migration plans.

Failed to initialize the parameters for creating auto migration plans.

Auto LUN has started executing auto migration plans.The auto migration started.

The creation of individual auto migrations plans has started.The creation of auto migration plans started.

Auto LUN has already started the creation of auto migration plans.

The creation of auto migration plans has already been started.

The creation of auto migration plans finished.The creation of auto migration plans finished.

States the number of auto migration plans that were created. ‘N’ is an integer value that represents the number of plans.

N auto migration plan(s) were created.

Auto LUN has finished executing auto migration plans.The auto migration finished.

The execution of auto migration plans stopped unexpectedly because Auto LUN failed to obtain the monitoring data.

The auto migration stopped because the statistics could not be obtained.

The execution of auto migration plans stopped unexpectedly because the SVP was rebooted.

The auto migration stopped because the SVP was rebooted.

Auto LUN failed to create auto migration plans because the monitoring data could not be obtained.

Failed to create auto migration plans. The statistics could not be obtained.

The auto migration plan(s) were deleted.The auto migration plan(s) were deleted.

Auto LUN failed to execute an auto migration plan, so the remaining plans were deleted.

The remaining auto migration plans that were not executed were deleted.

The creation of auto migration plans failed due to missing hihsmatm.dat file under the C:\dkc200\others folder.

Failed to create auto migration plans. The C:\dkc200\ others\hihsmatm.dat file does not exist.

Auto migration messages 29

Page 30

Table 11 Auto Migration General Status Messages (continued)

DescriptionMessage

This message is output when you start Auto LUN in the following conditions:

Auto migration is not available. All the parity groups cannot be used for auto migration.

• 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 in the SVP. Contact the service engineer for information on resolving this issue.

An internal logic error occurred.

Successful auto migration plan messages

Table 12 (page 30) lists messages related to successful auto migration plans.

The LDKC:CU:LDEV and Group X-X variables in the Message column represent the LDEV ID and the parity group.

Table 12 Successful Auto Migration Plan Messages

DescriptionMessage

The stated auto migration plan was created. ‘NNN’ represents the number of the auto migration plan.

The auto migration plan NNN was created. Source = LDKC:CU:LDEV in Group X-X, Target = LDKC:CU:LDEV in Group X-X.

The execution of the stated auto migration plan was completed successfully. The first LDEV ID represents the source volume and the second LDEV ID represents the target volume.

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was executed normally.

Auto LUN found a proper target volume candidate corresponding to the specified source volume candidate. The source volume was migrated to a parity group in a higher HDD class.

Source candidate = LDKC:CU:LDEV in Group X-X Target candidate = LDKC:CU:LDEV in Group X-X

Auto migration of a volume to a higher HDD class.

Auto LUN found a proper target volume candidate corresponding to the specified source volume candidate. The source volume was migrated to a parity group in a lower HDD class.

Source candidate = LDKC:CU:LDEV in Group X-X Target candidate = LDKC:CU:LDEV in Group X-X

Auto migration of a volume to a lower HDD class.

Auto LUN found a proper target volume candidate corresponding to the specified source volume candidate. The source volume was migrated to a parity group in the same HDD class.

Source candidate = LDKC:CU:LDEV in Group X-X Target candidate = LDKC:CU:LDEV in Group X-X

Auto migration of a volume in the same HDD class.

Stopped auto migration plan messages

Table 13 (page 30) lists messages related to auto migration plans that were stopped abnormally.

The LDKC:CU:LDEV IDs in the Message column represent the source volume and target volume, respectively.

Table 13 Stopped Auto Migration Plan Messages

DescriptionMessage

The execution of the auto migration plan was stopped because the specified target volume is not a reserved

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was stopped. The specified target volume is not the reserved volume. volume. This volume was changed to a normal volume after

the creation of the auto migration plan.

The emulation type of the source volume is different from that of the target volume. The volume configuration might

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was stopped. There is an emulation type mismatch between source and target volumes. have been changed after the creation of the auto migration

plan.

30 Auto LUN monitoring

Page 31

Table 13 Stopped Auto Migration Plan Messages (continued)

DescriptionMessage

The disk usage rate of the parity group including the source volume is over the specified limit. Or, the disk usage rate

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was stopped. The usage rate of the source volume is over

is unknown. If applicable, increase the Max. disk utilizationthe specified Max. disk utilization value, or the usage rate

is unknown. value in the Auto Plan Parameters section of the Auto Plan

window and reinstate the auto migration plan.

The migration plan failed due to an error indicated by the error code. ‘5205’ is the part code for Auto LUN and

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was stopped. The migration failed. Error code: 5205-NNNN. ‘NNNN’ represents the error number. For information on

the error and recommended action, see the HP P9000 Remote Web Console Messages document.

The size of the source volume is different from that of the target volume. The volume configuration might have been changed after the creation of the auto migration plan.

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was stopped. There is a volume size mismatch between source and target volumes.

The emulation type of the specified target volume is not supported. The volume configuration might have been changed after the creation of the auto migration plan.

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was stopped. Unsupported emulation type.

The check of the disk usage rate of the parity group including the source volume ended abnormally. Contact the service engineer for information on resolving this issue.

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was stopped. Failed to check the usage rate of the source volume.

The check of the target volume ended abnormally. Contact the service engineer for information on resolving this issue.

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was stopped. Failed to check the target volume.

An unknown error occurred while checking the target volume. Contact the service engineer for information on resolving this issue.

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was stopped. An unknown error occurred in checking target volumes.

The encryption status of the source volume is different from that of the target volume. The volume configuration might

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was stopped. There is an encryption status mismatch between source and target volumes. have been changed after the creation of the auto migration

plan.

Failed auto migration plan messages

Table 14 (page 31) lists messages related to failed auto migration plans.

The Class X and Group X-X variables in the Message column represent the HDD class and parity group where the error occurred.

Table 14 Failed Auto Migration Plan Messages

DescriptionMessage

Auto LUN could not specify a proper target volume for creating an auto migration plan.

Failed to create auto migration plans. Failed to specify a proper target volume.

Error location: Class X Group X-X

There are insufficient data for creating auto migration plans. Check the Sampling Term and Number of Sampling

Failed to create auto migration plans. Insufficient statistics data in the sampling term.

Points settings in the Auto Plan window to see if monitoring

Error location: Class X Group X-X

data is being properly acquired. Make any necessary adjustments and attempt to collect the data again.

There is an insufficient amount of reserved volumes for creating auto migration plans. If Auto LUN failed to obtain

Failed to create auto migration plans. Insufficient reserved volumes.

the specified information, check the Reserve volumes in the Attribute window.

Error location: Class X Group X-X

Auto LUN failed to obtain specified information or statistics which are required for creating auto migration plans.

Failed to create auto migration plans. Failed to obtain XXXXXXXXXX.

‘XXXXXXXXXX’ represents the information or statistics that

Error location: Class X Group X-X

Auto migration messages 31

Page 32

Table 14 Failed Auto Migration Plan Messages (continued)

DescriptionMessage

Auto LUN failed to obtain. Check the settings and values specified in the Auto Plan Parameters of the Auto Plan window.

Auto LUN failed to get specified information required for creating auto migration plans. ‘XXXXXXXXXX’ represents

Failed to create auto migration plans. Failed to get XXXXXXXXXX.

the information that Auto LUN failed to get. Contact the service engineer for information on resolving this issue.

Error location: Class X Group X-X

Auto LUN failed to write in information required for creating auto migration plans. ‘XXXXXXXXXX’ represents the

Failed to create auto migration plans. Failed to write in XXXXXXXXXX.

information that Auto LUN failed to write. Contact HP Technical Support for information on resolving this issue.

Error location: Class X Group X-X

Auto LUN failed due to invalid data. ‘XXXXXXXXXX’ represents the invalid data or statistics. Check the settings

Failed to create auto migration plans. Invalid XXXXXXXXXX. Error location: Class X Group X-X

and values specified in the Auto Plan Parameters of the Auto Plan window. Contact HP Technical Support for information on resolving this issue.

Auto LUN failed to allocate the memory for creating auto migration plans. Contact the service engineer for information on resolving this issue.

Failed to create auto migration plans. Memory allocation error.

Error location: Class X Group X-X

Auto LUN could not find a proper candidate for the target volume. The parity group to which the target volume

Source candidate = LDKC:CU:LDEV in Group X-X Failed to specify a proper target volume for this source

candidate. The parity group of the target candidate

candidate belongs includes a volume that was migrated in the specified sampling term.

includes a volume that was migrated in the specified sampling term.

Auto LUN could not find a proper candidate for the target volume. There is a risk of the HDD class disk usage rate

Source candidate = LDKC:CU:LDEV in Group X-X Failed to specify a proper target volume for this source

candidate. The disk usage rate of the parity group might exceed the class threshold.

exceeding the Max. disk utilization threshold value. Check the disk usage rate for the HDD class and adjust the Max. disk utilization value if necessary.

Auto LUN could not find a proper candidate for the target volume. There is an insufficient number of reserved volumes.

Source candidate = LDKC:CU:LDEV in Group X-X Failed to specify a proper target volume for this source

candidate. Insufficient reserved volumes.

The auto migration plan was canceled because the duration of the migration exceeded the time specified in the Max.

The auto migration plan (LDKC:CU:LDEV->LDKC:CU:LDEV) was canceled because of timeout.

Migration duration field of the Auto Plan window. The first LDEV ID represents the source volume and the second LDEV ID represents the target volume.

The auto migration plan was canceled because the specified parity group information is incorrect. The

The auto migration plan (LDKC:CU:LDEV (X-X)->LDKC:CU:LDEV (X-X)) was canceled because of invalid parity group information. correspondence between the source or target volume and

the parity group is invalid. The source volume might have been migrated manually after the creation of the auto migration plan. The first LDEV ID represents the source volume and the second LDEV ID represents the target volume.

There are some invalid samples in the parity group that were not used to create auto migration plans. ‘N’

In Group X-X, there are N invalid samples. These samples were not used for creating the auto migration plans.

represents the number of invalid samples. If there is only one invalid sample, this message is shown as “...there

is invalid sample. This sample was...”

Due to too much invalid data in the volume, Auto LUN created auto migration plans without using this volume.

There is too much invalid data in Group X-X LDKC:CU:LDEV. Hence this volume was not used to create the auto migration plans.

32 Auto LUN monitoring

Page 33

Migration History messages

The following table contains the messages that appear in Migration History logs.

Table 15 Migration History Log Messages

DescriptionMessage

The migration operation started.Migration Started

The migration operation completed successfully.Migration Completed

The migration operation was canceled by the user.Migration Canceled by User

The migration operation failed.Migration Failed

The migration operation was canceled by Auto LUN (e.g., volume usage rate exceeded specified maximum).

Migration Canceled by Controller

Because each program product started processing, the migration operation was canceled by Auto LUN.

Migration Canceled by Business Copy Migration Canceled by Continuous Access Migration Canceled by Controller Migration Canceled by Continuous Access Journal Migration Canceled by Compatible XRC Migration Canceled by Concurrent Copy

Copy Threshold option

The Copy Threshold option can be configured to temporarily stop Auto LUN operations when activity on the storage system becomes heavy. The use of this option is not recommended for hosts that frequently update volumes which are likely to be migrated because of the increased possibility of failure during migration.

For information about setting the Copy Threshold option, call HP Technical Support. The Copy Threshold option also stops migration operations associated with the following products:

• Business Copy

• Business Copy Z

• Compatible FlashCopy

• Snapshot

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. The increase in copy time may be as much as doubled and depends on the number of pairs set to the program product.

Migration History messages 33

Page 34

Table 16 Estimated Delay in Copy Time for Auto LUN and Other Program Products

Estimated delay in copying speed (in minutes)Capacity of Migrated Volume (MB)

40 - 1,000

181,001 - 5,000

375,001 - 10,000

18610,001 - 50,000

37250,001 - 100,000

1,860100,001 - 500,000

3,720500,001 - 1,000,000

9,6671,000,001 - 2,150,400

The estimates in Table 16 (page 34) are calculated based on the assumption that the workload for update I/Os for the migrated volume is 50 IOPS for one volume.

Best practices

Do not perform Auto LUN operations during storage system maintenance activities (such as, installation, replacement, removal of cache or drives, configuration changes, or replacement of the microcode).

CAUTION: If a volume migration operation of Auto LUN is in progress and the SVP is in Modify

mode, the Auto LUN process might not complete and the volume might continue to be migrated. In this case, make sure that the SVP is in View mode.

Before turning off the power on the storage system, confirm that all Auto LUN operations are complete. If you turn off the power of the storage system during Auto LUN operations, and power is later restored, Auto LUN operations resume, but there is a risk that data may be lost from the shared memory. If this happens, Auto LUN begins recopying all data, both the differential data not yet migrated as well as the data previously copied to the target volume before the power interruption.

34 Auto LUN monitoring

Page 35

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. For information on other error codes displayed on the Remote Web Console web client, see the HP P9000 Remote Web Console Messages.

Troubleshooting Auto LUN 35

Page 36

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

HP recommends that you register your product at the Subscriber's Choice for Business website:

http://www.hp.com/go/e-updates

After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources.

Documentation feedback

HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to

storagedocsfeedback@hp.com. Include the document title and manufacturing part number. All

submissions become the property of HP.

Related information

The following documents [and websites] provide related information:

• HP P9000 RAID Manager User Guide

• HP P9000 Remote Web Console Messages

• HP P9000 Remote Web Console User Guide

You can find these documents on the Manuals page of the HP Business Support Center website:

http://www.hp.com/support/manuals

In the Storage section, click Disk Storage Systems for hardware or Storage Software for software, and then select your product.

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

36 Support and other resources

Page 37

• 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,0002bytes

• 1 GB (gigabyte) = 1,0003bytes

• 1 TB (terabyte) = 1,0004bytes

• 1 PB (petabyte) = 1,0005bytes

• 1 EB (exabyte) = 1,0006bytes

P9000 disk arrays use the following values to calculate logical storage capacity values (logical devices):

• 1 KB (kilobyte) = 1,024 bytes

• 1 MB (megabyte) = 1,0242bytes

• 1 GB (gigabyte) = 1,0243bytes

• 1 TB (terabyte) = 1,0244bytes

• 1 PB (petabyte) = 1,0245bytes

• 1 EB (exabyte) = 1,0246bytes

Typographic conventions

Table 17 Document conventions

ElementConvention

Cross-reference links and e-mail addressesBlue text: Table 17 (page 37)

Website addressesBlue, underlined text: http://www.hp.com

Bold text

• Keys that are pressed

• Text typed into a GUI element, such as a box

• GUI elements that are clicked or selected, such as menu

and list items, buttons, tabs, and check boxes

Text emphasisItalic text

Monospace text

• File and directory names

• System output

• Code

• Commands, their arguments, and argument values

Monospace, italic text

• Code variables

• Command variables

Emphasized monospace textMonospace, bold text

WARNING! Indicates that failure to follow directions could result in bodily harm or death.

Conventions for storage capacity values 37

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.

38 Support and other resources

Page 39

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.

Figure 9 Auto LUN Pairs and RAID Manager Commands

The status of a pair can be checked by using the pairdisplay RAID Manager command.

Migrating volumes manually with RAID Manager

In this example, group1 represents the group name in the RAID Manager configuration definition file, and pair1 represents the name of the volume whose pair is the target volume of the operation.

Procedure 11 To perform a manual migration using RAID Manager commands:

1. Start RAID Manager.

2. Type the following command for a SMPL pair to start volume migration:

paircreate -g group1 -d pair1 -m cc -v1

When volume migration starts, the status of the pair changes to COPY.

3. Type the following command to check the status of the pair:

pairdisplay –g group1 –d pair1 -fcex

When volume migration completes, the status of the pair changes to PSUS. If volume migration fails, the status of the pair changes to PSUE.

4. Type the following command to change the pair status back to SMPL:

pairsplit –S –g group1 –d pair1

If the migration fails (the status of the pair becomes PSUE), repeat steps 2 and 3. If you are unable to change the pair status back to SMPL, contact HP Technical Support.

Auto LUN and RAID Manager commands 39

Page 40

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.

• Click File→Refresh All on the menu bar of the Remote Web Console main window to check

RAID Manager settings in Remote Web Console.

• While the microcode is being downgraded or upgraded, users must not perform any operations

that the resulting microcode would not support.

• If you delete a manual 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 Manual Plan window and confirming the existence of the manual 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.

• When you delete a manual Auto LUN plan, you should wait until the status of the volume

changes from SMPL(PD) to SMPL (usually about 10 seconds) before executing another Auto LUN operation through RAID Manager.

• When you attempt to migrate a volume or cancel a migration plan through RAID Manager,

you might encounter an "EX_CMDRJE" exception and the command might be refused depending on the condition in the DKC.

Troubleshooting when using RAID Manager

When you execute or cancel a manual Auto LUN plan through RAID Manager, you might identify the cause of the error by referring to the log displayed on the RAID Manager window or in the RAID Manager operation log file.

The RAID Manager operation log file is stored in:

/HORCM/log*/curlog/horcmlog_HOST/horcm.log

Where:

• * is the instance number.

• HOST is the host name.

The following figure shows an example of error log message in the RAID Manager window.

Figure 10 Example of a Log Displayed on The RAID Manager Window

Table 18 (page 40) shows the RAID Manager error messages related to executed or canceled

manual migration plans.

Table 18 RAID Manager Errors Related to Manual Migration Plans

Required ActionMessageError Code

(SSB2)

Check the configuration definition file.The cache mode does not match between the migration source volume and the migration target volume.

2027

Release the volume from Data Retention, and then

migrate the volume.

The migration target volume is being used with Data Retention.

2051

40 Using RAID Manager for manual Auto LUN

Page 41

Table 18 RAID Manager Errors Related to Manual Migration Plans (continued)

Required ActionMessageError Code

(SSB2)

The volume cannot be migrated. Check the configuration definition file

The migration source volume is a quorum disk.2039

The volume cannot be migrated. Check the configuration definition file.

The migration target volume is a quorum disk.203a

Specify a volume whose capacity is supported.The current microcode does not support the

capacity of the migration source volume.

204A

Specify a volume whose capacity is supported.The current microcode does not support the

capacity of the migration source volume.

204B

Release the volume from Continuous Access Journal, and then migrate the volume.

The migration target volume is being used with Continuous Access Journal.

2055

Release the volume from Continuous Access Journal, and then migrate the volume.

The migration source volume is being used with Continuous Access Journal.

2056

The source volume and target volume cannot belong to the same parity group. Select a source

The migration target volume and the migration source volume belong to the same parity group.

2058

volume and target volume from different parity groups.

Wait for the shredding operation to complete and then migrate the volume.

The migration source volume is being shredded.205A

Release the volume from Continuous Access Journal, and then migrate the volume.

The migration target volume is being used with Continuous Access Journal.

205C

Perform the following actions for each cause:The migration source volume corresponds to either

of the following causes:

2075

1. Change the Snapshot pair status to PAIR, and

then migrate the volume.1. The volume is P-VOL of the Snapshot pair. The

pair is not in PAIR status.

2. None. This migration plan cannot be executed.

2. The volume is S-VOL of the Snapshot pair or

V-VOL of Snapshot.

Perform the following actions for each cause:The migration target volume corresponds to either

of the following causes:

2076

1. Release the Snapshot pair, and then migrate

the volume.1. The volume is P-VOL of the Snapshot pair.

2.2. None. This migration plan cannot be executed.The volume is S-VOL of the Snapshot pair or

V-VOL of Snapshot.

Release the pool-VOL setting of Snapshot from the volume, and then migrate the volume.

The migration source volume is the pool-VOL of Snapshot.

2078

Release the pool-VOL setting of Snapshot from the volume, and then migrate the volume.

The migration target volume is the pool-VOL of Snapshot.

2079

Wait for the quick formatting to complete and then migrate the volume.

The migration source volume is undergoing quick formatting.

2089

Wait for the quick formatting to complete and then migrate the volume.

The migration target volume is undergoing quick formatting.

208A

Associate the Thin Provisioning or Smart Tiers virtual volume with a pool, and then migrate the volume.

The migration target volume is the Thin Provisioning or Smart Tiers virtual volume which is not associated with a pool.

2090

Associate the Thin Provisioning or Smart Tiers virtual volume with a pool, and then migrate the volume.

The migration source volume is the Thin Provisioning or Smart Tiers virtual volume which is not associated with a pool.

2091

None. This migration plan cannot be executed.The migration target volume and the migration

source volume are the Thin Provisioning or Smart

2095

Troubleshooting when using RAID Manager 41

Page 42

Table 18 RAID Manager Errors Related to Manual Migration Plans (continued)

Required ActionMessageError Code

(SSB2)

Tiers virtual volumes that are associated with the same pool.

Release the pair containing the migration source

volume, and then migrate the volume.

The migration source volume is used by Continuous Access Synchronous or Continuous Access Journal.

2096

The migration target volume is a Thin Provisioning or Smart Tiers virtual volume.

Perform the migration plan at least 40 minutes

after the system configuration is changed.

The specified volume cannot be migrated because the information about system configuration updates due to volume migration is being backed up.

2098

None. This migration plan cannot be executed.The volume cannot be migrated if the emulation type of either the migration source volume or the

2099

migration target volume is OPEN-0V. To migrate the volume, ensure that the emulation type of both volumes is OPEN-0V.

None. This migration plan cannot be executed.Migration is not allowed between the normal volume specified as a LUSE volume and the Thin Provisioning or Smart Tiers virtual volume.

209A

Wait until the capacity increase is completed.

Then, you must specify a target volume which has

The migration source volume is a Thin Provisioning or Smart Tiers virtual volume whose capacity is increasing.

20A5

the same capacity as the volume whose capacity

is increased and migrate the volume.

Wait until the capacity increase is completed.

Then, you must specify a source volume which has

The migration target volume is a Thin Provisioning or Smart Tiers virtual volume whose capacity is increasing.

20A6

the same capacity as the volume whose capacity

is increased and migrate the volume.

Wait until the Thin Provisioning or Smart Tiers

virtual volume discards zero data, and then

migrate the volume.

The migration source volume is a Thin Provisioning or Smart Tiers virtual volume in which the zero data are being discarded.

20AD

Wait until the Thin Provisioning or Smart Tiers

virtual volume discards zero data, and then

migrate the volume.

The migration target volume is the Thin Provisioning or Smart Tiers virtual volume in which the zero data are being discarded.

20AE

Set an LU path to the volume and then migrate the

volume.

The volume specified as a migration source volume has no LU path.

20BA

Set an LU path to the volume and then migrate the

volume.

The volume specified as a migration target volume has no LU path.

20BB

Release the Compatible FlashCopy pair, and then

migrate the volume.

The migration source volume is the primary or secondary volume of Compatible FlashCopy.

22FA

Release the Compatible FlashCopy pair, and then

migrate the volume.

The migration target volume is the primary or secondary volume of Compatible FlashCopy.

22FB

Install Auto LUN, and then migrate the volume.Auto LUN is not installed on the storage system.2301

Check the configuration information of your

storage system.

The shared memory which is necessary to use Auto LUN is not installed or the initial setting is not completed.

2302

None. This migration plan cannot be executed.The LBA size does not match between the migration target volume and the migration source volume.

2306

Reduce the number of pairs set in the storage

system, and then migrate the volume.

The maximum number of pairs which can be set in the storage system is exceeded.

2309

42 Using RAID Manager for manual Auto LUN

Page 43

Table 18 RAID Manager Errors Related to Manual Migration Plans (continued)

Required ActionMessageError Code

(SSB2)

Cancel the reservation by Auto LUN, and then migrate the volume.

The migration target volume is already reserved by Auto LUN.

2311

Make the migration source volume off-line from the host, and then migrate the volume.

The migration source volume is online with the host.

2312

Release the Business Copy pair, and then migrate the volume.

The migration source volume is set as the leaf volume of Business Copy

2322

Release the Business Copy pair, and then migrate the volume.

The migration target volume is set as the secondary volume of Business Copy.

2328

Release the volume from Auto LUN, and then migrate the volume.

The migration source volume is already specified as the target volume of Auto LUN.

232F

Perform the following actions, respectively:Either of the following causes can be considered:2331

1) Cancel the reservation by Auto LUN, and then migrate the volume.

1) The migration source volume is already reserved by Auto LUN.

2) None. This migration plan cannot be executed.2) The number of slots does not match between the migration target volume and the migration source volume.

Reduce the number of pair settings of the specified volume, and then migrate the volume.

You cannot add pair settings any more to the volume specified as the migration source.

2332

None. The specified volume is not a source volume.

The volume specified by the migration cancellation is not a migration source volume

2333

None. This migration plan cannot be executed.The emulation type does not match between the migration target volume and the migration source volume.

2336

Release the Business Copy pair, and then migrate

the volume.

The migration source volume is a leaf volume of Business Copy.

2337

Release the Business Copy pair, and then migrate

the volume.

The migration target volume is a primary volume of Business Copy.

233B

Release the Business Copy pair, and then migrate

the volume.

The migration target volume is a secondary volume of Business Copy.

233C

Release the volume from Auto LUN, and then

migrate the volume.

The migration target volume is already specified as the target volume of Auto LUN.

2342

Release the Business Copy pair, and then migrate

the volume.

The migration target volume is set as the primary volume of Business Copy.

2343

None. The specified volume is not a target volume.The volume specified by the migration cancellation is not a migration target volume

2344

Release the Continuous Access Synchronous pair,

and then migrate the volume.

The migration target volume is a primary volume of Continuous Access Synchronous.

2346

Release the Continuous Access Synchronous pair,

and then migrate the volume.

The migration target volume is a secondary volume of Continuous Access Synchronous.

2347

Release the volume from Auto LUN, and then

migrate the volume.

The migration target volume is already specified as the source volume of Auto LUN.

234B

None. This migration plan cannot be deleted or

canceled.

The migration source volume is not paired with the migration target volume.

2350

None. This migration plan cannot be executed,

deleted, or cancelled.

The migration source volume and the migration target volume are set to the same volume.

2351

Troubleshooting when using RAID Manager 43

Page 44

Table 18 RAID Manager Errors Related to Manual Migration Plans (continued)

Required ActionMessageError Code

(SSB2)

None. This migration plan cannot be executed.The setting of VLL is different between the migration

target volume and the migration source volume.

2355

Release the Compatible XRC pair, and then migrate the volume.

The migration source volume is a primary volume of Compatible XRC.

2362

Release the Compatible XRC pair, and then migrate the volume.

The migration target volume is a primary volume of Compatible XRC.

2363

Release the IBM Concurrent Copy pair, and then migrate the volume.

The migration source volume is a primary volume of IBM Concurrent Copy (CC).

2365

Release the IBM Concurrent Copy pair, and then migrate the volume.

The migration target volume is a primary volume of IBM Concurrent Copy.

2366

Change the Continuous Access Synchronous pair status from COPY to PAIR or PSUS, or delete the

The volume is being used as the primary volume of the Continuous Access Synchronous pair. The pair is in the COPY status.

2368

Continuous Access Synchronous pair, and then migrate the volume.

Change the Continuous Access Synchronous pair status from COPY to PAIR or PSUS, or delete the

The volume is being used as the secondary volume of the Continuous Access Synchronous pair. The pair is in the COPY status.

2369

Continuous Access Synchronous pair, and then migrate the volume.

Migrate the volume after the Business Copy pair is changed to SPLIT status.

The migration source volume is the primary volume of a Business Copy pair which is in the SP-PEND status.

236A

Migrate the volume after the Business Copy pair is changed to SPLIT status.

The migration source volume is the secondary volume of a Business Copy pair which is in the SP-PEND status.

236B

Install the volume or select another source volume.The migration source volume is not installed.2370

Perform the following actions for each cause:The migration source volume corresponds to either

of the following causes:

2371

1) Recover the blocked volume, and then migrate the volume.1) The volume is blocked.

2) None. A system disk cannot be used as a source volume.

2) The volume is the system disk.

Migrate the volume after formatting is completed.The migration source volume is being formatted.2372

None. A command device cannot be used as a source volume.

The migration source volume is a command device.2373

Release the Continuous Access Synchronous pair, and then migrate the volume.

The migration source volume is an external volume specified as a primary volume of Continuous Access Synchronous.

237C

Install the volume or select another target volume.The migration target volume is not installed.2380

Perform the following actions for each cause:The migration target volume corresponds to either

of the following causes:

2381

1) Recover the blocked volume, and then migrate the volume.1) The volume is blocked.

2) None. A system disk cannot be used as a target volume.

2) The volume is the system disk.

Migrate the volume after formatting is completed.The migration target volume is being formatted.2382

None. A command device cannot be used as a source volume.

The migration target volume is a command device.2383

44 Using RAID Manager for manual Auto LUN

Page 45

Table 18 RAID Manager Errors Related to Manual Migration Plans (continued)

Required ActionMessageError Code

(SSB2)

Release the setting of Cache Residency, and then

migrate the volume.

Cache Residency is set on the migration source volume.

2389

Release the setting of Cache Residency, and then

migrate the volume.

Cache Residency is set on the migration target volume.

238A

None. LUSE volumes cannot be specified as source

volumes or target volumes.

The migration source volume and the migration target volume is specified as LUSE volumes.

238B

Cancel the reservation by Business Copy, and then

migrate the volume.

The migration target volume is a reserved volume of Business Copy.

238C

Make sure that the specified volume is created.The pair operation command was rejected because the specified volume is not available.

B911

Make sure that the specified secondary volume is

created.

The pair operation command was rejected because the specified secondary volume is not available.

B912

Specify the mirror ID from 0 to 2.The pair operation command was rejected because the mirror ID is invalid.

B913

Troubleshooting when using RAID Manager 45

Page 46

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 11 Auto LUN Window

DescriptionTypeItem

Enable: Performance Monitor is monitoring the storage system.fieldMonitoring Switch Disable: The storage system is not being monitored.

Specify a period in which to gather usage statistics and display in Performance Monitor’s lists and graphs.

sectionMonitoring Term

To set a date and time in the From and To fields, do either of the following:

• Move the sliders to the left or to the right to adjust the date and times.

• In the text box, select a date or time unit that you want to change and

then use the up or down arrows.

Starting and ending times for collecting statistics are displayed on both sides of the slide bars. Performance Monitor stores the monitoring data between these times,

For example, if you want to view usage statistics within the range of 10:30 July 1 2006 to 22:30 July 31 2006, you set 2006/07/01 10:30 in the From field, set 2006/07/31 22:30 in the To field, and then click Apply.

When you specify dates and time in the From and To fields, Performance Monitor calculates and displays the length of the specified period. The length of the period is in days.

From and To are unavailable if the monitoring data (that is, usage statistics) is not stored in the storage system.

Click Plan to open the Auto LUN window.buttonOpen Migration Dialog

Closes the window.buttonClose

Common elements

The top-level elements and the four tabs of the Auto LUN window are summarized in the following table.

DescriptionTypeItem

The starting and ending times for collecting performance and usage statistics for HDD classes, parity groups, and volumes.

fieldMonitoring Term

Auto LUN analyzes disk usage information collected by Performance Monitor during the monitoring period, and then calculates estimated usage rates of the

46 Auto LUN GUI reference

Page 47

DescriptionTypeItem

source and target parity groups after a proposed volume migration. The program does not calculate estimated usage rates of external volume groups.

Displays the data collection interval used in Performance Monitor. The default long range interval is 15 minutes.

fieldGathering Interval

Click the Manual Migration tab to open the Manual Migration Plans window. The Manual Migration Plans window is used to create and execute manual

tabManual Migration

migration plans. See “Manual Migration window” (page 47) for more information.

Click the Auto Migration tab to open the Auto Plan window. The Auto Plan window is used to manage Auto Migration plans and set Auto Migration parameters. See “Auto Plan window” (page 52) for more information.

tabAuto Migration

Click the Attribute tab to open the Attribute window. The Attribute window is used to reserve target volumes and view detailed information on HDD classes,

tabAttribute

parity groups, external volume groups, Thin Provisioning virtual volume groups, and individual volumes. See “Attribute window” (page 55) for more information.

Click the History tab to open the History window. The History window displays information about successful and failed Auto Migration and Manual Migration plans. See “History window” (page 60) for more information.

tabHistory

Manual Migration window

Figure 12 Manual Migration Window

The Manual Migration window is used to create and execute Manual Migration plans.

Manual Migration window 47

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)

DescriptionTypeItem

When you select the source volume in the “LDEVs list” (page 50) and click Target, the “Target (Reserved) LDEV list” (page 50) displays the list of target volumes.

buttonTarget

When you select the target volume in the “Target (Reserved) LDEV list”

(page 50) and click Graph, the Graph window opens. The Graph window

buttonGraph

contains a trend chart as well as the current and estimated (after migration) usage rates of the specified source and target volumes.

Click Set to add a new Manual Migration plan to the list. The new Manual Migration plan consists of the volumes selected in Source LDEV and Target (Reserved) LDEV lists.

buttonSet

Displays all of the manual migration plans regardless of whether the plans are made in the Manual Migration window. Manual Migration plans yet

listManual Migration plans

to be executed are displayed in blue, and Manual Migration plans in progress or completed are displayed in black. Completed Manual Migration plans will subsequently disappear from the list.

Manual Migration plans being executed by other programs (for example, RAID Manager) are sorted in the list together. Migration plans executed by other programs are not erased from the list until they are completed and cleared from the other program.

Toggles the display of usage rates of the parity groups (in the navigation tree) and the volumes (in the LDEVs and the Target (Reserved) LDEV lists) on or off.

buttonDisplay usage rate

Deletes the migration plan selected in the list.

NOTE: Be aware of the following functionality before clicking Delete

• If you select a migration plan that is yet to be applied (in blue) and

click Delete, the migration plan is deleted immediately.

• If you select a migration plan that is waiting to be executed or is in

progress (in black) and click Delete, the DEL column displays the character “D” and the selected migration plan will not be deleted until you click Apply.

• Clicking Delete has no effect when both blue and black migration plans

are selected.

• A migration plan executed by a program other than Auto LUN (such

as RAID Manager) cannot be deleted.

buttonDelete

Click Apply to start executing new manual migration plans and to delete manual migration plans marked for deletion (that is, “D” is displayed in the DEL column).

buttonApply

Closes the Manual Migration window.buttonClose

Updates information in the Manual Migration window including updates to the navigation tree and LDEV lists after completion of a manual migration plan.

buttonRefresh

The Manual Migration window also has several GUI elements which are described in subsequent sections.

48 Auto LUN GUI reference

Page 49

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.

DescriptionTypeItem

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. However, a

icon

volume in a fixed parity group can be used as a source or target volume in a Manual Migration plan.

RAID1 parity group in HDD class A. A similar HDD class A icon indicating RAID5 or RAID6 might also appear.

icon

RAID1 parity group in HDD class B. A similar HDD class B icon indicating RAID5 or RAID6 might also appear.

icon

RAID1 parity group in HDD class C. A similar HDD class C icon indicating RAID5 or RAID6 might also appear.

icon

RAID1 parity group in HDD class D. A similar HDD class D icon indicating RAID5 or RAID6 might also appear.

icon

The parity group ID, usage rates, and corresponding CLPR appear directly to the right of the parity group icon in the following convention:

fieldParity group identifier

1-3(1-4)(!12/13%, 01:CLPR1)

Each element of the preceding example is described below.

• 1-3: indicates the parity group ID.

• (1-4): indicates a parity group to which parity group 1-3 is connected.

• !12/13%: indicates the average usage rate/maximum usage rate for the parity

group. An exclamation mark (!) indicates that the reported usage rate is likely to be inaccurate. “+0” succeeding either of the usage rates indicates that the usage rate is between 0 and 1 percent.

• 01:CLPR1: indicates the number and name of the CLPR corresponding to the

parity group.

The external volume group ID and corresponding CLPR appear directly to the right of the external volume group icon in the following convention:

fieldExternal volume group

identifier

E1-2(03:CLPR3)

Each element of the preceding example is described below.

• E1-2: indicates the external volume group ID.

• 03:CLPR3: indicates the number and name of the CLPR corresponding to the

external volume group.

NOTE: No volumes in an external volume group can be selected as target

volumes.

The Thin Provisioning group ID and corresponding CLPR appear directly to the right of the Thin Provisioning group icon in the following convention:

fieldThin Provisioning

group identifier

(X16-1,03:CLPR3)

• X16-1: indicates the Thin Provisioning virtual volume group ID.

• 03:CLPR3: indicates the number and name of the CLPR corresponding to the

Thin Provisioning virtual volume group.

Manual Migration window 49

Page 50

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.

DescriptionTypeItem

Indicates a normal volume that can be selected as a source volume and migrated to a different parity group. A normal volume cannot be selected as a target volume.

icon

Indicates a reserved volume that is a candidate for an Auto LUN target volume.icon

(blue)

Once you specify a source volume, Auto LUN checks the reserved volumes to verify which ones can be used as target volumes. The icons for all reserved volumes eligible

to be target volumes changes to the icon .

Indicates a reserved volume of a program other than Auto LUN. This type of volume is not a target volume candidate.

icon

(green)

Indicates a volume that can be used as a target volume.icon

Indicates a volume that is either in the process of being migrated, or a volume that is registered in a migration plan. This icon is also used to indicate a volume that is being migrated by a program other than Auto LUN.

icon

Indicates the LDEV ID of the volume. It appears directly to the right of the LDEV icon in the following convention:

fieldLDEV identifier

LDKC:CU:LDEV

Indicates the emulation type of the volume (VLVI or LUN).fieldEmulation

Indicates the capacity of the volume.fieldCapacity

Indicates the average usage rate for LDEVs. An exclamation mark (!) preceding the percentage value indicates that the reported usage rate is likely to be inaccurate.

fieldAve. (%)

This can occur when volumes used in Auto LUN are also formatted by Virtual LVI or Open Volume Management. A “+0” succeeding the percentage value indicates that the usage rate is between 0 and 1 percent.

Indicates the maximum usage rate for LDEVs. An exclamation mark (!) preceding the percentage value indicates that the reported usage rate is likely to be inaccurate.

fieldMax (%)

Indicates the used capacity of the Thin Provisioning pool. The pool capacity can be as much as 42 MB larger than the LDEV capacity of the Thin Provisioning virtual

fieldUsed Capacity

volume. This is because the size of each page of a pool used by Thin Provisioning is 42 MB.

Indicates the ID of the Thin Provisioning pool.fieldPool ID

Indicates the remaining capacity of the Thin Provisioning pool.fieldPool Remainder

Indicates the capacity of the Thin Provisioning pool.fieldPool Capacity

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.

DescriptionTypeItem

Indicates the LDEV ID of the volume in the following convention:fieldLDEV identifier

50 Auto LUN GUI reference

Page 51

DescriptionTypeItem

LDKC:CU:LDEV

Indicates the emulation type of the volume (VLVI or LUN).fieldEmulation

Indicates the capacity of the volume.fieldCapacity

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

fieldAve. (%)

be inaccurate. This can occur when volumes used in Auto LUN are also formatted by Virtual LVI or Open Volume Management. A “+0” succeeding the percentage value indicates that the usage rate is between 0 and 1 percent.

Indicates the maximum usage rate for the parity group. An exclamation mark (!) preceding the percentage value indicates that the reported usage rate is likely to

fieldMax (%)

Indicates the number and name of the CLPR corresponding to the parity group. The following convention is used:

fieldCLPR

CLPR-number:CLPR-name

Indicates the ID of the Thin Provisioning pool.fieldPool ID

Indicates the remaining capacity of the Thin Provisioning pool.fieldPool Remainder

Indicates the capacity of the Thin Provisioning pool.fieldPool Capacity

Manual Plan list

The Manual Plan list contains details of the Manual Migration plans, including information source volumes and target volumes. This list displays all the manual plans created using the Manual

Migration window.

DescriptionTypeItem

PSUE is displayed in this field if the execution of a migration plan created outside of

Remote Web Console fails. In this case, you must check the status of the application software which created the migration plan.

fieldStat

“D” is displayed in this field if you attempt to delete a migration plan that is waiting for execution, or is already in progress. Migration plans indicated by “D” are actually deleted when you click Apply.

fieldDEL

This field indicates the progress of the Manual Migration plan. The progress value is updated at one-minute intervals.

field%

An error code is displayed if clicking Apply generates an error. For the error details and solution, see HP P9000 Remote Web Console Messages.

Displays information about source volumes.fieldSource LDEV

Indicates the volume ID of the source volume in this format: LDKC:CU:LDEV. A icon to the left of the device ID indicates that the volume is being migrated or is registered in a migration plan.

fieldLDEV

Indicates the emulation type of the volume (VLVI or LUN).fieldEmulation

Indicates the capacity of the volume.fieldCapacity

Indicates the RAID type of the source volume.fieldRAID

Indicates the data protection level of the source volume.fieldProtection

Indicates the parity group ID or the external volume group ID of the source volume. The number before the hyphen (-) is the frame number. The number after the hyphen is the

fieldPG

Manual Migration window 51

Page 52

DescriptionTypeItem

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.

Indicates the type of hard disk drive containing the source volume.fieldHDD

Indicates the number and name of the CLPR corresponding to the source volume’s parity group. The following convention is used:

fieldCLPR

CLPR-number:CLPR-name

Display information about target volumes.fieldTarget LDEV

Indicates the volume ID of the target volume in this format: LDKC:CU:LDEV. The blue

icon indicates a reserved volume of Auto LUN. The green icon indicates a reserved

volume of other programs.

fieldLDEV

Indicates the parity group ID or the external volume group ID of the target volume.fieldPG

Indicates the type of hard disk drive containing the target volume.fieldHDD

Indicates the number and name of the CLPR corresponding to the target volume’s parity group. The following convention is used:

fieldCLPR

CLPR-number:CLPR-name

Indicates the program which uses this volume as a target volume. If P9500 is displayed, this is the target volume which is reserved by Remote Web Console. If Other[XX]is

fieldOwner

displayed, this is the target volume which is reserved by RAID Manager or another program. XX is an id which is given by this program. For example, 01 indicates RAID Manager, and 99 indicates Tiered Storage Manager. You cannot delete such a migration plan with the Delete.

Auto Plan window

Figure 13 Auto Plan Window

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)

52 Auto LUN GUI reference

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.

DescriptionTypeItem

Auto Migration Plans section

The value in this field is either Enable or Disable and indicates whether or not the Auto Migration function is enabled.

fieldAuto Migration

Indicates the status of the auto migration plans. This field can have the following values:

fieldMigration Status

• Not planned yet: the auto migration plans have yet to be created.

• Not performed yet: the auto migration plans have been created

but have yet to be executed.

• Failed to make a plan: Auto LUN has failed to create the auto

migration plans.

• Under migration: Auto LUN is executing auto migration plans.

• Last migration has been canceled: Auto LUN has canceled the last

auto migration plan.

A timestamp indicating when the auto migration plans were created.fieldPlan Creation

A timestamp indicating when Auto LUN will perform the next auto migration operations.

fieldNext Migration

The possible values for Auto Refresh are Enable and Disable. If Auto Refresh is enabled, the progress of migration plans are updated in

option buttonsAuto Refresh

real time, and if a new plan is created, the new plan will automatically be added to the list. If Auto Refresh is disabled, information in the list will not be updated automatically.

NOTE: The time values displayed on this window are retrieved from

the SVP, and may not correspond to the time displayed on the Remote Web Console web client.

Discards the existing auto migration plans and then creates new auto migration plans.

buttonMake New Plan

Deletes the auto migration plan selected in the list and all auto migration plans below the selected plan in the list.

buttonDelete

Deletes all auto migration plans in the list.buttonDelete All

Indicates the progress of the auto migration plans. A hyphen appears if Auto LUN has yet to execute the auto migration plans.

field%

The following information is displayed for the Source LDEV:listSource 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.

• Protection: the data protection level.

• PG: the parity group ID. If the indicated parity groups are the

interleaved parity groups, the only parity group ID displayed will be that of the group at the top of the interleaved parity groups.

• HDD: the type of hard disk drive.

Auto Plan window 53

Page 54

DescriptionTypeItem

The following information is displayed for the Target LDEV:listTarget 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.

• HDD: the type of hard disk drive.

Auto Plan Parameters section

The possible values for Auto Migration Function are Enable and Disable. If the Auto Migration function is enabled, auto migration

plans are executed automatically at the established time interval.

option buttonsAuto Migration

Function

The Sampling Term (Date) option buttons set the frequency at which usage statistics are analyzed. The following options are available:

option buttonsSampling Term (Date)

• None: resource usage statistics are not analyzed and auto

migration plans are not created.

• Every day: auto migration plans are created every day.

• Once every X days: auto migration plans are created every X days.

Use the list to specify the number of days (that is, the value of X).

• Once a week: auto migration plans are created once a week. Use

the list to select the day of the week.

• Once a month: auto migration plans are created on the Xth day

of the month. Use the list to specify a day in the month.

Specify a time period for analyzing resource usage statistics by using the From and To drop-down lists.

drop-down listsSampling Term (Time)

The Number of Sampling Points option buttons set the data that are analyzed. The following options are available:

option buttonsNumber of Sampling

Points

• All sampling points: Auto LUN uses all average usage rates during

the Sampling Term to determine disk usage.

• X highest sampling points: Auto LUN uses the Xth highest average

usage rate during the Sampling Term to determine disk usage. Use the list to specify the value of X.

Specify the time that auto migration starts by using the drop-down lists. If the Auto Migration function is enabled, the auto migration

drop-down listsMigration Time

operation starts at the specified time. The Migration Time should be set at least one hour after the ending time specified in the Sampling Term.

The time limit for the execution of an auto migration plan is specified in the Max. migration duration field. Allowable values range from

fieldMax. Migration

duration

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.

The disk usage limit during the execution of an auto migration plan is specified in the Max. disk utilization field. Allowable values range

fieldMax. disk utilization

from 10 to 100 percent. If the most recent usage for any source or target parity group is over this limit when auto migration starts, Auto LUN cancels the auto migration plan and will retry the plan at the next scheduled execution time.

The maximum number of volumes that can be migrated automatically during the execution of an auto migration plan is specified in the

fieldMax. number of vols for

migration

Max. number of vols for migration field. Allowable values range from 1 to 40 volumes. If the number of volumes to be migrated is larger

54 Auto LUN GUI reference

Page 55

DescriptionTypeItem

than the specified number of volumes, the remaining volumes will be migrated at the next scheduled execution time.

Click Default to restore all Auto Plan Parameters to default values and apply these parameters to the storage system.

buttonDefault

Click Set to apply each parameter setting to the storage system.buttonSet

Click Reset to undo all changes to Auto Plan Parameters during the current session.

buttonReset

Closes the Auto Plan window.buttonClose

Attribute window

Figure 14 Attribute Window

The following Auto LUN operations may be performed within the Attribute window:

• “Reserving a volume” (page 26)

• “Fixing a parity group” (page 27)

• “Changing disk usage rate limit for an HDD class” (page 27)

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.

Attribute window 55

Page 56

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.

DescriptionTypeItem

There is a folder for each HDD class. The threshold value for the disk usage rate appears to the right of each HDD class. To view a list of parity groups in an HDD class, double-click the HDD class folder.

foldersHDD Classes

This icon indicates a fixed parity group when it appears in the HDD class folders. A fixed parity group cannot be a part of an Auto

icon

Migration plan. However, a volume in a fixed parity group can be used as a source or target volume in a Manual Migration plan. This icon also indicates a external volume or a Thin Provisioning virtual volume when it appears under the External Group or Thin Provisioning folders. External volumes and Thin Provisioning virtual volume cannot be part of auto migration plans.

RAID1 parity group in HDD class A. A similar HDD class A icon indicating RAID5 or RAID6 might also appear.

icon

RAID1 parity group in HDD class B. A similar HDD class B icon indicating RAID5 or RAID6 might also appear.

icon

RAID1 parity group in HDD class C. A similar HDD class C icon indicating RAID5 or RAID6 might also appear.

icon

RAID1 parity group in HDD class D. A similar HDD class D icon indicating RAID5 or RAID6 might also appear.

icon

The parity group ID appears directly to the right of the parity group icon in the following convention: 1-4. If two or more parity groups

fieldParity group identifier

are connected together, you will see the following convention: 1-3[1-4].

The external volume group ID appears directly to the right of the external volume group icon in the following convention: E1-2.

fieldExternal volume group identifier

The Thin Provisioning group ID appears directly to the right of the Thin Provisioning group icon in the following convention: X16-1.

fieldThin Provisioning group identifier

HDD Class list

When you select a class in the navigation tree, the HDD Class list displays information about parity groups in that HDD class. This information is summarized in the following table.

DescriptionTypeItem

Indicates the parity group ID. The number before the hyphen is the frame number and the number after the hyphen is the group number. This list uses the same icons used in the

fieldPG

“Attribute navigation tree” (page 56). 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.

Indicates the type of hard disk drive.fieldHDD

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

fieldAve. (%)

can occur when volumes used in Auto LUN are also formatted by Virtual LVI or Open Volume Management. A “+0” succeeding the percentage value indicates that the usage rate is between 0 and 1 percent.

Indicates the maximum 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

fieldMax (%)

can occur when volumes used in Auto LUN are also formatted by Virtual LVI or Open Volume

56 Auto LUN GUI reference

Page 57

DescriptionTypeItem

Management. A “+0” succeeding the percentage value indicates that the usage rate is between 0 and 1 percent.

Indicates the total number of volumes in the parity group.fieldTotal

Indicates the number of reserved volumes.fieldReserved

Indicates the number and name of the CLPR corresponding to the parity group. The following convention is used:

fieldCLPR

CLPR-number:CLPR-name

Parity Group list

When you select a parity group in the navigation tree, the list displays information about volumes in that parity group. This information is summarized in the following table.

DescriptionTypeItem

This icon indicates a normal volume that can be selected as a source volume and migrated to a different parity group. This volume cannot be selected as a target

volume or changed to a reserved volume ( ).

icon

This icon indicates a normal volume that can be selected as a source volume and migrated to a different parity group. This volume can be changed to a reserved

volume ( ) and then it can be used as a target volume.

icon

Indicates a reserved volume that is a candidate for an Auto LUN target volume. This volume cannot be used as a source volume unless it is changed to a normal volume

( ).

icon

(blue)

Indicates a reserved volume of a program other than Auto LUN. The attribute of this type of volume cannot be changed.

icon

(green)

Indicates the LDEV ID of the volume. It appears directly to the right of the LDEV icon in the following convention:

fieldLDEV

LDKC:CU:LDEV

You cannot change an attribute of a LUSE volume, a pool volume, a system disk, a journal volume, or a quorum disk.

Indicates the emulation type of the volume.fieldEmulation

Indicates the capacity of the volume.fieldCapacity

Indicates the average usage rate for the volume. An exclamation mark (!) preceding the percentage value indicates that the reported usage rate is likely to be inaccurate.

fieldAve. (%)

Indicates the maximum usage rate for the volume. An exclamation mark (!) preceding the percentage value indicates that the reported usage rate is likely to be inaccurate.

fieldMax (%)

Indicates the number and name of the CLPR corresponding to the parity group to which the volume belongs. The following convention is used:

fieldCLPR

CLPR-number:CLPR-name

Indicates the program which reserved this volume. If P9500 is displayed, the reserved volume is reserved by Remote Web Console. If Other[XX] is displayed, the reserved

fieldOwner

volume is reserved by RAID Manager or another program. XX is an id which is given

Attribute window 57

Page 58

DescriptionTypeItem

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. This information is summarized in the following table.

DescriptionTypeItem

Indicates the ID of the external volume group.fieldExG

Indicates the type of hard disk drive.fieldHDD

Indicates the total number of volumes in the external volume group.fieldTotal

Indicates the number of reserved volumes.fieldReserved

Indicates the number and name of the CLPR corresponding to the external volume group. The following convention is used:

fieldCLPR

CLPR-number:CLPR-name

External volume list

When you select an external volume in the tree, the list displays information about external volumes. This information is summarized in the following table.

DescriptionTypeItems

Indicates the ID of the external volume in this format: LDKC:CU:LDEV. The same icons are used that are used in the “Parity Group list” (page 57).

fieldLDEV

You cannot change an attribute of a LUSE volume, a pool volume, a system disk, a journal volume, or a quorum disk.

Indicates the capacity of the volume.fieldCapacity

Indicates the number and name of the CLPR corresponding to the external volume group to which the volume belongs. The following convention is used:

fieldCLPR

CLPR-number:CLPR-name

Indicates the program which reserved this volume. If P9500 is displayed, the reserved volume is reserved by Remote Web Console. If Other[XX] is displayed, the reserved volume is

fieldOwner

reserved by RAID Manager or another program. XX is an id which is given 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.

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.

DescriptionTypeItem

Indicates the ID of the Thin Provisioning virtual volume.fieldLDEV#

Indicates the ID of the Thin Provisioning virtual volume group.fieldThin Provisioning

Indicates the total number of volumes in the Thin Provisioning virtual volume group.

fieldTotal

58 Auto LUN GUI reference

Page 59

DescriptionTypeItem

Indicates the number of reserved Thin Provisioning virtual volumes.fieldReserved

Indicates the number and name of the CLPR corresponding to the Thin Provisioning virtual volume group. The following convention is used:

fieldCLPR

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. This information is summarized in the following table.

DescriptionTypeItem

Indicates the ID of the Thin Provisioning virtual volume in this format: LDKC:CU:LDEV. The same icons are used that are used in the “Parity Group list” (page 57).

fieldLDEV

Indicates the emulation type of the Thin Provisioning virtual volume.fieldEmulation

Indicates the capacity of the Thin Provisioning virtual volume.fieldCapacity

Indicates the number and name of the CLPR corresponding to the Thin Provisioning virtual volume group to which the Thin Provisioning virtual volume belongs. The following convention is used:

fieldCLPR

CLPR-number:CLPR-name.

Indicates the program which reserved this volume. If P9500 is displayed, the reserved volume is reserved by Remote Web Console. If Other[XX] is displayed, the reserved

fieldOwner

volume is reserved by RAID Manager or another program. XX is an id which is given 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.

Indicates the remaining capacity of the Thin Provisioning pool.fieldPool Remainder

Indicates the entire capacity of the Thin Provisioning pool.fieldPool Capacity

Indicates the ID of the Thin Provisioning pool.fieldPool ID

Attribute window 59

Page 60

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.

DescriptionTypeItem

Auto Migration History section

This list is a log of Auto Migration plans that have been created and executed. Each entry has a time stamp. See “Auto migration messages”

(page 29) for more information on Auto Migration History logs.

listAuto Migration History

Click Erase to clear the Auto Migration History logs.buttonErase

Migration History section

This list is a log of all manual and auto migration events. This list can also contain logs of migration plans executed by programs other than Auto LUN.

listMigration History

Displays the current Migration History page as well as the total number of Migration History pages. Use the list to view the desired page, or use the arrow buttons, each of which is described below:

controlPage

• <<: displays the current (most recent) page Migration History logs.

• <: displays the previous page of the Migration History logs.

• >: displays the next page of the Migration History logs.

• >>: displays the oldest page of the Migration History logs.

Migration History logs can contain up to 256 pages, with a maximum of 2,408 entries displayed on one page.

Displays the date when the event occurred.fieldDate

Displays the time when the event occurred.fieldTime

Displays the event type.fieldAction

60 Auto LUN GUI reference

Page 61

DescriptionTypeItem

Displays the source volume and the parity group (or the external volume group if applicable). If the source parity groups and target parity groups

fieldSource[Parity Gr.]

are the interleaved parity groups, the parity group ID at the top of the interleaved parity groups appears.

Displays the target volume and the parity group (or the external volume group if applicable). If the source parity groups and target parity groups

fieldTarget[Parity Gr.]

are the interleaved parity groups, the parity group ID at the top of the interleaved parity groups appears.

Indicates the program which reserved this volume. If P9500 is displayed, the reserved volume is reserved by Remote Web Console. If Other[XX]

fieldOwner

is displayed, the reserved volume is reserved by RAID Manager or another program. XX is an id which is given 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. indicates a normal volume that is not reserved.

History window 61

Page 62

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.

BC P9000 or XP Business Copy. An HP application that provides volume-level, point-in-time copies

in the disk array.

BC Z The version of Business Copy that supports mainframe volumes. bit The basic unit of data in a binary numbering system (binary digit), represented by a 0 or a 1.

Eight bits equals one byte.

CHA Channel adapter. A device that provides the interface between the array and the external host

system. Occasionally, this term is used synonymously with the term channel host interface processor (CHIP).

CLI Command-line interface. An interface comprised of various commands which are used to control

operating system responses.

CLPR Cache logical partition. Cnt Ac-J P9000 or XP Continuous Access Journal software. Cnt Ac-J Z The version of Continuous Access Journal that supports mainframe volumes. Cnt Ac-S P9000 or XP Continuous Access Synchronous software. Cnt Ac-S Z The version of Continuous Access Synchronous that supports mainframe volumes. command device A volume in the disk array that accepts Continuous Access, Business Copy, or P9000 for Business

Continuity Manager control operations, which are then executed by the array.

CT group Consistency group. CU Control Unit. Used to organize the storage space attached to the disk controller ( DKC). You can

group similarly configured logical devices (LDEVs) with unique control unit images (CUs). CUs are numbered sequentially. The disk array supports a certain number of CUs, depending on the disk array model. Each CU can manage multiple LDEVs; therefore, both the CU number and the LDEV number are required to identify an LDEV.

CVS Custom volume size. CVS devices (OPEN-x CVS or 3390-x CVS) are custom volumes configured

using array management software to be smaller or larger than normal fixed-size OPEN or mainframe system volumes. Synonymous with volume size customization (VSC). OPEN-V is a CVS-based volume.

C-Track Continuous Track. An HP software program that detects internal hardware component problems

on an array and automatically reports them to HP Support Services.

DKA Disk adapter. DKC Disk controller. DKU Disk Unit. ESW Express switch adapter. FC-AL Fibre Channel arbitrated loop. fence 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.

Fibre Channel A data transfer architecture designed for mass storage devices and other peripheral devices that

require high bandwidth.

FICON Fibre connectivity. An FC layer 4 protocol used to map mainframe channel command and data

I/O operations onto standard FC infrastructure, protocol, and FC services.

HBA Host bus adapter. HDD Hard disk drive. LDKC Logical disk controller.

62 Glossary

Page 63

LUN 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. 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.

M-VOL Main volume. MCU Main control unit. MPB MSL to MicroProcessor Blade MU Mirror unit. ORM Online Read Margin P-VOL Primary volume. parity group A set of hard disk drives that have the same capacity and that are treated as one group. A parity

group contains both user data and parity information, which enables user data to be accessed if one or more drives in the group is not available.

path A path is created by associating a port, a target, and a LUN ID with one or more LDEVs. Also

known as a LUN.

PAV Parallel access volume. PCB Printed circuit board. PDEV Physical device. port A physical connection that allows data to pass between a host and the disk array. The number

of ports on a disk array depends on the number of supported I/O slots and the number of ports available per I/O adapter. The P9000 and XP family of disk arrays supports Fibre Channel (FC) ports and other port types. Ports are named by port group and port letter, such as CL1-A. CL1 is the group; A is the port letter.

R-VOL Remote volume. RAID level A configuration of disk drives that uses striping, mirroring, and parity to improve performance

and data availability and reliability.

RAID Manager The CLI configuration and replication tool for the P9000 or XP disk array that system administrators

can use to enter RAID Manager commands from open-system hosts to perform Continuous Access, Business Copy, Database Validator, and Data Retention operations, as well as provisioning commands on logical devices.

RCU Remote control unit. Remote Web

Console

A browser-based program installed on the SVP that allows you to configure and manage the disk array.

RIO Remote I/O. RM HP StorageWorks RAID Manager. S-VOL Secondary or remote volume. The copy volume that receives the data from the primary volume. SAS Serial Attached SCSI. SCP State-change-pending. SIM Service information message. SMPL Simplex. SSB Sense byte. SSD Solid state disk. A high-performance storage device that contains no moving parts. An SSD

contains DRAM or EEPROM memory boards, a memory bus board, a CPU, and a battery card.

SVP 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

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. UDP User Datagram Protocol. UTC Coordinated Universal Time. V-VOL Virtual Volume. VOL, vol Volume. volume Volume on disk. An accessible storage area on disk, either physical or virtual. VSC Volume size customization. Also known as CVS. WWN World Wide Name. A unique identifier assigned to a Fibre Channel device.

64 Glossary

Page 65

Index

auto LUN

window, 46

auto migration

changing disk usage rate limit , 27 flow, 8 function, 7, 17 identifying parity groups, 7 messages, 29 parameters, 21 prerequisites, 10

calculating differential tables

for a mainframe volume, 17 candidates for source and target volumes, 11 class, 26 contacting HP, 36 control cylinders, 17

open emulation type, 18 conventions

document, 37

storage capacity values, 37

text symbols, 37 copy operation, 6 Copy Threshold option, 33

deleting

auto migration plans, 25

manual migration plan, 23, 40 differential data, 6 differential tables

OPEN-V volume, 18 disk arrays

supported models, 5 disk usage

changing rate limit, 27

rate limit, 7 document

conventions, 37

related information, 36 documentation

HP website, 36

providing feedback, 36

emulation type, 17

example, 18 estimating

differential tables, 17

number of concurrent manual migration plans, 20

fixed parity groups, 27

overview, 20

fixing a parity group, 27

help

obtaining, 36 host name, 40 HP

technical support, 36

identifying parity groups, 7 instance number, 40

LDEV list, 50 list

LDEV, 50

manual plan, 51

manual migration

operations, 17 migrating volumes

improving performance, 5

manually, 6, 22

non disruptive, 5

planning, 17

with thin provisioning, 13

within the same HDD class, 8 migration

history logs, 27

manual operations, 6 migration plan

deleting a manual migration plan, 23

deleting an auto migration plan, 25

running concurrent plans, 19

permissible virtual volume combinations, 13 prohibited source or target volumes, 10

reapplying auto migration plans, 25 related documentation, 36 reserve attribute, 6 reserved volume, 6, 50, 57 reserving a volume, 26

setting up auto migration plan, 24 shared memory, 20 source and target volumes by storage feature, 11 source volume, 5 storage capacity values

conventions, 37

Page 66

Subscriber's Choice, HP, 36 symbols in text, 37

target volume, 5 technical support

HP, 36

service locator website, 36 text symbols, 37 troubleshooting

general, 35

when using RAID Manager, 40 typographic conventions, 37

volume migration

automatic , 7

interoperability, 40

limitations, 5

manual, 6

manual with RAID Manager, 39

manual;migrating volu:manually, 17

monitoring, 29

websites

HP , 36

HP Subscriber's Choice for Business, 36

product manuals, 36 window

auto LUN, 46

auto plan, 52

66 Index

HP XP P9500, Auto LUN User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual