veritas volume manager 3 - origin...

VERITAS Volume Manager ™ 3.1

Installation Guide

HP-UX

August 200030-000006-399

Disclaimer

The information contained in this publication is subject to change without notice.

VERITAS Software Corporation makes no warranty of any kind with regard to this

manual, including, but not limited to, the implied warranties of merchantability and

fitness for a particular purpose. VERITAS Software Corporation shall not be liable for

errors contained herein or for incidental or consequential damages in connection with the

furnishing, performance, or use of this manual.

Copyright

Copyright © 1998-2000 VERITAS Software Corporation. All rights reserved. VERITAS is a

registered trademark of VERITAS Software Corporation in the US and other countries.

The VERITAS logo and VERITAS Volume Manager are trademarks of VERITAS Software

Corporation. All other trademarks or registered trademarks are the property of their

respective owners.

Printed in the USA, August 2000.

VERITAS Software Corporation

1600 Plymouth St.

Mountain View, CA 94043

Phone 650–335–8000

Fax 650–335–8050

www.veritas.com

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Related Web Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Chapter 1. Pre-installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Basic Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Verifying Operating System Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Accessing Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Assuring Sufficient Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Selecting Disks for VxVM Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Enabling the Hot-Relocation Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Obtaining a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. Installing the Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Procedure Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Loading the Software from CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

iii

Disabling Hot-Relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Initializing the Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Excluding Disks from Volume Manager Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Excluding Controllers from Volume Manager Control . . . . . . . . . . . . . . . . . . . . . . . 14

Basic vxinstall Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Volume Manager Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Setting Up and Starting the Storage Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Storage Administrator Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Installing the Storage Administrator Server and/or Client (UNIX) . . . . . . . . . . . . 29

Customizing Security (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Starting the Storage Administrator Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Starting the Storage Administrator Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Running the Storage Administrator in Read-Only Mode . . . . . . . . . . . . . . . . . . . . . 32

Enabling Cluster Support in Volume Manager (Optional) . . . . . . . . . . . . . . . . . . . . . . . 34

Configuring Shared Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Upgrading to VxVM and Storage Administrator to Release 3.1 . . . . . . . . . . . . . . . . . . 35

Upgrading VxVM and Storage Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Checking Volume Manager Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Deinstalling Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Shutting Down the Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Removing the Volume Manager Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Removing the VM Storage Administrator Package . . . . . . . . . . . . . . . . . . . . . . . . . . 42

iv VERITAS Volume Manager Installation Guide

Preface

IntroductionThis document provides information on installing and initializing the VERITAS Volume

ManagerTM (VxVM) and the VERITAS Volume Manager Storage AdministratorTM (VMSA)

graphical user interface.

OrganizationThis guide is organized with the following sections:

◆ Pre-installation Instructions

◆ Installing the Volume Manager

◆ Initializing the Volume Manager

◆ Setting Up and Starting the Storage Administrator

◆ Enabling Cluster Support in Volume Manager (Optional)

◆ Upgrading to VxVM and Storage Administrator to Release 3.1

◆ Checking Volume Manager Processes

◆ Deinstalling Volume Manager

Related DocumentsThe following documents contain related information:

◆ VERITAS Managing HP-UX with SD-UX Guide

◆ VERITAS Volume Manager Migration Guide

v

Related Web Sites

Related Web SitesFor additional information about VERITAS and VERITAS products, visit the following

web site:

www.veritas.com

For an up-to-date list of patches currently required for the HP-UX operating system, visit

the following web site:

support.veritas.com

The table of current patches is located in Volume Manager, Volume Manager for UNIX,

Knowledge Base.

Getting HelpFor assistance with any of the VERITAS products, contact VERITAS Technical Support:

◆ U.S. and Canadian Customers: 1-800-342-0652

◆ International: +1-650-335-8555

◆ Email: [email protected]

For license information:

◆ Phone: 1-650-318-4265


◆ Fax: 1-650-335-8428

For software updates:

◆ Phone: 1-650-526-2549


vi VERITAS Volume Manager Installation Guide

Conventions

ConventionsThe following table describes the typographic conventions used in this guide.

Typeface Usage Examples

monospace Computer output, files,

directories, software elements

such as command options,

function names, and parameters

Read tunables from the

/etc/vx/tunefstab file.

See the ls (1) manual page for more

information.

monospace(bold )

User input # mount -F vxfs /h/filesys

italic New terms, book titles,

emphasis, variables replaced

with a name or value

See the User’s Guide for details.

The variable ncsize determines the

value of...

Symbol Usage Examples

% C shell prompt

$ Bourne/Korn shell prompt

# Superuser prompt (all shells)

\

Continued input on the

following line; you do not type

this character

# mount -F vxfs \

/h/filesys

[ ] In a command synopsis, brackets

indicates an optional argument

ls [ -a ]

| In a command synopsis, a

vertical bar separates mutually

exclusive arguments

mount [ suid | nosuid ]

Preface vii

Conventions

viii VERITAS Volume Manager Installation Guide

Pre-installation Instructions
1 Introduction
The following topics are covered in this chapter:

◆ Overview

◆ Basic Preparation

◆ Verifying Operating System Environment

◆ Accessing Directories

◆ Assuring Sufficient Disk Space

◆ Selecting Disks for VxVM Initialization

◆ Enabling the Hot-Relocation Feature

◆ Obtaining a License Key

OverviewReview the following items and make any appropriate changes before you install or

upgrade the Volume Manager.

Basic Preparation

Most of the commands used in the installation are in the /sbin or /usr/sbin directory.

Add these directories to your PATH environment variable as shown below. For a Bourne

Shell (sh or ksh ), use the command:

# PATH=/sbin:/usr/sbin:$PATH export PATH

For a C Shell (csh or tcsh), use the command:

% setenv PATH /sbin:/usr/sbin:${PATH}

1

Overview

Verifying Operating System Environment

This VERITAS VxVM release can only be installed on an HP-UX system running with the

XSWGR1100 (B.11.00.45) Extension Pack (May 1999). Descriptions of the installation of the

Extension Pack are provided by Hewlett-Packard along with the installation media.

The SD-UX packaging for VxVM verifies that the target machine is running the

appropriate level of the HP-UX 11.0 operating system. Installation of VxVM does not

occur if the system is not up to this release level. To ensure that the operating system is

running at the appropriate release level, use the following command:

# swlist -l bundle XSWGR1100

The output must contain:

XSWGR1100 B.11.00.45 HP-UX Extension Pack, May 1999

Installing HP-UX Operating System Patches

The VERITAS Volume Manager also requires additional updates to the HP-UX operating

environment in order to work properly. These updates are available as patches through

standard HP-UX patch distribution facilities. In some cases, the patches provide

functionality without which the Volume Manager panics your system.

Note Do not try to perform a Volume Manager installation without installing all of the

mandatory patches to HP-UX.

The following table shows all patches required for VxVM, and indicates which patches are

mandatory and which are optional. Optional patches can provide functionality without

which VxVM does not operate correctly. Lack of these patches does not harm your system

in any way; however, the lack of mandatory patches does cause harm. To ensure

maximum system efficiency, install all patches.

The following is a list of the HP-UX Operating System patches to be installed:

Patch Number Mandatory/Optional Description

PHKL_19245 mandatory scsi3/disc30 patch (includes passthru ioctl)

PHKL_19246 mandatory vm_superpage fix

PHCO_17454 optional mkfs_hfs VxVM coexistence patch

PHCO_17455 optional mkfs_vxfs VxVM coexistence patch

PHCO_19205 optional LVM commands cumulative patch

PHCO_19491 optional libc cumulative patch

PHSS_15853 optional Xserver cumulative patch

2 VERITAS Volume Manager Installation Guide

Overview

Specific patch numbers are correct at the time of this release. If subsequent patches

supersede any of these, the required patch numbers will change. Search mechanisms

provided through Hewlett Packard’s patch distribution sites help you locate successor

patches using the patch numbers provided here. In addition, VERITAS provides an

up-to-date list of currently required patches on its web site, support.veritas.com .

The table of current patches is located in Volume Manager, Volume Manager for UNIX,

Knowledge Base.

Note Volume Manager package scripts confirm that the mandatory HP-UX patches are

installed on your system before allowing Volume Manager installation. You are also

warned if any of the optional patches are not found.

Accessing Directories

The manual pages in the VRTSvxvm package are written into /usr/share/mandirectories. Installation of the VRTSvmdoc package copies documents into

/usr/share/doc . Write permission is required for each of these directories.

Assuring Sufficient Disk Space

Before installing the VERITAS Volume Manager software and related patches, verify that

there is sufficient disk space to contain all of the software. The SD-UX tools check space

available and prevent installation if a space problem is detected.

The following table shows the minimum space allowances for each package:

PHSS_19593 optional X/Motif2.1 Runtime SEP99 cumulative

patch

PHSS_19748 optional CDE Runtime SEP 99 cumulative patch

Patch Number Mandatory/Optional Description

Package Contents Size

VRTSvxvm Driver and Utilities 36Mb

VRTSvmdoc Documentation 10Mb

VRTSvmsa Storage Administrator Server and Client (UNIX) 26Mb

VRTSlic VERITAS Licensing Utilities .5Mb

Chapter 1, Pre-installation Instructions 3

Overview

Selecting Disks for VxVM Initialization

The vxinstall command initializes the Volume Manager, as described below. Tasks

performed through vxinstall include initializing disks and bringing them under

Volume Manager control. Be aware of the contents of all disks on your system so that you

can determine the disposition of each as vxinstall is run.

During the initialization process, you must decide whether you wish to place all or just

some of the disks on a controller under Volume Manager control. Two types of installation

are available, as follows:

◆ Custom Installation, to initialize certain disks and not others

◆ Quick Installation, to initialize all disks on a controller together

In order to complete a VxVM initialization through vxinstall, select at least one disk

to bring under Volume Manager control. Alternately, use the vxinstall -C option to

convert an existing LVM Volume Group as described on page 13. Even if you use the

conversion option for vxinstall , it is recommended that you survey your attached

disks as described below.

When you run vxinstall , disks that you want to initialize for Volume Manager control

cannot be under the control of LVM; vxinstall does not allow initialization of LVM

disks for VxVM control. If any disk that you want to bring under VxVM control is

currently under LVM control, execute the following commands before running

vxinstall :

1. lvremove to remove any LVM volumes using the disk

2. vgreduce to remove the disk from any LVM volume groups to which it belongs

3. pvremove to erase the LVM disk headers

Note If the disk to be removed is the last disk in the volume group, use vgremove to

remove the volume group and then use pvremove to erase the LVM disk headers.

If the disk is not currently in use by any volume or volume group, but has been initialized

by pvcreate , you must still use pvremove to remove LVM disk headers.

The pvremove command is a new LVM command designed to aid LVM and VxVM

coexistence on a system. It is currently included in the PHCO_19205 patch (or successor

patch), which is available through standard HP-UX patch update services.


Overview

Enabling the Hot-Relocation Feature

The hot-relocation feature is enabled by default. The associated daemon, vxrelocd , is

automatically started during system startup. To disable hot-relocation, prevent vxrelocdfrom running after you load the VxVM software. See “Disabling Hot-Relocation” on

page 12 for details.

Obtaining a License Key

VxVM is a licensed product. When you purchase this product, a license key must be

issued by VERITAS Customer Support. Some features require a separate license key.

Obtain your license key before installing or upgrading this product. Store license key

information in a location apart from the computer for use if the system requires

reinstallation.

To obtain a license key, complete the License Key Request Form and fax it to VERITAS

Customer Support (see the Preface in this Guide for contact information).

To issue a new license key, VERITAS Customer Support requires the host ID and the

machine type. Obtain the host ID with the following command:

# /bin/uname -i

Obtain the machine type with the following command:

# /bin/uname -m

During installation/initialization, you are prompted for the license key. If the software is

already installed and you are upgrading or replacing an evaluation license with a

permanent license, follow the instructions that accompany the license key to replace the

old license with the new one.

Chapter 1, Pre-installation Instructions 5

Overview


Installing the Volume Manager
2 Introduction
The following topics are covered in this chapter:

◆ Procedure Overview

◆ Loading the Software from CD-ROM

◆ Troubleshooting

◆ Disabling Hot-Relocation

◆ Initializing the Volume Manager

◆ Excluding Disks from Volume Manager Control

◆ Excluding Controllers from Volume Manager Control

◆ Basic vxinstall Initialization

◆ Volume Manager Processes

◆ Setting Up and Starting the Storage Administrator

◆ Storage Administrator Installation Overview

◆ Installing the Storage Administrator Server and/or Client (UNIX)

◆ Customizing Security (Optional)

◆ Starting the Storage Administrator Server

◆ Starting the Storage Administrator Client

◆ Running the Storage Administrator in Read-Only Mode

◆ Enabling Cluster Support in Volume Manager (Optional)

◆ Configuring Shared Disks

◆ Upgrading to VxVM and Storage Administrator to Release 3.1

◆ Upgrading VxVM and Storage Administrator

◆ Checking Volume Manager Processes

7

Procedure Overview

◆ Deinstalling Volume Manager

◆ Preparation

◆ Shutting Down the Volume Manager

◆ Removing the Volume Manager Package

◆ Removing the VM Storage Administrator Package

Procedure OverviewInstall the VERITAS Volume Manager and set up the Storage Administrator as follows:

1. Install any necessary patches to the HP-UX system as described in “Installing HP-UX

Operating System Patches” on page 2.

2. Obtain a software license key as described in “Obtaining a License Key” on page 5.

3. Install the VERITAS Volume Manager and Storage Administrator software packages

onto the system as described in “Loading the Software from CD-ROM” on page 8.

4. Initialize VxVM using vxinstall as described in “Initializing the Volume

Manager” on page 12.

5. Set up and start the Storage Administrator as described in “Setting Up and Starting

the Storage Administrator” on page 28.

Loading the Software from CD-ROM

Packages

The VERITAS Volume Manager CD-ROM contains the following packages:

◆ VRTSvxvm—the base Volume Manager software and manual pages.

◆ VRTSvmsa—the Volume Manager Storage Administrator graphical user interface

(GUI) software.

◆ VRTSvmdoc—online copies of the VERITAS documents.

◆ VRTSlic —the VERITAS licensing utilities.

Mounting the CD-ROM

Load the software from the CD-ROM as follows:


Procedure Overview

1. Log in as a superuser.

2. Insert the VERITAS CD-ROM into a CD-ROM drive connected to your system.

3. Mount the CD-ROM by determining the device access name of the CD-ROM device.

The format for the device access name is cx t ydz, where x is the controller number, yis the target number, and z is the device number. After inserting the CD-ROM into the

CD-ROM drive, enter the following commands:

# mkdir -p /cdrom# mount -o ro /dev/dsk/c xt ydz /cdrom

Note The installation process may generate one or more messages indicating that the

media is not writable. You can ignore these messages.

Installing VERITAS Volume Manager

There are two methods of installing the VERITAS Volume Manager packages from the

CD-ROM. VERITAS recommends that you use the vmins script provided on the

CD-ROM. You can also use swinstall directly.

Installation using vmins

The vmins script verifies both the proper release level of the HP-UX operating system

and the installation of all necessary HP-UX operating system patches. Once the operating

system state is checked, the script allows you to select which Volume Manager packages

to install and then installs the selected packages on your system.

The vmins script is interactive and directs you through installation and any necessary

troubleshooting. To invoke the script, enter:

# /cdrom/vmins

Installation using swinstall

To use swinstall, your HP-UX operating system must be at the proper release level for

VxVM installation. Review “Installing HP-UX Operating System Patches” on page 2 to

verify this. You can then use swinstall directly to install VxVM packages.

The following description of swinstall is for a simple, non-interactive install of each

package. You can also use either the interactive swinstall or the SAM menus to do the

installation; however, neither the interactive swinstall or the SAM installation options

are described here.

All of the VERITAS Volume Manager packages are collected in the depot in the VxVM

directory of the CD-ROM.

Chapter 2, Installing the Volume Manager 9

Procedure Overview

You can install each package individually or several packages in a group with one

swinstall invocation. You must decide whether you want to install the VRTSdocpackage at this point. The VRTSvxvm package is the base Volume Manager software

installation and it is dependent on the VRTSlic package; you must install at least these

two packages. When you install the Volume Manager package, an autoreboot occurs.

Note You must install the VRTSlic package with any VRTSvxvm package installation.

The Volume Manager Storage Administrator GUI contains some Java class files with file

names longer than 37 characters. The cdfs file system does not allow names of this

length. Because of this restriction, the package for VMSA is in the SD-UX archive format

(referred to as the “tape format” in the “swpackage” man page) and not in the file system

(directory) format. The following command line examples showing the installation of the

VERITAS packages differ slightly for VMSA because the VMSA package format is

different.

To install the basic Volume Manager package (and the licensing utilities for it), enter:

# swinstall -x autoreboot=true -s /cdrom/vxvm VRTSlic VRTSvxvm

To install the basic Volume Manager package without the EMC patch, enter:

# swinstall -x autoreboot=true -x autoselect_patches=false \-s/cdrom/vxvm VRTSlic VRTSvxvm

To install the Volume Manager and documentation packages, enter:

# swinstall -x autoreboot=true -x allow_downdate=false \-s /cdrom/vxvm VRTSlic VRTSvxvm VRTSvmdoc

Installing VERITAS Volume Manager Storage Administrator

The VERITAS Volume Manager Storage Administrator is the GUI for the VERITAS

Volume Manager. If you wish to use the GUI, you must install Storage Administrator on

all machines on which Volume Manager is installed. An autoreboot is not required

when installing the Storage Administrator.

Before you can run Storage Administrator, you need to install and then initialize Volume

Manager.

To install the VERITAS Volume Manager Storage Administrator package and client, enter:

# swinstall -s /cdrom/vxvm/VRTSvmsa VRTSvmsa

To install the VERITAS Volume Manager Storage Administrator package (client-only),

enter:

# swinstall -s /cdrom/vxvm/VRTSvmsa VRTSvmsa.VMSA-CLIENT-SP


Procedure Overview

Troubleshooting

Possible problem:

If you install on a hostname cshp1, your root file system is vxfs and you get the following

message:

ERROR: There is currently no depot software on host “cshp1” atlocation “/cdrom/vxvm”.Source connection failed for “cshp1:/cdrom/vxvm”.Selection had errors.

The workaround for this situation is to rerun /cdrom/vmins or swinstall. This will

resolve the problem.

Possible problem:

If the kernel is not rebuilt and the system doesn’t reboot, check the log file, identify and

correct the problem, and rebuild the kernel, as follows:

1. Check the log file. If errors are reported during swinstall , the errors are logged in

the file /var/adm/sw/swagent.log . Refer to the Managing HP-UX with SD-UXGuide for more information.

2. Identify and correct the problem.

3. Rebuild the kernel. The kernel building and rebooting process is described in the

following steps.

a. Change directories to /stand/build using the following command:

# cd /stand/build

b. Create a new system file from the running kernel using the following command:

# /usr/lbin/sysadm/system_prep -s system

c. Edit the kernel with the planned changes using the following command. (This

step is not necessary if the drivers are already in the system file.)

# vi system

d. Build the new kernel using the following command:

# /usr/sbin/mk_kernel -s system

e. Move the old system and vmunix file using the following command. (If you

encounter any problems, reboot the system from the old kernel.)


Initializing the Volume Manager

# mv /stand/system /stand/system.prev# mv /stand/vmunix /stand/vmunix.prev# mv /stand/dlkm /stand/dlkm.vmunix.prev

f. Move the new system file and new kernel into place using the following

command. (This step prepares the new system file and new kernel for the system

reboot.)

# mv /stand/build/system /stand/system# kmupdate /stand/build/vmunix_test

g. Change directory to root. This will prepare for the shutdown command.

# cd /

h. Reboot the system off the new kernel using the following command:

# shutdown -ry now

Disabling Hot-Relocation

The hot-relocation feature is enabled by default and it is recommended that you leave it

on. However, you can disable it by preventing the vxrelocd daemon from starting up

during system startup. This should be done after the VxVM packages have been installed.

To disable hot-relocation, comment out the vxrelocd line in the startup file

/sbin/rc2.d/S095vxvm-recover , as follows:

# nohup vxrelocd root &

Initializing the Volume ManagerThis section describes how to initialize the Volume Manager using the vxinstallprocedure. Initializing Volume Manager does the following:

◆ ensures that proper licenses for the VERITAS Volume Manager software are in place,

given license keys previously obtained from VERITAS customer support.

◆ allows you to set up the initial Volume Manager disk group and populate it with

disks.

◆ starts the various configuration, notification, and relocation daemons used by Volume

Manager.

The first two tasks require user information. Obtain the license keys necessary to complete

Volume Manager initialization by referring to “Obtaining a License Key” on page 5. After

you obtain the license key, survey the disks on your system to determine which of them

will go under Volume Manager control.



Like LVM, VxVM puts collections of disks into groups. In LVM, these disk collections are

known as volume groups, and in VxVM, they are referred to as disk groups. In order for

VxVM to initialize, the default disk group rootdg must be set up using vxinstall .

To set up rootdg , initialize at least one disk into the group. A minimum vxinstallsession includes setting up licenses and giving one disk over to the rootdg VxVM disk

group.

Two methods are available to bring disks under VxVM control, as follows:

◆ basic vxinstall places disks that are currently not in use by LVM or other data

managers (databases, file systems) under VxVM control. This is the preferred method.

◆ vxinstall -C converts an existing LVM volume group to VxVM. If you use the

vxinstall -C option, read the VERITAS Volume Manager Migration Guide section

dealing with conversion from LVM to VxVM. The vxinstall -C option invokes the

vxvmconvert utility to convert LVM Volume Groups to VxVM disk groups. Become

familiar with the cautions about using vxvmconvert .

To place some of your disks in another disk group, wait until after vxinstall is run and

rootdg is set up. Use vxdiskadm and the Storage Administrator GUI to create and

populate the other groups. Remember that you must place at least one disk under Volume

Manager rootdg control using vxinstall before other tools can be used.

Excluding Disks from Volume Manager Control

To exclude specific disks from Volume Manager control, add the names of those disks to

the /etc/vx/disks.exclude file.

LVM disks are automatically excluded from VxVM control and do not need to be added to

the /etc/vx/disks.exclude file. No Volume Manager utility can be used to initialize

an LVM-controlled disk. You must take specific actions to remove a disk from LVM

control before attempting to place it under VxVM control.

Volume Manager utilities recognize file systems on raw disks (not under LVM control).

Raw disks with file systems cannot be placed under Volume Manager control without

administrator confirmation that the disk file system be destroyed. However, to avoid any

possible confusion, enter these disks in the disks.exclude list.

Raw disks in use by other managing agents, such as databases, are not automatically

recognized by VxVM utilities. These disks are good candidates for inclusion in the

disks.exclude file.

The disks.exclude file is not created by VxVM software installation. To add disk

names to this file, you must create the file. To list a disk in the file, enter only the base

device file name. For example:

c0t0d0c0t2d0



c1t10d0

To add disks that are in use by LVM volumes to the disks.exclude file, add all disks in

the volume group to which the disk belongs. For example:

# for i in ‘vgdisplay -v uservg | grep dsk | awk ’{print $3}’‘# do# basename $i# done

Note At least one disk must remain in rootdg at all times while VxVM is running.

Excluding Controllers from Volume Manager Control

The /etc/vx/cntrls.exclude file is used to list controllers. When the name of a disk

controller is added to this file, Volume Manager does not initialize or control all disks on

the controller.

The following is an example of the file’s contents:

c1c3c8

Basic vxinstall Initialization

The following description is for the basic vxinstall initialization option. For a full

presentation of the vxinstall -C option, see the VERITAS Volume Manager MigrationGuide description of vxvmconvert .

After completing the package install, initialize the Volume Manager as follows:

1. Log in as root .

2. Set up any lists of disks and/or controllers to exclude from VxVM control. See

“Excluding Disks from Volume Manager Control” on page 13 and “Excluding

Controllers from Volume Manager Control” on page 14.

3. Run vxinstall :

# vxinstall

vxinstall runs the vxlicense command to initialize the Volume Manager license

key file, displays licensing information, and then prompts for a key. You must obtain

and enter a valid key in order to proceed with the initialization. Refer to “Obtaining a

License Key” on page 5.



After the key is entered,vxinstall populates the /dev/vx/dmp directories with the

appropriate VxVM DMP nodes and examines all controllers attached to the system.

Notes are displayed as each action is performed.

Starting menus are displayed with the results of the controller search and an

introduction to the installation process. You are then prompted for either a “quick” or

a “custom” installation.

4. Select either 1 (Quick Installation) or 2 (Custom Installation) to proceed with the

installation.

◆ If you choose Quick Installation, go to “Quick Installation” on page 15.

◆ If you choose Custom Installation, go to “Custom Installation” on page 19.

Note Quick Installation places every disk and controller on your system under Volume

Manager control with the exception of disks under LVM control. To exclude specific

disks and controllers, refer to “Excluding Disks from Volume Manager Control” on

page 13 and “Excluding Controllers from Volume Manager Control” on page 14, or

choose the Custom Installation option.

Quick Installation

The Quick Installation option is the easiest to use. For each controller, Quick Installation

provides the option of initializing all disks. To initialize only certain disks on a controller,

use Custom Installation instead.

You cannot use Quick Installation to initialize disks on a controller if LVM logical volumes

are found on those disks. Avoid selecting the initialize option for any disks containing

valid data. The following session example illustrates a Quick Installation.

Example: Quick Installation

Volume Manager InstallationMenu: VolumeManager/Install

The Volume Manager names disks on your system using the controller and disk number of the disk, substituting them into the following pattern:

c<controller>t<disk>d<disk>

NOTE: With the Dynamic Multipathing (DMP) facility of VxVM, the controller number represents a multipath pseudo controller number for those disk devices with multiple access paths. For example, if a disk has 2 paths from controllers c0 and c1, then the Volume Manager displays only one of them, such as c0, to represent both



of the controllers.

c0t0d0- first controller, first target, first diskc1t0d0- second controller, first target, first diskc1t1d0- second controller, second target, first disk

The Volume Manager has detected the following controllers on your system:

c0:c1:

Hit RETURN to continue.


You will now be asked if you wish to use Quick Installation or Custom Installation. Custom Installation allows you to select how the Volume Manager will handle the installation of each disk attached to your system.

Quick Installation examines each disk attached to your system and attempts to create volumes to cover all disk partitions that might be used for file systems or for other similar purposes.

If you do not wish to use some disks with the Volume Manager, or if you wish to reinitialize some disks, use the Custom Installation option Otherwise, we suggest that you use the Quick Installation option.


Volume Manager Installation OptionsMenu: VolumeManager/Install

1 Quick Installation 2 Custom Installation

? Display help about menu ?? Display help about the menuing system q Exit from menus

Select an operation to perform:

1



Note The vxinstall option prompts for each controller and disk it finds connected to

your system. When a default response is displayed in parentheses, press Return to

accept that default. At any of the vxinstall prompts, you can select q to abandon

the initialization and then start over. Disks are initialized at the end of the

vxinstall procedure. If you quit vxinstall before it initializes the disks, all

disks are left as they were before vxinstall was started.

Volume Manager Quick InstallationMenu: VolumeManager/Install/QuickInstall/c0Generating list of attached disks on c0....

The Volume Manager has detected the following disks on controllerc0:

c0t1d0 c0t1d1 c0t1d2 c0t1d3 c0t1d4


Volume Manager Quick Installation For Controller c0Menu: VolumeManager/Install/QuickInstall/c0

Initialize all disks on this controller ? (destroys data on thesedisks)[y,n,q,?] (default: n)

Note If you enter y, vxinstall prompts you for confirmation and warns you that this

action destroys existing data on the disks. If you enter n, the disks are not

initialized.

y

Are you sure ? (destroys data on these disks)[y,n,q,?] (default: n) y

Volume Manager will now initialize all the disks on this controllerHit RETURN to continue.

Volume Manager Quick InstallationMenu: VolumeManager/Install/QuickInstall/c0/Init

Use default disk names for these disks? [y,n,q,?] (default: y)



Note If you enter y, vxinstall automatically assigns and lists default disk names for

each disk. If you enter n, vxinstall prompts you for a disk name for each disk on

the controller individually. For each disk, respond with the desired disk name and

press Return.

y

The c0t1d0 disk will be given disk name disk01 The c0t1d1 disk will be given disk name disk02 The c0t1d2 disk will be given disk name disk03 The c0t1d3 disk will be given disk name disk04 The c0t1d4 disk will be given disk name disk05


Volume Manager Quick InstallationMenu: VolumeManager/Install/QuickInstall/c1Generating list of attached disks on c1....

<excluding root disk c1t5d0><excluding LVM disk c1t6d0>

No disks were found attached to controller c1 !


Volume Manager Quick InstallationMenu: VolumeManager/Install/QuickInstall

The following is a summary of your choices.c0t1d0 New Disk c0t1d1 New Disk c0t1d2 New Disk c0t1d3 New Disk c0t1d4 New Disk

Is this correct [y,n,q,?] (default: y)

Note This is your last chance to review and alter your choices for the disks to be placed

under Volume Manager control. If you enter y, vxinstall initializes and destroys

any existing data on all disks listed with New Disk . If you enter n, vxinstallprompts for the name of a disk to be removed from the list and excluded from

Volume Manager control. To remove a disk from the list, enter the name of the disk

to be removed from the list and press Return. Repeat for each disk to be removed



and then press Return once more. The vxinstall option now displays an updated

summary that excludes the disks chosen for removal. If you are satisfied with the

summary, enter y.

y

The Volume Manager is now reconfiguring (partition phase)...

Volume Manager: Initializing c0t1d0 as a new disk. Volume Manager: Initializing c0t1d1 as a new disk. Volume Manager: Initializing c0t1d2 as a new disk. Volume Manager: Initializing c0t1d3 as a new disk. Volume Manager: Initializing c0t1d4 as a new disk.

The Volume Manager is now reconfiguring (initialization phase)... Volume Manager: Adding disk01 (c0t1d0) as a new disk.

The Volume Daemon has been enabled for transactions. Volume Manager: Adding disk02 (c0t1d1) as a new disk. Volume Manager: Adding disk03 (c0t1d2) as a new disk. Volume Manager: Adding disk04 (c0t1d3) as a new disk. Volume Manager: Adding disk05 (c0t1d4) as a new disk. Starting the relocation daemon, vxrelocd#Installation is complete.

Custom Installation

Custom Installation allows you to control which disks are placed under Volume Manager

control and how they are added. This is important if you do not want all your disks

placed under Volume Manager control. Custom Installation also provides the option of

initializing all disks on a controller or initializing just certain disks on a controller. The

following session example illustrates a Custom Installation.

Example: Custom Installation


The Volume Manager names disks on your system using the controller and disk number of the disk, substituting them into the following pattern:

c<controller>t<disk>d<disk>

NOTE: With the Dynamic Multipathing (DMP) facility of VxVM, the



controller number represents a multipath pseudo controller number for those disk devices with multiple access paths. For example, if a disk has 2 paths from controllers c0 and c1, then the Volume Manager displays only one of them, such as c0, to represent both of the controllers.

Some examples would be:

c0t0d0- first controller, first target, first diskc1t0d0- second controller, first target, first diskc1t1d0- second controller, second target, first disk

The Volume Manager has detected the following controllers on your system:

c0:c1:



You will now be asked if you wish to use Quick Installation or Custom Installation. Custom Installation allows you to select how the Volume Manager will handle the installation of each disk attached to your system.

Quick Installation examines each disk attached to your system and attempts to create volumes to cover all disk partitions that might be used for file systems or for other similar purposes.

If you do not wish to use some disks with the Volume Manager, or if you wish to reinitialize some disks, use the Custom Installation option Otherwise, we suggest that you use the Quick Installation option.


Volume Manager Installation OptionsMenu: VolumeManager/Install

1 Quick Installation 2 Custom Installation

? Display help about menu ?? Display help about the menuing system



q Exit from menus

Select an operation to perform:2

Note The vxinstall option prompts for each controller and disk it finds connected to

your system. When a default response is displayed in parentheses, press Return to

accept that default. At any of the vxinstall prompts, you can select q to abandon

the initialization and then start over. Disks are initialized at the end of the

vxinstall procedure. If you quit vxinstall before it initializes the disks, all

disks are left as they were before vxinstall was started.

Volume Manager Custom InstallationMenu: VolumeManager/Install/Custom/c0Generating list of attached disks on c0....


c0t12d0 c0t13d0 c0t14d0 c0t15d0


Installation options for controller c0Menu: VolumeManager/Install/Custom/c0

1 Install all disks as new disks. (discards data on disks!) 2 Install one disk at a time.3 Leave these disks alone.? Display help about menu ?? Display help about the menuing system q Exit from menus


Caution Using the option for initializing all disks on the controller (option 1) can result

in loss of data. When all disks on this controller are reinitialized, all data on

each disk is destroyed and the disk becomes available as free space for

allocating new volumes or mirrors of existing volumes.

If you install all disks as new disks, the following message is displayed:



Volume Manager Custom InstallationMenu: VolumeManager/Install/Custom/c0/Init

Installation options for disk c0t12d0Menu: VolumeManager/Install/Custom/c0/c0t12d0

1 Install as a new disk. (discards data on disk!) 2 Leave this disk alone.

? Display help about menu ?? Display help about the menuing system q Exit from menus


Are you sure (destroys data on c0t12d0) [y,n,q,?] (default: n)

Installation options for disk c0t13d0

Menu: VolumeManager/Install/Custom/c0/c0t13d0

1 Install as a new disk. (discards data on disk!) 2 Leave this disk alone.

? Display help about menu ?? Display help about the menuing system q Exit from menusSelect an operation to perform:1


Note If you enter y, vxinstall automatically assigns and lists default disk names for

each disk. If you enter n, vxinstall prompts for a disk name for each disk on the

controller. For each disk, respond with the desired disk name and press Return.

When all of the disks on the current controller have been named, press Return to

move on to the next controller.

The c0t12d0 disk will be given disk name disk01 The c0t13d0 disk will be given disk name disk02 The c0t14d0 disk will be given disk name disk03 The c0t15d0 disk will be given disk name disk04






c1t0d0 c1t10d0 c1t11d0 c1t12d0 c1t13d0 c1t14d0 c1t15d0 c1t1d0 c1t2d0 c1t3d0 c1t4d0 c1t5d0 c1t8d0 c1t9d0



Use default disk names for these disks? [y,n,q,?] (default: y)The c1t0d0 disk will be given disk name disk05 The c1t10d0 disk will be given disk name disk06 The c1t11d0 disk will be given disk name disk07 The c1t12d0 disk will be given disk name disk08 The c1t13d0 disk will be given disk name disk09 The c1t14d0 disk will be given disk name disk10 The c1t15d0 disk will be given disk name disk11 The c1t1d0 disk will be given disk name disk12 The c1t2d0 disk will be given disk name disk13 The c1t3d0 disk will be given disk name disk14 The c1t4d0 disk will be given disk name disk15 The c1t5d0 disk will be given disk name disk16 The c1t8d0 disk will be given disk name disk17 The c1t9d0 disk will be given disk name disk18

Note When all of the disks on the current controller have been named, press Return to

move on to the next controller.






c2t0d0 c2t1d0




The c2t0d0 disk will be given disk name disk19 The c2t1d0 disk will be given disk name disk20





<excluding root disk c6t5d0><excluding LVM disk c6t6d0>


c6t4d0


Volume Manager Custom InstallationMenu: VolumeManager/Install/Custom

The following is a summary of your choices.

c0t12d0 New Disk c0t13d0 New Disk c0t14d0 New Disk c0t15d0 New Disk c1t0d0 New Disk c1t10d0 New Disk c1t11d0 New Disk c1t12d0 New Disk c1t13d0 New Disk c1t14d0 New Disk c1t15d0 New Disk c1t1d0 New Disk c1t2d0 New Disk c1t3d0 New Disk c1t4d0 New Disk c1t5d0 New Disk c1t8d0 New Disk c1t9d0 New Disk c2t0d0 New Disk c6t4d0 New Disk

Is this correct [y,n,q,?] (default: y)



Note This is your last chance to review and alter your choices for the disks to be placed

under Volume Manager control. If you enter y, vxinstall initializes and destroys

any existing data on all disks listed with New Disk . If you enter n, vxinstallprompts for the name of a disk to be removed from the list and excluded from

Volume Manager control. To remove a disk from the list, enter the name of the disk

to be removed from the list and press Return. Repeat for each disk to be removed

and then press Return once more. The vxinstall option now displays an updated

summary that excludes the disks chosen for removal. If you are satisfied with the

summary, enter y.

y

The Volume Manager is now reconfiguring (partition phase)...

Volume Manager: Initializing c0t12d0 as a new disk. Volume Manager: Initializing c0t13d0 as a new disk. Volume Manager: Initializing c0t14d0 as a new disk. Volume Manager: Initializing c0t15d0 as a new disk. Volume Manager: Initializing c1t0d0 as a new disk. Volume Manager: Initializing c1t10d0 as a new disk. Volume Manager: Initializing c1t11d0 as a new disk. Volume Manager: Initializing c1t12d0 as a new disk. Volume Manager: Initializing c1t13d0 as a new disk. Volume Manager: Initializing c1t14d0 as a new disk. Volume Manager: Initializing c1t15d0 as a new disk. Volume Manager: Initializing c1t1d0 as a new disk. Volume Manager: Initializing c1t2d0 as a new disk. Volume Manager: Initializing c1t3d0 as a new disk. Volume Manager: Initializing c1t4d0 as a new disk. Volume Manager: Initializing c1t5d0 as a new disk. Volume Manager: Initializing c1t8d0 as a new disk. Volume Manager: Initializing c1t9d0 as a new disk. Volume Manager: Initializing c2t0d0 as a new disk. Volume Manager: Initializing c6t4d0 as a new disk.

The Volume Manager is now reconfiguring (initialization phase)... Volume Manager: Adding disk01 (c0t12d0) as a new disk.

The Volume Daemon has been enabled for transactions.

volume Manager: Adding disk02 (c0t13d0) as a new disk. Volume Manager: Adding disk03 (c0t14d0) as a new disk. Volume Manager: Adding disk04 (c0t15d0) as a new disk. Volume Manager: Adding disk05 (c1t0d0) as a new disk. Volume Manager: Adding disk06 (c1t10d0) as a new disk. Volume Manager: Adding disk07 (c1t11d0) as a new disk.



Volume Manager: Adding disk08 (c1t12d0) as a new disk. Volume Manager: Adding disk09 (c1t13d0) as a new disk. Volume Manager: Adding disk10 (c1t14d0) as a new disk. Volume Manager: Adding disk11 (c1t15d0) as a new disk. Volume Manager: Adding disk12 (c1t1d0) as a new disk. Volume Manager: Adding disk13 (c1t2d0) as a new disk. Volume Manager: Adding disk14 (c1t3d0) as a new disk. Volume Manager: Adding disk15 (c1t4d0) as a new disk. Volume Manager: Adding disk16 (c1t5d0) as a new disk. Volume Manager: Adding disk17 (c1t8d0) as a new disk. Volume Manager: Adding disk18 (c1t9d0) as a new disk. Volume Manager: Adding disk19 (c2t0d0) as a new disk. Volume Manager: Adding disk20 (c6t4d0) as a new disk. Starting the relocation daemon, vxrelocd

Installation is complete.

Volume Manager Processes

After the Volume Manager is successfully installed, confirm that key Volume Manager

processes are running using the following command:

# ps -ef | grep vx

This command displays output similar to the following:

root 8 0 0 Apr 19 ? 412:53 vxiodroot 20 0 0 Apr 19 ? 0:00 vxfsdroot 324 316 0 Apr 19 ? 0:00 vxnotify -f -w 15root 316 1 0 Apr 19 ? 0:00 vxrelocd -/etc/vx/bin/vxrelocdroot 253 1 0 Apr 19 ? 0:00 vxconfigdroot 4033 3997 1 14:40:50 pts/0 0:00 grep vx


Setting Up and Starting the Storage Administrator

Setting Up and Starting the Storage AdministratorThis section describes how to install and set up the Volume Manager Storage

Administrator. The Storage Administrator server must be installed and run on a UNIX

(HP-UX) machine running the Volume Manager. The Storage Administrator client can be

installed and run on any machine that supports the Java 1.1 Runtime Environment.

The minimum system recommendation for the UNIX (HP-UX) Storage Administrator

client is a Hewlett-Packard D-class machine with 64M memory.

Note Before installing and running the Storage Administrator, you must install the

Volume Manager and run vxinstall to initialize the Volume Manager.

Storage Administrator Installation Overview

Set up and start the Storage Administrator as follows:

1. Install the Volume Manager Storage Administrator server and client on the machine

to be administered. This must be a UNIX (HP-UX) machine. See “Installing the

Storage Administrator Server and/or Client (UNIX)” on page 29.

2. If users other than root need to access the Storage Administrator, set up security and

specify which users can run the Volume Manager Storage Administrator. See

“Customizing Security (Optional)” on page 30.

3. To run the Storage Administrator client from a machine other than the machine to be

administered, install the Storage Administrator client on the machine where the client

will run. See “Installing the Storage Administrator Server and/or Client (UNIX)” on

page 29.

4. Start the Storage Administrator server on the machine to be administered. See

“Starting the Storage Administrator Server” on page 31.

5. Start the Storage Administrator client. See “Starting the Storage Administrator Client”

on page 32.



Installing the Storage Administrator Server and/or Client (UNIX)

Install the Storage Administrator server and client on a UNIX (HP-UX) machine as

follows:

1. Log in as root .

2. Install the Storage Administrator package as described in “Loading the Software from

CD-ROM” on page 8.

The Storage Administrator client can be installed with or without the Storage

Administrator server. To install the Storage Administrator server, answer y (es) at the

appropriate prompt. The Storage Administrator package also contains an optional

Web server package. At the appropriate prompt, indicate whether or not to install the

Web package.

The Storage Administrator package contains the following directories:

3. Go to the directory where Storage Administrator is installed (/opt/VRTSvmsa , by

default).

4. Set the VMSAHOME environment variable, as follows:

# export VMSAHOME=Storage_Administrator_directory

where Storage_Administrator_directory is the directory where the Storage

Administrator is installed.

Directory Contents

jre/ Java Runtime Environment (JRE)

bin/ vmsa_server – Storage Administrator server startup script

vmsa – Storage Administrator startup script

vmsa/ java/vmsa.jar – Storage Administrator class archive

java/images / – Storage Administrator image .gif files

java/help/ – Storage Administrator help files

server/ – Storage Administrator server libraries and properties

index.html – Storage Administrator applet HTML page

man/ Volume Manager Storage Administrator manual pages



5. Update the PATH environment variable to include the directory containing the

Storage Administrator startup scripts:

# export PATH=$PATH:$VMSAHOME/bin

Customizing Security (Optional)

The Volume Manager Storage Administrator can only be run by users with appropriate

privileges. By default, only root can run the Storage Administrator.

After you install the Storage Administrator, you can specify which users will have access

to the Storage Administrator. To set up a list of users with permission to use the Storage

Administrator, add a group named vrtsadm to the group file (/etc/group) or NIS

(Network Information Name Service) group table on the machine to be administered. The

vrtsadm group must include the user names of any users (including root) who will have

access to the Storage Administrator. For example:

# vrtsadm::999:root,joe,bill

If the vrtsadm group does not exist, only root has access to the Storage Administrator. If

vrtsadm exists, root must be included in vrtsadm in order for root to access the

Volume Manager Storage Administrator.

Changing the Group Name (Optional)

vrtsadm is the default VERITAS group name. However, you can change vrtsadm to

another name by setting the vrts.server.adminGroup property to another value. You

can reset the VERITAS group name by adding the following to the java command at the

end of the /opt/VRTSvmsa/bin/vmsa_server file:

# -Dvrts.server.adminGroup= new_groupname

Monitoring Access to the Volume Manager Storage Administrator

Once you have set up security for the Volume Manager Storage Administrator, you can

monitor access to the Storage Administrator by reviewing the contents of the access log

file. By default, the access log file is /var/opt/vmsa/logs/access . This file contains

entries similar to the following:

Fri Jan 23 10:22:17 PST 1998: user xyz login succeededFri Jan 23 10:59:52 PST 1998: user xyz login failed with error "Userpassword invalid"

Entries for failed access can be logged multiple times. This is due to a security

requirement and is not an error.



Starting the Storage Administrator Server

To use the Volume Manager Storage Administrator, the Storage Administrator server

must be running on the HP-UX machine to be administered. Once started, the Storage

Administrator server must run continuously and must not be stopped. Only one instance

of the Storage Administrator server can be running at a time.

Start the Volume Manager Storage Administrator server manually as follows:

1. Log in as root .

2. Go to the directory where the Storage Administrator is installed, using the following

command:

# cd $VMSAHOME/bin

3. Start the server, using the following command:

# ./vmsa_server &

A file named server.log is created in the /var/opt/vmsa/logs directory. When the

server starts successfully, this file is populated with the following information:

rebound //host:2410/vrts.remote.vrtsServer

Confirm that the Volume Manager Storage Administrator is running, using the following

command:

# vmsa_server -q

To stop the Volume Manager Storage Administrator server, use the following command:

# vmsa_server -k

Note Once the Storage Administrator is installed, the Storage Administrator server starts

up automatically at system startup.

The VMSA server has an auto-start mode that starts the server on an as-needed basis. In

auto-start mode, the VMSA server automatically starts whenever a VMSA client tries to

connect to the server and the server is not already running. If no VMSA clients are

connected for a certain amount of time (15 minutes, by default), the server automatically

terminates and restarts at the next client connection.

To start the server in auto-start mode, type:

autostart on

To confirm that auto-start mode is enabled, run the following:

netstat -a | grep vmsa

The output should show that a VMSA service has a LISTEN state:



*.vmsa *.* 0 0 0 0 LISTEN

Auto-start mode remains in effect across system reboots. To disable auto-start mode, type:

autostart off

For more information about auto-start mode, refer to the autostart (1M) manual page.

Starting the Storage Administrator Client

Note Only users with appropriate privileges can run the Volume Manager Storage

Administrator. For information on Storage Administrator security and access

permissions, refer to “Customizing Security (Optional)” on page 30.

The Volume Manager Storage Administrator can administer the local machine or a remote

machine. However, Volume Manager 2.5 (or higher) and the Storage Administrator server

must be installed on the machine to be administered. The Volume Manager daemon

(vxconfigd ) and the Storage Administrator server must be running on the machine to be

administered.

After installing the Volume Manager and Storage Administrator and starting the server,

run the Storage Administrator as follows:

◆ For the local UNIX machine, use the following command:

# vmsa

◆ For a remote UNIX machine, use the following command:

# vmsa remote_machine_name

Running the Storage Administrator in Read-Only Mode

The default mode for the Storage Administrator is full operational mode. However, the

Storage Administrator server can be configured in read-only mode for monitoring or

browsing purposes. Read-only mode allows the administrator to view objects on the

system through the Storage Administrator, but prevents administrative actions from

taking effect. This mode is enabled through the properties file

(/opt/VRTSvmsa/vmsa/properties ).

To start the Storage Administrator server in read-only mode, add the following command

to the properties file:

# vrts.server.readonly=true

To restore the Storage Administrator server to full operational mode, use the following

command:

# vrts.server.readonly=false



Note Stop and restart the server to enable these changes to take effect.


Enabling Cluster Support in Volume Manager (Optional)

Enabling Cluster Support in Volume Manager (Optional)

Note Cluster support is not supported in release 3.1 Beta. This section will be supported

in a future release.

This Volume Manager release includes an optional cluster feature that enables VxVM to be

used in a cluster environment. The cluster functionality in the Volume Manager allows

multiple hosts to simultaneously access and manage a set of disks under Volume Manager

control. A cluster is a set of hosts sharing a set of disks; each host is referred to as a node in

the cluster.

Enable the cluster functionality in the Volume Manager as follows:

1. Obtain a license for the Volume Manager cluster feature from your Customer Support

channel.

2. Install the software packages onto each system (node) to be included in the cluster as

described in “Loading the Software from CD-ROM” on page 8.

3. Initialize VxVM using the vxinstall procedure as described in “Initializing the

Volume Manager” on page 12.

4. Set up and start the Storage Administrator as described in “Setting Up and Starting

the Storage Administrator” on page 28.

5. Configure shared disks as described in “Configuring Shared Disks” on page 34.

Configuring Shared Disks

This section describes how to configure shared disks. When installing VxVM for the first

time or adding disks to an existing cluster, you must configure new shared disks. When

upgrading VxVM, you must verify that your shared disks still exist.

Shared disks are configured from one node only. Since the Volume Manager software is

unable to determine whether or not a disk is shared, you must specify which disks are

shared.

When configuring disks, ensure that no one else is accessing shared disks from another

node. Start the cluster on the node where the configuration is performed in order to

prevent disk accesses from other nodes. Quorum control reserves the disks for the single

node.


Upgrading to VxVM and Storage Administrator to Release 3.1

Upgrading to VxVM and Storage Administrator to Release 3.1If you are running an earlier release of the Volume Manager, upgrade to VxVM Release

3.1 with the procedure that follows. This section also contains information on upgrading

the Storage Administrator.

The upgrade procedure allows you to retain your existing VxVM configuration. After

upgrading, you can resume using VxVM as before, without running the vxinstallprocedure.

Note Importing a 3.0 Volume Manager disk group does not automatically upgrade the

disk group version to the VxVM 3.1 level. Each disk group must be manually

upgraded following a VxVM upgrade. See the chapter on disk tasks in the VERITASAdministrator’s Guide for information on upgrading a disk group.

Upgrading VxVM and Storage Administrator

Upgrade VxVM as follows:

1. Save the current configuration into a file that is not on the VxVM server being

upgraded using the following command:

# vxprint -mh > /file1

2. Unmount all file systems mounted on VxVM volumes using the following command:

# umount all VxVm file systems

3. Stop the Volume Manager using the following command:

# vxdctl stop

4. Remove VxVM 3.0 only or VxVM 3.0 and Storage Administrator using one of the

following commands:

◆ VxVM 3.0 only:

# swremove -x autoreboot=true VRTSvxvm

◆ VxVM 3.0 and Storage Administrator:

# swremove -x autoreboot=true VRTSvxvm VRTSvmsa

5. After the system reboots, insert the CD-ROM and enter the following command, if

necessary:

# mkdir /cdrom


Upgrading to VxVM and Storage Administrator to Release 3.1

6. Mount the VxVM 3.1 CD-ROM using the following command:

# mount -o ro /dev/c xt ydz /cdrom (where x, y, and z are specific toyour system)

7. Install VxVM 3.1 as described in “Installing VERITAS Volume Manager” on page 9,

but do not initialize Volume Manager.

Caution Do not run VXINSTALL after the system reboots.

8. When the system comes up, bring the system to single-user mode using the following

command:

# exec init S

9. When prompted, enter the password and press Return to continue.

10. Remove installation files that were created when you loaded Volume Manager but are

no longer needed using the following command:

# rm -rf /etc/vx/reconfig.d/state.d/install-db

11. After removing the installation files, start Volume Manager I/O daemons using the

following command:

# vxiod set 10

12. Start the Volume Manager configuration daemon, vxconfigd , in disabled mode

using the following command:

# vxconfigd -m disable

13. Initialize vxconfigd using the following command:

# vxdctl init

14. Initialize the DMP subsystem using the following command:

# vxdctl initdmp

15. Enable vxconfigd using the following command:

# vxdctl enable

16. Compare file1 and file2 to ensure that all of the pre-existing volumes have been found

using the following command:

# vxprint -mh > /file2


Checking Volume Manager Processes

17. Once all of the pre-existing volumes are located, upgrade each disk group using the

following command:

# vxdg upgrade

18. When the upgrade is complete and there are no error messages, bring the system up

to multi-user mode using the following command:

# exec init 3

Checking Volume Manager ProcessesAfter the Volume Manager is successfully installed and you have rebooted the system, use

the following command to confirm that key Volume Manager processes (vxconfigd ,

vxnotify , and vxrelocd ) are running:

# ps -ef | grep vx

This command displays output similar to the following:

root 19 0 0 09:09:51 ? 0:00 vxfsdroot 45 1 0 09:10:25 ? 0:01 vxconfigd -m bootroot 52 0 0 09:10:37 ? 0:00 vxiodroot 325 1 0 09:14:08 ? 0:00 vxrelocd -/etc/vx/bin/vxrelocd rootroot 337 325 0 09:14:09 ? 0:00 vxnotify -f -w 15root 1723 1700 1 09:53:39 pts/1 0:00 grep vx

Note If you have disabled Hot-Relocation, only the vxconfigd process is running.


Deinstalling Volume Manager

Deinstalling Volume ManagerTo deinstall Volume Manager, you will need to move all the VxVM volumes to LVM disks.

This can be done using one of the following three methods:

◆ Back up the system onto tape and recover from it.

◆ Back up each file system individually, create new file systems on LVM logical

volumes, and recover all volumes.

◆ Move volumes incrementally (“evacuate”) onto logical volumes. Evacuation moves

subdisks from the source disks to target disks. The evacuated disks provide the initial

free disk space for volumes to be moved to LVM volumes. Use the following steps to

do this:

a. Evacuate as many disks as possible using one of the following:

◆ vxdiskadmNote: If you use vxdiskadm, choose option “Remove a disk” and follow

through the prompted steps.

◆ VMSA, or

◆ the vxevac script.

b. Remove the evacuated disks from Volume Manager control using the following

commands:

# vxdg rmdisk diskname# vxdisk rm devname

c. Decide which volume to move first. If the volume to be moved is mounted,

unmount it. If the volume is being used as a raw partition for database

applications, ensure that the application is not updating the volume and that data

on the volume is synced.

d. Create an LVM logical volume equal to the same size as the volume on the free

disk space. If there is not enough free space for the logical volume, add a new disk

to the system at least for the first volume to be removed. Subsequent volumes can

use the free space generated by the removal of the first volume.

e. Copy the data on the volume onto the newly created LVM logical volume using

the following command:

# dd if=/dev/vx/dsk/lhome of=/dev/vgvol/lhome

where vgvol is a newly created LVM volume group and lhome is a new logical

volume.



f. Replace the entry for that volume, if it is present in /etc/fstab , with an entry

for the newly created LVM logical volume.

g. Mount the logical volume if the corresponding volume was previously mounted.

h. Remove the volume from Volume Manager control using the following

command:

# vxedit -rf rm volume_name

i. Remove any free disks (without subdisk definitions) by removing volumes from

Volume Manager control. To check if subdisks remain on a disk, use the following

command:

# vxprint -F “%sd num” diskname

If the output is other than 0, some subdisks remain on this disk and must be

removed. If the output is 0, remove the disk from Volume Manager control using

the following commands:

# vxdg rmdisk diskname# vxdisk rm devname

j. Copy the data in the next volume to be removed to the newly created free space.

k. Reboot the system after all volumes have been converted successfully. Verify that

no open volumes remain after the system reboot using the following command:

# vxprint -Aht -e v_open

If any volumes remain open, repeat the steps listed above.

Preparation

If the Volume Manager must be removed, complete the following preparations before the

deinstallation:

◆ Modify all file systems and other applications using volume devices to use the

underlying disks or logical volumes.

◆ Make file systems created since the Volume Manager was installed accessible through

a disk or LVM logical volume.

◆ Move all data from volumes created from multiple regions of storage, including

striped or spanned volumes, onto a single disk or appropriate LVM logical volume.

◆ Remove all but one copy of file systems and other databases.

◆ Remove all but one plex from volumes that contain multiple plexes (mirrors).



To display a list of all volumes, use the command:

# vxprint -Ath



To remove a plex, use the command:

# vxplex -o rm dis plex_name

◆ If a remaining plex contains multiple subdisks, consolidate the subdisks into a single

subdisk using the commands:

# vxassist mirror volume_name layout=contig# vxplex -o rm dis plex_name

Note Sufficient space on another disk is required for this operation to complete.

◆ Modify /etc/fstab to mount all file systems using a partition or logical volume

instead of a VxVM volume. Update /etc/fstab for volumes that are not on

rootdg .

Shutting Down the Volume Manager

To shut down the Volume Manager, use the following commands:

# vxdctl stop# vxiod -f set 0

Removing the Volume Manager Package

To remove one or more of the installed Volume Manager packages, use the following

command:

# swremove -x autoreboot=true VRTSvxvm

Errors that occur during the software removal process are due to the following:

◆ the system contains open volumes

◆ the root disk is under Volume Manager control

For more information, select the Logfile button in the user interface to check the log file

/var/adm/sw/swagent.log .



Removing the VM Storage Administrator Package

To remove the Volume Manager Storage Administrator package by itself, use the

following command:

# swremove VRTSvxvm

To remove Storage Administrator package when removing the Volume Manager package,

use the following command:

# swremove -x autoreboot=true VRTSvxvm VRTSvmsa
