Veritas Volume Manager 4.1 Release Notes HP-UX 11i Version 3 HP Part Number: 5900-0590 Published: March 2010 Edition: 2.
© Copyright 2010 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..........................................................................................................5 Intended Audience.................................................................................................................................5 Document Organization.........................................................................................................................5 Typographic Convention.....................................................
List of Tables 1 2 1-1 4 Document Organization..................................................................................................................5 Publishing History..........................................................................................................................6 Product License Requirement.........................................................................................................
About this Document This document provides information on Veritas Volume Manager 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.
• • Veritas Volume Manager 4.1 Troubleshooting Guide Veritas Enterprise Administrator (VEA 500 Series) Getting Started Guide Publishing History The manual publication date and part number indicate its current edition. The publication date will change when a new edition is released. The manual part number will change when extensive changes are made. To ensure that you receive the new editions, you should subscribe to the appropriate product support service. See your HP sales representative for details.
1 Veritas Volume Manager 4.1 Release Notes This document provides information on Veritas Volume Manager 4.1 (VxVM 4.1) on HP-UX 11i Version 3. The following topics are discussed: • • • • • • • • • • • “Product Description” “New Features in This Release” “Features not Supported” “Product Licensing” “VEA Issues” “Coexistence with HP Logical Volume Manager (LVM)” “Limitations of VxVM 4.
• Detecting and correcting the Serial Split Brain Condition in a Disk Group Serial Split Brain (SSB) checks for changes to disk group configuration copies and data. SSB checks are done, when a disk is added to a disk group or when a disk group is imported. SSB increments are done when a disk becomes non-available or when a disk group is imported with missing disks.
• • • • Cluster Volume Manager Cluster File System Multi-Device Support Instant Snapshot Product Licensing The following table lists the features available with Veritas Volume Manager 4.1 and the required licenses. Table 1-1 Product License Requirement VxVM License Description of Supported Features Base Concatenation, spanning, rootability and root disk mirroring, multiple disk groups and VEA.
HP Recommended Method For Dump/Swap Device Configuration On HP-UX 11i Version 3, crashconf (1M) is the preferred mechanism for marking VxVM logical volume as persistent and, crashconf (1M) should be used for any dump device configuration. The preferred swap configuration commands to be used are swapon (1M) and swapctl(2). System Requirement Following are the hardware and software requirements for VxVM 4.1 on HP-UX 11i Version 3.
Installation Issues Following installation issues are identified: • Mirror not Booted when VxVM is Started in HP-UX Maintenance Mode Boot (MMB) Problem HP-UX Maintenance Mode Boot (MMB) is used to recover from catastrophic failures that have prevented the target machine from booting. If a mirrored root is configured, when you boot in MMB, only one mirror is activated. Therefore, any writes to the root file system in MMB can cause root file system corruption later when both mirrors are configured.
• Using vxdiskadm to Replace a Failed Disk Problem The vxdiskadm command requires two attempts to replace a failed disk. The first attempt can fail with a message of the form: /usr/lib/vxvm/voladm.d/bin/disk.repl: test: argument expected Workaround The command is not completed and the disk is not replaced. If you rerun the command, using Option 5 of the vxdiskadm command, the replacement successfully completes.
After a layered volume is resized, the volume, plex and subdisk names associated with the subvolumes, are changed. • Problems with Relayout Using the vxassist Command Problem The vxassist relayout operation requires all mirrors in the volume to have the same layout Workaround If the volume contains mirrors with different layouts, then you need to relayout the mirror plexes to the same layout before performing the volume relayout operation.
# vxdctl enable This command updates the status of all the VxVM disks. NOTE: The vxdctl enable command initiates an entire disk device scan. Therefore the time VxVM takes to scan all of the devices in the environment of that particular host will increase as the number of devices increases. If you know which disk’s state has been changed, it is faster to use vxdisk online to update that disk only.
To recover these disks, run the vxdarestore command. See “Issues Regarding Persistent Simple/Nopriv Disks with Enclosure-Based Naming? in the Veritas Volume Manager 4.1 Administrator’s Guide and the vxdarestore (1M) manual page. • HDS9500V Array Support Library In VxVM 3.5, support for the Hitachi Data Systems HDS9500V array was provided by the VRTShds9500v Array Support Library (ASL). If the VRTShds9500v ASL is currently installed on your VxVM 3.
Data Integrity Issues Following data integrity issues are identified: • Disks with Write-Back Caches Exhibit Data Integrity Problems Problem Disk drives configured to use a write-back cache, or disk arrays configured with volatile write-back cache, exhibit data integrity problems. Workaround The problems occur after power failure, SCSI bus reset, or other event in which the disk has cached data, but has not yet written it to a non-volatile storage.
The Actions > Disk Mirror menu is incorrectly disabled if you do not have a Full VxVM license. Workaround Use the vxmirror command line to mirror the disk. • Name Service Switch Configuration File Problem For VEA to operate successfully, the name service switch configuration file, /etc/nsswitch.conf, must be present on the system. Workaround See nsswitch.conf (4) for more information. • Accessing the Task Log Problem The task log accessed from the Log tree is not supported. Workaround None.
If it is an absolute must that a disk group not be auto-imported when the system is rebooted, the disk group should be imported temporarily using the -t flag of the vxdg import command. • Volumes Not Started Following a Reboot Problem During fast system reboots, on a system with many volumes, vxconfigd may not be able to auto-import all of the disk groups by the time vxrecover -s is run to start the volumes. As a result, some volumes may not be started when an application starts after reboot.
Title:Veritas Volume Manager 4.1 Troubleshooting Guide 1. Chapter 2: Recovery from Failure of Instant Snapshot Operations. Ignore this content as it requires a separate FlashSnap license.
