VERITAS Volume Manager 3.5 Release Notes (August 2003)

VERITAS Volume Manager™ HP-UX 11i v2 Release Notes
Patches and Fixes in This Version
Chapter 144
After Upgrading to VxVM 3.5
If you upgrade your system to Volume Manager 3.5 and you have
persistent simple or nopriv disks and you select to change from c#t#d#
naming to enclosure-based naming, these disks may be in an error state
after upgrading. To recover these disks, run vxdarestore after you have
completed the upgrade.
After Changing Your Disk Naming Scheme
If you change your Volume Manager 3.5 system to enclosure-based
naming using vxdiskadm, you need to check any persistent simple or
nopriv disks, as these disks may be in an error state after the change. To
recover these disks, run vxdarestore.