VERITAS Volume Manager™ 3.
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 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cluster Environment Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Check the Operating System Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Install HP-UX Operating System Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Preparing to Install VxVM on a System with LVM Volume Groups . . . . . . . . . . . . . . 15 Chapter 2. Installing VERITAS Volume Manager . . . . . . . . . . . . . . . . . . . . . . .
Upgrading Disk Group Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Supported Upgrade Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Upgrading to a VxVM Root Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Upgrade Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Upgrading VxVM 3.
Moving Data Out of VxVM Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Shutting Down and Removing VxVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Shutting Down VxVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Removing the VxVM Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Introduction This document provides information on installing and initializing VERITAS Volume ManagerTM (VxVMTM) and VERITAS Enterprise AdministratorTM (VEATM)).
Conventions Conventions The following table describes the typographic conventions used in this guide. Typeface Usage Examples monospace 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 Getting Help If you have any comments or problems with VERITAS products, contact 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.
Getting Help x VERITAS Volume Manager Installation Guide
1 Before You Start The following topics are covered in this chapter: ◆ Installation and Upgrade Overview ◆ Installation and Upgrade Roadmaps ◆ Installation and Upgrade Requirements ◆ Preparing to Install VxVM on a System with LVM Volume Groups 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: 1.
Installation and Upgrade Overview 6. For upgrading, there are a number of scenarios; including upgrading from HP-UX 11.0 and HP-UX 11.11i. These are discussed in “Upgrading the VERITAS Volume Manager.” Note If your system is running at a release level earlier than HP-UX 11.11i and VxVM is not installed, you must upgrade to HP-UX 11.11i before installing VxVM. If VxVM is already installed, you must upgrade the operating system to HP-UX 11.11i at the same time as you upgrade VxVM. 7.
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 ◆ Installation and Upgrade Requirements Installing VxVM on HP-UX 11i VxVM is part of the Operating Environment (OE), and is installed by default on every new OE installation.
Installation and Upgrade Roadmaps VxVM Controlling the Root Disk Upgrade to VxVM rootability can be accomplished in conjunction with the HP AR0902 release. VxVM Not Controlling the Root Disk If you are running a VxVM release earlier than 3.5, and do not wish to have the root disk controlled by VxVM, then you need to upgrade to VxVM Release 3.5. If your system is running under HP-UX 11.0 or earlier, you must first upgrade to HP-UX 11i.
Installation and Upgrade Roadmaps Summary of VxVM Products VxVM consists of several related software packages as shown in the following tables: HP AR0902 Software Bundle Product Name Base VxVM Base VxVM 3.5 for Free with HP-UX 11i Application Software, HP-UX HP-UX 11i 11i Internet, all HP-UX 11i Operating Environments B9116AA VxVM 3.5 full features for HP-UX 11i Purchase license to enable VXVM-FULL; use codeword to unlock from HP-UX 11i Application Software B9117AA VERITAS Cluster Volume Manager 3.
Installation and Upgrade Requirements Note The HP Base-VXVM bundle consists of the following products: VRTSvxvm, VRTSvmdoc, VRTSvlic, VRTSob, VRTSobgui, VRTSvmpro, and VRTSfspro.: VERITAS VxVM Software Packages Product Description VRTSvxvm VERITAS VxVM 3.5 for HP-UX 11.11i (Drivers and Utilities) VRTSvlic SIG Licensing Package (Licensing Utilities) VRTSvmdoc VERITAS VxVM 3.
Installation and Upgrade Requirements Check Disk Space Before installing the VxVM software and related patches, verify that there is sufficient disk space to contain all of the software. The SD-UX tools check space available and prevent installation if a space problem is detected. The following table shows the approximate breakdown of the recommended space requirements for each file system (assuming the VxVM packages are installed in their default locations.
Installation and Upgrade Requirements package. The LKRF has all the information required to establish a user account on the VERITAS vLicense™ website and generate your license key. If you do not receive a License Key Request Form, contact your sales representative, or send an email with your sales order number to license@veritas.com. To obtain a product license, use the vLicense website (see below) or complete the License Key Request Form, including your system’s host ID and model type.
Installation and Upgrade Requirements Add or Upgrade Licenses VxVM 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. The following table lists equivalency between licensing commands in VRTSlic and VRTSvlic: VRTSlic command VRTSvlic command Description vxlicense -c vxlicinst Installs a license.
Installation and Upgrade Requirements Upgrading VxVM You cannot upgrade the VRTSvxvm (or Base-VXVM) and license packages at the same time, since the license package does not support upgrade.
Installation and Upgrade Requirements Installing VRTSob, VRTSvmpro, and VRTSfspro 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) Note All these packages are dependent on one another, and all must be present on the server for VEA to run.
Installation and Upgrade Requirements Cluster Environment Requirements If your configuration has a cluster, which is a set of hosts that share a set of disks, follow these steps: 1. Obtain a license for the optional VxVM cluster feature from your Customer Support channel. 2. Decide where to place the rootdg disk group for each node in the cluster. A system using VxVM has one or more disk groups, including the rootdg. The rootdg must exist, and it cannot be shared between systems.
Installation and Upgrade Requirements Check the Operating System Environment This release of VxVM can only be installed on an HP-UX system running the HP-UX 11.11i operating system. Installation of VxVM does not occur if the system is not up to this release level. For example, installation is not possible on HP-UX 11.0. VxVM 3.5 supports both 32-bit and 64-bit HP-UX 11.11i.
Installation and Upgrade Requirements The following table shows all patches required for VxVM 3.5.: Patch Number Description Mandatory/Optional PHKL_26452 scsi3/disc30 patch (includes passthru ioctl) Mandatory PHKL_26519 scsi IO Subystem cumulative patch Mandatory PHKL_19246 vm_superpage fix Mandatory PHKL_27096 Patch for VxVM rootability changes to HP-UX Kernel Mandatory (needed for VxVM 3.
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.
Preparing to Install VxVM on a System with LVM Volume Groups 16 VERITAS Volume Manager Installation Guide
2 Installing VERITAS Volume Manager If you are installing VxVM from the HP-UX pre-AR0902 CD, then the Base VxVM package is installed by default, and includes all the necessary VxVM products. This chapter describes only with installing the VxVM product from the VERITAS CD.
Mounting the CD-ROM Note The installation process may generate one or more messages indicating that the media is not writable. You can ignore these messages. VxVM Packages The VERITAS CD-ROM for VxVM contains the following packages: ◆ VRTSvxvm and Volume Replicator software. ◆ VRTSvlic-VERITAS Licensing Utilities ◆ VRTSvmdoc-online copies of VxVM guides. Note The VERITAS Volume Manager Release Notes are not installed with any of the packages.
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 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: ◆ VERITAS Enterprise Administrator (VRTSobgui)—the client package for HP-UX.
Installing VEA The VEA package for HP-UX contains the following directories: Directory Contents jre/ Java Runtime Environment (JRE) bin/ vxsvc—VEA server startup and stop script vea—VEA startup script /opt/VRTS/man/ 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.
Removing Previous Licensing Packages - For Windows XP, ME, Windows 98 or Windows 95, restart the computer. 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. 1.
3 Setting up the VxVM Environment Use the vxinstall procedure to initialize VxVM.
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.
Initializing VxVM LVM disks are automatically excluded from VxVM control and do not need to be added to the /etc/vx/disks.exclude file. No Volume Manager utility can be used to initialize an LVM-controlled disk. You must take specific actions to remove a disk from LVM control before attempting to place it under VxVM control. Volume Manager utilities recognize file systems on raw disks (not under LVM control).
Initializing VxVM Excluding Enclosures from VxVM Control The /etc/vx/enclr.exclude file is used to exclude enclosures. When the name of a disk enclosure is added to this file, VxVM does not initialize or control all disks on the controller.
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.
Using vxinstall You must create the exclude files, /etc/vx/disks.exclude, /etc/vx/enclr.exclude, and /etc/vx/cntrls.exclude, if you need them; they are not created automatically. To exclude a disk, add its base device file name on a line by itself in the file. For example: # cat /etc/vx/disks.exclude c0t0d0 c0t2d0 c1t10d0 Adding disk controller names to /etc/vx/cntrls.exclude precludes VxVM initialization or control of all disks on that controller.
Using vxinstall 6. If you selected n in the previous step, the vxinstall program displays a brief introduction to the installation process, as follows: Hit RETURN to continue 7. Press Return to continue The vxinstall program next displays a menu with the following options: The options are defined as follows: - 1 (Quick Installation) uses default options for installation - 2 (Custom Installation) allows you to control whether and how each disk will be brought under VERITAS Volume Manager control.
Using vxinstall /etc/vx/ntrls.exclude or /etc/vx/enclr.exclude files, the option “Prevent multipathing/Suppress devices from VxVM’s view” in vxinstall, or the Custom Installation option (which allows you to leave certain disks alone). 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.
Using vxinstall - If you enter n, the vxinstall program prompts you for a disk name for each disk on the disk array individually. 4. For each disk, respond with the desired disk name and press Return. 5. When all of the disks on the current disk array have been named, press Return and repeat step 3 and step 4 for the remaining controllers on your system.
Using vxinstall - Custom Installation allows you to initialize disks in a disk array, even if valid data exists on those disks. Avoid selecting the initialize option for any disks that contain valid data. 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.
Using vxinstall ❖ To initialize all disks in the disk array, select 1. Caution Initializing a disk destroys all data on the disk. All disks in the disk array are reinitialized. This destroys all data and partitions on each disk and makes the disk available as free space for allocating new volumes, or mirrors of existing volumes. If you are running the vxinstall program on new disks that have never been placed under VxVM control before, choose this option.
Using vxinstall No changes are made to the disks and they are not placed under VxVM control. If applications are currently using these disks and you do not want to upgrade these applications to use VxVM, use this option to ensure that your applications continue to use the disks without modification. 5. Repeat step 4 on page 44 for each of the remaining disk arrays on your system.
Using vxinstall Volume Manager Installation Menu: VolumeManager/Install/Exclude Devices This operation might lead to some devices being suppressed from VxVM’s view or prevent them from being multipathed by vxdmp. (This operation can be reversed using the vxdiskadm command). Do you want to continue? [y,n,q,?] (default: n) y 2. Enter y. 3. The following message displays. Select an operation.
Using vxinstall - 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. The controller you name is excluded from DMP control. - Option 6 excludes a specified path from dynamic multipathing.
4 Upgrading the VERITAS Volume Manager The following topics are covered in this chapter: ◆ Upgrading to the Latest VxVM Version ◆ Upgrading Disk Group Versions ◆ Supported Upgrade Scenarios ◆ Upgrading VxVM 3.1 on HP-UX 11.0 to VxVM 3.
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 the HP pre-AR0902 CD.
Upgrading Disk Group Versions If a disk group version is not specified using the -T option, this command upgrades the disk group to the highest version supported by the VxVM version on your system. For shared disk groups, the latest disk group version is only supported by the latest cluster protocol version. See “Upgrading Cluster Functionality” in the Volume Manager Administrator’s Guide for more information on changing the cluster protocol version.
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. When you do have to remove the old package, you should follow the procedure for saving your VxVM configuration to a file, as outlined in “Migration Procedure.” With the release of VxVM 3.5, you also have the choice of having your root disk placed under VxVM control.
Supported Upgrade Scenarios The-v option is highly recommended. The cloning of the root disk is a lengthy operation, and the -v option gives a time-stamped progress indication as each volume is copied, and other major events. Note The vxcp_lvmroot command checks the OS revision number, and will not allow upgrade to proceed unless the OS revision is AR0902 or greater. 4. You can use the setboot (1M) command to save the hardware path of the new VxVM root disk in the system NVRAM.
Supported Upgrade Scenarios 3. Upgrade from HP-UX 11.0 LVM rootable system with VxVM 3.1 to HP-UX 11i AR0902 LVM rootable system with VxVM 3.5. Rootability Upgrade Paths If Your Current Configuration is ... ... And You Want to Upgrade to ... ... Then You Need to ... Refer to Scenario 1 Pre-AR0902 HP-UX 11i LVM rootable, with VxVM 3.1 configured HP-UX 11i AR0902 LVM rootable with VxVM 3.5 Upgrade using the HP AR0902 (or later) CD. VxVM 3.
Upgrading VxVM 3.1 on HP-UX 11.0 to VxVM 3.5 on HP-UX 11i Upgrading VxVM 3.1 on HP-UX 11.0 to VxVM 3.5 on HP-UX 11i The upgrade procedure allows you to retain your existing HP-UX 11.0 VxVM configuration. After upgrading, you can resume using VxVM on the same host with an upgraded operating system without running the vxinstall procedure.
Upgrading VxVM 3.1 on HP-UX 11.0 to VxVM 3.5 on HP-UX 11i 6. Stop the Volume Manager using the following command: # vxdctl stop 7. Remove VxVM, and any other VRTS products on the HP-UX 11.00 machine (such as VRTSlic, VRTSvmdoc and VRTSvmsa), and any patch bundles (such as VRTSvxvm_310_01 or VRTSvxvm_310_02), using a command of the form: # swremove -x autoreboot=true VRTSvxvm ... The host will now reboot. At this time, the host can be upgraded to HP-UX 11i with no impact to the VxVM disk groups.
Upgrading VxVM 3.1 on HP-UX 11.0 to VxVM 3.5 on HP-UX 11i 14. Initialize vxconfigd using the following command: # vxdctl init 15. Initialize the VxVM dynamic multipathing (DMP) subsystem using the following command: # vxdctl initdmp 16. Enable vxconfigd using the following command: # vxdctl enable 17. Put VxVM lines copied in Step 5 back into /etc/fstab. 18. Start the volumes using the following command: # vxrecover -s 19. Mount the volumes on the host using the following command: # mountall 20.
Upgrading VxVM 3.1 on HP-UX 11.0 to VxVM 3.
5 Getting Started with VxVM The following topics are covered in this chapter: ◆ Starting the VEA Service ◆ Starting the VEA Client ◆ Using Hot-Relocation ◆ Enabling Cluster Support in VxVM ◆ Configuring Shared Disks ◆ System Setup Guidelines ◆ Protecting Your System and Data ◆ Working With VxVM 3.
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.
Using Hot-Relocation Confirming that VxVM Processes are Running After VxVM has been successfully installed or upgraded, use the following command to confirm that key VxVM processes (vxconfigd, vxnotify, and vxrelocd) are running: # ps -ef | egrep vx This command displays output similar to the following: root 18 0 root 20 0 root 324 316 root 316 0 /etc/vx/bin/vxrelocd root 253 1 root 4033 3997 0 0 0 0 Apr Apr Apr Apr 19 19 19 19 ? ? ? ? 412:53 0:00 0:00 0:00 0 1 Apr 19 ? 0:00 14:40:50 pts/0 0:00 vxi
Enabling Cluster Support in VxVM To disable hot-relocation, you comment out the vxrelocd line in the startup file /etc/rc2.d/S95vxvm-recover, as follows: # nohup vxrelocd root & Refer to the Volume Manager Administrator’s Guide for more information on hot-relocation. 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.
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 1. Place disks under VxVM control. 2.
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, VERITAS Volume Manager keeps track of the regions within a volume that have changed as a result of writes to a plex. VERITAS 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.
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: ◆ Only one RAID-5 plex can exist per RAID-5 volume (but there can be multiple log plexes).
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.
Working With VxVM 3.5 Root Disks Working With VxVM 3.5 Root Disks This section describes: ◆ Adding Dump Volumes Using Volume Manager Disks ◆ Changing the Boot Disk to be the New Volume Manager Root Disk ◆ Removing a Mirrored Volume Manager Root Disk 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. 1. Remove a disk from LVM control.
Adding Swap Space Using VxVM Volumes 3. Change primary boot path back to current boot device: # setboot -p device_path_from_above (Use -a if you want to change the alternate bootpath.
Adding Swap Space Using VxVM Volumes 5. Run the commands: # vxassist make swapvol2 4191378 swapdisk # echo "/dev/vx/dsk/rootdg/swapvol2 ... swap pri=1 0 0" >>/etc/fstab 6. Use SAM to: a. Increase the maxswapchunks tunable as required by swapon. b. Build a the kernel. c. Reboot your system.
Adding Swap Space Using VxVM Volumes 70 VERITAS Volume Manager Installation Guide
6 Deinstalling the VERITAS Volume Manager The following topics are covered in this chapter: ◆ ◆ Preparing to Remove VxVM - Preparatory Steps - Moving Data Out of VxVM Control Shutting Down and Removing VxVM - Shutting Down VxVM - Removing the VxVM Package 71
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.
Preparing to Remove VxVM # vxassist mirror volume layout=contig # vxplex -o rm dis plex_name Note This operation does not work if you do not have sufficient space on another disk. ◆ Modify /etc/fstab to mount all file systems using a partition or logical volume instead of a VxVM volume. Update /etc/fstab for volumes that are not on rootdg. Moving Data Out of VxVM Control Before removing the VxVM, all the VxVM volumes must be moved to LVM disks.
Shutting Down and Removing VxVM Shutting Down and Removing VxVM To deinstall VxVM, you must move all VxVM volumes to LVM disks. This can be done using one of the following three methods: ◆ 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.
Shutting Down and Removing VxVM g. Mount the logical volume if the corresponding volume was previously mounted. h. Remove the volume from Volume Manager control using the following command: # vxedit -rf rm volume_name i. Remove any free disks (without subdisk definitions) by removing volumes from Volume Manager control. To check if subdisks remain on a disk, use the following command: # vxprint -F “%sdnum” diskname If the output is other than 0, some subdisks remain on this disk and must be removed.
Shutting Down and Removing VxVM The host will now reboot. Errors that occur during the software removal process are due to the following: ◆ the system contains open volumes ◆ the root disk is under VxVM control For more information, select the Logfile button in the user interface to check the log file /var/adm/sw/swagent.log .
