VERITAS 4.1 Installation Guide (March 2006)

Setting Up Base-VXFS 4.1 and Base-VXVM 4.1

Chapter 536

VxVM uses license keys to control access. If you have not yet installed

a VxVM license key on your system, you will need to do so if you want to

use the full functionality of the product.

Licensing information:

System host ID: <hostid>

Host type: <servertype>

Are you prepared to enter a license key [y,n,q] (default: n) n

Step 2. To use enclosure-based names, enter y when prompted by the vxinstall utility:

Do you want to use enclosure based names for all disks ? y

[y,n,q,?] (default: n)

NOTE Disks use the traditional naming format, usually c#t#d#.

Enclosure-based naming allows disk devices to be named for

enclosures rather than for the controllers through which they are

accessed. In a Storage Area Network (SAN) that uses Fibre Channel

hubs or fabric switches, information about the disk location provided

by the operating system may not correctly indicate the physical

location of the disks. Enclosure-based naming allows VxVM to access

enclosures as separate physical entities. By conﬁguring redundant

copies of your data on separate enclosures, you can safeguard your

data against failure of one or more enclosures.

Step 3. To set up a system wide default disk group, enter y when prompted by the

vxinstall utility:

Do you want to setup a system wide default disk group ?

[y,n,q,?] (default: y)

If you know the name of the disk group to be used as the default disk group, enter

y, and type the name of the disk group at the prompt, or use the list option and

make a selection. Otherwise, enter n if you do not want to deﬁne a default disk

group.

NOTE In releases prior to VxVM 3.5, the default disk group was rootdg (the

root disk group). For VxVM 3.5 to function, the rootdg disk group

had to exist, and it had to contain at least one disk. This is no longer