VERITAS Volume Manager 3.5 Migration Guide (August 2002)

Examples Final 24 July 2002
30 VERITAS Volume Manager Migration Guide
Group conversion may require a reboot for the changes to take
effect. For this release, only Non-root LVM Volume Groups are
allowed to be converted.
More than one Volume Group or pattern may be entered at the prompt.
Here are some LVM Volume Group selection examples:
all: analyze all LVM Volume Groups (all except Root VG)
listvg:list all LVM Volume Groups
list: list all disk devices
vg_name:a single LVM Volume Group, named vg_name
<pattern>:for example vg08 vg09 vg05
Select Volume Groups to convert :
[<pattern-list>,all,list,listvg,q,?] listvg
LVM VOLUME GROUP INFORMATION
NAME TYPE PHYSICAL VOLUME
vg00 ROOT c4t6d0
vg05 Non-Root c4t5d0
vg03 Non-Root c4t3d0 c4t2d0
vg08 Non-Root c4t8d0
Select Volume Groups to convert :
[<pattern-list>,all,list,listvg,q,?] vg08
vg08
Convert this Volume Group? [y,n,q,?] (default: y)
Name a new disk group [<group>,list,q,?] (default: dg08)
The following disk has been found in the vg08 volume group and will
be configured for conversion to a VxVM disk group.
c4t8d0
A new disk group dg08 will be created and the disk device c4t8d0
will be converted and added to the disk group with the disk name
dg0801.
The c4t8d0 disk has been configured for conversion.
The first stage of the conversion operation has completed
successfully. If you commit to the changes hereafter, the system
will attempt to umount all of the associated file systems, stop
and export each Volume Group, and then attempt to complete the
conversion without having to reboot the system. If we are unable
to stop and export any of the Volume Groups, then the conversion
process will not be able to complete without a reboot.You would
then be given the choice to either abort the conversion, or
finish the conversion by rebooting the system.