HP XP P9000 Command View Advanced Edition Software - Manual (Page 147)

The following indicates the maximum value and recommended user count when using Tiered Storage
Manager in Legacy mode.
Table 17 Tiered Storage Manager user count values in Legacy mode
Recommended value Maximum value Item
1 or 2 5
Number of users that access the Tiered Storage Man-
ager server at the same time.
Data migration tasks take a long time from start of execution to completion. This might affect the
performance of the 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 performed again.
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.
Conditions for data migration in Legacy mode
The conditions for data migration in Legacy mode 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).
For some volumes, the reasons why they cannot be selected as migration-source volumes or
migration-target volumes are displayed on-screen.
Volume migration requirements
All volumes for which data migration is to be performed in Legacy mode must meet the conditions
below:
• Migration-source and migration-target volumes exist within one of the following storage systems
(chassis):
• P9500 Disk Array
• XP24000/XP20000
• XP12000/XP10000/SVS200
• 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 XP24000/XP20000 is 60-03-20-00/00-xx or later and if both the mi-
gration source and the migration target volumes are THP/Smart 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-source volume is re-created. The remaining capacity can be reused. If you use the
server properties, 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.
User Guide 147