Patch Name: PHSS_30570 Patch Description: s700_800 10.20 OV OB4.10 patch - SSEA packet Creation Date: 04/05/05 Post Date: 04/06/03 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: OmniBackII A.04.10 Filesets: OMNIBACK-II.OMNI-SSEA-P,A.04.10 Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_30570 Symptoms: PHSS_30570: Change Request: H555009003 SSEA backup session fails with the following error: "|Critical| From:BSM@<hostname> "<barlist>" Time: <time> None of the Disk Agents completed successfully. Session has failed." Change Request: H555010461 An error is reported during multiple split mirror sessions on HP-UX running simultaneously. Change Request: H555011053 The backup session intermittently fails with the following error reported by the SSEA agent: "|Normal| From: SSEA@<hostname> "" Time:<time> ABORTED SSEA-Backup Agent on <hostname>." More detailed error message is reported in the SSEA debug file: "| -2| |SseXPairSplit| pairsplit failed! |EL_CMDIOE| Control command I/O error, or rejected. ... ... |Major| From: SSEA@<hostname> "" Time:<time> Failed to split the BC pair of LDEV <LDEV NUMBER>, SEQ# <SEQ NUMBER>, MU# <MU NUMBER>." Change Request: H555011457 During SSEA backup the following error is shown in the session report: "|Normal| From: SSEA@<R1_hostname> "" Time: <time> The following BC pairs will be used in current session: SEQ# LDEV Port TID LUN MU# Status SEQ# LDEV--------------------------------------------- -------<more then 10 BC pairs reported>---------- ------------------------------------------------- |Normal] From: SSEA@<R2_hostname> "" Time:<time> ABORTED SSEA-Backup Agent on <R2_hostname>." Change Request: H555011701 SureStore XP integration backup fails with the following error: "|Major| From: BSM@<hostname> Time: <time> |61:3003| Lost connection to Split Mirror Agent named "<name>" on host <hostname>. Ipc subsystem reports: "Details unknown." Change Request: H555012230 Business Copy (BC) backups fail with the following error message: "|Critical| From: SSEA@<hostname> "<object>" Time: <time> |225:1012| Failed to get pairs for all LDEVs." PHSS_28742: Change Request: H555009231 OmniBack II A.04.10 does not support XP1024 split mirror box. Change Request: H555009456 SSEA backup session report displays messages: "|Normal| From: SSEA@<hostname> "" Time: <time> ABORTED SSEA-Backup Agent on <hostname>. |Normal| From: SSEA@<hostname> "" Time: <time> ABORTED SSEA-Application Agent on <hostname>. |Critical| From: BSM@<hostname> "<datalist>" Time: <time> None of the Disk Agents completed successfully. Session has failed.". Change Request: H555010044 During multiple SSEA sessions running at the same time following is reported in the session report: "|Major| From: SYMA@<R2_hostname> "" Time: <time> Filesystem <fs_name> could not be mounted to <mountpoint>. /usr/sbin/mount -F vxfs -r <fs_name> 2>&1 mount: file system table may be corrupt". Change Request: H555010251 Volume group activation fails during Instant Recovery. Change Request: H555010436 SSEA integration backup fails with: "|Major| From: OB2BAR@<backup_hostname> Time:<time> Resolve of the disks fails. "|Major| From: OB2BAR@<backup_hostname> Time:<time> Resolving to disk level failed (error=-14)". PHSS_28338: Change Request: H555009140 Aborting SSEA Integration backup session after the mirror disks have been split, leaves backup system enabled. Change Request: H555009270 SSEA Integration backup occasionally fails with: "|Critical| From: BSM@<hostname> <barlist> Time: <time> None of the Disk Agents completed successfully. Session has failed." Change Request: H555009573 Instant Recovery fails reporting an invalid BC pairs status. PHSS_27593: Change Request: H555008644 During an OmniBack II XP Integration restore following error message is reported: "[Major] From: SSEA@<hostname> "" Time: <time> Filesystem /dev/vx/dsk/<disk_group>/<lvol> could not be dismounted from /<mountpoint> (Details unknown.)". Change Request: H555008685 In some cases SSEA takes a long time to resolve all the objects on the backup side. Change Request: H555008788 SSEA backup fails with: "/usr/sbin/vgchange -q n -a y /dev/<vg_name> [Major] From: SSEA@<hostname> "" Time: <time> Volume group /dev/<vg_name> could not be activated.". Change Request: H555008886 SSEA agent abnormally ends on the application side after Disk Agents are completed successfully. Change Request: H555008887 The connection with the host running SSEA agent is broken. PHSS_26883: Change Request: H555006991 OmniBack II XP split-mirror backup fails with: "[Critical] From: SSEA@<hostname> "" Time: <time> Failed to attach to the command device <device>. (Bad catalog access for message #10822 in set 12!)" Change Request: H555007253 OmniBack II XP split-mirror backup fails with: "[Major] From: SSEA@<hostname> "" Time: <time> Failed to split the BC pair of LDEV <ldev#>, SEQ# <seq#>, MU# <mu#>." Change Request: H555007298 SSEA agent dies ungracefully right after the last medium is unloaded at the end of backup. Change Request: H555007572 OmniBack II XP integration sessions fail with: "[Major] From: SSEA@<hostname> "" Time: <time> Failed to split the <BC or CA> pair of LDEV <ldev#>, SEQ# <seq#>, MU# <mu#>." Change Request: H555007572 OmniBack II XP Integration backup reports: "[Warning] From: SSEA@<hostname> "" Time: <time> File system <filesystem_path> could not be mounted to <mountpoint>. ([27] File too large)." Change Request: H555008141 Pre- and post-exec scripts are improperly executed under shell or "sh -c" type. Change Request: H555008573 During an OmniBack II XP Integration backup following error message is reported: "[Critical] From: SSEA@<hostname> "" Time: <time> Failed to attach to the command device <device>. (Raid Manager LIB Error: [2] Can't attach to the command device.)" Change Request: H555008585 A warning: "[Warning] From: SSEA@<hostname> "" Time: <time> Failed to get a BC pair for LDEV 0, MU# 0 in RAID <num>. (Details unknown.)" is reported during an OmniBack II XP Integration backup. Change Request: 8606257980 OmniBack II XP Integration backup using split-mirror fails with: "[Major] From: SSEA@<hostname> "" Time: <time> File system for / object not mounted or local disk is in backup." Defect Description: PHSS_30570: Change Request: H555009003 The data structure that holds information used for calling the pairvolstat() API is not re-initialized before a new pairvolstat() call. Resolution: The data structure that holds information used for calling the pairvolstat() API is re-initialized before a new pairvolstat() call. Change Request: H555010461 When multiple split mirror backup sessions are running, and the backup system is being prepared by two or more sessions simultaneously, the mount system command fails because the "/etc/mnttab" is being refreshed by one of the other split mirror sessions at the same time. Resolution: The system level umount(1M) command is used instead of the program level umount(2) command in order to avoid problems with synching the "mnttab" file. Change Request: H555011053 pairsplit() API call occasionally fails with no obvious reason. Resolution: Call of pairsplit() is put in a loop that will repeat the call if pairsplit() fails. If pairsplit() fails 10 times, error message will be displayed. Change Request: H555011457 If the volume groups seen from the application host include more than 10 LVM Mirror pairs, then the BC pair report dumped in the session report is not displayed by chunks, causing the buffer to overflow. Resolution: The counter for the displayed BC pairs takes into account also LVM mirror primary disks that do not need to be displayed in the BC pairs report. This way, the BC pairs report is dumped to the session report by chunks. Change Request: H555011701 Table of XP ports is not appropriate for the 01.07.00 and higher versions of the "rmlib" api. Resolution: Special table of XP ports is defined for the 01.07.00 and higher versions of the "rmlib" api. Change Request: H555012230 The StorageWorks XP Agent (SSEA) calls to the RAID Manager Library API are using LUNs that are greater than the 0-255 range (XP1024 box). With the RAID Manager Library version 1.07, the truncating feature has been removed. SSEA was not able to resolve the disks. Resolution: Execution of the "getdkclimit()" Raid Manger Library API function will ensure that calls to the XP box only use the LUNs from the 0-255 range. Part of SSPUX410_087. PHSS_28742: Change Request: H555009231 OmniBack II A.04.10 does not support XP1024 split mirror box. Resolution: OmniBack II A.04.10 supports XP1024 split mirror box. Change Request: H555009456 pairvolstat () API call fails for some disks. Resolution: Three parameters (linenumber, detailerrno and sourcename)of pCmd data structure which holds information used forcalling the pairvolstat() API are re-initialized beforea new pairvolstat() call. Call of ErrClearError is addedin SarQuery function. Part of SSPUX410_063. Change Request: H555010044 In the situation when multiple SSEA backups are running, and the R2 host is being prepared by two or more sessions at the same time, the mount system command might fail because the /etc/mnttab is refreshed by one of the other SSEA sessions at rightthat m-oment. Resolution: A retry/sleep is introduced for the problematic mount system command. Change Request: H555010251 When the OmniBack II mounts the data from the primary server to the backup server in order to move data to tape, it turns off the cluster bit for the volume group. The problem appears during reactivation of the volume groups after the Instant Recovery disk resynchronization is completed. Data is resynchronized onto the original volume group, but the cluster bit is still turned off. As a result, volume group activation fails. Resolution: If SSEA_IR_VGCHANGE_A in .omnirc file is set to "vgchange -a e", "vgchange -c y <volume group name>" is executed before "vgchange -a e <volume group name>" in order to turn on the cluster bit of the volume group after instant recovery. Change Request: H555010436 HP-UX LVM Mirroring configuration looks for BC PVOLs on all involved XP boxes instead of only on the XP box(es) where the BC is configured. Resolution: PVOLs are sought only on the XP box(es) where BC is configured. Part of SSPUX410_073. PHSS_28338: Change Request: H555009140 Clean-up procedure is not executed after backup session is aborted. Volume groups on backup host are left activated with the filesystems mounted. Resolution: Proper clean-up procedure (deactivation of volume groups, umounting the filesystems and re-synching the mirror) is executed after backup session is aborted. Part of SSPUX410_055. Change Request: H555009270 Backup session fails because of incorrect information sent to pairvolstat() API. Resolution: The data structure carrying the information to be provided to pairvolstat() API is re-initialized before executing new pairvolstat() call. Change Request: H555009573 If only one BC pair target disk is configured for Instant Recovery, then the session fails due to incorrect checking for more target disks. Resolution: Status checking for target disks is improved in a manner that it correctly recognizes what disks are going to be used for Instant Recovery. PHSS_27593: Change Request: H555008644 If during the restore SSEA fails to unmount the only mountpoint present in the session on the application side, agent proceeds with synching and splitting the disks although it should abort the session. Resolution: If the only mountpoint present in the session fails to be unmounted on the application side, then the session fails immediately. If there are multiple mountpoints in the session, and some of the mountpoints fail to be unmounted then SSEA skips the restore of the disks related to those mountpoints, but proceeds the restore of disks related to the mountpoints that were successfully unmounted. Change Request: H555008685 Resolving of objects from Business Copy XP on backup host proceeds very slowly if some (out of backup) objects are in PAIR state: -CA PAIR are in PSUS/SUSU: resolving takes less then <x> minutes, -CA PAIR are in PAIR state: resolving takes more then <6*x> minutes. The resolving algorithm has a very bad performance in this case. Resolution: The resolving algorithm is improved. Part of SSPUX410_041. Change Request: H555008788 If the application side is configured in a MC/SG cluster then the volume groups on the backup side can not be activated in the read/write mode with "vgchange -q n -a y" command. Resolution: The volume group on the backup side is marked as "not clustered" with the "vgchange -q n -c n" command before the activation in the read/write mode happens. To change this behavior set the SMB_CLUS_DEACT=1 environment variable in the .omnirc file on the R2 host. Part of SSPUX410_044. Change Request: H555008886 The allocated buffer size is too small. Resolution: The allocated buffer size is increased. Change Request: H555008887 In environments where the firewall between Cell Server and client(s) with firewall idle timeout of <x> minutes is present, it can happen that an agent is in idle state for the amount of time longer than mentioned timeout. In such cases, firewall breaks the connection between Cell Server and the client(s). Resolution: New environment variable OB2IPCKEEPALIVE is introduced. Setting its value to any of YES, TRUE, ON or 1 in /opt/omni/.omnirc file on Cell Server causes sending a dummy package from time to time in order to keep the connection open. Part of SSPUX410_046. PHSS_26883: Change Request: H555006991 SSEA agent tries to attach to the first command device it finds. In cases when first command device is busy, SSEA fails to attach. Resolution: A list of command devices is created and if one of them is busy, SSEA agent tries to attach to the next one. Change Request: H555007253 SSEA agent collects physical volume names from "vgdisplay" output. In environments where physical volumes are configured their names are collected as well although they are not needed for resolving process. This causes backup to fail. Resolution: SSEA agent skips parsing of "vgdisplay" command as soon as "PVG name" token is encountered. Part of SSPUX410_010. Change Request: H555007298 SSEA agent dies when updating XP database because of buffering problem. Resolution: Buffer holding logical devices information is extended. Part of SSPUX410_011. Change Request: H555007572 A "Major" message is displayed instead of "Warning" is environments with LVM mirroring on application side. Resolution: Message level is lowered to the level documented in XP Integration Guide. Change Request: H555007572 Some combinations of mount API options and ownerships of disk groups cause failures when import mapfile from Application to Backup host. Resolution: Command line mount is used instead of mount API. Change Request: H555008141 Scripts are executed with ".%s" which is "sh" instead of script name. Resolution: The dot is removed from function that executes the scripts. Change Request: H555008573 Attaching fails in environments where alternate links are used because of incorrect instance number counting. Resolution: Instance numbers are properly counted if alternate links are used. Change Request: H555008585 SSEA agent improperly handles "LDEV 0" (unknown logical device). Resolution: Logical device resolution is improved by adding additional checking in cases where "LDEV 0" is encountered. Part of SSPUX410_032. Change Request: 8606257980 SSEA agent cannot handle "/" (root) mountpoint when performing a split-mirror backup. Resolution: Mountpoint "/" (root) can be used in SSEA split-mirror backup if following is satisfied: 1. Root mountpoint is located on an XP disk. 2. SSEA_PRESERVE_MOUNTPOINT environment variable is not set to 1 on Backup host. 3. SSEA_BACKUP_ROOT_MOUNTPOINT environment variable is set to 1 on Application side. Note: Such backup cannot be used for Instant Recovery! SR: H555011701 H555011457 H555011053 H555010461 H555009003 H555012230 H555010251 H555010044 H555010436 H555009231 H555009456 H555009270 H555009140 H555009573 H555008685 H555008644 H555008886 H555008788 H555008887 H555006991 H555008585 H555007298 H555007748 8606257980 H555008141 H555007253 H555007572 H555007564 H555008573 Patch Files: /opt/omni/databases/vendor/ssea/sun/sparc/solaris-7/A.04.10/ packet.Z /opt/omni/databases/vendor/ssea/hp/s800/hp-ux-1020/A.04.10/ packet.Z /opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.04.10/ packet.Z what(1) Output: /opt/omni/databases/vendor/ssea/sun/sparc/solaris-7/A.04.10/ packet.Z: None /opt/omni/databases/vendor/ssea/hp/s800/hp-ux-1020/A.04.10/ packet.Z: None /opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.04.10/ packet.Z: None cksum(1) Output: 3794808292 258051 /opt/omni/databases/vendor/ssea/sun/sparc/ solaris-7/A.04.10/packet.Z 2358985463 536305 /opt/omni/databases/vendor/ssea/hp/s800/ hp-ux-1020/A.04.10/packet.Z 2530348066 547406 /opt/omni/databases/vendor/ssea/hp/s800/ hp-ux-11/A.04.10/packet.Z Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: Some of the defect fixes contained in this patch depend on the following other patches or their successors in order to completely resolve the problem: PHSS_30128: Cell Server (CS) packet patch, Release Date: Available Change Request: H555008887 PHSS_30128 is required for this defect fix. Supersedes: PHSS_26883 PHSS_27593 PHSS_28338 PHSS_28742 Equivalent Patches: PHSS_30571: s700: 11.00 11.11 s800: 11.00 11.11 Patch Package Size: 1320 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_30570 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_30570.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_30570. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. WARNING: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_30570.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_30570.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_30570: NOTE! This patch has to be installed on the Installation Server host. The OB2 SSEA agent must be redistributed to the SSEA client system(s) after the installation of the patch in order to get the fixes into effect. For distribution of the SSEA agent, refer to the OmniBackII Installation guide. Patch includes the following Site Specific Patches: SSPUX410_010 SSPUX410_011 SSPUX410_032 SSPUX410_041 SSPUX410_044 SSPUX410_046 SSPUX410_055 SSPUX410_063 SSPUX410_073 SSPUX410_087 A Site Specific Patch is a temporary hotfix that you might have received from HP Support if you have encountered a problem with Data Protector for which no General Release patch was or is available yet. If any newer Site Specific Patch - that is one with a higher number - for the SSEA agent is installed on your system, then you must re-apply this SSP after installing this SSEA agent patch.