Veritas 4.1 Installation Guide HP-UX 11i v3 HP Part Number: 5991–6383 Published: February 2007 Edition: 1.
© Copyright 2007 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About this Document..........................................................................................................9 Intended Audience.................................................................................................................................9 Document Organization.........................................................................................................................9 Typographic Convention.....................................................
Supported Upgrade Paths for VxFS 4.1 and VxVM 4.1........................................................................22 3 Installing the Veritas 4.1 Suite of Products.................................................................25 Mounting the media.............................................................................................................................25 Installing VxFS 4.1............................................................................................................
Upgrading VxFS Disk Layout......................................................................................49 Upgrading VxFS 3.5 on HP–UX 11i Version 2 to VxFS 4.1 on HP–UX 11i Version 3...........................49 Upgrading VxFS 4.1 on HP–UX 11i Version 2 to VxFS 4.1 on HP–UX 11i Version 3...........................50 6 Migrating to VxVM 4.1 on HP-UX 11i v3..................................................................51 Converting Unused LVM Physical Volumes to VxVM Disks......................
List of Tables 1 2 1-1 2-1 2-2 2-3 2-4 2-5 4-1 4-2 6-1 6-2 6-3 6-4 A-1 A-2 Document Organization..................................................................................................................9 Publishing History........................................................................................................................10 Supported File Systems on HP-UX 11i Version 3..........................................................................17 Base-VXFS 4.1 Bundle Components.....
About this Document This document provides information on Veritas Volume Manager 4.1 and Veritas File System 4.1 on HP-UX 11i Version3. Intended Audience This document is intended for system administrators responsible for installing and configuring UNIX systems with the Veritas suite of products.
In command synopsis, brackets indicates an optional argument. [ ] ls [ -a ] | In command synopsis, a vertical bar separates mutually exclusive arguments. mount [ suid | nosuid ] blue text An active hypertext link In PDF and HTML files, click on the links to move to the specified location. Related Documentation For more information on the Veritas 4.1 suite of products, refer to the following documents available at http://docs.hp.com: • • • • • • Veritas File System 4.
• For latest information on available patches see: http://itrc.hp.com • For technical support see: http://welcome.hp.com/country/us/en/support.html HP Encourages Your Comments HP encourages your comments concerning this document. Please use the feedback form available at the following location to provide your valuable suggestions: http://docs.hp.com/en/feedback.
1 Product Overview HP-UX 11i Version 3 is the new enterprise operating system from Hewlett-Packard. The Veritas File System (VxFS) 4.1 and Veritas Volume Manager (VxVM) 4.1 from Symantec Corporation constitute a suite of products referred to as the Veritas 4.1 in this document. Veritas Volume Manager (VxVM) 4.1 is a storage management subsystem that allows you to manage physical disks as logical devices called volumes. A volume is a logical device that appears to a data management system as a physical disk.
• Mirrored Stripes VxVM supports a combination of mirroring and striping. • Striped Mirrors VxVM supports a combination of striping and mirroring. • RAID-5 RAID-5 provides data redundancy using parity. • Online Resizing of Volumes You can dynamically resize VxVM volumes while the data remains available to the user. • Hot-relocation The hot-relocation feature in VxVM automatically detects disk failures, and notifies the system administrators of the failure, by electronic mail.
VxVM Daemons VxVM relies on the following daemons for its operation: • • • vxconfigd – The VxVM configuration daemon maintains disk and disk group configuration information, communicates configuration changes to the kernel, and modifies configuration information stored on the disks. vxiod – The VxVM I/O daemon provides extended I/O operations without blocking calling processes.
Non-Layered In a non-layered volume layout, a subdisk maps directly to a VM disk. This allows the subdisk to define a contiguous extent of storage space backed by the public region of a VM disk. Layered Volumes A layered volume is constructed by mapping its subdisks to underlying volumes. The subdisks in the underlying volumes must map to VM disks, and hence to the attached physical storage.
after a failure. If a portion of a RAID-5 volume fails, the data that was on that portion of the failed volume can be recreated from the remaining data and parity information. It is also possible to mix concatenation and striping in the layout.
mission-critical applications, where high availability is required. It increases I/O and provides structural integrity. The Veritas File System version 4.1 (VxFS 4.1) is the vxfs file system for HP-UX 11i Version 3 release. VxFS Features VxFS has the following features: • Extent-based Allocation An extent is defined as one or more adjacent blocks of data within the file system. VxFS allocates storage in groups of extents rather than a block at a time thereby resulting in faster read-write operations.
• Extended Mount Options The extended mount options supported by VxFS include the following: — — — — — • Enhanced data integrity modes Enhanced performance modes Temporary file system modes Improved synchronous writes Large file sizes Large File and File System Sizes File systems up to 32 TB and files up to 16 TB in size are supported on HP-UX 11i Version 3. See the white paper “Supported File and File System Sizes” available at http://docs.hp.
The various VxFS on-disk structures are: • Superblock Superblock (SB) resides ~8k from the beginning of the storage and tracks the status of the file system. Supports maps of free space and other resources (inodes, allocation units, and so on). • Intent Log VxFS reduces system failure recovery time by tracking file system activity in the VxFS intent log. This feature records pending changes to the file system structure in a circular intent log.
2 System Requirement This chapter discusses the various hardware and software requirements for the Veritas 4.1 suite of products. The following disk arrays, JBODs, Servers and 3rd Party Array products are supported by the Veritas 4.1 suite of products. Hardware Configuration Supported For information on supported disk arrays, JBODs, third party arrays products and other supported hardware VxFS 4.1 and VxVM 4.1 on HP-UX 11i Version 3, see “Hardware Support Matrix For VxFS 4.1 and VxVM 4.
Table 2-2 Base-VXVM 4.1 Bundle Components (continued) Bundle Description VRTSvmpro VERITAS Volume Manager Management Services Provider VRTSvmdoc VERITAS Volume Manager Documentation VRTSvlic VERITAS License Utilities VRTSobgui VERITAS Enterprise Administrator VRTSob VERITAS Enterprise Administrator Service VRTSfspro VERITAS File System Management Services Provider License Bundles Following license bundles are available for the Veritas 4.
Table 2-5 Supported upgrade paths (continued) S.No. From To Supported/Not Supported 3 VxFS 3.5/VxVM 3.5 on HP-UX 11iv2 VxFS 4.1/VxVM 4.1 on HP-UX 11iv3 Supported (But VxFS DLV must be minimum 4.) 4 VxFS 4.1/VxVM 4.1 (Without Cluster VxFS 4.1/VxVM 4.1 on HP-UX Support) on HP-UX 11iv2 11iv3 Supported 5 VxFS 4.1 /VxVM 4.1 on HP-UX (With VxFS 4.1/VxVM 4.1 on HP-UX Cluster Support) 11iv3 Not supported 6 VxFS 5.0/VxVM 5.0 (Without Cluster) VxFS 4.1/VxVM 4.
3 Installing the Veritas 4.1 Suite of Products This chapter discusses the installation steps for the Veritas 4.1 suite of products on HP-UX 11i Version3. Mounting the media For a media based installation, you must mount the media before starting the installation process. Mount the media as follows: 1. Insert the media into the drive and log in as root: $ su root See su (1), for more information on the supported options. 2.
Verifying Base-VXFS 4.1 Installation Verify the Base-VXFS 4.1 installation on your system: # swverify Base-VXFS See swverify (1M), for more information on the supported options. Installing HP OnlineJFS (B3929EA) 4.1 The HP OnlineJFS (B3929EA) license enables additional VxFS functionality not available with Base-VXFS 4.1. You can install HP OnlineJFS (B3929EA) 4.1 either in the non-interactive or in the interactive mode. Installing HP OnlineJFS (B3929EA) 4.
See swinstall (1M), for more information on the supported options. 2. 3. Mark the Base-VXVM bundle on the SD Install Window. Select Actions, and click Install. Follow the on-screen instructions to complete the installation. Verifying the Base-VXVM Installation Verify the Base-VXVM 4.1 installation on your system: # swverify Base-VXVM See swverify (1M), for more information on the supported options.
des=:/HPUX11i-OE-MC 4. Set the variable rem_sw to the software to be removed: rem_sw= 2. Copy the existing depot to the location of the VERITAS-4.1 depot: # swcopy -s $src \* @ $des 3. Remove the software listed in rem_sw: # swremove $rem_w @ $des 4. Copy the new software provided with the VERITAS-4.1 into the new depot. # swcopy -s $src_VERITAS-4.1 \* @ $des This results in the full VERITAS-4.1 depot. 5. Install the new VERITAS-4.
4 Setting up the Veritas 4.1 Products This chapter discusses the basic steps for initializing and setting up VxVM 4.1 and VxFS 4.1. For more detailed information on VxVM and VxVM administration refer to the following documents available at http://docs.hp.com: • Veritas Volume Manager 4.1 Administrator's Guide • Veritas File System 4.1 Administrator's Guide Setting up and managing VxVM 4.1 Initializing VxVM using vxinstall You can use the vxinstall utility to initialize VxVM.
NOTE: In releases prior to VxVM 3.5, the default disk group was rootdg (the root disk group). For VxVM 3.5 to function, the rootdg disk group had to exist, and it had to contain at least one disk. This is no longer required in VxVM 4.1. However, you can still create a root disk group as a system wide default disk group. For operations that require a disk group, the system wide default disk group is used if the VxVM command do not explicitly mention the disk group with the -g option.
• • If the disk was previously in use by the LVM subsystem, you can preserve existing data while still letting VxVM take control of the disk. This is accomplished using the conversion utility vxvmconvert. If the disk was previously in use by the LVM subsystem, and you do not want to preserve the data on it, use the LVM command, pvremove before attempting to initialize the disk for VxVM. Multiple disks on one or more controllers can be placed under VxVM control simultaneously.
See vxdg (1M), for more information on the supported options. • Creating Disk Groups You can create a disk group in one of the following ways: — — Use option 1 (Add or initialize one or more disks) of the vxdiskadm command Use vxdiskadd command. # vxdiskadd See vxdiskadd (1M), for more information on the supported options. — Use the vxdg init command: # vxdg init [cds=on|off] diskname= See vxdg (1M), for more information on the supported options.
See vxdg (1M), for more information on the supported options. — Rename a Disk Group During Deport Rename a disk group during deport: # vxdg [-h hostname] -n newdg deport See vxdg (1M), for more information on the supported options. When renaming on deport, you can specify the -h hostname option to assign a lock to an alternate host. This ensures that the disk group is automatically imported when the alternate host reboots.
• Reorganizing Disk Group Content This option is not supported with the VxVM 4.1 release on HP-UX 11i Version3. • Upgrading Disk Group All disk groups have a version number associated with them. Veritas Volume Manager releases support a specific set of disk group versions. VxVM can import and perform operations on a disk group of that version. The operations are limited by the features supported by the specific disk group version.
Use the vxnotify command as follows: vxnotify [-ACcdefimr] -g -n -t -w See vxnotify (1M), for more information on the supported options. • Removing Disks From Disk Group Remove disks from Disk Group: # vxdg -g rmdisk See vxdg (1M), for more information on the supported options. Subdisks Subdisks are low-level building blocks in a Veritas Volume Mananger (VxVM) configuration that are required to create plexes and volumes.
Join several subdisks: # vxsd -g join ... See vxsd (1M), for more information on the supported options. • Associating Subdisks Associating a subdisk with a plex places the amount of disk space defined by the subdisk at a specific offset within the plex. The entire area that the subdisk fills must not be occupied by any portion of another subdisk.
You can do the following operations on plexes: • Creating Plexes You can create plexes in one of the following ways: — Creating simple plexes Use the vxmake command to create VxVM objects, such as plexes. When creating a plex, identify the subdisks that are to be associated with it. Create a plex from existing subdisks: # vxmake -g plex sd= See vxmake (1M), for more information on the supported options.
You can set the plex to the ACTIVE state in one of the following ways: — Reattach a plex to a volume that is currently in ENABLED state: # vxplex -g att See vxplex (1M), for more information on the supported options. — Reattach a plex to a volume that is currently not in use (not ENABLED): # vxmend -g on See vxmend (1M), for more information on the supported options.
You can do the following operations on volumes: • Determining the Maximum Size of a Volume Determine the maximum size of a volume: # vxassist -g maxsize layout= See vxassist (1M), for more information on the supported options. • Creating volumes You can create volumes in two ways: — — Assisted Approach Advanced Approach Assisted Approach Assisted approach is based on the vxassist command.
Table 4-2 Following types of volume creation operations are supported: (continued) Volume Creation Task Description Syntax Creating Dirty Region Enables (DRL) Volumes Dirty Region Logging (DRL), if enabled, speeds recovery of mirrored volumes after a system crash. # vxassist -g make volume length layout=layout \ logtype=drl [nlog=n] [loglen=size] [other attributes] A striped volume contains at least one plex that consists of two or more subdisks located on two or more physical disks.
3. Associate plexes with the volume using vxmake vol. See vxmake (1M), for more information on the supported options. 4. Initialize the volume using vxvol start or vxvol init zero. See vxvol (1M), for more information on the supported options. • Displaying Volume Information You can display the volume, plex, and subdisk information for all volumes in the system.
# vxassist [ options] -b convert See vxassist (1M), for more information on the supported options. • Relayout Volumes Relayout changes the volume layout and properties. The change affects the number of columns in a stripe or the stripe width of a volume. It also converts a volume to or from RAID-5, concatenated-mirror, striped, striped-mirror or any similar layout.
# /opt/VRTSob/bin/vxsvcctrl start See vxsvcctrl (1M), for detailed description of the supported options. NOTE: Stop the VEA service later: # /opt/VRTSob/bin/vxsvcctrl stop Setting Up a Veritas Enterprise Administrator (VEA) Client To run VEA and administer a local or remote system, ensure that you have sufficient privileges. Also, ensure that the VxVM and the VEA server are installed on the same machine to be administered and that the vxconfigd daemon and the VEA server are running.
After logging in, go to the “Disk and File Systems” section under “System Configuration” menu. 44 Setting up the Veritas 4.
Invoke Veritas Enterprise Administrator (VEA) from the link provided on the right navigation bar of the “Disk and File System Tools” Screen as shown below: NOTE: You must have an X-client running on your system to invoke VEA. You can create and administer VxVM and VxFS once you have logged into VEA. See “Veritas Enterprise Administrator (VEA) Getting Started Guide”, for more information on using VEA. Setting up and managing VxFS 4.
Mounting a VxFS File System Mount a vxfs file system: # mount -F vxfs [generic_options] [-r] [-o specific_options] special See mount_vxfs (1M), for detailed description of the supported options. Displaying Information on Mounted File System View the status of mounted file systems: # mount -v See mount (2), for detailed description of the supported options.
See the edquota (1M), quota (1M), quotaon (1M), and quotaoff (1M), for more information on using quotas with files. Unmounting a VxFS File System Use the umount command to unmount a file system: umount special | mount_point Specify the file system to be unmounted as a mount_point or special (the device on which the file system resides. See umount(2), for detailed description of the umount command. Setting up and managing VxFS 4.
5 Upgrading VxFS Disk Layout This chapter discusses the following VxFS upgrade paths: • • “Upgrading VxFS 3.5 on HP–UX 11i Version 2 to VxFS 4.1 on HP–UX 11i Version 3” “Upgrading VxFS 4.1 on HP–UX 11i Version 2 to VxFS 4.1 on HP–UX 11i Version 3” NOTE: • The HP-UX 11i boot loader requires the boot file system (if a vxfs file system) on disk layout version 5 or less. The boot file system, usually mounted under /stand or /, contains the HP-UX boot kernel.
5. VxFS file systems with disk layout 4, and 5 can be mounted with VxFS 4.1. However, to upgrade the disk layout version of mounted file systems to 6, use the vxupgrade command as follows: 1. Upgrade a mounted VxFS file system from disk layout 4 to disk layout 6: # vxupgrade -n 5 # vxupgrade -n 6 See vxupgrade (1M), for detailed description of the supported options. 2.
6 Migrating to VxVM 4.1 on HP-UX 11i v3 HP-UX 11i v3 supports the volume managers, HP LVM and Veritas Volume Manager (VxVM) from Symantec Corporation. You can use LVM with VxFS or you can migrate to VxVM.
vxvmconvert command, the only possible method of conversion is to take full backup of user data, destroy the existing LVM configuration leaving only raw disks, recreate the configuration in VxVM, and then reload the user data. The vxvmconvert process converts LVM volume groups to VxVM disk groups in place.
NOTE: • For user data backup, use your regular backup processes. • For file system back up use the utility fbackup (1M) to backup the data to tape. • For application backup use the backup facilities provided by the application. If no such facility exists, consider using the dd command. 6. Stopping Application Access to Volumes in the Volume Group to be Converted Before attempting to convert any volume group, you must ensure that applications using that group are shut down.
1. Restore LVM internal data: # vgrestore See vgrestore (1M), for detailed description of the supported options. 2. Restore user or application data : # mount -F vxfs See mount (2), for detailed description of the supported options. # frecover -r -f See frecover (1M), for detailed description of the supported options. Conversion Speed Factors affecting conversion speed are: • • • • Size of volume groups.
Table 6-2 Command Comparison (continued) LVM Description/Action VxVM Description/Action lvremove Removes one or more logical volumes from a volume group. vxedit Removes volumes with the -rf rm parameters. vxassist vxedit -rf rm Removes a volume with the remove volume parameters. vxassist remove volume lvsplit Splits a mirrored logical volume into two logical volumes.
Table 6-2 Command Comparison (continued) LVM Description/Action VxVM pvmove Moves allocated physical vxevac extents from source to vxsd mv destination within a volume vxdiskadm group. Description/Action Moves volumes off a disk. Performs volume operations on a subdisk. Moves the contents of old subdisk onto the new subdisks and replaces old sub disk with the new subdisks for any associations. The vxdiskadm script presents a menu of possible operations to the user.
Table 6-2 Command Comparison (continued) LVM Description/Action vgremove Removes the definition of a vxdg deport volume group from the vxdiskadm system. Deports a disk group from the system. Removes a volume group from the system. Deports a disk group from the system. vgexport VxVM Description/Action vxdg deport vxdiskadm Use option 9 in the vxdiskadm menu to remove a disk group. Use option 9 in the vxdiskadm menu to remove a disk group.
Table 6-3 LVM and VxVM Task Comparison (continued) Task Type LVM Description Example Task Type Description Extend a logical volume or increase space allocated to a logical volume. lvextend -l 50 /dev/vol_grp/lvol_name VxVM Increase the vxresize -g volume by or to -F vxfs a given length.
Table 6-3 LVM and VxVM Task Comparison (continued) Task Type LVM Description Example Task Type Description Example Increase or decrease secondary swap space. lvextend—to increase swap space VxVM Add a new swap volume vxassist make VxVM Add one or vxdiskadd more disks to the disk group. Option 1 in the vxdiskadm main menu performs this task. VxVM Remove a disk from disk group.
Table 6-3 LVM and VxVM Task Comparison (continued) Task Type Description Example Task Type Description Example Mirroring an LVM root disk involves several steps. 1. pvcreate -B /dev/rdsk/ VxVM Mirroring the VxVM root disk.
Table 6-3 LVM and VxVM Task Comparison (continued) Task Type Task Type Description Example vgreduce Remove disks from a /dev/ /dev/dsk/ volume group or reduce the number of disks in the volume group. VxVM Remove disks from a disk group. vxdg rmdisk LVM Remove an entire volume group. Before attempting to remove the volume group, you must remove the logical volumes using lvremove, and all physical volumes except the last one using vgreduce.
Table 6-3 LVM and VxVM Task Comparison (continued) Task Type LVM Description Example Task Type Description Example Reduce a single/double mirrored logical volume to an unmirrored logical volume. lvreduce -m 0 /dev/vol_grp/mirr_lv VxVM Remove mirrors or reduce the number of plexes/mirrors. vxplex -o rm dis lvremove /dev/vol_grp/ vxedit -rf rm Remove a volume with the plexes associated with it. Remove a mirrored logical volume.
Table 6-3 LVM and VxVM Task Comparison (continued) Task Type Description LVM LVM Example Synchronize vgsync /dev/ extents within mirrored logical volumes in a volume group. Start a volume. Task Type Description Example VxVM Resynchronize vxrecover -s operations for the named volumes, or for volumes residing on the named disks. If no medianame or volume operands are specified, then the operation applies to all volumes.
• Replace a disk: Use option 4 of vxdiskadm. • Recover volumes on a disk: vxrecover -g See vxrecover (1M), for detailed description of the supported options. • Rename a disk group: vxdg -tC -n import See vxdg (1M), for detailed description of the supported options. • Rename a volume: vxedit -v rename See vxedit (1M), for detailed description of the supported options. Update the /usr/fstab file with the new name.
Table 6-4 LVM Features and VxVM equivalents LVM Feature VxVM Equivalent Physical volume groups VxVM has no equivalent feature. The disk group feature of VxVM combines the logical volume group (VG) and physical volume group (PVG) of LVM. Powerfail timeout feature: Automatically re-enable a disk or a path to a disk, after temporary error condition (resulting in EPOWERF error on I/Os) disappears on that disk or path.
7 Removing Veritas 4.1 Products This chapter discusses the steps for removing the Veritas 4.1 suite of products from an HP-UX 11i Version3 system, using the HP-UX SD commands. Removing VxVM VxVM 4.1 can be removed from systems only where the root disk is under HP Logical Volume Manager (LVM) control. If you try to remove VxVM 4.1 software from your system without completing the following steps, you will lose data and your system will be in an unstable state.
# vxprint -F “%sdnum” diskname If the output is 0, remove the disk from Volume Manager control: # vxdg rmdisk diskname See vxdg (1M), for detailed description of the supported options. # vxdisk rm devname See vxdisk (1M), for detailed description of the supported options. If the output is not 0, remove sub-disks from the disk and then remove the disk. 10. Copy the data in the next volume to be removed to the newly created free space. 11.
8 VxVM 4.1, New Style DSFs and HP-UX Native Multipathing Introduction HP-UX 11i v3 introduces a new representation for the mass storage devices called the agile view. The central idea behind the agile view is that the disk devices and tape drives are identified by the actual object, and not by a hardware path to the object. Legacy View (Old Style DSFs) Prior to HP-UX 11iv3, DSFs for mass storage devices had their hardware path, or lunpath, encoded in their name and their minor number.
• • • • • • appropriate physical path. Unless all the underlying physical paths of the native multipathing metanode fail, any I/O that DMP performs on a legacy path succeeds. The output from the DMP vxdmpadm iostat command does not match the output from the native HP-UX iostat command. Using the vxdmpadm disable and vxdmpadm enable commands on a path or controller causes Veritas DMP to use another path for I/O, but HP-UX native multipathing still continues to send I/O to the disabled path or controller.
A Appendix The following topics are discussed here: • “Controlling Memory Utilization of VxFS 4.1 on HP-UX 11i v3” • “LVM Volume Groups to VxVM Conversion Error Messages” Controlling Memory Utilization of VxFS 4.1 on HP-UX 11i v3 Introduction VxFS 4.1 caches objects in memory to improve performance. Most of the memory consumed by VxFS is used to cache inodes (in the inode cache) and metadata (in the buffer cache). The cache size and VxFS behaviour is controlled by a set of tunables.
exposed to file server and web server loads, or when the file system performance is not critical, may not require a large inode cache. In such cases, vx_ninode can be tuned down by hand. It is recommended to use the following table to tune vx_ninode to a minimum value based upon memory size. HP recommends that you set a minimum value as specified below based upon the memory configuration. Table A-2 Physical Memory Vs.
• Device device_name has the following bad blocks... Cannot convert LVM Volume Group — Description Unlike LVM, VxVM does not support bad block revectoring at the physical volume level. If there appear to be any valid bad blocks in the bad block directory of any disk used in an LVM volume group, the group cannot be converted.
• Too many LVM Volumes to convert in this LVM Volume Group Description — Description If there is insufficient private space, the conversion is not allowed to continue. Also, the conversion records already generated are removed such that in the event of an unexpected crash and reboot, the conversion cannot proceed automatically. — • vgchange: Couldn't deactivate volume group /dev/vol_grp — Description The conversion process was unable to deactivate the volume group.
