8 volumes used for migration, Volumes used for migration, N (section – HP StorageWorks XP10000 Disk Array User Manual

Page 25

Advertising
background image


25

The refresh scope on Device Manager is the domain controllers that make up the storage domain that is the
refresh target on Tiered Storage Manager.

1-8 Volumes Used for Migration

Migration source and target volumes must satisfy the following conditions in a migration using Tiered Storage
Manager:

The emulation types of the migration source volumes and migration target volumes match.

The sizes of the migration source and migration target volumes match.
The emulation types of the migration source volumes and the migration target volumes are not OPEN-V,
but the volumes are both CVS or both normal.

You can check the emulation type and size of a volume in the Volume Detailed Information – Device Number
popup window. For details on this window, see the GUI Help.

Volumes that cannot be migrated
For volumes that cannot be migrated, you can check the status from the Volume Detailed Information -
Device Number pop-up window - Can Migrate or Volume Status.

Can Migrate

When Yes is specified for Can Migrate, you can perform migration using the volume as a source
volume.

When No is specified, you cannot perform migration using the volume as a source volume. An error
occurs when you click the Migration button.

Volume Status

When Unused is specified for Volume Status, it is available as a source target.

When Used is specified, the volume will not be displayed as a candidate for the migration target
volume.

When No is specified for Can Migrate, or Used is specified for Volume Status, the reasons are displayed in
Reasons that a volume cannot become source/target volume in the Volume Detailed Information - Device
Number
pop-up window. For details on the character strings to be displayed and their descriptions, see Table
1.5 Character Strings Representing Reasons a Volume Cannot Be a Migration Source or Target, and a
Description of those Character Strings.

Volumes that cannot be checked for migration suitability
The following volumes cannot be checked for suitability by using Can Migrate or Volume Status. An error
occurs when executing a migration task with these volumes selected as a source volume. Also, an error
occurs when creating a migration task that has these volumes selected as migration target volumes.

A volume that makes up a Cross-system Copy pair

A volume that is the target of XRC (Extended Remote Copy, which is the IBM remote copy function)

A volume that is the target of Concurrent copy

A volume that cannot be accessed because it has a blocked status or is being formatted

An error occurs when executing a migration task using the following volumes together:

For a migration source volume: volume made up of a TrueCopy pair

For a migration target volume: externally connected volumes

Information displayed as reasons that a volume cannot be a migration source or target
When migration suitability checks can be performed from Tiered Storage Manager, if volumes are
determined to be unsuitable as a migration source or target, the reasons are displayed in Reasons that a
volume cannot become source/target volume in the Volume Detailed Information - Device Number pop-up
window.

The following table shows the character strings representing the reasons that a volume cannot be a
migration source or target.

Volumes that can be checked by Tiered Storage Manager, and for which a migration task or data deletion task
is being executed, are not displayed in Reasons that a volume cannot become source/target volume. Such
volumes cannot be used as either migration source volumes or migration target volumes.

Table 1-3

Character Strings Representing Reasons a Volume Cannot Be a Migration Source or Target

Advertising