Patch-ID# 112407-05 Keywords: netbackup 4.5 vrtsnb_45_5_m Synopsis: NetBackup 4.5 files fix Date: Aug/14/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.5 Xref: Topic: NetBackup 4.5 jumbo patch Relevant Architectures: sparc BugId's fixed with this patch: 4502555 4635705 4660793 4669203 4670934 4686309 4693371 4697369 4698033 4726930 4892600 Changes incorporated in this version: 4892600 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /openv/java/.nbjConf /openv/java/VxHelpViewer.jar /openv/java/allFSA.jar /openv/java/allJBP.jar /openv/java/allNB.jar /openv/java/dbext.jar /openv/java/nbCommon.jar /openv/netbackup/bin/add_slave /openv/netbackup/bin/add_slave_on_clients /openv/netbackup/bin/admincmd/bpauthorize /openv/netbackup/bin/admincmd/bpauthsync /openv/netbackup/bin/admincmd/bpbackupdb /openv/netbackup/bin/admincmd/bpccname /openv/netbackup/bin/admincmd/bpchangeprimary /openv/netbackup/bin/admincmd/bpclassnew /openv/netbackup/bin/admincmd/bpclclients /openv/netbackup/bin/admincmd/bpcldelete /openv/netbackup/bin/admincmd/bpclexclude /openv/netbackup/bin/admincmd/bpclient /openv/netbackup/bin/admincmd/bpclinclude /openv/netbackup/bin/admincmd/bpclinfo /openv/netbackup/bin/admincmd/bpcllist /openv/netbackup/bin/admincmd/bpclsched /openv/netbackup/bin/admincmd/bpclschedrep /openv/netbackup/bin/admincmd/bpclschedwin /openv/netbackup/bin/admincmd/bpclvalid /openv/netbackup/bin/admincmd/bpconfig /openv/netbackup/bin/admincmd/bpcounts /openv/netbackup/bin/admincmd/bpcoverage /openv/netbackup/bin/admincmd/bpdbjobs /openv/netbackup/bin/admincmd/bpdir /openv/netbackup/bin/admincmd/bpdrfiles /openv/netbackup/bin/admincmd/bpduplicate /openv/netbackup/bin/admincmd/bperror /openv/netbackup/bin/admincmd/bpexpdate /openv/netbackup/bin/admincmd/bpflist /openv/netbackup/bin/admincmd/bpfrag /openv/netbackup/bin/admincmd/bpgetconfig /openv/netbackup/bin/admincmd/bpgethost /openv/netbackup/bin/admincmd/bpgetmedia /openv/netbackup/bin/admincmd/bpimage /openv/netbackup/bin/admincmd/bpimagelist /openv/netbackup/bin/admincmd/bpimmedia /openv/netbackup/bin/admincmd/bpimport /openv/netbackup/bin/admincmd/bplabel /openv/netbackup/bin/admincmd/bplicense /openv/netbackup/bin/admincmd/bplocaladdrs /openv/netbackup/bin/admincmd/bpmedia /openv/netbackup/bin/admincmd/bpmedialist /openv/netbackup/bin/admincmd/bpminlicense /openv/netbackup/bin/admincmd/bpmoverinfo /openv/netbackup/bin/admincmd/bppficorr /openv/netbackup/bin/admincmd/bprdreq /openv/netbackup/bin/admincmd/bprecover /openv/netbackup/bin/admincmd/bpretlevel /openv/netbackup/bin/admincmd/bprsh /openv/netbackup/bin/admincmd/bpschedreq /openv/netbackup/bin/admincmd/bpsetconfig /openv/netbackup/bin/admincmd/bpstuadd /openv/netbackup/bin/admincmd/bpstudel /openv/netbackup/bin/admincmd/bpstulist /openv/netbackup/bin/admincmd/bpsturep /openv/netbackup/bin/admincmd/bpsyncinfo /openv/netbackup/bin/admincmd/bpuser /openv/netbackup/bin/admincmd/bpverify /openv/netbackup/bin/admincmd/bpversion /openv/netbackup/bin/admincmd/bpversion_update /openv/netbackup/bin/admincmd/nbdbsetport /openv/netbackup/bin/admincmd/nbdbsetpw /openv/netbackup/bin/admincmd/nbdbstop /openv/netbackup/bin/admincmd/nbdbupdatedb /openv/netbackup/bin/bpadm /openv/netbackup/bin/bpbrm /openv/netbackup/bin/bpdbm /openv/netbackup/bin/bpdm /openv/netbackup/bin/bpgp /openv/netbackup/bin/bpinst /openv/netbackup/bin/bpjava-susvc /openv/netbackup/bin/bpjobd /openv/netbackup/bin/bprd /openv/netbackup/bin/bpsched /openv/netbackup/bin/bptm /openv/netbackup/bin/cat_convert /openv/netbackup/bin/driver/snapctl9 /openv/netbackup/bin/driver/snapctl9_x /openv/netbackup/bin/goodies/backuptrace /openv/netbackup/bin/goodies/bpgetdebuglog /openv/netbackup/bin/goodies/check_dep /openv/netbackup/bin/goodies/netbackup /openv/netbackup/bin/goodies/restoretrace /openv/netbackup/bin/goodies/support/NCVU.README /openv/netbackup/bin/goodies/support/NCVU.tar /openv/netbackup/bin/goodies/support/support /openv/netbackup/bin/index_clients /openv/netbackup/bin/update_clients /openv/netbackup/bin/update_dbclients /openv/netbackup/client/Solaris/Solaris2.6/bpbackup /openv/netbackup/client/Solaris/Solaris2.6/bpbkar /openv/netbackup/client/Solaris/Solaris2.6/bpblr /openv/netbackup/client/Solaris/Solaris2.6/bpcd /openv/netbackup/client/Solaris/Solaris2.6/bpfastrax /openv/netbackup/client/Solaris/Solaris2.6/bphdb /openv/netbackup/client/Solaris/Solaris2.6/bpjava-msvc /openv/netbackup/client/Solaris/Solaris2.6/bpjava-usvc /openv/netbackup/client/Solaris/Solaris2.6/bplist /openv/netbackup/client/Solaris/Solaris2.6/bprestore /openv/netbackup/client/Solaris/Solaris2.6/bptpcinfo /openv/netbackup/client/Solaris/Solaris2.6/client_config /openv/netbackup/client/Solaris/Solaris2.6/cp_to_client /openv/netbackup/client/Solaris/Solaris2.6/driver/snapctl /openv/netbackup/client/Solaris/Solaris2.6/driver/snapctl9 /openv/netbackup/client/Solaris/Solaris2.6/driver/snapctl9_x /openv/netbackup/client/Solaris/Solaris2.6/driver/snapctl_x /openv/netbackup/client/Solaris/Solaris2.6/ftp_to_client /openv/netbackup/client/Solaris/Solaris2.6/install_client /openv/netbackup/client/Solaris/Solaris2.6/libxbsa.so /openv/netbackup/client/Solaris/Solaris2.6/libxbsa64.so /openv/netbackup/client/Solaris/Solaris2.6/tar /openv/netbackup/client/Solaris/Solaris2.6/version /openv/netbackup/client/Solaris/Solaris_x86_2.6/bpbackup /openv/netbackup/client/Solaris/Solaris_x86_2.6/bpbkar /openv/netbackup/client/Solaris/Solaris_x86_2.6/bpcd /openv/netbackup/client/Solaris/Solaris_x86_2.6/bphdb /openv/netbackup/client/Solaris/Solaris_x86_2.6/bpjava-msvc /openv/netbackup/client/Solaris/Solaris_x86_2.6/bpjava-usvc /openv/netbackup/client/Solaris/Solaris_x86_2.6/bplist /openv/netbackup/client/Solaris/Solaris_x86_2.6/bprestore /openv/netbackup/client/Solaris/Solaris_x86_2.6/client_config /openv/netbackup/client/Solaris/Solaris_x86_2.6/cp_to_client /openv/netbackup/client/Solaris/Solaris_x86_2.6/ftp_to_client /openv/netbackup/client/Solaris/Solaris_x86_2.6/install_client /openv/netbackup/client/Solaris/Solaris_x86_2.6/tar /openv/netbackup/client/Solaris/Solaris_x86_2.6/version /openv/volmgr/bin/acsd /openv/volmgr/bin/acstest /openv/volmgr/bin/avrd /openv/volmgr/bin/goodies/scan /openv/volmgr/bin/lmfcd /openv/volmgr/bin/lmfd /openv/volmgr/bin/ltid /openv/volmgr/bin/mmcrawl /openv/volmgr/bin/odld /openv/volmgr/bin/oprd /openv/volmgr/bin/robtest /openv/volmgr/bin/sg.build /openv/volmgr/bin/sgscan /openv/volmgr/bin/stopltid /openv/volmgr/bin/tl4d /openv/volmgr/bin/tl8cd /openv/volmgr/bin/tl8d /openv/volmgr/bin/tl8test /openv/volmgr/bin/tldcd /openv/volmgr/bin/tldd /openv/volmgr/bin/tldtest /openv/volmgr/bin/tlhcd /openv/volmgr/bin/tlhd /openv/volmgr/bin/tlhtest /openv/volmgr/bin/tlmd /openv/volmgr/bin/tlmtest /openv/volmgr/bin/tpautoconf /openv/volmgr/bin/tpclean /openv/volmgr/bin/tpconfig /openv/volmgr/bin/tpformat /openv/volmgr/bin/tpreq /openv/volmgr/bin/tpunmount /openv/volmgr/bin/ts8d /openv/volmgr/bin/tsdd /openv/volmgr/bin/tsdtest /openv/volmgr/bin/tshd /openv/volmgr/bin/tshtest /openv/volmgr/bin/vmadd /openv/volmgr/bin/vmadm /openv/volmgr/bin/vmchange /openv/volmgr/bin/vmcheckxxx /openv/volmgr/bin/vmctrldbm /openv/volmgr/bin/vmd /openv/volmgr/bin/vmdareq /openv/volmgr/bin/vmdb_cat /openv/volmgr/bin/vmdb_compact /openv/volmgr/bin/vmdb_dump /openv/volmgr/bin/vmdelete /openv/volmgr/bin/vmglob /openv/volmgr/bin/vminitlists /openv/volmgr/bin/vmoprcmd /openv/volmgr/bin/vmpool /openv/volmgr/bin/vmquery /openv/volmgr/bin/vmrule Problem Description: 4892600 need NB_45_5_M released as Sun patch (from 112407-04) 4670934 nbu restore date window 4660793 *** NBU 4.5 Beta *** No exit backdoor when cancel job with Details window (from 112407-03) 4502555 Netbackup 3.4 sg.install reports incorrectly on status of "add_drv sg" 4669203 tapealert handling 4726930 Syslog incorrectly logs NBU tape cleaning messages (from 112407-02) 4698033 calendrical scheduling kills backups and screws up jnbSA gui 4697369 bpclclients coredumps in GetBufferedPrivateProfileSection 4635705 *** NBU 4.5 Beta *** vmadm says incorrect numbers for input range. (from 112407-01) 4686309 nbdbd stop prevents power cycling on sol 9 4693371 NBU 4.5 install scripts do not configure or display Fabric attached devices Patch Installation Instructions: ------------------------------------------------------------------------- Refer to the Install.info file within the patch for instructions on using the generic 'installpatch' and 'backoutpatch' scripts provided with each patch. Any other special or non-generic installation instructions should be described below. ------------------------------------------------------------------------- Special Install Instructions: As root on your NetBackup Master Server: 1) Stop the NB daemons and all NB activity by running /usr/openv/netbackup/bin/goodies/bp.kill_all 2) Install patched binaries via patchadd/installpatch. 3) Restart daemons. /usr/openv/netbackup/bin/initbprd /usr/openv/volmgr/bin/ltid -v 4) Update the NetBackup clients, including the NetBackup master and media servers, with the update_clients script. /usr/openv/netbackup/bin/update_clients where is one of the following: Solaris Solaris2.6 Solaris Solaris7 Solaris Solaris8 Solaris Solaris9 Solaris Solaris_x86_2.6 Solaris Solaris_x86_7 Solaris Solaris_x86_8 Remember to include the master server's type. Note: This patch contains Solaris client binaries only. If there are other platforms, it is important to patch those clients as well. For the binaries of other clients, download the latest patches from the VERITAS website, http://support.veritas.com. Note: The /usr/openv/netbackup/bin/update_clients command without any parameters will update all the Unix clients. ------------------------ Working with Leadville ------------------------ Configure/Unconfigure/Verify tape devices with VERITAS NetBackup in SAN 4.x/Leadville 6.x.x: The following procedures should be followed when configuring VERITAS NetBackup in SAN 4.x/Leadville 6.x.x. 1. The tape and robotic devices must be configured before configuring VERITAS NetBackup in SAN 4.x/Leadville 6.x.x. The following procedures should be followed: a. Verify that the device nodes are listed by executing the command: cfgadm -al b. Execute the command below to configure the controller(s) for the devices: cfgadm -c configure e.g. cfgadm -c configure c7 NOTE: I/O error will be received at this point when running with SAN 4.1/Leadville 6.1.x. Refer to Sun bug ID 4752477 for the details. Please ignore this error and continue with the rest of the steps. c. Verify that the native driver nodes are created by cfgadm: cfgadm -al e.g. cfgadm -al c7 d. Proceed with configuring VERITAS NetBackup software following the documented procedure. 2. VERITAS NetBackup sg driver must be unloaded, before unconfiguring tape and/or robotic device nodes in SAN 4.x/Leadville 6.x.x. The following procedures must be followed: a. Shutdown VERITAS NetBackup daemons to avoid NBU loading the sg driver while working with the devices. b. Execute the command below to locate the loaded sg driver: modinfo | grep sg c. Unload the sg driver by: modunload -i d. Execute the command below to unconfigure the devices: cfgadm -c unconfigure Note that after a tape device is unconfigured following the above procedure, if the sg driver is loaded and then "cfgadm -al" is executed, the output will show the unconfigured tape device as being configured. This is resulted from the inconsistency between the state of the sg driver and the Solaris native driver (i.e. st driver). Therefore, the sg driver must stay unloaded when verifying devices with "cfgadm -al" at this stage. To make sg driver recognize the device as unconfigured, reconfigure the devices within VERITAS NetBackup following documented procedures. 3. If the system is rebooted after devices are configured with SAN 4.1/Leadville 6.1.x and VERITAS NetBackup, it is required to configure the robotic/media changer devices again for them to work properly. Refer to Sun bug ID 4752477 for the details. The procedure below should be followed to configure the robotic/media changer device again: a. Execute the command below to configure the robotic device: cfgadm -c configure e.g. cfgadm -c configure c3::500104f00045df22 b. Execute the command below to locate the loaded sg driver: modinfo | grep sg c. Unload the sg driver by: modunload -i d. Execute the command below to reload the sg driver: /usr/openv/volmgr/bin/sgscan NOTE: This issue is resolved in SAN 4.2/Leadville 6.2.x. 4. When VERITAS NetBackup is configured with SAN 4.1/Leadville 6.1.x, running "cfgadm -al" command while sg driver is loaded, the output shows the Type of the tape devices as "unknown". Refer to Sun bug ID 4756032 for the details. To avoid this problem, the sg driver must be unloaded before running the "cfgadm -al" command to verify the devices. To unload the sg driver, refer to the steps a to c in bullet 2 above. NOTE: This issue is resolved in SAN 4.2/Leadville 6.2.x. ============================================ DESCRIPTION OF PROBLEMS FIXED ================================== The following are descriptions of the problems fixed. Please read the entire document before installing. README Conventions : Description Describes particular problem or feature contained in this Maintenance Pack. ** Description ** Describes a problem that can lead to potential data loss. Please read these problem descriptions carefully. Workaround Any available workarounds to a problem are also listed. Workarounds can be used INSTEAD of applying the Maintenance Pack. Additional Notes Any additional information regarding this problem or feature. ============= 112407-05 ============= KNOWN ISSUES ============= The following are known issues. Please note that these known issues will NOT be resolved after installing this pack. Description: The vxlicense utility and elm licenses that are used for VxFS 3.3 and VxFS 3.4 are no longer used with VxFS 3.5. VxFS 3.5 uses a new license utility and new licenses. Customers using NBU BLIB on Solaris or HP-UX systems will experience a problem causing BLIB to fail if the system is a clean install of VxFS 3.5. There is no problem if this was an upgrade from VxFS 3.3 or 3.4 up to VxFS 3.5. Workaround: Install the old vxlicense utility on the system and install the old elm licenses using that utility. Description: The "backuptrace" command of the log analysis utility, introduced in this maintenance pack, will hang on Tru64 systems. Avoid using this command on Tru64 systems. Description: If NetBackup is installed on a VxFS file system (VxFS 3.4) on AIX 5.1, the system may stop responding when the NetBackup daemons are started. This problem is isolated to AIX 5.1 and VxFS 3.4 with NetBackup installed on a VxFS file system. Workaround: The minimum AIX kernel patch level for supporting VxFS on AIX 5.1 is: 1. AIX 5.1 at ML02 with APAR IY32907, or 2. AIX 5.2 at ML03 The APAR IY32907 is required at ML02 level to prevent AIX kernel from crashing while loading/executing certain NBU daemons that reside in vxfs file systems. This crash only occurs when the target file system(s) for installing NBU binaries was vxfs. If target file system for NBU was not vxfs, the crash does not occur. Regardless of the type of file system used for installing NBU, this APAR is required for correct operation of VxFS on AIX 5.1 at ML02. Description: After upgrading to NetBackup 4.5 Maintenance Pack 2, AIX client restores are now getting exit status 5. If AIX is using VxFS, the Master Servers, Media Servers and Client Backups/Archives/Restores will work fine if all platforms are at the Maintenance Pack 2 level. If the Client is at Maintenance Pack 2, but the Master and/or Media Servers are still at GA level, backups will work fine, but restores will fail with an error code 5. Workaround: Upgrade the Media and Master Servers to Maintenance Pack 2 and retry the restore. Description: The installation of the NetBackup client Maintenance Pack, NB_CLT_45_2, may fail on HP-UX machines under the following circumstances: Sybase IQ 12.4.3 (32 bit) is running, and a backup using the NetBackup for Sybase agent has been previously done. When doing a local installation of the NetBackup client Maintenance Pack, the installation may fail with the following error: mv: /usr/openv/lib//libVcvcomb.sl: cannot write: Text file busy mv: /usr/openv/lib//libxbsa.sl: cannot write: Text file busy When doing a remote installation of the NetBackup client Maintenance Pack, the installation may fail with the following error: Couldn't open /usr/openv/lib/libVcvcomb.sl on client Client open errno = 26 Workaround: The workaround for this problem is to stop Sybase IQ, and then to do the installation of the NetBackup client Maintenance Pack again. Description: NetBackup for Lotus Notes does not support the file list directive, ALL_LOTUS_DATABASES. Workaround: Add the Domino data directory, containing the database files with extensions .nsf, .ntf or .box, in the file list instead of using the ALL_LOTUS_DATABASES file list directive. There will be an increase in performance since the NetBackup for Lotus Notes extension does not have to parse the file system for .nsf, .ntf or .box extensions. Description: NetBackup extension for Lotus Notes is not supported in the Microsoft Cluster environment (MSCS). NetBackup does support Lotus Notes in a non-clustered configuration. ================================================================================ Description: When trying a restore operation using RMAN, the files are retrieved and written to disk, however and failure may occur and result in an error 5 code. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The bplist command fails after running "bpimage -create_image_list" on binary catalogs. Workaround: To avoid this issue, do not use "bpimage -create_image_list" to create IMAGE_LIST files. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: AIX systems may fail to unload tapes from robotic daemons. Windows systems may down drives or fail to unload tapes when certain error conditions are reported. (All NetBackup Servers: Intel-NT RS6000) -------------------------------------------------------------------------------- Description: The following eject error message is consistently written to the debug log, even in a successful transaction. "08:13:07.468 [9657] <16> WaitForEjectStatus: robot information failed, Control daemon connect or protocol error" (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When the tpcommand debug directory exists, calls to tpconfig -robdrtype and others may cause a core dump. This includes hidden calls to said commands such as vmupdate uses. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When running media manager VERBOSE, the following syslog message is always logged, even in the event that the CONTINUE is successfully received. "Dec 16 08:15:43 tldcd[9651]: media access port operation timed out waiting for user to "CONTINUE"" (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Authentication commands such as bpauthsync were reporting unresolved symbols at execution time on DGUX and NCR clients. Changes were made in how the libvopie.so library is created so that this problem no longer occurs. (NetBackup Clients: Dgux NCR ) -------------------------------------------------------------------------------- Description: You may receive an exit status 51 (timed out waiting for database information) when monitor information is not processed fast enough or when only a partial write of the database information occurs. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Portions of bpgetmedia output format are hard coded. When these portions the output are displayed in the Japanese locale, the fields do not line up. Added message: SmeGme0170N SmeGme0180N (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When performing updates, there are instances where the admincmd and bpclient would lose some information. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Increased the size of the buffer that holds the Read Element Status Data Transfer Descriptor during device discovery and tld* operations. Certain new HPQ robots have exceeded the previous threshold of this buffer. Failed device discovery for these devices is a primary symptom of this problem. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If an Oracle backup is started from a policy, it fails with a status code of 6. (All NetBackup Windows Clients All NetBackup Unix Clients) -------------------------------------------------------------------------------- Description: A problem has been fixed in tldtest in which barcodes were not being returned for the IBM 3607 robotic tape library. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The install of a new client can cause a kill -HUP to be sent to inetd. If osinetd is running it may mistakenly send the -HUP and be killed. (All NetBackup Unix Clients ) -------------------------------------------------------------------------------- Description: The snap driver is now compiled separately for Solaris 9. The ftp_to_client, client_config, install_client, and bpinst all push the new binaries to a Solaris client. The fb.snap_install and install_vfms copy the correct version to the kernel. (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: The bpdbm -consistency [1 | 2] command may incorrectly report errors for database extension backups or scheduled Vault sessions. The errors will be reported as follows: checking image file < db_oracle_rev2_1038284396_FULL> >> PRIMARY_COPY is set to an invalid copy >> EXPIRATION is not set to the next valid copy to expire Workaround: Ignore these errors for database extension backups or scheduled Vault sessions. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Searching for backup images to duplicate (for example, bpduplicate -PM) may periodically fail with an error status 43 (unexpected message received) or error status 144 (invalid command usage). (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When specifying a preprocess interval using bpadm, there is no way to set the default value. Bpadm is changed to enable these options to be set. In addition, bpadm clearly reports the settings. Workaround: Use bpconfig to set the preprocess interval. Use the following command to set the default preprocess interval (every four hours): bpconfig -prep -1 Use the following command to set the preprocess interval to occur prior to every backup: bpconfig -prep 0 (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: A tape-unload problem has been fixed on SGI media servers when running TLH robotics. (All NetBackup Servers: Sgi) -------------------------------------------------------------------------------- Description: The SCSI Reservation could be lost when selecting a second piece of media during one backup or restore session. The new media must be mounted on a different tape drive than the original media for this problem to occur. (All NetBackup Servers: HP) -------------------------------------------------------------------------------- Description: If the size of a backup fills one tape and spans to another tape, a new tape is used. However, the scheduler no longer recognizes that the original drive is now available for reuse. This error causes the scheduler to not use all the available drives. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The bpdbm child process may hang during the TIR pruning process. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The bpplsched and bpplschedrep commands were limiting the input of calendar dates to 50, which also imposed a limit on the NetBackup-Java Administration Console. The limits have been increased. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Added support for Windows access-control lists (ACLs) and Attributes for the ServPoint NAS on Linux systems. (All NetBackup Unix Clients ) -------------------------------------------------------------------------------- Description: The first Lotus transaction log extent in a backup image has incorrect owner and group permissions. Rather than have the owner and group permissions for the Lotus Domino server as administrator, the owner and group permissions are set to root. (All NetBackup Unix Clients ) -------------------------------------------------------------------------------- Description: A new Linux client was added (Linux 2.4) and the code modified to support files that are larger than 2GB. (NetBackup Clients: Linux2.2 ) -------------------------------------------------------------------------------- Description: The bpadm utility will not prompt the user for the policy volume pool if the storage unit name (stunit) is any_available. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: In the NetBackup 4.5 Japanese release the Shift-JIS multi-byte character set treats the 0x5B and 0x7B characters in second byte of a multi-byte as a '[' and '{' wildcards, respectively. Additional Notes: Use of wildcards in the backup policy file list is not currently supported for languages that use multi-byte character set mapping. (All NetBackup Servers and All NetBackup Unix Clients) -------------------------------------------------------------------------------- Description: Fix for security vulnerabilities that have been reported in versions of MySQL prior to 3.23.54. The version of MySQL used by NetBackup can allow unauthorized access to the system. MySQL runs as nbdbd process on UNIX and NetBackup Persistent Storage Manager service on Windows 2000/NT systems only when Global Data Manager is used. VERITAS strongly suggests you do not allow unauthorized access to the database port on any NetBackup Master server. For more information, contact VERITAS Support. (http://www.support.veritas.com) (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If an SSO Drive Release message fails, the server can continue to scan the drive as it is used by other systems. This can cause the media to be rewound during a backup or restore operation. The scanning stops as soon as the SSO drive Release message is retried and works. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The NetBackup tape manager (bptm) uses information from 3pc.conf if the /dev/rmt path matches the tape in use. The bptm uses this information without validating that it is still pointed at the same tape. If a user were to reconfigure, this information may be wrong, resulting in accessing the wrong tape from an extended copy engine. (All NetBackup Servers: HP RS6000 Solaris) -------------------------------------------------------------------------------- Description: Add support in the Tape Stacker Half-inch (TSH) robot for the IBM 3590H11 stacker. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Non-multiplexed duplication on a UNIX media server of a multiplexed backup that was originally created on a Windows media server fails if the backup spans media. This occurs when duplicating an imported backup originally created on Windows to a UNIX server, or by using the -altreadhost bpduplicate option. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Import of compressed files of size (2GB - 1MB) through 2GB won't restore. Workaround: Manually change the size of the file in the image database to the correct value (reduce size by 1GB). (All NetBackup Unix Clients ) -------------------------------------------------------------------------------- Description: When an NDMP backup or restore job is aborted, NetBackup does not consistently send the appropriate abort or stop messages to the NDMP server. Because the NDMP server still "owns" the tape device, subsequent tape positioning and/or tape writes by NetBackup would fail causing the tape to be frozen or suspended. This could also happen if the NDMP backup/restore job fails to complete successfully. Additional Notes: There are still cases where NetBackup cannot send the NDMP abort/stop messages, such as when the connection is hung or when interrupted in the midst of receiving or sending a message. However, in these cases NetBackup also fails when it attempts to send tape-positioning messages and will not attempt to write the empty header. These tape-positioning failures are logged, but the tape is not frozen or suspended for these failures. (All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris) -------------------------------------------------------------------------------- Description: The Sun Leadville HBA driver truncates autosense data to 20 bytes, and the full sense data from an extended copy command must be obtained using a Receive Copy Results command. (All NetBackup Servers: HP Solaris) -------------------------------------------------------------------------------- Description: Too many "cancel job" requests would deadlock NetBackup. The nightly clean process does not update the attached monitors with information about deleted jobs. The queued vault job receives a status 50 after 20 minutes. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When frozen image is used and there are multiple file systems in the backup file list, and one file system is inside of another (for example, / /usr/usr/a/fs2), then the device number that is used to identify the file system in the database may not be correct. This will be a problem if you use the 'don't cross mount point' option during a restore. (NetBackup Clients: HP Solaris ) -------------------------------------------------------------------------------- Description: If a schedule in a policy was defined to use calendar-based scheduling, bpsched used the "frequency" from the schedule when searching for older images written under the same policy. This has been changes so the frequency is ignored for calendar-based schedules. Workaround: To avoid this problem, temporarily switch FULL schedule to frequency-based, and modify the frequency to a longer value than that of the CINC schedule and save this schedule. Then switch the schedule back to calendar-based, and re-define the calendar dates for the schedule (because they were lost when they were switched to frequency-based). (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The IBM ATL library (TLH) would mount tapes on the wrong drives. This situation would happen when the TLH takes a drive out of its internal drive list and changes the drive name for all of the rest of the drives in the library by shifting all of the names down by one. This causes NetBackup to mount tapes to the incorrect drive because NetBackup mounts the tape by the configured drive name. To use this fix, the user must create a frozen drive map in the tlhtest utility by using the drmapfreeze command. All drives need to be up and available when this command is issued. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When searching a backup that is indexed and the search path is at a lower level than what was actually backed up, the search can go into an infinite loop. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The word "interrupted" was not spelled correctly in the text of the error and log messages. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Add support for HP ESL9000 Series and HP MSL5000 Series robots. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: ACSD robotic mounts may fail if many tape drives are loaded at the same time by a single server. Additional Notes: The syslog will contain the message, "waited 60 times for ready", twice for a drive, and then the mount will fail. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: TIR backups with move detection cause a segmentation fault on Linux clients. (NetBackup Clients: Linux2.2 ) -------------------------------------------------------------------------------- Description: Tapes might not be unmounted on a media server until all jobs on that media server completed if a user backup was initiated while a non-user backup was active. (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: AIX and NETLINK ACL information was not restored correctly for directories. (All NetBackup Unix Clients ) ============= Java List ============= KNOWN ISSUES Description: On Linux platforms, the Java client gui will not display files greater than 2GB when browsing for backup. Restore browsing works fine. ============= Description: A problem can occur when updates for 'Active' jobs are sent to the Activity Monitor by bpjobd during an initial job loading. This problem is likely to occur if: a) There are a large number of 'Active' jobs. b) The total number of jobs being loaded is large. c) A high frequency of updates are received for 'Active' jobs. Two copies of a job were put into the jobs table because the highest job ID was not being set during the initial pull of 200 jobs (which includes all 'Active' jobs because bpjobd sends them first). Also the 'Active' jobs usually have the highest job ID's. When updates for 'Active' jobs (which are queued by bpjobd during initial loading) are received, a new entry is created in the jobs table because their Job ID is higher than the highest Job ID (which was not set correctly). This problem was fixed in FP3 when multiple jobs table data models were consolidated into a single data model (JobDataModel class). (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: The Cancel and Delete buttons on the Activity Monitor job details dialog are risky because a user may accidentally cancel or delete a job by clicking on the wrong button. Because of this risk, the Cancel and Delete buttons have been removed. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: Browsing the Windows system state node in the Java Backup Archive and Restore application may cause the interface to hang. This was due to a program exception caused by an unexpected data type received from the server's bplist command call. (All NetBackup Java GUI capable NetBackup servers and clients) ================================================================================ ============= 112407-04 ============= Description: When trying a restore operation using RMAN, the files are retrieved and written to disk, however and failure may occur and result in an error 5 code. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The bplist command fails after running "bpimage -create_image_list" on binary catalogs. Workaround: To avoid this issue, do not use "bpimage -create_image_list" to create IMAGE_LIST files. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The following eject error message is consistently written to the debug log, even in a successful transaction. "08:13:07.468 [9657] <16> WaitForEjectStatus: robot information failed, Control daemon connect or protocol error" (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When the tpcommand debug directory exists, calls to tpconfig -robdrtype and others may cause a core dump. This includes hidden calls to said commands such as vmupdate uses. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When running media manager VERBOSE, the following syslog message is always logged, even in the event that the CONTINUE is successfully received. "Dec 16 08:15:43 tldcd[9651]: media access port operation timed out waiting for user to "CONTINUE"" (All NetBackup Servers) -------------------------------------------------------------------------------- Description: You may receive an exit status 51 (timed out waiting for database information) when monitor information is not processed fast enough or when only a partial write of the database information occurs. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Portions of bpgetmedia output format are hard coded. When these portions the output are displayed in the Japanese locale, the fields do not line up. Added message: SmeGme0170N SmeGme0180N (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When performing updates, there are instances where the admincmd and bpclient would lose some information. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Increased the size of the buffer that holds the Read Element Status Data Transfer Descriptor during device discovery and tld* operations. Certain new HPQ robots have exceeded the previous threshold of this buffer. Failed device discovery for these devices is a primary symptom of this problem. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If an Oracle backup is started from a policy, it fails with a status code of 6. (All NetBackup Windows Clients All NetBackup Unix Clients) -------------------------------------------------------------------------------- Description: A problem has been fixed in tldtest in which barcodes were not being returned for the IBM 3607 robotic tape library. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The install of a new client can cause a kill -HUP to be sent to inetd. If osinetd is running it may mistakenly send the -HUP and be killed. (All NetBackup Unix Clients ) -------------------------------------------------------------------------------- Description: The snap driver is now compiled separately for Solaris 9. The ftp_to_client, client_config, install_client, and bpinst all push the new binaries to a Solaris client. The fb.snap_install and install_vfms copy the correct version to the kernel. (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: The bpdbm -consistency [1 | 2] command may incorrectly report errors for database extension backups or scheduled Vault sessions. The errors will be reported as follows: checking image file < db_oracle_rev2_1038284396_FULL> >> PRIMARY_COPY is set to an invalid copy >> EXPIRATION is not set to the next valid copy to expire Workaround: Ignore these errors for database extension backups or scheduled Vault sessions. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Searching for backup images to duplicate (for example, bpduplicate -PM) may periodically fail with an error status 43 (unexpected message received) or error status 144 (invalid command usage). (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When specifying a preprocess interval using bpadm, there is no way to set the default value. Bpadm is changed to enable these options to be set. In addition, bpadm clearly reports the settings. Workaround: Use bpconfig to set the preprocess interval. Use the following command to set the default preprocess interval (every four hours): bpconfig -prep -1 Use the following command to set the preprocess interval to occur prior to every backup: bpconfig -prep 0 (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: If the size of a backup fills one tape and spans to another tape, a new tape is used. However, the scheduler no longer recognizes that the original drive is now available for reuse. This error causes the scheduler to not use all the available drives. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The bpdbm child process may hang during the TIR pruning process. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The bpplsched and bpplschedrep commands were limiting the input of calendar dates to 50, which also imposed a limit on the NetBackup-Java Administration Console. The limits have been increased. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Added support for Windows access-control lists (ACLs) and Attributes for the ServPoint NAS on Linux systems. (All NetBackup Unix Clients) -------------------------------------------------------------------------------- Description: The first Lotus transaction log extent in a backup image has incorrect owner and group permissions. Rather than have the owner and group permissions for the Lotus Domino server as administrator, the owner and group permissions are set to root. (All NetBackup Unix Clients) -------------------------------------------------------------------------------- Description: The bpadm utility will not prompt the user for the policy volume pool if the storage unit name (stunit) is any_available. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: In the NetBackup 4.5 Japanese release the Shift-JIS multi-byte character set treats the 0x5B and 0x7B characters in second byte of a multi-byte as a '[' and '{' wildcards, respectively. Additional Notes: Use of wildcards in the backup policy file list is not currently supported for languages that use multi-byte character set mapping. (All NetBackup Servers and All NetBackup Unix Clients) -------------------------------------------------------------------------------- Description: Fix for security vulnerabilities that have been reported in versions of MySQL prior to 3.23.54. The version of MySQL used by NetBackup can allow unauthorized access to the system. MySQL runs as nbdbd process on UNIX and NetBackup Persistent Storage Manager service on Windows 2000/NT systems only when Global Data Manager is used. VERITAS strongly suggests you do not allow unauthorized access to the database port on any NetBackup Master server. For more information, contact VERITAS Support. (http://www.support.veritas.com) (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If an SSO Drive Release message fails, the server can continue to scan the drive as it is used by other systems. This can cause the media to be rewound during a backup or restore operation. The scanning stops as soon as the SSO drive Release message is retried and works. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The NetBackup tape manager (bptm) uses information from 3pc.conf if the /dev/rmt path matches the tape in use. The bptm uses this information without validating that it is still pointed at the same tape. If a user were to reconfigure, this information may be wrong, resulting in accessing the wrong tape from an extended copy engine. (All NetBackup Servers: Solaris) -------------------------------------------------------------------------------- Description: Add support in the Tape Stacker Half-inch (TSH) robot for the IBM 3590H11 stacker. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Non-multiplexed duplication on a UNIX media server of a multiplexed backup that was originally created on a Windows media server fails if the backup spans media. This occurs when duplicating an imported backup originally created on Windows to a UNIX server, or by using the -altreadhost bpduplicate option. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Import of compressed files of size (2GB - 1MB) through 2GB won't restore. Workaround: Manually change the size of the file in the image database to the correct value (reduce size by 1GB). (All NetBackup Unix Clients ) -------------------------------------------------------------------------------- Description: When an NDMP backup or restore job is aborted, NetBackup does not consistently send the appropriate abort or stop messages to the NDMP server. Because the NDMP server still "owns" the tape device, subsequent tape positioning and/or tape writes by NetBackup would fail causing the tape to be frozen or suspended. This could also happen if the NDMP backup/restore job fails to complete successfully. Additional Notes: There are still cases where NetBackup cannot send the NDMP abort/stop messages, such as when the connection is hung or when interrupted in the midst of receiving or sending a message. However, in these cases NetBackup also fails when it attempts to send tape-positioning messages and will not attempt to write the empty header. These tape-positioning failures are logged, but the tape is not frozen or suspended for these failures. (All NetBackup Servers: Solaris) -------------------------------------------------------------------------------- Description: The Sun Leadville HBA driver truncates autosense data to 20 bytes, and the full sense data from an extended copy command must be obtained using a Receive Copy Results command. (All NetBackup Servers: Solaris) -------------------------------------------------------------------------------- Description: Too many "cancel job" requests would deadlock NetBackup. The nightly clean process does not update the attached monitors with information about deleted jobs. The queued vault job receives a status 50 after 20 minutes. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When frozen image is used and there are multiple file systems in the backup file list, and one file system is inside of another (for example, / /usr/usr/a/fs2), then the device number that is used to identify the file system in the database may not be correct. This will be a problem if you use the 'don't cross mount point' option during a restore. (NetBackup Clients: Solaris ) -------------------------------------------------------------------------------- Description: If a schedule in a policy was defined to use calendar-based scheduling, bpsched used the "frequency" from the schedule when searching for older images written under the same policy. This has been changes so the frequency is ignored for calendar-based schedules. Workaround: To avoid this problem, temporarily switch FULL schedule to frequency-based, and modify the frequency to a longer value than that of the CINC schedule and save this schedule. Then switch the schedule back to calendar-based, and re-define the calendar dates for the schedule (because they were lost when they were switched to frequency-based). (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The IBM ATL library (TLH) would mount tapes on the wrong drives. This situation would happen when the TLH takes a drive out of its internal drive list and changes the drive name for all of the rest of the drives in the library by shifting all of the names down by one. This causes NetBackup to mount tapes to the incorrect drive because NetBackup mounts the tape by the configured drive name. To use this fix, the user must create a frozen drive map in the tlhtest utility by using the drmapfreeze command. All drives need to be up and available when this command is issued. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When searching a backup that is indexed and the search path is at a lower level than what was actually backed up, the search can go into an infinite loop. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The word "interrupted" was not spelled correctly in the text of the error and log messages. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Add support for HP ESL9000 Series and HP MSL5000 Series robots. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: ACSD robotic mounts may fail if many tape drives are loaded at the same time by a single server. Additional Notes: The syslog will contain the message, "waited 60 times for ready", twice for a drive, and then the mount will fail. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Tapes might not be unmounted on a media server until all jobs on that media server completed if a user backup was initiated while a non-user backup was active. (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: AIX and NETLINK ACL information was not restored correctly for directories. (All NetBackup Unix Clients) ============= Java List ================================================================================ Description: A problem can occur when updates for 'Active' jobs are sent to the Activity Monitor by bpjobd during an initial job loading. This problem is likely to occur if: a) There are a large number of 'Active' jobs. b) The total number of jobs being loaded is large. c) A high frequency of updates are received for 'Active' jobs. Two copies of a job were put into the jobs table because the highest job ID was not being set during the initial pull of 200 jobs (which includes all 'Active' jobs because bpjobd sends them first). Also the 'Active' jobs usually have the highest job ID's. When updates for 'Active' jobs (which are queued by bpjobd during initial loading) are received, a new entry is created in the jobs table because their Job ID is higher than the highest Job ID (which was not set correctly). This problem was fixed in FP3 when multiple jobs table data models were consolidated into a single data model (JobDataModel class). (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: The Cancel and Delete buttons on the Activity Monitor job details dialog are risky because a user may accidentally cancel or delete a job by clicking on the wrong button. Because of this risk, the Cancel and Delete buttons have been removed. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: Browsing the Windows system state node in the Java Backup Archive and Restore application may cause the interface to hang. This was due to a program exception caused by an unexpected data type received from the server's bplist command call. (All NetBackup Java GUI capable NetBackup servers and clients) ================================================================================ ============= 112407-03 ============= Description: The NO_TAPEALERT touch file that is used to disable TapeAlert-based drive cleaning was not being used properly in avrd. Partially configured drives (only visible through tpconfig -tables) are no longer scanned by avrd. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: An erroneous backup failure and frozen tape could occur if a backup hits the end of the media (EOM), and selects a previously mounted tape to continue the backup. This will only happen if no scratch tapes are available. The error log will contain the following message: "FREEZING media id xxxxxx, too many data blocks written, check tape/driver block size configuration" The bptm log will show that a previously mounted tape was selected after EOM processing. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When NetBackup DB indexing is turned on, some searches will return the following status message when the same path exists sequentually in the index file with the .i1 suffix. "EXIT STATUS 227: no entity was found" Workaround: Rename the /usr/openv/netbackup/db/images//INDEX directory so that the index files cannot be used. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: FlashBackup restores can log an excessive amount of information if sfr has to wait for bpbrm to end. In addition, it will not sleep, causing a load on the system during this time. (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: If an error occured on a backup that caused a job to requeue, and the backup window to close, the status would be 196 (window closed) instead of the error that caused the job to requeue. Under some circumstances, a tape would be unmounted before the media unmount dalay time had expired. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: A duplication from a disk storage unit image to tape results in the media retention level being incorrect if using the option to use the original expiration for the copy. However, the expiration of the tape and the duplicated copy is correct. In addition, if duplicating to a disk storage unit, the retention level setting is ignored. In this case, the expiration of the duplicate copy is the same as the original copy. Workaround: For the tape retention level issue, use the option to explicitly set the retention level. For the retention level issue with a destination disk storage unit, use the bpexpdate command to reset the expiration of the copy. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Changes have been made to bpminlicense to correct logging problems. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The backup may run more times than it should on Windows NT and Windows 2000 systems if the following conditions apply: - Muliple data streams are enabled - No wild cards are entered in the filelist - The filelist contains a directory without a backslash '\' as the final character Workaround: Make sure all directory names in the file lists of policies end with a back slash '\'. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Under some circumstances, usually relating to a disk hang condition, two backups using the NBU_SNAP driver could both start at exactly the same time and both select the same unused location in the cache table. This results in a kernel panic with an assertion failure in the snap driver. (NetBackup Clients) -------------------------------------------------------------------------------- Description: A FlashBackup caused a kernel panic with an assertion in the snap driver resulting in the following message. Sep 24 09:08:58 turnip savecore: reboot after panic: assertion failed: sbp->sb_b count > 0, file: x_snap.c, line: 403 (NetBackup Clients) -------------------------------------------------------------------------------- Description: When searching an image that is indexed, the search can fail to return the contents of a directory if that directory is a file system mountpoint and the mountpoint is part of another file system that was backed up right before this file system and the last entry for the prior file system was the directory mountpoint that is being searched for. Workaround: Turn off indexing or add "/*" to the end of the search directory. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When using a Crossroads router as the mover to a tape that is SCSI attached to the Crossroads, the retry count may not be high enough to get past the initial tape settling time because the retry count is based on the number of targets. FlashBackup initially has only the tape target while it is writing the file system map. Workaround: To avoid this problem, try duplicating each entry in mover.conf. The selection process will then try the same device again with the original retry count. Additional Notes: This can also be reduced by turning off tape queueing in the router. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The bpgetdebuglog command may hang under certain conditions when trying to read a debug log on the local host. The command will copy most of the debug log to standard output, but then it will hang indefinitely. The bpgetdebuglog command is a helper command for the backuptrace and restoretrace commands in the /usr/openv/netbackup/bin/goodies directory. You are most likely to see this problem while running backuptrace or restoretrace. Workaround: Issue the backuptrace or restoretrace command from a host that is not the master server, media server, or client of the job that is being traced. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Cleaning media can be overused when cleaning does not complete within 30 minutes after a cleaning request is initiated. After 30 minutes, the cleaning request is removed from internal tables, so that when the cleaning actually does complete, the cleaning statistics (for example, last clean time, total mount time, number of cleanings remaining for the cleaning tape, etc.) are not updated. In addition, when the cleaning request is removed, system log messages such as "Removed cleaning queue entry for drive index 1 (drive 2), it has not completed in 30 minutes" show up, giving a false impression that the drive was not cleaned, when in fact the cleaning request may have been still active. The following vm.conf entry is available to make the cleaning request timeout configurable: CLEAN_REQUEST_TIMEOUT = minutes The variable "minutes" specifies how long Media Manager should wait for a drive to be cleaned before removing the request from the cleaning queue if the request has not been processed. The minimum for "minutes" is 1. The maximum is 144000 (100 days). The default is 30. A value of 0 is converted to the default value of 30. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When more than one copy of a backup expire at the same time and a copy of the backup remains, the primary copy for the backup may be incorrectly set to a copy number that does not exist. This causes restores to fail with a 147 error (required or specified copy was not found). Workaround: To prevent the problem, set different expiration dates for each copy. If the problem has occurred, change the primary copy on the affected images so that it is correct. This is done using the bpduplicate -npc -backupid command. This is not needed once the patch is applied as the primary copy on the affected images will be corrected. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: A Customer can successfully install BLI and run an Oracle script-based BLI policy without creating the BLI scripts. The activity monitor will report a status 0 for the backup. As noted in the bpbkar log below, the process encountered a warning "WRN"; however, it continued on with the backup and completed with a status 0. Since the block incremental notify script was not found, this backup image would not be a valid image. Without the notify script the database was not placed into backup mode to obtain a quiesant backup image of the database. bpbkar log 02:00:25 [19616] < 2> logparams: bpbkar -r 604800 -ru root -dt 93610 - to 0 -clnt as370 -class as370_BLI -sched incrementals -st INCR - bpstart_to 300 -bpend_to 300 -read_to 300 -block_incr -keyword spps -streams 1 -bt 990511247 - prev_bli_incr 990417647 -last_bli_full 990331247 -use_otm -fso -b as370_0990511247 -kl 14 -shm 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (ufs) /dev/vx/dsk/rootvol on / 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (ufs) /dev/vx/dsk/usr on /usr 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (proc) /proc on /proc 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (fd) fd on /dev/fd 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (ufs) /dev/vx/dsk/var on /var 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/appdg/app_01 on /app1 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/appdg/app_02 on /opt/openv 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (autofs) - hosts on /net 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (autofs) auto_home on /home 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (autofs) - xfn on /xfn 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (NFS) as370:vold(pid620) on /vol 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/appdg/app_03 on /app1/inktomi 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/Foracle_dg1/spps1_vol on /oracle_spps1 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/Foracle_dg2/arch_vol on /oracle_spps/arch 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/Foracle_dg1/spps3_vol on /oracle_spps3 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/Foracle_dg1/spps2_vol on /oracle_spps2 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/Foracle_dg1/oracle_vol on /opt/oracle 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/Foracle_dg1/data_vol on /oracle_spps/data 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/Foracle_dg3/dbf_vol on /opt/oracle/admin/spps/dbf 02:00:25 [19616] < 2> bpbkar initialize: INF - Selecting files modified or changed after Mon May 21 00:00:15 2001 02:00:25 [19616] < 4> bpbkar main: INF - setenv KEYWORD=spps 02:00:25 [19616] < 4> bpbkar main: INF - setenv STREAM_PID=19616 02:00:25 [19616] < 4> bpbkar main: INF - setenv STREAM_NUMBER=0 02:00:25 [19616] < 4> bpbkar main: INF - setenv STREAM_COUNT=0 02:00:25 [19616] < 4> bpbkar main: INF - setenv STREAMS=1 02:00:25 [19616] < 4> bpbkar main: INF - setenv BPSTART_TIMEOUT=300 02:00:25 [19616] < 4> bpbkar main: INF - setenv BPEND_TIMEOUT=300 02:00:25 [19616] < 4> bpbkar main: INF - setenv BACKUPID=as370_0990511247 02:00:25 [19616] < 4> bpbkar main: INF - setenv UNIXBACKUPTIME=0990511247 02:00:25 [19616] < 4> bpbkar main: INF - setenv BACKUPTIME=Tue May 22 02:00:47 2001 02:00:25 [19616] < 4> bpbkar main: INF - Inform when done 02:00:25 [19616] < 8> bpbkar notify: WRN - Missing block incremental notify script /usr/openv/netbackup/bin/bpstart_notify.as370_BLI 02:00:25 [19616] < 4> bpbkar main: INF - Could not open /usr/openv/netbackup/bin/BLOCK_INCR/class_in_control.spps. Setting CLASS_IN_CONTROL to as370_BLI 02:00:25 [19616] < 4> bpbkar main: INF - BACKUP START 02:00:25 [19616] < 2> bpbkar main: INF - CONTINUE BACKUP message received 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (ufs) /dev/vx/dsk/rootvol on / 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (ufs) /dev/vx/dsk/usr on /usr 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (proc) /proc on /proc 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (fd) fd on /dev/fd 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (ufs) /dev/vx/dsk/var on /var 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/appdg/app_01 on /app1 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/appdg/app_02 on /opt/openv 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (autofs) - hosts on /net 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (autofs) auto_home on /home 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (autofs) - xfn on /xfn 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (NFS) as370:vold(pid620) on /vol 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/appdg/app_03 on /app1/inktomi 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/Foracle_dg1/spps1_vol on /oracle_spps1 02:00:25 [19616] < 2> mount build_mount_list: INF - Processing (vxfs) /dev/vx/dsk/Foracle_dg2/arch_vol on /oracle_spps/arch Workaround: Create the BLI scripts using the setup_bli_scripts utility found in the /usr/openv/netbackup/ext/db_ext/oracle/bin directory. (NetBackup Clients) -------------------------------------------------------------------------------- Description: NCVU version 4.5.3 Support for Solaris 9 added. NCVU, NCVU_media_server and NCVU_client are now binaries, Perl is no longer a requirement. Enhanced hostname checking. Added NetBackup 4.5 pack checking. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Suppose you have a machine that is both a NetBackup server and client. Suppose the machine has more than 20 network interfaces and there is a NetBackup client defined for each interface. If the machine (as a server) tries to connect to itself via one of the network interface clients, the connection may fail with a "server not allowed access" error (status 46) or "access to the client was not allowed" error (status 59). For example, the machine may be a media server that is trying to backup a client defined for one of its network interfaces. It is possible that you will see a status 59 error. Workaround: Add the hostnames of all the network interfaces to the SERVER list in the machine's configuration. (All NetBackup Servers and Clients) -------------------------------------------------------------------------------- Description: The Device Configuration Wizard can now configure drives in Plasmon robotic libraries. The drives are now properly configured within the library, instead of being configured as standalone drives. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Suppose you configure catalog backups to be written to a device or directory on a media server and the media server is in the master server's MEDIA_SERVER list, but not in the master server's SERVER list. The catalog backups will appear to fail. You may see messages in the debug logs similar to the following: operation requested by an invalid server Workaround: Add the media server's host name to the master server's SERVER list. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When ejecting media from the NetBackup Administration Console, the user receives a prompt to begin removing the media. At this time, the user has only 10 minutes to remove the media and respond to the prompt in the Administration Console. If the user does not respond in that time, the volumes will be put away, and all tapes' ejects will be aborted. The length of time in which users will have to remove their volumes and respond to the Administration Console will now be 30 minutes. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The update_clients tag when run with the option to update the client's bp.conf entry, causes the existing SERVER lines to be listed multiple times. Now each SERVER entry will stay as it is and not be added a second time. (All NetBackup Clients ) -------------------------------------------------------------------------------- Description: When using update_clients to ship binaries to an AIX client, there would be occasions where the command would fail because it was unable to open a shared library. The errno listed indicated the file was busy. bpinst has been changed to run slibclean first when shipping files to an AIX client. This ensures that all unused shared libraries will be unloaded. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: bplist and bprestore failed if thery were run for an alternate client as non-root, even if alternate names were used. Status code 140, "user id was not superuser" was returned. (All NetBackup Clients ) -------------------------------------------------------------------------------- Description: When using multiple data streams with NDMP, the dump levels for incremental backups were sometimes incorrect causing more data to be backed up than should have been. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Suppose you have storage units defined on more than one media server. Suppose the master server's firewall configuration defines vnetd style connections for some media servers, but not for others. For example, a UNIX master server's bp.conf file might look like this: SERVER = master1 SERVER = media1 SERVER = media2 CONNECT_OPTIONS = media1 0 0 CONNECT_OPTIONS = media2 0 1 If you try to enter a bpmedialist or bpexpdate command that connects to all of the media servers, you will receive "socket read failed" errors. Commands that might cause the error include: bpmedialist -mlist bpexpdate -deassignempty Workaround: Use the same vnetd CONNECT_OPTIONS for all media servers. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: An e4 target descriptor can be up to 20 characters long. The Hitachi 9900 disks provide a 20-character, type 1 descriptor, but an e4 descriptor is not generated because the check that is performed in process_dev is for < 20 when it should be <= 20. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: Suppose you have a policy with the attribute that "allows multiple data streams". In addition, some of the clients of that policy have the client attribute to use "connect-back" connections (the default) while other clients have the client attribute to use "no connect-back" connections. When the server initiates scheduled backups of that policy, there may be delays before the backups are started. For some of the clients, the backups may only use a single stream when multiple streams are expected. You may see messages like this in bpsched's debug log: 01:48:59.867 [23749] <2> rcvline: read timeout (300 secs) from bpmount 01:48:59.867 [23749] <2> rcvline: fgets failed: Interrupted system call (4) 01:48:59.867 [23749] <2> get_bpmount_version: rcvline failed: socket read failed (23) or: 10:16:10.990 [29125] <2> sendline: fputs() failed: Bad file number (9) 10:16:10.990 [29125] <2> get_bpmount_version: sendline failed: socket write failed 10:16:10.991 [29125] <2> build_streams_file: Error obtaining info from bpmount, will build locally: socket write failed (24) Workaround: Make sure all clients in a policy have the "connect-back" attribute or all clients have the "no connect-back" attribute. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The day of the week (Sunday, Monday, ...) is displayed incorrectly on the Catalog node in the NetBackup Administration Console. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The single catalog image .f continues to grow until it eventually fills the disk space on the Windows platform. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: cat_convert core dumps when attempting to convert invalid ASCII catalog entries in the .f file. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Multi-streamed backups end with an error code 229, "Image Inconsistency". (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Performing an import or verify of an image that is created from the backup of a Windows client on a UNIX media server could cause a core dump in tar. Workaround: Perform the import or verify of Windows images on a Windows media server. (All NetBackup Clients ) -------------------------------------------------------------------------------- Description: End-users performing robot ejects from the GUI get a 211 error and the eject fails. The GUI displays the following messge: "There is no available media access port. Eject Preparation Failed: Process killed by signal (211)" From the command line the end-user will see: "/usr/openv/volmgr/bin/vmchange -h host1 -robot_info -rn 0 -rh host1 -rt tl8 -res Process killed by signal (211)" Workaround: The customer can perform ejects from the command line without using the ROBOT_INFORMATION protocol. /usr/openv/volmgr/bin/vmchange -res -multi_eject -w -verbose -rn -rt -rh -ml (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Specify, in the duplication progress log, which media-id is the source and which is the destination to assist in problem resolution. Additional Notes: Added the following I18N message: SmeBtm1109N "INF - Beginning duplication on server %s of client %s image, creating copy %d, destination media id %s." Changed the following I18N messages: SmeDup0020N "media id" SmeDup0030N "path" SmeBtm1110N "INF - %s duplication on server %s of client %s image, creating copy %d." to: SmeDup0020N "source media id" SmeDup0030N "source path" SmeBtm1110N "INF - Continuing duplication on server %s of client %s image, creating copy %d, destination media id %s." (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Extended the REQUIRED INTERFACE concept to cover device configuration and robotic operations. This enables the user to effectively name the media server something different than what is returned by gethostname(), such as the short versus fully-qualified hostname, other host alias, or virtual host name. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Libcatalog is static linked with bpdbm.exe and cat_convert.exe. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Drives are downed silently if the /usr/openv/volmgr/bin/drive_unmount_notify script returns a non-zero status. If ltid is started in verbose mode, a notice will appear, but nothing indicating that the drive was downed. A change was made so that if the script returns a non-zero status, a message will always appear in the system log as follows: Oct 29 10:33:02 host1 ltid[22060]: [ID 365382 daemon.notice] Unmount callout returned abnormal status, DriveName = MyDrive0, Status = 255, DOWN'ing drive Additional Notes: The syslog message now includes the fact that the drive is down, when the drive_unmount_nofity script fails with a non-zero status. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When you run robtest on a Windows Media Server with an ACS robot attached and select the ACS robot, ejecting volumes with the 'eject' command results in the utility failing with the following error: Robotic test utility \acstest.exe returned abnormal exit status (0). This is only known to be a problem on Windows systems. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When spanning a tape, the activity monitor shows the job doing a mounting operation but fails to change to writing when the mount and positioning operations are complete. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Using bplist with a wildcard to a search on a binary catalog has worse perfomance than doing the same search on an ASCII catalog. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Under some circumstances, extended copy backups can fail because the timeout waiting for the command to be executed is too short. This is primarily seen when debug mode is enabled in the mover device itself, which greatly reduces execution speed. Additional Notes: The timeout has been increased from 180 seconds to 300 seconds. The ability to add a to=nnn to the mover.conf entry for a mover has been added to change the timeout value to nnn seconds. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When the first part of a spanned media written by NetBackup NT, is imported (phase 1) on a Unix media server, bpimport fails with the following error message. big-adaj@/nb/bin/admincmd>bpimport -create_db_info -id APSP01 Import phase 1 started Wed Oct 30 2002 10:15:52 INF - Create DB information for media id APSP01. INF - Initiation of bptm process to read media id APSP01 was successful. INF - Status = media position error. Additional Notes: This fix will only prevent the wrong error message "INF - Status = media position error" from being displayed at the time of Phase 1 import. Even without the fix, Phase 1 import would work (only an incorrect media position error message would be displayed). This fix also enables correct EOD detection on some versions of Solaris. This part of the fix is not directly related to Phase 1 import. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: bpdbm cores while trying to verify image. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Restore jobs report meaningless numbers for kilo-bytes/second in the job monitor. Both JAVA and Windows have this problem. Several example from the JAVA debug log (from machine dandelion): JobdInterface.readJobData - reading data for job 7553 Job ID (0): (ignored) 7553 Main PID (3): (ignored) 2514 Job type (7): Restore Status (9): 0 Client (15): dandelion Owner (17): root Group (18): other Job state (22): Done Source media server (29): dandelion Job started (34): 10/16/2002 17:29:04 Job ended (35): 10/16/2002 17:32:16 Active start (56): 10/16/2002 17:29:04 Attempt (36): 1 Kilobytes (37): 17344 Files (38): 0 Kilobytes per second (43): 17344000 Job version (48): (ignored) 2 Suspendable (57): 1 Bit field (49): Job ID (0): 7549 JobdInterface.readJobData - reading data for job 7575 Job ID (0): (ignored) 7575 Main PID (3): (ignored) 18273 Job type (7): Restore Status (9): 0 Client (15): dandelion Owner (17): root Group (18): root Job state (22): Done Source media server (29): dandelion Job started (34): 10/17/2002 15:45:45 Job ended (35): 10/17/2002 16:48:44 Active start (56): 10/17/2002 15:45:45 Attempt (36): 1 Kilobytes (37): 23604992 Files (38): 4829 Kilobytes per second (43): 2147483647 Job version (48): (ignored) 2 Suspendable (57): 1 Bit field (49): (All NetBackup Servers) -------------------------------------------------------------------------------- Description: With NDMP backup turn HIST=n, you cannot browse or see the second directory from bplist. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When attempting to run a user backup, the error was recorded in the user log: Backup started Fri Nov 1 18:19:54 2002 18:19:55 Initiating backup 18:51:54 INF - Backup by root on client isle using policy UBAK1, sched 2weeks: failed trying to allocate memory. ---------------------------------- The include list has 900 individual files, each with a total path length of 40 characters. If the path length is reduced to 27 characters, the backup runs. It appears that the failure is related to the number of characters in the list of files to be backed up, somewhere between 24300 and 28683, (the latter number was derived from the character count that fails at the customer site. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When restoring files that have both the setgid bit set and ACL (Access Control List) information, and overwriting existing files which have had the setgid bit removed, the setgid bit is not restored. Workaround: Manually reset the setgid bit. (All NetBackup Clients ) -------------------------------------------------------------------------------- Description: The bpcllist/bppllist command does not display BLI information for Oracle Proxy. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Using remote NDMP, the backup or restore will hang at random points, usually on large backups. After eight hours of no progress, the job fails with a 99 status. The bptm log shows an error that indicates "no progress". There are no other errors. Remote NDMP performance has been improved significantly by increasing the number of shared memory buffers. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Combined the three NCVU binaries (NCVU, NCVU_media_server and NCVU_client) into one binary (NCVU). This reduces the footprint and download times by 66%. Required adding a new command line parameter -host_node . This also negated the need for the chk_nbu_node.pm module. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When manually configuring tape drives, consult the global database to ensure drive name uniqueness across media servers. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Add device discovery support for the Quantum DX30 robot. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Volume change and move operations would take an excessive amount of time to complete. This could cause vmd to be very slow to respond when an operation such as changing the pool of a volume was performed in a configuration with a large number of volumes in the volume database. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The customer configuration required that one of two possible world wide names be supplied and tested to find the correct value for the selected mover device. Additional Notes: The syntax for 3pc.conf entries was modified to maintain comments and to accept anything from a # character to the end of the line as a comment. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Configuration of TIMEOUT_IN_QUE did not work. Jobs would remain queued even after the timeout had expired. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: An undocumented vmchange option "-single_cycle" has been added to support vault ejects which require that the volumes be allowed to stay in the MAP after an eject has completed. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Media may not get unmounted after multiplexed backups are cancelled. The bptm log shows entries similar to the following, which show bptm receives the -U command from bpsched, but the backup process still has the media locked and the unmount does not occur: 09:31:14.346 [23609] <2> send_brm_msg: EXIT hartstongue_1037114842 150 09:31:16.429 [23940] <2> bptm: INITIATING (VERBOSE = 5): -U 09:31:16.431 [23940] <2> db_byid: search for media id 00009 09:31:16.431 [23940] <2> db_byid: 00009 found at offset 1 09:31:16.450 [23940] <2> db_lock_media: unable to lock media at offset 1 (00009) 09:31:16.450 [23940] <2> bptm: EXITING with status 0 <---------- 09:31:18.303 [23946] <2> bptm: INITIATING (VERBOSE = 5): -U 09:31:18.305 [23946] <2> db_byid: search for media id 00009 09:31:18.305 [23946] <2> db_byid: 00009 found at offset 1 09:31:18.320 [23946] <2> db_lock_media: unable to lock media at offset 1 (00009) 09:31:18.321 [23946] <2> bptm: EXITING with status 0 <---------- 09:31:19.340 [23609] <2> bct_clear_active: removing group 0 shmid 109 09:31:19.341 [23609] <2> bct_clear_active: Set BCTable entry 1 to inactive, ACTIVE_GC count decremented to 0 09:31:19.341 [23609] <2> write_backup: waited for full buffer 141 times, delayed 351 times 09:31:19.342 [23609] <2> bptm: waiting for TERMINATE from bpbrm/bpsched 09:31:19.342 [23609] <2> read_brm_msg: TERMINATE 09:31:19.342 [23609] <2> bptm: EXITING with status 0 <---------- (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Occasionally robot operations will fail on the ADIC Scalar family of libraries due to a corrupted transport element address. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Fail to restore second directory(volume) for NDMP backup with HIST=N setting. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Added device discovery support for FUJITSU LT160. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When allocating tape resources for inline tape copy, locally attached storage units were not being favored over non-local ones. This patch corrects this behavior. However, the must_use_local_drives is not honored for inline tape copy at this point. Must_use_local_drives support will be added to inline tape copy in the next patch. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The MAP_ID vm.conf entry does not take effect. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: vmchange -res -robot_info fails on libraries with no mailslots. (All NetBackup Servers) ================================================================================ ============= Java list ================================================================================ Description: This patch fixes a failure in the NetBackup-Java Administration Console to correctly set the Override Policy Volume Pool checkbox when a schedule overrides the volume pool for a policy with a disk storage unit. Symptoms of the problem that this patch fixes: Create a policy with a disk storage unit. Create a schedule, select Override Policy Storage Unit and select a non-disk storage unit, then select Override Policy Volume Pool. It is possible to save this schedule correctly, but the next time the GUI is used to edit the schedule, the Override Policy Volume Pool checkbox is not correctly enabled and selected. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: In NetBackup 4.5, the Catalog Backup tab provided a default value for the "Volume Pool" in the profile dialog. Because this default can be "bad", a change has been made to provide no default. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: On AIX NetBackup Server, the Vault Java GUI application disabled all functionality without giving the correct error messages to the user if the Vault configuration file was missing. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: The text for suspend media option on eject tab in the Vault Java GUI is being truncated in Japanese Locale. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: The 'New vault' operation fails in the Vault Java GUI when there are no volume groups configured for the robot, for which the vault is being created. The error messages does not say that there are no volume groups. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: When the load of a directory is interrupted, double-clicking on that same directory in the right-hand pane (table) does not load the directory and appears to do nothing. Navigating to a different node in the tree and then back to the node representing the interrupted directory results in a successful load. This can also cause a bit of consternation for the user as the data in the table does not correctly correspond to the data for the selected node in the tree once the interrupt is initiated. (All NetBackup Java GUI capable NetBackup servers and clients) ============= 112407-02 ============= Description: The message file, OutMsgs, is used by NetBackup Administration Console and not by NetBackup core programs. Renamed ~20 message ID's to go to PrgMsgs file so that they are found by the NetBackup core programs using the ovgetmsg() function. Previously, these messages would always be displayed in English (not translated). (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Progress logs for backup and restore may be incomplete. The file open() function returns a -1 upon failure, but the code was checking for positive non-zero success. On an almost idle system, it is possible to get a zero value for a file descriptor. If this were to happen, the (backup or restore) process would not log all messages. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: By adding two bpclinclude signatures with -f option It is now possible to add a file that contains a list of includes and avoid long command line problems. The two signatures are: - bpclinclude policy_name [-v] [-M master_server,...] -add -f filename - bpclinclude policy_name [-v] [-M master_server,...] -delete -f filename (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When doing a TIR with move detection backup, the bpbkar process core dumped and exited with a status 130 (system error occurred). (All NetBackup Clients) -------------------------------------------------------------------------------- Description: Add device support for the COMPAQ TSL-10000 DAT Autoloader. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The SCSI-2 prevent/allow capability has now been added to the tldtest binary. In some cases, user were locked out of their libraries by other applications or third-party drivers. The robtest utility enables you to unlock the library by issuing the "allow" command. Workaround: The customer is able to use tl8test on their tld library's robotic control path and then issue an "allow" command from there. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The add robot option in the tpconfig menu listed robot types 1 through 12, with the twelfth robot type listed as TSH. However, the prompt that the user received asked the user to enter a number between 1 and 11. The program would accept an entry of 12 even though the display was incorrect. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When large numbers of small files are backed up, the directory entries were sorted into alphabetical order, but the backup takes longer in sorted order when compared to the directory order. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: There are circumstances where ja locale java files might erroneously be removed from /usr/openv/java. One example would be a client patch being pushed to a client that had the NetBackup Japanese Message Files package installed. Code has been added to make sure that the ja locale java files are no longer removed in these circumstances. (All NetBackup Servers and Clients) -------------------------------------------------------------------------------- Description: Fix core dump in acstest where acs ejects would fail due to uninitialized variable. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Add support for new ACSLS 6.1 drive and media types. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The BSAQueryObject function calls an internal function which sets signal handlers. This sometimes affects the signal handlers set by the agents using the XBSA interface, in this case DB2. BSAQueryObject will no longer set the signal handlers. Also, on UNIX systems, an incompatibility exists between IBM DB2 and NetBackup for DB2 which can halt a DB2 process. The problem results from an incompatibility involving UNIX timer events (i.e. SIGALRM signal). This failure is difficult to predict, because it is dependent upon several conditions within DB2 and NetBackup. Additional Notes: An example of this condition as recorded in the DB2 db2diag.log file: 2002-05-07-12.08.38.097656 Instance:db2inst Node:000 PID:60322(db2db 0) Appid:none oper_system_services sqloEDUSIGCHLDHandler Probe:30 waitpid() status of abnormally terminated child process: 0000 000e .... 2002-05-07-12.08.38.110692 Instance:db2inst Node:000 PID:60322(db2db 0) Appid:none oper_system_services sqloEDUSIGCHLDHandler Probe:50 Signal that terminated the child process: 0000 000e .... (All NetBackup Clients) -------------------------------------------------------------------------------- Description: When importing images with UIDs or GIDs over 65535, the code would loop on the record preceding the file with the long UID or GID. This would then cause extra entries to be generated in the NBU database and eventually fill up the filesystem. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: Periodically the Device GUi performs a synchronization operation between the local device databases on each media server and the global datatbase. This operation may report false positives in the case where ACS controlled drives are present. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Possible vmd core dump when using the command line to change the number of days to keep media manager debug logs. For example: vmquery -keep_logs 1000 Workaround: The workaround is to manually edit the "DAYS_TO_KEEP_LOGS = " entry in the vm.conf file. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: bplist exits with status that is not localized. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: message id conflicts between nb/admincmd/bpconfig.c and nbe_tape/beconv/beconv_engine.cpp This results in some localized messages being displayed incorrectly. This is not a problem in english locale. problem manifests itself in the japan locale. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Release 4.5.2 of the NetBackup Configuration Validation Utility (NCVU). (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Backup verification fails with "unexpected message received" error. A restore of the backup is successful. The admin log will have an entry similar to the following: 09:56:51 [19428] <16> get_adaptable_string: (4) network read() error: Connection reset by peer (131) (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Incorrect time displayed on bpexpdate verify message: #./bpexpdate -recalculate -backupid stuka_1024730370 -copy 1 -d 12/12/2008 12:00:00 Are you SURE you want to recalculate expiration dates on all images that meet the following criteria: backupid stuka_1024730370 copy 1 to expire on Fri Dec 12 2002 14:50:08 Continue?(y/n)y NOTE: the recalculate actually works and sets the expiration to the entered year example 12/12/2008, however the confirmation message shows 2002. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: During certain incremental backups, the file list wouldn't always include all the directories required to find the correct file. This could cause bplist to fail (with a status 227 -- "no entity was found"), or certain files to not appear in the restore list. Workaround: The bplist error could be worked around by not appending a "/" at the end of the path (for a directory), or by turning off indexing. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: Add the logging utilities currently available on our web site to a 4.5 patch so the customer does not have to download them. (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: The nb/admincmd/nbdbsetpw program queries for password and confirmation are done in English only. This change localizes the queries for the benefit of non-English speaking customers. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Add support for Instant Image. Additional Notes: New messages (bpbkar): PrgBkr2391N "Could not set ServerFree Client - Media Server relationship." PrgBkr2392N "Client (%s) and Media Server (%s) are the same." PrgBkr2393N "Client (%s) and Media Server (%s) are different." (All NetBackup Servers and Clients ) -------------------------------------------------------------------------------- Description: Corrected conflicting i18n message. All references to message id MMmTPC0733V now read "NDMP drives should be in form of client:drivepath, no /ndmp should be present." (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Media is not unmounted when it should be, or media is incorrectly unmounted. This only occurs in unusual circumstances, for example when a job is cancelled. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The possibility exists for a MPX backup to fail checking if the media is from a previous NDMP backup and return without setting the exit status correctly. This change correctly returns the correct error code. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: After receiving a mover pause the issueing of a mover abort was causing NDMP data connection problems on vendor filers. Various errors were encountered including restore hangs, NDMP internal errors, as well as media errors. This change alters the behaviour after receiving the mover pause we no longer issue the mover halt but rather wait for the data halt message and then clean up the connections. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Multiple eject and Multiple Inject do not work with the ADIC Scalar 10k and other very large SCSI libraries. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If an NDMP backup using multiple datastreams uses a wild card in the filelist, backups fail. Auto discover is not supported for ndmp but scheduler was attempting autodiscover anyway. The autodiscover feature is now disabled for ndmp. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Fail to browse or convert compressed binary catalog .f files. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Image database cleanup not working if empty catstore dir exists (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Binary catalog creates .f file when one should not exist (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Fastrax restores that suspend due to Fastrax resource limits may mount the same tape repeatedly, restoring relatively little data per mount. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Every other Fastrax backup LBO has only one extent. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Files already successfully restored are deleted if a subsequent error terminates the overall restore. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Some LBO-related global functions are not prototyped in lbo.h (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Add support for serializaton of drives in the Securitus I virtual tape library from Alacritus Software, Inc. Workaround: Drag and Drop the tape drives into the library. Additional Notes: All Virtual Library Types must have Vendor Type set to "ALACRIT", and Product Id set to "VTL". Any other value will not work with auto-discovery. Firmware must be 02.01.00 (Build #1080) or above. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Reported Kbyte/sec backup rates were too high for Fastrax backups that caused LBO definition to be suspended for lack of Fastrax resources. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: For Fastrax restores, alternate path and alternate destination restore were not working. For alternate path restores tar was removing the rename file before bpblr attempted to process it. For alternate destination restores, bptm was supplying the original client name as the alternate destination. (NetBackup Servers Clients) -------------------------------------------------------------------------------- Description: cat_convert can fail and create a bad catalog entry when the disk is full, but report success (All NetBackup Servers) -------------------------------------------------------------------------------- Description: For disk storage units on a down media server, scheduler would repeatedly attempt to ping the host. A timeout occured each time which was a major impact on scheduling since this was happening in the main scheduler process. This has been corrected by changing such that when the media server is detected as down, the pings no longer occur. A very small memory leak was eliminated in bpsched. If no policies existed and a user backup was initiated, scheduler would fail to write entries into the progress log and activity monitor that indicate why the job failed. If a job was started in which the go into effect date was in the future, the job would fail without entering the job in the activity monitor. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: In MSC backup with SOLARIS, data is read from /dev/rdsk/cxtxdxs2. s2 partition is assumed to be the whole disk without checking. Generally s2 is the whole disk, but there are cases that s2 partition isn't. Added checking for the s2 partition. If it's not the whole disk, report error and abort. Error should looke like this: shb_insert: Can't read the disk shb_insert: Partition 2 doesn't start from sector 0 shb_extend_copy: device partition is invalid (All NetBackup Servers) -------------------------------------------------------------------------------- Description: th bpclinfo/bpplinfo command allowed the -blkinc option even if the bli license is not installed. Also a bad argument on that field was not rejected. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Bpbkar failed to mount vxfs clone on HP-UX 11i. This problem was caused by bpbkar invoking the mount and umount commands with out specifying the full pathnames. Additionally, during regression testing fixed a bug with BLIB backups where the Oracle data files were configured directly under the root filesystem. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: bpdbm <16> compress_dbfile: system() returned 512 when compress zero length catalog image section file. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Beginning with 4.5 GA, the customer attempts to refresh the media tree/pane in the Client (Java) GUI. Nothing happens. This fix requires the installation of the NBJava GUI MP2 maintenance pack. (All NetBackup Servers and Clients) -------------------------------------------------------------------------------- Description: Solaris needs new IBM ATL library version 5.2.2.0 available from IBM to support the 3590H drives in an IBM 3494 library (NBU TLH library). (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Enhanced the robotic drive selection algorithm for the Shared Storage Option (SSO) to help avoid tape mount delays. The robotic daemons previously checked with ltid, the Media Manager device daemon and NetBackup Device Manager service. Now, the robotic daemons make the check directly for assigned drives, skipping those, thereby reducing the load on ltid. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When using a Crossroads router as an extended copy data mover, and the router has tape queueing enabled, the initial extended copy command can be started before the backup label write has completed. The retry sequence for extended copy commands was too fast and the number of retries too few to get past this condition. Workaround: Disable tape queueing on the Crossroads router. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Improve drive selection for NDMP restores by allowing robotic daemons to select any available drive in the tape library and not be required to select a drive connected to a specific NDMP host. Also correct a bpsched problem where backups were being started on a storage unit with no available drives, resulting in error code 20 (Invalid argument). (All NetBackup Servers) -------------------------------------------------------------------------------- Description: 134 errors(resources busy) are being logged in the error as errors even though they are not errors and should not be logged. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The number of include/exclude dates that can be configured in a calendar schedule is limited to 70. This change increases the limit to about 250. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When NetBackup is used with an ACS robot with more than 10 CAPs/MAPs (StorageTek term, cartridge access port; NetBackup term, media access port) the pre-eject phase of multiple media eject fails. In the Media Manager Administrative Interface for Windows and Java, the Eject Dialog window shows an error explaining that there are no MAPs available to eject to. In the NetBackup Vault product, the vltopmenu eject operation fails with an error 299: "There is no available MAP for ejecting". Also, an automatic eject operation for a vault session will fail with error 299 in the detail.log file. Workaround: Ejects can be performed with the /usr/openv/volmgr/bin/vmchange command line interface by choosing a MAP that is known to be available. See the vmchange man page for how to perform the multiple eject operation. Additional Notes: Using the /usr/openv/volmgr/bin/vmchange or INSTALL_PATH\volmgr\bin\vmchange command line utility with the "-res - pre_eject" or "-res -robot_info" arguments, the MAP_INFO output contains only "MAP_INFO 0 0 0 0 0 0". (All NetBackup Servers) -------------------------------------------------------------------------------- Description: vmd logs too much information to the daemon debug log by default. very string that is sent and received over the socket is logged. In cases where there are tens of thousands of volumes in the volume database, the daemon debug log can hit the current 2GB size limit. Much of the information logged is unneeded or only needed when trying to debug a rare problem. By reducing the volume of logging it will be easier to diagnose problems. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When the volume database contains tens of thousands of volume records, some vmd queries did not return the list of volume records to the caller in the most efficient manner possible. Whenever one of these queries was made, it would consume the vmd connection for an extended period of time, leading to contention for vmd connections among multiple processes and machines in large NetBackup installations. This change replaces many of those queries with a more efficient version which will both speed up the return of the list of volume records to the caller and, in turn, reduce the contention for vmd connections in large NetBackup installations. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Large catstore directores. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Timezone issues with Calendar based scheduling. First issue affects the Administration Console GUI on a UNIX master server only, the NT GUI is ok. The issue can be seen by doing using Calender based scheduling polices using "Recurring Weeks Days" option. Graphical green ticks are not displayed for all the days selected. This issues is now corrected. The second issue happens running using TZ=Israel (i.e. GMT+3 and above for locations east of GMT). Situation occurs when calendar based cumulative incremental schedule with "Retries allowed after runday" and then selecting "Set All" for 'Recurring Week Days'. The cumulative incremental backup will be started every time bpsched wakes up and a window is open for that schedule. By default, this causes the scheduler to initiate a backup every ten minutes. Resetting back to TZ=GB the schedule no longer runs even though the window is still open. All of the above issues is now corrected with the inclusion of Sig 2.50.028/SchedulingService/v2.50.028 and SigFCL/v2.50.020. bpsched log entries displaying symptoms of issue TZ=Israel are: 13:20:26.069 [10141] <2> calendar_due_day: No specific exclude dates entered 13:20:26.114 [10141] <2> calendar_due_day: last runtime=07/22/2002 next_run_time=01/01/1980, 13:20:26.114 [10141] <2> calendar_due_day: due With TZ=GB, the last 3 lines are as follows for the same class/schedule: 13:09:13.397 [1674] <2> calendar_due_day: No specific exclude dates entered 13:09:13.453 [1674] <2> calendar_due_day: last runtime=07/22/2002 next_run_time=07/22/2002, 13:09:13.453 [1674] <2> calendar_due_day: not due (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Bpduplicate periodically sends keepalives to bpjobd. If bpjobd does not receive a keepalive within a certain period of time (20 mins.), it considers the job done and sets the status to 50 (client process aborted). There are 2 situations where this could occur with bpduplicate: - multiplexed duplications; it appears that the code to send the keepalives is not present in this case. - for non-mpx duplications for Unix. The time period for sending the keepalive is 20 mins. - 30 seconds. While waiting for statuses from bptm, bpduplicate is waiting on a select(). NT times out of this select() every 10 secs., but Unix does not. It does get a keepalive from bpdbm every 1 min. However, the timing could be such that bpduplicate would not send the keepalive in the appropriate amount of time. (All NetBackup Servers) -------------------------------------------------------------------------------- ============= Java list ================================================================================ Description: The Move Volume Dialog does not properly size itself when using MBE. Workaround: Manually resize the dialog. -------------------------------------------------------------------------------- Description: The date/time field in the Change Volume dialog is not large enough to see the entire date/time when using MBE. -------------------------------------------------------------------------------- Description: The Rescan/Update Barcodes dialog was not properly sized when using MBE. The dialog was updated to correctly work with MBE. -------------------------------------------------------------------------------- Description: The hosts, robots, and drives tabs in device management needed to be localized. -------------------------------------------------------------------------------- Description: Correct a spelling error in a localized constant. -------------------------------------------------------------------------------- Description: Need to localize "tapes" and "errors" on the Eject dialog -------------------------------------------------------------------------------- Description: Need to localize "hosts" on the configuration analyzer. -------------------------------------------------------------------------------- Description: Device management - drive cleaning dialog headers can't be expanded. -------------------------------------------------------------------------------- Description: If the user selected export under vault, the gui would generate a traceback. The export option should not be available under vault. -------------------------------------------------------------------------------- Description: The Media Id Generation Dialog was not sizing properly. The code was updated so the dialog properly sizes for MBE. Workaround: Manually increase the size of the dialog. -------------------------------------------------------------------------------- Description: The Device Monitor uses "PEND" as a control status. The PEND status was not being converted into a localized string. The code was modified so PEND will now be properly translated. -------------------------------------------------------------------------------- Description: Added new ACSLS 6.1 media types: ACS_VIRTUAL ACS_LTO_CLNU -------------------------------------------------------------------------------- Description: On Japanese systems the File System Analyzer would not display graphs. -------------------------------------------------------------------------------- Description: Default size of confiration dialog box was small so it was not showing complete text Workaround: Just increase size of the dialog to see the complete text. -------------------------------------------------------------------------------- Description: Strings in message box title are not internationlized properly. -------------------------------------------------------------------------------- Description: When a nonroot user tries to move media back to robotic status with the Java GUI, it fails "system error occurred". In some other operations within Media Management the GUI may hang for a nonroot user. This fix is dependent on a fix to bpcd, so installation of the MP2 UNIX client maintenance pack is required. -------------------------------------------------------------------------------- Description: A label change was made in the NT GUI, but didn't get into the Java GUI. There is a text box labelled "Eject tapes from these volume pools only:" to be consistent with the NT GUI and the user doc, this was changed to "Off-site volume pools (eject tapes from these volume pools only):" -------------------------------------------------------------------------------- Description: Choose Backups is configured with "". Advanced view of Dup tab has one dulplication rule (i.e. not all media servers are represented in duplication rules). Problem: The dialog which is to warn the user that the Choose Backups media server list has servers not represented in duplication rules does not appear. The GUI allows the user to save this configuration with no warning. -------------------------------------------------------------------------------- Description: Using the Vault Java GUI, every time a change is made to the Vault config, the user gets an error dialog saying: The vault configuration was saved to /usr/openv/netbackup/logs/user_ops/vault/vault.tmp..xml. An attempt to rename this file to /usr/openv/netbackup/db/vault/vault.xml Failed. In order to proceed further rename /usr/openv/netbackup/logs/user_ops/vault/vault.tmp..xml to /usr/openv/netbackup/db/vault/vault.xml and do a refresh. The error dialog is displayed because when the source and the destination files for the rename are on separate filesystems, then the rename would fail giving an error. This problem has been fixed for situations where the Java GUI is being run locally, from the master server being modified. -------------------------------------------------------------------------------- Description: Using the Vault Java GUI on Solaris 8.0 (64 bit). Every time a change to the Vault config, the gets the error dialog: The vault configuration was saved to /usr/openv/netbackup/logs/user_ops/vault/vault.tmp..xml. An attempt to rename this file to /usr/openv/netbackup/db/vault/vault.xml Failed. In order to proceed further rename /usr/openv/netbackup/logs/user_ops/vault/vault.tmp..xml to /usr/openv/netbackup/db/vault/vault.xml and do a refresh. The error dialog is displayed because when the source and the destination files for the rename are on separate filesystems, then the rename would fail giving an error. -------------------------------------------------------------------------------- Description: When logging into the Java GUI on a UNIX machine, and then doing a change server to a Windows master server, the user was unable to make/save any changes to the vault configuration. This has been corrected. Additional Notes: The following scenarios are not supported by Netbackup in non-english locales : logging into a Localized(eg Japanese) UNIX Master server and administering a Localized(eg Japanese) Windows Master server by doing a Change Server. logging into a English UNIX Master server and administering a Localized(eg Japanese) Windows Master server by doing a Change Server. logging into a Localized(eg Japanese) UNIX Master server and administering a English Windows Master serverby doing a Change Server. ================================================================================ ============= 112407-01 ============= Description: When trying to create a storage unit group with no storage units in it, the new storage unit dialog goes away when you click OK. The group is not created and no error message is shown. When you click OK, an error dialog should appear and remain visible. The error message should inform the user that a storage unit group must contain at least one storage unit. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The spinner control on the GDM page in the Host Properties dialog has a limited input of 32767. This patch properly limits the input to 32767 and corrects a problem where a user was able to enter data without the spinner control of up to 65535. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: In NetBackup 4.5, if a user attempts to eject a tape, which is currently mounted, the user will get a final status of "Eject aborted." Nowhere is it noted that the eject was aborted because the tape was mounted. This fix provides a new final eject status of "This volume is mounted, eject failed." to indicate which volume was in the drive. Furthermore, this volume will be skipped and other volumes in the request will be handled correctly. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: In NetBackup 4.5, if a user is using the new -multi_inject option for vmchange, the inject session will simply abort when the library becomes full - with no indication of why. Furthermore, any tapes which were in the last MAP-full that had been injected before the library was full, will report the incorrect status "Inject Aborted." Now users will see the correct status for the tapes which were successfully injected and the library full status for the tape that failed to inject due to the library being full. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: In NetBackup 4.5 users will get incorrect status from libraries with multiple-volume mailslot elements. A multiple-volume mailslot element is one singe element address within the library that is capable of holding more than one volume. Usually these are gravity-fed mailslots but there can also be full and not full mailslots. Examples of such libraries are the SpectraLogic Gator 12000 or the Breece Hill Q140/210. The status will be correct for the first volume in the MAP but subsequent volumes will have statuses of pending or scanning. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: sgscan and sg.build would only detect tape and library devices connected to Sun F/C HBA's. If a bridge is exporting a data mover, or other device on LUN 0, then these utilities wouldn't configure the bridge for use with the VERITAS SG driver. Report any type 3 device as a Processor in the sgscan output. Report any type c device as an Array-controller in the sgscan output. Resolve SunSolve BugID 4693371, detect and configure devices connected via Fabric Topology. Workaround: Manually add the bridge to the sg.conf and devlink.tab files. Use the sgscan "basic" mode to report all devices, and look for the Movers. No workaround for SunSolve BugID 4693371. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The NetBackup Administration Console for Windows was improperly limiting the addition and deletion of storage unit names of up to 125 characters. (The command line properly limits storage unit names of up to 128 characters.) This problem was evident when attempting to delete a storage unit from the NetBackup Administration Console for Windows with 125 to 128 characters that had been created from the command line. The NetBackup Administration Console for Windows has been fixed to properly accept storage unit names up to 128 characters. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The bpjava* servers released in NetBackup 4.5 did not provide the Java clients with a mechanism for using the BPCD_WRITE protocols and insuring that the file in question was truncated if it pre-existed. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: On a NetBackup BusinesServer host, the global device database host must be the local host. If a user has both DataCenter and BusinesServer hosts, the global device database host on the BusinesServer host could be changed by adding the BusinesServer host to the host list when running the device configuration wizard and connected to a DataCenter host. When the global device database host is changed on a BusinesServer host, robots cannot be configured. Additional Notes: Changed message: OLD: "unused Media Manager error 38" NEW: "Current version does not support remote device host" (All NetBackup Servers) -------------------------------------------------------------------------------- Description: This patch entry eliminates bad catalog content because of illegal duplicate NDMP node messages for the same node sent from Auspex NAS boxes. To correct this problem the binary catalog engine's NDMP message processing algorithm has been modified to ignore duplicate NDMP node messages. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Fastrax metadata can be corrupt if Fastrax restore fails with SYMAPI_C_DEVICE_NOT_FOUND. This error code appears in the symlogs and the bptm logs during restore. Additional Notes: If this error occurs, certain files in the backup will not be restorable, even though the backup appeared to have been successful. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The lifetime limit for the number of logical backup objects (LBOs) per VC is 64. This limit should be 1024. Currently, if you exceed the limit of 64 the backup will terminate with the bptm log message: "Exceeded maximum number of logical backup objects." (All NetBackup Servers) -------------------------------------------------------------------------------- Description: During Fastrax backup, bptm can become mired in a state in which logical backup objects (LBOs) of one extent each are created until Fastrax resources or NetBackup heap memory are exhausted. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Fastrax restore repeatedly dismounts and remounts the tapes involved in the restore, or persistently unmounts and remounts the same tape if there is only one tape involved in the backup. This only occurs if the restore definition must be suspended because of a lack of Fastrax resources, that must be reclaimed before the restore can continue. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The code to generate random port numbers in a given range has been modified so it does not generate duplicate port numbers in succession. On HP/UX 11.0, if a connection is initiated re-using the port number used by a previously closed connection that is in TIME_WAIT, the new connection times out. HP has fixed this problem in patch # PHNE_22397. The above fix has been added to eliminate the conditions that lead to the connection timeout problem experienced via the NetBackup Administration Console for UNIX. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: This patch entry provides additional text descriptions of the ASC/ASCQ error codes for more standard errors, as well as a vendor unique error from the EXB 221L (0x5/0x3b/0x90). (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Restores of Quick I/O files to a file system with a larger file system block size get allocated more blocks than necessary. The extent information needs to be modified to account for the larger file system block size. Workaround: Restore Quick I/O files to a filesystem with the same block size. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: For unusually large file sizes (> 32 bit) the high order 32 bits were not being returned in the remote browse. This resulted in the client returning an incorrect entry that caused remote browse to GPF (Gross/General Protection Fault). It now returns zero. Please see DDTS RSVmn30702. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: Incorrect "Bad image header" entries occur in the problem report and bpdbm debug log when block-level, incremental images expire. The bpdbm log shows entries similar to the following: 10:49:02.347 [6060] <2> db_get_image_info: fopen (/usr/openv/netbackup/db/images/hartstongue/1018000000/test_1018363428_FULL) : No such file or directory (2) 10:49:02.348 [6060] <2> image_file_name: ? 10:49:02.349 [6060] <16> delete_expired_backups: Bad image header: test_1018363428_FULL (All NetBackup Servers) -------------------------------------------------------------------------------- Description: This adds SONY DMS libraries to external mappings file, as TLD robots. It also ignores storage slots that are configured as cleaning slots for automatic robotic cleaning. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Robotic daemons log messages may contain non-printable characters when performing inquiries on devices. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Messages that should be in a server-directed restore progress log are missing if a SIGCLD occurs during the write to the file. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Restricted media servers may not be able to do Lotus Notes restores or Single Instance Store and Hard Link restores. The NetBackup System Administrator's Guide includes a section called, "Restricting Administrative Privileges of Media Servers". This section describes how to set host properties on a master server to prevent OS administrators on one or more of its media servers from being NetBackup administrators on the master server. A media server configured with these restricted privileges may not be able to do a "secondary restore". Secondary restores can occur during Lotus Notes restores or Single Instance Store and Hard Link restores. The likely error is "client is not validated to perform the requested operation" (135). Workaround: If you need to do Lotus Notes restores or Single Instance Store and Hard Link restores, you will need to make sure the media server is an unrestricted server in the master server's hosts properties. This means the media server is in the "Additional Servers" list rather than the "Media Servers" list for the master server. (Or for a UNIX master server, the media server is listed in a SERVER entry rather than a MEDIA_SERVER entry.) (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The example usage text provided by the vmchange command suggests date and time input parameters in a fixed format rather than suggesting an input format appropriate for the user's locale setting. Listing locale-insensitive example text may mislead administrators to believe they must provide date-time data to the vmchange command in a format other than the preferred format for their locale. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The end user could not delete partially configured robots that had drives associated with them. The user would get an error 12 with the text: "Failed writing drive or robot config file" Workaround: From the command line, the user can use tpconfig to delete the drives associated with the robot. Then, deleting the robot should work. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Added the -l option to vmquery to display the same data as the -w with the following exceptions: - no header line is displayed - the robot control host name is not truncated The -w display contained a formatted output that could not accommodate 256 character hostnames. Workaround: The -j option provides a similar display, however it is not supported and subject to change without notice. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Two possible error conditions that are very rare could cause the system to panic in the snap driver. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: Resume logic must re-establish the SCSI Reservation prior to checking the current tape position. The problem that caused resume logic to be activated may have caused the SCSI Reservation to be lost. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The catalog backup up appears as DONE on the Activity Monitor while it is still running. I know that it is still running because the bpbackupdb processes are still going and the server will not start an immediate backup of a policy/schedule while the catalog backup is still running. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When running AUTO_UPDATE_ROBOT, the tldcd parent process can core dump while attempting to empty out the media access port on some robots. Workaround: Turn off AUTO_UPDATE_ROBOT. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: TIR with move detection fails to manage the tir_info directory properly when wildcards are used in the filelist. This causes the incrementals to back up all the files specified each time an incremental is run for the filelist entries with a wildcard in the name. Workaround: Don't use wildcards in the filelist when using TIR with move detection. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: After a media write error (error 84) from bptm, during a multiplexed duplication, the bpduplicate process hangs. However, the bptms exit properly. Here is a snapshot of administration log after this error. 22:07:44 [167.55] <2> read_media_msg: ERROR 84 22:07:44 [167.55] <2> process_WRITE_media_msg: ? 22:07:44 [167.55] <4> process_WRITE_media_msg: got ERROR 84 from media manager 22:07:44 [167.55] <2> terminate_mpx_group: called by write 22:07:44 [167.55] <2> send_WRITE_media_msg: (pid 279) TERMINATE 22:07:44 [167.55] <16> put_long: (11) network write() error: Connection reset by peer.; socket = 88 22:07:44 [167.55] <16> send_WRITE_media_msg: could not write TERMINATE to media socket. bptm pid = 279 22:07:44 [167.55] <2> send_READ_media_msg: (pid 173) STOP ALL 22:07:44 [167.55] <2> signal_media: setting pending msg event 22:07:44 [167.55] <2> release_write: ? 22:07:44 [167.55] <2> handle_backup_image_status: hcus-ny24_1016154366 status = 84 22:07:44 [167.55] <2> getsockconnected: host=HCUS-NY24 service=bpdbm address=10.40.33.12 protocol=tcp non-reserved port=13721 22:07:44 [167.55] <2> getsockconnected: host=hcus-ny24 service=bpcd address=10.40.33.12 protocol=tcp reserved port=13782 22:07:44 [167.55] <2> getsockconnected: Connect to hcus-ny24 on port 526 22:07:44 [167.55] <16> BPDUPLICATE: host hcus-ny24 backupid hcus- ny24_1016154366 write failed, media write error (84). 22:07:44 [167.55] <2> duplication_complete: hcus-ny22_1016154357 finished:1 write_finished:1 22:07:44 [167.55] <2> duplication_complete: hcus-ny22_1016154358 finished:1 write_finished:1 22:07:44 [167.55] <2> duplication_complete: hcus-ny22_1016154359 finished:1 write_finished:1 22:07:44 [167.55] <2> duplication_complete: hcus-ny23_1016154360 finished:1 write_finished:1 22:07:44 [167.55] <2> duplication_complete: hcus-ny23_1016154361 finished:1 write_finished:1 22:07:44 [167.55] <2> duplication_complete: hcus-ny23_1016154362 finished:1 write_finished:0 22:07:44 [167.55] <2> handle_backup_image_status: duplication not complete After this point bpduplicate will loop for statuses indefinitely. 03:09:40 [167.55] <2> mon_mm: select: 0, w:0, r:-1, h:0 03:09:40 [167.55] <2> start_indep_grp: active_mpx_groups:0, active_backups:0, Starting 03:09:40 [167.55] <2> start_indep_grp: p_image = NULL 03:09:40 [167.55] <2> start_indep_grp: oldest_time = 0x7fffffff 03:09:40 [167.55] <2> start_indep_grp: active_mpx_groups = 0 03:09:40 [167.55] <2> start_indep_grp: p_active_dup_for_first_grp = NULL 03:09:40 [167.55] <2> start_indep_grp: p_first_mpx_group_for_restore = NULL 03:09:40 [167.55] <2> next_active_mpx_group: 8573296: bptm_pid:0 03:09:40 [167.55] <2> next_active_mpx_group: 8573216: bptm_pid:0 03:09:40 [167.55] <2> next_active_mpx_group: 8573376: bptm_pid:0 03:09:40 [167.55] <2> next_active_mpx_group: 8573296: bptm_pid:0 03:09:40 [167.55] <2> next_active_mpx_group: 8573216: bptm_pid:0 03:09:40 [167.55] <2> mon_mm: called by mpxdup 03:09:50 [167.55] <2> mon_mm: select: 0, w:0, r:-1, h:0 03:09:50 [167.55] <2> start_indep_grp: active_mpx_groups:0, active_backups:0, Starting 03:09:50 [167.55] <2> start_indep_grp: p_image = NULL 03:09:50 [167.55] <2> start_indep_grp: oldest_time = 0x7fffffff 03:09:50 [167.55] <2> start_indep_grp: active_mpx_groups = 0 03:09:50 [167.55] <2> start_indep_grp: p_active_dup_for_first_grp = NULL 03:09:50 [167.55] <2> start_indep_grp: p_first_mpx_group_for_restore = NULL 03:09:50 [167.55] <2> next_active_mpx_group: 8573296: bptm_pid:0 03:09:50 [167.55] <2> next_active_mpx_group: 8573216: bptm_pid:0 03:09:50 [167.55] <2> next_active_mpx_group: 8573376: bptm_pid:0 03:09:50 [167.55] <2> next_active_mpx_group: 8573296: bptm_pid:0 03:09:50 [167.55] <2> next_active_mpx_group: 8573216: bptm_pid:0 03:09:50 [167.55] <2> mon_mm: called by mpxdup (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Fastrax single file restore fails with the following error: SYMAPI_C_READ_METADATA_FAILED. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Fastrax backup bptm core dumps in commit_extent(). (All NetBackup Servers) -------------------------------------------------------------------------------- Description: A multi-tape, multi-LBO restore terminates normally before the restore has completed. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The command bptpcinfo -c is used to check syntax errors of 3pc.conf. Currently, it checks parameter values, but not for parameter combinations. For example, if a device entry is constructed with w=, or n=, it must have l=, otherwise, the TPC backup will fail when the device is used. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Inquiry page 0x83 Type 7 (MD5) has been approved at T10. We need to add type 7 as a supported identifier, so the type 7 identifier can be used when scsi-to-fc bridge vendors support it in the near future. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: After a couple of attempts of adding and removing devices on a media server, some entries in the 3pc.conf are no longer valid. There is a need to remove those invalid entries. Currently, there is not any bptpcinfo option to do this. Therefore a new option "-r" is needed to remove those invalid entries in 3pc.conf. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Add building, installation, and packaging support for AIX 5 database extensions. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The Fastrax LBO and extent limits are now dynamically set by calling the SYMAPI for the limits in effect. The various limits are then logged to the directory /usr/openv/netbackup/logs/symlogs. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If there are two libraries (example: library A and library B) configured on the same server. This bug would cause library B to try and behave as library A and possibly fail if library B was not capable of doing what library A does. For example, if library A is capable of doing an "extend and retract" and library B tries to do the same function, it would fail. This is not the case with all libraries; just a few of them. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If a TapeAlert-based cleaning was initiated by ltid or avrd for an ACS, TLH, or an LMF drive, the vmd/DA would never release the drives. Since these robot types clean themselves, we do not need to initiate cleaning. If TapeAlert-based cleaning was initiated by ltid or avrd for non-API SSO robots and no cleaning media was available, or the number of cleanings was 0, the vmd/DA would never release the drives. Additional Notes: Added a touchfile for disabling TapeAlert based cleaning. For unix, this is /usr/openv/volmgr/database/NO_TAPEALERT. For Windows, this is volmgr\database\NO_TAPEALERT. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The date and time fields of the usage statement were not localized. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Some of the Volume Manager debug information has been limited to the verbose condition. This is because in large Volume Manager installations the excess logging caused a performance degradation. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Vault jobs: Cancelled Duplicate job SOMETIMES shows as "Active" A couple of Duplicate Vault Jobs (on Solaris) are cancelled from the Windows box and sometimes from the Solaris box. The Duplicate jobs are cancelled correctly every time, however, sometimes the job incorrectly appears as "Active" in the Activity Monitor, even though it has been cancelled. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: For Fastrax backups and restores large amounts of memory could be used by bpbkar and bpblr if the installation had many Symmetrix striped meta devices. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: If an error occurs during a Fastrax restore, then files being restored might be preallocated but not contain any restored data and have permissions bits set to zero. This fix enables bptm to remove these files after the error is encountered. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: On UNIX clients with a local file system mounted as a subdirectory of a loopback file system (lofs), a normal NetBackup file system backup cannot back up the local file system. For example, assume the following mounted file systems: /local/2 (local mount of /dev/dsk/part2) /opt/document (lofs, looped back to /local/2/opt/document) /opt/document/test (local mount of /dev/dsk/partt) When attempting to backup /opt/document/test, NetBackup will report a successful backup. However, it will not backup the data under /opt/document/test. Workaround: Unmount the loopback file systems before backing up the local file system, or use raw partition (or FlashBackup) to backup the disk partition. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: If an alternate path restore was specified thru the GUI, then the path that bptm supplies to bpblr is the original path not the alternate path. This causes a failure when attempting to determine the Symmetrix ID initially or when mapping the files to be restored. Workaround: Alternate path restores using the command line work. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The default size for the tape buffer size for TPC backups using hcart was 256K. This exceeds the maximum buffer size supported by some extended copy vendors, causing the backup to fail. Workaround: Use the SIZE_DATA_BUFFERS_TPC file in /usr/openv/netbackup/db/config to set the buffer size to 64k. Additional Notes: This may have some performance impact, but we have not seen any effect in inhouse testing. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Basically, the problem revolves around the way FlashBackup Files file (for example, the ".f" files) are generated in the NetBackup image database. FlashBackup sends directory information and inode information through bpbrm to bpdbm to generate the Files file. For FlashBackup MPX this information was not being processed correctly by bpbrm. Consequently, the ".f" file that was generated was corrupted. As a result the individual file restore feature was broken. The Activity Monitor/Job Details information was incorrect because bpbrm was sending both directory information and inode information to the scheduler for processing by the job monitor daemon. This resulted in twice the number of files counted in the backup than should have been. In addition, the last block of files that were being processed (for example, the number between the default of 500 and the end) was not being processed correctly. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When configuring devices in an HACMP clustered environment, the name of the particular node that NetBackup was running on was being used instead of the cluster name. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The ITC dialog in NetBackup performs certain validations that can either be presented to the user as warnings or errors. In 4.5GA, they were all given as warnings. Changes have been made to make some of the warnings into errors to prevent the user from misconfiguring ITC. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: This are architecture fixes for the Informix patch to fix the requeueing error where the Informix backup job fails with a 134 error. (All NetBackup Clients) -------------------------------------------------------------------------------- Description: Media is unmounted after a restore prior to the media unmount delay interval. For example, the bptm log has entries similar to the following: 10:11:04 [1935] <4> mpx_read_backup: successfully restored 1 of 1 requests, read total of 107892 Kbytes at 7269.448 Kbytes/sec 10:11:04 [1935] <2> read_backup_unmount_delay: waiting 180 seconds before unmounting media after restore 10:11:05 [135] <2> bptm: INITIATING: -U 10:11:05 [135] <2> db_byid: search for media id AA1010 10:11:05 [135] <2> db_byid: AA1010 found at offset 6 10:11:05 [135] <2> tpunmount_all: tpunmount'ing /usr/openv/netbackup/db/media/tpreq/AA1010 10:11:05 [135] <2> bptm: EXITING with status 0 <---------- (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Under some circumstance a less than optimal drive was being selected for a Fastrax backup/restore. The problem would show up when multi-streaming or after all virtual connections for the drives had been established. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: An import of a Fastrax tape thru the GUI failed since there is no way to specify that it is an import of a Fastrax tape. The log entry in the bptm log follows: io_read_block: read error on media id XXXXXX drive index 0 reading header block, Error 0 Workaround: Import using the command line works properly since there is a parameter provided to specify the backup copy type. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: NDMP backup fails. The failure occurs when the backup hits the end of the tape just as the backup is completing. This is a rare event, but it can happen. The order of events (as seen in the NDMP log) are: - Data side sends NDMP_NOTIFY_DATA_HALTED, reason SUCCESSFUL - Mover side sends NDMP_NOTIFY_MOVER_PAUSED reason EOM - After 5 minutes NetBackup times out waiting for NDMP_NOTIFY_MOVER_HALTED - Backup errors off A subsequent backup of the same directories may very well succeed. There are several reasons for this. - The files being backed up may have changed, causing the end of media to occur at a slightly earlier or later time. - The tape drive might detect end of media at a slightly different point. - A different media might be selected for the backup. Workaround: Since this error occurs only when the end of media happens at just the right moment, anything that would change when the end of media happens would fix this problem. Some suggestions: - Backup a different directory first. - Cause a different media to be selected. This can be done by freezing the media that the error occurs on. You can then unfreeze the media after the backup completes so the media can be used again. - Modify the directories being backed up. (This may happen naturally as applications are running and changing files.) - Sometimes just re-running the backup will work since the end of media may occur at a different point because of the tape drive or the data has changed. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: NDMP restore after backup of two or more directories fails. The failure might occur in different ways depending on the conditions and the timing of the NDMP events. The most common way for this to fail would be when files from two or more of the backup images (the directories originally backed up) are recovered. The first part will work OK, but the restore fails when attempting to restore files from the second image. Another common way for this to fail is to fail on the restore of the files in the first image. The bptm log would show either the ndmp_mover_set_window, the ndmp_mover_listen, or ndmp_mover_continue messages failing with status 19 (NDMP_ILLEGAL_STATE_ERR). Workaround: Restore files from one backup image at a time. (Each directory originally backed up is a backup image.) The files will be restored OK even though NetBackup may report an error. This is because the "error" in this case is caused by NetBackup attempting to send messages to continue the restore after the restore has actually completed successfully. (Thus the illegal state error.) (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Meaningless data appeared in the client progress log when a restored failed or was aborted. The file names of the unrestored files are UTF8 encoded Unicode and the viewer was not decoding them so they were sometimes unreadable. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When performing a restore on Windows NT/2000/XP and the names of the files/folders being restored contain non-ascii characters, there are some messages that get logged to the progress log that contain a file name. When the file name gets displayed, it is inaccurate. These inaccurate names have been seen when: - The file cannot be restored - The file is being renamed - The file is not being restored because existing files are being kept (All NetBackup Servers) -------------------------------------------------------------------------------- Description: During a restore, processes that are killed can cause bprd to core dump. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: In certain circumstances, ltid can hang for as long as five minutes at startup. This problem has occurred on Windows servers and has potential to happen on all server types. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: In a frozen image multiple data stream backup, if one of the streams failed with a 134 error, it would be retried immediately. Before the retry begins, it needs to wait until all other data streams terminate. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If a class with multiple clients is duplicated and the type changes to vault, the scheduler will attempt to start vault one time for each client. All but one will fail. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Tape reserves were not maintained when the extended copy commands were sent to the tape lun, and the i= keyword in mover.conf did not set up the Third-party Reserve correctly. Additional Notes: This change adds additional keywords to each entry in mover.conf. The default operation is to maintain the tape reserve when sending the extended copy command to the tape lun, and to drop it when sending it to a nontape lun if the i= keyword is not present. A "dr" keyword has been added to dictate dropping the reserve for a tape lun if the vendor does not support sending the extended copy command without detecting a tape reservation. A "hr" keyword has been added to allow maintaining the tape reserve for nontape luns if the vendor allows an extended copy command to control luns without detecting a reservation conflict. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: TLM eject was exiting an eject operation after 30 minutes without setting the media left to be ejected to "Eject Aborted" status. The media will now be updated to the proper status and the eject timeout has been extended to one week instead of 30 minutes. In addition, when ejecting to a full media access port(map), the user would not be notified to remove the media already present in the map. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The possibility exists when stopping ltid that the termination processing for Fastrax tape drives, such as Fastrax cleanup operation and rewinding of the tape, may not have completed. This can then cause a problem in ltid initialization when attempting to initialize these Fastrax drives. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If a calendar-based, cumulative, incremental schedule is used with multiple data streams, the schedule will run repeatedly. Workaround: There are three potential work-arounds for this problem. 1. Uncheck multiple data streams in the class 2. Change the schedule to differential incremental 3. Change the schedule to frequency based. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: This corrects the wording of several Vault error-code and troubleshooting messages. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: This corrects a problem with NDMP restores where process bpbrm would hang indefinitely if bp.conf contains MEDIA_UNMOUNT_DELAY = 0. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: In some cases, shutdown of the server could hang when attempting to stop the nbdbd service. A console message would say the automounter is unavailable. (All NetBackup Servers) ================================================================================ ============= Java list ================================================================================ Description: The Vault Java GUI enabled a user to configure the "Offsite Volume Group" as the "Source Volume Group". This is an invalid configuration. Description: If the user makes any changes to Volume pools, these changes will not appear in the Vault Java GUI unless the user refreshes the Vault Java GUI. Description: The Media Management dialog was not performing a refresh after rescanning barcodes. Workaround: Press the 'refresh' button after rescan barcodes dialog is closed. Description: The Delete Volume dialog did not always report error messages when multiple volumes were deleted and some could not be deleted. Description: The location of the popup menu in Device/Topology was not correct. If a user clicked the mouse too close to the right or bottom edge of the screen, the popup menu will be placed such that it overlaps the current location of the mouse pointer. If the pointer happens to fall over an enabled menu item, the user may unintentionally select a menu item. Description: The only time the Recover Limits wizard page should appear is if it is a whole database recovery. The RMAN syntax does not allow PIT at the tablespace or datafile level. Description: Within the Backup, Archive, and Restore client, if files were marked or unmarked in the "Search Backups" dialog, the files in the table may not reflect this marking properly. Description: A non-root user authorized for administration cannot perform the vault administrative functions using the Vault Java GUI. Description: When the Java GUI is logged into an HP-UX system and the user tries to save a vault profile, the underlying file write request issued by the Java GUI fails with a "Connection (or socket) timed out" failure. Description: In the past, no message dialog was shown when an error occurred on the invocation of the Backup History dialog. Now, in the case where the bprd daemon is not running, invoking the Backup History dialog will result in a user notification that an error has occurred. Description: The Media Summary Report has some rows that are displayed as follows. ACTIVE FULL SUSPENDED FROZEN IMPORTED 0 0 0 9 0 These rows should look like the following example: ACTIVE FULL SUSPENDED FROZEN IMPORTED 0 0 0 9 0 By using fixed width font to show the contents of this Report, the problem is solved. Description: After running a Report try to show/hide some random columns, and then run that report again. Now try to show/hide some columns again. The report that appears now contains some columns with wrong column headers (while column content is proper). This was observed only in few cases and has been corrected. Description: When the Device Monitor is currently showing the selection(s) in the Drives or Pending Requests table, if there is any, the selection remains selected when a user clicks on the Device Monitor tree node. Description: Change the help text for adding items to the file list on the Catalog Backup tab of the Profile dialog in the Vault GUI. The changed text is as follows: "Use the following formats for all paths: servername:/Path (for Unix servers) servername:Drive:\Path (for Windows servers)" Description: The Robot Control Host field is not set correctly (in the xml file) for all robot types. Because of this, the user may face problems while vaulting. Description: A new "Find" dialog was added to Media Management so the user can search for media. This was added to match the Windows "Find" functionality. Description: The error code MAILSLOT_STATUS_TAPE_IN_DRIVE was recently added to multiple TLD/TL8 eject. The NetBackup Administration Console for UNIX was updated to handle this error code properly. Description: The Help button is enabled on the Disk Storage Unit window of the Device wizard, however when you click it, nothing happens. No help window appears. This action generates an exception that is printed to the logs. The exception does not cause any problems and the user can still advance to the next page.) Description: Updated Media Management to clear table selections after a user selects a tree node in the left pane of the NetBackup Administration Console. Description: The "Type of backup" combo box on the Catalog GUI in the NetBackup Administration Console allows text to be entered. This field should not be editable. Description: The Catalog Backup Configuration wizard does not auto-configure the catalog locations for the media servers when the current server is also the one logged into. Description: Multiple accessibility problems exist in the Catalog Configuration Wizard. Description: The text, "Enter host name:", for the Change Server dialog was hardcoded and therefore could not be internationalized. Description: Add the core logic for "Export to File" for the NetBackup Administration Console for UNIX. This is required to provide functionality similar to xbpadm's "Print" and "Print List" capabilities. Description: The device area of the NetBackup Administration Console for UNIX needed to support exporting data to a file. Description: When the load of a node in the tree was interrupted, clicking the node in the tree again did not result in another attempted loading of this node. Also, the resulting contents from the previously selected node remained in the table. Moving to a different node in the tree after interrupting the load of one and then moving back to the original node would result in the loading of the node that was interrupted previously. The node selection is now moved back to the previously selected tree node in the case of an interrupt. This results in the proper corresponding data being shown in the table, as well as reloading of the interrupted node upon its reselection. Description: The following exception occurs when the FW support in NetBackup Java is turned on and a user tries to interrupt a load of data in the Java Backup, Archive and Restore client. Connection to user service via VNETD is unsuccessful - status: 10. ServerInterface:Logon: java.net.ConnectException: Connection to user service via VNETD is unsuccessful - status: 10. ServerInterface:Logon - Initial host:spirea, Current host:spirea, Firewall Env:t rue, MS port:13722, VNETD:13724, m_intPort:0, localPort:0, range use:false java.lang.NullPointerException at vrts.nbu.client.JBP.BRTreeNode.loadData(BRTreeNode.java:796) at vrts.nbu.client.JBP.BRTreeNode$1$LoadWorker.loadData(BRTreeNode.java:160) at vrts.nbu.admin.LoadInProgressMessage$1$LoadWorker.construct(LoadInPro gressMessage.java:362)at vrts.common.utilities.SwingWorkerHack$2.run SwingWorkerHack.java:120)at java.lang.Thread.run(Thread.java:484) Description: Media Management now supports the Exportable interface which provides the ability to save Media Management tables to a file. Description: The Activity Monitor values for job state (Queued, Active, Requeued, Done) in the jobs table and the Job Details dialog are not localizable. This relates to the Activity Monitor values in the NetBackup Administration Console for UNIX. Description: The Motif GUI had the ability to select more than one policy and initiate a manual backup for each. The same functionality has been implemented in the NetBackup Administration Console for UNIX and operates the same as it did in the Motif GUI. Description: The Robot Inventory dialog in the NetBackup Administration Console for UNIX displays the Media ID Generation rules for the host the user originally logged into. Note: Media ID Generation rules are stored in the vm.conf file. For example, if the user logs into machine X and then changes the server to machine Y, the list of Media ID Generation rules will still be from machine X. This happens because Robot Inventory uses the vmupdate command that reads the local vm.conf file (which in this case is on machine X because it is the machine the user originally logged into making it the local machine for all of the Robot Inventory commands). Because of this example, providing and showing the list of Media ID Generation rules than can be used for the vmupdate command will eliminate user confusion. Description: The words on License Key Properties dialog are missing for the Chinese localization. In addition, the Active/Inactive strings were not localized. Description: This is a Japanese location problem only. The problem is that the restore type strings such as "JnBClbLB0111=Normal Backups|N" (and related strings) are being used in two places, one that uses the shortcut key and one that does not. The Restore Type pull-down menu does not display the shortcut keys, and the Actions menu does. This is correct for English, but for localization the mechanism used will not work. The localized string displays the shortcut key by adding a (N) in the following example: JnBClbLB0111=(N)|N Because this key is used in both situations where it uses the shortcut key for Actions, but not for the drop down, the strings in the drop down show up as (N). Having this shortcut key will be confusing to the user in this instance because it will not work. Description: When selecting advanced duplication, and specifying multiple copies to multiple media server, an error message dialog box appears that has confusing text. Description: The bpvault 3.4 product supports robots without media access ports using a special configuration. The Vault 4.5 provides support for robots that do not have media access ports. Description: If a NetBackup media server is known by more than one name, then duplication rules can be configured that will never be used. A media server can have multiple names (for example, H1 and H1.min.ov.com). Vltadm, enables them to be treated them as either the same or different. If these two names (H1 and H1.min.ov.com) are put in the common Alternate Media Server list, then the two media servers are considered the same or the two are considered different. In the first case, two duplicate rules are not allowed to be configured with media servers H1 and H1.min.ov.com because they are treated similarly. However, the second case allows two duplicate rules with media servers H1 and H1.min.ov.com. This provides a lot of flexibility. Description: While changing from simple configuration to advanced configuration in the Duplication tab, the duplication rule configured by default has an invalid media/backup server value. Description: The Write Drives field on the Duplication tab shows an invalid value for a duplication rule that has multiple copies configured. Description: When using Vault, the duplication rule should not allow storage units on multiple media servers. ============================================================== README -- Last modified date: Thursday, August 14, 2003