Veritas Volume Manager 5.0 Release Notes HP-UX 11i v3 HP Part Number: 5992-1952 Published: August 2011 Edition: 3.
© Copyright 2011 Hewlett-Packard Development Company, L.P. 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.
Contents About this Document......................................................................................4 Intended Audience....................................................................................................................4 Document Organization............................................................................................................4 Typographic Conventions...........................................................................................................
About this Document This document describes the Veritas™ Volume Manager (VxVM) of the Veritas 5.0 product features supported on HP-UX 11i v3. It also describes product licensing, limitations, system requirements, upgrading disk groups and known problems with VxVM 5.0. Intended Audience This document is intended for system administrators responsible for installing and configuring UNIX systems with Veritas™ Volume Manager.
• Veritas Enterprise Administrator User's Guide • Veritas Storage Foundation 5.0 Cross-Platform Data Sharing Administrator’s Guide • Veritas Storage Foundation 5.0 Intelligent Storage Provisioning Administrator’s Guide • Veritas Storage Foundation 5.0 Intelligent Storage Provisioning Solutions Guide • Veritas Storage Foundation for Oracle 5.0 Release Notes • Veritas Storage Foundation 5.0 for Oracle Administrator’s Guide • Veritas Storage Foundation 5.
1 Veritas Volume Manager 5.0 Release Notes This chapter discusses new features, licenses, system requirements, compatibility with previous releases, and known problems with Veritas Volume Manager 5.0 which is supported on systems running HP-UX 11i v3. This chapter addresses the following topics: • “Product Description” • “New Features in This Release” • “Product Licensing” • “Limitations of VxVM 5.
• Default private region size The default size of the private region has been increased from 1 MB to 32 MB. However, the default size is still 1 MB for bootable disks, created with vxdisksetup -B. CAUTION: You must use vxdisksetup -B instead of running vxdisk -B init directly to initialize bootable disks as the latter command will take up the new default private region size (32 MB) that does not work for bootable disks.
• Enhancements to DMP The following enhancements have been done to the Dynamic Multi-pathing (DMP) feature: ◦ Faster failure detection and recovery by DMP DMP has been enhanced to allow the vxdmpadm command to be used to adjust the I/O error recovery and I/O throttling mechanisms on individual paths. ◦ Changing DMP tunables The values of most DMP tunables can now be set by using the vxdmpadm settune command.
• Disk Tags Disks can be tagged with an arbitrary tag name and optional tag value. Multiple tags can be associated with a single disk. Such tags are used by features such as Remote Mirror, Intelligent Storage Provisioning (ISP), and importing cloned disks. • Data Migration The vxassist, vxevac, and vxsd commands have been enhanced to allow data to be migrated at the volume, disk, or subdisk level respectively. Once the data migration is in the tentative state, it can either be committed or cancelled.
• Recommendation for Config Backup and Restore The Config Backup and Restore (CBR) feature of VxVM allows the disk group configuration to be backed up and restored if configuration information is lost or corrupted. The backup directory should be large enough to accommodate copies of all the disk groups present at any given point in time. With Veritas Volume Manager 5.
NOTE: You must install all the required licenses otherwise, you will not be able to use certain features of Veritas Volume Manager 5.0. Table 2 Feature Enabled by Full VxVM Only Feature Veritas Volume Manager 5.
Table 3 Features Enabled by SG-SMS Bundle (continued) VxVM Features T2771CB T2772CB T2773CB T2774CB T2775CB T2776CB T2777CB RAID5SNAP - This allows you to Yes split a volume comprising of two RAID-5 plexes.
Table 3 Features Enabled by SG-SMS Bundle (continued) VxVM Features T2771CB T2772CB T2773CB T2774CB T2775CB T2776CB T2777CB Dynamic LUN Expansion - online Yes LUN resize and automatic volume growth Yes Yes Yes Yes Yes Yes Import Cloned LUN on the same No host as the original LUN - used with ShadowCopies, BCVs, and so on.
• 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. • VxVM does not currently support RAID-5 volumes in cluster-shareable disk groups. System Requirements Following are the hardware and software requirements for VxVM 5.0 on HP-UX 11i v3. Supported Platforms The Veritas Volume Manager 5.0 is supported on all servers that support HP-UX 11i v3.
NOTE: System Administration Manager (SAM) is deprecated in HP-UX 11i v3. HP System Management Homepage (HP SMH) is the system administration tool for managing HP-UX. HP SMH provides systems management functionality, at-a-glance monitoring of system component health and consolidated log viewing. HP SMH provides Graphical User Interface (GUI), Text User Interface (TUI), and Command Line Interface (CLI) for managing HP-UX. You can access these interfaces using the /usr/sbin/smh command.
The output from the vxdisk list command now displays a list of devices following the agile naming scheme of the operating system instead of the DMP metanode names For example: # vxdisk list DEVICE TYPE disk155 auto:LVM disk156 auto:LVM disk224 auto:cdsdisk disk225 auto:cdsdisk disk226 auto:cdsdisk disk227 auto:hpdisk disk228 auto:hpdisk disk229 auto:hpdisk DISK - GROUP - STATUS LVM LVM online online online online online online This procedure essentially instructs DMP to bypass all auto-configured device
Prior to running this procedure, ensure that there are no applications accessing VxVM volumes and no file system is mounted on VxVM volumes. To migrate from HP-UX native multipathing to DMP, complete the following steps: 1. To stop all volumes in each disk group on the system, enter the following command: # vxvol –g diskgroup stopall 2. To initiate the migration, enter the following commands: # vxddladm rmforeign blockdir=/dev/disk chardir=/dev/rdisk # vxconfigd –kr reset 3.
The output from the vxdisk list command shows the DMP metanode names according to the current naming scheme. Output in the default old naming scheme: # vxdisk list DEVICE TYPE c2t0d0 auto:LVM c3t2d0 auto:LVM c89t0d0 auto:cdsdisk c89t0d1 auto:cdsdisk c89t0d2 auto:cdsdisk c89t0d3 auto:hpdisk c89t0d4 auto:hpdisk c89t0d5 auto:hpdisk DISK - GROUP - STATUS LVM LVM online online online online online online Output in agile naming scheme.
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 work only on disk groups with the current disk group versions; so you need to upgrade existing disk groups before you can perform the tasks.
disabling the PFTO feature. You can use the commands mentioned above to re-enable PFTO, if necessary. For more information, see pfto(7), vxpfto(1M), vxdisk(1M) man pages. • Enable DMP time-based LUN retries using the following command: vxdmpadm settune dmp_lun_retry_timeout=120 This system-wide tunable instructs DMP to retry failed I/O requests on a LUN for the time in seconds specified. The vxdmpadm manpage has not been updated for this release.
WARNING: The installed kernel modules include multiple versions of module 'llt'. Version 1.500.[447C70B3] will be ignored. WARNING: The installed kernel modules include multiple versions of module 'gab'. Version 1.500.[447C7115] will be ignored. You can ignore these messages.
• Problem Due to a limitation on the length of the path name to backing store volumes, cold-installing HP-UX 11i v3 fails in an HP VM guest.
# vxassist mirror volume layout=log ... The mirror is added but the log is omitted. Workaround To add a log and a mirror, add them separately as using two different instances of the vxassist command. For example: # vxassist mirror volume ... # vxassist addlog volume ... • Problem The vxvol and vxmend commands do not handle layered volumes. When the vxmend command is run on the top level volume to change the state of a volume, it is executed only on the top level volume.
to signals or interact with native interprocess communication. This scenario can result in the following problems: ◦ The node becomes unavailable for VxVM administrative commands. ◦ In a clustered or HA environment where Veritas Cluster Server agents need to communicate with vxconfigd daemon to determine the health of VxVM components, service groups will time out and fail. Workaround No workaround exists for this problem.
This message can be ignored. Once the disk group is imported successfully, there should be no problem in accessing its volumes. • Problem Online shrinking of an active swap volume is not supported. Workaround The vxassist command has no built-in protection to prevent you from shrinking the swap volume without first shrinking what the system sees as available swap space. If it is necessary to shrink the swap volume, the operation must be done in single user mode and the system must be rebooted immediately.
• Problem When all failed paths to the storage are restored, DMP automatically re-discovers them. However, you would have to run the vxdctl enable command for VxVM/CVM to get the disks back online. If the paths were restored before the reboot happens, then as part of boot, device discovery would happen automatically. However, if the paths are restored after the reboot, then you have to run vxdctl enable command to have VxVM rescan and rediscover the failed devices.
dd if=/dev/zero of=/dev/dsk/diskname bs=1024k count=50 vxdisk scandisks vxdisk -f init diskname • Problem If there are any stale devices in the /dev/disk and /dev/rdisk directories on which I/O processes cannot be performed, VxVM cannot access these devices. As a result, these devices are added as disks in the error state. When you run the vxdisk list command, these devices are displayed as disks in the error state. Workaround No workaround exists for this problem.
Hot-Relocation Issues The following Hot-Relocation issues are known: • Problem Hot-relocation could have an impact on performance. Workaround 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).
# vxdmpadm settune dmp_lun_retry_timeout=interval Where the interval value is in seconds. The default value of the tunable is 0, which means that the paths are probed only once. • Problem Rootability support and option to reboot when adding or removing boot disk into foreign category. The vxddladm addforeign command is used to add a device into a foreign device category and the vxddladm rmforeign command is used to remove a device from a foreign category. With VxVM 5.
# vxvol -f resync volume • Problem The use of file systems other than Veritas Storage Foundation Cluster File System (SFCFS) on volumes in cluster-shareable disk groups can cause system deadlocks. Workaround No workaround exists for this problem.
Workaround No workaround exists for this problem. • Problem You cannot use the vxvol command to set site consistency on a volume unless sites and site consistency have first been set up for the disk group. Workaround No workaround exists for this problem. • Problem 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.
You must first reattach the site and recover the disk group by running these commands: # vxdg -g diskgroup reattachsite sitename # vxrecover -g diskgroup The vxdiskadm command gives an error when replacing disk on which the site tag had been set.
When taking a snapshot of an SFCFS file system, you must ensure that at least one of the volumes defined in the command line is mounted on the CVM master node. • Problem 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. Workaround Do not perform these operations on a mounted volume.
array manufacturer to determine whether your system disk drives use a write-back cache, and if the configuration can be changed to disable write-back caching. • Problem During very fast boots on a system with many volumes, vxconfigd daemon 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.
If you are using Serviceguard with VxVM disk group in your package control script, you will see the following errors in the package control log output during package halt: VxVM vxdg ERROR V-5-1-584 Disk group dg_name: Some volumes in the disk group are in use ERROR: Function deactivate_disk_group ERROR: Failed to deport dg_name Workaround Outside Serviceguard Environment If you are experiencing this problem outside of the Serviceguard environment, you can workaround this problem by manually re-running vxdg
This prevents the DDL provider from loading, but has the effect of making enclosure, path, and controller objects no longer available in the VEA client GUI. 2. Restart the Storage Agent: # /opt/VRTSobc/pal33/bin/vxpal -a StorageAgent • Problem VEA does not work without the nsswitch.conf file. Workaround 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 for more information.
The message is erroneous, and it is safe to ignore it and continue the operation. • Problem The create disk group wizard shows internal disks as being available for the creation of shared disk groups. Workaround Avoid initializing the boot disks while creating a disk group. • Problem An object not found error is displayed when a volume set is created. Workaround No workaround exists for this problem.
