c89t0d3 | auto:hpdisk | - | - | online |
c89t0d4 | auto:hpdisk | - | - | online |
c89t0d5 | auto:hpdisk | - | - | online |
Output in agile naming scheme.
# vxdisk list |
|
|
| |
DEVICE | TYPE | DISK | GROUP | STATUS |
disk155 | auto:LVM | - | - | LVM |
disk156 | auto:LVM | - | - | LVM |
disk224 | auto:cdsdisk | - | - | online |
disk225 | auto:cdsdisk | - | - | online |
disk226 | auto:cdsdisk | - | - | online |
disk227 | auto:hpdisk | - | - | online |
disk228 | auto:hpdisk | - | - | online |
disk229 | auto:hpdisk | - | - | online |
For information on migrating an individual device or only a subset of devices, see vxdiskadm(1M). For information on foreign devices, see Veritas Volume Manager 5.1 SP1 Administrator's Guide. For more information on foreign devices and naming schemes, see the Migration from Legacy to Agile Naming Model in VxVM 5.0.1 on
Upgrading from VxVM 3.5 on
You must consider the following guideline prior to upgrading from VxVM 3.5 on
•VxVM 3.5 and VxVM 5.1 SP1 both support disk group version 90.
All upgrades from
If you upgrade to
To Upgrade from VxVM 3.5 on
To upgrade from VxVM 3.5 on
1.Stop activity to all VxVM volumes. For example, stop any applications such as databases that access the volumes, and unmount any file systems that have been created on the volumes.
2.Upgrade from
3.Upgrade from
For more information on upgrading to
4.If patches to VxVM 5.1 SP1 on
5.Install the VxVM 5.1 SP1 package.
# swinstall –x autoreboot=true -s <depot_path> Base-VxVM-51
Upon successful completion of the upgrade, VxVM 5.0 will be replaced by VxVM 5.1 SP1. Disk groups with older disk group versions (90, 120 or 140) will be accessible after the upgrade.
58 Upgrading from Previous Versions of VxVM to VxVM 5.1 SP1