HP XP20000XP24000 Disk Array User Manual

Page 18

Advertising
background image

• TrueCopy for Mainframe operation that changes the volume status to something other than

suspended or simplex.

• Continuous Access operation that changes the volume status to something other than PSUS,

PSUE, or SMPL.

• Continuous Access Journal operation or Universal Replicator for Mainframe operation that

changes the volume status to COPY.

• ShadowImage for Mainframe operation that changes the volume status to SP-Pend or V-Split.
• Business Copy operation that changes the volume status to COPY(SP) or PSUS(SP).
• Continuous Access Journal operation or Universal Replicator for Mainframe operation.

Expanded LUs as source volumes. To specify an expanded LU as a source volume for migration,

you can specify individual LDEVs within the expanded LU (for example, LDEVs with high usage),

and Auto LUN will migrate only the specified LDEVs. If desired, you can also specify all LDEVs of

the expanded LU to relocate the entire expanded LU. In this case, you must make sure that the

required reserved target LDEVs are available.

Target volumes. Target volumes must be reserved prior to migration using the Auto LUN software.

Hosts cannot access reserved volumes.

The following volumes cannot be reserved as target volumes:
• Expanded LUs
• Volumes which are set as command devices (devices reserved for use by the host).
• Volumes which are assigned to Business Copy or Continuous Access pairs.
• Volumes which are used by the IBM 3990 Concurrent Copy (CC) host software function.
• Volumes which are reserved for Business Copy operations.
• Volumes which have Cache Residency Manager data or Cache Residency Manager for

Mainframe data stored in cache.

• Volumes used by Continuous Access Journal or Universal Replicator for Mainframe as a data

volume or journal volume.

• Volumes in which HP StorageWorks XP Volume Retention Manager specified the Read Only

or Protect attribute.

• Volumes which HP StorageWorks XP Volume Security disabled to be used as secondary

volumes.

• Volumes which Data Retention Utility specified the Read Only or Protect attribute, or disabled

to be used as secondary volumes.

• Volumes which are reserved by a migration program other than Auto LUN.
• Volumes on which RAID Manager is performing volume migration operation.
• Volumes that form a XP Snapshot pair.
• Virtual volumes, XP Thin Provisioning volumes and pool volumes.
• Volumes which are in an abnormal or inaccessible condition (for example, pinned track,

fenced).

You can also reserve external volumes as target volumes. However, if you specify a TrueCopy

for Mainframe volume or Continuous Access volume as a source volume, you cannot specify an

external volume as the target volume.

Number of migration plans that can be executed concurrently: In manual migration, the number

of migration plans that can be executed concurrently might be restricted depending on the usage

of other storage system programs, and also depending on the emulation types and sizes of

the migrated volumes.

Auto LUN uses the differential tables to manage differentials occurred by write operation while

migrating volumes. Differential tables are the resources shared by XP Snapshot, Auto LUN,

Business Copy, ShadowImage for Mainframe, HP StorageWorks XP for Compatible FlashCopy

Mirroring, and Compatible FlashCopy V2. Therefore, the maximum number of differential tables

that Auto LUN can use is the number of total differential tables in the storage system minus

the number of that used by other programs.

Moreover, the number of differential tables needed to migrate one volume differs depending on

the emulation type and size of the volume. Thus, the maximum number of migration plans that

About Auto LUN Operations

18

Advertising
This manual is related to the following products: