HP P9000 User manual

HP StorageWorks
P9000 Auto LUN User Guide
Abstract
This guide explains how to balance system workloads and improve performance by migrating high-usage volumes to low-usage
and high-performance disks using HP StorageWorks P9000 Auto LUN Software. Topics include how to create and execute
migration plans manually and automatically and how to troubleshoot errors. The intended audience is a storage administrator
with independent knowledge of HP StorageWorks P9000 disk arrays, the HP StorageWorks Remote Web Console, and the
operating system and web browser on the HP StorageWorks Remote Web Console.
HP Part Number: AV400-96358
Published: May 2011
Edition: Fourth

© Copyright 2010, 2011 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. 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

Contents
1 Overview of Auto LUN................................................................................6
Overview of Auto LUN..............................................................................................................6
Limitations of Auto LUN.............................................................................................................6
Source and target volumes.........................................................................................................6
Manual volume migration..........................................................................................................7
When to use manual volume migration........................................................................................8
Automatic volume migration.......................................................................................................8
Migrating volumes to another HDD class.................................................................................9
Migrating volumes within the same HDD class.........................................................................9
2 Requirements...........................................................................................11
System requirements................................................................................................................11
Volumes assigned to resource groups........................................................................................11
Source and target volume general requirements..........................................................................11
Supported and prohibited source and target volumes..................................................................11
Auto LUN with Thin Provisioning virtual volumes..........................................................................14
Auto LUN with Continuous Access Synchronous and Continuous Access Journal V-VOLs...................15
Auto LUN and Continuous Access Journal Z...............................................................................16
Auto LUN and Continuous Access Journal..................................................................................17
3 Auto LUN planning...................................................................................19
Manual migration plans..........................................................................................................19
Estimating differential tables.....................................................................................................19
Calculating the required amount of differential tables for a mainframe volume................................19
Control cylinders by mainframe emulation type......................................................................19
3390-3 emulation type example..........................................................................................20
Calculating the required amount of differential tables for an open-system volume............................20
Control cylinders by open emulation type..............................................................................20
Differential tables calculation for an OPEN-V volume..............................................................21
Differential tables calculation for other open emulation types...................................................21
Running concurrent manual migration plans...............................................................................21
Estimating the number of concurrent manual migration plans...................................................22
Fixed parity groups.................................................................................................................22
Auto Migration Parameters.......................................................................................................23
4 Auto LUN operations................................................................................24
Migrating a volume manually...................................................................................................24
Deleting a manual migration plan.............................................................................................25
Setting up auto migration plan parameters.................................................................................26
Deleting auto migration plans...................................................................................................27
Recreating auto migration plans ..............................................................................................27
Stopping the Auto Migration function........................................................................................28
Reserving a volume.................................................................................................................28
Fixing a parity group..............................................................................................................29
Changing disk usage rate limit for an HDD class........................................................................30
Viewing the migration history logs............................................................................................30
Contents 3

5 Auto LUN monitoring................................................................................31
Auto migration messages.........................................................................................................31
Auto migration general status messages................................................................................31
Successful auto migration plan messages..............................................................................32
Stopped auto migration plan messages.................................................................................32
Failed auto migration plan messages ...................................................................................33
Migration History messages.....................................................................................................35
Copy Threshold option............................................................................................................35
Effects of Auto LUN on other program products...........................................................................36
Best practices.........................................................................................................................36
6 Troubleshooting........................................................................................37
Troubleshooting Auto LUN.......................................................................................................37
7 Support and other resources......................................................................38
Contacting HP........................................................................................................................38
Subscription service............................................................................................................38
Documentation feedback....................................................................................................38
Related information.................................................................................................................38
HP websites......................................................................................................................38
Conventions for storage capacity values....................................................................................39
Typographic conventions.........................................................................................................39
A Using RAID Manager for manual Auto LUN.................................................41
Auto LUN and RAID Manager commands .................................................................................41
Migrating volumes manually with RAID Manager........................................................................41
Interoperability of Auto LUN and RAID Manager........................................................................42
Troubleshooting when using RAID Manager...............................................................................42
B Auto LUN GUI reference............................................................................48
Auto LUN window..................................................................................................................48
Common elements..................................................................................................................49
Manual Migration window......................................................................................................49
Manual Migration Plans navigation tree................................................................................51
LDEVs list..........................................................................................................................52
Target (Reserved) LDEV list..................................................................................................53
Manual Plan list.................................................................................................................53
Auto Plan window..................................................................................................................54
Attribute window....................................................................................................................57
Attribute navigation tree......................................................................................................58
HDD Class list...................................................................................................................58
Parity Group list.................................................................................................................59
External Volume Group list..................................................................................................60
External volume list............................................................................................................60
Thin Provisioning groups list.................................................................................................61
Thin Provisioning virtual volumes list.....................................................................................61
History window......................................................................................................................62
Glossary....................................................................................................64
4 Contents

Index.........................................................................................................67
Contents 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”
6 Overview of Auto LUN

(page 11) for more information on requirements and restrictions when selecting source and target
volumes.
Manual volume migration
In a manual volume migration operation, the data on the source volume is copied to a reserved
target volume. Once all data is copied to the target volume, host access is transferred to the target
volume to complete the migration. 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
Manual volume migration 7

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

Figure 3 Auto LUN to Improve Disk Usage Efficiency
When parity groups in a higher HDD class run out of reserved volumes, the low-usage volumes in
this class are automatically migrated to a lower HDD class parity group in order to maintain an
inventory of volumes that may be reserved in the higher HDD class parity groups. 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
Automatic volume migration 9

HDD class and force another volume out of that parity group, the Auto Migration operation requires
a minimum of 20 percent difference in estimated disk usage between the two volumes. If the
difference in disk usage is less than 20 percent, the migration plan is considered an ineffective
strategy, and the volume is not migrated. The following figure illustrates this Auto Migration
operation.
Figure 6 Migrating a Volume Automatically Within the Same HDD Class
10 Overview of Auto LUN

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
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 StorageWorks P9000 Provisioning for Open Systems
User Guide or the HP StorageWorks 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
System requirements 11

•IBM 3390 Concurrent Copy volumes
•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
the same Thin Provisioning
pool as the source volume
NOTE: The maximum
capacity is 4 TB.
Yes
NOTE: The maximum
capacity is 4 TB.
V-VOLThin Provisioning
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
12 Requirements

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 primary volume in any
status
Continuous Access Journal
Z
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
Supported and prohibited source and target volumes 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 in COPY (SP) or
PSUS (SP) status
Business Copy
NoNoA volume in SP-Pend or
V-Split status
Business Copy Z
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
amount of target volumes
are reserved.
All LDEVs in an expanded
LU
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.
14 Requirements

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
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.Internal Volume
A migration plan can be created. A
warning message appears if there is a
possibility that the data size may
exceed the pool threshold after
migration.
A migration plan can be created.V-VOL in Normal state
A migration plan can be created. A
warning message appears if there is a
possibility that the data size may
exceed the pool threshold after
migration.
A migration plan can be created.V-VOL in Blocked state due to full
capacity
The migration plan might not be executed if the storage system is experiencing a heavy workload.
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 15) 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 Volume
Candidate
Continuous Access Synchronous or
Continuous Access Journal Pair
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
Auto LUN with Continuous Access Synchronous and Continuous Access Journal V-VOLs 15

Table 4 Poor Target Volume Candidates for Cnt Ac-S/Cnt Ac-J Pair Combinations (continued)
Poor Target Volume CandidateSource Volume
Candidate
Continuous Access Synchronous or
Continuous Access Journal Pair
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 16)
and Table 6 (page 17).
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
16 Requirements

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
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 7 (page 17)
and Table 8 (page 18).
Also, the source and target volumes must belong to the same CLPR.
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
Auto LUN and Continuous Access Journal 17

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
18 Requirements

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
Manual migration plans 19

Table 9 Number of Control Cylinders Based on Emulation Type (continued)
Number of Control CylindersEmulation Type
63390-3, 3390-3A, 3390-3B, 3390-3C, 3390-3R
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
20 Auto LUN planning