Patch Name: PHSS_32019 Patch Description: s700_800 10.20 OV OB4.10 patch - CS packet Creation Date: 04/11/17 Post Date: 04/12/01 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: OmniBackII A.04.10 Filesets: OMNIBACK-II.OMNI-CS,A.04.10 Automatic Reboot?: No Status: General Superseded Critical: No (superseded patches were critical) PHSS_30343: ABORT Path Name: /hp-ux_patches/s700_800/10.X/PHSS_32019 Symptoms: PHSS_32019: Change Request: QXCR1000201702 In case a large number of concurrent devices or smb disks locks shared memory locking buffer fills up. Sessions that can not lock the resources fail. PHSS_31051: Change Request: QXCR1000177996 While importing a backup session, the media session manager (MSM) ends abnormally. Change Request: QXCR1000193430 When querying the catalog on the Cell Server with the "omnidb" command the wrong owner of a SAP object is displayed. Change Request: QXCR1000193452 Old detail catalog is not deleted on medium copy operation. Change Request: QXCR1000193518 NT GUI problem. Change Request: 8606325101 Restore does not have the same cleaning mechanism as backup. Change Request: H555013629 Command "omnirpt -list_media -protection NoOfDays" does not properly list tapes whose protection expires in "NoOfDays" as specified in the command. Change Request: H555013676 Cron job "omnimm -repository_update" may fail with error 11 if library has empty slots. Session is marked completed with failures. Change Request: H555013764 "omnidbcheck -extended" command reports OMNIDC errors when logical database is corrupted. PHSS_30343: Change Request: 8606362207 Backup session cannot be aborted when minimum load balancing equals 2 and first 2 drives report an error. Change Request: H555011989 The post-exec script is started even though the pre-exec script has not been run and the "OB2FORCEPOSTEXEC" option is NOT set. Change Request: H555011996 OmniBack II does not properly show a tape capacity when a tape was initialized with the specific size. Change Request: H555012097 Restores of incremental backups can be slow. Change Request: H555012114 The "omnidb -sap <object> -session <time> -catalog" command reports the following error: "|12:10900| Detail Catalog Database Internal Error." Change Request: H555012187 Non-existent libraries are scanned for media. Change Request: H555012263 a.) CRS quits after cluster failover. b.) RDS ends abnormally when running frequent reports. Change Request: H555012346 When restoring from two backup objects, the performance between the completion of the first backup object and the beginning of the second backup object is sluggish. Change Request: H555012374 The "omnidb -filesystem <Object> -session <Session_ID> -catalog" command stops responding. Change Request: H555012376 Deletion of objects from the OmniBack II internal database (IDB) is sluggish. Other sessions are waiting indefinetly. Change Request: H555012377 The "omnirpt -report obj_lastbackup -datalist <backup specification> -debug 1-999" ends abnormally. Change Request: H555012428 Backup session manager (BSM) intermittently ends abnormally. Change Request: H555012804 The following message is reported when attempting to perform a restore: "|Warning| From: RSM@<hostname> "" Time: <time> No more media for restore on device <device>. Aborting running Disk Agents." Change Request: H555013280 When running the "omnicellinfo -allbdf" command, the following error appears: "Failed to locate disks on host <hostname>! Host may be unreachable." Change Request: H555013315 SQL restore may stop responding after installing the Cell Server patch PHSS_30129. Change Request: H555013333 During a restore from the STK/ACS library, a mount request is issued to get the correct tape. If confirmed, an incorrect tape is loaded. Change Request: H555013469 Post-exec scripts fail to execute. PHSS_30128: Change Request: H555011451 After tape import, Lotus Notes database restore cannot be performed using the graphical user interface (GUI). Change Request: H555011685 While restarting a failed session, the following error message appears: "Error-Detail Unknown." Change Request: H555011708 After mount request, Backup Media Agent (BMA) exits and Backup Session Manager (BSM) stops responding. Change Request: H555011784 Size values returned by the "omnidbutil -info" and "ll" command are different. Change Request: H555011788 The "omnimm -catalog medium_id" command may end abnormally on tapes with large number of files and file versions. PHSS_29865: Change Request: H555007363 After the MC/ServiceGuard failover, the MMD service fails to start. Change Request: H555009725 Insufficient information regarding the "MaxMAperSM" global options variable in the Administrator's Guide and Release Notes. Change Request: H555010638 When there are large numbers of backup specifications holding lots of data in the backup specification headers, some of them are not displayed in the Graphical User Interface (GUI). Change Request: H555010730 CRS intermittently ends abnormally. Change Request: H555010787 Backup session with enabled debugs stops responding when the Backup Session Manager (BSM) or the Backup Media Agent (BMA) debug file reaches 2 GB in size. Change Request: H555010817 When drives do not become available, session ends abnormally. Change Request: H555010850 Filename purge is not functioning. Change Request: H555010860 Scheduled backups do not start. Change Request: H555010910 Device unlocking is not functioning as expected for the Informix backup when device that is used for backing up Logical Logs "L" resource type is out of DYNAMIC range. Change Request: H555011095 BSM ends abnormally when the "omniabort" command is used. Change Request: H555011119 Linux Media Agent requests UNIX Single Drive license instead of MS Windows NT Single license. Change Request: H555011230 When using Single Server Edition (SSE) of OmniBack II, backup session fails with the following error: "|Major| From BSM@<hostname> <object> Time: <time> Device: <device> does not reside on the Cell Manager. It cannot be used for backup under SSE license." Change Request: H555011264 Every SNMP trap message is received twice in SNMP management station during library rescan. Change Request: H555011297 Purge session does not appear in the GUI purge report. Change Request: H555011298 When OmniBack II database (OBDB) backup flushes hot file, the scheduled backups do not start. Change Request: H555011344 "omnidbutil -free_locked_devs" command does not unlock the medium. Change Request: H555011379 The Media Agent (MA) fails when trying to do a local backup with only SSE license available. Change Request: H555011460 No catalog information available for "WinFs" objects when backing up drive or host. "Winfs" objects return the following error message when "omnidb -session <time> -winfs <hostname>:/G 'G:' -catalog" is run: "No catalog available for WinFS <hostname>:/G 'G:' within session <session_name>." Change Request: 8606324070 Device lock timeout exceeds the time set with the "SmWaitForDevice" global variable. PHSS_28740: Change Request: H555008723 Media copy operation completes successfully but at the end Media Session Manager (MSM) reports that 0 media out of 1 were successfully copied. Change Request: H555009054 Backup fails with an error: "|Critical| From: BMA@<host> "<device>" Time:<time> |90:30| SM/MA protocol error => aborting" Change Request: H555010030 During NDMP Backup Session Omniback II Database gets corrupted, which can be detected by running a "omnidbcheck -sibf" command . Change Request: H555010269 After OmniBack II A.03.50 tapes with Exchange objects are imported to Omniback II A.04.10, Internal DataBase (IDB) is corrupt. Change Request: H555010280 Command "omnidbutil -writedb" fails with error: "|Critical| From: OMNIDBUTIL@<host> "" Time:<time> |12:1165| Database network communication error." Change Request: H555010285 Medium import operation fails with message: "|Critical| From: MSM@<host> "datalist" Time:<time> |65:99|Import failed with possible cause: this media already has valid copy in DB." Change Request: H555010380 NDMP restore from multiple imported tapes fails with: "|Major| From: RSM@<host> "" Time:<time> Unknown internal error." Change Request: H555010381 When media in free pool is used and becomes protected it still remains in free pool. Change Request: H555010432 When performing omnisv -stop command crs dies with: "Cannot stop "omniback_crs" service, system error: |502|". Change Request: 8606307557 If one of BMA fails in a load-balanced backup, then all other available devices are started and the total amount of started devices is greater than MAX number of devices defined in datalist. PHSS_28731: Change Request: H555009289 Performing "omnisv -stop" command sometimes returns exit code different then 0 and because of that crs dies with error message: "Cannot stop "omniback_crs" service system error:|502|" Change Request: H555009297 After aborting host backup the object post-exec script does not execute. Change Request: H555009322 "omnib" started from different scheduler completes successfully, but the following error is reported to stderr: "SystemErr: |10054| Connection reset by peer" Change Request: H555009381 Catalog import fails if "dcbf" file does not exist. Change Request: H555009382 Running backup on Cell Manager which is inhibited with command: omniclus -clus host_name -inhibit "time" produces default error report and abnormal end of session. Change Request: H555009560 Backup run twice when daylight saving time is changed. Change Request: H555009567 "debug.log" contains messages that Detail Catalog Binary Files (DCBF) is corrupted, although "omnidbcheck" does not report any error. Change Request: H555009593 When using the "omnimm -list_scratch_media 'pool_name'" command, no NDMP media is listed . Change Request: H555009779 After installing SSPUX410_056, aborted Oracle backup session hangs. Change Request: H555009833 When omnitrig is stopped and omnisv is started with "omnisv -start_mon", all services stop. Change Request: H555009877 Backup specification does not reflect correct schedules. Change Request: H555009895 omnidbutil -cdbsync fails in a non-MOM environment. Change Request: H555010043 Message "EIPCALREADYINIT" is filling the debug.log file. Change Request: H555010075 When virtual name does not match the hostname of the host currently running as the cell manager, all the scripts are considered as remote exec script. Change Request: H555010103 Imported catalog from media has catalog protection set to None. Change Request: H555010123 Restore session fails with error: "|Critical| From: RSM "" Time:<time> Media Management daemon subsystem reports: "Invalid slot specified." Change Request: H555010158 After aborting the backup session, new backup session is started and it hangs for a SmMaIdleTimeout variable, before it aborts. Change Request: H555010234 Integration restore hangs if SmWaitForNewClient variable is not properly set. Change Request: 8606289026 Device Flow Report is not working correctly. Change Request: 8606298931 Instead of positioning the tape to the beginning of the file, backint restore positions the tape to the beginning of the whole object. Change Request: 8606300821 Executing "crs -redebug" from command line displays a usage summary. PHSS_27602: Change Request: H555008641 Whenever there is OmniBack II activity going on in the Cell, the update of the NT clients fails. Change Request: H555008650 Restarting CS daemons using omnisv produces the following entries in the debug.log: "VELOCIS DB ERROR [0] internal error [-2005] server unavailable" Change Request: H555008680 When Cartridge Memory Support is activated for drives with the LTO-Ultrium media type, MSM (Media Session Manager) goes into a loop when try to reformatting or listing Cartridge Memory contents. Change Request: H555008690 If a Manager-of-Managers Server is also a MC/ServiceGuard virtual node, then the command "omnirpt -report list_sessions -timeframe <start_hours_ago><hours_duration> -multicell -no_multiple" lists the matching sessions from this node twice. Change Request: H555008704 Format the original medium and purge the database deletes Detail Catalog Binary Files (DCBF) files. Change Request: H555008716 Messages from pre/post exec scripts are not filtered. Change Request: H555008722 Reporting Email header does not contain device name. Change Request: H555008807 When backing up SAP integration with EMC split mirror functionality, not all the SAP files are backed up. Change Request: H555008832 Filesystem backup fails with an error: "[Major] From: BSM@<computer> "<object>" Time: <time> [61:3003] Lost connection to VBDA named <object> on host <host>. Ipc subsystem reports: "IPC Read Error System error: [232] Connection reset by peer" Change Request: H555008887 The connection with the host running SSEA agent is broken. Change Request: H555008908 When OmniBack II tries to backup non-existent SAP redo logs, session is ended as failed. Change Request: H555008927 While configuring OmniBack II reports using GUI, only datalists are listed (barlists are missing). Change Request: H555008950 After running "omnidbutil -cdbsync", the Catalog Database is lost. Change Request: H555008998 When a host backup session is using WakeOnLan option, it can not retry using specified value from the SmMaxAgentStartupRetries option. Change Request: H555009008 Restore Graphical User Interface (GUI) does not browse nested mountpoints. Change Request: H555009017 Load balancing does not work correctly in case of mount request. Change Request: H555009053 In case when only Single Server Edition license is applied, media agent fails during local backup. Change Request: H555009061 In Manager-of-Managers configuration with Central Media Management Database request for pools list report fails. Change Request: H555009083 In case that Detail Catalog Binary Files do not exist in the OmniBack II database, catalog import fails. Change Request: H555009153 OmniBack II does not display data written in Disk Agent (DA) context of the Graphical User Interface (GUI) during NDMP restore. Change Request: H555009194 Total blocks and Used blocks of medium are reported as negative numbers. Change Request: H555009209 a)During backup session using multiple devices, Cancel Device options leaves device locked. Device is not available to another session. b)If connection to a Monitor is lost during backup session the following message appears: "[Major] From: BSM@<HOSTNAME> "<OBJECT>" Time: <TIME> [61:3003] Lost connection to Monitor named "noname" on host <HOSTNAME>. Ipc subsystem reports: "IPC Read Error System error: [232] Connection reset by peer." Change Request: H555009263 "omnidbutil" ends abnormally during "readascii" process. Change Request: H555009286 Catalog binary file is deleted if original medium with copy is recycled or exported. Importing the catalog from copy medium is not possible. Change Request: 8606245960 Backup GUI displays selection, which is inconsistent with datalist. Change Request: 8606280024 Report "Extended report on used media" gives wrong info about used media in selected timeframe. PHSS_27454: Change Request: H555007590 OmniBack II does not check into what slot mediums were entered when mount request is confirmed. Change Request: H555007736 Report "Backup Error" does not properly display the number of errors of the backup session. Change Request: H555008063 Restore is started even in case that drive is disabled. Change Request: H555008105 Although the number of devices specified in the backup specification is greater than minimum value specified in load balancing options, the following message is displayed: "Number of devices specified in backup specification is smaller than MIN value of load balancing." Change Request: H555008180 DailyMaintenance backup deletes DCBF files of currently running backups. Change Request: H555008242 During backup of NDMP integration Backup Media Agent session completes with failures. Change Request: H555008261 Backup fails with an error: "Internal error. Allocation form library failed. The Media Management daemon reports: "Internal error: DbaXXXX functions."" Change Request: H555008452 Backup Session Manager does not terminate after the time specified in the SmDaIdleTimeout variable when connection to Disk Agent and Media Agent is lost. Change Request: H555008549 The following warning message is displayed: "[Warning] From: <hostname> "<datalist or barlist name>" Time: mm/dd/yy hh:mm:ss License not available "Split Mirror Extension for ONE EMC Symmetrix"" Change Request: H555008606 SAP offline backup using the VA integration reports the following errors: "[Major] From: BSM@<CM_hostname> "<datalist_or_barlist_name>" Time: mm/dd/yy hh:mm:ss [61:1002] The Snapshot Agent named "" on host <hostname> reached its inactivity timeout of 7200 seconds. The agent on host will be shutdown." Change Request: 8606262839 Configuration Report creates an incorrect list of scheduled backups. PHSS_26353: Change Request: H555006969 The OmniBack II database backup fails with 'Session Aborted' if the global variable 'RecoveryIndexDir=' refers to a directory that either does not exist or is not accessible. (This variable indicates the location of a copy of the RecoverIndex file.) Change Request: H555007177 If ".util HOSTNAME" returns nothing with "omnicc -import_host", crs ends abnormally. Change Request: H555007218 If you try to restore files in interval that does not include full backup the following error appears: "DB unknown error". Change Request: H555007362 Devices are locked after the end of media session. Change Request: H555007364 After OmniBack II services are stopped during backup and the remaining OmniBack II processes are killed, mmd and crs fail to start afterwards. Change Request: H555007383 "Restore by query" loops forever. Change Request: H555007428 Backup fails with error: "[Major] From: BMA@<HOST> Time:<TIME> [90:64] Can not unload exchanger medium (Storage slot is occupied.)". Change Request: H555007455 When source tape protection expires and the catalog is still protected, the tape is reused although a copy is attached to it. Transporting the catalog then results is protection set to "None" for the objects from original tape. Change Request: H555007485 Purgeadvisor reports that filename purge is needed even after the purge is done. Change Request: H555007524 Although the number of devices specified in the backup specification is greater then minimum value specified in load balancing options, the following message is displayed: "Number of devices specified in backup specification is smaller than minimum value of load balancing.". Change Request: H555007700 Backup fails with error: "[Critical] From: BMA@<HOST> "<DEVICE>" Time:<TIME> [90:30] SM/MA protocol error => aborting" Change Request: H555007901 After applying CS patch (PHSS_25962/PHSS_25963), the OB2PORTRANGE variable is ignored. Change Request: 8606248483 Address of a Cell Console client is incorrectly handled. PHSS_25962: Change Request: H555006771 Load balancing is not working properly. Change Request: H555006772 Omniback database suddenly stops reporting any details about sessions. Change Request: H555006788 After the execution of a session with load balacing used, devices remain locked and cannot be used for later sessions. Change Request: H555006819 Forced ownership in datalist does not function properly. Change Request: H555006843 Backup Session Manager abnormally ends. Change Request: H555006868 Vault reporting does not work properly. Change Request: 8606229643 Changing any option for a DCBF directory resets all other values to default. Change Request: H555006757 "End of Session" e-mail notification does not specify datalist name for which it was created. Change Request: H555006939 Restore of Oracle 8 objects hangs. Change Request: H555006948 Cell Request Server abnormally ends periodically. Change Request: H555006968 The 'omnidbrestore -autorecover' fails with error: "Current medium is refused for restore. Aborting!" Change Request: H555006998 Using a "\" sign when setting RecoveryIndexDir option in global options file sometimes causes Backup Session Manager failure. Change Request: H555007081 "omnisv -start_mon" is inactive for 1 second between loops. Change Request: H555007115 Executing "omnidbutil -purge -filenames <hostname>" fails with an error: "[Major] From: OMNIDBUTIL@<host> "" Time: <time> Functionality not (yet) supported." Change Request: 8606221771 Case sensitive search does not work. Change Request: 8606236143 Not all session manager processes are correctly stopped using csfailover.ksh script. Change Request: H555007234 Some objects are missing from the OmniBack internal database after upgrading OmniBack II A.03.xx to OmniBack II A.04.10. Defect Description: PHSS_32019: Change Request: QXCR1000201702 Shared memory locking buffer is too small to handle large number of concurrent resource locks. Resolution: Shared memory locking buffer is increased. Part of SSPUX410_092. PHSS_31051: Change Request: QXCR1000177996 Insufficient buffer space. Resolution: Backup specification is truncated if the size exceeds "STRLEN_MESSAGE". Change Request: QXCR1000193430 The 32 bit numbers for user ID and group ID are not supported. Only 16 bit IDs is supported. Resolution: Support for 32 bit numbers for user ID and group ID added. Change Request: QXCR1000193452 Detail catalog file is not deleted. Resolution: Detail catalog file is now removed. Added code to remove dcbf file on medium copy operation. Change Request: QXCR1000193518 Action problem. Resolution: Behavior is adjusted. Change Request: 8606325101 When Media Agent detects a dirty drive, the Restore Session Manager issues a Mount Request for cleaning tape instead of automatically loading a cleaning tape from the cleaning slot. Resolution: When Media Agent detects dirty drive, Data Protector automatically loads a cleaning tape for the backup and restore session. Change Request: H555013629 Command "omnirpt -list_media -protection NoOfDays" lists tapes with expired protection and no protection. Resolution: If option "-protection NoOfDays" is selected, OmniBack II lists only tapes whose protection will expire in "NoOfDays". Change Request: H555013676 Completed with failures exit status is used by Media Session Manager (MSM) on "LIB_RESCAN" when library has empty slots. Resolution: MSM exits with success on "LIB_RESCAN" when total media count is larger than media actually scanned. Change Request: H555013764 "Fixmpos" does not fix corrupted detail catalog part of database if problematic detail catalog does not exist. Resolution: The "mbfconfig" record is now deleted even if detail catalog file does not exist. Additional query on "mbfconfig" is implemented in the "cdbsync" functionality. PHSS_30343: Change Request: 8606362207 OmniBack II tries to lock new devices. When they are not available, it loops indefinitely. Resolution: If there is an unusable device and minimum load balance is set higher than 1, it is decreased. Change Request: H555011989 The post-exec script is set to execute if the pre-exec script executes without errors. The problem occurs when the session is aborting and the pre-exec script has not been executed yet as its execution status is still set to OK. Resolution: Added additional checking for session manager state to not execute the post-exec script when the state is set to "BSM_STATE_ABORTED". Change Request: H555011996 OmniBack II always shows the real tape capacity although the tape was initialized with the specific size. Resolution: OmniBack II properly shows a tape capacity. Change Request: H555012097 The query that calculates which objects from a full restore chain are required for a restore is time consuming. Resolution: The query is optimized. Change Request: H555012114 Invalid option "lan" is imported to the OmniBack II internal database (IDB). Resolution: On catalog import, the invalid "lan" option is removed if the "OB2IMPORTCATALOGSAP=1" variable is exported to the "omnirc" file. Change Request: H555012187 Barcode scan uses non-existent devices and/or barcode scan is attempted on devices without a barcode reader. Resolution: Additional functionalities are implemented. Barcode scan uses only existent devices, as displayed in the OmniBack II graphical user interface (GUI). Barcode scan is performed only on devices with a barcode reader. Change Request: H555012263 a.) After the failover, CRS quits because the MMD service quits. The MMD service quits because a time-out occurs while obtaining the licensing information. b.) Due to the memory leaks in the RDS extension modules, the memory usage per process increases. Eventually, the reallocation calls fail. Resolution: a.) Licensing information is released when the OmniBack II services end abnormally. b.) Memory leaks are eliminated. Change Request: H555012346 Restore Media Agent performs a serial search between objects instead of seeking to the beginning of the second object. Resolution: Algorithm for searching segment position on the tape is changed. If two objects are more than one segment apart, Restore Media Agent seeks to the beginning of the second object. Change Request: H555012374 If "new line" characters are present in the filenames tablespace in the OmniBack II internal database (IDB), the "omnidb -filesystem <Object> -session <Session_ID> -catalog" command stops responding. Resolution: "omnidb" command functions correctly regardless of the type of characters present in the filenames tablespace in the IDB. Change Request: H555012376 A session spends a long time deleting old objects from the IDB when an expired medium is used, causing other sessions to wait indefinetely. The reason is that the IDB is locked while objects are being deleted. Resolution: Other sessions are allowed to run during a deletion of old objects from the IDB. Change Request: H555012377 When expanding host objects, the DiskLabel buffer is overflown. Resolution: DiskLabel buffer size is enlarged. Change Request: H555012428 BSM quits in the function "BsmOnClose" when trying to set the Disk Agent's "endTime" variable. The pointer to the Disk Agent's structure is invalid at the time the BSM is trying to update it. Resolution: The "endTime" variable setting is moved higher in the "BsmOnClose" function code where the Disk Agent's structure pointer is still valid. Change Request: H555012804 "No more media for restore on device" message is displayed and restore session stops responding. This message may appear when restoring hardlinks (pointing to the same file) that are present on more than one tape. Resolution: Problem fixed in Restore Session Manager (RSM). For this fix to work, set the "RepositionWithinRestoredObject" variable in the global options file to 0. Change Request: H555013280 "Omnicellinfo" returns random responses. Resolution: "Omnicellinfo" return status changed. Change Request: H555013315 SQL restore may stop responding after installing the Cell Server patch PHSS_30129. Resolution: SQL restore completes successfully. Part of SSPUX410_091. Change Request: H555013333 Another tape is loaded instead of issuing another mount request. Resolution: Restore Session Manager (RSM) procedure is improved to issue a mount request until the correct tape is loaded. Change Request: H555013469 This occurs because there were some changes made to executing remote scripts as local when on a local host. Local execution of scripts fails because of an incorrect current working directory that is "/var/opt/omni/log" instead of "/opt/omni/lbin". Resolution: Corrected relative path of an executing script on a local host to be a full path with "/opt/omni/lbin/" preappended. Part of SSPUX410_090. PHSS_30128: Change Request: H555011451 Info about the type of session is not written on tape during a backup, while OBDB is correctly updated. After the tape import, information about the type of session does not enter OBDB, therefore the object version is not displayed in restore GUI for Lotus Notes integration. Resolution: Problem fixed in BSM and Media Session Manager (MSM). Change Request: H555011685 After restarting the failed session, the following dialog window appears: "Changes in the database detected. Would you like to refresh database objects." When the dialog is closed, the following error can be seen in the session report window: "Restart of Backup: <SESSION_ID> Error-Detail Unknown." Resolution: Backup Session Manager (BSM) is fixed to allow a successfully restart of the failed session. Change Request: H555011708 If there are no appendable media available for backup, a mount request is issued and 10 minutes later, the BMA exits without reporting any errors. After this, the BSM stops responding until the session is manually aborted. Resolution: BMA is not aborted when it is in the mount request state. Change Request: H555011784 Calculated sizes are not properly rounded up. Resolution: Size calculation of the OmniBack II database (OBDB) is improved by rounding up the size. Change Request: H555011788 "omnimm" consumes the 1 GB process address space and ends abnormally. Resolution: "omnimm" and "dbsm" are build as "EXEC_MAGIC" to enlarge the maximum process memory consumption up to 1.75 GB. PHSS_29865: Change Request: H555007363 After MC/ServiceGuard failover, semaphore locking problem and problem with cleaning shared memory occur. Since semaphore lock and shared memory are not cleaned after failover, all licenses are taken and there is no free license available for use. Resolution: Semaphores and shared memory are properly cleaned. Change Request: H555009725 Insufficient information regarding the "MaxMAperSM" global options variable in the Administrator's Guide and Release Notes. Resolution: Complemented the definition of the "MaxMAperSM" variable in the Administrator's Guide and Release Notes. Change Request: H555010638 OmniBack II limitation of 80 KB, reserved for the list of backup specifications, is exceeded. Resolution: Backup specification description data which is passed to the GUI twice, also at querying every single backup specification, has been left out to secure more space in the message. Change Request: H555010730 CRS intermittently ends abnormally on the HP-UX 11.x systems. Resolution: CRS is functioning correctly. Change Request: H555010787 Binaries are not properly build. Resolution: Binaries are properly build. Change Request: H555010817 With particular configurations of load balancing, waiting sessions do not obtain freed-up drives and they abort. Resolution: Session waits when there are no HP-UX or Windows drive licenses available. Change Request: H555010850 Bad option ("-- number") in the internal database (IDB) causes filename not to run. Resolution: During readdb/writedb process, bad options are skipped. Change Request: H555010860 Omnitrig process does not start any backup at all if the "holidays" file includes a syntax error. The "holidays" file is read at the beginning, before omnitrig starts the scheduled backups. In case of a syntax error, omnitrig aborts execution, which prevents omnitrig to read the scheduler files and to execute backups at scheduled times. Resolution: Omnitrig behavior in case of syntax errors in the "holidays" file is changed. Now omnitrig continues with an execution in such cases, which means that the syntax errors are skipped, logged to the "debug.log" file and most important scheduled backups are started. Change Request: H555010910 When all devices are locked and device used for backing up Logical Logs resource type is not included in the DYNAMIC range, the backup session will stop responding and the backup will not complete successfully. Resolution: Unused device will be unlocked when the global options variable "BackupDeviceIdle" times out. The new device will be locked then and used for a backup session. Part of SSPUX410_077. Change Request: H555011095 When a mount script is configured to issue an "omniabort" command, anytime a mount request is issued and not responded to by the time mount script is called, BSM ends abnormally after the mount script calls the "omniabort" command. Resolution: BSM functions properly when the "omniabort" command is used. Change Request: H555011119 OmniBack II recognizes i686 as non-Intel architecture, hence required license is the UNIX type license. Resolution: Added i686 as possible Linux architecture. Change Request: H555011230 OmniBack II does not compare hostnames correctly. Resolution: When OmniBack II checks for SSE license, hostnames are compared with case insensitive function. Change Request: H555011264 BSM checking for NULL message is not functioning correctly. Resolution: BSM checking for NULL message is functioning correctly. Checking for existence of Media Session Manager (MSM) session is added. If MSM session exists, BSM does not send SNMP messages. Change Request: H555011297 Report is not generated during a purge. Resolution: Purge report is generated. Change Request: H555011298 Functions "d_open" and "d_iopen" were denied while flushing hot files in the database. No other agent can connect at this time. Resolution: Defect in the libraries is corrected. Change Request: H555011344 MMD is checking for lock owner. Resolution: Checking for lock owner is disabled when unlock is called using "omnidbutil" command. Change Request: H555011379 BSM abnormally ends a session with only the SSE license available before checking whether there is an attempt to put the locked device in a queue. Resolution: BSM first checks whether there is an attempt to put the locked device in a queue. If it is, then it checks for the SSE license. If only the SSE license is present, then the session is ended abnormally. Change Request: H555011460 "-tree" option is missing in the IDB. Resolution: "-tree" option is added to the IDB. Change Request: 8606324070 Each time a needed device is released by concurrent session, timeout is reset. If session does not get the device because it is outran by another session, session waits for another "SmWaitForDevice". Theoretically, session can wait for the unlimited amount of time. Resolution: Timeout is reset only at the beginning of the DEVLOCKQUEUE-DEVLOCK state. This is forced by initializing timeout only at the beginning of session and when all needed devices are locked. Part of SSPUX410_082. PHSS_28740: Change Request: H555008723 MSM ignores status reported by the agents. Resolution: When waiting for Cell Manager update answer MSG_OPEN is swallowed. Cell Manager update result is now received asynchronically. Part of SSPUX410_071. Change Request: H555009054 In case that reconnect option is used for backup, it is possible that Media Agent fails due to a protocol error. Resolution: Protocol between Session Manager and Media Agent is changed in order not to acknowledge normal formatted messages. Change Request: H555010030 Meta files are removed although there are still object versions in the Omniback II database with reference to those meta files. Resolution: Meta files are no longer removed if there are object versions in the Omniback II database with references to them. Change Request: H555010269 OmniBack II A.03.50 IDB records for Exchange objects are not properly re-formatted during tape import procedure. Resolution: Tape import procedure reformats Exchange objects to Omniback II A.04.10 format during import phase. Change Request: H555010280 If Omniback II database contains a lot of object versions, a 'Stack Frame OverFlow Violation' error is reported in RDS.log and RDS ends abnormally. Resolution: Failing "WriteASCIIOVerTre" function is split into two separate functions. Change Request: H555010285 It can happen that media positions remain in database. When you try to import the medium an error occurs. Resolution: New "DbForceImportIfPositionsExist" variable is introduced in global file. When set to 1 it forces medium import even if medium positions exist. Change Request: H555010380 Meta files are linked to the last medium used by NDMP backup. When importing first (other than last) medium to Omniback II database, object versions are entered into the database. Since they already exist in the database it is assumed that the database reference to the meta file also exists while importing the last tape, but that is not the case. Resolution: Only when the old object versions already contain reference to the meta-file is the old object version copied over the newer and the reference to the meta file is assumed to be already existing. By default reference to meta-file is reestablished. Change Request: H555010381 When "omnidbutil -free_pool_update" is started during the backup, protected medium is moved back to free pool. Resolution: The option for disabling automatic deallocation of media is put in global file. Change Request: H555010432 Omnisv does not wait long enough before stopping crs service. Resolution: Global variable OmnisvStatusSleep is not correctly set and exported. Part of SSPUX410_074. Change Request: 8606307557 Currently locked and running devices are not taken into account by the algorithm. Resolution: The parameters passed to algorithm are changed. Part of SSPUX410_070. PHSS_28731: Change Request: H555009289 Omnisv does not wait long enough for crs service to be stopped. Resolution: New global option variable "OmnisvStatusSleep" is introduced. Add this new variable into global options file: OmnisvStatusSleep=X; where x should be in range 2<X<60. This will enable omnisv to wait for X seconds to successfully stop crs service. Change Request: H555009297 Before executing the object post-exec script, OmniBack II checks if session is aborting. If it is, then script does not execute. Resolution: Global variable PostExecOnAbortHostBackup was added. If this global variable is set to 1, the post-exec script will execute even if the session is aborting. Change Request: H555009322 Backup Session Manager (BSM) is going down too fast after sending "MSG_CLOSE" to connected monitors. Resolution: "OB2BSMSLEEPBEFORECLOSE" environment variable is added in order to wait few seconds before going down. Change Request: H555009381 During catalog import OmniBack II tries to remove the original "dcbf" file. If this file does not exist, catalog import fails. Resolution: Catalog import is improved in order not to abort in case if "dcbf" file does not exist. Change Request: H555009382 Crs tries to receive messages by inhibited Cell Manager. Resolution: If Cell Manager is inhibited, Data Protector does not send or receive any messages, but exits with message: "|12:1602| Cannot access the Cell Manager system". Change Request: H555009560 The algorithm, that handles the daylight saving time changes is uncomplete. Resolution: The algorithm is changed for both time changes: 02h->03h and 03h->02h. Change Request: H555009567 "omnidbcheck" does not correctly report corruption in Detail Catalog Binary Files (DCBF). Resolution: "omnidbcheck" is improved in order to correctly report errors on the Detail Catalog Binary Files (DCBF). Change Request: H555009593 NDMP media data format is not marked as OmniBack II data format. Command "omnimm -list_scratch_media 'pool_name'" lists only OmniBack data format. Resolution: Command "omnimm -list_scratch_media 'pool_name'" is changed; now it also lists NDMP data format media. Change Request: H555009779 When Oracle integration backup issues a mount request and an attempt to abort backup is made, the omniabort will hang and the session will not shut down. This happens with SSPUX410_056 installed. Resolution: Backup Session Manager (BSM) is fixed. Part of SSPUX410_061. Change Request: H555009833 "omnisv -start_mon" checks status of all services. Resolution: omnisv -start_mon checks status of all services excluding omnitrig. Change Request: H555009877 Schedules with excluded days are interpreted incorrectly. Resolution: Schedules interpretation for excluded days is changed. Change Request: H555009895 After checking for mom_server file error is not cleared. Resolution: After checking for mom_server file error is cleared. Change Request: H555010043 Function IpcExit() is never called, so each time the function IpcInit() is called, the error is written in debug log. Resolution: Function IpcExit() is put to correct place in the code. Change Request: H555010075 When session is configured using post or pre exec scripts on virtual machines no check is being made to determine if IP is local. Only hostnames (strings) are compared. Resolution: Additional checking is made to determine if IP is local. Change Request: H555010103 When importing catalog its protection is set to None. When catalog is imported with None protection it is purged out of database first time when purge is started. Resolution: Catalog's protection is changed to be set to Permanent after importing it. Change Request: H555010123 OmniBack II does not lock tapes properly. Resolution: OmniBack II checks if tape is locked by any of the owners before locking the tape. Change Request: H555010158 Omniback II aborts all OB2BAR connections which do not make connection to object in time. Resolution: OB2BAR connections that do not make it to objects in time are now aborted properly. Change Request: H555010234 When Media Agent is in stopping state Restore Session Manager (RSM) can not handle restore request from the OB2BAR. Resolution: Request list is reset after Media Agent gets MSG_STOP from RSM. Change Request: 8606289026 When backup is aborted OmniBack II does not enter "End Time" variable in the database. Resolution: When session is aborted or mount request is issued OmniBack enters "End time" variable in the database. Change Request: 8606298931 Restore position for file is not calculated. Resolution: Calculation of file position within object is added. Change Request: 8606300821 While parsing arguments passed to crs binary, missing arguments after -redebug options are not expected thus abort follows and help is written. Resolution: Parsing is changed. When arguments for redebug are not passed on command line, trace file is examined. If trace file does not include parameters, help is written. PHSS_27602: Change Request: H555008641 OmniBack II erroneously tries to unpack already unpacked error message in "omnicc" and overwrites another variable. Resolution: Error unpacking and variable name are changed. Change Request: H555008650 CRS service is trying to connect to Raima Database Server while it is still in pending state. Resolution: CRS service waits for RDS to start listening. Part of SSPUX410_043. Change Request: H555008680 Media Agent ends abnormally when listing all Cartridge Memory contents for the specific medium or reformatting Cartridge Memory of a specific medium. Resolution: MSM (Media Session Manager) is improved in order to session finish successfully in case of reformatting cartridge memory or listing cartridge memory contents. Part of SSPUX410_039. Change Request: H555008690 When running "omnirpt" command all the cell servers from the "mom_info" and the local Cell Server are queried for matching sessions. The virtual node and the local host are actually the same machine, so the matching sessions are listed twice. Resolution: The function gethostname() is not used any more to determine if the inspected host is also the local host, cause in case of a Manager-of-Managers/ServiceGuard environment it returns the physical node hostname and not the virtual node hostname, making the virtual hostname being seen as a non-local host. In this way the virtual hostname is not queried for matching sessions any more. Change Request: H555008704 Purge operation purges catalogs even if copied tape still exist in the database. Tape format removes catalog from the database even if the copy tape is still protected. Resolution: The Detail Catalog Binary Files (DCBF) files are not deleted if the copy tape has valid protection. Change Request: H555008716 Non OmniBack II format messages from pre/post exec script are not filtered. Resolution: The Backup Session Manager is changed in order to filter non OmniBack II format messages from pre/post exec script. Change Request: H555008722 Device name is not exported in EVENTOBJECT environment variable. Resolution: Device name is exported in to EVENTOBJECT environment variable. Change Request: H555008807 In split mirror environment with huge SAP databases it can happen that the size of the message buffer OmniBack II uses is too small to receive complete list of SAP files to be backed up. Resolution: Setting the OB2IPCBUFSIZE environment variable in the /opt/omni/.omnirc file on Cell Server, R1 and R2 hosts, specifying the desired amount of memory to be used for the buffer solves the described problem. Please read the following instructions and make sure that the patches listed in "Other Dependencies" section (see below) are installed and the environment variable is set on Cell Server, R1 and R2 systems before running the backup! How to determine the buffer size? --------------------------------- N_obj: number of objects (files) N_fs: number of file systems N_lvmvg: number of volume groups N_dg: number of disk groups N_rdsk: number of rawdisks Obj: Object Name ObjBack: Object Backup Name MntPathLen: Path name on backup (R2) host (example: /var/opt/omni/tmp/App_host) fsmnt: File System Mount Point fsdev: File System Device File (example: /dev/dsk/[c0t1d1,lvol1]) vg: Volume group (ex: /dev/vg01) dg: Disk group (VxVM) - dependence on mapfile which is required for creating disk group (example:/dev/vx/dsk/dg01) rdsk: Raw disk file name (example: /dev/rdsk/c1t1d1) AvgLen_<xxx> average length of <xxx> There are two different buffers used: 1. BSM <-> R1 2. R1 <-> R2 Calculating the BSM <-> R1 buffer size -------------------------------------- MsgSize_BSM_R1 = N_obj * (AvgLen_Obj + 1 + MntPathLen) Calculating the R1 <-> R2 buffer size ------------------------------------- MsgSize_R1_R2 = N_obj*(AvgLen_Obj+1+AvgLen_ObjBack) + N_fs*(AvgLen_fsmnt*2 + MntPathLen + AvgLen_fsdev*2)+ N_lvmvg*(AvgLen_vg*2) + N_dg*(AvgLen_dg*2) + N_rdsk*(AvgLen_rdsk*2) Calculating the OB2IPCBUFSIZE value ----------------------------------- OB2IPCBUFSIZE > max (MsgSize_BSM_R1, MsgSize_R1_R2) RESTORE NOTE: ------------- If restore is started using the sapbda utility, the variable OB2IPCBUFSIZE must be exported to environment prior to starting sapbda. Known problems: --------------- If the calculated variable OB2IPCBUFSIZE is correctly set, but is still too small for the file list to fit into the message buffer, the session will fail with the following error seen in the report: BR295I Splitting mirror disks... BR280I Time stamp <time> BR279E Return code from '/opt/omni/lbin/ob2smbsplit /<sap_homedir_path>/.<filename>.lst': 2 BR299E Split/resynchronization of mirror disks failed In this case the variable OB2IPCBUFSIZE must be recalculated to appropriate value. See above how to determine it. Part of SSPUX410_033. Change Request: H555008832 Last message from Disk Agent is sometimes lost. This causes Disk Agent's status reported as "Failed". Resolution: New environment variable: OB2VBDASLEEPBEFORECLOSE is introduced. Its default value is 0. Setting it to a positive number, in /<OMNIBACK_HOME>/.omnirc file, it specifies number of seconds to pass before Disk Agent completes after sending the last block of data. Sleep time insignificantly influences backup performance. 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. Change Request: H555008908 By design, whenever there are no objects backed up, OmniBack II ends session as failed. Resolution: Two new global variables have been introduced: a) SessSucessfullWhenNoObjectsBackedUp Setting this variable to 1 user can change the OmniBack II behavior in order to end the session as successful when there are no objects backed up. b) TreatScriptReturnAsNormal Setting this variable to a certain number instructs OmniBack II to treat all the script returns equal to the specified number as normal. Change Request: H555008927 Barlists are members of a group which is not displayed under reporting group in GUI Reporting. Resolution: Barlists are moved to a group that is displayed in GUI. Change Request: H555008950 If "omnidbutil -cdbsync" is started on the Manager-of-Managers client, local Media Management Database (MMDB) is used for database synchronization. Resolution: If "omnidbutil -cdbsync" is running on a Manager-of-Managers client, it issues an error message and stops the operation. Change Request: H555008998 When a host backup session is using WakeOnLan option, it can not retry using specified value from the SmMaxAgentStartupRetries option and there are no mechanism to specify the timeout between retries. Resolution: When a host backup session is using WakeOnLine option, it can retry using specified value from the SmMaxAgentStartupRetries option and specified timeout value from MinDelayForConnectionRetry option. Change Request: H555009008 Tree options are not entered into OmniBack II database during host backup of nested mountpoints. Resolution: Tree options are entered in to OmniBack II database. Change Request: H555009017 In case that mount request appears at the beginning of the backup, load balancing does not work correctly. After the confirmation of mount request, filesystem which is supposed to be started as the first one, is started as the last one. Resolution: Load balancing is improved in order to work correctly in case of mount request. Change Request: H555009053 In case when only Single Server Edition license is applied, Backup Session Manger aborts the session before checking if there was an attempt to put the locked device in a queue. Resolution: Backup Session Manger checks if there is an attempt to put the locked device in a queue. If this is the case it check for the Single Server Edition license. Part of SSPUX410_052. Change Request: H555009061 In Manager-of-Managers configuration where Database Session Manager acts as a gateway for direct access to Media Management Database, main Database Session Manager is not aware of pools list report and cannot get report information from the Media Management Database. Resolution: Database Session Manager can get pools list report information from the Media Management Database. Change Request: H555009083 During catalog import OmniBack II tries to remove the old binary files and create new ones. In case that old files do not exist, catalog import fails. Resolution: Catalog import is improved in order not to abort, in case that Detail Catalog Binary Files do not exist. Change Request: H555009153 Restore Session Manager (RSM) does not include the information about data written when updating Graphical User Interface (GUI) Disk Agent (DA) context. Resolution: The information about data written is added to Restore Session Manager (RSM) messages sent to Graphical User Interface (GUI). Change Request: H555009194 Data type 'Long' does not allow numbers bigger than 2TB. Resolution: Reported Total blocks and Used blocks of medium are limited to 2TB. Change Request: H555009209 a)Device that was locked during backup session, can not be unlocked using Cancel Device option and it is not available for another session. b)If backup is started with reconnect option, in case that Monitor is closed, OmniBack II reports Error that connection to Monitor was lost. Session continues and completes successfully. Resolution: a)Device is unlocked for another session. b)Only lost connections with Disk Agent (DA) or Media Agent (MA) are reported as error. Part of SSPUX410_056. Change Request: H555009263 Files names with new line are not handled correctly. Resolution: "readdb" and "writedb" was changed so that file names with new line are handled correctly. Change Request: H555009286 When Recycling or exporting original medium from OmniBack II database purge deletes Detail Catalog Binary Files (DCBF) even if the copy medium is still protected in the OmniBack II database. In addition importing catalog from copy is not possible. Resolution: Catalog import from copy medium is possible. Part of SSPUX410_053. Change Request: 8606245960 GUI is not able to handle nested mount points. When GUI receives excluded directory from datalist file it assumes that the part of the string between first and second slash represents mount point. Besides this, mount point is shown in GUI as a mountpoint and as directory. Resolution: GUI is aware of nested mountpoints. Change Request: 8606280024 OmniBack II does not properly create list of sessions for used media in selected timeframe. Resolution: "Extended report on used media" report is removed from reporting. PHSS_27454: Change Request: H555007590 Before loading medium on mount request confirmation database is not checked properly. Resolution: On mount request confirmation database is checked properly. Change Request: H555007736 Errors that were sent by Disk Agent are doubled. Resolution: OmniBack II reports right number of errors for the backup session. Change Request: H555008063 In case that integration restore session is started, restore session manager does not check if the device is disabled. Resolution: Restore Session Manager is changed so that the restore will not be started if the device is disabled. Change Request: H555008105 Backup Session Manager uses incorrect variable when calculating the number of devices used for backup. Resolution: Session Manager uses proper variable. Part of SSPUX410_021. Change Request: H555008180 If backup protection is specified in a time interval (-days, -weeks) and backup spans over multiple media, "omnidbutil -purge -daily" command which is started by DailyMaintenance process deletes DCBF files for the media used in backup which ran at the same time as the DailyMaintenance. Resolution: "omnidbutil -purge -daily" is improved in order not to remove DCBF files for currently running backups. Part of SSPUX410_022. Change Request: H555008242 In case that NDMP backup contains large number of files, Backup Media Agent uses large amount of memory. Resolution: Backup Media Agent memory usage is improved so it can backup up to 5 million files. Change Request: H555008261 In case of a Media Management Database corruption backup can fail due to problems with the media allocation. Resolution: Media allocation is improved. Change Request: H555008452 In some cases because of incorrect agent exit code Backup Session Manager does not terminate other agents in correct order, which results in Backup Session Manager does not terminate. Resolution: The exit code was changed. Change Request: H555008549 OmniBack II never looks for the new TB EMC license (B6959CA), but always looks for the old EMC standard license (B6959BA). The same is with the new TB XP license. Resolution: The Backup Session Manager agent looks also for the new TB EMC and TB XP licenses. Part of SSPUX410_030. Change Request: H555008606 Backup Session Manager does not set the timeout of infinitive seconds for the SNAPA agent, but leaves the timeout set to the value of SmDaIdleTimeout. Resolution: Backup Session Manager sets the timeout of infinitive seconds for the SNAPA agent. Change Request: 8606262839 Database session manager compares days, not taking into account 15 minute units. Therefore report shows some additional backups that are scheduled past the specified time frame. Resolution: Beside days Database Session Manager compares 15 minute units. PHSS_26353: Change Request: H555006969 If RecoveryIndex path is incorrect, the file can not be created. OmniBack II then shows a 'Major' error and aborts the session. Resolution: Messages are changed to 'Warning' and the session is not aborted if the RecoveryIndex path is invalid. Change Request: H555007177 OmniBack II returns wrong exit code when the client does not return any information. Resolution: The exit code is changed. Change Request: H555007218 Selecting files for restore within interval that does not include the full backup will trigger an error in the list_full_rest_chain function. Resolution: The function marks an error and sends it to GUI, which will show a message: "You have chosen an interval which does not include all the sessions needed to compose a full restore chain. Please reconnect to the Cell Server". Change Request: H555007362 Devices are locked with device lock, which can differ from device name. When devices are unlocked, device name is always used. If device name and device lock are not equal, device unlock fails. Resolution: Device lock/unlock policy is synchronized. Change Request: H555007364 When all the OmniBack II services are up and running, backup is started. If during backup OmniBack II services are stopped due to some reason and all the OmniBack II processes are killed, mmd and crs from OmniBack II services will be unable to start. Resolution: There were some problems with licenses, which were not released properly. Licenses are now released properly. After fix installation, reboot of Cell Server host is highly recommended! Part of SSPUX410_013 Change Request: H555007383 Database file search performance is poor. Resolution: Database search performance is improved. Change Request: H555007428 Executing an "enter" operation for the slot being used for backup results in backup failure. Resolution: New global option EnterEjectCheckLocking is introduced. If this option is set, Media Management operation checks if slot is locked and does not use it. Part of SSPUX410_012. Change Request: H555007455 Object protection on the copied medium is set to "None" after original tape protection expires. Resolution: The catalog is now transposed from the source. The object protection for the copied medium is set on the same level as medium protection the catalog is transported from the source. Change Request: H555007485 Purge advisor incorrectly interprets the growth of the database and reports daily needed purges. Resolution: Purge advisor correctly recognizes the database when purge of the database is needed. Change Request: H555007524 Backup Session Manager uses incorrect variable when calculating the number of devices used for backup. Resolution: Session Manager uses proper variable. Change Request: H555007700 In case in which reconnect option is used for backup, it is possible that Media Agent fails due to a protocol error. Resolution: Protocol between Session Manager and Media Agent is changed in order not to acknowledge normal formatted messages. Complete functionality of fix will be available when Media Agent patch PHSS_26357/PHSS_26358 is installed - or successors of it. Part of SSPUX410_017. ID = HSLco34429 The OB2PORTRANGE variable is not exported. Resolution: The OB2PORTRANGE variable is exported. Change Request: 8606248483 When a Cell Console client connects to the server, user name, system name and domain are parsed correctly, but IP address is not. Resolution: A new environment variable 'OB2CRSSTRICTHOSTNAMECHECKING' is introduced. Setting its value to 1 is to enforce the use of hostnames obtained from IP address. PHSS_25962: Change Request: H555006771 There is no warning reported when one creates a datalist or a barlist with load balancing enabled and minimum number of devices greater than number of configured logical devices. Resolution: Comparison of minimum and configured devices number is implemented. Change Request: H555006772 Aborting an import session corrupts Omniback internal database. Resolution: Aborting an import session is properly handled and it does not corrupt internal database. If a database corruption has been experienced because of this defect, then after installation of this patch, the corruption can be removed and the import of OmniBack II 3.x tapes be enabled as follows: 1. step: Import the problematic tape. The import itself will fail, complaining about catalog and media management database not being in sync. But internally it will remove the suspective media position from the database which makes second step possible. 2. step: Import the problematic tape again. This succeeds and results in imported medium and fixed database. Part of SSPUX410_007. Change Request: H555006788 Device lock counter is not working correctly. Resolution: Device lock counter is working properly and the devices are unlocked after the session ends. Part of SSPUX410_006. Change Request: H555006819 Object ownership is incorrectly set if it is specified in the datalist. Resolution: Object ownership is correctly set. Part of SSPUX410_015. Change Request: H555006843 Backup Session Manager abnormally ends in cases when there are more than 100 objects within one data segment. Resolution: Backup Session Manager works properly with unlimited number of objects within one data segment. Change Request: H555006868 Omniback incorrectly compares selected libraries versus all libraries when creating "List of Media" report. Resolution: "List of Media" is created properly. Change Request: 8606229643 Omniback does not check whether options have been passed from the command line. Resolution: Additional checking of options is implemented for the case that options have been sent from command line. Change Request: H555006757 Datalist name is not exported into environment. Resolution: Datalist name is exported into environment. Change Request: H555006939 When delay between two connections for different Oracle 8 objects is bigger that the value of SmWaitForNewClient global variable, restore hangs. Resolution: Omniback deletes barlist from memory and starts new restore session in case that Restore Session Manager timed out and new connection for restore was accepted. Change Request: H555006948 Command "omnicc -query" causes memory leaks in Cell Request Server. Resolution: Memory leaks are removed. Part of SSPUX410_001. Change Request: H555006968 The '-autorecover' option in 'omnidbrestore' command does not set the correct block size for the device. Resolution: The code for setting the block size was corrected. Change Request: H555006998 If "\" sign is the last character when setting RecoveryIndexDir value, Backup Session Manager fails because of incorrect parsing of the value. Resolution: Any "\" sign that appears at the end of an argument is cut off during the parsing. Change Request: H555007081 With 1 second inactivity between loops, "omnisv -start_mon" is executed too often. Resolution: New option "-timeout" is added for omnisv. Usage: "omnisv -start_mon -timeout N" where N is time in seconds. Change Request: H555007115 omnidbutil is not able to connect to Administration Session Manager (ASM). Resolution: Missing fuctionality is added to ASM. Change Request: 8606221771 Flag for case sensitivity is not checked before search session is executed. Resolution: Case sensitivity flag is always checked. Change Request: 8606236143 The regular expression that is parsed by the awk script does not return the process ID (PID) which should be killed. Resolution: Regular expression string in awk parse command is changed. Change Request: H555007234 Objects whose protection has expired are purged from OmniBack internal database during the upgrade. Resolution: New environment variable OB2UPGRADEIGNOREEXPIREDOBJECTS is introduced. Setting its value to 1 in /opt/omni/.omnirc file will purge objects with expired protection during the upgrade. Otherwise, unprotected objects are left intact. Part of the SSPUX410_008. SR: QXCR1000201702 8606325101 H555013764 H555013629 H555013676 QXCR1000177996 QXCR1000193430 QXCR1000193452 QXCR1000193518 H555012114 H555011996 H555011989 H555013333 H555013315 H555013280 H555012263 H555012804 H555012346 8606362207 H555012374 H555012428 H555012097 H555012187 H555012376 H555012377 H555013469 H555011788 H555011708 H555011451 H555011784 H555011685 8606324070 H555011230 H555010730 H555010910 H555011460 H555011119 H555011344 H555010850 H555011264 H555010860 H555011095 H555010817 H555010638 H555007363 H555011297 H555011298 H555011379 H555010787 H555009725 H555009054 H555010269 H555010432 H555010280 H555008723 H555010030 H555010380 H555010381 H555010285 8606307557 H555010234 H555009593 8606300821 H555009567 H555009297 H555009289 H555010075 8606298931 H555010158 H555009895 H555009877 H555009779 H555009322 H555009721 H555009560 H555010103 H555009381 H555009382 H555010123 H555009833 8606289026 H555010043 H555009286 H555008908 H555008891 H555008927 8606280024 H555008958 H555008887 H555008998 8606245960 H555009061 H555009053 H555009017 H555009008 H555009153 H555008722 H555008704 H555008650 H555008641 H555009209 H555009083 H555009263 H555008651 H555008832 H555008913 H555008716 H555008680 H555008950 H555009194 H555008807 H555008690 H555008754 H555008549 8606262839 H555008105 H555008242 H555008063 H555008180 H555008261 H555008452 H555008606 H555007590 H555007736 8606248483 H555007700 H555006969 H555007524 H555007218 H555007362 H555007903 H555007364 H555007383 H555007428 H555007455 H555007177 H555007485 H555006757 H555006948 H555006939 H555006868 H555006968 H555006788 H555007115 H555007234 8606236143 H555007081 H555006998 8606221771 H555006771 H555006843 H555006772 8606229643 H555006819 Patch Files: /opt/omni/.CII_CS /opt/omni/newconfig/etc/opt/omni/sg/csfailover.ksh /opt/omni/newconfig/etc/opt/omni/options/global /opt/omni/sbin/omnidbutil /opt/omni/sbin/omnitrig /opt/omni/sbin/omnidbrestore /opt/omni/sbin/omnisv /opt/omni/sbin/omnisv11 /opt/omni/sbin/omnidbcheck /opt/omni/sbin/omnidbinit /opt/omni/sbin/utilns/get_info /opt/omni/lib/libob2eadm.sl /opt/omni/lib/libob2ecdb.sl /opt/omni/lib/libob2ecmn.sl /opt/omni/lib/libob2emmdb.sl /opt/omni/lib/lib_rdm.sl /opt/omni/lbin/bsm /opt/omni/lbin/rsm /opt/omni/lbin/dbsm /opt/omni/lbin/crs /opt/omni/lbin/dbbda /opt/omni/lbin/asm /opt/omni/lbin/msm /opt/omni/lbin/mmd what(1) Output: /opt/omni/.CII_CS: None /opt/omni/newconfig/etc/opt/omni/sg/csfailover.ksh: None /opt/omni/newconfig/etc/opt/omni/options/global: None /opt/omni/sbin/omnidbutil: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:53 :13 2004 /opt/omni/sbin/omnitrig: HP OpenView OmniBack II A.04.10; internal build PHSS _29865/PHSS_29866, built on Thu Nov 20 17:16 :56 2003 /opt/omni/sbin/omnidbrestore: HP OpenView OmniBack II A.04.10; internal build PHSS _29865/PHSS_29866, built on Thu Nov 20 17:17 :27 2003 /opt/omni/sbin/omnisv: HP OpenView OmniBack II A.04.10; internal build PHSS _29865/PHSS_29866, built on Thu Nov 20 17:16 :46 2003 /opt/omni/sbin/omnisv11: HP OpenView OmniBack II A.04.10; internal build PHSS _29865/PHSS_29866, built on Thu Nov 20 17:21 :32 2003 /opt/omni/sbin/omnidbcheck: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:53 :20 2004 /opt/omni/sbin/omnidbinit: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:52 :59 2004 /opt/omni/sbin/utilns/get_info: None /opt/omni/lib/libob2eadm.sl: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:52 :39 2004 /opt/omni/lib/libob2ecdb.sl: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:50 :51 2004 /opt/omni/lib/libob2ecmn.sl: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:48 :22 2004 /opt/omni/lib/libob2emmdb.sl: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:49 :19 2004 /opt/omni/lib/lib_rdm.sl: None /opt/omni/lbin/bsm: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:56 :25 2004 /opt/omni/lbin/rsm: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:57 :30 2004 /opt/omni/lbin/dbsm: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:53 :47 2004 /opt/omni/lbin/crs: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 15:03 :28 2004 /opt/omni/lbin/dbbda: HP OpenView OmniBack II A.04.10; internal build PHSS _29865/PHSS_29866, built on Thu Nov 20 17:19 :46 2003 /opt/omni/lbin/asm: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:59 :19 2004 /opt/omni/lbin/msm: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:58 :22 2004 /opt/omni/lbin/mmd: HP OpenView OmniBack II A.04.10; internal build PHSS _32019/PHSS_32020, built on Fri Oct 15 14:58 :46 2004 cksum(1) Output: 2050380835 1552447 /opt/omni/lbin/bsm 1722067850 1314395 /opt/omni/lbin/rsm 2269615409 1543558 /opt/omni/lbin/dbsm 1163459306 809437 /opt/omni/lbin/crs 2023156276 736141 /opt/omni/lbin/dbbda 2276025457 801250 /opt/omni/lbin/asm 3890561233 908111 /opt/omni/lbin/msm 890638828 608483 /opt/omni/lbin/mmd 1628456796 889692 /opt/omni/lib/libob2eadm.sl 3565046124 922438 /opt/omni/lib/libob2ecdb.sl 833447582 931552 /opt/omni/lib/libob2ecmn.sl 1568158191 750239 /opt/omni/lib/libob2emmdb.sl 1057310634 747217 /opt/omni/lib/lib_rdm.sl 2111885075 920041 /opt/omni/sbin/omnidbutil 4095712355 571355 /opt/omni/sbin/omnitrig 1670052680 550548 /opt/omni/sbin/omnidbrestore 1420691591 419493 /opt/omni/sbin/omnisv 870777921 446464 /opt/omni/sbin/omnisv11 572379331 817496 /opt/omni/sbin/omnidbcheck 2413169079 26880 /opt/omni/sbin/utilns/get_info 2404051215 714920 /opt/omni/sbin/omnidbinit 60206861 11133 /opt/omni/.CII_CS 1522663409 30114 /opt/omni/newconfig/etc/opt/omni/options/ global 4109013506 2408 /opt/omni/newconfig/etc/opt/omni/sg/ csfailover.ksh Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: If this Cell Server patch is installed on a Cell Manager system in a Manager of Manager's environment with a Centralized Media Management Data Base (CMMDB/MOM), then it must also be installed to all other Cell Managers running the same Operating System. For Cell Manager systems on other OS platforms, the respective equivalent patch or it's successor must be applied: PHSS_32019 for HP-UX 10.20 PHSS_32020 for HP-UX 11.X OMNIBACK_00122 for Windows 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_30829: Disk Agent (DA) packet patch, release date: Available Change Request: H555012804 PHSS_30829 is required for this defect fix. PHSS_30348: Cell Console (CC) packet patch, release date: Available Change Request: H555009725 Change Request: H555009877 Change Request: H555009286 Change Request: H555008927 Change Request: H555008807 Change Request: H555007485 Change Request: 8606245960 Change Request: 8606280024 PHSS_30348 is required for these defect fixes. PHSS_30568: SAP packet patch, release date: Available Change Request: H555008908 Change Request: H555008807 PHSS_30568 is required for these defect fixes. PHSS_28341: EMC packet patch, release date: Available Change Request: H555008807 PHSS_28341 is required for this defect fix. PHSS_30339: Core packet patch, release date: Available Change Request: H555008950 Change Request: H555008807 Change Request: H555007590 Change Request: H555006771 Bad catalog access messages are displayed without PHSS_30339. PHSS_30570: SureStore Agent (SSEA) packet patch, release date: Available Change Request: H555008887 PHSS_30570 is required for this defect fix. PHSS_31055: Media Agent (MA) packet patch, release date: Available Change Request: H555010787 Change Request: H555008680 Change Request: H555008242 Change Request: H555007700 Change Request: H555009054 Change Request: H555010030 PHSS_31055 is required for these defect fixes. Supersedes: PHSS_25962 PHSS_26353 PHSS_27454 PHSS_27602 PHSS_28731 PHSS_28740 PHSS_29865 PHSS_30128 PHSS_30343 PHSS_31051 Equivalent Patches: PHSS_32020: s700: 11.00 11.11 s800: 11.00 11.11 Patch Package Size: 4780 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_32019 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_32019.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_32019. 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_32019.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_32019.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_32019: 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". In some cases, when machine is rebooted, "omnidbutil -clear" is executed before rds service is up and running. As a result, this command is not executed and error is reported to rc.log. In such cases delay in environment variable OmniDBUtilClearSleep=DelayInSeconds in global file should be set. Default value is set to 0. Patch includes the following Site Specific Patches: SSPUX410_001 SSPUX410_006 SSPUX410_007 SSPUX410_008 SSPUX410_012 SSPUX410_013 SSPUX410_015 SSPUX410_017 SSPUX410_021 SSPUX410_022 SSPUX410_030 SSPUX410_033 SSPUX410_039 SSPUX410_043 SSPUX410_046 SSPUX410_052 SSPUX410_053 SSPUX410_056 SSPUX410_061 SSPUX410_070 SSPUX410_071 SSPUX410_074 SSPUX410_077 SSPUX410_082 SSPUX410_090 SSPUX410_091 SSPUX410_092 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 Cell Manager is installed on your system, then you must re-apply this SSP after installing this Cell Manager patch.