Hitachi Command Suite 8 User Guide

in a tier. Migration source volumes can also be selected from volume searchresults. If a volume that cannot be migrated is included in the selected
volumes, that volume is excluded from migration and only volumes that can
be migrated, will be migrated.
Migration targets are selected from tiers, DP pools, or resource search results. If DP pools are selected, DP volumes with the same capacity as the migration-source volumes are automatically created. The existing DP volumesalso can be specified as...

Notes on performing data migrationThe number of volumes that are candidates for migration target volumes are
narrowed down and displayed when selecting a migration target volume. If you want to display all the volumes, in the  migration.properties file on the
Device Manager server set a value for the migration.plan.candidateVolumeCountLimit  property.
For details on the properties file, refer to the  Hitachi Command Suite
Administrator Guide . To avoid insufficient memory, we recommend that you
use the...

For some volumes, when you try to select those volumes as migration-sourcevolumes, the reasons why they cannot be selected as migration-source volumes are displayed on-screen.
Volume migration requirements
All volumes for which data migration is to be performed must meet the
following conditions:
• Migration-source and migration-target volumes exist within one of the following storage systems (chassis):
○ Virtual Storage Platform
○ Universal Storage Platform V/VM
○ Virtual Storage Platform G1000
○...

Table 8-1  Migration sources and targets by volume type and state
Volume Type, StateSourceTargetNormal volumesYYExternal volumesYYLUSE volumesY1YDP volumes 2HDT volumes to which a data placement profile is
applied.NNVirtual volumes that are not associated with a DP pool.NNVolumes other than the aboveYYDP poolsNY 3DP pool volumesNNVolumes for which Cache Residency Manager is setNNCommand DeviceNNVolumes that are configured as a Cross-system Copy pairNNNAS system volumesYNSystem DiskNNVolumes that are...

Volume Type, StateSourceTargetUniversal Storage Platform V/VM, VirtualStorage Platform, Virtual Storage Platform
G1000, or HUS VM)Volumes other than the aboveNNUniversal
Replicator, Hitachi
Universal
ReplicatorP-VOL
S-VOLCOPY
PAIR
[Pending duplex]
[Duplex]NNVolumes other than the aboveY 4NJNL-VOLNNCopy-on-Write
SnapshotP-VOLPAIR (1 to 63 generations)YNVolumes other than the aboveNNV-VOL
POOLNNThin ImageP-VOLNNV-VOLNNPOOLNNData Retention
Utility 5Read/WriteYYVolumes other than the aboveYNVolumes that are...

Volume Type, StateSourceTarget• The RAID level, drive type, and SLPR (storage management logical partition) of allmigration target volumes are the same.
Note that if you are migrating a LUSE volume of a Universal Storage Platform V/VM storage system for which the micro version is earlier than 60-05-12-00/00, you must not perform I/O operations on the volumes while migration is being executed.
2. The migration-source volumes and migration target volumes or pools are in different DP
pools.
3. The following...

Displayed character stringReason preventing use as a migration source• The volume is the P-VOL of a Copy-on-Write Snapshot pairand its status is not PAIR
• The volume is the V-VOL of a Copy-on-Write Snapshot pair
• The volume is the POOL of a Copy-on-Write Snapshot pairDynamic Provisioning [Pool
Volume]The volume is a DP pool volume.Dynamic Provisioning
[Unassigned]The volume is a virtual volume and is not associated with a DP
pool.Externally LockedThe volume is locked by Data Retention Utility (not...

Displayed character stringReason preventing use as a migration source• The volume is part of a Universal Replicator pair, and thestatus is either COPY or PAIR
• The volume is part of a Universal Replicator for Mainframe pair, and the status is either Pending duplex or Duplex
• The volume is part of a Universal Replicator journal volume
• The volume is a Universal Replicator for Mainframe journal volumeVolume Migration V2Volume Migration V2 is not installed in the storage system.global-active...

3.Verify that the correct migration source volumes are selected, and then
click  Next .
4. Specify the migration target, DP pool or tier and then click  Next. When
the parity group selection rule is set, a candidate volume that is
appropriate as a migration target is selected depending on the
application that is being used or the usage rate of the parity group.
Specifically, the system attempts one of the following:
• Balance Capacity : Selects a migration target candidate so that the
remaining capacity...

• Identify the migration source host, file server, logical group, tier, or storagesystem.
• Identify the migration target DP pools, tier, or migration target volumes.
Procedure 1. On the  Resources  tab, select  Storage Systems .
2. Expand the tree for the source storage system that is to be migrated,
select the volumes to be migrated from the list of external storage
systems, and then click the  Migrate Data button.
3. Confirm that the correct migration source volumes are selected, and then
click the...