Patch Name: PHSS_21636 Patch Description: s700_800 10.X OV OB2.55 patch - WindowsNT packet Creation Date: 00/05/19 Post Date: 00/05/24 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.02.55 Filesets: OMNIBACK-II.OMNI-WIN-P Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_21636 Symptoms: PHSS_21636: Id = JAGac29664 Pre-exec script, post-exec script, brbackup and brarchive return values are not checked. Id = NSMex02580 File system restore fails with the following error: [Critical] From: VRDA@host.domain " [/E]" Time: 07.07.99 18:39:17 Incorrect record sequence number: 38554 [Critical] From: VRDA@host.domain " [/E]" Time: 07.07.99 18:39:17 Error reading next backup record! Id = NSMex02288 Scheduler doesn't store the information about the excluded dates correctly. Id = NSMex02342 Object post-exec script is not executed after the SAP backup. OmniBack reports: "unknown internal error occurred". Id = NSMex01958 Cleaning does not work for DLT7000. Id = NSMex02093, NSMex03409 Restore of SAP file bigger than 2Gb fails, although the backup has not reported any errors. The error reported is: "Size of restored file is different than backuped size!" PHSS_17309: Id = NSMex01367 Datalist pre/post-exec fails on Windows NT system, if the Cell Server is in MC/SG cluster. Id = NSMex01515 No error message in case write error occurrs on tape device. Disk agent aborts with critical error message "Received ABORT request from BSM". Id = NSMex01391 Process exbar.exe is still running after exchange backup session has been aborted. Id = NSMex01685 In multihost library environment, connecting to SCSI changer host results in critical error "Cannot open exchanger control device ()". Id = NSMex01750 Windows NT Disk Agent hangs when it is trying to read the corrupted file. Id = NSMex01787 Hardware compression is toggled from one backup session to another. Id = NSMex01816 Help doesn't work on non-english Windows 95 systems. Id = NSMbb21907 During backup file access time attributes are not preserved. Id = NSMex01943 In case dbcmd function fails there are no error messages displayed. Id = NSMbb21587 Restore exclude option is not functioning properly. Id = HSLco12743 Backup on multivolume ExaByte is corrupted from the third tape on. PHSS_16533: Id = HSLco10531 or Id = HSLco10922 A user could obtain unauthorized access on an OmniBack II client host. PHSS_15776: Id = NSMex01367 Datalist preexec scripts failed on NT system. Id = NSMex01183 'Omit deleted files' on NT restore caused application error. Id = NSMex01198 or NSMex01372 Disk Agent failed during backup of registry on Windows 95. Id = HSLco09396 Directory permissions were not restored correctly. Id = NSMex01462 Setup had an endless loop when installing OmniBack on Primary (Backup) Domain Controller. Id = NSMex01397 During the upgrade of OmniBack II Client from version A.02.10 to A.02.55 the setup removed all directories on the directory where OmniBack II resided. Id = NSMex01284 Seek to End Of Data could abort prematurely. This caused writing of data to start at a wrong position, potentially overwriting valid data. A tape with this problem will be marked as poor and has to be verified. Id = NSMex01379 Appending data to direct access media (MO, file) by a lot of sessions could cause data corruption. PHSS_14676: Id = HSLco07638 If the Patch PHSS_14351/PHSS_14352 was installed then OmniBack II did not backup all needed configuration files on Windows NT. Id = NSMex01178 Backup of shared directory failed with error: "Not a valid mount point => aborting." PHSS_14351: Id = NSMex00971 File has been restored with the different name than it was backed up. Id = NSMfc08157 Deinstallation of OmniBack II - A.02.55 on Windows NT aborted crssrv.exe. Defect Description: PHSS_21636: Id = JAGac29664 Session exit status is incorrect because the return value checking is not implemented for pre/post-exec scripts, brbackup and brachive. Resolution: Return status checking has been implemented. Id = NSMex02580 If VBDA encounters corrupted file, it leaves a gap between the records on the tape. In such case record sequence number is increased twice although the corrupted record is missing on the tape. VRDA tries to find the missing record and aborts the restore session. Resolution: Record handling has been improved. Part of SSPNT255_033. Id = NSMex02288 Scheduler exclude dates are not correctly written into the datalist schedule file. Resolution: Datalist schedule file has been corrected. Part of SSPNT255_032. Id = NSMex02342 OmniBack tries to start the script with the incorrect startup parameters. Resolution: Script starting has been improved. Part of SSPNT255_031. Id = NSMex01958 It is not possible to clean DLT7000 drives with OB2.55. Resolution: Cleanme signal for DLT7000 added. Part of SSPNT255_026. Id = NSMex02093, NSMex03409 SAP backup does not detect that the SAP file is bigger than 2Gb. Instead, only the first 2Gb of the file are backed up. At the restore time, the file cannot be restored completely, and the restore agent fails with an error. Resolution: Backup agent is now able to backup SAP file bigger than 2Gb. File size limit has been changed to 64-bit integer. PHSS_17309: Id = NSMex01367 Cell Server is in MC/SG cluster. When Cell Server contacts NT client, the client verifies the server hostname using nslookup command. This evaluates in physical hostname instead of the relocatable Cell Server hostname. Comparition the two hostnames shows that they differ, and the session preexec is denied. Part of SSPNT255_08, SSPNT255_11. Resolution: Hostname checking is removed from omniinet. Check special installation instructions for more info on how to restrict the access to clients. Id = NSMex01515 Write error when trying to write to a tape should be reported, but it is not. The media agent is just aborted, and this causes the disk agent to report Critical error message. Part of SSPNT255_12. Resolution: Added an error message. Id = NSMex01391 If the exchange backup session is aborted by the user, the process exbar.exe remains running on the Windows system. Part of NTSSP255_16. Resolution: Improved abort procedure. Id = NSMex01685 Hardcoded port 5555 causes OmniBack II to fail in multihost library environment, when trying to load a medium on the SCSI changer system. Part of SSPNT255_17, SSPNT255_18. Resolution: Id = NSMex01750 Windows NT Disk Agent hangs when it is trying to read the corrupted file. Part of SSPNT255_19. Resolution: Ability to skip the corrupted file is implemented. Id = NSMex01787 When user selects scsi address for tape drive without a compression (no compression flag at the end of the drive name: scsi2:0:5:0 without compression flag C) the compression is changed from one session to another. Part of SSPNT255_21. Resolution: Compression flag setting is stored properly. Id = NSMex01816 Help doesn't work on the non-english Windows 95 systems because it doesn't support non-english languages. Part of SSPNT255_23. Resolution: Help files properly recompiled. Id = NSMbb21907 Regardless of the options given to the vbda.exe the access time attributes of the files being backed up are not preserved. Part of SSPNT255_24. Reolution: Reseting of last access time attributes implemented in the Disk Agent. Id = NSMex01943 Return value of the dbcmd function is not checked. Part of SSPNT255_25. Resolution: Improved dbcmd return checking. Id = NSMbb21587 RDA interpretes exclude path incorrectly. Part of SSPNT255_28. Resolution: Proper exclude path handling. Id = HSLco12743 Restore of a single large multivolume backup on NT Media Agent with ExaByte device fails on third tape with duplicated DA block. Resolution: Fix implemented in Backup Media Agent. PHSS_16533: Id = HSLco10922 A user could obtain unauthorized access on an OmniBack II client host. PHSS_15776: Id = NSMex01367 If the Cell Server was installed on a ServiceGuard system the datalist pre-exec scripts failed with the error "Host not in local cell". Part of SSPNT_255_08. Id = NSMex01183 Restore Disk Agent was aborted on all the incrementals other than 0 when "omit deleted files" option was selected. The following error message was displayed: "vrda.exe - application error Instruction at 0x77F25F19 referenced memory at 0x0020700. The memory could not be written" Part of SSPNT_255_09 Id = NSMex01198 or NSMex01372 Backup of the disk and the registry of the Windows 95 client failed with the message: "this application will be closed because an illegal operation occurred." Part of SSPNT_255_09. Id = HSLco09396 'Omit deleted files' option did not properly restore all directory permissions. Id = NSMex01462 Setup detected that the computer is a Primary (Backup) Domain Controller and displayed the following warning message: "Permissions must be set manually on the Primary Domain Controller". Pressing the button resulted in displaying the warning message again and again. Part of SSPNT_255_10. Id = NSMex01397 During the upgrade of OmniBack II Client from version A.02.10 to A.02.55 the setup did not only removed the OmniBack directory but all directories on the directory where OmniBack II has been installed. Part of SSPNT_255_07. Id = NSMex01284 Seek to End Of Data could abort prematurely. This caused writing of data to start at a wrong position, potentially overwriting valid data. A tape with this problem will be marked as poor and has to be verified. Id = NSMex01379 Appending data to direct access media (MO, file) by a lot of sessions could cause data corruption. PHSS_14676: Id = HSLco07638 If the Patch PHSS_14351/PHSS_14352 was installed and the new packet was pushed to Windows NT then OmniBack II did not backup all needed configuration files. It backed up only configuration files that are the same on Windows NT and on Windows 95. Id = NSMex01178 If there was shared non-root directory then the backup of it failed with error message: "Not a valid mount point => aborting." PHSS_14351: Id = NSMex00971 File has been restored with the different name than it was backed up. The problem appeared if the different character set is used on Windows NT, for example: Danish or Swedish character set. Part of SSPNT255_001. Id = NSMfc08157 Deinstallation of OmniBack II - A.02.55 on Windows NT packet aborted and erased crs.exe and crssrv.exe. Part of SSPNT255_003. SR: 1653288902 5003452904 5003460758 5003418798 1653262386 Patch Files: /opt/omni/databases/vendor/win/packet.Z what(1) Output: /opt/omni/databases/vendor/win/packet.Z: None cksum(1) Output: 2556606431 10488018 /opt/omni/databases/vendor/win/packet.Z Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_14351 PHSS_14676 PHSS_15776 PHSS_16533 PHSS_17309 Equivalent Patches: PHSS_21637: s700: 11.00 s800: 11.00 Patch Package Size: 10300 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_21636 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_21636.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_21636. 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_21636.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_21636.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_21636: NOTE! Patch has to be installed on the Cell Server host. The patch includes a new push packet with all fixes for Windows NT. The packet is located on the Cell Server host: /opt/omni/databases/vendor/win/packet.Z The packet has to be reinstalled on all Windows NT hosts. See the HP OpenView OmniBack II Integration Guide in order to get instructions for installing the Windows NT Integration. NOTE! After the patch has been installed on an NT client, some measures must be taken to restrict the access to it from specified system(s). Without these, the client can be accessed and backed up from any Cell Server in LAN. There are two registry entries, which can enable or disable access from particular system(s) in the LAN. Specify a list of hosts if you want allow/deny access from specific hosts in these registry entries: HKEY_LOCAL_MACHINE\SOFTWARE\HEWLETT_PACKARD\OPENVIEW\ OMNIBACK\COMMON ALLOW_HOSTS:REG_MULTI_SZ DENY_HOSTS:REG_MULTI_SZ The patch includes the following Site Specific Patches: SSPNT255_001 SSPNT255_003 SSPNT255_004 SSPNT255_007 SSPNT255_008 SSPNT255_009 SSPNT255_010 SSPNT255_011 SSPNT255_012 SSPNT255_016 SSPNT255_017 SSPNT255_018 SSPNT255_019 SSPNT255_021 SSPNT255_023 SSPNT255_024 SSPNT255_025 SSPNT255_026 SSPNT255_028 SSPNT255_031 SSPNT255_032 SSPNT255_033