Veritas Storage Foundation Intelligent Storage Provisioning 5.0.1 Administrators Guide, HP-UX 11i v3, First Edition, November 2009

.
.
.
The default intent that ISP applies to the volumes that are being migrated is to
allocate plexes, logs and columns on separate disks. You can specify additional
rules using the -I option on the command line, or by entries in the definitions
file. You cannot include mirror, stripe or log rules. After the volumes have been
migrated, their intent is preserved by ISP as for volumes that are created directly
using the vxassist or vxvoladm commands.
Rules specified on the command line are applied to all the specified volumes.
Using a definitions file allows you to apply different rules to each volume.
Volumes that are specified on the command line are also associated with the same
storage pool. If a storage pool is not specified using the -P option, the volumes
are placed in the data storage pool of the disk group. Using a definitions file allows
the migrated volumes to be placed in different storage pools.
The following example demonstrates how to use a definitions file to migrate two
volumes to separate data and clone storage pools:
vxassist -M migrate <<!!
diskgroup "mydg"
volume "myvol" {
pool "mydatapool"
};
volume "snap_myvol" {
pool "myclonepool"
};
!!
Note the following limitations of the migration operation:
All volumes in a VVR replicated volume group (RVG) must be migrated together.
All non-ISP volumes that share a set of disks must be migrated in a single
operation.
Disks cannot be shared with any volumes that are not listed on the command
line or in a definitions file.
Volumes cannot share disks unless these disks are to be located in the same
storage pool.
Volumes with a usage type of root, such as those on a root disk that is under
VxVM control, cannot be migrated.
Administering application volumes
Migrating non-ISP volumes to ISP volumes
94