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 migration targets.
Note the following:
• When the migration source and the migration target are selected, individual pairs of migration source volumes and migration target volumes
(or DP pools) are automatically created. Although, you can change these
pairs, pairs of volumes that cannot be migrated will not be created.
• During migration, data can still be accessed. • When data migration is completed normally, the LDEV ID and host I/O of the migration source volumes are changed to those of the migration target
volumes. The procedure for accessing migrated data is not changed before or after migration.
• If linked with Hitachi Tuning Manager, parity group busy rate for the migration source volume and migration target volume can be checked.
• When you create a migration task, you can select whether to delete the migration source volume after the migration completes. As an alternative,
after migrating, you can delete the data of the source volumes.
• After volumes are migrated to DP volumes, unused capacity in the target volumes is returned to the pool (zero page reclaim) if the zero pagereclaim option is on. We recommend that the migration source volume be
deleted if it is a DP volume and you will not use it. If you do not delete the
migration source volume, we recommend that the zero page of the migration source volume be discarded after the migration task finishes.
• You cannot work with volumes (such as copy pair or volume allocation) until the migration tasks are completed.
You must have a Tiered Storage Manager license registered to perform Data Migration.
Related tasks
•
Migrating data for volume performance  on page 338
•
Migrating data to a different storage system  on page 339
Related references •
Notes on performing data migration  on page 332
•
Conditions for data migration  on page 332
Optimizing storage performance331Hitachi Command Suite User Guide 
						

							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 default.
The maximum number of volumes that can be displayed as migration target
candidates is 2,000 volumes. Exceeding this value will produce an error.
The maximum number of volumes that can be displayed as migration source
candidates is 500 volumes. Exceeding this value will produce an error.
Data migration tasks take a long time from start of execution to completion.
This might affect the performance of access from hosts to target volumes. To
avoid executing such tasks while the access frequency is high, check the time
required to complete the tasks and set a task execution schedule before
registering the tasks. Actual required time might differ considerably in cases such as performing migration for the first time, migrating a volume smaller
than 170 GB, or migrating many volumes at the same time.
When storage systems or hosts are under a heavy load, migration might fail.
In this case, reduce the load on the storage systems, and then perform data migration again.
If data migration fails, the integrity of data on the migration target cannot be ensured. Therefore, data migration must be restarted.
If a data migration fails, and operations for the migration target such as re-
execution of data migration and volume allocation cannot be performed, the
storage system must be refreshed.
Related concepts
•
About data migration  on page 330
Related tasks •
Migrating data for volume performance  on page 338
•
Migrating data to a different storage system  on page 339
Conditions for data migration Data migration conditions include conditions that apply to all volumes
(volume migration requirements), and conditions that depend on the type of
volume (volume migration requirements related to volume type).
332Optimizing storage performanceHitachi Command Suite User Guide 
						

							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
○ Universal Storage Platform
○ HUS VM
• The emulation type, number of blocks, and size are the same for the source and target migration volumes. However, note the following
exceptions:
○ If the micro version of Universal Storage Platform V/VM is
60-03-20-00/00-xx or later and if both the migration source and the
migration target volumes are DP volumes, the emulation type can be between OPEN-V and OPEN-0V.
○ If a volume whose emulation type is OPEN-V is a normal volume, and if
the size of a migration target volume is larger than a migration source volume, a volume that has the same size of the migration sourcevolume is re-created. The remaining capacity can be reused. If you seta value for the propertymigration.plan.candidateCapacityGroupDisplayMaxCount  in the
migration.properties  file, you can specify how many volumes with a
larger capacity than the migration source volume to display, in addition
to the volumes with the same capacity as the migration source volume.
• The LDKC:CU:LDEV number for the volume is in the range from 00:00:00 to 00:FF:FF
• Volumes can be accessed, and are not reserved by other programs, Device Manager, or tasks.
• If the emulation type is not OPEN-V, and both the migration source and the migration target volumes are normal, or both are CVS volumes.
Volume migration requirements related to volume type
Whether you can select a volume as a migration source or migration target
depends on the volume type. The following table shows which volume types can and cannot be selected as migration sources and targets.Optimizing storage performance333Hitachi Command Suite User Guide 
						

							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 configured for concurrent copyingNNOn-demand device volumesNNIntermediate volumesNNMainframe volumes for which a path is setYNMainframe volumes for which SYSPLEXID is setYYMainframe volumes for which DEVN is setYYMainframe volumes for which VOLSER is setYNQuorum disks used for High Availability ManagerNNHigh Availability
ManagerP-VOL
S-VOLNNShadowImage,
ShadowImage for
MainframeVolumes for which pairs are configured with a P-VOL and
three S-VOLsNNVolumes for which pairs are configured with an S-VOL
and an SP-VOLNNVolumes for which pairs are configured with an SP-VOL
and two S-VOLsNNVolumes other than the aboveYNTrueCopy
Synchronous,
TrueCopy for
MainframeP-VOL
S-VOLPSUS
PSUE
[Suspended]
PAIR
[Duplex]
(PAIR and Duplex can be a migration source when using TrueCopy Sync withY 4
(In the
case of
an
internal
storage
system)N334Optimizing storage performanceHitachi Command Suite User Guide 
						

							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
configured for
XRCSuspended statusYNVolumes other than the aboveNNVolumes for which virtual IDs are specifiedYY 6Volumes that are a global-active device pair.NNVolumes reserved as global-active device secondary volumes.NNVolumes that are quorum disks in a global-active device environment.NNLegend:
• Y: Can be selected
• N: Cannot be selected
• [ ]: Names indicated are those for mainframe-based programs
Notes: 1. When the migration source volume is a LUSE, a migration target must be selected for each
volume that constitutes the LUSE. Migration target volumes must also satisfy the following
conditions:
• All of the migration target volumes are internal volumes, or all are external volumes.
• The I/O suppression mode, cache mode, and CLPR of all migration target volumes are the same.
• Migration target volumes are not DP volumes.
Also, for HCS to automatically create pairs for migration sources and migration targets, we recommend that the following conditions also be met:
• If the migration target volumes are external volumes, all of the volumes are in the same external storage system.Optimizing storage performance335Hitachi Command Suite User Guide 
						

							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 conditions must be satisfied:
• The status is not blocked.
• The DP pool has more unused capacity than the migration-source volumes. • Used DP pool capacity does not exceed both used thresholds 1 and 2 (even after a migration is performed).
• DP pool subscription does not exceed the subscription warning and subscription limit (even after a migration is performed).
• When selecting migration-target resources, if the option to create new DP volumes is selected, the number of virtual volumes in the DP pool is less than the limit (VSP G1000:
63,232; Virtual Storage Platform: 63,232; Universal Storage Platform V/VM: 8,192; HUS
VM: 14,080).
4. The CLPRs for the migration target and migration source are the same.
5. If an external storage system is locked (not Read/Write), it cannot be a migration source or
migration target.
6. Volumes with virtual IDs specified cannot be selected as migration target volumes when:
• The migration target is a DP pool, and Create new HDP volumes is selected in the migration target creation options.
• The specified capacity differs from the capacity of the migration source.
Reasons why volumes cannot be selected as migration sources
If a volume cannot be made a migration source and the reason for it is displayed, in the Data Migration wizard, a character string is displayed in the
Migration Restriction column for Selected Column on the Migration Source
page. The following table shows the character strings and corresponding
reasons why a volume cannot be made a migration source.
Table 8-2  Volumes that cannot be used as migration sources
Displayed character stringReason preventing use as a migration sourceArray TypeThe volume is part of an unsupported storage system.Cache Residency ManagerCache Residency Manager or Hitachi Cache Residency Manager
for Mainframe is set for the volume.Command DeviceThe volume is used as a command device.Copy-On-Write Snapshot StatusThe volume is one of the following:
• The volume is the P-VOL of a Copy-on-Write Snapshot pair, its status is PAIR, and the number of generations is 64336Optimizing storage performanceHitachi Command Suite User Guide 
						

							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 Read/Write).Intermediate volumeThe volume is an intermediate volume.Migration ReservedThe volume has already been reserved as a migration target.Not Acquired Volume
InformationInformation for the volume cannot be acquired.On Demand DeviceThe volume is an on-demand device volume.ReservedThe volume has already been reserved in Device Manager.RoleOnly the View role is assigned.ShadowImage Configuration
[Leaf]The volume is part of a ShadowImage or ShadowImage for
Mainframe S-VOL, and paired with an SP-VOL.ShadowImage Configuration
[Node]The volume is part of a ShadowImage or ShadowImage for
Mainframe SP-VOL, and paired with two S-VOLs.ShadowImage Configuration
[Root]The volume is part of a ShadowImage or ShadowImage for
Mainframe P-VOL, and paired with three S-VOLs.System DiskThe volume is a system disk.Thin ImageThis is a Thin Image P-VOL, V-VOL, or Pool.TrueCopy Asynchronous StatusThe volume is one of the following:
• The volume is part of a TrueCopy Asynchronous pair, and the status is neither PSUS nor PSUE
• The volume is part of a TrueCopy for Mainframe pair, and the status is not suspendedTrueCopy Synchronous StatusThe volume is one of the following:
• The volume is part of a TrueCopy Synchronous pair, and the status is other than PSUS, PSUE, or PAIR
• The volume is part of a TrueCopy for Mainframe pair, and the status is not suspended
• The volume is in a Hitachi USP, and a part of a TrueCopy Synchronous pair, and the status is PAIR
• The volume is from a Hitachi USP, and part of a TrueCopy for Mainframe pair, and the status is DuplexUniversal Replicator StatusThe volume is one of the following:Optimizing storage performance337Hitachi Command Suite User Guide 
						

							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 deviceVolumes that are a global-active device pair.GAD ReservedVolumes reserved as global-active device secondary volumes.
Related concepts
•
About data migration  on page 330
Related tasks •
Migrating data for volume performance  on page 338
•
Migrating data to a different storage system  on page 339
Migrating data for volume performance You can migrate data based on the results of monitoring volume
performance.
Prerequisites
• Register a Tiered Storage Manager license.
• Set up an external connection to a Virtual Storage Platform, Universal Storage Platform V/VM, Universal Storage Platform, Virtual StoragePlatform G1000, or HUS VM storage system.
• Create a tier in which the target mainframe volumes are grouped (only when migrating mainframe volumes).
• Gather the following information: ○Migration source host, file server, logical group, tier, or storage system.
○ Migration target DP pools, tier or migration target volumes.
Procedure 1. In the  Resources  or Mobility  tab, select a migration source host or
logical group. From a list of hosts or logical groups, you may also select
migration source volumes. If migrating data from a mainframe volume,
expand the  Tiers tree on the  Resources tab or the Mobility tab, and
then select the corresponding tier.
2. Click the  Migrate Data  button.
338Optimizing storage performanceHitachi Command Suite User Guide 
						

							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 of the targeted parity group is equalized with other parity groups.
• Maximum Coverage : Selects a candidate for the migration target
from as many parity groups as possible.
• Minimum Coverage : Selects a candidate for the migration target
from as few parity groups as possible.
5. Confirm that all migration source volumes and target volumes or DP
pools are paired properly, confirm that no other problems exist, and then click  Next . If necessary, change the pairs. To change a pair, first select
the volume pair, then from the  Other Candidates for Migration  list,
select the target volume to change to, and then click  Map Volume.
6. Specify plan options as necessary, and then run the task.
7. In the tasks list, confirm the result of the task. After a task is created,
you must not perform any operations on volumes included in the task byusing Hitachi Command Suite or other programs until the task hasfinished executing.
Related concepts
•
About data migration  on page 330
Related tasks
•
Migrating data to a different storage system  on page 339
Related references
•
Conditions for data migration  on page 332
Migrating data to a different storage system You can migrate data to a different storage system.
Prerequisites
• Register a Tiered Storage Manager license
• Set up an external connection to a Virtual Storage Platform, Universal Storage Platform V/VM, Universal Storage Platform, Virtual StoragePlatform G1000, or HUS VM storage system.
• Create a tier in which the target mainframe volumes are grouped (only when migrating mainframe volumes).
Optimizing storage performance339Hitachi Command Suite User Guide 
						

							• 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  Next button.
4. Specify the migration target, DP pools, or tier and then click the  Next
button. When the parity group selection rule is set, a candidate volume
that is appropriate as a migration target will be selected depending on
the application that is being used or the usage rate of the parity group.
Specifically:
• Balance Capacity : System attempts to select a migration target
candidate so that the remaining capacity of the targeted parity group
is equalized with other parity groups.
• Maximum Coverage : Select a candidate for the migration target
from as many parity groups as possible.
• Minimum Coverage : Select a candidate for the migration target from
as few parity groups as possible.
5. Confirm that all migration source volumes and target volumes or DP
pools are paired properly, confirm that no other problems exist, and then click the  Next button. If necessary, change the pairs. To change a pair,
first select the volume pair, then from the  Other Candidates for
Migration Target  list, select the target volume to change to, and then
click the  Map Volume  button.
6. Specify plan options as necessary and then execute the task.
7. In the tasks list, confirm the execution result of the task. After a task is
created, you must not perform operations on volumes included in the
task by using Hitachi Command Suite or other programs until the task has finished executing.
Related concepts •
About data migration  on page 330
Related tasks
•
Migrating data for volume performance  on page 338
Related references •
Conditions for data migration  on page 332
340Optimizing storage performanceHitachi Command Suite User Guide