Migrating Volumes to ISP
To make volumes that you previously created using vxassist manageable by ISP, you can use the following form of the vxvoladm command:
# vxvoladm [-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.
After migration, you must use the vxvoladm command to administer the volumes instead of vxassist. It is not possible to perform a reverse migration.
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:
# vxvoladm [-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 migrated, their intent is preserved by ISP as for volumes that are created directly using the vxvoladm command.
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:
vxvoladm -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 vxassist-created 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.
- The disk group containing the volumes to be migrated must have a version number of 120 or greater.
|
