HP StorageWorks P9000 Tiered Storage Manager Software 7.1.1 CLI Reference Guide (TB585-96014, September 2011)

• The migration task is changed to the terminated (canceled) status by using the CancelTask
command.
• The migration task ends with a failure.
Once migration terminates normally, the controller LDEV numbers of the migration source and target
volumes are swapped. Note that the labels assigned to the volumes remain the same. If you want to
change these labels along with migration, do so after the migration task is executed. In addition, do
not specify a label for the migration target volume until execution of the migration task ends.
By default, the data on a migration source volume is not deleted after migration (The default value of
the server.migration.dataErase.defaultValue key is false (do not delete)). However,
to prevent any inadvertent disclosure of information, HP recommends that you use the erasedata
parameter to erase all the data on the migration source volume immediately after a migration.
You can specify whether the data on the migration source volume should be erased after migration
terminates normally (the erasedata parameter) and whether the unused capacity on the migration
target volume should be released (the zerodatadiscard parameter). When the zero data discard
function is performed, the unused capacity of the pool can be increased by releasing unused pages
in virtual volumes.
If you specify that the data in the migration source volume is to be erased, before executing the
CreateMigrationTask command, make sure that data erasure software (Volume Shredder) has
been installed on your storage system. If you specify that the data is to be erased on a storage system
in which Volume Shredder is not installed, and then execute the CreateMigrationTask command,
the error message KATS50315-E will be displayed. If Volume Shredder has not been installed on
the storage system, perform either of the following operations so that the CreateMigrationTask
command is not set to erase the data in the migration source volume, and then execute the command:
• Specify No for the erasedata parameter.
• Omit the erasedata parameter, and specify parameter.erasedata=No in the htsmcli.prop-
erties file. (Even if server.migration.dataErase.defaultValue=true is specified in
the server.properties file, the setting in the htsmcli.properties file is given priority.)
• Omit the erasedata parameter, and specify server.migration.dataErase.default-
Value=false in the server.properties file while parameter.erasedata is not specified
in the htsmcli.properties file.
When the migration source is a THP volume and the migration target is a THP pool, if you attempt to
erase the data in the migration source volume, the actual data that is erased might vary depending
on whether Open Volume Management is installed. For details, see “Conditions for migrating data
to THP pools” on page 203.
CAUTION:
During the execution of a migration in which a volume is re-created, if an error occurs during the
processing or the processing stops in the middle, the migration target volume might remain deleted.
Check the output message, and then manually create the volume.
Details of CLI commands108