Veritas Storage Foundation Intelligent Storage Provisioning 5.0 AdministratorÆs Guide, HP-UX 11i v3, First Edition, May 2008

90 Administering application volumes
Migrating non-ISP volumes to ISP volumes
Note: New volumes that are created using the output from running the vxassist
printrules command on an existing volume are allocated storage in exactly the
same way as for that volume. If you use the output from the
vxassist
printintent command to create new volumes, the rule set is regenerated from
the capabilities and templates. This may give a different result while still
preserving the intent of the volume as advertised by the capabilities and
templates.
Migrating non-ISP volumes to ISP volumes
To make non-ISP volumes that you previously created into volumes that are
manageable by ISP, you can use the following form of the
vxassist command:
# vxassist [-g diskgroup ] [-P storage_pool] [-I rules] \
migrate
volume ...
Note: Volumes to be migrated must be CDS-compliant and have an alignment
value of 8k.
The volumes to be migrated from a disk group may be specified on the command
line, or in a definitions file that is read from the standard input if the -M option is
specified:
# vxassist [-g diskgroup ] -M migrate
The syntax of the definitions file is shown below:
diskgroup " dgname "
volume "
volumename1 " {
pool "
pool_name1 "
rules {
volume1_rules }
};
volume "
volumename2 " {
pool "
pool_name2 "
rules {
volume2_rules }
};
.
.
.
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