veritas storage foundation 4.1 installation...

N17447H

August 2005

VERITAS Storage Foundation™ 4.1

Installation Guide

Linux

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 © 2005 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS Logo, VERITAS Storage Foundation, FlashSnap and QuickLog are trademarks or registered trademarks of VERITAS Software Corporation or its affiliates in the U.S. and other countries. Other names may betrademarks of their respective owners.

VERITAS Software Corporation350 Ellis StreetMountain View, CA 94043 USAPhone 650–527–8000 Fax 650–527–2908www.veritas.com

Third-Party Legal Notices

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

http://www.veritas.com

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

How This Guide Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1. Preinstallation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

VERITAS Storage Foundation Product Suites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Preinstallation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Supported Linux Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Supported DB2 Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Required Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Package Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Required Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

System Disk Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Remote and Cluster Installation and Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Persistent Network Interface Names on SUSE Clusters . . . . . . . . . . . . . . . . . . . . . . . . . 10

VERITAS Product Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Component Product Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

VERITAS Licensing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Accessing Storage Foundation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Accessing Manual Pages and Documentation Directories . . . . . . . . . . . . . . . . . . . . . . . 13

iii

Chapter 2. Installing the VERITAS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Mapping Services and Performance Statistics for DB2 . . . . . . . . . . . . . . . . . . . . . . . 15

Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Installing the Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Configuring Storage Foundation on a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Completing the Installation Procedure in an HA Environment . . . . . . . . . . . . . . . . 23

Verifying the VERITAS Storage Foundation Installation . . . . . . . . . . . . . . . . . . . . . . . . 26

Checking Volume Manager Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Checking Cluster Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Verifying the Low Latency Transport (LLT) Configuration . . . . . . . . . . . . . . . . 28

Verifying LLT Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Verifying Group Membership and Atomic Broadcast (GAB) Configuration . . 29

Verifying GAB Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

VERITAS Enterprise Administrator (VEA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Installing the VEA Client on a Microsoft Windows System . . . . . . . . . . . . . . . . . . . 30

Starting and Stopping the VEA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Using the VEA Client to Administer Local and Remote Systems . . . . . . . . . . . . . . 32

Configuring VERITAS Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Disabling Hot-Relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Enabling Intelligent Storage Provisioning (ISP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Loading and Unloading the File System Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Configuring VERITAS Storage Foundation for DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Setting Administrative Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

VERITAS Enterprise Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Adding Users to the VEA Service Console Registry for DB2 . . . . . . . . . . . . . . . 35

Removing Users from the VEA Service Console Registry for DB2 . . . . . . . . . . 36

iv VERITAS Storage Foundation Installation Guide

Chapter 3. Upgrading VERITAS Storage Foundation and Linux . . . . . . . . . . . . . . . .39

Previously Supported Installations on Red Hat Linux . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Previously Supported Installations on SUSE Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Upgrading the VERITAS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Red Hat Upgrade Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

SUSE Upgrade Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Upgrading the VERITAS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Upgrading the Linux Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Upgrading VxFS Disk Layout Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

When to Upgrade Disk Layout Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

When to Use vxfsconvert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

When to Use vxupgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Requirements for Upgrading to Disk Layout Version 6 . . . . . . . . . . . . . . . . . . . . . . . 49

Upgrading VxVM Disk Group Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Upgrading the VEA Client on a Microsoft Windows System . . . . . . . . . . . . . . . . . . . . . 50

Chapter 4. Uninstalling VERITAS Storage Foundation . . . . . . . . . . . . . . . . . . . . . . .51

Shutting Down Cluster Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Removing Rootability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Removing VxFS File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Moving Volumes To Disk Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Moving Volumes onto Disk Partitions Using VxVM . . . . . . . . . . . . . . . . . . . . . . . . . 54

Uninstalling VERITAS Storage Foundation Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Uninstalling VERITAS Infrastructure Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Removing License Files (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Removing the VEA Client from a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Contents v

vi VERITAS Storage Foundation Installation Guide

Preface

This document provides information on installing and initializing a VERITAS Storage Foundation™ 4.1 product. VERITAS Storage Foundation is comprised of VERITAS File System (VxFS), VERITAS Volume Manager (VxVM), and the VERITAS Enterprise Administrator (VEA) graphical user interface. Storage Foundation for DB2 contains all elements of Storage Foundation, plus DB2-specific enhancements.

Follow the instructions in this guide if you are installing one of the following products:

◆ VERITAS Storage Foundation (QuickStart, Standard, Enterprise, Enterprise HA Editions)

◆ VERITAS Storage Foundation for DB2 (Standard, Enterprise, Enterprise HA Editions)

Note If you are installing VERITAS Volume Replicator, see the VERITAS Volume Replicator Installation Guide on the product disc. The VERITAS Volume Replicator Installation Guide explains how to install the product and directs you to the VERITAS Volume Replicator documentation.

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

6 July 2005, 4:16pm vii

How This Guide Is Organized

How This Guide Is Organized This guide describes how to install or remove the packages associated with the Storage Foundation product you have purchased. If you have a previous release of the VERITAS software already installed on your systems, you can upgrade to the VERITAS Storage Foundation 4.1 software by recording the details of your existing installation, and then installing the required operating system and VERITAS software.

See the VERITAS Storage Foundation Release Notes for late-breaking information related to product installation.

Note Most VxVM and VxFS commands require superuser (root) or other appropriate privileges.

This guide is organized with the following chapters:

◆ Chapter 1. “Preinstallation Instructions” on page 1

◆ Chapter 2. “Installing the VERITAS Software” on page 15

◆ Chapter 3. “Upgrading VERITAS Storage Foundation and Linux” on page 39

◆ Chapter 4. “Uninstalling VERITAS Storage Foundation” on page 51

Conventions

Convention Usage Example

monospace Used for path names, commands, output, directory and file names, functions, and parameters.

Read tunables from the /etc/vx/tunefstab file.

See the ls(1) manual page for more information.

monospace (bold)

Indicates user input. # ls pubs

italic Identifies book titles, new terms, emphasized text, and variables replaced with a name or value.

See the User’s Guide for details.

The variable system_name indicates the system on which to enter the command.

bold Depicts GUI objects, such as fields, list boxes, menu selections, etc. Also depicts GUI commands.

Enter your password in the Password field.

Press Return.

viii VERITAS Storage Foundation Installation Guide

Getting Help

Convention Usage Example

blue text Indicates hypertext links. See “Getting Help” on page ix.

# UNIX superuser prompt (all shells).

# cp /pubs/4.0/user_book /release_mgnt/4.0/archive

db2 => DB2 command processor prompt

db2 => list database directory

\ Continued input on the following line; you do not type this character

# mkfs -t vxfs -o largefiles \ /dev/vx/rdsk/PRODdg/db01

Getting Help

For technical assistance, visit http://support.veritas.com and select phone or email support. This site also provides access to resources such as TechNotes, product alerts, software downloads, hardware compatibility lists, and the VERITAS customer email notification service. Use the Knowledge Base Search feature to access additional product information, including current and past releases of product documentation.

Diagnostic tools are also available to assist in troubleshooting problems associated with the product. These tools are available on disc or can be downloaded from the VERITAS FTP site. See the README.VRTSspt file in the /support directory for details.

For license information, software updates and sales contacts, visit https://my.veritas.com/productcenter/ContactVeritas.jsp. For information on purchasing product documentation, visit http://webstore.veritas.com.

Documentation Feedback Your feedback on product documentation is important to us. Send suggestions for improvements and reports on errors or omissions to [email protected] or [email protected]. Include the title and part number of the document (located in the lower left corner of the title page), and chapter and section titles of the text on which you are reporting. Our goal is to ensure customer satisfaction by providing effective, quality documentation. For assistance with topics other than documentation, visit http://support.veritas.com.

Preface ix

http://support.veritas.com

https://my.veritas.com/productcenter/ContactVeritas.jsp

http://webstore.veritas.com

mailto:[email protected]

mailto:[email protected]

http://support.veritas.com

Documentation Feedback

x VERITAS Storage Foundation Installation Guide

Preinstallation Instructions
1 Follow the preinstallation instructions outlined in this chapter if you are installing one of the following VERITAS Storage Foundation products:
◆ VERITAS Storage Foundation (QuickStart, Standard, Enterprise, Enterprise HA Editions)

◆ VERITAS Storage Foundation for DB2 (Standard, Enterprise, Enterprise HA Editions)

Note If you are installing VERITAS Volume Replicator, see the VERITAS Volume Replicator Installation Guide on the product disc. The VERITAS Volume Replicator Installation Guide explains how to install the product and directs you to the VERITAS Volume Replicator documentation.

The following topics are covered in this chapter:

◆ “VERITAS Storage Foundation Product Suites” on page 2

◆ “Preinstallation Instructions” on page 4

◆ “System Requirements” on page 5

◆ “Remote and Cluster Installation and Uninstallation” on page 10

◆ “VERITAS Product Licensing” on page 11

◆ “Accessing Storage Foundation Commands” on page 12

◆ “Accessing Manual Pages and Documentation Directories” on page 13

Review the information in these sections and make appropriate changes before you install VERITAS Storage Foundation or VERITAS Storage Foundation for DB2.

1

VERITAS Storage Foundation Product Suites

VERITAS Storage Foundation Product Suites There are multiple software discs in the VERITAS product distribution. The VERITAS software discs have an automated installation and licensing procedure that lets you install packages using the VERITAS product installer instead of installing from the command line. The Getting Started Guide, included with the VERITAS software discs, provides complete information on using the product installer. Review the Getting Started Guide before installing any of the Storage Foundation products.

The following table lists the VERITAS products and optionally licensed features available with each Storage Foundation product suite.

Storage Foundation Version Products and Features

Storage Foundation QuickStart

Storage Foundation Standard

Storage Foundation Standard HA

Storage Foundation Enterprise

VERITAS File System (Base feature set) VERITAS Volume Manager (Base feature set)

VERITAS File System VERITAS Volume Manager

Optionally licensed features:

VERITAS Volume Replicator

VERITAS File System VERITAS Volume Manager VERITAS Cluster Server


VERITAS Cluster Volume Manager VERITAS Volume Replicator

VERITAS File System VERITAS Volume Manager VERITAS FlashSnap Option



2 VERITAS Storage Foundation Installation Guide

VERITAS Storage Foundation Product Suites

Storage Foundation Version Products and Features

Storage Foundation Enterprise HA VERITAS File System VERITAS Volume Manager VERITAS Cluster Server VERITAS FlashSnap Option



Storage Foundation for DB2 Standard VERITAS File System

Storage Foundation for DB2 Enterprise

Storage Foundation for DB2 Enterprise HA

VERITAS Volume Manager VERITAS Quick I/O option



VERITAS File SystemVERITAS Volume ManagerVERITAS FlashSnap OptionVERITAS Quick I/O optionVERITAS Storage Checkpoint optionVERITAS Storage Mapping option



VERITAS File SystemVERITAS Volume ManagerVERITAS Cluster ServerVERITAS FlashSnap OptionVERITAS Quick I/O optionVERITAS Storage Checkpoint optionVERITAS Storage Mapping option



Chapter 1, Preinstallation Instructions 3

Preinstallation Instructions

Preinstallation Instructions Review the following items and make any appropriate changes before you install the VERITAS Storage Foundation software:

◆ Review the VERITAS Storage Foundation Release Notes, sf_notes.pdf located on the VERITAS software disc under the storage_foundation/release_notes directory.

Because product release notes and installation guides are not installed by any packages, VERITAS recommends that you copy them from the software disc to the /opt/VRTS/docs directory so that they are available for future reference.

◆ The VRTSspt package provides a group of tools for troubleshooting a system and collecting information on its configuration. 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. The tools are not required for operation of any VERITAS product, and they may adversely impact system performance if not used correctly. VERITAS provides these tools to analyze systems if you suspect that there are performance problems, and should be used only under the direction of a VERITAS Technical Support Engineer.

◆ To enable Storage Foundation features, obtain a license key as described in “VERITAS Product Licensing” on page 11. You will be asked to enter your license keys during the installation process.


System Requirements

System Requirements

Supported Linux Operating Systems The VERITAS 4.1 release operates on the following operating systems and hardware:

◆ Red Hat Enterprise Linux 4 (RHEL 4) Update 1 (2.6.9-11 kernels)

x86 (32-bit), Xeon (32-bit, 64-bit), Opteron (32-bit, 64-bit), IA64

◆ SUSE Linux Enterprise Server 9 (SLES 9) with SP1 (2.6.5-7.139 and 2.6.5-7.145 kernels)

x86, x86-64 (32-bit and 64-bit modes), IA64

Note 32-bit Storage Foundation Cluster File System (SFCFS) and Storage Foundation for Oracle RAC (SFRAC) are not currently supported on the Red Hat and SUSE distributions.

Read the following VERITAS Technical Support TechNote for the latest information on updates, patches, and software issues regarding this release:

http://support.veritas.com/docs/277033

Supported DB2 Versions DB2 8.2, also referred to as DB2 8.1 with FixPak 7, or later is supported on the Linux operating systems listed in “Supported Linux Operating Systems” on page 5.


http://support.veritas.com/docs/277033

System Requirements

Required Disk Space Before installing any of the VERITAS Storage Foundation products, confirm that your system has enough free disk space. Use the “Perform a Preinstallation Check” (P) option of the product installer to determine whether there is sufficient space.

The following table shows the approximate disk space used by the Storage Foundation products for all (both the required and optional) packages:

Storage Storage Storage Storage Foundation Foundation Foundation for Foundation for QuickStart, Standard HA or DB2 Standard or DB2 Standard HA Standard or Enterprise HA Enterprise or Enterprise HA Enterprise

Minimum Space Required (Without Optional Packages)

155MB 310MB 210MB 370MB

Maximum Space Required (Including All Packages)

275MB 465MB 335MB 525MB


System Requirements

Package Information The VERITAS software discs contains the following Storage Foundation packages:

Package Contents

Volume Manager Packages

VRTSvxvm-common VERITAS Volume Manager common files

VRTSvxvm-platform VERITAS Volume Manager platform-specific files

VRTSvmpro VERITAS Volume Manager Provider

VRTSalloc VERITAS Intelligent Storage Provisioning (ISP) feature (optional)

VRTSlvmconv VERITAS Linux LVM to VxVM Converter (optional)

VRTSvmdoc VERITAS Volume Manager online guides (optional)

VRTSvmman VERITAS Volume Manager manual pages (optional)

File System Packages

VRTSvxfs-common VERITAS File System common files

VRTSvxfs-platform VERITAS File System platform-specific files

VRTSfspro VERITAS File System Provider

VRTSfssdk VERITAS File System Software Developer Kit (optional

VRTSfsmnd VERITAS File System Software Developer Kit Manual Pages and Online Guides (optional)

VRTSfsdoc VERITAS File System online guides (optional)

VRTSfsman VERITAS File System manual pages (optional)

Database Packages

VRTSdb2ed-common VERITAS Storage Foundation for DB2 common files

VRTSd2gui-common VERITAS Storage Foundation for DB2 Graphical User Interface


System Requirements

Package Contents

VRTSvxmsa VERITAS Federated Mapping Service, Application Libraries

VRTSdbdoc VERITAS Storage Foundation Documentation for Databases (optional)

VERITAS Enterprise Administrator Packages

VRTSob VERITAS Enterprise Administrator Service

VRTSobgui VERITAS Enterprise Administrator (required for VEA client)

Infrastructure Packages

VRTSddlpr VERITAS Device Discovery Layer Services Provider

VRTSvail VERITAS Array Providers (VERITAS Array Integration Layer)

VRTSap VERITAS Action Provider (optional)

Note VRTSap is the rules engine add-on for the VERITAS Enterprise Administrator GUI. Installing VRTSap enables SNMP trap and email

VRTStep VERITAS Task Execution Provider (optional)

Note VRTStep provides the command execution add-on for the VERITAS Enterprise Administrator GUI. Installing VRTStep and VRTSap enables command execution in response to an alert.

High Availability (VERITAS Cluster Server) Packages

VRTSat VERITAS Authentication Service

VRTScscm VERITAS Cluster Server Cluster Manager

VRTScscw VERITAS Cluster Server Configuration Wizards

VRTScssim VERITAS Cluster Server Simulator

VRTScutil VERITAS Cluster Utility

VRTSgab VERITAS Group Membership and Atomic Broadcast

VRTSjre VERITAS Java Runtime Environment Redistribution


System Requirements

Package Contents

VRTSllt VERITAS Low Latency Transport

VRTSvcs VERITAS Cluster Server

VRTSvcsag VERITAS Cluster Server Bundled Agents

VRTSvcsmg VERITAS Cluster Server Message Catalogs

VRTSvcsw VERITAS Cluster Server (Web Console)

VRTSvxfen VERITAS I/O Fencing

VRTSweb VERITAS Java Web Server

VRTSvcsdc VERITAS Cluster Server Documentation (optional)

VRTSvcsmn VERITAS Cluster Server Manual Pages (optional)

Other Packages

VRTSvlic VERITAS licensing utilities

VRTSperl PERL language

VRTScpi VERITAS Cross Product Installation (CPI) utilities

windows/vrtsobgui.msi VERITAS Enterprise Administrator for Windows

Volume Replicator Packages (if you purchased the VERITAS Volume Replicator option)

VRTSvrpro VERITAS Volume Replicator Management Services Provider (required for VVR; requires VRTSvmpro

VRTSvcsvr VERITAS Cluster Server Agents for VERITAS Volume Replicator (optional)

VRTSvrw VERITAS Volume Replicator Web Console (optional)

VRTSvrdoc VERITAS Volume Replicator documentation (optional)


Remote and Cluster Installation and Uninstallation

Required Memory A minimum of 512 MB of memory is required.

System Disk Check Before installing VERITAS Storage Foundation, 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. Correct any problems before you install the Storage Foundation software.

Remote and Cluster Installation and Uninstallation Establishing communication between nodes is required to install VERITAS software from a remote system, or to install and configure a cluster. 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. Remote shell utilities on Linux are disabled by default. See “Configuring SSH or RSH Before Installing VERITAS Products” in the Getting Started Guide for more information.

Persistent Network Interface Names on SUSE Clusters On SUSE systems, network interfaces can change their names following a reboot. To configure persistent network interface names, add a PERSISTENT_NAME=ethX entry to the /etc/sysconfig/network/ifcfg-eth-id-mac_address network interface configuration file for each interface on each node of the cluster, where X and mac_address correspond to the interface number and MAC address.


VERITAS Product Licensing

VERITAS Product Licensing You must obtain new licenses to use all of the features in VERITAS Storage Foundation 4.1 or VERITAS Storage Foundation 4.1 for DB2. Any VERITAS licenses for previous releases that are currently installed will allow you to use only a limited subset of these features.

Product keys are available on the License Key certificate. The certificate also includes the number of product licenses purchased. A single key enables product installation on the number and the type of systems for which you purchased the license. A key may enable the operation of more products than specified on the certificate, but you are legally limited to the number of product licenses purchased.

If you encounter problems while licensing your product, visit the VERITAS licensing support website at http://www.veritas.com/buy/vLicense/vLicenseHome.jhtml.

Component Product Licensing A Storage Foundation QuickStart key licenses VxVM Base and VxFS Base.

A Storage Foundation Standard key licenses VxVM and VxFS.

A Storage Foundation Standard HA keys licenses VxVM, VxFS, and VCS.

A Storage Foundation Enterprise key licenses VxFS, VxVM, VERITAS FlashSnap, FlashSnap Agent for Symmetrix, and Quality of Storage Service.

A Storage Foundation Enterprise HA key license VxFS, VxVM, VCS, VERITAS FlashSnap, FlashSnap Agent for Symmetrix, Quality of Storage Service and the Global Cluster option.

When you install using the VERITAS product installer, the following information is displayed on the Product Status Page:

◆ Products available for installation

◆ Products currently installed

◆ Products that are licensed

◆ Options for operations you can initiate

Select option L to enter the license key. You do not have to re-enter the key for other licensed products.


http://www.veritas.com/buy/vLicense/vLicenseHome.jhtml

Accessing Storage Foundation Commands

VERITAS Licensing Commands The VERITAS licensing commands are provided in the VRTSvlic package. The product installer automatically installs the VRTSvlic package. If Storage Foundation is installed manually, you must install VRTSvlic for the licensing process to work. There are three commands:

vxlicinst Licenses a VERITAS product already installed on a system.

vxlicrep Enables you to view currently installed licenses.

vxlictest Retrieves features encoded in a license key and describes them.

You can review descriptions and options for these commands in the manual pages installed with the VRTSvlic package.

Accessing Storage Foundation Commands Symbolic links to all Storage Foundation command executables are installed in the /opt/VRTS/bin directory. Add the /opt/VRTS/bin directory to your PATH environment variable to access the commands.

Note Specify /opt/VRTS/bin in your PATH after the path to the standard Linux commands. To invoke the VxFS-specific df, fsdb, ncheck, or umount commands, type the full path name: /opt/VRTS/bin/command.

Most of the commands used in the installation are in the /sbin or /usr/sbin directory. Add these directories to your PATH environment variable as shown below. For shells similar to the Bourne Shell (bash, ksh or sh), use the command:

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

For shells similar to the C Shell (csh or tcsh), use the command:

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


Accessing Manual Pages and Documentation Directories

Accessing Manual Pages and Documentation Directories Volume Manager manual pages are in the VRTSvmman package. VERITAS File System manual pages are in the VRTSfsman package. VERITAS Storage Foundation for DB2 manual pages are in the VRTSdb2ed package. Manual pages are installed in the /opt/VRTS/man directories. Set the path of your MANPATH environment variable to include /opt/VRTS/man.

If you are using a shell such as sh or bash, do the following:

$ MANPATH=$MANPATH:/opt/VRTS/man; export MANPATH

If you are using a shell such as csh or tcsh, do the following:

% setenv MANPATH ${MANPATH}:/opt/VRTS/man

On a Red Hat system, also include the 1m manual page section in the list defined by your MANSECT environment variable.

If you are using a shell such as sh or bash, do the following:

$ MANSECT=$MANSECT:1m; export MANSECT

If you are using a shell such as csh or tcsh, do the following:

% setenv MANSECT ${MANSECT}:1m

Installation of the documentation packages copies PDF files into the /opt/VRTS/docs directory.

Note If you use the man(1) command to access manual pages, set LC_ALL=C in your shell to ensure that they display correctly.


Accessing Manual Pages and Documentation Directories


Installing the VERITAS Software
2 This chapter provides an overview of the installation tasks for VERITAS Storage Foundation and VERITAS Storage Foundation for DB2 and describes how to install the packages for the first time. If you already have an earlier version of any of the VERITAS products installed, see “Upgrading VERITAS Storage Foundation and Linux” on page 39.

◆ “Installation Requirements” on page 15

◆ “Installing the Product” on page 16

◆ “Verifying the VERITAS Storage Foundation Installation” on page 26

◆ “VERITAS Enterprise Administrator (VEA)” on page 30

◆ “Configuring VERITAS Volume Manager” on page 33

◆ “Loading and Unloading the File System Module” on page 33

◆ “Configuring VERITAS Storage Foundation for DB2” on page 34

Note Only users with superuser privileges can install and initialize Storage Foundation.

Installation Requirements Review the following VERITAS software and operating system requirements before installing the product.

Mapping Services and Performance Statistics for DB2 ◆ You must install VERITAS Array Integration Layer (VAIL) and VERITAS Mapping

Services (VxMS) if you want to use deep mapping services and performance statistics for supported storage arrays.

15

Installing the Product

◆ Install the EMC Solutions Enabler (SYMCLI) before you install VAIL. If you install Solutions Enabler after you install VAIL, rescan the EMC Symmetrix arrays so that they can be discovered. For more information, see the VERITAS Storage Foundation for DB2 Administrator’s Guide.

Operating System If patches to the Linux operating system are required, the patches should be applied just prior to installing the VERITAS products. Patches may be required to resolve Linux kernel, product performance, or other issues.

The system should be in a quiescent state before adding patches.

Note See product Release Notes for last minute information on patches required for VERITAS, Linux, or DB2 (IBM).

Installing the Product The VERITAS product installer is the recommended method to license and install the product. The installer also enables you to configure or uninstall the product, verify preinstallation requirements, and view the product’s description.

At most points during an installation, you can type “b” (“back”) to return to a previous section of the installation procedure. The back feature of the installation scripts is context-sensitive, so it returns to the beginning of a grouped section of questions. If an installation procedure hangs, use Control–c to stop and exit the program. There is a short delay before the script exits.

The following sample procedure is based on the installation of a Storage Foundation for DB2 Enterprise HA cluster with two nodes: “host1” and “host2.” The nodes are Intel Xeon EM64T systems running under Red Hat Enterprise Linux 4 Update 1. If you are installing on standalone systems only, the cluster-configuration steps are unnecessary, and these are indicated. Default responses are enclosed by parentheses. Press Enter to accept defaults.

Note VERITAS Storage Foundation Enterprise HA will install similarly, without the database packages.



▼ To install a Storage Foundation product

1. Log in as superuser.

2. Insert the disc containing the VERITAS Storage Foundation and VERITAS Storage Foundation for DB2 software into the CD-ROM drive.

3. Mount the disc on a suitable mount point, for example:

# mount -o ro /dev/cdrom /mnt/cdrom

4. Move to the top-level directory on the disc:

# cd /mnt/cdrom

5. From this directory, type the following command if you are installing on the local system only, or if you are using the secure shell (SSH) utilities to install on remote systems:

# ./installer

If you are using the remote shell (RSH) utilities to install on remote systems, additionally specify the -usersh option:

# ./installer -usersh

The sample installation assumes that SSH is being used.

6. The Selection Menu appears. Enter I at the prompt to install packages, and select the product that is to be installed, for example, VERITAS Storage Foundation Enterprise HA.

7. You are prompted to enter the system names (in the following example, “host1” and “host2”) on which the software is to be installed. When prompted, press Enter to continue.

Enter the system names separated by spaces on which to installSF: host1 host2Checking OS version on host1 ............... Linux 2.6.9-6.37.smpChecking Processor Type on host1 ...........................EM64TChecking Machine Type on host1 .............................EM64TChecking Redhat Release on host1 ........................ 4AS-7.2Checking kernel release level on host1.......................6.37Verifying communication with host2 .............. ping successfulAttempting ssh -x with host2 .................. ssh -x successfulAttempting scp with host2 ........................ scp successfulChecking OS version on host2 ............... Linux 2.6.9-6.37.smpChecking Processor Type on host2 ...........................EM64TChecking Machine Type on host2 .............................EM64T

Chapter 2, Installing the VERITAS Software 17


Checking Redhat Release on host2 ........................ 4AS-7.2Checking kernel release level on host2 ......................6.37Creating log directory on host2 ............................ Done

Logs for installsf are being created in/var/tmp/installsf416173103.

Using /usr/bin/ssh -x and /usr/bin/scp to communicate with remotesystems.

Initial system check completed successfully.

Press [Enter] to continue:

8. Press Enter. The utility begins installing the infrastructure rpms.

Installing VERITAS Infrastructure rpms on host1:

Checking VRTSvlic rpm ............................. not installedChecking VRTScpi rpm .............................. not installedChecking file system space .......... required space is availableInstalling VRTSvlic 3.05 on host1 .......................... DoneInstalling VRTScpi 4.1.0.90 on host1 ....................... Done

Installing VERITAS Infrastructure rpms on host2:

Checking VRTSvlic rpm ............................. not installedChecking VRTScpi rpm .............................. not installedChecking file system space .......... required space is availableCopying VRTSvlic rpm to host2 .............................. DoneInstalling VRTSvlic 3.05 on host2 .......................... DoneCopying VRTScpi rpm to host2 ............................... DoneInstalling VRTScpi 4.1.0.90 on host2 ....................... Done

VERITAS Infrastructure rpms installed successfully.


9. Press Enter to begin license verification, and enter license keys for each system.

Checking SF license key on host1 ................... not licensed

Enter a SF license key for host1: [?]

XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX

Registering VERITAS Storage Foundation Enterprise HA key on host1

Do you want to enter another license key for host1? [y,n,q,?] (n)

Enter n if you have no further license keys to add for a system. You are then prompted to enter the keys for the next system. The following prompt is displayed when you have added licenses to all the systems. Press Enter to continue.



SF licensing completed successfully.


10. A list of optional packages is now displayed. Enter 1 or press Enter to install the standard and all optional packages. (Required packages are not listed.)

VRTSobgui VERITAS Enterprise AdministratorVRTSvmman VERITAS Volume Manager Manual PagesVRTSvmdoc VERITAS Volume Manager DocumentationVRTSlvmconv VERITAS Linux LVM to VxVM ConverterVRTSap VERITAS Action ProviderVRTStep VERITAS Task ProviderVRTSfsman VERITAS File System Manual PagesVRTSfsdoc VERITAS File System DocumentationVRTSfsmnd VERITAS File System Software Developer Kit Manual

PagesVRTSvxfen VERITAS I/O FencingVRTSdbdoc VERITAS Storage Foundation Documentation for

DatabasesVRTSvcsmn VERITAS Cluster Server Man PagesVRTSvcsApache VERITAS Cluster Server Apache AgentVRTSvcsdc VERITAS Cluster Server DocumentationVRTScssim VERITAS Cluster Server SimulatorVRTScscm VERITAS Cluster Server Cluster ManagerVRTSvrdoc VERITAS Volume Replicator DocumentationVRTSvrw VERITAS Volume Replicator Web Console

1) Install all of the optional rpms2) Install none of the optional rpms3) View rpm descriptions and select optional rpms

Select the optional rpms to be installed on all systems? [1-3,q,?] (1) 1

Note The list may differ depending on the license keys that you entered in step 9.

The utility lists the required and optional packages that are to be installed.

installsf will install the following SF rpms:VRTSperl VERITAS Perl 5.8.0 RedistributionVRTSob VERITAS Enterprise Administrator ServiceVRTSobgui VERITAS Enterprise AdministratorVRTSvxvm VERITAS Volume Manager BinariesVRTSvmman VERITAS Volume Manager Manual PagesVRTSvmdoc VERITAS Volume Manager DocumentationVRTSvmpro VERITAS Volume Manager Management Services

ProviderVRTSfspro VERITAS File System Management Services Provider



VRTSalloc VERITAS Volume Manager Intelligent StorageProvisioning

VRTSddlpr VERITAS Device Discovery Layer Services ProviderVRTSlvmconv VERITAS Linux LVM to VxVM ConverterVRTSvxfs VERITAS File SystemVRTSap VERITAS Action ProviderVRTStep VERITAS Task ProviderVRTSfppm VERITAS File Placement Policy ManagerVRTSfsman VERITAS File System Manual PagesVRTSfsdoc VERITAS File System DocumentationVRTSfsmnd VERITAS File System Software Developer Kit Manual

PagesVRTSllt VERITAS Low Latency TransportVRTSgab VERITAS Group Membership and Atomic Broadcast


Press Enter to continue listing the rpms.

...continued:VRTSvxfen VERITAS I/O FencingVRTSvcs VERITAS Cluster ServerVRTSvcsmg VERITAS Cluster Server Message CatalogsVRTSvcsag VERITAS Cluster Server Bundled AgentsVRTSvcsmn VERITAS Cluster Server Man PagesVRTSvcsApache VERITAS Cluster Server Apache AgentVRTSvcsdc VERITAS Cluster Server DocumentationVRTScspro VERITAS Cluster Server VEA ProviderVRTSjre VERITAS Java Runtime Environment RedistributionVRTScssim VERITAS Cluster Server SimulatorVRTScscw VERITAS Cluster Server Configuration WizardsVRTSweb VERITAS Java Web ServerVRTSvcsw VERITAS Cluster Manager (Web Console)VRTScscm VERITAS Cluster Server Cluster ManagerVRTScutil VERITAS Cluster UtilitiesVRTSvrdoc VERITAS Volume Replicator DocumentationVRTSvrw VERITAS Volume Replicator Web ConsoleVRTSdbdoc VERITAS Storage Foundation Documentation for

DatabasesVRTSdb2edcommon VERITAS Storage Foundation for DB2VRTSd2guicommon VERITAS Storage Foundation Graphical User

Interface for DB2VRTSvxmsa VERITAS Mapping Service, Application Libraries




11. Press Enter. The installation utility begins checking the installation requirements for each of the nodes.

Checking system installation requirements:

Checking SF installation requirements on host1:

Checking VRTSperl rpm ............................. not installedChecking VRTSob rpm ............................... not installedChecking VRTSobgui rpm ............................ not installed...Checking SF installation requirements on host2:

Checking VRTSperl rpm ............................. not installedChecking VRTSob rpm ............................... not installedChecking VRTSobgui rpm ............................ not installed...

Installation requirement checks completed successfully.


12. If you are installing on a cluster, proceed to “Configuring Storage Foundation on a Cluster” on page 21 to configure Storage Foundation Enterprise HA. Otherwise, skip to “Completing the Installation Procedure in an HA Environment” on page 23.

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.

As the installation and configuration procedure continues, a message displays notifying you that configuring the Storage Foundation product at this point in the installation procedure is optional.

▼ To configure Storage Foundation on a cluster

1. At the following prompt, enter y or press Enter to configure Storage Foundation.

Are you ready to configure SF? [y,n,q] (y) y

A message is displayed describing how to configure Storage Foundation using the product installer.



2. Press Enter to continue. A message is displayed describing the VERITAS Cluster Server (VCS) configuration requirements.

3. You are then prompted to enter information about the cluster’s private network. Sample entries and output are based on the two-node cluster comprising “host1” and “host2.” The redundant private network is configured over the network interfaces “eth1” and “eth2,” and the public network connected via “eth0” is not used as a low priority heartbeat link.

Enter the unique cluster name: [?] tantanEnter the unique Cluster ID number between 0-255: [b,?] 199

Discovering NICs on host1 ............. discovered eth0 eth1 eth2

Enter the NIC for the first private heartbeat link on host1: [b,?] eth1

eth1 is currently active as a public NIC on host1Are you sure you want to use eth1 for the first private heartbeat link? [y,n,q,b,?] (n) y

Would you like to configure a second private heartbeat link? [y,n,q,b,?] (y) y

Enter the NIC for the second private heartbeat link on host1: [b,?] eth2

eth2 is currently active as a public NIC on host1

Are you sure you want to use eth2 for the second private heartbeat link? [y,n,q,b,?] (n) y

Do you want to configure an additional low priority heartbeat link? [y,n,q,b,?] (n) n

Are you using the same NICs for private heartbeat links on allsystems? [y,n,q,b,?] (y) y

4. The utility begins to verify the cluster information. When prompted, enter y to confirm the information is correct. If the information displayed is not correct, enter n to re-enter the information.

Cluster information verification:

Cluster Name: tantanCluster ID Number: 199Private Heartbeat NICs for host1: link1=eth1 link2=eth2Private Heartbeat NICs for host1: link1=eth1 link2=eth2

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



5. A message displays notifying you of the information required to add VCS users. To add a password for the Administrator, enter y at the prompt and change the password.

6. To add a VCS user, enter y at the prompt, and enter a user name, password and privilege level for each user.

7. The utility begins to verify the VCS user information. When prompted, enter y to confirm the information is correct.

8. A message displays notifying you of the configuration requirements for Cluster Manager (the VCS graphical user interface). To configure this feature, enter y at the prompt, and then enter the details of the public NIC, virtual IP address and network mask to be used by Cluster Manager.

9. A message displays notifying you of the configuration requirements for SMTP. To configure this feature, enter y at the prompt, and then enter the details of the SMTP server’s host name, email addresses of recipients, and the minimum security level of messages to be sent to each recipient.

10. A message displays notifying you of the configuration requirements for SNMP. To configure this feature, enter y at the prompt, and then enter the details of the systems’ names of the SNMP consoles that are to receive VCS trap messages, SNMP daemon port numbers for each console, and the minimum security level of messages to be sent to each console.

11. Proceed to “Completing the Installation Procedure in an HA Environment” on page 23.

Completing the Installation Procedure in an HA Environment At this point in the installation and configuration procedure, the installation utility begins to install the various packages on one node and copy them to any other specified nodes. The following sample output is for a Storage Foundation Enterprise HA.

▼ To complete installing and configuring Storage Foundation

1. As the installation continues, you are prompted to choose whether to install on all systems simultaneously. Enter y or press Enter to accept simultaneous installation.

Would you like to install Storage Foundation HA on all systemssimultaneously? [y,n,q,?] (y) y

Installing Storage Foundation Enterprise HA 4.1 on all systemssimultaneously:



Copying VRTSperl rpm to host2 ............... Done 1 of 102 stepsInstalling VRTSperl 4.1 on host1 ............ Done 2 of 102 stepsInstalling VRTSperl 4.1 on host2 ............ Done 3 of 102 stepsCopying VRTSob rpm to host2 ................. Done 4 of 102 stepsInstalling VRTSob 3.2.535 on host1 .......... Done 5 of 102 stepsInstalling VRTSob 3.2.535 on host2........... Done 6 of 102 steps..

Depending on the number of packages, the installation may take several minutes. Progress is indicated by the number of steps performed out of the total.

2. A message displays notifying you of successful installation. Press Enter to continue.

Storage Foundation Enterprise HA installation compeleted successfully.


3. A message displays describing the VxVM enclosure-based naming scheme and showing which nodes are eligible. If desired, you can use the vxdiskadm command or the VERITAS Enterprise Administrator to configure this feature after installation. See the vxdiskadm(1M) manual page and the “Administering Disks” chapter of the VERITAS Volume Manager Administrator’s Guide for more information.

4. If you are installing an HA version of the product, a message displays indicating the VCS configuration files are being created and copied. Press Enter to continue.

5. A message displays indicating on which systems VxVM can be started, and the status after attempting to start VxVM on those system.

Evaluating which systems can now be started...

System host1 is eligible -- can be started.System host2 is eligible -- can be started.

Preparing to start VxVM on target systems...

Begin initial start of VxVM on system host1Disabling enclosure-based naming ......................... DoneStarting vxconfigd for VxVM ......................... Succeeded

Done with initial start of VxVM on system host1

Begin initial start of VxVM on system host2Disabling enclosure-based naming ......................... DoneStarting vxconfigd for VxVM ......................... Succeeded

Done with initial start of VxVM on system host2

Done with starting VxVM on target systems...




6. Press Enter to continue. If you are installing an HA version of the product, a message displays notifying you that Cluster Server is starting. This message also contains information about configuring a default disk group.

Starting Cluster Server:

Starting LLT on host1 ................................... StartedStarting LLT on host2 ................................... StartedStarting GAB on host1 ................................... StartedStarting GAB on host2 ................................... StartedStarting Cluster Server on host1 ........................ StartedStarting Cluster Server on host2 ........................ StartedConfirming Cluster Server startup ............. 2 systems RUNNING

7. You are now given the option of specifying the default disk group name. This name will be assumed by VERITAS Volume Manager commands if you do not explicitly specify a disk group.

Many Volume Manager commands affect the contents or configuration of a disk group. Such commands require that the user specify adisk group. This is accomplished by using the -g option of a command or setting the VXVM_DEFAULTDG environment variable. Analternative to these two methods is to configure the default disk group of a system.

Evaluating which systems can now have their default disk groupconfigured...

System host1 is eligible -- can configure the default diskgroup.System host2 is eligible -- can configure the default diskgroup.

Do you want to set up the default disk group for each system? [y,n,q,?] (y) y

You can set the name of the default disk group after installation by running the vxdctl defaultdg diskgroup command on a system. 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.

Note If you specify the name of a default disk group, this step does not create the disk group. After installation, you can use menu item 1 in the vxdiskadm command or the VERITAS Enterprise Administrator to create the disk group.

8. Finally, a message displays indicating that the installation utility is preparing to start the daemons on the target systems.

Preparing to start daemons on target systems...

Starting vxrelocd on host1 .............................. Success


Verifying the VERITAS Storage Foundation Installation

Starting vxcached on host1 .............................. SuccessStarting vxconfigbackupd on host1 ....................... Success

Starting vxrelocd on host2 .............................. SuccessStarting vxcached on host2 .............................. SuccessStarting vxconfigbackupd on host2 ....................... Success

Storage Foundation Enterprise HA was started successfully.


Press Enter. A message displays notifying you of a successful installation and the locations of the /VRTS/install files.

The installation summary is saved at:

/opt/VRTS/install/logs/installsf416172204.summary

The installsf log is saved at:

/opt/VRTS/install/logs/installsf416172204.log

The installation response file is saved at:

/opt/VRTS/install/logs/installsf416172204.response

It is recommended that you retain the log files in case it becomes necessary to debug the installation.

Verifying the VERITAS Storage Foundation Installation After installation is complete, you can perform the following checks to verify that the systems are operating correctly:

◆ “Checking Volume Manager Processes” on page 26

◆ “Checking Cluster Operation” on page 27

Checking Volume Manager Processes After the Storage Foundation software has been successfully installed, you can confirm that key Volume Manager processes (vxconfigd, vxnotify, 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 ? 00:00:00 vxiod143 ? 00:00:00 vxiod



.

.

.150 ? 00:00:00 vxiod151 ? 00:00:00 vxiod159 ? 00:01:12 vxconfigd405 ? 00:00:00 vxrelocd410 ? 00:00:00 vxnotify411 ? 00:00:00 vxrelocd

Note If you have disabled hot-relocation, 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.

To verify that the cluster is operating, type the following command on any node:

# hastatus -summary

-- SYSTEM STATE -- System State Frozen

A host1 RUNNING 0 A host2 RUNNING 0

If the state of all nodes is RUNNING, VCS is successfully installed and running. Refer to the hastatus(1M) manual page and the VERITAS Cluster Server User’s Guide for more information on system states and state transitions.

To display the VCS attribute values for each node in the cluster, 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.



Verifying the Low Latency Transport (LLT) Configuration

After installation, the /etc/llthosts and /etc/llttab files contain information about LLT configuration.

◆ /etc/llthosts

The llthosts file is a database containing one entry per node that links the LLT system ID (in the first column) with the LLT host name. This file is identical on each cluster node.

Based on the sample installation, the /etc/llthosts contains the entries:

0 host11 host2

See the llthosts(4) manual page for more information.

◆ /etc/llttab

The llttab file contains information derived from the installation, and is used by the lltconfig utility. After installation, this file lists the network links that correspond to each node.

The first line identifies the node. The second line identifies the cluster, based on the cluster ID entered during installation. The next two lines, beginning with the link command, identify the two network cards used by the LLT protocol.

See the llttab(4) manual page for details on how to modify the LLT configuration. The manual page describes ordering the directives in the llttab file.

Verifying LLT Operation

Use the lltstat command to verify that links are active for LLT. This command returns information about the links for LLT for the node on which it is typed.

With LLT configured correctly, the output of lltstat -n shows all of the nodes in the cluster and two links for each node. If the output shows otherwise, enter the following command on any node to view additional information about LLT:

# lltstat -nvv | more

For information on ports open for LLT, enter the following command on any node.

# lltstat -p



Verifying Group Membership and Atomic Broadcast (GAB) Configuration

After installation, the /etc/gabtab file contains a gabconfig(1M) command line to configure the GAB driver. The following shows the format of an entry in this file:

/sbin/gabconfig -c -nN

The -c option configures the driver and -nN specifies the cluster will not be formed until at least N nodes are ready. The variable N represents the number of cluster nodes.

Verifying GAB Operation

To verify that GAB is operating, type the following command on each node:

# /sbin/gabconfig -a

If GAB is operating, GAB port membership information is returned:

GAB Port Memberships===================================Port a gen a36e0003 membership 01Port h gen fd570002 membership 01

Port a indicates that GAB is communicating, gen a36e0003 is a random generation number, and membership 01 indicates that nodes 0 and 1 are connected.

Port h indicates that VCS is started, gen fd570002 is a random generation number, and membership 01 indicates that nodes 0 and 1 are both running VCS.

If GAB is not operating, no GAB port membership information is returned.

If only one network is connected, the following GAB port membership information is returned:

GAB Port Memberships===================================Port a gen a36e0003 membership 01Port a gen a36e0003 jeopardy 1Port h gen fd570002 membership 01Port h gen fd570002 jeopardy 1

For more information on GAB, including descriptions of ports, refer to the VERITAS Cluster Server User’s Guide.


VERITAS Enterprise Administrator (VEA)

VERITAS Enterprise Administrator (VEA) The VERITAS Enterprise Administrator (VEA) is the graphical administrative interface for configuring shared storage devices. VEA simplifies administrative tasks, such as mounting and unmounting file systems, creating and removing storage checkpoints, enabling and disabling change log, and many others. For basic information on running the VEA, refer to VERITAS Enterprise Administrator (VEA 500 Series) Getting Started. For a complete list of administrative tasks and their instructions, see the online help that is available from within the VEA.

The VEA server package, VRTSob, is installed by the installation script on all nodes that are to be administered. The VRTSobgui package contains the VEA client Graphical User Interface (GUI) program, which may also be installed on one or more of these nodes, or on a separate system that can be used to administer both these and other nodes. 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.”

Note The VERITAS Enterprise Administrator (VEA) GUI client cannot operate on Intel IA64 systems because the 1.5.0_01 version of the Java Runtime Environment (JRE) is not supported on this architecture. This applies to all Red Hat or SUSE distributions supported by VERITAS Storage Foundation products. You can administer VERITAS Storage Foundation software running on IA64 systems from a VEA GUI client installed on any of the supported architectures: x86 (32-bit), Xeon (32-bit, 64-bit), Opteron (32-bit, 64-bit), or Microsoft Windows® systems.

Installing the VEA Client on a Microsoft Windows System The VEA client package (\windows\VRTSobgui.msi) for Windows systems may be used to access servers running VERITAS Storage Foundation software and the VEA service on Linux. This package can be installed on Windows NT®, Windows 2000, Windows XP, Windows ME, Windows 98, and Windows 95 machines.

To install and run the VEA client, your system must conform to the following specifications:

◆ Windows Installer 2.0 or later must be present. For information about upgrading Windows Installer, visit http://www.microsoft.com. For Windows NT 4.0, it is also recommended that you use Windows NT 4.0 Service Pack 6.

◆ Java Runtime Environment (JRE) version 1.5.0_01.

◆ 100MHz Pentium with 256MB memory or higher specification.

◆ 22MB available disk space.


http://www.microsoft.com


Note Microsoft Installer is required to install the VRTSobgui.msi package. You can get this product from the Microsoft website if it is not already installed on your system.

Before you install VEA on a Windows system, you must uninstall any existing VERITAS Volume Manager Storage Administrator (VMSA) packages and remove the old setup.exe from that machine. Only one VEA package can be installed on a Windows machine at a time.

▼ To install the VEA GUI on a Windows system

1. Log in as administrator.

2. Insert the disc containing the VERITAS software in the CD-ROM drive

3. Using Windows Explorer or a DOS Command window, change directory to \windows\VRTSobgui.msi and execute the VRTSobgui.msi program with Windows Installer.

4. Follow the instructions presented by the VRTSobgui.msi program.

5. After installation is complete, ensure environment changes made during installation take effect as follows:

◆ For Windows NT or Windows 2000, log out and then log back in.

◆ For Windows XP, ME, Windows 98 or Windows 95, restart the computer.

Starting and Stopping the VEA Server

Note The VEA server is automatically started when you reboot your system.

To check the state of the VEA server, enter:

# /opt/VRTSob/bin/vxsvcctrl status

To start the VEA service, enter:

# /opt/VRTSob/bin/vxsvcctrl start

To stop the VEA server, enter:

# /opt/VRTSob/bin/vxsvcctrl stop



Using the VEA Client to Administer Local and Remote Systems

Users with appropriate privileges can use the VEA client to administer a local or remote machine. VERITAS Volume Manager and the VEA server must be installed, and the VxVM configuration daemon, vxconfigd, and the VEA server daemon, vxsvc, must be running on the machine to be administered.

To use the VEA client GUI provided with this release to administer VERITAS software on other platforms, you must upgrade those systems to at least the following releases:

◆ AIX requires VERITAS Storage Foundation 3.2.2 or later

◆ HP-UX requires VERITAS Volume Manager 3.5 Update 2 or later

◆ Linux requires VERITAS Storage Solutions 2.2 or later

◆ Solaris requires VERITAS Storage Foundation 3.5 MP2 or later

To use the VEA client on Linux to administer the local system, type:

# /opt/VRTSob/bin/vea

To use the VEA client on Linux to administer a remote system, type:

# /opt/VRTSob/bin/vea -host remote_system -user username \-password password

To use the VEA client on Windows to administer a remote system, select Start > Programs > VERITAS Enterprise Administrator > VERITAS Enterprise Administrator.


Configuring VERITAS Volume Manager

Configuring VERITAS Volume Manager For information on setting up VxVM disk groups and volumes after installation, see “Configuring VERITAS Volume Manager” in the VERITAS Volume Manager Administrator’s Guide.

Disabling Hot-Relocation The hot-relocation feature is enabled by default and it is recommended that you leave it on. However, you can disable it by preventing the vxrelocd daemon from starting up during system startup. This should be done after the VxVM packages have been installed.

To disable hot-relocation, comment out the vxrelocd line in the startup file /etc/init.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.

Enabling Intelligent Storage Provisioning (ISP) If you load the allocator provider package (VRTSalloc) after installation, 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; this occurs when a user tries to mount a VxFS file system.

In some instances, you may find it efficient to load the file system module manually. For example, some larger class systems can have many dual interface I/O cards with multiple disk chains attached. The device interrogation process when such a system is rebooted can be very time consuming, so to avoid doing a reboot, use the modprobe command to load the vxfs module:

# modprobe vxfs

Do not use the insmod command to load the vxfs module as insmod does not examine the module configuration file /etc/modprobe.conf.


Configuring VERITAS Storage Foundation for DB2

To determine if the modules successfully loaded, use the lsmod command as shown here:

# lsmod | grep vxportalvxportal 2952 0vxfs 3427960 0 fdd vxportal# lsmod | grep fddfdd 67212 0 (unused)vxfs 3427960 0 [fdd vxportal]# lsmod | grep vxfsvxfs 3427960 0 [fdd vxportal]

The first field in the output is the module name. You can unload the modules by entering:

# rmmod fdd# rmmod vxportal# rmmod vxfs

The rmmod command fails if there are any mounted VxFS file systems. To determine if any VxFS file systems are mounted, enter:

# df -T | grep vxfs

Configuring VERITAS Storage Foundation for DB2 After installing VERITAS Storage Foundation for DB2, configure the software as described in this section.

Setting Administrative Permissions To allow database administrators to administer a database using VERITAS Storage Foundation for DB2, you are required to change some permission settings. You are asked during the installation process if you want to allow database administrators access to various functionality. If you did not make the permission changes during installation, you can do so at a later time.

The default settings at installation time for the /opt/VRTSdb2ed directory allow only the root login to access the directory.

▼ To allow the user “db2inst1” access to the /opt/VRTSdb2ed directory

Use the chown and chmod commands as follows:

# chown db2inst1 /opt/VRTSdb2ed# chmod 500 /opt/VRTSdb2ed



▼ To allow users in the group “db2iadm1” access to the /opt/VRTSdb2ed directory

Use the chgrp and chmod commands as follows:

# chgrp db2iadm1 /opt/VRTSdb2ed# chmod 550 /opt/VRTSdb2ed

VERITAS Enterprise Administrator You may need to update VERITAS Enterprise Administrator so that users other than root can access features.

Adding Users to the VEA Service Console Registry for DB2

You may want to add database administrators (DBAs) to the VEA server console registry so they can perform tasks from the GUI. You also have the option to give database administrators root privileges.

▼ To add users other than root to the VEA Service console registry

1. Make sure that the optional GUI package was installed.

# rpm -q VRTSd2gui

The output should look similar to the following:

VRTSd2gui-common-4.1.00.A10-SLES9

2. Stop the VEA server.

# /opt/VRTS/bin/vxsvcctrl stop

3. To give root privileges to the database administrator, use the vxdb2edusr command as follows.

# /opt/VRTS/bin/vxdb2edusr -a <user or group> [-A] [-f] -n \user_name

where:

-a user adds a user to the registry

-A grants the user root access

-f allows the user to be a user other than the /opt/VRTSdb2ed owner.

-n indicates the name of the user or group.



For example, to add a database administrator with the name “db2inst1” as a user with root privileges, enter the following:

# /opt/VRTS/bin/vxdb2edusr -a user -A -f -n db2inst1

4. To add a user without root privileges, use the vxdbedusr command as follows.

# /opt/VRTS/bin/vxdbe2dusr -a user -n user_name

where -a adds a user to the registry.

For example, to add “db2inst1” as a user, enter the following:

# /opt/VRTS/bin/vxdb2edusr -a user -n db2inst1

5. To add a group to the console registry, use the vxdb2edusr command as follows:

# /opt/VRTS/bin/vxdb2edusr -a group [-A] [-f] -n group_name

where -a adds the user group to the registry.

-a group adds a group to the registry

-A grants the group root access

-f allows the group to be other than the /opt/VRTSdb2ed owner.

-n indicates the name of the user or group.

For example, to add “dba” as a group, enter the following:

# /opt/VRTS/bin/vxdb2edusr -a group -n dba

6. Restart the VEA Server.

# /opt/VRTS/bin/vxsvcctrl start

Removing Users from the VEA Service Console Registry for DB2

You may need to restrict access to the VEA server console registry. You can remove users or user groups from the registry if they have been previously added.

Note You cannot remove root from the VEA console registry.

▼ To remove users other than root from the VEA Service console registry

1. Make sure that the optional GUI package was installed.

# rpm -q VRTSd2gui

The output should look similar to the following:

VRTSd2gui-common-4.1.00.A10-SLES9



2. Stop the VEA server.

# /opt/VRTS/bin/vxsvcctrl stop

3. Use the vxdb2edusr command to remove a group or user.

# /opt/VRTS/bin/vxdb2edusr -r <user or group> \-n <user_name or group_name>

where -r removes a user or user group from the registry.

For example, to remove the user “db2inst1,” enter the following:

# /opt/VRTS/bin/vxdb2edusr -r user -n db2inst1

4. Restart the VEA Server.

# /opt/VRTS/bin/vxsvcctrl start


Upgrading VERITAS Storage Foundation and Linux
3
If you are running an earlier release of VERITAS Storage Foundation, you can upgrade to the latest version of VERITAS Storage Foundation or VERITAS Storage Foundation for DB2 using the procedures described in this chapter.

The information in “Upgrading the VERITAS Software” on page 41 pertains to VERITAS Storage Foundation and VERITAS Storage Foundation for DB2.


◆ “Previously Supported Installations on Red Hat Linux” on page 40

◆ “Previously Supported Installations on SUSE Linux” on page 40

◆ “Upgrading the VERITAS Software” on page 41

◆ “Upgrading the Linux Kernel” on page 46

◆ “Upgrading VxFS Disk Layout Versions” on page 48

◆ “Upgrading VxVM Disk Group Versions” on page 49

◆ “Upgrading the VEA Client on a Microsoft Windows System” on page 50

Note In-place upgrading of the VERITAS software is not supported. The recommended method for upgrading an existing system is by reinstallation of the operating system, and fresh installation of the VERITAS Storage Foundation software. Follow the procedure given in “Upgrading the VERITAS Software” on page 41.

If you need to upgrade your kernel with VERITAS Storage Foundation 4.1 already installed, follow the procedure given in “Upgrading the Linux Kernel” on page 46.

Only users with superuser privileges can upgrade and initialize VERITAS Storage Foundation and Linux.

39

Previously Supported Installations on Red Hat Linux

Previously Supported Installations on Red Hat Linux The following table shows the supported kernels for previous releases of VERITAS Storage Foundation on the Red Hat Linux platform:

VERITAS Product Red Hat 7.1 or Red Red Hat Advanced Red Hat Enterprise Hat 7.2 Server 2.1 Linux 3

Foundation Suite 1.0 2.4.9-12 (RH7.1) Not Supported Not Supported 2.4.7-10, 2.4.9-10 (RH7.2)

Foundation Suite 1.1 2.4.7-10 (RH7.2) 2.4.9-e.3 Not Supported

Storage Solutions 2.2 Not Supported 2.4.9-e.12 Not Supported

Storage Solutions 2.2 MP1 Not Supported Not Supported 2.4.21-4

Storage Solutions 2.2 MP2 Not Supported Not Supported 2.4.21-4, 2.4.21-12

Storage Solutions 2.2 MP3 or Not Supported Not Supported 2.4.21-12 MP5

Storage Foundation 4.0 Not Supported Not Supported 2.4.21-15

See “Supported Linux Operating Systems” on page 5 for details of the Red Hat Enterprise Linux 4 systems that are supported by the VERITAS Storage Foundation 4.1 software.

Previously Supported Installations on SUSE Linux The following table shows the supported previous releases of VERITAS software on the SUSE Linux platform:

VERITAS Product SUSE Linux Enterprise Server 8

Storage Solutions 2.2 MP2 SP2 or SP2a

Storage Solutions 2.2 MP4 or SP3 MP5


Upgrading the VERITAS Software

See “Supported Linux Operating Systems” on page 5 for details of the SUSE Linux Enterprise Server 9 systems that are supported by the VERITAS Storage Foundation 4.1 software.

Upgrading the VERITAS Software Before upgrading to VERITAS Storage Foundation or VERITAS Storage Foundation for DB2, make sure your operating system is at the supported level.

Red Hat Upgrade Information If you are upgrading your operating system from a previous version of Red Hat Advanced Server to Red Hat Enterprise Linux 4 Update 1, VERITAS strongly recommends that you install a clean version of Red Hat Enterprise Linux 4 Update 1 instead of performing an upgrade. For more information, see the following:

http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/x8664-multi-instal l-guide/ap-upgrade.html

SUSE Upgrade Information If you are upgrading your operating system from SUSE Linux Enterprise Server 8 to SUSE Linux Enterprise Server 9 SP1, VERITAS strongly recommends that you install a clean version of SUSE Linux Enterprise Server 9 SP1. However, you do have the option to upgrade the operating system. For more information, see the following:

http://support.novell.com/cgi-bin/search/searchtid.cgi?/en/2005/01/dcon_upgrade_s les8_sles9_recommended.html

Upgrading the VERITAS Software Before upgrading, 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, /etc/elilo.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.

If you are upgrading an HA cluster, follow the guidelines given in the VERITAS Cluster Server (VCS) Installation Guide for information on preserving your VCS configuration across the upgrade procedure. In particular, you should make backups of configuration

Chapter 3, Upgrading VERITAS Storage Foundation and Linux 41

http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/x8664-multi-install-guide/ap-upgrade.html

http://support.novell.com/cgi-bin/search/searchtid.cgi?/en/2005/01/dcon_upgrade_sles8_sles9_recommended.html


files, such as main.cf and types.cf, in the /etc/VRTSvcs/conf/config directory. Additional configuration files, such as Oracletypes.cf, may also be present in this directory if you have installed any VCS agents. You should also back up these files.

▼ To upgrade a VERITAS Storage Foundation product


2. Use the vxlicrep command to make a record of the currently installed VERITAS licenses.

3. If the systems are running as a cluster, take all service groups offline, and shut down VCS prior to launching the uninstallsf script:

# /opt/VRTSvcs/bin/hastop -all

Note Do not use the -force option when executing hastop. This will leave all service groups online and shut down VCS, causing undesired results during uninstallation of the packages.

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.



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. There must be at least one other disk in the rootdg disk group in addition to the root disk for vxunroot to succeed.

# /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 VxFS file systems or Storage Checkpoints are mounted:

# df -T | grep vxfs

6. Unmount all Storage Checkpoints and file systems:

# umount /checkpoint_name# umount /filesystem

7. Verify that all file systems have been cleanly unmounted:

# echo "8192B.p S" | fsdb -t vxfs filesystem | grep cleanflags 0 mod 0 clean clean_value

A clean_value value of 0x5a indicates the file system is clean, 0x3c incidates the file system is dirty, and 0x69 indicates the file system is dusty. A dusty file system has pending extended operations.

a. If a file system is not clean, enter the following commands for that file system:

# fsck -t vxfs filesystem# mount -t vxfs filesystem mountpoint# umount mountpoint

This should complete any extended operations that were outstanding on the file system and unmount the file system cleanly.

There may be a pending large fileset clone removal extended operation if the umount command fails with the following error:

file system device busy

You know for certain that an extended operation is pending if the following message is generated on the console:

Storage Checkpoint asynchronous operation on file_system filesystem still in progress.



b. If an extended operation is pending, you must leave the file system mounted for a longer time to allow the operation to complete. Removing a very large fileset clone can take several hours.

c. Repeat step 7 to verify that the unclean file system is now clean.

8. 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.

9. 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

10. Make a record of the mount points for VxFS file systems and VxVM volumes that are defined in the /etc/fstab file. You will need to recreate these entries in the /etc/fstab file on the freshly installed system.

11. Shut down the system.

12. Install Red Hat Enterprise Linux 4 Update 1 or SUSE Linux Enterprise Server 9 SP1 on your system.

Caution This is likely to destroy any existing data on any disks that are touched by the installation procedure. During installation, do not reconfigure any disks other than the root disk or those disks that were previously in the rootdg disk group. To ensure the integrity of your data, it is recommended that you back it up before starting the upgrade.

13. Perform any necessary preinstallation checks. See “Preinstallation Instructions” on page 1 for more information.

14. Install VERITAS Storage Foundation 4.1 or VERITAS Storage Foundation 4.1 for DB2 and any additional required packages from the VERITAS software disc as described in “Installing the VERITAS Software” on page 15. If you have not yet obtained new licenses, enter the license keys that you recorded in step 2 on page 42. This will allow you to use some, but not all, of the software features.

15. Reinstate the mount points in the /etc/fstab file that you recorded in step 10 on page 44.

16. Reboot the upgraded systems.



17. Restart all the volumes by entering the following command for each disk group:

# vxvol -g diskgroup startall

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

◆ If you want to use features of VERITAS Storage Foundation 4.1 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.

◆ Stop the cluster, restore the VCS configuration files to the /etc/VRTSvcs/conf/config directory, and restart the cluster.

◆ 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.

18. If you upgraded to the current version of VERITAS Storage Foundation for DB2, see “Configuring VERITAS Storage Foundation for DB2” on page 34.


Upgrading the Linux Kernel


Note This procedure is only required if your root disk is encapsulated, or if the systems to be upgraded are in an HA cluster.

If you need to upgrade your Linux kernel after the VERITAS Storage Foundation 4.1 software has been installed, follow this procedure:

▼ To upgrade the Linux kernel


2. If you are upgrading a node in an HA cluster, perform the following steps:

a. From any node in the cluster, make the VCS configuration writable:

# haconf -makerw

b. Enter the following command to freeze HA service group operations on the node that is to be upgraded:

# hasys -freeze -persistent node_name

c. Make the VCS configuration read-only:

# haconf -dump -makero


# df -v /


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.



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. There must be at least one other disk in the rootdg disk group in addition to the root disk for vxunroot to succeed.



4. Upgrade Linux on the node, and then reboot the system to load the new kernel.

5. If you removed rootability in step 3 on page 46, re-encapsulate and remirror the root disk as described in the “Administering Disks” chapter of the VERITAS Volume Manager Administrator’s Guide.

6. If you are upgrading a node in an HA cluster, perform the following steps:

a. Make the VCS configuration writable again from any other node in the cluster:

# haconf -makerw

b. Enter the following command on the upgraded node to unfreeze HA service group operations:

# hasys -unfreeze -persistent node_name

c. Make the configuration read-only:

# haconf -dump -makero

d. Bring each service group online on the upgraded node:

# hagrp -online service_group -sys node_name

Repeat this entire procedure for each node in an HA cluster.


Upgrading VxFS Disk Layout Versions

Upgrading VxFS Disk Layout Versions VERITAS File System 4.1 allows Version 4 and 6 file system disk layouts to be mounted. Disk layout Versions 1, 2, and 5 are not supported by VxFS 4.1 on the Linux platform. All file systems created on VxFS 4.1 use disk layout Version 6 by default.

To determine the disk layout version of a VxFS file system, run the fstyp_vxfs command on the file system physical device, for example:

# /opt/VRTS/bin/fstyp –v /dev/vx/dsk/rootdg/volname | grep versionmagic 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.1 release, use the vxfsconvert or vxupgrade utilities to upgrade older disk layout versions to disk layout Version 6 as described in the following sections. (See the VERITAS Storage Foundation Release Notes for information on new features in VxFS 4.1.)

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.

# vxfsconvert /device_name

See the vxfsconvert(1M) and fsadm_vxfs(1M) manual pages for more information on converting to VxFS file systems.

When to Use vxupgrade You can use the vxupgrade command to upgrade older VxFS disk layouts to disk layout Version 6 while the file system remains mounted.

# vxupgrade -n 6 /mount_point

See the vxupgrade(1M) and fsadm_vxfs(1M) manual pages for more information on upgrading VxFS file systems.

Note The contents of intent logs created on a previous disk layout version cannot be used after the disk layout version is upgraded.


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. The space and time required to complete the upgrade increases with the number of files, extended attributes, and hard links in the file system. Typical maximum space is at least two additional inodes with one block for every inode. Allow at least ten minutes to upgrade for every million inodes in the file system.

Upgrading VxVM Disk Group Versions All VERITAS Volume Manager disk groups have an associated version number. Each VxVM release supports a specific set of disk group versions and can import and perform tasks on disk groups with those versions. Some new features and tasks work only on disk groups with the current disk group version, so you need to upgrade existing disk groups before you can perform the tasks. The following table summarizes the disk group versions that correspond to each VxVM release on Linux from 3.2 to the present.

VERITAS Volume Manager Disk Group Version Supported Disk Group Release Versions

3.2 90 90

4.0 110 90, 110

4.1 120 90, 110, 120

Use the following command to find the version of a disk group:

# vxdg list diskgroup

To upgrade a disk group from version 90 or 110 to version 120, use the following command:

# vxdg upgrade diskgroup


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, first uninstall the existing VEA client package.

▼ To upgrade the VEA client package


2. Select Start > Settings > Control Panel.

3. Double-click Add/Remove Programs to display a list of installed products.

4. Select VERITAS Enterprise Administrator from the list, and click the Remove button.

5. Click Yes when a dialog box appears asking you to confirm the removal.

6. After removing the existing package, install the new VEA client package by following the instructions given in “Installing the VEA Client on a Microsoft Windows System” on page 30.


Uninstalling VERITAS Storage Foundation
4 This chapter covers steps to uninstall VERITAS Storage Foundation and VERITAS Storage Foundation for DB2.

◆ “Shutting Down Cluster Operations” on page 52

◆ “Removing Rootability” on page 52

◆ “Removing VxFS File Systems” on page 53

◆ “Moving Volumes To Disk Partitions” on page 53

◆ “Uninstalling VERITAS Storage Foundation Packages” on page 55

◆ “Uninstalling VERITAS Infrastructure Packages” on page 56

◆ “Removing License Files (Optional)” on page 56

◆ “Removing the VEA Client from a Windows System” on page 57

Note Only users with superuser privileges can uninstall VERITAS Storage Foundation or VERITAS Storage Foundation for DB2.

Caution Failure to follow the instructions in the following sections may result in unexpected behavior.

51

Shutting Down Cluster Operations

Shutting Down Cluster Operations If the systems are running as an HA cluster, use the following command to take all service groups offline, and shut down VCS:

# /opt/VRTSvcs/bin/hastop -all

Note Do not use the -force option when executing hastop. This will leave all service groups online and shut down VCS, causing undesired results during uninstallation of the packages.

Removing Rootability

Note Perform this procedure if you configured rootability by encapsulating the root disk.

▼ To remove rootability


# df -v /


2. 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.



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

3. 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:




Removing VxFS File Systems

Removing VxFS File Systems The VxFS package cannot be removed if there are any mounted VxFS file systems. Unmount all VxFS file systems before removing the package. After you remove the VxFS package, VxFS file systems are not mountable or accessible until another VxFS package is installed. It is advisable to back up VxFS file systems before installing a new VxFS package. If VxFS will not be installed again, all VxFS file systems must be converted to a new file system type.

▼ To remove VxFS file systems

1. Check if any VxFS file systems or Storage Checkpoints are mounted:

# df -T | grep vxfs

2. Make backups of all data on the file systems that you wish to preserve, or recreate them as non-VxFS file systems on non-VxVM volumes or partitions.

3. Unmount all Storage Checkpoints and file systems:

# umount /checkpoint_name# umount /filesystem

4. Comment out or remove any VxFS file system entries from the /etc/fstab file.

Moving Volumes To Disk Partitions All volumes must be moved to disk partitions. This can be done using one of these procedures:

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

◆ Back up each file system individually and then recover them all after creating new file systems on disk partitions.

◆ Use VxVM to move volumes incrementally onto disk partitions as described in the following section.

Chapter 4, Uninstalling VERITAS Storage Foundation 53

Moving Volumes To Disk Partitions

Moving Volumes onto Disk Partitions Using VxVM

▼ To move volumes onto disk partitions

1. Evacuate disks using the vxdiskadm program, VEA, or the vxevac script. You should consider the amount of target disk space required for this before you begin.

Evacuation moves subdisks from the specified disks to target disks. The evacuated disks provide the initial free disk space for volumes to be moved to disk partitions.

2. 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. Decide which volume to move first. If the volume to be moved is mounted, unmount it.

4. If the volume is being used as a raw partition for database applications, make sure that the application is not updating the volume and that data on the volume is synced.

5. Create a partition on free disk space of the same size as the volume. If there is not enough free space for the partition, a new disk must be added to the system for the first volume removed. Subsequent volumes can use the free space generated by the removal of this volume.

6. 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.

7. Replace the entry for that volume (if present) in /etc/fstab with an entry for the newly created partition.

8. Mount the disk partition if the corresponding volume was previously mounted.

9. 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


Uninstalling VERITAS Storage Foundation Packages

10. Remove any disks that have become free (have no subdisks defined on them) by removing volumes from VERITAS Volume Manager control. To check if there are still some subdisks remaining on a particular disk, use the following command:

# vxprint -F “%sdnum” disk_media_name

11. If the output is not 0, there are still some subdisks on this disk that must be subsequently removed. If the output is 0, remove the disk from VERITAS Volume Manager control using the following commands:

# vxdg -g diskgroup rmdisk disk _media_name# vxdisk rm disk_access_name

12. The free space now created can be used for adding the data in the next volume to be removed.

13. After all volumes have been converted into disk partitions successfully, reboot the system. After the reboot, none of the volumes should be open. To verify that none of the volumes are open, use the following command:

# vxprint -Aht -e v_open

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

Uninstalling VERITAS Storage Foundation Packages To shut down and remove the installed VERITAS Storage Foundation or VERITAS Storage Foundation for DB2 packages, use the following commands:

# cd /opt/VRTS/install# ./uninstallsf

You can use this command to remove the packages from one or more systems.

Note To remove packages from remote systems, configure ssh or rsh as described in “Remote and Cluster Installation and Uninstallation” on page 10.

Not all these packages may be installed on your system depending on the choices that you made when you installed VxVM.


Uninstalling VERITAS Infrastructure Packages

Uninstalling VERITAS Infrastructure Packages There are several packages, referred to as infrastructure packages, that are used by multiple VERITAS products. These packages are not removed when uninstalling a single VERITAS product. If you remove all VERITAS products from a system and want to ensure that there are no remaining VERITAS packages, use the following commands:

# cd /opt/VRTS/install# ./uninstallinfr

The uninstallinfr script removes the remaining packages that are required for product installation. The VERITAS Enterprise Administrator packages, VRTSob and VRTSobgui, are also removed.

Removing License Files (Optional)

▼ To remove license files

1. To see what license key files you have installed on a system, enter:

# /sbin/vxlicrep

The output lists the license keys and information about their respective products.

2. Go to the directory containing the license key files and list them. Enter:

# cd /etc/vx/licenses/lic# ls -a

3. Using the output from step 1, identify and delete unwanted key files listed in step 2. Unwanted keys may be deleted by removing the license key file.


Removing the VEA Client from a Windows System


▼ To uninstall the VEA client from a Windows system


2. Select Start > Settings > Control Panel.

3. Double-click Add/Remove Programs to display a list of installed products.

4. Select VERITAS Enterprise Administrator from the list, and click the Remove button.

5. Click Yes when a dialog box appears asking you to confirm the removal.


veritas storage foundation 4.1 installation...

Documents