VERITAS Storage Foundation™ 4.

0
Installation Guide
Linux

N12947H August 2004

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. VERITAS Legal Notice Copyright © 2003 - 2004 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS
Logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of
VERITAS Software Corporation. The VERITAS logo, Reg. U.S. Pat. & Tm. Off. Other product names
and/or slogans mentioned herein may be trademarks or registered trademarks of their respective
companies.
VERITAS Software Corporation
350 Ellis Street
Mountain View, CA 94043
USA
Phone 650–527–8000 Fax 650–527–2908
www.veritas.com
Third-Party Copyrights
Data Encryption Standard (DES) Copyright
Copyright © 1990 Dennis Ferguson. All rights reserved. Commercial use is permitted only if products that are derived from or include this software are made available for purchase and/or use in Canada. Otherwise, redistribution and use in source and binary forms are permitted. Copyright 1985, 1986, 1987, 1988, 1990 by the Massachusetts Institute of Technology. All rights reserved. Export of this software from the United States of America may require a specific license from the United States Government. It is the responsibility of any person or organization contemplating export to obtain such a license before exporting. WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. M.I.T. makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty.

ii

VERITAS Storage Foundation Installation Guide

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
How This Guide Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Unique Message Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
VERITAS Storage Foundation Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Comment on the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Chapter 1. Preinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Preinstallation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Supported Linux Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Required Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Required Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
System Disk Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Prerequisites for Remote and Cluster Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Licensing Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Using the VERITAS vLicense Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Faxing the License Key Request Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
VERITAS Licensing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Accessing Storage Foundation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Accessing Manual Pages and Documentation Directories . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 2. Installing VERITAS Storage Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Storage Foundation Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

iii

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Installing the Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Adding Unsupported Disk Arrays as JBODS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Configuring Storage Foundation on a Cluster . . . . . . . . 32 RAID-5 Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Checking Volume Manager Processes . . . . . . 25 Chapter 3. . . . . . . . . . . . . 30 Mirroring Guidelines . . . . . . . . . . . . . . . . . . . . . . . 31 Dirty Region Logging (DRL) Guidelines . . . . . . . . 33 Hot-Relocation Guidelines . . 20 Checking Cluster Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 The VERITAS Enterprise Administrator (VEA) . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Configuring Cluster Support in VERITAS Volume Manager (Optional) . . . . . . . . . . . . . . . 23 Installing the VEA Client on a Microsoft Windows System . . . . . 27 Setup Tasks After Installation . . . . . . . 31 Striping Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Loading and Unloading the File System Module . . 36 iv VERITAS Storage Foundation Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Controlling VxVM’s View of Multipathed Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Guidelines for Configuring Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 GAB Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GAB and Cluster Operation . . Configuring VERITAS Storage Foundation After Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 20 LLT (Low Latency Transport) . . . . . . . 30 Guidelines for Protecting Your System and Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Adding Foreign Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Completing the Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Disabling Hot-Relocation on VxVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Adding Disks to Disk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Using VEA to Administer Remote Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Enabling Intelligent Storage Provisioning (ISP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 GAB Files. . . . . . . . . . 34 Accessing Volume Devices . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Supported Operating Systems and Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Enabling or Disabling Enclosure-Based Naming . . . . . . . . . . . . . . . . 56 Contents v . . . . .0 . . . . . . . . . . 38 Configuring VxFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Shared Disk Groups . . . . . . . . . . . . 44 Upgrading Linux Kernel Errata with Storage Foundation 4. . . 37 Reconfiguration Tasks . .0 Already Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 When to Use vxupgrade . . . . . . . . . . . . . . . 51 Removing Rootability . . . . . . . . . . . . . . . . . . 36 Converting Existing VERITAS Volume Manager Disk Groups to Shared Disk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Removing the VEA Client from a Microsoft Windows System . . . . . . . . . . . . . . . . . . . . . . . 53 Moving Volumes onto Disk Partitions Using VxVM . 53 Moving Volumes To Disk Partitions . . . . 38 Changing the Name of the Default Disk Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Upgrading the VEA Client on a Microsoft Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Chapter 4. . . . . . . . 49 Upgrading VxVM Disk Group Versions . . . . . . . . . 48 Requirements for Upgrading to Disk Layout Version 6 . . . . . . 40 Upgrading to Storage Foundation 4. . . . . . . . . . . 41 Upgrading Storage Foundation After Reinstalling Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 When to Upgrade Disk Layout Versions . . . . . . . . . . . . Uninstalling VERITAS Storage Foundation . . . . . . . .39 Using Existing Licenses . . . . . . . . . . . . . . 50 Chapter 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Upgrading VxFS Disk Layout Versions . Upgrading VERITAS Storage Foundation and Linux . 48 When to Use vxfsconvert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Removing Storage Foundation Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Removing VERITAS File Systems . . . 55 Uninstalling VERITAS Infrastructure Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vi VERITAS Storage Foundation Installation Guide .

Storage Foundation is comprised of the VERITAS File System (VxFS). VERITAS Volume Manager (VxVM). and the VERITAS Enterprise Administrator (VEA) graphical user interface.Preface This document provides information on installing and initializing VERITAS Storage Foundation™. This guide assumes that you have a: ◆ ◆ ◆ Working knowledge of the Linux operating system Basic understanding of Linux system administration Basic understanding of Linux file systems and volume management vii .

“Preinstallation” on page 1 Chapter 2. “Upgrading VERITAS Storage Foundation and Linux” on page 39 Chapter 5. Descriptions of Storage Foundation commands. their options. upgrade or remove the Storage Foundation packages. and usage are provide in the VxVM and VxFS online manual pages. “Installing VERITAS Storage Foundation” on page 7 Chapter 3.How This Guide Is Organized How This Guide Is Organized This guide describes how to install. This guide is organized with the following chapters: ◆ ◆ ◆ ◆ ◆ Chapter 1. See the VERITAS Storage Foundation Release Notes for more information related to product installation. “Configuring VERITAS Storage Foundation After Installation” on page 27 Chapter 4. “Uninstalling VERITAS Storage Foundation” on page 51 viii VERITAS Storage Foundation Installation Guide . Note Most VxVM and VxFS commands require superuser or other appropriate privileges.

visit https://my. be sure to provide the unique message identifier preceding the message. product alerts. For license information. software updates and sales contacts.veritas.” For example: VCS NOTICE V-16-1-10075 Invalid host name. VERITAS Storage Foundation Documentation The following documents provide information related to Storage Foundation: ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ VERITAS FlashSnap Point-In-Time Copy Solutions Administrator’s Guide VERITAS Storage Foundation Cross-Platform Data Sharing Administrator’s Guide VERITAS Storage Foundation Release Notes VERITAS File System Administrator’s Guide VERITAS Volume Manager Administrator’s Guide VERITAS Volume Manager Hardware Notes VERITAS Volume Manager Troubleshooting Guide VERITAS Volume Manager Intelligent Storage Provisioning Administrator’s Guide VERITAS Volume Manager User’s Guide — VERITAS Enterprise Administrator VERITAS Volume Manager and VERITAS File System online manual pages Preface ix . Use the Knowledge Base Search feature to access additional product information.com/productcenter/ContactVeritas. The identifier is an alpha-numeric string that denotes the type of message. and our customer email notification service. visit http://webstore. VERITAS Technical Services uses message identifiers to locate TechNotes and other information to assist in troubleshooting your case. Error messages begin with the letter “V. For information on purchasing product documentation.Getting Help Getting Help For technical assistance.com and select phone or email support.veritas.com. hardware compatibility lists.veritas. This site also provides access to resources such as TechNotes.jsp. including current and past releases of VERITAS documentation. Unique Message Identifiers When contacting VERITAS Technical Services. either by telephone or by visiting the Technical Services website. software downloads. visit http://support.

or tell us what you would find useful in future versions of our manuals and online help.Comment on the Documentation Comment on the Documentation Let us know what you like and dislike about the documentation. Were you able to find the information you needed quickly? Was the information clearly presented? Report errors and omissions. See “Getting Help” on page ix for how to contact Technical Support about software issues. We appreciate your feedback. Please include the following information with your comment: ◆ ◆ ◆ ◆ The title and product version of the manual you are commenting on The topic (if relevant) you are commenting on Your comment Your name Email your comment to the following address: ◆ foundation_docs@veritas.com Use this email address only to comment on product documentation. x VERITAS Storage Foundation Installation Guide .

functions. In a command synopsis. Superuser prompt (all shells). a vertical bar separates mutually exclusive arguments. Indicates user input. and parameters. etc. Preface xi . Also depicts GUI commands. directory and file names. # cd pubs/vx/4. Example Read tuneables from the /etc/vx/tunefstab file. output.0 monospace (bold) italic Identifies book titles. list boxes. such as fields. emphasized text.Conventions Conventions Convention monospace Usage Used for path names. Depicts GUI objects. Windows user prompt. # -modify resource ls [ -a ] bold # [] | mount [ suid | nosuid ] [] ls [ -a ] C:\> Key+Key C:\> -modify resource Press Ctrl+S to save your changes. See the User’s Guide for details. In a command synopsis. On Windows. this indicates pressing and holding the first key while pressing the second. brackets indicates an optional argument. menu selections. See the ls(1) manual page for more information. Enter your password in the Password field. new terms. Press Return. In a command synopsis. commands. and variables replaced with a name or value. The variable system_name indicates the system on which to enter the command. brackets indicates an optional argument.

Conventions xii VERITAS Storage Foundation Installation Guide .

Preinstallation The following topics are covered in this chapter: ◆ ◆ ◆ ◆ ◆ ◆ 1 Preinstallation Instructions Supported Linux Operating Systems Prerequisites for Remote and Cluster Installation Licensing Procedures Accessing Storage Foundation Commands Accessing Manual Pages and Documentation Directories Review the information in these sections and make appropriate changes before you install or upgrade VERITAS Storage Foundation. 1 .

The tools are not required for operation of any VERITAS product. VERITAS provides these tools to analyze systems if you suspect that there are performance problems. The versions on your system may differ from these. and they may adversely impact system performance if not used correctly. The versions of these packages in Red Hat Enterprise Linux 3 Update 2 are compat-gcc-c++-7.128 and compat-libstdc++-7. You can determine whether this package has been installed by using the following command: # rpm -q patch ◆ ◆ The Storage Foundation software requires that the compat-gcc-c++ and compat-libstdc++ packages be present on the system.pdf located on the VERITAS software disc under the storage_foundation/release_notes directory.0 for Linux Disc 1. The VERITAS Storage Foundation software is on VERITAS Storage Solutions 4.3-2. The VRTSspt package provides a group of tools for troubleshooting a system and collecting information on its configuration. sf_notes. obtain a license key as described in “Licensing Procedures” on page 4. VERITAS recommends that you copy them from the software disc to the /opt/VRTS/docs directory so that they are available for future reference. Because product release notes and installation guides are not installed by any packages.rpm (or later) is available in the rhel3_i386/RPMS directory on the Red Hat CD.5. and should be used only under the direction of a VERITAS Technical Support Engineer. The patch package. The tools can gather VERITAS File System and VERITAS Volume Manager metadata information and establish various benchmarks to measure file system and volume manager performance.i386. ◆ In the VERITAS Storage Foundation Release Notes. Note There are two software discs in the product distribution from VERITAS. You can determine whether these libraries have been installed by using the following command: # rpm -qa | egrep compat ◆ To initialize Storage Foundation features.3-2. Ensure that the patch RPM is present on a Red Hat Enterprise Linux System before installing the VERITAS Storage Foundation software. patch-2.96.96. review the information on VRTSexplorer and installing the VRTSspt package.128. VERITAS Storage Foundation Installation Guide 2 .Preinstallation Instructions Preinstallation Instructions Review the following items and make any appropriate changes before you install or upgrade the VERITAS Storage Foundation software: ◆ Review the VERITAS Storage Foundation Release Notes.4-10.

Supported Linux Operating Systems Supported Linux Operating Systems VERITAS 4. Preinstallation 3 .ELhugemem and errata Note This release does not support Intel IA64 or AMD architectures.4.ELsmp and errata 2. Storage Foundation Standard Standard or Enterprise HA or Enterprise HA Minimum Space Required (Without Optional Packages) Maximum Space Required (Including All Packages) 145MB 300MB 265MB 455MB Chapter 1. The approximate minimum and maximum space required in the root file system for each product is shown in the table below.21-15. see the following TechNote: http://support. For information about the latest supported Red Hat erratas and updates.21-15.com/docs/256426 Required Disk Space Note It is recommended that you run the preinstallation check (available in the installer) to verify that there is sufficient disk space on all systems.4.21-15.0 products operate on the following Red Hat operating systems and kernels: Operating System Kernel Red Hat Enterprise Linux 3 Update 2 (i686) 2. Storage Foundation QuickStart.4.veritas.EL and errata 2. The VERITAS installation utilities verify that there is sufficient disk space available before installing the software.

See “Configuring SSH or RSH Before Installing VERITAS Products” in the Getting Started Guide for more information. Fax the License Key Request Form included in the license kit. You must have this form to obtain a software license key for your VERITAS product. run the fdisk -l command and review the output to verify that all disks installed on the system are visible to the operating system and functioning correctly. Using the VERITAS vLicense Website The License Key Request Form is a one-page insert included in the product license kit. or have misplaced. The node from which the installation utility is run must have permissions to run rsh (remote shell) or ssh (secure shell) utilities as root on all cluster nodes or remote systems. email license@veritas. Correct any problems before you install the Storage Foundation software. Note If you did not receive. Licensing Procedures To obtain a valid software license key. Remote shell utilities on Linux Advanced Server are disabled by default. Save the form for future reference. System Disk Check Before installing VERITAS Storage Foundation. or to install and configure a cluster. The form lists the following information required to establish a user account on vLicense and generate a license key: ◆ ◆ Customer number Order number 4 VERITAS Storage Foundation Installation Guide . Prerequisites for Remote and Cluster Installation Establishing communication between nodes is required to install VERITAS software from a remote system. the form.Prerequisites for Remote and Cluster Installation Required Memory A minimum of 512 MB of memory is recommended.com to obtain a new form. use one of the following methods: ◆ ◆ Access the VERITAS vLicense website (recommended).

use the command: # PATH=/sbin:/usr/sbin:$PATH. you can log in. vxlictest Retrieves features encoded in a license key and describes them. you cannot invoke the VxFS-specific df. Note If you specify /opt/VRTS/bin in your PATH after the path to the standard Linux commands. Faxed orders typically require several business days to process. export PATH Chapter 1. fax the License Key Request Form directly to VERITAS. If not. Preinstallation 5 . Most of the commands used in the installation are in the /sbin or /usr/sbin directory. ncheck. For shells similar to the Bourne Shell (bash. read “Installing VERITAS Storage Foundation” on page 7. you must create an account before logging in. After you receive the license key. There are three commands: vxlicinst Licenses a VERITAS product already installed on a system. You must install VRTSvlic for the licensing process to work. Accessing Storage Foundation Commands Symbolic links to all Storage Foundation command executables are installed in the /opt/VRTS/bin directory. If you already have an account. Add these directories to your PATH environment variable as shown below. After you receive a license key. You can review descriptions and options for these commands in the manual pages installed with the VRTSvlic package. vxlicrep Enables you to view currently installed licenses. VERITAS Licensing Commands The VERITAS licensing commands are provided in the VRTSvlic package. Faxing the License Key Request Form If you do not have web access. read “Installing VERITAS Storage Foundation” on page 7. Add the /opt/VRTS/bin directory to the end of your PATH environment variable to access the commands. or umount commands unless you type the full path name: /opt/VRTS/bin/command.com and follow the instructions. ksh or sh).veritas. Sign and date the form in the appropriate spaces and fax it to the number shown on the form. fsdb.Accessing Storage Foundation Commands ◆ Serial number Use a web browser to access the vLicense website at http://vlicense.

6 VERITAS Storage Foundation Installation Guide . use the command: % setenv PATH /sbin:/usr/sbin:${PATH} Accessing Manual Pages and Documentation Directories Volume Manager manual pages are in the VRTSvmman package. set LC_ALL=C in your shell to ensure that they display correctly. Note If you use the man command to access manual pages. and include the 1m manual page section in the list defined by your MANSECT environment variable. do the following: $ PATH=/usr/sbin:/sbin:/etc/vx/bin:/usr/lib/vxvm/bin: \ /opt/VRTS/bin:$PATH $ export PATH $ MANPATH=$MANPATH:/opt/VRTS/man. Set the path of your MANPATH environment variable to include /opt/VRTS/man. export MANPATH $ MANSECT=$MANSECT:1m. export MANSECT If you are using a shell such as csh or tcsh.Accessing Manual Pages and Documentation Directories For shells similar to the C Shell (csh or tcsh). Manual pages are installed in the /opt/VRTS/man directories. If you are using a shell such as sh or bash. do the following: % setenv PATH /usr/sbin:/sbin:/etc/vx/bin:/usr/lib/vxvm/bin: \ /opt/VRTS/bin:$PATH % setenv MANPATH ${MANPATH}:/opt/VRTS/man % setenv MANSECT ${MANSECT}:1m Installation of the documentation packages copies PDF files into the /opt/VRTS/docs directory. VERITAS File System manual pages are in the VRTSfsman package.

Installing VERITAS Storage Foundation The following topics are covered in this chapter: ◆ ◆ ◆ ◆ ◆ ◆ 2 Storage Foundation Packages Installing the Product The VERITAS Enterprise Administrator (VEA) Disabling Hot-Relocation on VxVM Enabling Intelligent Storage Provisioning (ISP) Loading and Unloading the File System Module Note Only users with superuser privileges can install and initialize Storage Foundation. 7 .

even if you are not installing the VERITAS File System software) VERITAS Enterprise Administrator Service (required for VEA and ISP) VERITAS Enterprise Administrator (required for VEA client) PERL language (required) VERITAS licensing utilities (required) VERITAS Volume Manager online guides (optional) VERITAS Volume Manager manual pages (optional) VERITAS Volume Manager Provider (required for VEA and ISP) VERITAS Volume Manager (required) VERITAS File System (required) VERITAS File System manual pages (optional) VERITAS File System online guides (optional) VERITAS File Placement Policy Manager VERITAS Action Provider VERITAS Task Exec Provider VRTSob VRTSobgui VRTSperl VRTSvlic VRTSvmdoc VRTSvmman VRTSvmpro VRTSvxvm VRTSvxfs VRTSfsman VRTSfsdoc VRTSfppm VRTSap VRTStep 8 VERITAS Storage Foundation Installation Guide .Storage Foundation Packages Storage Foundation Packages The VERITAS software disc contains the following standard Storage Foundation packages: VRTSalloc VRTScpi VRTSddlpr VRTSfspro VERITAS Intelligent Storage Provisioning (ISP) feature (optional) VERITAS Common Platform Installation (CPI) utilities. (required) VERITAS Device Discovery Layer Provider (required) VERITAS File System Provider (required for VEA.

requires VRTSvmpro) VERITAS Volume Replicator Web Console (optional) VRTSvrw Chapter 2.Storage Foundation Packages VRTSvcsvr VRTSvrdoc VRTSvrpro VERITAS Cluster Server Agents for VERITAS Volume Replicator (optional) VERITAS Volume Replicator documentation (optional) VERITAS Volume Replicator Management Services Provider (required for VVR. Installing VERITAS Storage Foundation 9 .

If an installation procedure hangs. You can also install the product using the installsf script located on the VERITAS software disc under the storage_foundation directory. some steps are unnecessary. Move to the rhel3_i386 directory on the CD-ROM: # cd /mnt/cdrom/rhel3_i386 5. VERITAS Storage Foundation Enterprise HA. The back feature of the installation scripts is context-sensitive./installer If you are using the remote shell (RSH) utilities to install on remote systems. 6. Press Return to accept defaults. The Selection Menu appears. 2. The installer also enables you to configure or uninstall the product. Log in as superuser. Mount the CD-ROM on a suitable mount point. The following sample procedure is based on the installation of a Storage Foundation Enterprise HA cluster with two nodes: “sflx1” and “sflx2.Installing the Product Installing the Product The VERITAS product installer is the recommended method to license and install the product. type the following command if you are installing on the local system only. From this directory. At most points during an installation. ▼ To install Storage Foundation 1. and view the product’s description. 3. There is a short delay before the script exits. and these are indicated. or if you are using the secure shell (SSH) utilities to install on remote systems: # . additionally specify the -usersh option: # . Default responses are enclosed by parentheses. so it returns to the beginning of a grouped section of questions. for example. verify preinstallation requirements. use Control–c to stop and exit the program. 10 VERITAS Storage Foundation Installation Guide .” If you are installing on standalone systems only./installer -usersh The sample installation assumes that SSH is being used. for example: # mount -o ro /dev/cdrom /mnt/cdrom 4. Insert the disc containing the VERITAS software into the CD-ROM drive. Enter I at the prompt to install packages. and select the product that is to be installed. you can use type “b” (“back”) to return to a previous section of the installation procedure.

.....4.. Linux 2......................... scp successful Checking OS version on sflx2 .. required space is available Copying VRTSvlic rpm to sflx2 ............................... i686 Checking Machine Type on sflx2 ............................. Installing VERITAS Storage Foundation 11 ..................... Press Enter.. 3AS-7...... Installing VERITAS Infrastructure rpms on sflx1: Checking VRTSvlic rpm ............... Done Installing VRTScpi 4..2 Checking kernel release level on sflx2 .. Done Chapter 2.. The utility begins installing the infrastructure rpms.... Enter the system names separated by spaces on which to install SF: sflx1 sflx2 Checking system communication: Checking OS version on sflx1 ............. When prompted......... not installed Checking VRTScpi rpm ...............02 on sflx2 ........ not installed Checking file system space . i686 Checking Machine Type on sflx1 ................0 on sflx1 ...ELsmp Checking Processor Type on sflx2 .... “sflx1” and “sflx2”) on which the software is to be installed...................15 Verifying communication with sflx2 ..........................02 on sflx1 ...................21-15....................... ping successful Attempting ssh -x with sflx2 ........................ not installed Checking file system space ..............................15 Creating log directory on sflx2 ......................21-15........... not installed Checking VRTScpi rpm ............. press Enter to continue.. ssh -x successful Attempting scp with sflx2 ...... Using /usr/bin/ssh -x and /usr/bin/scp to communicate with remote systems...... Done Logs for installsf are being created in /var/tmp/installsf416173103..............Installing the Product 7.2 Checking kernel release level on sflx1 ............ Linux 2. 3AS-7..................... i686 Checking Redhat Release on sflx2 ... Done Installing VRTSvlic 3...ELsmp Checking Processor Type on sflx1 ............................. Press [Enter] to continue: 8... Initial system check completed successfully.. Done Copying VRTScpi rpm to sflx2 .............. i686 Checking Redhat Release on sflx1 ..................................... Done Installing VERITAS Infrastructure rpms on sflx2: Checking VRTSvlic rpm .............................4........... You are prompted to enter the system names (in the following example................... required space is available Installing VRTSvlic 3......

and enter license keys for each system.... Press [Enter] to continue: 10... VRTSobgui VERITAS Enterprise Administrator VRTSvmman VERITAS Volume Manager Manual Pages VRTSvmdoc VERITAS Volume Manager Documentation VRTSlvmconv VERITAS Linux LVM to VxVM Converter VRTSap VERITAS Action Provider VRTStep VERITAS Task Provider VRTSfsman VERITAS File System Manual Pages VRTSfsdoc VERITAS File System Documentation VRTSvxfen VERITAS I/O Fencing VRTSvcsmn VERITAS Cluster Server Man Pages VRTSvcsApache VERITAS Cluster Server Apache Agent VRTSvcsdc VERITAS Cluster Server Documentation VRTScssim VERITAS Cluster Server Simulator VRTScscm VERITAS Cluster Server Cluster Manager 1) 2) 3) Install all of the optional rpms Install none of the optional rpms View rpm descriptions and select optional rpms 12 VERITAS Storage Foundation Installation Guide ...n.....?] (n) Enter n if you have no further license keys to add for a system... .....q... Checking SF license key on sflx1 .Installing the Product Installing VRTScpi 4...... Press Enter to continue. not licensed Enter a SF license key for sflx1: [?] XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Registering VERITAS Storage Foundation Enterprise HA key on sflx1 Do you want to enter another license key for sflx1? [y.0 on sflx2 ..... You are then prompted to enter the keys for the next system... SF licensing completed successfully... Enter 1 or press Enter to install the standard and all optional rpms... .... Press [Enter] to continue: 9.. Done VERITAS Infrastructure rpms installed successfully.. ... A list of optional rpms is now displayed.. Press Enter to begin license verification.. The following prompt is displayed when you have added licenses to all the systems...

The utility lists the rpms to be installed.. installer will install the following SF rpms: VRTSperl VERITAS Perl 5.?] (1) Note The list may differ depending on the license keys that you entered in step 9.Installing the Product Select the optional rpms to be installed on all systems? [1-3.0 Redistribution VRTSob VERITAS Enterprise Administrator Service VRTSobgui VERITAS Enterprise Administrator VRTSvxvm VERITAS Volume Manager Binaries VRTSvmman VERITAS Volume Manager Manual Pages VRTSvmdoc VERITAS Volume Manager Documentation VRTSvmpro VERITAS Volume Manager Management Services Provider VRTSfspro VERITAS File System Management Services Provider VRTSalloc VERITAS Volume Manager Intelligent Storage Provisioning VRTSddlpr VERITAS Device Discovery Layer Services Provider VRTSlvmconv VERITAS Linux LVM to VxVM Converter VRTSvxfs VERITAS File System VRTSap VERITAS Action Provider VRTStep VERITAS Task Provider VRTSfppm VERITAS File Placement Policy Manager VRTSfsman VERITAS File System Manual Pages VRTSfsdoc VERITAS File System Documentation VRTSllt VERITAS Low Latency Transport VRTSgab VERITAS Group Membership and Atomic Broadcast Press [Enter] to continue: Press Enter to continue listing the rpms..q. .continued: VRTSvxfen VERITAS I/O Fencing VRTSvcs VERITAS Cluster Server VRTSvcsmg VERITAS Cluster Server Message Catalogs VRTSvcsag VERITAS Cluster Server Bundled Agents VRTSvcsmn VERITAS Cluster Server Man Pages VRTSvcsApache VERITAS Cluster Server Apache Agent VRTSvcsdc VERITAS Cluster Server Documentation VRTScspro VERITAS Cluster Server VEA Provider VRTSjre VERITAS Java Runtime Environment Redistribution VRTScssim VERITAS Cluster Server Simulator VRTScscw VERITAS Cluster Server Configuration Wizards VRTSweb VERITAS Java Web Server VRTSvcsw VERITAS Cluster Manager (Web Console) VRTScscm VERITAS Cluster Server Cluster Manager Chapter 2. Installing VERITAS Storage Foundation 13 .8.

If you are installing on a cluster....... proceed to “Configuring Storage Foundation on a Cluster” on page 15 to configure Storage Foundation Enterprise HA.......... Press [Enter] to continue: 12................... Otherwise...... Checking VRTSperl rpm .... Press Enter...... not installed Checking VRTSob rpm ............. Checking system installation requirements: Checking SF installation requirements on sflx1: Checking Checking Checking ..... .... not installed SF installation requirements on sflx2: Checking VRTSperl rpm ......... not installed VRTSobgui rpm ...... The utility begins checking the installation requirements for each of the nodes. .Installing the Product VRTScutil VERITAS Cluster Utilities Press [Enter] to continue: 11............... skip to “Completing the Installation Procedure” on page 17......... not installed Checking VRTSobgui rpm .................... . ............................ not installed VRTSob rpm ................... 14 VERITAS Storage Foundation Installation Guide .... not installed .. Installation requirement checks completed successfully...

?] (y) y Enter the NIC for the second private heartbeat link on sflx1: [b.b.. You are then prompted to enter information about the cluster’s private network. ▼ To configure Storage Foundation on a cluster 1. Are you ready to configure SF? [y.n.b. discovered eth0 eth1 eth2 Enter the NIC for the first private heartbeat link on sflx1: [b.?] eth2 eth2 is currently active as a public NIC on sflx1 Are you sure you want to use eth2 for the second private heartbeat link? [y.?] eth1 eth1 is currently active as a public NIC on sflx1 Are you sure you want to use eth1 for the first private heartbeat link? [y.. As the installation and configuration procedure continues..Installing the Product Configuring Storage Foundation on a Cluster Note The procedure in this section is only relevant if you are installing an HA version of the Storage Foundation software.n. Enter the unique cluster name: [?] tantan Enter the unique Cluster ID number between 0-255: [b.” and the public network connected via “eth0” is not used as a low priority heartbeat link..?] (n) y Chapter 2. Installing VERITAS Storage Foundation 15 .. Sample entries and output are based on the two-node cluster comprising “sflx1” and “sflx2. Press Enter to continue.q.b.. A message is displayed describing the VERITAS Cluster Server (VCS) configuration requirements..q. At the following prompt. 3..” The redundant private network is configured over the network interfaces “eth1” and “eth2... 2.?] (n) y Would you like to configure a second private heartbeat link? [y.n. enter y or press Enter to configure Storage Foundation...q.q] (y) y A message is displayed describing how to configure Storage Foundation using the product installer.?] 199 Discovering NICs on sflx1 . a message displays notifying you that configuring Storage Foundation at this point in the installation procedure is optional.n.

and the minimum security level of messages to be sent to each recipient. 9. 8. enter n to re-enter the information.n. you are prompted to enter details of the public NIC. When prompted to configure this feature. When prompted to add a password for the Administrator. If you enter y.?] (y) y 4. A message displays notifying you of the configuration requirements for SMTP. When prompted to configure this feature. The utility begins to verify the VCS user information. If you enter y. 7. When prompted. If you enter y. When prompted to add a user. The utility begins to verify the cluster information. 6. enter n if you want to decline.n. and the minimum security level of messages to be sent to each console. enter n if you want to decline. When prompted. 10. enter n if you want to decline.q] (y) 5. A message displays notifying you of the configuration requirements for Cluster Manager (the VCS graphical user interface).Installing the Product Do you want to configure an additional low priority heartbeat link? [y. virtual IP address and network mask to be used by Cluster Manager. password and privilege level for each user. you are prompted to enter a user name. you are prompted to enter details of the SMTP server’s host name.n. 11. A message displays notifying you of the information required to add VCS users. you are prompted to enter details of the systems names of the SNMP consoles that are to receive VCS trap messages.q. email addresses of recipients.?] (n) n Are you using the same NICs for private heartbeat links on all systems? [y. If the information displayed is not correct. enter n if you want to decline. you are prompted to change the password. Cluster information verification: Cluster Cluster Private Private Name: tantan ID Number: 199 Heartbeat NICs for sflx1: link1=eth1 link2=eth2 Heartbeat NICs for sflx1: link1=eth1 link2=eth2 Is this information correct? [y.q. A message displays notifying you of the configuration requirements for SNMP. enter y to confirm the information is correct. enter n if you want to decline. If you enter y. Proceed to “Completing the Installation Procedure” on page 17. SNMP daemon port numbers for each console. enter n to re-enter the information. enter y to confirm the information is correct. 16 VERITAS Storage Foundation Installation Guide . If the information displayed is not correct. If you enter y.b. When prompted to configure this feature.b.

.. 4. Press [Enter] to continue: 3. Installing VRTSperl 4.. ..... Press Enter to continue.. Installing VERITAS Storage Foundation 17 ...525 on sflx1 .. you are prompted to choose whether to install on all systems simultaneously.. Chapter 2.Installing the Product Completing the Installation Procedure At this point in the installation and configuration procedure.. Installing VRTSob 3.. Press Enter to continue.2. If you are installing an HA version of the product. The following sample output is for a Storage Foundation Enterprise HA.... As the utility continues the procedure..0 on all systems simultaneously: Copying VRTSperl rpm to sflx2 ..... When prompted to configure this feature.........0 on sflx2 ... a message displays indicating the VCS configuration files are being created and copied.......525 on sflx2. A message displays describing the VxVM enclosure-based naming scheme and showing which nodes are eligible..n.. ▼ To complete installing and configuring Storage Foundation 1.2.q..... ..... .. Enter y or press Enter to accept simultaneous installation....0 on sflx1 .. Storage Foundation Enterprise HA installation compeleted successfully. See the vxdiskadm(1M) manual page and the “Administering Disks” chapter of the VERITAS Volume Manager Administrator’s Guide for more information.?] (y) y Installing Storage Foundation Enterprise HA 4... enter n if you want to decline.. If required.. Installing VRTSperl 4.. you can use the vxdiskadm command or the VERITAS Enterprise Administrator to configure this feature after installation... the utility begins to install the various packages on one node and copy them to any other specified nodes..... Would you like to install Storage Foundation HA on all systems simultaneously? [y. A message displays notifying you of successful installation....... Copying VRTSob rpm to sflx2 . Installing VRTSob 3. Done Done Done Done Done Done 1 2 3 4 5 6 of of of of of of 102 102 102 102 102 102 steps steps steps steps steps steps 2..

........................... Succeeded Done with initial start of VxVM on system sflx1 Begin initial start of VxVM on system sflx2 Disabling enclosure-based naming ................. Starting GAB on sflx2 ......can be started........... System sflx2 is eligible -......... Preparing to start VxVM on target systems.. Such commands require that the user specify a disk group... System sflx1 is eligible -............. Starting Cluster Server on sflx1 .......................... Starting LLT on sflx2 .......... Many Volume Manager commands affect the contents or configuration of a disk group......... 18 VERITAS Storage Foundation Installation Guide .. Starting Cluster Server on sflx2 .... 2 systems Started Started Started Started Started Started RUNNING 7......... A message displays indicating which systems can be started and on the systems that VxVM selects as targets....... This is accomplished by using the -g option of a command or setting the VXVM_DEFAULTDG environment variable...... Done Starting vxconfigd for VxVM ..........................can be started..Installing the Product 5........ Press [Enter] to continue: 6................. Confirming Cluster Server startup ... Starting Cluster Server: Starting LLT on sflx1 ......... a message displays notifying you that Cluster Server is starting........ Starting GAB on sflx1 .. An alternative to these two methods is to configure the default disk group of a system. Evaluating which systems can now be started........ Done Starting vxconfigd for VxVM ................... Succeeded Done with initial start of VxVM on system sflx2 Done with starting VxVM on target systems. Press Enter to continue.................. Begin initial start of VxVM on system sflx1 Disabling enclosure-based naming ... This message also contains information about configuring a default disk group.... You are now given the option of specifying the default name of a disk group that is to be assumed by VERITAS Volume Manager commands if a disk group is not otherwise specified.. Evaluating which systems can now have their default disk group configured............... If you are installing an HA version of the product........................

.. After installation...... Finally........can configure the default diskgroup...q..Installing the Product System sflx1 is eligible -.. Success Starting vxconfigbackupd on sflx1 ........... Success Starting vxconfigbackupd on sflx2 ... Success Storage Foundation Enterprise HA was started successfully..........log The installation response file is saved at: /opt/VRTS/install/logs/installsf416172204... System sflx2 is eligible -...... A message displays notifying you of a successful installation and the locations of the /VRTS/install files....summary The installsf log is saved at: /opt/VRTS/install/logs/installsf416172204.......... The installation summary is saved at: /opt/VRTS/install/logs/installsf416172204..can configure the default diskgroup.......... See the vxdctl(1M) manual page and the “Creating and Administering Disk Groups” chapter of the VERITAS Volume Manager Administrator’s Guide for more information.. you can use menu item 1 in the vxdiskadm command or the VERITAS Enterprise Administrator to create the disk group.. Success Starting vxrelocd on sflx2 .... Starting vxrelocd on sflx1 . Note If you specify the name of a default disk group........... Do you want to set up the default disk group for each system? [y.......................response Chapter 2....... Preparing to start daemons on target systems... this step does not create the disk group... You can set the name of the default disk group after installation by running the vxdctl defaultdg diskgroup command on a system....n.... Press [Enter] to continue: Press Enter.... Success Starting vxcached on sflx1 ......... 8.......................... Installing VERITAS Storage Foundation 19 ..?] (y) Enter n if you do not want to specify the name of the default disk group at this time.. Success Starting vxcached on sflx2 .. a message displays indicating the utility is preparing to start the daemons on the target systems...

System A A sflx1 sflx2 State RUNNING RUNNING Frozen 0 0 Identify the system state of each node in the output of this command.SYSTEM STATE -. If the value is RUNNING for all the nodes. 150 151 159 405 410 411 ? ? 00:00:00vxiod 00:00:00vxiod ? ? ? ? ? ? 00:00:00vxiod 00:00:00vxiod 00:01:12vxconfigd 00:00:00vxrelocd 00:00:00vxnotify 00:00:00vxrelocd Note If you have disabled hot-relocation. VCS is successfully installed and running. .Installing the Product Checking Volume Manager Processes After the Storage Foundation software has been successfully installed. . 20 VERITAS Storage Foundation Installation Guide . Refer to the hastatus(1M) manual page and the VERITAS Cluster Server User’s Guide for more information on system states and state transitions. and vxrelocd) are running by using the following command: # ps -e | grep vx Entries for these processes appear in output similar to the following: 142 143 . the vxrelocd and vxnotify processes are not displayed. Checking Cluster Operation Note This section is only relevant if you installed and configured an HA version of the Storage Foundation software. type the following command on any node: # hastatus -summary -. To verify that the cluster is operating. you can confirm that key Volume Manager processes (vxconfigd. vxnotify.

This command returns information about the links for LLT for the node on which it is typed. type lltstat -p on any node. See the llttab(4) manual page for details on how to modify the LLT configuration. Based on the sample installation. the output of lltstat -n shows all of the nodes in the cluster and two links for each node. This file is identical on each cluster node. With LLT configured correctly. beginning with the link command. identify the two network cards used by the LLT protocol. If the output shows otherwise. LLT Operation Use the lltstat command to verify that links are active for LLT. The manual page describes ordering the directives in the llttab file. based on the cluster ID entered during installation. The second line identifies the cluster. this file lists the network links that correspond to the specific node. the file /etc/llthosts contains the entries: 0 sflx1 1 sflx2 The /etc/llttab File The file llttab(1M) contains information derived from the installation and used by the utility lltconfig(1M). The first line identifies the node.Installing the Product To display the VCS attribute values for each node in the cluster. type lltstat -nvv | more on any node to view additional information about LLT. The next two lines. LLT (Low Latency Transport) The /etc/llthosts File The file llthosts(4) is a database containing one entry per node that links the LLT system ID (in the first column) with the LLT host name. For information on ports open for LLT. enter the following command on any node: # hasys -display For more information on interpreting the output from this command. see the hasys(1M) manual page and the VERITAS Cluster Server User’s Guide. Installing VERITAS Storage Foundation 21 . Chapter 2. After installation.

If GAB is not operating. 22 VERITAS Storage Foundation Installation Guide . no GAB port membership information is returned: GAB Port Memberships =================================== If only one network is connected. and membership 01 indicates that nodes 0 and 1 are connected. including descriptions of ports. GAB Operation To verify that GAB is operating. gen fd570002 is a random generation number. The /etc/gabtab File The file /etc/gabtab contains a line that resembles: /sbin/gabconfig -c -nN where the -c option configures the driver and -nN specifies the cluster will not be formed until at least N nodes are ready. gen a36e0003 is a random generation number. The variable N represents the number of cluster nodes. the file /etc/gabtab contains a gabconfig(1M) command that configures the GAB driver.Installing the Product GAB Files. the following GAB port membership information is returned: GAB Port Memberships =================================== Port a gen a36e0003 membership 01 Port h gen fd570002 membership 01 Port a indicates that GAB is communicating. Port h indicates that VCS is started. type the following command on each node: # /sbin/gabconfig -a If GAB is operating. GAB and Cluster Operation After installation. refer to the VERITAS Cluster Server User’s Guide. and membership 01 indicates that nodes 0 and 1 are both running VCS. the following GAB port membership information is returned: GAB Port Memberships =================================== Port a gen a36e0003 membership 01 Port a gen a36e0003 jeopardy 1 Port h gen fd570002 membership 01 Port h gen fd570002 jeopardy 1 For more information on GAB.

msi) for Windows systems may be used to access servers running VxVM 3. Java Runtime Environment 1. Windows 98. A version of the VEA client package is provided that can be installed and run on a Microsoft Windows® system. as described in “Installing the VEA Client on a Microsoft Windows System. You can get this product from the Microsoft website if it is not already installed on your system. and many others. 22MB available disk space.” Installing the VEA Client on a Microsoft Windows System The VEA client package (\rhel3_i386\windows\VRTSobgui. For a complete list of administrative tasks and their instructions. To install and run the VEA client.microsoft. For information about upgrading Windows Installer. VRTSob.0. VEA simplifies administrative tasks. visit http://www. or on a separate system that can be used to administer both these and other nodes.com. creating and removing storage checkpoints. This package can be installed on Windows NT®. Windows 2000. may be installed by the installation script on all nodes that are to be administered. it is also recommended that you use Windows NT 4.2 and the VEA service on Linux. Chapter 2. Installing VERITAS Storage Foundation 23 . which may also be installed on one or more of these nodes. The VEA server package.The VERITAS Enterprise Administrator (VEA) The VERITAS Enterprise Administrator (VEA) The VERITAS Enterprise Administrator (VEA) is the graphical administrative interface for configuring shared storage devices.1 or later must be present.exe from that machine. 100MHz Pentium with 32MB memory or higher specification. you must uninstall any existing VERITAS Volume Manager Storage Administrator (VMSA) packages and remove the old setup. Before you install VEA on a Windows system. enabling and disabling change log. For Windows NT 4. such as mounting and unmounting file systems.0 Service Pack 6. ◆ ◆ ◆ Note Microsoft Installer is required to install the VRTSobgui. Only one VEA package can be installed on a Windows machine at a time. and Windows 95 machines.0 or later must be present. Windows ME. your system must conform to the following specifications: ◆ Windows Installer 2. The VRTSobgui package contains the VEA client Graphical User Interface (GUI) program. see the VERITAS Volume Manager User’s Guide–Enterprise Administrator.msi package.

restart the computer. 2.2 Update 1 or later Linux on IA64 requires VxVM 3. ME. type: # /opt/VRTSob/bin/vea To use the VEA client on Linux to administer a remote system. Windows 98 or Windows 95.msi program. Follow the instructions presented by the VRTSobgui. Using VEA to Administer Remote Systems To use the VEA GUI provided with this release to administer VERITAS Volume Manager systems on other platforms. type: # /opt/VRTSob/bin/vea remote_machine_name To use the VEA client on Windows to administer a remote system. Log in as administrator.msi and execute the VRTSobgui.2 Update 3 or later Linux on x86 requires VxVM 3.2.2 Update 6 or later Solaris requires VxVM 3.5 MP2 or later To use the VEA client on Linux to administer the local system. 4. Using Windows Explorer or a DOS Command window. change directory to \rhel3_i386\windows\VRTSobgui. For Windows XP. Insert the CD-ROM containing VEA. 5. After installation is complete. select Start > Programs > VERITAS Enterprise Administrator > VERITAS Enterprise Administrator.The VERITAS Enterprise Administrator (VEA) ▼ To install the VEA GUI on a Windows system 1.msi program with Windows Installer.5 Update 2 or later Linux on IBM zSeries requires VxVM 3.2 or later HP-UX requires VxVM 3. ensure environment changes made during installation take effect by performing one of the following procedures: ◆ ◆ For Windows NT or Windows 2000. you must upgrade VxVM to the following releases: ◆ ◆ ◆ ◆ ◆ ◆ AIX requires VxVM 3. 24 VERITAS Storage Foundation Installation Guide . 3. log out and then log back in.

4. you may find it efficient to load the file system module manually. This should be done after the VxVM packages have been installed.com Chapter 2.Disabling Hot-Relocation on VxVM Disabling Hot-Relocation on VxVM The hot-relocation feature is enabled by default and it is recommended that you leave it on.Proprietary.org/lkml/#export-tainted for information about tainted modules Module vxfs loaded. simply load the vxfs module using the modprobe command: # modprobe vxfs Warning: loading /lib/modules/2.ELsmp/veritas/vxfs/vxfs.o will taint the kernel: non-GPL license .ELsmp/veritas/vxfs/vxportal.Proprietary. this occurs when a user tries to mount a VxFS file system.com See http://www.tux. comment out the vxrelocd line in the startup file /etc/init. However.4. Enabling Intelligent Storage Provisioning (ISP) If you load the allocator provider package (VRTSalloc) after installation. Send bug reports to support@veritas. The device interrogation process when such a system is rebooted can be very time consuming.21-4. so to avoid doing a reboot to upgrade VxFS.o will taint the kernel: non-GPL license . Installing VERITAS Storage Foundation 25 . To disable hot-relocation. you can disable it by preventing the vxrelocd daemon from starting up during system startup. Send bug reports to support@veritas.21-4. In some instances. enter the following commands to restart the VEA service and enable the Intelligent Storage Provisioning (ISP) feature: # /opt/VRTS/bin/vxsvcctrl stop # /opt/VRTS/bin/vxsvcctrl start Loading and Unloading the File System Module The vxfs file system module automatically loads on the first reference to a VxFS file system.d/vxvm-recover by inserting a leading # character as shown here: # vxrelocd root & Any changes that you make to the vxvm-recover file do not take effect until you next reboot the system. some larger class systems can have many dual interface I/O cards with multiple disk chains attached. with warnings Warning: loading /lib/modules/2. For example.

o will taint the kernel: non-GPL license . To determine if the modules successfully loaded.21-4. enter: # df -T | grep vxfs 26 VERITAS Storage Foundation Installation Guide .ELsmp/veritas/vxfs/fdd. enter: # lsmod | grep vxportal vxportal 2952 vxfs 3427960 # lsmod | grep fdd fdd 67212 vxfs 3427960 # lsmod | grep vxfs vxfs 3427960 0 0 [fdd vxportal] 0 0 0 (unused) [fdd vxportal] [fdd vxportal] The above commands provide information about the modules.Loading and Unloading the File System Module Module vxportal loaded.conf. The first field in the output is the module name. Send bug reports to support@veritas.Proprietary. with warnings Warning: loading /lib/modules/2. To determine if any VxFS file systems are mounted. You can unload the module by entering: # rmmod fdd # rmmod vxportal # rmmod vxfs The rmmod command fails if there are any mounted VxFS file systems. with warnings Do not use the insmod command to load the vxfs module as insmod does not examine the module configuration file /etc/modules.com Module fdd loaded.4.

the VERITAS File System Administrator’s Guide and the VERITAS Volume Manager User’s Guide. see the VERITAS Volume Manager Administrator’s Guide.Configuring VERITAS Storage Foundation After Installation 3 This chapter provides guidelines for setting up efficient storage management after installing the VERITAS Storage Foundation software. For details of these tasks. This chapter describes: ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ Setup Tasks After Installation Adding Unsupported Disk Arrays as JBODS Adding Foreign Devices Adding Disks to Disk Groups Guidelines for Configuring Storage Controlling VxVM’s View of Multipathed Devices Configuring Cluster Support in VERITAS Volume Manager (Optional) Reconfiguration Tasks Configuring VxFS 27 .

Create disk groups to place disks under VERITAS Volume Manager control. Configure DRL and FastResync on volumes. Add mirrors to volumes. Add more disks.Setup Tasks After Installation Setup Tasks After Installation The setup sequence listed below is a typical example. Create and maintain snapshots. ▼ Maintenance Tasks ◆ ◆ ◆ Resize volumes and file systems. and create new volumes. 2. ▼ Initial Setup Tasks 1. Configure file systems on volumes. 3. Create volumes in the disk groups. Your system requirements may differ. 28 VERITAS Storage Foundation Installation Guide . ▼ Optional Setup Tasks ◆ ◆ ◆ Designate hot-relocation spare disks in each disk group. create new disk groups.

Refer to “Administering the Device Discovery Layer” in the “Administering Disks” chapter of the VERITAS Volume Manager Administrator’s Guide for details.Adding Unsupported Disk Arrays as JBODS Adding Unsupported Disk Arrays as JBODS After installation. Adding Disks to Disk Groups To place disks in disk groups. For these devices it may be preferable to use the multipathing capability that is provided by the third-party drivers rather than using the Dynamic Multipathing (DMP) feature. Refer to the VERITAS Volume Manager User’s Guide and the “Creating and Administering Disk Groups” chapter of the VERITAS Volume Manager Administrator’s Guide for information on how to create disk groups for your disks. use VEA or the vxdiskadm program after completing the installation. Adding Foreign Devices The device discovery feature of VxVM cannot discover some devices that are controlled by third-party drivers. add any disk arrays that are unsupported by VERITAS to the DISKS (JBOD) category as described in “Administering the Device Discovery Layer” in the “Administering Disks” chapter of the VERITAS Volume Manager Administrator’s Guide. such as for EMC PowerPath. Configuring VERITAS Storage Foundation After Installation 29 . Such foreign devices can be made available to VERITAS Volume Manager as simple disks by using the vxddladm addforeign command. Chapter 3. This also has the effect of bypassing DMP.

At least two disks are required for the striped plex. See the cross-references in each section for more information about each guideline. The following are suggestions for protecting your system and data: ◆ Perform regular backups to protect your data. VERITAS Volume Manager can protect your system from these problems.Guidelines for Configuring Storage Guidelines for Configuring Storage The following general guidelines help you understand and plan an efficient storage management system. ◆ ◆ ◆ ◆ ◆ ◆ ◆ 30 VERITAS Storage Foundation Installation Guide . typing a command in error can remove critical files or damage a file system directly. When combining striping and mirroring. See “RAID-5 Guidelines” on page 33 for details. Power surges can damage several (or all) disks on your system. Backups are necessary if all copies of a volume are lost or corrupted. Performing regular backups ensures that lost or corrupted data is available to be retrieved. Make sure enough disks are available for a combined striped and mirrored configuration. never place subdisks from one plex on the same physical disk as subdisks from the other plex. Leave the VERITAS Volume Manager hot-relocation feature enabled. The data must be preserved so it can be used in case of failure. Loss of access is due to the failure of a key disk used for system operations. Make sure that each RAID-5 volume has at least one log plex. See “Dirty Region Logging (DRL) Guidelines” on page 31 for details. To maintain system availability. Use logging to prevent corruption of recovery data in RAID-5 volumes. data important to running and booting your system must be mirrored. Use the DRL feature to speed up recovery of mirrored volumes after a system crash. Also. Guidelines for Protecting Your System and Data A disk failure can cause loss of data on the failed disk and loss of access to your system. Use mirroring to protect data against loss from a disk failure. See “Hot-Relocation Guidelines” on page 34 for details. See “Mirroring Guidelines” on page 31 for details. Use striping to improve the I/O performance of volumes. See “Striping Guidelines” on page 32 for details. and one or more additional disks are needed for the mirror.

Set the read policy to prefer the faster plex. Another controller can continue to provide data from a mirror. or when located on a much faster device. DCO volumes are independent of plexes. VERITAS Volume Manager maintains a bitmap and stores this information in the DCO volume. This can cause the read/write ratio for physical I/O operations through the file system to be biased toward writing (when compared to the read/write ratio at the application level).Guidelines for Configuring Storage Mirroring Guidelines Refer to the following guidelines when using mirroring. VERITAS Volume Manager keeps track of the regions within a volume that have changed as a result of writes to a plex. Mirroring across controllers allows the system to survive a failure of one of the controllers. ◆ Where possible. are ignored by plex policies. A higher percentage of read operations results in even better performance. Chapter 3. ◆ Note The operating system implements a file system cache. DCO Volumes are defined for and added to a volume to provide DRL. Mirroring may not provide a performance increase or may even result in performance decrease in a write-intensive workload environment. Configuring VERITAS Storage Foundation After Installation 31 . Most disk controllers support overlapped seeks. When DRL is enabled. By default. This action compromises the availability benefits of mirroring and degrades performance. and are only used to hold the DRL information. Do not configure two plexes of the same volume on disks that are attached to a controller that does not support overlapped seeks. This allows seeks to begin on two disks at once. use disks attached to different controllers when mirroring or striping. at least 70 percent of physical I/O operations should be read operations. ◆ Do not place subdisks from different plexes of a mirrored volume on the same physical disk. a volume with one striped plex is configured to prefer reading from the striped plex. see the VERITAS Volume Manager Administrator’s Guide. Using the vxassist or vxdiskadm commands precludes this from happening. ◆ For more information. This is important for older controllers or SCSI disks that do not cache on the drive. Read requests can frequently be satisfied from the cache. It is less important for modern SCSI disks and controllers. A plex exhibits superior performance when striped or concatenated across multiple disks. To provide optimum performance improvements through the use of mirroring. Dirty Region Logging (DRL) Guidelines Dirty Region Logging (DRL) can speed up recovery of mirrored volumes following a system crash.

This means that the track size differs between cylinders. does this automatically. combine striping with mirroring to combine high-performance with improved reliability. the greater the improvement in I/O performance. see the VERITAS Volume Manager Administrator’s Guide. If only one plex of a mirrored volume is striped. configure the same stripe-unit size for each striped plex. unless you know the I/O pattern of the application. Typically. In general. random I/O streams. Avoid the use of controllers that do not support overlapped seeks.Guidelines for Configuring Storage Note Using Dirty Region Logging can impact system performance in a write-intensive environment. distribute the subdisks of a striped volume across drives connected to different controllers and buses. however. (The default read policy. so that outer disk tracks have more sectors than inner tracks. Note Many modern disk drives have variable geometry.) If more than one plex of a mirrored volume is striped. select. 32 VERITAS Storage Foundation Installation Guide . For these drives. ◆ Volumes with small stripe-unit sizes can exhibit poor sequential I/O latency if the disks do not have synchronized spindles. or largely asynchronous. the greater the number of physical disks in the stripe. For more information. Generally. striping over disks without synchronized spindles yields better performance when used with larger stripe-unit sizes and multi-threaded. Striping Guidelines Refer to the following guidelines when using striping.) ◆ ◆ ◆ ◆ ◆ The vxassist command automatically applies and enforces many of these rules when it allocates space for striped plexes in a volume. Where possible. (Such controllers are rare. use a moderate stripe-unit size (such as 64 kilobytes). 64 kilobytes. which is also the default used by vxassist) is recommended. a moderate stripe-unit size (for example. If it is not feasible to set the stripe-unit size to the track size. set the policy of the volume to prefer for the striped plex. If this is an issue. use the default 64-kilobyte stripe-unit size. It is therefore not always appropriate to use the track size as the stripe-unit size. and you do not know the application I/O pattern. this reduces the effective mean time between failures of the volume. Calculate stripe-unit sizes carefully. ◆ ◆ ◆ Do not place more than one column of a striped plex on the same physical disk.

it is set to the length of any RAID-5 plex associated with the volume. they must belong to disks other than those used for the RAID-5 plex. it must be a multiple of the stripe-unit size of the associated RAID-5 plex. RAID-5 logs can be mirrored and striped. In general. it is set to the length of the smallest RAID-5 log plex that is associated. Configuring VERITAS Storage Foundation After Installation 33 . it is set to zero. Chapter 3. it is set to zero. RAID-5 Guidelines Refer to the following guidelines when using RAID-5. If no RAID-5 log plexes are associated. if any. If you specify the volume length. If any log plexes exist. The RAID-5 plex must be derived from at least three subdisks on three or more physical disks. the guidelines for mirroring and striping together also apply to RAID-5. Sparse RAID-5 log plexes are not valid. see the VERITAS Volume Manager Administrator’s Guide. The following guidelines should also be observed with RAID-5: ◆ ◆ Only one RAID-5 plex can exist per RAID-5 volume (but there can be multiple log plexes). ◆ ◆ ◆ ◆ ◆ For more information. otherwise. RAID-5 volumes are not supported for sharing in a cluster. if any. If the volume length is not explicitly specified. see the VERITAS Volume Manager Administrator’s Guide. If the log length is not explicitly specified.Guidelines for Configuring Storage For more information.

it is possible to have performance degradation after the relocation. configure the disk group so that there is at least one disk that does not already contain a mirror of the volume. vxrelocd. When free space is used for relocation purposes. Refer to the following guidelines when using hot-relocation. set up the spare disks on different controllers (in case one of the controllers fails). This disk should either be a spare disk with some available space or a regular disk with some free space and the disk is not excluded from hot-relocation use. ◆ The hot-relocation feature is enabled by default. configure the disk group so that at least one disk does not already contain the RAID-5 plex (or one of its log plexes) of the volume. you cannot relocate the data plex. VERITAS Volume Manager uses any available free space within the disk group. This disk should either be a spare disk with some available space or a regular disk with some free space and the disk is not excluded from hot-relocation use. The hot-relocation feature is enabled by default. Instead. For a mirrored and striped volume. If no spares exist. The associated daemon. If a mirrored volume has a DRL log subdisk as part of its data plex. This gives you some control over which disks are used for relocation. attempt to relocate any affected subdisks that are redundant.Guidelines for Configuring Storage Hot-Relocation Guidelines Hot-relocation automatically restores redundancy and access to mirrored and RAID-5 volumes when a disk fails. it is advisable to leave it enabled. Although it is possible to disable hot-relocation. is automatically started during system startup. Although hot-relocation does not require you to designate disks as spares. ◆ ◆ ◆ ◆ ◆ ◆ ◆ 34 VERITAS Storage Foundation Installation Guide . and initiate recovery procedures. For a RAID-5 volume. This is done by relocating the affected subdisks to disks designated as spares and/or free space in the same disk group. If a given disk group spans multiple controllers and has more than one spare disk. configure the disk group so that at least one disk does not already contain one of the mirrors of the volume or another subdisk in the striped plex. It will notify you of the nature of the failure. place log subdisks in log plexes that contain no data. Some of the original spare space may be occupied by relocated subdisks. This disk should either be a spare disk with some available space or a regular disk with some free space and the disk is not excluded from hot-relocation use. For a mirrored volume. designate one or more additional disks as spares to augment the spare space. designate at least one disk as a spare within each disk group. After hot-relocation occurs.

Examine the locations of newly-relocated subdisks to determine whether they should be relocated to more suitable disks to regain the original performance benefits. Accessing Volume Devices As soon as a volume has been created and initialized. use the vxdiskadm command as described in “Disabling and Enabling Multipathing for Specific Devices” in the “Administering Dynamic Multipathing (DMP)” chapter of the VERITAS Volume Manager Administrator’s Guide. mount and repair file systems. Configuring VERITAS Storage Foundation After Installation 35 . Chapter 3. Although it is possible to build VERITAS Volume Manager objects on spare disks (using vxmake or the VEA interface). or by application programs such as relational databases and other data management software. Creating a volume in a disk group sets up block and character (raw) device files that can be used to access the volume: /dev/vx/dsk/diskgroup/volume /dev/vx/rdsk/diskgroup/volume block device file for volume character device file for volume The pathnames include a directory named for the disk group.Controlling VxVM’s View of Multipathed Devices ◆ Hot-relocation does not guarantee to preserve the original performance characteristics or data layout. it is recommended that you use spare disks for hot-relocation only. it is available for use as a virtual disk partition by the operating system for the creation of a file system. Controlling VxVM’s View of Multipathed Devices To control how a device is treated by the Dynamic Multipathing (DMP) feature of VxVM. and to lay out databases that require raw partitions. ◆ See the “Administering Hot-Relocation” chapter of the VERITAS Volume Manager Administrator’s Guide for more information. Use the appropriate device node to create.

3. To determine if a node is a master or slave. The cluster functionality in VERITAS Volume Manager allows multiple hosts to simultaneously access and manage a set of disks under VERITAS Volume Manager control. run the command vxdctl -c mode. If you use the vxdg command. run vxdctl enable to see the newly initialized disks. The VERITAS Volume Manager software includes an optional cluster feature that enables it to be used in a cluster environment. Start the cluster on one node only to prevent access by other nodes. If you are setting up VERITAS Volume Manager for the first time.0 Getting Started Guide. 2. On other nodes in the cluster. Note The VERITAS Volume Manager cluster feature requires a license. run the vxdiskadm program and choose option 1 to initialize new disks. each host is referred to as a node in the cluster. use vxassist or VEA to create volumes in the disk groups. Configuring Shared Disk Groups This section describes how to configure shared disks in a cluster. A cluster is a set of hosts sharing a set of disks. 5. you need to configure new shared disks. 4. create disk groups on the shared disks. which can be obtained from your Customer Support channel. When asked to add these disks to a disk group. refer to the VERITAS Storage Solutions 4. specify the -s option to create shared disk groups. configure the shared disks using the following procedure: 1. For information about enabling cluster functionality in VERITAS Volume Manager.Configuring Cluster Support in VERITAS Volume Manager (Optional) Configuring Cluster Support in VERITAS Volume Manager (Optional) Note The VERITAS Cluster Server software (VCS) must be used as the cluster monitor. From the master node. 36 VERITAS Storage Foundation Installation Guide . choose none to leave the disks for future use. On one node. Use the vxdg command or VEA to create disk groups. If you are installing VERITAS Volume Manager for the first time or adding disks to an existing cluster. From the master node only.

This command displays the same list of shared disk groups displayed earlier. 6. Enter the vxdg list command on each node to display the shared disk groups. If not. To display the shared flag for all the shared disk groups. bring up the other cluster nodes. Converting Existing VERITAS Volume Manager Disk Groups to Shared Disk Groups To convert existing disk groups to shared disk groups: 1. use the following command: # vxdg deport diskgroup To import disk groups to be shared. Configure the disk groups using the following procedure. To list all disk groups. enabling other nodes to recognize the shared disks. 2. see the VERITAS Cluster File System Installation and Configuration Guide. Bring up the other cluster nodes. If the cluster is only running with one node. 3. replace them with larger ones. Configuring VERITAS Storage Foundation After Installation 37 . Enter the vxdg list command on each node to display the shared disk groups. use the following command: # vxdg -s import diskgroup This procedure marks the disks in the shared disk groups as shared and stamps them with the ID of the cluster. For information on converting disk groups in a VERITAS Cluster File System (CFS) environment. Start the cluster on one node only to prevent access by other nodes. use the following command: # vxdg list To deport the disk groups that are to be shared.Configuring Cluster Support in VERITAS Volume Manager (Optional) Note RAID-5 volumes are not supported for sharing in a cluster. Chapter 3. use the following command: # vxdg list The disk groups are now ready to be shared. If dirty region logs exist. ensure they are active.

The VERITAS-specific commands are described in the VxFS guides and online manual pages. Changing the Name of the Default Disk Group If you use the VERITAS installer to install the VERITAS Volume Manager software. you can use the vxdiskadm command to change the naming convention that is used. or the VXVM_DEFAULTDG environment variable is not set. you can choose whether the displayed disk access names are based on device names or on names that you assign to disk enclosures. If required. Enabling or Disabling Enclosure-Based Naming If you use the VERITAS installer to install the VERITAS Volume Manager software. Before you can use this file system. See “Displaying and Specifying the System-Wide Default Disk Group” in the “Creating and Administering Disk Groups” chapter of the VERITAS Volume Manager Administrator’s Guide for details. Configuring VxFS After installation. This disk group will be used by commands if you do not specify the -g option. you can enter the name of the default disk group. A file system can be automatically mounted at system boot time if you add an entry for it in the /etc/fstab file. you must mount it with the mount -t vxfs command. If required. 38 VERITAS Storage Foundation Installation Guide .Reconfiguration Tasks Reconfiguration Tasks The following sections describe tasks that allow you to make changes to the configuration that you specified during installation. you can use the vxdctl defaultdg command to change the default disk group. You can unmount the file system later with the umount command. Refer to the Quick Start Reference appendix of the VERITAS File System Administrator’s Guide for examples of the most common VxFS operating procedures. See “Changing the Disk-Naming Scheme” in the “Administering Disks” chapter of the VERITAS Volume Manager Administrator’s Guide for more information. you can create a VERITAS File System on a disk slice or on a VERITAS Volume Manager volume by using the mkfs -t vxfs command.

0. To use the optional cluster functionality of VERITAS Volume Manager (VxVM).Upgrading VERITAS Storage Foundation and Linux The following topics are covered in this chapter: ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ 4 Using Existing Licenses Supported Operating Systems and Upgrade Paths Upgrading to Storage Foundation 4.0 installed where you need to upgrade the Linux kernel. If you are upgrading the HA version of the VERITAS Storage Solutions software.0 Already Installed Upgrading VxFS Disk Layout Versions Upgrading VxVM Disk Group Versions Upgrading the VEA Client on a Microsoft Windows System Note This chapter applies only to systems on which VERITAS Foundation Suite for Linux or VERITAS Storage Solutions for Linux is already installed.0 Upgrading Storage Foundation After Reinstalling Linux Upgrading Linux Kernel Errata with Storage Foundation 4. Only users with superuser privileges can upgrade and initialize VERITAS Storage Foundation and Linux. follow the guidelines given in the VERITAS Cluster Server (VCS) Installation Guide and Release Notes for information on preserving your VCS configuration across the upgrade procedure. 39 . In addition. the nodes cannot be updated while the cluster functionality is in use. See “Installing VERITAS Storage Foundation” on page 7 for more information on installing VERITAS software in a cluster. all the cluster nodes must be running VxVM 4. and to systems with VERITAS Storage Foundation 4.

0 2.0 systems.7-10.Using Existing Licenses Using Existing Licenses You must obtain new licenses to use all of the features in the VERITAS Storage Foundation 4.2 Red Hat Advanced Server 2.2 MP1 Storage Solutions 2.1 Storage Solutions 2.4.4.1) Not Supported Not Supported Not Supported 2. Supported Operating Systems and Upgrade Paths The following table shows the supported Red Hat kernels for VERITAS software on Linux: VERITAS Product Red Hat 7.21-15 To determine which Linux kernel version your system is running. 2.21-4 Not Supported Not Supported 2.4.0 Update2 without performing a complete reinstallation.0” on page 41.12 Not Supported Not Supported Not Supported Not Supported Not Supported 2. it is possible to upgrade the operating system to Red Hat Enterprise Linux 3. 40 VERITAS Storage Foundation Installation Guide .1 or Red Hat Enterprise Linux 3.4.0 Not Supported 2. Use the procedure given in “Upgrading to Storage Foundation 4.9-e. use the following command: # uname -r For Red Hat Advanced Server 2.9-e.1 Red Hat Enterprise Linux 3. Any VERITAS licenses for previous releases that are currently installed will allow you to use only a limited subset of these features.9-10 (RH7.0 software.21-12 Foundation Suite 1.4.2) Not Supported Not Supported Not Supported Not Supported 2.4.7-10 (RH7.4.21-4 Not Supported 2.9-12 (RH7.2) 2. See “Preinstallation” on page 1 for more information.2 Storage Solutions 2.0 Red Hat Enterprise Linux 3.0 Update2 Foundation Suite 1.4.4.1 or Red Hat 7.3 2.2 MP2 Storage Foundation 4.4.

lst. 4. Upgrading VERITAS Storage Foundation and Linux 41 . and vxprint -ht commands. 2. If you need to upgrade your kernel with VERITAS Storage Foundation 4. In particular. You can also use this procedure if you want to migrate to a VxVM 4. 3. Log in as root. if this has not already been done.0 Update2.conf (as appropriate).0 system is already running VERITAS Storage Solutions software on a Red Hat Advanced Server 2.0 requires that a Red Hat Advanced Server 2.Upgrading to Storage Foundation 4. 1.0 Update 2. See “Preinstallation” on page 1 for more information. You should also run the vxlicrep. It is recommended that you make a complete backup of all data on the system before proceeding with the upgrade.0 If your Red Hat Enterprise Linux 3. You may need this information to reconfigure your system after the upgrade. you will need the information in files such as /boot/grub/menu.0 already installed.1 or Red Hat Enterprise Linux 3.0 Already Installed” on page 47. Use the vxlicrep command to make a record of the currently installed VERITAS licenses. Follow the procedure given in “Upgrading Storage Foundation After Reinstalling Linux” on page 44. this section describes how to upgrade it to VERITAS Storage Foundation 4.conf or /etc/lilo. and /etc/fstab. Check if the system’s root disk is under VxVM control by running this command: # df -v / Chapter 4. Upgrading to Storage Foundation 4.0 system is also upgraded to Red Hat Enterprise Linux 3.0 system. and record the output from these. Perform any necessary preinstallation checks and configuration. follow the procedure given in “Upgrading Linux Kernel Errata with Storage Foundation 4.0 As it is not possible to upgrade a Red Hat 7. a full reinstallation of both the operating system and VxVM is required.1 or Red Hat Enterprise Linux 3.0. Note Upgrading to VERITAS Storage Foundation 4.1 or 7. /etc/grub. vxdisk list.2 system to Red Hat Enterprise Linux 3.0 system on a fresh installation of Linux.

Upgrading to Storage Foundation 4.0

The root disk is under VxVM control if /dev/vx/dsk/rootvol is listed as being mounted as the root (/) file system. If so, unmirror and unencapsulate the root disk as described in the following steps: a. Use the vxplex command to remove all the plexes of the volumes rootvol, swapvol, usr, var, opt and home that are on disks other than the root disk. For example, the following command removes the plexes mirrootvol-01, and mirswapvol-01 that are configured on a disk other than the root disk:
# vxplex -o rm dis mirrootvol-01 mirswapvol-01

Note Do not remove the plexes on the root disk that correspond to the original disk partitions. b. Enter the following command to convert all the encapsulated volumes in the root disk back to being accessible directly through disk partitions instead of through volume devices:
# /etc/vx/bin/vxunroot

Following the removal of encapsulation, the system is rebooted from the unencapsulated root disk. 5. Use the following command to check if any VERITAS File Systems or Storage Checkpoints are mounted:
# df -T | grep vxfs

6. Unmount all Storage Checkpoints and VxFS file systems:
# umount /checkpoint_name
# umount /filesystem

7. Stop activity to all VxVM volumes. For example, stop any applications such as databases that access the volumes, and unmount any file systems that have been created on the volumes. 8. Stop all the volumes by entering the following command for each disk group:
# vxvol -g diskgroup stopall

To verify that no volumes remain open, use the following command:
# vxprint -Aht -e v_open

9. Comment out any mount points in the /etc/fstab file for VxFS file systems, or for any file systems that are configured on VxVM volumes.

42

VERITAS Storage Foundation Installation Guide

Upgrading to Storage Foundation 4.0

10. Stop the VEA service by entering the following command:
# /opt/VRTS/bin/vxsvcctrl stop

11. Use the rpm -ev command to remove all the old VERITAS packages:
# # # # # rpm rpm rpm rpm rpm -ev -ev -ev -ev -ev VRTSvxvm VRTSvmman VRTSvmdoc
VRTSvxfs VRTSfsman VRTSfsdoc
VRTSvmpro VRTSfspro
VRTSobgui VRTSob
VRTSvlic

Note This is an example of the commands to be used. Your system may have more or fewer packages installed than shown here. 12. If required, upgrade Linux on your system to Red Hat Enterprise Linux 3.0 Update2, and then reboot the system to load the new kernel. 13. Install VERITAS Storage Foundation 4.0 and any additional required packages from the VERITAS CD-ROM as described in “Installing VERITAS Storage Foundation” on page 7. 14. Reinstate the mount points in the /etc/fstab file that you commented out in step 9 on page 42. 15. Shut down and reboot the system. VERITAS Volume Manager should recognize the existing disks and volumes without any intervention from you. 16. Check if the VEA service restarted:
# /opt/VRTS/bin/vxsvcctrl status

If the VEA service did not restart, restart it:
# /opt/VRTS/bin/vxsvcctrl start

There are several optional configuration steps that you may want to perform:

If you want to use features of VERITAS Storage Foundation 4.0 for which you do not currently have an appropriate license installed, obtain the license and run the vxlicinst command to add it to your system. To encapsulate and mirror the boot disk, follow the procedures in the “Administering Disks” chapter of the VERITAS Volume Manager Administrator’s Guide. To upgrade VxFS Disk Layout versions and VxVM Disk Group versions, follow the instructions given in “Upgrading VxFS Disk Layout Versions” on page 48 and “Upgrading VxVM Disk Group Versions” on page 49.

◆ ◆

Chapter 4, Upgrading VERITAS Storage Foundation and Linux

43

Upgrading Storage Foundation After Reinstalling Linux

Upgrading Storage Foundation After Reinstalling Linux
If your system is already running VERITAS Foundation Suite software on a Red Hat 7.1 or 7.2 system, this section describes how to upgrade it to a Red Hat Enterprise Linux 3.0 Update2 system running VERITAS Storage Foundation 4.0. Note This procedure requires a complete reinstallation of both the operating system and the VERITAS software. There is no supported procedure for upgrading from Red Hat 7.1 or 7.2 to Red Hat Enterprise Linux 3.0 Update2. You must ensure that you have made backups of all data that you want to preserve. In particular, you will need the information in files such as /boot/grub/menu.lst, /etc/grub.conf or /etc/lilo.conf (as appropriate), and /etc/fstab. You should also run the vxlicrep, vxdisk list, and vxprint -ht commands, and record the output from these. You may need this information to reconfigure your system after the upgrade. 1. Log in as root. 2. Perform any necessary preinstallation checks and configuration. See “Preinstallation” on page 1 for more information. 3. Use the vxlicrep command to make a record of the currently installed VERITAS licenses. 4. Check if the system’s root disk is under VxVM control by running this command:
# df -v /

The root disk is under VxVM control if /dev/vx/dsk/rootvol is listed as being mounted as the root (/) file system. If so, unmirror and unencapsulate the root disk as described in the following steps: a. Use the vxplex command to remove all the plexes of the volumes rootvol, swapvol, usr, var, opt and home that are on disks other than the root disk. For example, the following command removes the plexes mirrootvol-01, and mirswapvol-01 that are configured on a disk other than the root disk:
# vxplex -o rm dis mirrootvol-01 mirswapvol-01

Note Do not remove the plexes on the root disk that correspond to the original disk partitions.

44

VERITAS Storage Foundation Installation Guide

Unmount all Storage Checkpoints and VxFS file systems: # umount /checkpoint_name # umount /filesystem 7. Enter the following command to convert all the encapsulated volumes in the root disk back to being accessible directly through disk partitions instead of through volume devices. Caution This is likely to destroy any existing data on any disks that are touched by the installation procedure. stop any applications such as databases that access the volumes. For example. Stop activity to all VxVM volumes. and unmount any file systems that have been created on the volumes. 8. Shut down the system. 11.Upgrading Storage Foundation After Reinstalling Linux b. You will need to recreate these entries in the /etc/fstab file on the freshly installed system. the system is rebooted from the unencapsulated root disk. # /etc/vx/bin/vxunroot Following the removal of encapsulation. it is recommended that you back it up before starting the upgrade. 5. Make a record of the mount points for VxFS file systems and VxVM volumes that are defined in the /etc/fstab file. Install Red Hat Enterprise Linux 3. do not reconfigure any disks other than the root disk or those disks that were previously in the rootdg disk group. During installation. 10. Stop all the volumes by entering the following command for each disk group: # vxvol -g diskgroup stopall To verify that no volumes remain open. Use the following command to check if any VERITAS File Systems or Storage Checkpoints are mounted: # df -T | grep vxfs 6.0 on your system. See “Preinstallation” on page 1 for more information. Upgrading VERITAS Storage Foundation and Linux 45 . There must be at least one other disk in the rootdg disk group in addition to the root disk for vxunroot to succeed. use the following command: # vxprint -Aht -e v_open 9. Perform any necessary preinstallation checks. 12. Chapter 4. To ensure the integrity of your data.

If you have not yet obtained new licenses. To encapsulate and mirror the boot disk. To upgrade VxFS Disk Layout versions and VxVM Disk Group versions. but not all. Shut down and reboot the system. obtain the license and run the vxlicinst command to add it to your system.Upgrading Storage Foundation After Reinstalling Linux 13. This will allow you to use some. There are several optional configuration steps that you may want to perform: ◆ If you want to use features of VERITAS Storage Foundation 4. 15. VERITAS Volume Manager 4. of the software features.0 for which you do not currently have an appropriate license installed. follow the instructions given in “Upgrading VxFS Disk Layout Versions” on page 48 and “Upgrading VxVM Disk Group Versions” on page 49. follow the procedures in the “Administering Disks” chapter of the VERITAS Volume Manager Administrator’s Guide. enter the license keys that you recorded in step 3 on page 44. Reinstate the mount points in the /etc/fstab file that you recorded in step 9 on page 45. ◆ ◆ 46 VERITAS Storage Foundation Installation Guide .0 should recognize the existing disks and volumes without any intervention from you. 14. Install VERITAS Storage Foundation 4.0 and any additional required packages from the VERITAS CD-ROM as described in “Installing VERITAS Storage Foundation” on page 7.

re-encapsulate and remirror the root disk as described in the “Administering Disks” chapter of the VERITAS Volume Manager Administrator’s Guide. If you removed rootability in step 2 on page 47. Upgrade Linux on your system. Log in as root.0 has been installed. If so. var. There must be at least one other disk in the rootdg disk group in addition to the root disk for vxunroot to succeed.0 Already Installed Note This procedure is only required if your root disk is encapsulated. Check if the system’s root disk is under VxVM control by running this command: # df -v / The root disk is under VxVM control if /dev/vx/dsk/rootvol is listed as being mounted as the root (/) file system.0 Already Installed Upgrading Linux Kernel Errata with Storage Foundation 4. 2. b. Chapter 4. Upgrading VERITAS Storage Foundation and Linux 47 . usr. 3.Upgrading Linux Kernel Errata with Storage Foundation 4. Use the vxplex command to remove all the plexes of the volumes rootvol. and mirswapvol-01 that are configured on a disk other than the root disk: # vxplex -o rm dis mirrootvol-01 mirswapvol-01 Do not remove the plexes on the root disk that correspond to the original disk partitions. Enter the following command to convert all the encapsulated volumes in the root disk back to being accessible directly through disk partitions instead of through volume devices. follow this procedure: 1. # /etc/vx/bin/vxunroot Following the removal of encapsulation. If you need to upgrade your Linux kernel after VERITAS Storage Foundation 4. the following command removes the plexes mirrootvol-01. unmirror and unencapsulate the root disk as described in the following steps: a. the system is rebooted from the unencapsulated root disk. swapvol. 4. opt and home that are on disks other than the root disk. and then reboot the system to load the new kernel. For example.

0 on the Linux platform. Version 2. # vxfsconvert /device_name See the vxfsconvert(1M) and fsadm_vxfs(1M) manual pages for more information on converting to VxFS file systems.0 is the last major release to support disk layout Version 4.0 allows Version 4 and Version 6 file system disk layouts to be mounted.Upgrading VxFS Disk Layout Versions Upgrading VxFS Disk Layout Versions VERITAS File System 4.0). When to Use vxupgrade You can use the vxupgrade command to upgrade VxFS disk layout Version 4 to disk layout Version 6 while the file system remains mounted.0 release. # vxupgrade -n 6 /mount_point See the vxupgrade(1M) and fsadm_vxfs(1M) manual pages for more information on upgrading VxFS file systems. Any file system created on VxFS 4. VxFS 4. but you can specify the Version 4 disk layout using the mkfs_vxfs command: # mkfs -t vxfs -o version=4 /devicename To determine the disk layout version of a VxFS file system. upgrade older disk layout versions to disk layout Version 6 (see the VERITAS Storage Foundation Release Notes for information on new features in VxFS 4. run the fstyp_vxfs command on the file system physical device. 48 VERITAS Storage Foundation Installation Guide . and Version 5 are not supported by VxFS 4. Note The contents of intent logs created on a previous disk layout version cannot be used after the disk layout version is upgraded. When to Use vxfsconvert You can use the vxfsconvert command to convert an unmounted ext2 or ext3 file system to a VERITAS file system with disk layout Version 4. for example: # /opt/VRTS/bin/fstyp –v /dev/vx/dsk/rootdg/volname | grep version magic a501fcf5 version 6 ctime Thu Jul 31 11:29:31 2004 When to Upgrade Disk Layout Versions To make use of the extended features available in the VxFS 4.0 uses disk layout Version 6 by default. Disk layout Version 1.

110 90 110 Use the following command to find the version of a disk group: # vxdg list diskgroup To upgrade a disk group from version 90 to version 110. use the following command: # vxdg upgrade diskgroup Chapter 4.2 to the present. Upgrading VxVM Disk Group Versions All VERITAS Volume Manager disk groups have an associated version number.Upgrading VxVM Disk Group Versions Requirements for Upgrading to Disk Layout Version 6 Converting a Version 4 disk layout to Version 6 disk layout requires adequate free space to complete. Allow at least ten minutes to upgrade for every million inodes in the file system. Typical maximum space is at least two additional inodes with one block for every inode. Upgrading VERITAS Storage Foundation and Linux 49 . The space and time required to complete the upgrade increases with the number of files. VERITAS Volume Manager Release 3.0 Disk Group Version Supported Disk Group Versions 90 90. The following table summarizes the disk group versions that correspond to each VxVM release on Linux from 3. extended attributes. and hard links in the file system. so you need to upgrade existing disk groups before you can perform the tasks. Some new features and tasks work only on disk groups with the current disk group version.2 4. Each VxVM release supports a specific set of disk group versions and can import and perform tasks on disk groups with those versions.

50 VERITAS Storage Foundation Installation Guide . first uninstall the existing VEA client package as follows: 1. 2. and click the Remove button.Upgrading the VEA Client on a Microsoft Windows System Upgrading the VEA Client on a Microsoft Windows System To upgrade the VEA client on a Windows system. Click Yes when a dialog box appears asking you to confirm the removal. 3. Double-click Add/Remove Programs to display a list of installed products. install the new VEA client package by following the instructions given in “Installing the VEA Client on a Microsoft Windows System” on page 23. Log in as administrator. 4. 5. Select VERITAS Enterprise Administrator from the list. After removing the existing package. Select Start > Settings > Control Panel.

The following sections describe in detail how to do this. you must remove any mirrors of the volumes on the root disk.Uninstalling VERITAS Storage Foundation To remove the VERITAS Storage Foundation software. remove any VERITAS File Systems or Storage Checkpoints. 51 . unencapsulate the volumes on the root disk. and move volumes from VERITAS Volume Manager control. and how to remove the VERITAS packages: ◆ ◆ ◆ ◆ ◆ ◆ Removing Rootability Removing VERITAS File Systems Moving Volumes To Disk Partitions Removing Storage Foundation Packages Uninstalling VERITAS Infrastructure Packages Removing the VEA Client from a Microsoft Windows System Note Only users with superuser privileges can uninstall VERITAS Storage Foundation. complete the following preparations before the uninstallation: 5 Before uninstalling.

Check if the system’s root disk is under VxVM control by running this command: # df -v / The root disk is under VxVM control if /dev/vx/dsk/rootvol is listed as being mounted as the root (/) file system. usr. opt and home that are on disks other than the root disk. If so. unmirror and unencapsulate the root disk as described in the following steps: 2. Use the vxplex command to remove all the plexes of the volumes rootvol. For example. var. 1. the following command removes the plexes mirrootvol-01. Enter the following command to convert all the encapsulated volumes in the root disk back to being accessible directly through disk partitions instead of through volume devices: # /etc/vx/bin/vxunroot Following the removal of encapsulation. 3. swapvol.Removing Rootability Removing Rootability Note Perform this procedure if you configured rootability by encapsulating the root disk. 52 VERITAS Storage Foundation Installation Guide . and mirswapvol-01 that are configured on a disk other than the root disk: # vxplex -o rm dis mirrootvol-01 mirswapvol-01 Caution Do not remove the plexes that correspond to the original root disk partitions. the system is rebooted from the unencapsulated root disk.

Moving Volumes onto Disk Partitions Using VxVM 1. If VxFS will not be installed again. Make backups of all data on the file systems that you wish to preserve. Unmount all VxFS file systems before removing the package. VEA. 1. all VxFS file systems must be converted to a new file system type. This can be done using one of these procedures: ◆ ◆ ◆ Back up the system fully onto tape and then recover from it. Moving Volumes To Disk Partitions All volumes must be moved to disk partitions. After you remove the VxFS package. Chapter 5. or the vxevac script. or recreate them as non-VxFS file systems on non-VxVM volumes or partitions. It is advisable to back up VxFS file systems before installing a new VxFS package. Check if any VERITAS File Systems or Storage Checkpoints are mounted: # df -T | grep vxfs 2. You should consider the amount of target disk space required for this before you begin. Uninstalling VERITAS Storage Foundation 53 . Evacuate disks using the vxdiskadm program. The evacuated disks provide the initial free disk space for volumes to be moved to disk partitions. Back up each file system individually and then recover them all after creating new file systems on disk partitions. 3. Comment out or remove any VxFS file system entries from the /etc/fstab file. Evacuation moves subdisks from the specified disks to target disks. VxFS file systems are not mountable or accessible until another VxFS package is installed. Unmount all Storage Checkpoints and file systems: # umount /checkpoint_name # umount /filesystem 4. Use VxVM to move volumes incrementally onto disk partitions as described in the following section.Removing VERITAS File Systems Removing VERITAS File Systems Note The VxFS package cannot be removed if there are any mounted VxFS file systems.

If the output is 0. make sure that the application is not updating the volume and that data on the volume is synced. use the following command: # vxprint -F “%sdnum” disk_media_name 11. 9. If there is not enough free space for the partition. remove the disk from VERITAS Volume Manager control using the following commands: # vxdg -g diskgroup rmdisk disk _media_name # vxdisk rm disk_access_name 54 VERITAS Storage Foundation Installation Guide . Stop the volume and remove it from VERITAS Volume Manager using the following commands: # vxvol -g diskgroup -f stop volume_name # vxedit -g diskgroup -rf rm volume_name 10. If the volume is being used as a raw partition for database applications. Subsequent volumes can use the free space generated by the removal of this volume.Moving Volumes To Disk Partitions 2. 7. Mount the disk partition if the corresponding volume was previously mounted. Remove the evacuated disks from VERITAS Volume Manager control using the following commands: # vxdg -g diskgroup rmdisk disk _media_name # vxdisk rm disk_access_name 3. To check if there are still some subdisks remaining on a particular disk. If the volume to be moved is mounted. 5. Decide which volume to move first. unmount it. 4. there are still some subdisks on this disk that must be subsequently removed. 8. Create a partition on free disk space of the same size as the volume. a new disk must be added to the system for the first volume removed. Copy the data on the volume onto the newly created disk partition using a command similar to the following: # dd if=/dev/vx/dsk/diskgroup/lhome of=/dev/sdb2 where sdb is the disk outside of VERITAS Volume Manager and 2 is the newly created partition on that disk. If the output is not 0. Replace the entry for that volume (if present) in /etc/fstab with an entry for the newly created partition. 6. Remove any disks that have become free (have no subdisks defined on them) by removing volumes from VERITAS Volume Manager control.

Uninstalling VERITAS Infrastructure Packages There are several packages./uninstallinfr The uninstallinfr script removes the remaining packages that are required for product installation. use the following commands: # cd /opt/VRTS/install # . Removing Storage Foundation Packages To shut down and remove the installed VERITAS Storage Foundation packages. VRTSob and VRTSobgui. After the reboot. configure ssh or rsh as described in “Prerequisites for Remote and Cluster Installation” on page 4. none of the volumes should be open. are also removed. If you remove all VERITAS products from a system and want to ensure that there are no remaining VERITAS packages./uninstallsf You can use this procedure to remove the packages from one or more systems. These packages are not removed when uninstalling a single VERITAS product. The VERITAS Enterprise Administrator packages. that are used by multiple VERITAS products. repeat the steps listed above. reboot the system. referred to as infrastructure packages. Note To remove packages from remote systems. 13. use the following commands: # cd /opt/VRTS/install # . Not all these packages may be installed on your system depending on the choices that you made when you installed VxVM. Uninstalling VERITAS Storage Foundation 55 .Removing Storage Foundation Packages 12. To verify that none of the volumes are open. Chapter 5. After all volumes have been converted into disk partitions successfully. If any volumes remain open. use the following command: # vxprint -Aht -e v_open 14. You may also choose to remove the VRTSvlic licensing package unless this is required by other VERITAS software. The free space now created can be used for adding the data in the next volume to be removed.

Select Start > Settings > Control Panel. Log in as administrator. and click the Remove button. 5. Select VERITAS Enterprise Administrator from the list. 2.Removing the VEA Client from a Microsoft Windows System Removing the VEA Client from a Microsoft Windows System To remove the VEA client from a Windows system. uninstall the package as follows: 1. Double-click Add/Remove Programs to display a list of installed products. 56 VERITAS Storage Foundation Installation Guide . 3. 4. Click Yes when a dialog box appears asking you to confirm the removal.

Sign up to vote on this title
UsefulNot useful