VERITAS Volume Manager 3.2 for HP-UX Release Notes

VERITAS Volume Manager 3.2 for HP-UX Release Notes
Initializing the VERITAS Volume Manager for HP-UX
Chapter 152
controllers, or enclosures to the appropriate file.
If you have any disks that are in use, explicitly excluding them this way allows you
to run the Quick Installation option of vxinstall.
NOTE The /etc/vx/disks.exclude, /etc/vx/cntrls.exclude,and
/etc/vx/enclr.exclude files are used only by vxinstall and vxdiskadm to
automatically exclude controllers, disks or enclosures so that these devices are
not configured as Volume Manager devices. These files do not exclude
controllers, disks, and enclosures from use by any other Volume Manager
commands. The Storage Administrator GUI, vmsa, does not use these files.
You may want to exclude from VxVM control:
raw disks that contain file systems
raw disks in use by other managing agents, such as databases.
When a VxVM utility, such as vxinstall, vxdiskadm, or vmsa, brings a disk under
VxVM control, it destroys any data on the disk. VxVM utilities recognize file
systems on raw disks, and will ask you to confirm that the data can be destroyed.
However, VxVM utilities do not recognize raw disks that are managed by other
agents. It is safest to explicitly exclude any disks in use by editing the exclude file.
You must create the exclude files, /etc/vx/disks.exclude ,
/etc/vx/enclr.exclude, and /etc/vx/cntrls.exclude, if you need them; they
are not created automatically. To exclude a disk, add its base device file name on a
line by itself in the file. For example:
$ cat /etc/vx/disks.exclude
c0t0d0
c0t2d0
c1t10d0
Adding disk controller names to /etc/vx/cntrls.exclude precludes VxVM
initialization or control of all disks on that controller. To exclude all disks on a
controller, add the controller name on a line by itself in the file. For example:
$ cat /etc/vx/cntrls.exclude
c1
c3
c8
To exclude enclosures, use /etc/vx/enclr.exclude. When the name of a disk