Patch Name: PHSS_23105 Patch Description: s700_800 10.X OV OB3.50 patch - CS packet Creation Date: 01/01/31 Post Date: 01/02/02 Hardware Platforms - OS Releases: s700: 10.00 10.01 10.10 10.20 s800: 10.00 10.01 10.10 10.20 Products: OmniBackII A.03.50 Filesets: OMNIBACK-II.OMNI-CS,A.03.50 Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_23105 Symptoms: PHSS_23105: Id = NSMex03757 Bad backup performance after upgrade from OmniBack II 2.55 or 3.00. Id = NSMex03977 Execution of command "omnirpt -report used_media -timeframe " results in the following error message: "DB[4] internal error [-16] record not connected to set". PHSS_22369: Id = JAGad13634 Informix barlists are not converted into a OmniBack II 3.50 format after an upgrade from OmniBack II 2.55. Id = JAGad17029 "List from media" ignores "See private objects" option. Id = NSMex03356 Permanent license shows up as out of IP range. Id = NSMex03365 Backup session is not logged in the database if file pattern search is performed in parallel. Id = NSMex03419 After importing a tape from 2.55 to 3.x cell some of the files can not be restored. Id = NSMex03466 After the upgrade from OmniBack II 3.00 to 3.50, a warning "Received connect from BAR backup DA on host that is not specified in CLIENT statement in barlist." appears on a client with multiple lan cards. Id = NSMex03481 A backup of MC/SG can not be aborted after the switch. Id = NSMex03491, JAGad28516 Directories are backed up even if excluded in host backup. Id = NSMex03493 Omnitrig does not pass debugging parameters to omnirpt. Id = NSMex03583, NSMex03631 OmniBack II ignores the tape loaded after the mount request for SCSI-II changer device. Id = NSMex03638 Option "-change_objname" does not work properly. Id = NSMex03501 List of media fails with an error: "Medium details not available. Medium owned by Cell Manager: ." Id = NSMex03683 Copy session of write-protected tape is aborted and cleaning tape is requested in the source tape drive. Id = NSMex02584 Internal database server (RDS) abnormally ends due to lack of memory. Id = NSMex03702 Internal database server (RDS) abnormally ends during a SAP restore. Id = NSMex03289 Sessions are disappearing from OmniBack II database. Id = NSMex03521 OmniBack II database gets corrupted. Id = NSMex03737 Sessions are disappearing from OmniBack II database. Id = NSMex03758, NSMex03759, NSMex03646 Execution of commands "omnidb -session " and "omnirpt -report used_media -timeframe " reports that the database is corrupt, but omnidbcheck reports no problem. Defect Description: PHSS_23105: Id = NSMex03757 Performance degrated by up to 50% after upgrade from OmniBack II 2.55 or 3.00. Resolution: Redundant update of the objects removed. Part of SSPUX350_023. Id = NSMex03977 Listing of objects failed for the objects that have been purged from the database, because there is no link between objects and object versions. Resolution: Fix is implemented in libob2ecbd.sl. PHSS_22369: Id = JAGad13634 File /opt/omni/sbin/nb_informix is missing. Resolution: File /opt/omni/sbin/nb_informix is added to OMNI-CS fileset. Id = JAGad17029 Using "List from media" option in restore context ignores "See private objects" option. Objects that are backed up as "Private" are not listed. Resolution: Option parsing in restore context is improved. Id = NSMex03356 If there are more than 100 network interfaces, ioctl() call fails. Resolution: Buffer for SIOCGIFCONF is increased to support up to 1000 network interfaces. Id = NSMex03365 When backup and file search sessions are started in parallel, file search session locks the database. Backup Session Manager tries to write backup information into locked database. Since this action can not be performed, the following messages are logged in the rds.log: "11740 [10-Apr-00 17:37:07] error status=5 11741 [10-Apr-00 17:37:07] GROUPLOCK ELEMENT: userID=4, LockType=6, LockMode= *, RecSetType=10002, dba=[0:0], odnum=1" Resolution: File pattern search is optimized to minimize the possibilities of group locks. Id = NSMex03419 OmniBack II 3.50 objects are case insensitive which is not true for the SAP objects backed up with 2.55 version. Object tape format is changed with 3.50 as well. These changes caused some SAP objects not to be displayed in the Restore GUI after importing the tape with SAP objects from 2.55 to 3.50. Resolution: Object names from tape are converted into OmniBack II 3.50 format after tape import from 2.55. Id = NSMex03466 System name checking is not performed for systems with multiple LAN cards. Backup Session Manager is checking the system names only when looking for clusters. Resolution: System name checking is performed when looking for clusters and systems with multiple LAN cards. Id = NSMex03481 Aborting backup session is not possible because Backup Session Manager incorrectly aborts Disk Agents after the package switch. Resolution: Disk Agents are properly aborted. Id = NSMex03491, JAGad28516 In host backup only mount point directories can be excluded. If a directory is not a mount point then it cannot be excluded from the backup. Resolution: Non-mountpoint directories can now be excluded. Id = NSMex03493 Scheduled reports are not started with "-debug" option although omnitrig is. Resolution: Command line option passing is implemented for omnirpt. Id = NSMex03583, NSMex03631 Mount request is not properly implemented for SCSI-II changer devices. Resolution: OmniBack II properly handles mount requests. Id = NSMex03638 Option "-change_objname" is not meant to be a part of OmniBack II A.03.50. Resolution: Option "-change_objname" is removed. Id = NSMex03501 After upgrading OmniBack ServiceGuard package from 3.00 to 3.50, it is not possible to list media due to incorrect ownership of medium. Resolution: Virtual hostname is used for medium ownership. Part of SSPUX350_001. Id = NSMex03683 Copy session is aborted when copying a write-protected tape. When write-protected tape in the source drive is checked, the cleaning tape for that drive is requested and the following message appears: "Cleaning tape requested by device . Please clean the drive.". Resolution: The cleanme signal is now processed correctly. Part of SSPUX350_004. Id = NSMex02584 Execution of command "omnidb -filesystem -file " causes a memory leak in RDS (approx. 300 bytes). If the command is started more than 100000 times, it can cause RDS to die due to a lack of memory. Resolution: Fix is implemented in libob2ecdb.sl. Part of SSPUX350_006. Id = NSMex03702 RDS dies during a large SAP restore due to memory leak described in NSMex02584. Resolution: Fix is implemented in libob2ecbd.sl. Part of SSPUX350_006. Id = NSMex03289 Media sync does not work properly when table of exported/recycled media gets too big (>3000 media). Some new sessions dissapear from database. No error is reported. Resolution: Improved error handling logs this event in debug.log. Part of SSPUX350_003. Id = NSMex03521 Database stays in the hot mode after issuing an "omnidbcheck" command. If a large amount of data is written before OmniBack II daemons are stopped, it can happen that hot files are not properly flushed. This causes corruption of database. Resolution: omnidbcheck flushes hot files immediately after database check. Part of SSPUX350_003. Id = NSMex03737 Media Session Manager is incorrectly initializing media in ServiceGuard environment. Owner of medium is set to hostname of the active node. This results in wrong medium handling and objects from such medium are removed from the OmniBack II database each time Media Session Manager is started. Resolution: Initialization of media in ServiceGuard environment is improved. Please see Special Installation Instructions. Part of SSPUX350_010. Id = NSMex03758, NSMex03759, NSMex03646 OmniBack II reports an error: "Database is probably corrupt." for backup sessions that span over two or more media if one of them is already overwritten/exported because then some of the objects are already removed from the database. Resolution: Removed objects are skipped during the database queries. Part of SSPUX350_010. SR: H555004350 8606159187 8606144294 8606147687 Patch Files: /opt/omni/lbin/crs /opt/omni/lbin/bsm /opt/omni/lbin/dbsm /opt/omni/lbin/msm /opt/omni/lbin/mmd /opt/omni/sbin/omnitrig /opt/omni/sbin/omnidbutil /opt/omni/sbin/omnidbcheck /opt/omni/sbin/nb_informix /opt/omni/lib/libob2ecmn.sl /opt/omni/lib/libob2ecdb.sl /opt/omni/lib/libob2emmdb.sl what(1) Output: /opt/omni/lbin/crs: [TZ=GMT0 /opt/omni/lbin/crs -version] HP OpenView OmniBack II A.03.50: CRS, internal build PHSS_22369/PHSS_22370, built on Wed Oct 4 12:06:13 2000 /opt/omni/lbin/bsm: [TZ=GMT0 /opt/omni/lbin/bsm -version] HP OpenView OmniBack II A.03.50: BSM, internal build PHSS_22369/PHSS_22370, built on Thu Oct 12 14:46:08 2000 /opt/omni/lbin/dbsm: [TZ=GMT0 /opt/omni/lbin/dbsm -version] HP OpenView OmniBack II A.03.50: DBSM, internal buil d PHSS_22369/PHSS_22370, built on Wed Oct 4 11:24:40 2000 /opt/omni/lbin/msm: [TZ=GMT0 /opt/omni/lbin/msm -version] HP OpenView OmniBack II A.03.50: MSM, internal build PHSS_22369/PHSS_22370, built on Wed Oct 18 12:50:42 2000 /opt/omni/lbin/mmd: [TZ=GMT0 /opt/omni/lbin/mmd -version] HP OpenView OmniBack II A.03.50: MMD, internal build PHSS_22369/PHSS_22370, built on Wed Oct 4 11:57:37 2000 /opt/omni/sbin/omnitrig: [TZ=GMT0 /opt/omni/sbin/omnitrig -version] HP OpenView OmniBack II A.03.50: OMNITRIG, internal build PHSS_22369/PHSS_22370, built on Wed Oc t 4 12:08:12 2000 /opt/omni/sbin/omnidbutil: [TZ=GMT0 /opt/omni/sbin/omnidbutil -version] HP OpenView OmniBack II A.03.50: OMNIDBUTIL, interna l build PHSS_22369/PHSS_22370, built on Wed Oct 4 11:37:50 2000 /opt/omni/sbin/omnidbcheck: [TZ=GMT0 /opt/omni/sbin/omnidbcheck -version] HP OpenView OmniBack II A.03.50: OMNIDBCHECK, intern al build PHSS_22369/PHSS_22370, built on Wed Oct 4 11:38:00 2000 /opt/omni/sbin/nb_informix: None /opt/omni/lib/libob2ecmn.sl: None /opt/omni/lib/libob2ecdb.sl: None /opt/omni/lib/libob2emmdb.sl: None cksum(1) Output: 1116505986 714587 /opt/omni/lbin/crs 764770845 1162202 /opt/omni/lbin/bsm 2188331003 1219052 /opt/omni/lbin/dbsm 4258663179 681954 /opt/omni/lbin/msm 2231509019 517734 /opt/omni/lbin/mmd 2915825235 398571 /opt/omni/sbin/omnitrig 2047777077 693853 /opt/omni/sbin/omnidbutil 3214669779 464150 /opt/omni/sbin/omnidbcheck 2755861046 353611 /opt/omni/sbin/nb_informix 3688959795 804257 /opt/omni/lib/libob2ecmn.sl 1035736335 881364 /opt/omni/lib/libob2ecdb.sl 2189475600 651912 /opt/omni/lib/libob2emmdb.sl Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_22369 Equivalent Patches: PHSS_23106: s700: 11.00 s800: 11.00 Patch Package Size: 8410 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_23105 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_23105.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_23105. 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_23105.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_23105.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_23105: NOTE! This Patch has to be installed on the Cell Manager host. OmniBack II server must be shutdown before installing the patch. Use the following command for shutting down the server: "/opt/omni/sbin/omnisv.sh stop". After the installation is complete, restart OmniBack II server using "/opt/omni/sbin/omnisv.sh start". NOTE! After installation of the patch, the erroneous feature reported in NSMex03638 will still show up in "omnidbutil -help" output. It is fully removed only when in addition patch PHSS_22434/PHSS_22435 is installed. NOTE! Before applying the fix for NSMex03737 please run following commands: omnidbutil -change_cell_name and omnidbutil -change_cell_name where and are names of ServiceGuard nodes. Patch includes the following Site Specific Patches: SSPUX350_001 SSPUX350_003 SSPUX350_004 SSPUX350_006 SSPUX350_010 SSPUX350_023