Patch-ID# 115224-02 Keywords: netbackup 4.5fp_3 informix agent Synopsis: NetBackup 4.5FP_3 NB_INX_45_5_F fix Date: Oct/08/2003 Install Requirements: None Solaris Release: 2.6 7 8 9 SunOS Release: 5.6 5.7 5.8 5.9 Unbundled Product: Veritas NetBackup Unbundled Release: 4.5FP_3 Xref: Topic: Veritas NetBackup 4.5FP_3 Informix Agent jumbo patch Relevant Architectures: sparc BugId's fixed with this patch: 4924258 Changes incorporated in this version: 4924258 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: 115218-02 or greater Obsoleted by: Files included with this patch: /openv/netbackup/dbext/INFORMIX.solaris2.6.tar.Z /openv/netbackup/dbext/INFORMIX.solaris2.6.version Problem Description: 4924258 Need FP4 or latest patches in Sun Patch format Patch Installation Instructions: ------------------------------------------------------------------------- Refer to the Install.info file within the patch for instructions on using the generic 'patchadd' and 'patchrm' scripts provided with each patch. Any other special or non-generic installation instructions should be described below. ------------------------------------------------------------------------- Special Install Instructions: 1. add Sun-patch 2. - Server Remote installation instructions: To run installation of database clients (including local box if present). Run update_dbclients script located at /usr/openv/netbackup/bin. Example: update_dbclients -ClientList or update_dbclients If the 32-bit NetBackup DataBase Agent is currently installed, the script /usr/openv/netbackup/bin/update_dbclients will report in the trace file: Extension version files match - no update needed. The following is displayed to standard output: [N_number] client update(s) had up-to-date software according to the database extension version file. To force the installation of the database extension software for these client updates, you need to execute: update_dbclients -ForceInstall -ClientList or update_dbclients -ForceInstall For more information look in the NetBackup Oracle System Administrator's Guide. 2. - Local installation instructions: Warning: Before installation - If production Informix scripts are found in the /usr/openv/netbackup/ext/db_ext/informix/scripts, please save them in another location to prevent them from being overwritten. Run /usr/openv/netbackup/bin/install_infxbsa 3. - Local installation instructions: Insert this information into the table bar_version in the sysutils database. bar_version bsa_version bar_sm sm_version 1 1.1.0 VERITAS-NetBackup 1 insert into bar_version values ("1", "1.1.0", "VERITAS-NetBackup","1") ============================================ ================= KNOWN ISSUES ================= If you want to browse and restore backups that are owned by another client, perform the following: 1) Ensure the NetBackup server is configured to allow the redirected restore. (See the NetBackup System Administrator?s Guide - UNIX or the NetBackup System Administrator?s Guide - Windows NT/2000) 2) Set the Informix environment variable, INFXBSA_CLIENT. For example, if you are using the C shell, the following command specifies the machine "jupiter" as the client to browse. setenv INFXBSA_CLIENT jupiter 3) For doing a redirected restore, restore the data in 2 steps, Physical restore using Logical restore using (DO NOT USE onbar -r) ============================================ Description: If the time on the Informix client is ahead of the time of the master server, server, then some and not all of the backed-up logical logs are restored. After a successful physical restore, a logical recovery is required: onbar -r -l The ixbar file only "knows" about logical logs backed up at the time the ixbar file was backed up. Its very likely that more logical logs (such as, salvaged logs) have been backed up since the full backup, but are not recorded in the ixbar file as this occurred after the ixbar file backup. OnBar understands this and after restoring all the logical logs recorded in the ixbar file, it then submits a query to the Storage Manager (SM) and queries for the next logical log in the sequence (it speculates there may be another log). If the SM has the log, OnBar will restore it then try again. In this way, OnBar will roll forward all the logical logs that have been backed up, even though it doesn't know from the ixbar file they were backed up. However, it seems if the time on the Informix client is ahead of the time of the master server, not all the backed up logical logs are restored when NetBackup is the SM. NetBackup presents the "image time" (the time the job ran on the master server) as the timestamp for the logical log. OnBar decides this is old, stops recovering logical logs, completes logical recovery and puts the server in Quiescent mode (wrongly as not all the logs that could be restored were restored). ------------------------------------------------------------- Description: When "onbar -v" is invoked, it starts the onbar_d process that runs as root. The NetBackup Informix Agent sets the user ID of this process to Informix. When the backup verification is done, onbar (Informix) tries to delete the shared memory but fails because the user ID of the process is now Informix and not root. As a result, the verification returns an error code of 131 and the bar_act.log contains the message, "Failed to delete the shared memory". Workaround: Set the parameter, BAR_RETRY, in the onconfig file to a value of 5. File name : $INFORMIXDIR/etc/onconfig Parameter : BAR_RETRY Value : 5 README -- Last modified date: Wednesday, October 8, 2003