VERITAS Volume Manager 3.5 Installation Guide HP-UX 11i v2 Manufacturing Part Number: 5991-0607 September 2004 © Copyright 2004 VERITAS Software Corporation. All rights reserved..
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.
Contents 1. Before You Start Installation and Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 VxVM Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 VEA Set Up Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Upgrading to the Latest VxVM Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 Upgrading Disk Group Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Supported Upgrade Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Introduction This document provides information on installing and initializing VERITAS Volume ManagerTM (VxVMTM) and VERITAS Enterprise AdministratorTM (VEATM)).
Related Documents The following documents contain related information: NOTE 6 • VERITAS Volume Manager Migration Guide • VERITAS Volume Manager Release Notes • VERITAS Volume Manager Hardware Notes “Dynamic Disk Groups" were formerly known as "Disk Groups." They are still sometimes referred to as "Disk Groups" in documentation, menu displays, and the CLI.
Conventions The following table describes the typographic conventions used in this guide. Table 1 Typographic Conventions Typeface Examples Computer output, file contents, files, directories, software elements such as command options, function names, and parameters Read tunables from the /etc/vx/tunefstab file. New terms, book titles, emphasis, variables to be replaced by a name or value See the User’s Guide for details.
Getting Help If you have any comments or problems with the VERITAS products, contact the VERITAS Technical Support: • U.S. and Canadian Customers: 1-800-342-0652 • International Customers: +1 (650) 527-8555 • Email: support@veritas.com For license information (U.S. and Canadian Customers): • Phone: 1-925-931-2464 • Email: license@veritas.com • Fax: 1-925-931-2487 For software updates: • Email: swupdate@veritas.
Using VRTSexplorer The VRTSexplorer program can help VERITAS Technical Support engineers diagnose the cause of technical problems associated with VERITAS products. You can download this program from the VERITAS FTP site or install it from the VERITAS Installation CD.
1 Before You Start The following topics are covered in this chapter: Chapter 1 • “Installation and Upgrade Overview” on page 2 • “Installation and Upgrade Roadmaps” on page 3 • “Installation and Upgrade Requirements” on page 5 • “Preparing to Install VxVM on a System with LVM Volume Groups” on page 11 1
Before You Start Installation and Upgrade Overview Installation and Upgrade Overview The section gives an overview of the installation and upgrade processes. VxVM Installation Installing the VxVM for the first time involves the following steps: Step 1. Familiarize yourself with the section “Installation and Upgrade Requirements” on page 5 Step 2.
Before You Start Installation and Upgrade Roadmaps Installation and Upgrade Roadmaps This section gives an overview of the installation and upgrade procedures: • “Installing VxVM on HP-UX 11i v2” on page 3 • See “Installation and Upgrade Requirements” on page 5 Installing VxVM on HP-UX 11i v2 VxVM is part of the Operating Environment (OE), and is installed by default on every new OE installation.
Before You Start Installation and Upgrade Roadmaps Summary of VxVM Products VxVM consists of several related software packages as shown in the following tables: Table 1-1 HP-UX 11i v2 September 2004 Release Software Bundle Product Name Availability Base VxVM Base VxVM 3.5 for HP-UX 11i v2 Free with HP-UX 11i v2 September 2004 Application Software, HP-UX 11i v2 Internet, all HP-UX 11i v2 Operating Environments B9116AA VxVM 3.
Before You Start Installation and Upgrade Requirements Installation and Upgrade Requirements Before you install or upgrade, you need to check that: Step 1. The administrator who performs the upgrade has root access and a working knowledge of HP-UX administration. Step 2.
Before You Start Installation and Upgrade Requirements Product Licensing The VERITAS Volume Manager is a licensed product. Before you install the VERITAS Volume Manager 3.5 software packages, you need to obtain a license key from VERITAS. If you have a temporary license key, you must obtain a permanent license key when you purchase the product. A License Key Request Form (LKRF) is included in the product package.
Before You Start Installation and Upgrade Requirements Add or Upgrade Licenses Volume Manager 3.5 introduces a new licensing package, VRTSvlic, that is common to all new VERITAS products. The VRTSvlic package replaces the functionality of the VRTSlic package that was used in VxVM 3.2 and earlier releases.
Before You Start Installation and Upgrade Requirements • VERITAS Volume Manager Service Provider (VRTSvmpro) • VERITAS File System Service Provider (VRTSfspro) NOTE All these packages are dependent on one another, and all must be present on the server for VEA to run. Furthermore, VRTSob must already be installed before you can install VRTSvmpro. Once installed, you cannot remove VRTSob before removing (deinstalling) VRTSvmpro.
Before You Start Installation and Upgrade Requirements To ensure that the operating system is running at release level 11i v2, use the following command on a 64-bit machine: # swlist -l bundle HPUXBaseOS The output must contain: HPUXBaseOS B.11.23 HP-UX Base OS On a 32-bit machine, use the following command: # swlist -l bundle HPUXBase32 The output must contain: HPUXBase32 B.11.
Before You Start Installation and Upgrade Requirements Table 1-5Required Patches (Continued) Patch Number Description Mandatory/Option al PHCO_27209 Patch for VxVM rootability changes to the insf command Mandatory (needed for VxVM 3.
Before You Start Preparing to Install VxVM on a System with LVM Volume Groups Preparing to Install VxVM on a System with LVM Volume Groups You can use the vxvmconvert command to migrate LVM volume groups to VxVM disk groups (apart from the root volume group). NOTE You can enable a VxVM rootable system by using the vxcp_lvmroot command to clone the LVM-based root disk to a VxVM root disk.
Before You Start Preparing to Install VxVM on a System with LVM Volume Groups 12 Chapter 1
2 Installing VERITAS Volume Manager VxVM is installed by default, when: 1. Upgrading from HP-UX 11.22 to HP-UX 11i v2 2. Installing HP-UX 11i v2 This chapter describes only with installing the VxVM product from the VERITAS CD.
Installing VERITAS Volume Manager Mounting the CD-ROM Mounting the CD-ROM Before you install the VxVM or VEA, you need to mount the VxVM CD-ROM on your system as follows: Step 1. Log in as superuser. Step 2. Insert the VxVM CD-ROM into your system’s CD-ROM drive. Step 3. Determine the block device file for the CD-ROM drive by entering: # ioscan -fnC disk Make a note of the device file as it applies to your system. Step 4.
Installing VERITAS Volume Manager Mounting the CD-ROM Chapter 2 • B9117AA—Full CVM 3.5 for HP-UX. • B9116AA—Full Volume Manager 3.5 for HP-UX. • B9118AA—Volume Manager 3.5 FastResync Option for HP-UX.
Installing VERITAS Volume Manager Installing VxVM Installing VxVM You can install VxVM using the swinstall utility, as described in the following sections; alternatively, the VERITAS software disc has an automated installation and licensing procedure that lets you install packages using an Installation Menu. Installing VxVM Using the Installation Menu The Product License and Installation Guide, included with the VERITAS software disc, provides complete information on using the Installation Menu.
Installing VERITAS Volume Manager Installing VEA Installing VEA To use VEA, the following packages need to be installed and running on the server: • VERITAS Enterprise Administrator Service (VRTSob) • VERITAS Volume Manager Service Provider (VRTSvmpro) • VERITAS File System Service Provider (VRTSfspro) In addition, one of the following packages needs to be installed and running on the client: NOTE • VERITAS Enterprise Administrator (VRTSobgui)—the client package for HP-UX.
Installing VERITAS Volume Manager Installing VEA Table 2-2 VEA Directories (Continued) Directory /opt/VRTS/man/ Contents VEA manual pages Installing the VEA Client on Windows The VEA client runs on Windows NT, Windows XP, Windows 2000, Windows ME, Windows 98, and Windows 95 machines. If you plan to run VEA from a Windows machine, install the optional Windows package after you have installed the VEA server on an HP-UX machine.
Installing VERITAS Volume Manager Removing Previous Licensing Packages Removing Previous Licensing Packages If you add the VRTSvlic package and see the following message, you must first remove the existing VRTSvlic package: Current administration requires that a unique instance of the package be created. However, the maximum number of instances of the package which may be supported at one time on the same system has already been met. Step 1. De-install the old package. Step 2.
Installing VERITAS Volume Manager Removing Previous Licensing Packages 32 Chapter 2
3 Setting up the VxVM Environment Use the vxinstall procedure to initialize VxVM.
Setting up the VxVM Environment Initializing VxVM Initializing VxVM After you install the VERITAS Volume Manager, use vxinstall(1M) to initialize it. vxinstall does the following: • Sets up the initial VxVM disk group, rootdg, and populates it with disks. • Starts the configuration, notification, and relocation daemons used by VxVM. Selecting Disks for VxVM Initialization The vxinstall command initializes the Volume Manager, as described below.
Setting up the VxVM Environment Initializing VxVM The disks.exclude file is not created by VxVM software installation. To add disk names to this file, you must create the file. To list a disk in the file, enter only the base device file name. For example: c0t0d0 c0t2d0 c1t10d0 To add disks that are in use by LVM volumes to the disks.exclude file, add all disks in the volume group to which the disk belongs.
Setting up the VxVM Environment Using vxinstall Using vxinstall This section describes how to use vxinstall. To place some of your disks in another disk group, wait until after you have used vxinstall to set up rootdg. Use vxdiskadm(1M) or the VEA to create and populate other groups. NOTE You only need to run vxinstall once.
Setting up the VxVM Environment Using vxinstall Adding disk controller names to /etc/vx/cntrls.exclude precludes VxVM initialization or control of all disks on that controller. To exclude all disks on a controller, add the controller name on a line by itself in the file. For example: # cat /etc/vx/cntrls.exclude c1 c3 c8 To exclude enclosures, use /etc/vx/enclr.exclude. When the name of a disk enclosure is added to this file, VxVM does not initialize or control all disks on the controller.
Setting up the VxVM Environment Using vxinstall Step 8. Select either 1 for Quick Installation or 2 for Custom Installation. • Quick Installation uses default options and brings every disk on your system under VxVM control, except for disks under LVM control (including your root/boot disk) and disks listed in the files /etc/vx/disks.exclude and /etc/vx/cntrls.exclude. See “Quick Installation” on page 40 below for details.
Setting up the VxVM Environment Using vxinstall If you enter n, vxinstall prompts you for a disk name for each disk on the disk array individually. For each disk, respond with the desired disk name and press Return. Step 3.
Setting up the VxVM Environment Using vxinstall NOTE vxinstall shows default responses in parentheses; to choose the default, press Return. You can quit the initialization at any time by typing q at any of the vxinstall prompts. Disks are initialized at the end of the vxinstall procedure. If you quit vxinstall before it initializes the disks, all disks are left as they were before vxinstall was started. To use the Custom Installation option, perform the following procedure: Step 1.
Setting up the VxVM Environment Using vxinstall If you enter n, the vxinstall program prompts you for a disk name for each disk on the controller, as follows: Enter disk name for c1t0d0 [,q,?](default: disk01) For each disk, enter the desired disk name and press Return. When all of the disks in the current disk array have been named, press Return to move on to the next disk array. • To install one disk at a time, select 2.
Setting up the VxVM Environment Using vxinstall If a shutdown is not required, the vxinstall program indicates successful completion of the installation Installation is complete. Preventing Multipathing/Suppressing Devices from VxVM’s View This section describes how to exclude a device which is under Volume Manager or Dynamic Multipathing control. Follow these steps to disable multipathing. Step 1. Select menu item 3 (Prevent Multipathing/Suppress devices from VxVM’s view) from the vxinstall main menu.
Setting up the VxVM Environment Using vxinstall • For example, the VID:PID combination for an ACME Z1 disk array would be specified as ACME:Z1. • Option 4 prevents VxVM from defining a set of paths, or pathgroup, for disks that are not multipathed by VxVM. (A pathgroup specifies a set of paths that VxVM should recognize as a single path. Only one path is made visible from a pathgroup.) • Option 5 excludes devices by preventing VxVM from applying dynamic multipathing (DMP) to all disks on a controller.
Setting up the VxVM Environment Using vxinstall 46 Chapter 3
4 Upgrading the VERITAS Volume Manager The following topics are covered in this chapter: Chapter 4 • “Upgrading to the Latest VxVM Version” on page 48 • “Upgrading Disk Group Versions” on page 49 • “Supported Upgrade Scenarios” on page 50 47
Upgrading the VERITAS Volume Manager Upgrading to the Latest VxVM Version Upgrading to the Latest VxVM Version We recommend that you upgrade to VxVM 3.5 on any and all of the VxVM products you have previously installed. Version VxVM 3.5 is more robust than earlier versions of the software. Upgrading to the latest VxVM software is automated when installing HP-UX 11i v2. Do not run vxinstall(1M) after upgrading.
Upgrading the VERITAS Volume Manager Upgrading Disk Group Versions Upgrading Disk Group Versions All disk groups have a version number associated with them. 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 only work on disk groups with the current disk group version, so you need to upgrade existing disk groups before you can perform these tasks.
Upgrading the VERITAS Volume Manager Supported Upgrade Scenarios Supported Upgrade Scenarios If you are already running a previous version of VxVM, you can upgrade to VxVM 3.5. In some cases, you do not have to do a complete removal of the old VxVM packages. With the release of VxVM 3.5, you also have the choice of having your root disk placed under VxVM control. With this in mind, the following upgrade procedures are broken down into: • Procedures needed to upgrade to the VxVM 3.
Upgrading the VERITAS Volume Manager Supported Upgrade Scenarios Step 5. Reboot from your new VxVM root disk. If you created a mirrored root disk, then there is nothing more to do. The LVM root disk can now safely co-exist with your VxVM root disk, giving you an emergency backup boot target. Step 6.
Upgrading the VERITAS Volume Manager Supported Upgrade Scenarios 52 Chapter 4
5 Getting Started with VxVM The following topics are covered in this chapter: Chapter 5 • “Starting the VEA Service” on page 54 • “Starting the VEA Client” on page 55 • “Using Hot-Relocation” on page 56 • “Enabling Cluster Support in VxVM” on page 57 • “Configuring Shared Disks” on page 58 • “System Setup Guidelines” on page 59 • “Protecting Your System and Data” on page 63 • “Working With VxVM 3.
Getting Started with VxVM Starting the VEA Service Starting the VEA Service After installing the VEA packages, the VEA service needs to be stopped and restarted. To stop the VEA backend service, enter: # /opt/VRTSob/bin/vxsvc -k You can also stop the VEA backend service manually by killing this process. NOTE The VEA backend service is automatically started on a reboot.
Getting Started with VxVM Starting the VEA Client Starting the VEA Client NOTE Only users with appropriate privileges can run VEA. VEA can administer the local machine or a remote machine. However, Volume Manager and the VEA server must be installed on the machine to be administered. The Volume Manager vxconfigd daemon and the VEA server must be running on the machine to be administered. After installing Volume Manager and VEA and starting the server, start VEA in one of the following ways.
Getting Started with VxVM Using Hot-Relocation Using Hot-Relocation Hot-relocation automatically restores redundancy and access to mirrored and RAID-5 volumes when a disk fails. This is done by relocating the affected subdisks to disks designated as spares and/or free space in the same disk group. The hot-relocation feature is enabled by default. The associated daemon, vxrelocd, is automatically started during system startup. Follow these recommendations: Step 1.
Getting Started with VxVM Enabling Cluster Support in VxVM Enabling Cluster Support in VxVM NOTE Cluster management software such as MC/ServiceGuard must be installed on the nodes of your cluster system. VxVM includes an optional cluster feature that enables VxVM to be used in a cluster environment. The cluster functionality in VxVM allows multiple hosts to simultaneously access and manage a set of disks under VxVM control.
Getting Started with VxVM Configuring Shared Disks Configuring Shared Disks When installing VxVM for the first time or adding disks to an existing cluster, you must configure new shared disks. When upgrading VxVM, you must verify that your shared disks still exist. Shared disks are configured from one node only. Since the VxVM software is unable to determine whether or not a disk is shared, you must specify which disks are shared.
Getting Started with VxVM System Setup Guidelines System Setup Guidelines This section contains information to help you set up your system for efficient storage management. For specific setup tasks, refer to the VERITAS Volume Manager Administrator’s Guide. The following system setup sequence is typical and is used as an example. Your system requirements may differ. The system setup guidelines provide helpful information for specific setup configurations. Initial Setup Step 1.
Getting Started with VxVM System Setup Guidelines Dirty Region Logging (DRL) Guidelines Dirty Region Logging (DRL) can speed up recovery of mirrored volumes following a system crash. When DRL is enabled, Volume Manager keeps track of the regions within a volume that have changed as a result of writes to a plex. Volume Manager maintains a bitmap and stores this information in a log subdisk. Log subdisks are defined for and added to a volume to provide DRL.
Getting Started with VxVM System Setup Guidelines Mirroring and Striping Guidelines NOTE The VxVM Full license is required to use this feature. Refer to the following guidelines when using mirroring and striping together. For more information, see the VERITAS Volume Manager Administrator’s Guide for details. Chapter 5 • Make sure enough disks are available for the striped and mirrored configuration.
Getting Started with VxVM System Setup Guidelines RAID-5 Guidelines NOTE The VxVM Full license is required to use this feature. Refer to the following guidelines when using RAID-5. For more information, see the VERITAS Volume Manager Administrator’s Guide. In general, the guidelines for mirroring and striping together also apply to RAID-5. The following guidelines should also be observed with RAID-5: 62 • Only one RAID-5 plex can exist per RAID-5 volume (but there can be multiple log plexes).
Getting Started with VxVM Protecting Your System and Data Protecting Your System and Data VxVM can protect your system from loss of data due to disk failure. The following are suggestions for protecting your data: • Use mirroring to protect data against loss from a disk failure. To preserve data, create and use mirrored volumes that have at least two data plexes. The plexes must be on different disks. If a disk failure causes a plex to fail, the data in the mirrored volume still exists on the other disk.
Getting Started with VxVM Working With VxVM 3.5 Root Disks Working With VxVM 3.5 Root Disks This section describes: • “Adding Dump Volumes Using Volume Manager Disks” on page 64 • “Changing the Boot Disk to be the New Volume Manager Root Disk” on page 64 • “Removing a Mirrored Volume Manager Root Disk” on page 64 Adding Dump Volumes Using Volume Manager Disks Volume Manager volumes can be used for additional dump volumes in configurations with LVM or VxVM root disks. Step 1.
Getting Started with VxVM Working With VxVM 3.
Getting Started with VxVM Adding Swap Space Using VxVM Volumes Adding Swap Space Using VxVM Volumes The HP System Administration Manager (SAM) currently does not have the capability to add swap space using VxVM volumes. You need to use the VxVM CLI; for example: Step 1. Run the command: # /etc/vx/bin/vxdisksetup -i device Step 2. If this command comes back with: vxvm:vxdisk: ERROR: Device device is already in use by LVM. then, go to Step 3; otherwise, go to Step 4. Step # # # # 3.
6 Uninstalling the VERITAS Volume Manager This chapter conves the following topics: • “Preparing to Remove VxVM” on page 68 — “Preparatory Steps” on page 68 — “Moving Data Out of VxVM Control” on page 69 • “Shutting Down and Removing VxVM” on page 70 — “Shutting Down VxVM” on page 71 — “Removing the VxVM Package” on page 71 Chapter 6 67
Uninstalling the VERITAS Volume Manager Preparing to Remove VxVM Preparing to Remove VxVM Before removing the VxVM software with swremove, you must backup your data, move data out of VxVM control, and stop the VxVM. CAUTION If you try to swremove the VxVM software from your system without doing the following preparatory steps, you will likely lose data and leave your system in an uncertain state.
Uninstalling the VERITAS Volume Manager Preparing to Remove VxVM Moving Data Out of VxVM Control Before removing the VxVM, all the VxVM volumes must be moved to LVM disks. This can be done in one of the following ways: Chapter 6 • Incrementally create LVM volumes and move the data from each VxVM volume to an LVM volume one at a time. This procedure is described in “Preparing to Remove VxVM” on page 68.
Uninstalling the VERITAS Volume Manager Shutting Down and Removing VxVM Shutting Down and Removing VxVM To uninstall VxVM, you must move all VxVM volumes to LVM disks. This can be done using one of the following three methods: Step Step • Back up the system to tape or other media and recover the system from this. • Back up each file system individually, create new file systems on LVM logical volumes, and recover all volumes. • Move volumes incrementally (“evacuate”) onto logical volumes.
Uninstalling the VERITAS Volume Manager Shutting Down and Removing VxVM If the output is other than 0, some subdisks remain on this disk and must be removed. If the output is 0, remove the disk from Volume Manager control using the following commands: # vxdg rmdisk diskname # vxdisk rm devname Step 10. Copy the data in the next volume to be removed to the newly created free space. Step 11. Reboot the system after all volumes have been converted successfully.
Uninstalling the VERITAS Volume Manager Shutting Down and Removing VxVM 72 Chapter 6
