Veritas Volume Manager 5.0 Release Notes HP-UX 11i Version 2 Second Edition Manufacturing Part Number: 5900-0593 March 2010 © 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.
Preface The Veritas Volume Manager 5.0 Release Notes provides information on the September 2006 release of Volume Manager. Publication 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.
For latest information on available patches visit: • http://itrc.hp.com For technical support visit: • http://welcome.hp.com/country/us/en/support.html Typographic Conventions Table 1 describes the typographic conventions used in this document. Table 1 Typographic Conventions Typeface monospace Usage Computer output, files, directories, software elements such as command options, function names, and parameters Examples Read tunables from the /etc/vx/tunefstab file.
Related Documentation For more information about Veritas 5.0 products, see the following documents located in the /usr/share/doc directory: Veritas 5.0 Installation Guide • Veritas File System 5.0 Release Notes • Veritas File System 5.0 Administrator’s Guide • Veritas Volume Manager 5.0 Administrator’s Guide • Veritas Volume Manager 5.0 Troubleshooting Guide • Veritas Volume Manager 5.0 Migration Guide • Veritas Volume Manager 5.
1 Veritas Volume Manager 5.0 Release Notes This document provides information on Veritas Volume Manager 5.0. The Veritas Volume Manager 5.0 is supported on HP-UX 11i Version 2 September 2006. The following topics are discussed: • Product Description • New Features in VxVM 5.
Veritas Volume Manager 5.0 Release Notes New Features in VxVM 5.0 imported successfully. Because using the -f option to forcibly import an incomplete disk group counts as a successful import, the disk group can subsequently be imported without specifying this option. • Faster startup time The time required to start the Veritas Volume Manager configuration daemon, vxconfigd, to discover new devices, to initialize dynamic multipathing, and import disk groups has been significantly reduced.
Veritas Volume Manager 5.0 Release Notes New Features in VxVM 5.0 NOTE • The SCSI 3 PR enhancements are not available with Base-VxVM and Full VxVM bundles.To enable this feature, an additional license is required. File-level SmartSync The SmartSync feature of VxVM has been extended to support Oracle Resilvering of files in Veritas File System.
Veritas Volume Manager 5.0 Release Notes New Features in VxVM 5.0 • Linked break-off snapshot volumes A new variant of the third-mirror break-off snapshot type is linked break-off snapshot volumes, which use the vxsnap addmir command to link a specially prepared volume with the data volume. The volume that is used for the snapshot is prepared in the same way as for full-sized instant snapshots.
Veritas Volume Manager 5.0 Release Notes Unsupported Features Disks that have been duplicated outside the VxVM environment (usually using specialized hardware) are referred to as cloned disks. The vxdisk and vxdg commands have been enhanced to allow such cloned disks to be identified, tagged, and more easily managed. For example, a subset of the disks in a disk group that are similarly tagged can be imported together in a single operation.
Veritas Volume Manager 5.0 Release Notes Features Requiring Special Licenses • Veritas Cluster Server (VCS) Features Requiring Special Licenses • The FlashSnap (FastResync and Dynamic Disk Group Split and Join and Storage Checkpoints). • The Veritas Cluster File System(CFS) • Quicklog • Cluster Volume Manager (CVM) Features of Base-VxVM Compared to LVM The Veritas Volume Manager 5.
Veritas Volume Manager 5.0 Release Notes Veritas Base-VXVM 5.0 Licenses Veritas Base-VXVM 5.0 Licenses The following table shows the supported features available with Veritas Volume Manager 5.
Veritas Volume Manager 5.0 Release Notes VEA Graphical User Interface and SAM Table 1-2 (Continued) Feature Veritas Volume Manager 5.
Veritas Volume Manager 5.0 Release Notes Coexistence with HP Logical Volume Manager (LVM) Coexistence with HP Logical Volume Manager (LVM) The Veritas Volume Manager for HP-UX coexists with HP Logical Volume Manager (LVM). Both LVM and Base-VXVM utilities are aware of the other volume manager, and will not overwrite disks that are being managed by the other volume manager. As mentioned above, the administrative utilities (SAM and VEA) recognize and identify all disks on the system.
Veritas Volume Manager 5.
Veritas Volume Manager 5.0 Release Notes Known Issues • Array Support Libraries Release 5.0 of VxVM will attempt to detect and obsolete any pre-5.0 array support library (ASL) packages. Once the upgrade is complete, you should not see these ASL packages in the swlist ouput. If the upgrade fails , please use the following command to remove these obsoleted ASL packages: #swremove • HPVM Software Installation Requirements with VxVM 5.0 If VxVM 5.
Veritas Volume Manager 5.0 Release Notes Known Issues If a volume in a Remote Mirror configuration has detached plexes, at a remote site, you can use the following procedure to resize it: 1. Turn off the allsites attribute for the volume: # vxvol -g diskgroup set allsites=off volume 2. Remove the detached plexes # vxassist -g diskgroup remove mirror volume plexnames=plex1,plex2,... 3. Use the vxresize command to resize the volume. When the remote site comes back up: a.
Veritas Volume Manager 5.0 Release Notes Known Issues The mirror is added, but the log is silently omitted. To add a log and a mirror, add them in two separate vxassist invocations, as follows: # vxassist mirror volume ... # vxassist addlog volume ... 7. Using vxdiskadm to replace a failed disk 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.
Veritas Volume Manager 5.0 Release Notes Known Issues # vxvol -g mydg init zero vol-L01 # vxvol -g mydg init zero vol-L02 10. Growing or shrinking layered volumes Due to the current implementation of a resize of layered volumes, it is recommended that you do not grow or shrink layered volumes (for example, stripe-mirror or concat-mirror) during resynchronization. This limitation does not apply to ISP layered volumes.
Veritas Volume Manager 5.0 Release Notes Known Issues There is no option in the vxddladm command to display the current naming scheme. The naming scheme that is in operation can be deduced from the output to the vxdisklist command. • vxdiskadm displays error V-5-1-9764 when excluding devices The vxdiskadm operation displays error V-5-1-9764 if a vendor and product ID combination are specified to exclude devices from multipathing. This error is harmless and can be ignored.
Veritas Volume Manager 5.0 Release Notes Known Issues Unlike the VxVM I/O daemons, DMP daemons, which are also kernel threads, appear in the output from the ps command as they have an associated process table entry. This difference in behavior is harmless.
Veritas Volume Manager 5.0 Release Notes Known Issues Hot-Relocation Issues • Impact of hot-relocation on performance Except for rootvol and swapvol, hot-relocation does not guarantee the same layout of data or performance after relocation. It is therefore possible that a single subdisk that existed before relocation may be split into two or more subdisks on separate disks after relocation (if there is not enough contiguous space on a single disk to accommodate that subdisk).
Veritas Volume Manager 5.0 Release Notes Known Issues # vxdisk scandisks All the nodes should now be using the primary path. [579536] • Volume persists in SYNC state If a node leaves the cluster while a plex is being attached to a volume, the volume can remain in the SYNC state indefinitely.
Veritas Volume Manager 5.0 Release Notes Known Issues • Setting site consistency on a volume The vxvol command cannot be used to set site consistency on a volume unless sites and site consistency have first been set up for the disk group. [530484] • Adding a remote mirror Adding a remote mirror to a new site for a site-consistent volume does not also create a DRL log plex or a DCO plex at that site.
Veritas Volume Manager 5.0 Release Notes Known Issues Use -f flag to move all such the volumes turning off allsites flag on them. The volume(s) with allsites flags are being moved to the target disk group that doesn’t have any site records. Use -f flag to add all such volumes turning off allsites flag on them. Workaround: The suggested workaround is to ensure that allsites=off is set on all the volumes that are being moved between disk groups: 1.
Veritas Volume Manager 5.0 Release Notes Known Issues Inconsistencies can arise in point-in-time copies if any of the following snapshot operations are performed on a volume while a file system in the volume is being mounted: vxassist snapshot, vxplex snapshot, vxsnap make, vxsnap refresh, or vxsnap restore. • Cache volumes in volume sets Do not add cache volumes (used by space-optimized instant snapshots) to volume sets. This causes data corruption and system panics.
Veritas Volume Manager 5.0 Release Notes Known Issues • Volumes not started following a reboot During very fast boots 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. Workaround: Check the state of the volumes before starting the application, or place a sleep (sleep sec) before the last invocation of vxrecover.
Veritas Volume Manager 5.0 Release Notes Known Issues The vxdg command deport operation is known to fail intermittently because VxVM daemons may still be accessing the disk group (for a few seconds) to handle configuration backup. This is a transient situation.
Veritas Volume Manager 5.0 Release Notes Known Issues For VEA to operate successfully, the name service switch configuration file, /etc/nsswitch.conf, must be present on the system. See the nsswitch.conf (4) manual page. • Setting a comment on an ISP volume If you create a new ISP volume by right-clicking on a user template and selecting the New Volume menu item, a comment that you specify to the Create Volume Dialog is not set on the volume.
Veritas Volume Manager 5.0 Release Notes Known Issues Controller states may be reported as Not Healthy when they are actually healthy, and Healthy when they are actually not healthy. • Remote Mirror (campus cluster) There is no option to create site-based snapshots. [541104] • Action pull-down menu items No Action pull-down menu items exist for the Layout View, the Disk View, or the Volume View. [596284] • Java exception error in the Statistics View A Java exception error occurs in the Statistics View.
Veritas Volume Manager 5.0 Release Notes Known Issues • Maximum size of a volume The maximum size of a volume is shown as a rounded-down integer number of gigabytes. If the maximum size is less than 1GB, the maximum size is shown as 0GB.
Veritas Volume Manager 5.0 Release Notes Known Issues The create disk group wizard shows internal disks as being available for the creation of shared disk groups. [574717] • Object not found error on creating a volume set An object not found error may be displayed when a volume set is created. [615960] • Java exception when deleting a volume Deleting a volume that has just been deleted produces a Java exception.
Veritas Volume Manager 5.0 Release Notes Known Issues As a work around for this problem, complete the following steps: # rm /var/vx/isis/vxisis.lock # /opt/VRTSob/bin/vxsvcctrl start 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.
Veritas Volume Manager 5.0 Release Notes Known Issues To see the current cluster protocol version, type: # vxdctl support To upgrade the protocol version for the entire cluster, enter the following command on the master node: # vxdctl upgrade See the Administering Cluster Functionality chapter of the Veritas Volume Manager 5.0 Administrator’s Guide.
