Patch Name: PHSS_10382 Patch Description: s700_800 10.X OmniBackII A.02.10 patch Creation Date: 97/03/18 Post Date: 97/05/16 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.10 Filesets: OMNIBACK-II.OMNI-ACS-P OMNIBACK-II.OMNI-CC OMNIBACK-II.OMNI-CC-P OMNIBACK-II.OMNI-CORE OMNIBACK-II.OMNI-CS OMNIBACK-II.OMNI-DA-P OMNIBACK-II.OMNI-DAS-P OMNIBACK-II.OMNI-MA-P OMNIBACK-II.OMNI-OPC-P OMNIBACK-II.OMNI-SAP-P OMNIBACK-II.OMNI-WIN-P OMNIBACK-II.OMNI-OST-P Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_10382 Symptoms: PHSS_10382: 1. Incorrect report of omninotify.ksh if duration time was bigger than 277 hours. 2. User without "Save datalist" access right had no permission to start backup from GUI. 3. Failed rawdisk backup could not be restarted. 4. It was not possible to run more than 25 parallel sapback processes. 5. It was not possible to skip symbolic links only. 6. On Win95 the omniinet process terminated when the user who started it logged off. 7. xomnimonitor occasionally coredumped. 8. Connection to ACSLS did not work if the location of cmd_proc was /export/home/ACSSS/bin/cmd_proc. 9. omnimm with -eject -location did not work properly. 10. Restore of large files (> 500MB) failed on SOLARIS. 11. When overwriting an OB2 tape the internal label was not rewritten. 12. The "omnimm -list_pool" showed different location info than the GUI. 13. Restore didn't use all the advanced options of the VxFS file system. 14. Improved handling of SCSI bus resets. 15. Restore of VBFS objects without detail catalogs was not possible. 16. Incorrect restore of VxFS extent attributes on HP-UX 10.20 if backup was made on HP-UX 10.10 or previous versions of HP-UX. PHSS_9870: 1. SAP or Oracle template script was started before the device was locked. 2. Backup to StorageTek 9704 DataWheel failed if PHSS_9047 has been installed. 3. Informix integration is supported on HP-UX 10.x. PHSS_9047: 1. Not all SAP files are listed for restore. 2. Uma coredumps on Solaris. 3. Fatal error opening DLT device on Solaris. 4. Programs are not executable after backup of Advanced VxFS if PHSS_8801 is installed. 5. OBII creates duplicate media labels. 6. Cannot enter more than 11 media at once into ACS silo. 7. Invalid device type reported on AIX. 8. ITO 3.0 fails to start Omniback. 9. Size of previous backup medium is added to a newly initialized one. 10. Listing objects from a large OBII DB causes timeout. 11. No devices found when browsing on WinNT systems 12. Restore on WinNT does not work with port other than the default 5555. 13. WinNT user profiles are stored under wrong tree. 14. OBII installation on WinNT deletes ITO registry entry. 15. Compressed files are restored uncompressed on WinNT. 16. Various performance enhancements. 17. OmniStorage integration is supported on HP-UX 10.10. PHSS_8802: 1. Error message "Specified slot X is not configured or used by some other OB2 session" during restores. 2. Restore of large file fails on AIX. 3. Omniback creates duplicate medium IDs. 4. Internal error in ("polmax.c":536) during rescan of 48AL. 5. "Cannot open exchanger control device" after device was powered-on. 6. During init of MO wrong medium size is determined. 7. Can't use barcode for HP tape library. 8. Various errors when accessing autochanger slots after init/verify/scan. 9. Rescanning MO jukebox causes error for all empty slots: "Cannot open device (No such device or address)" 10. Not possible to install host which has '0' as part of its IP address from within xomniadmin GUI. Error message is "Invalid number in second field!" 11. Use of preallocation list causes Omniback to issue erratic mount request. 12. Various performance enhancements. Defect Description: PHSS_10382: 1. omninotify.ksh did not report any session if duration time option was bigger than 277 hours. 2. If a user did not have the "save datalist" access right then he/she could not start backup from the GUI. 3. In the xomnimonitor it was not possible to restart failed rawdisk backup sessions. 4. During SAP backup a maximum of 25 paralel sapback processes could be started. 5. There was no backup option to allow skip symbolic links only. 6 On Win95 the omniinet process terminated when the user who started it logged off and the backup could not be started. 7. If there was a certain number of datalists then xomnimonitor coredumped during the listing of datalists in the previous sessions screen of the GUI. 8. Connection to ACSLS did not work if the location of cmd_proc was /export/home/ACSSS/bin/cmd_proc. OmniBack II reported - cannot find cmd_proc. 9. omnimm with -eject -location did not eject the tape. 10. File size was computed incorrectly on the SOLARIS platform which caused that restore of files bigger than 500MB was not possible. 11. When overwriting an OB2 tape the internal label remained unchanged. 12. If the medium was not in the exchanger then "omnimm -list_pool" reported empty string for the location while GUI reported "Non-Resident". 13. Restore performances are improved if restore if performed to advanced VxFS file system. 14. If scsi bus reset occurred then it could happen that the EOF mark was written at the beginning of the tape. 15. If restore of VBFS objects without detail catalogs was performed, then it failed because Media Agent could not be started. 16. OB2 did not restore VxFS extent attributes properly on HP-UX 10.20 if files were backed up on HP-UX 10.10 or on any previous version of HP-UX. PHSS_9870: 1. SAP or Oracle template script was started before the device was locked. 2. Backup to StorageTek 9704 DataWheel failed if PHSS_9047 has been installed. 3. Informix integration is supported on HP-UX 10.x. PHSS_9047: 1. OBII was confused when the input directory list was not in correct sort order. 2. Uma could not handle the status returned by the device correctly. 3. The device type was not recognized. 4. The use of the direct I/O feature of Advanced VxFS triggered a problem. (Also see the Special Installation Instructions) 5. Provide memset() workaround for tape driver inconsistency. 6. Caused by a timing problem within the session manager. 7. Reported device type was not recognized. 8. Triggered by use of port number other than the default 5555. 9. Problem with calculation of media sizes. 10. HidePrivateObj global option did not work when listing objects. 11. Problem in scanning routine. 12. Restore did not use a non-standard port. 13. Wrong path was used for the restore. 14. Problem with handling registry entries. 15. The compression attribute was not handled correctly during restore. 16. OmniStorage integration is supported on HP-UX 10.10. PHSS_8802: 1. This happens with media on which the post-backup script failed. First restore runs fine, another restore will fail with the given error message. 2. File size computed incorrectly in the disk agent on the AIX system which causes very large numbers. 3. Happens only when initializing more than one medium at once. 4. Seen with cleaning tape in slot 6 of the exchanger. 5. Status returned by device after power-on is not interpreted correctly. Operation succeeds when repeated a second time. 6. Ioctl(SIOC_CAPACITY) doesn't work on HP-UX 9.04, need to use DIOC_CAPACITY instead 7. Barcode support is not enabled by default for HP tape library. 8. Medium slot is locked during init/verify/scan and not released properly when the operation fails. 9. Incorrect status is generated for empty slots. 10. The IP address is rejected because it fails the plausibility check. 11. Happens with old-style autochangers (old SCSI II, jukebox, external control), but not Exchanger/ACS/DAS pools. SR: 1653186676 1653179333 1653181081 1653196535 5003347369 1653185223 1653204131 1653191957 Patch Files: /opt/omni/lbin/msm /opt/omni/lbin/bsm /opt/omni/lbin/rsm /opt/omni/lbin/dbsm /opt/omni/bin/xomniadmin /opt/omni/bin/xomnibackup /opt/omni/bin/xomnirestore /opt/omni/bin/omnib /opt/omni/bin/omnistat /opt/omni/bin/omnicellinfo /opt/omni/bin/xomnimonitor /opt/omni/bin/xomnimm /opt/omni/bin/omninotify.ksh /opt/omni/databases/vendor/da/hp/s800/hp-ux-10/A.02.10/ packet.Z /opt/omni/databases/vendor/da/hp/s800/hp-ux-1020/A.02.10/ packet.Z /opt/omni/databases/vendor/da/hp/s800/hp-ux/A.02.10/packet.Z /opt/omni/databases/vendor/da/ibm/rs6000/aix/A.02.10/ packet.Z /opt/omni/databases/vendor/da/sun/sparc/solaris/A.02.10/ packet.Z /opt/omni/databases/vendor/ma/hp/s800/hp-ux-10/A.02.10/ packet.Z /opt/omni/databases/vendor/ma/hp/s800/hp-ux/A.02.10/packet.Z /opt/omni/databases/vendor/ma/ibm/rs6000/aix/A.02.10/ packet.Z /opt/omni/databases/vendor/ma/sun/sparc/solaris/A.02.10/ packet.Z /opt/omni/databases/vendor/sap/hp/s800/hp-ux-10/A.02.10/ packet.Z /opt/omni/databases/vendor/sap/hp/s800/hp-ux/A.02.10/ packet.Z /opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.02.10/ packet.Z /opt/omni/databases/vendor/opc/hp/s800/hp-ux-10/A.02.10/ packet.Z /opt/omni/databases/vendor/opc/hp/s800/hp-ux/A.02.10/ packet.Z /opt/omni/databases/vendor/opc/hp/s800/hp-ux-1020/A.02.10/ packet.Z /opt/omni/databases/vendor/win/packet.Z /opt/omni/databases/vendor/ost/hp/s800/hp-ux/A.02.10/ packet.Z /opt/omni/databases/vendor/ost/hp/s800/hp-ux/A.02.10/ utils.tar /opt/omni/databases/vendor/ost/hp/s800/hp-ux-10/A.02.10/ utils.tar /opt/omni/databases/vendor/ost/hp/s800/hp-ux-10/A.02.10/ packet.Z /opt/omni/databases/vendor/ost/hp/s800/hp-ux-10/A.02.10/ require.dat /opt/omni/databases/vendor/ost/hp/s800/hp-ux-10/require.dat /opt/omni/databases/vendor/acs/hp/s800/hp-ux/A.02.10/ packet.Z /opt/omni/databases/vendor/acs/hp/s800/hp-ux-10/A.02.10/ packet.Z /opt/omni/databases/vendor/das/hp/s800/hp-ux-10/A.02.10/ packet.Z /opt/omni/databases/vendor/das/hp/s800/hp-ux/A.02.10/ packet.Z /opt/omni/databases/vendor/informix/hp/s800/hp-ux-10/ A.02.10/packet.Z /opt/omni/databases/vendor/informix/hp/s800/hp-ux-10/ A.02.10/require.dat /opt/omni/databases/vendor/informix/hp/s800/hp-ux-10/ A.02.10/utils.tar /opt/omni/databases/vendor/informix/hp/s800/hp-ux-10/ require.dat /opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.02.10/ packet.Z /opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.02.10/ packet.Z /opt/omni/databases/vendor/cc/hp/s800/hp-ux/A.02.10/packet.Z /opt/omni/lib/nls/C/omni.cat /opt/omni/lib/help/C/ob2.hv /opt/omni/lib/help/C/ob2.hvk /opt/omni/lib/help/C/ob200.ht /opt/omni/lib/help/C/ob201.ht /opt/omni/sbin/install/omni_inst.sh what(1) Output: /opt/omni/lbin/msm: [TZ=GMT0 /opt/omni/lbin/msm -version] HP OpenView OmniBack II A.02.10: MSM, built on Fri M ar 14 12:26:13 1997 /opt/omni/lbin/bsm: [TZ=GMT0 /opt/omni/lbin/bsm -version] HP OpenView OmniBack II A.02.10: BSM, built on Fri M ar 14 12:10:45 1997 /opt/omni/lbin/rsm: [TZ=GMT0 /opt/omni/lbin/rsm -version] HP OpenView OmniBack II A.02.10: RSM, built on Fri M ar 28 13:33:56 1997 /opt/omni/lbin/dbsm: [TZ=GMT0 /opt/omni/lbin/dbsm -version] HP OpenView OmniBack II A.02.10: DBSM, built on Fri Mar 14 12:22:25 1997 /opt/omni/bin/xomniadmin: [TZ=GMT0 /opt/omni/bin/xomniadmin -version] HP OpenView OmniBack II A.02.10: XOMNIADMIN, built o n Fri Mar 14 12:39:17 1997 /opt/omni/bin/xomnibackup: [TZ=GMT0 /opt/omni/bin/xomnibackup -version] HP OpenView OmniBack II A.02.10: XOMNIBACKUP, built on Tue Mar 18 09:14:02 1997 /opt/omni/bin/xomnirestore: [TZ=GMT0 /opt/omni/bin/xomnirestore -version] HP OpenView OmniBack II A.02.10: XOMNIRESTORE, built on Fri Mar 14 12:47:57 1997 /opt/omni/bin/omnib: [TZ=GMT0 /opt/omni/bin/omnib -version] HP OpenView OmniBack II A.02.10: OMNIB, built on Fri Mar 14 12:55:40 1997 /opt/omni/bin/omnistat: [TZ=GMT0 /opt/omni/bin/omnistat -version] HP OpenView OmniBack II A.02.10: OMNISTAT, built on Fri Mar 14 12:55:10 1997 /opt/omni/bin/omnicellinfo: [TZ=GMT0 /opt/omni/bin/omnicellinfo -version] HP OpenView OmniBack II A.02.10: OMNICELLINFO, built on Fri Mar 14 12:56:27 1997 /opt/omni/bin/xomnimonitor: [TZ=GMT0 /opt/omni/bin/xomnimonitor -version] HP OpenView OmniBack II A.02.10: XOMNIMONITOR, built on Fri Mar 14 12:42:22 1997 /opt/omni/bin/xomnimm: [TZ=GMT0 /opt/omni/bin/xomnimm -version] HP OpenView OmniBack II A.02.10: XOMNIMM, built on F ri Mar 14 12:41:06 1997 /opt/omni/bin/omninotify.ksh: None /opt/omni/databases/vendor/da/hp/s800/hp-ux-10/A.02.10/ packet.Z: None /opt/omni/databases/vendor/da/hp/s800/hp-ux-1020/A.02.10/ packet.Z: None /opt/omni/databases/vendor/da/hp/s800/hp-ux/A.02.10/ packet.Z: None /opt/omni/databases/vendor/da/ibm/rs6000/aix/A.02.10/ packet.Z: None /opt/omni/databases/vendor/da/sun/sparc/solaris/A.02.10/ packet.Z: None /opt/omni/databases/vendor/ma/hp/s800/hp-ux-10/A.02.10/ packet.Z: None /opt/omni/databases/vendor/ma/hp/s800/hp-ux/A.02.10/ packet.Z: None /opt/omni/databases/vendor/ma/ibm/rs6000/aix/A.02.10/ packet.Z: None /opt/omni/databases/vendor/ma/sun/sparc/solaris/A.02.10/ packet.Z: None /opt/omni/databases/vendor/sap/hp/s800/hp-ux-10/A.02.10/ packet.Z: None /opt/omni/databases/vendor/sap/hp/s800/hp-ux/A.02.10/ packet.Z: None /opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.02.10/ packet.Z: None /opt/omni/databases/vendor/opc/hp/s800/hp-ux-10/A.02.10/ packet.Z: None /opt/omni/databases/vendor/opc/hp/s800/hp-ux/A.02.10/ packet.Z: None /opt/omni/databases/vendor/opc/hp/s800/hp-ux-1020/A.02.10/ packet.Z: None /opt/omni/databases/vendor/win/packet.Z: None /opt/omni/databases/vendor/ost/hp/s800/hp-ux/A.02.10/ packet.Z: None /opt/omni/databases/vendor/ost/hp/s800/hp-ux/A.02.10/ utils.tar: None /opt/omni/databases/vendor/ost/hp/s800/hp-ux-10/A.02.10/ utils.tar: None /opt/omni/databases/vendor/ost/hp/s800/hp-ux-10/A.02.10/ packet.Z: None /opt/omni/databases/vendor/ost/hp/s800/hp-ux-10/A.02.10/ require.dat: None /opt/omni/databases/vendor/ost/hp/s800/hp-ux-10/require.dat: None /opt/omni/databases/vendor/acs/hp/s800/hp-ux/A.02.10/ packet.Z: None /opt/omni/databases/vendor/acs/hp/s800/hp-ux-10/A.02.10/ packet.Z: None /opt/omni/databases/vendor/das/hp/s800/hp-ux-10/A.02.10/ packet.Z: None /opt/omni/databases/vendor/das/hp/s800/hp-ux/A.02.10/ packet.Z: None /opt/omni/databases/vendor/informix/hp/s800/hp-ux-10/ A.02.10/packet.Z: None /opt/omni/databases/vendor/informix/hp/s800/hp-ux-10/ A.02.10/require.dat: None /opt/omni/databases/vendor/informix/hp/s800/hp-ux-10/ A.02.10/utils.tar: None /opt/omni/databases/vendor/informix/hp/s800/hp-ux-10/ require.dat: None /opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.02.10/ packet.Z: None /opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.02.10/ packet.Z: None /opt/omni/databases/vendor/cc/hp/s800/hp-ux/A.02.10/ packet.Z: None /opt/omni/lib/nls/C/omni.cat: None /opt/omni/lib/help/C/ob2.hv: None /opt/omni/lib/help/C/ob2.hvk: None /opt/omni/lib/help/C/ob200.ht: None /opt/omni/lib/help/C/ob201.ht: None /opt/omni/sbin/install/omni_inst.sh: None cksum(1) Output: 1085422440 1354825 /opt/omni/lbin/msm 618694913 1753121 /opt/omni/lbin/bsm 1218696739 1432976 /opt/omni/lbin/rsm 1711750186 1657894 /opt/omni/lbin/dbsm 2832807567 1433635 /opt/omni/bin/xomniadmin 1779568566 1898319 /opt/omni/bin/xomnibackup 2546406722 1384797 /opt/omni/bin/xomnirestore 170424620 427070 /opt/omni/bin/omnib 3746729944 328624 /opt/omni/bin/omnistat 412490117 525658 /opt/omni/bin/omnicellinfo 3516919158 932966 /opt/omni/bin/xomnimonitor 1735112705 1175116 /opt/omni/bin/xomnimm 2983436345 14251 /opt/omni/bin/omninotify.ksh 3678290236 1174635 /opt/omni/databases/vendor/da/hp/s800/ hp-ux-10/A.02.10/packet.Z 3627146077 1031287 /opt/omni/databases/vendor/da/hp/s800/ hp-ux-1020/A.02.10/packet.Z 2807286787 1139565 /opt/omni/databases/vendor/da/hp/s800/ hp-ux/A.02.10/packet.Z 832171848 780760 /opt/omni/databases/vendor/da/ibm/rs6000/ aix/A.02.10/packet.Z 685148629 923926 /opt/omni/databases/vendor/da/sun/sparc/ solaris/A.02.10/packet.Z 1687369971 1387909 /opt/omni/databases/vendor/ma/hp/s800/ hp-ux-10/A.02.10/packet.Z 2829547860 1253415 /opt/omni/databases/vendor/ma/hp/s800/ hp-ux/A.02.10/packet.Z 3513588115 1146505 /opt/omni/databases/vendor/ma/ibm/rs6000/ aix/A.02.10/packet.Z 3296450662 1256525 /opt/omni/databases/vendor/ma/sun/sparc/ solaris/A.02.10/packet.Z 1660284813 768581 /opt/omni/databases/vendor/sap/hp/s800/ hp-ux-10/A.02.10/packet.Z 974461909 747161 /opt/omni/databases/vendor/sap/hp/s800/ hp-ux/A.02.10/packet.Z 1660284813 768581 /opt/omni/databases/vendor/sap/hp/s800/ hp-ux-1020/A.02.10/packet.Z 1783546367 1130673 /opt/omni/databases/vendor/opc/hp/s800/ hp-ux-10/A.02.10/packet.Z 3349463166 1131569 /opt/omni/databases/vendor/opc/hp/s800/ hp-ux/A.02.10/packet.Z 1783546367 1130673 /opt/omni/databases/vendor/opc/hp/s800/ hp-ux-1020/A.02.10/packet.Z 659201809 5093677 /opt/omni/databases/vendor/win/packet.Z 1135185807 856325 /opt/omni/databases/vendor/ost/hp/s800/ hp-ux/A.02.10/packet.Z 2556797582 81920 /opt/omni/databases/vendor/ost/hp/s800/ hp-ux/A.02.10/utils.tar 2394913140 51200 /opt/omni/databases/vendor/ost/hp/s800/ hp-ux-10/A.02.10/utils.tar 1176399482 1102929 /opt/omni/databases/vendor/ost/hp/s800/ hp-ux-10/A.02.10/packet.Z 1391861633 17 /opt/omni/databases/vendor/ost/hp/s800/ hp-ux-10/A.02.10/require.dat 1391861633 17 /opt/omni/databases/vendor/ost/hp/s800/ hp-ux-10/require.dat 3089670507 1727803 /opt/omni/databases/vendor/acs/hp/s800/ hp-ux/A.02.10/packet.Z 4161607978 1881677 /opt/omni/databases/vendor/acs/hp/s800/ hp-ux-10/A.02.10/packet.Z 2454041873 1462188 /opt/omni/databases/vendor/das/hp/s800/ hp-ux-10/A.02.10/packet.Z 155790447 1328263 /opt/omni/databases/vendor/das/hp/s800/ hp-ux/A.02.10/packet.Z 2342427930 1013781 /opt/omni/databases/vendor/informix/hp/ s800/hp-ux-10/A.02.10/packet.Z 2495226274 17 /opt/omni/databases/vendor/informix/hp/s800/ hp-ux-10/A.02.10/require.dat 4159707393 51200 /opt/omni/databases/vendor/informix/hp/ s800/hp-ux-10/A.02.10/utils.tar 2495226274 17 /opt/omni/databases/vendor/informix/hp/s800/ hp-ux-10/require.dat 4221454854 7852477 /opt/omni/databases/vendor/cc/hp/s800/ hp-ux-10/A.02.10/packet.Z 2315960249 14497110 /opt/omni/databases/vendor/cc/hp/s800/ hp-ux-1020/A.02.10/packet.Z 167961569 7585738 /opt/omni/databases/vendor/cc/hp/s800/ hp-ux/A.02.10/packet.Z 3559302471 259802 /opt/omni/lib/nls/C/omni.cat 3206118282 67122 /opt/omni/lib/help/C/ob2.hv 252267528 8141 /opt/omni/lib/help/C/ob2.hvk 1184866288 660580 /opt/omni/lib/help/C/ob200.ht 29389185 16203 /opt/omni/lib/help/C/ob201.ht 3005398358 123415 /opt/omni/sbin/install/omni_inst.sh Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_8802 PHSS_9047 PHSS_9870 Equivalent Patches: PHSS_10381: s700: 9.01 9.03 9.05 9.07 s800: 9.00 9.04 Patch Package Size: 74170 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_10382 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_10382.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHSS_10382.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_10382. 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_10382.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_10382.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: SUBSYSTEM_SHUT "/opt/omni/sbin/omnisv.sh stop" must be executed on the cell server before swinstall is run. After the update, restart OmniBackII using "/opt/omni/sbin/omnisv.sh start". NOTE * Using this patch with advanced VxFS (JFS) filesystems on HP-UX 10.X clients can cause corruption of the kernel data structures. The corruption is a result of the direct I/O on VxFS that is implemented in this patch. The problem can be avoided by either - including the assignment OB2VXDIRECT=0 in the /opt/omni/.omnirc file on the respective backup client. Setting this variable for non-VxFS filesystems will have no effect. Setting the variable for VxFs filesystems will disable the direct I/O feature that introduces the corruption and thus it will not be possible to take advantage of the performance improvement during backup. or - installing one of the following patches: PHKL_9404 on s700 with HP-UX 10.01 PHKL_9405 on s800 with HP-UX 10.01 PHKL_9413 on s700 with HP-UX 10.10 PHKL_9414 on s800 with HP-UX 10.10 PHKL_9415 on s700 with HP-UX 10.20 PHKL_9416 on s800 with HP-UX 10.20 If the respective patch is installed, then the direct I/O feature can be enabled for VxFS filesystems by including the assignment OB2VXDIRECT=1 in the /opt/omni/.omnirc file on the respective backup client. The default behaviour of this patch is to have the direct I/O feature disabled. * If restore of VxFS extent attributes fails then for the correct restore of the attributes the following assignment has to be included OB2RESTOREFROM32=1 in the /opt/omni/.omnirc file on the respective backup client. * The Disk Agent, Media Agent and/or any integration modules need to be redistributed to the appropriate systems from within the "Cell Administration - Install" window of the OmnibackII graphical user interface before the patch modifications take effect. * The DAS agent module contains an old version of the libaci.sl shared library which is distributed to the clients during the Install step. If the client system has a newer version of this library, then it must be saved before distributing the DAS agent module and put in place again after the module has been distributed to the DAS agent. The full filename of the library is /usr/omni/lib/libaci.sl on HP-UX 9.X and /opt/omni/lib/libaci.sl on HP-UX 10.X. * Users who experienced the problem of OmnibackII creating media with duplicate IDs should scratch the medium header of one of the affected media before initializing it again. This can be done by writing at least 16 KByte of irrelevant data using for example a command like dd if=/usr/lib/libc.a of=/dev/rmt/MyDevice bs=10k After this step the medium can be re-initialized using the OmnibackII GUI or command line interface. * For Windows NT the patch includes a new push packet with all fixes for Windows NT. The packet is located on the Cell Server host and it has to be reinstalled on all Windows NT hosts. Please refer to HP OpenView OmniBack II Integration Guide for details on installation of Windows NT packet. * User profiles on WinNT 4.0 must be backed up as part of a filesystem. User profiles are subdirectories under %SystemRoot%\Profiles. For restoring these profiles they must not be logged interactive. The best way to achieve this is to start the restore session from another system. * When several cells are controlled through ITO then the same OBII port number must be used in the cells. * If PHSS_9047 has been previously installed and the OmniStorage packet has been distributed to an HP-UX 9.X client system, then before re-distributing the OmniStorage packet delivered with PHSS_9870 the old one needs to be deinstalled on the respective system. * From PHSS_9047 patch OmniBack II officially supports Windows NT 4.0. * From PHSS_9047 patch OmniBack II officially supports Omnistorage integration on HP-UX 10.01 and HP-UX 10.10. * From PHSS_9870 patch OmniBack II officially supports OmniBack/Informix integration. The integration is supported with Informix ODS 7.21. The customer should get respective files from Informix Software Co. Note that Informix ODS 7.21 requires HP-UX 10.X. * For solving the bus reset handling one of the following patches has to be installed: PHKL_9307 on HP-UX 10.20 PHKL_8616 on HP-UX 10.10 PHKL_8615 on HP-UX 10.01 * If the pathname to cmd_proc is different than /home/ACSLS/bin/cmd_proc then the STK_EXEC environmental variable has to be exported before starting the xomni GUI: export STK_EXEC=/export/home/ACSLS/bin/cmd_proc * New maximum number of paralel sapback processes is 50.