Patch-ID# 116264-03 Keywords: netbackup 5.0 nb_50_1_m Synopsis: NetBackup 5.0 UNIX server and client fix Date: Apr/27/2004 Install Requirements: None Solaris Release: 7 8 9 SunOS Release: 5.7 5.8 5.9 Unbundled Product: Veritas NetBackup Unbundled Release: 5.0 Xref: Topic: Veritas NetBackup 5.0 Jumbo Patch Relevant Architectures: sparc BugId's fixed with this patch: 5008663 5020450 5022651 5032355 Changes incorporated in this version: 5032355 Patches accumulated and obsoleted by this patch: 116263-01 Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /openv/db/bin/nbdbd /openv/java/allJBP.jar /openv/java/allNB.jar /openv/java/nbCommon.jar /openv/lib/libVbp.so /openv/lib/libVcom.so /openv/lib/libVdb.so /openv/lib/libVnbaz.so /openv/lib/libVnbazST.so /openv/lib/libVnbdb.so /openv/lib/libbasictemplate.so /openv/lib/libcatalog.so /openv/lib/libsfr.so /openv/lib/libxm.so /openv/msg/.conf /openv/netbackup/bin/admincmd/backupdbtrace /openv/netbackup/bin/admincmd/backuptrace /openv/netbackup/bin/admincmd/bpauthorize /openv/netbackup/bin/admincmd/bpbackupdb /openv/netbackup/bin/admincmd/bpclient /openv/netbackup/bin/admincmd/bpdbjobs /openv/netbackup/bin/admincmd/bpduplicate /openv/netbackup/bin/admincmd/bpexpdate /openv/netbackup/bin/admincmd/bpimagelist /openv/netbackup/bin/admincmd/bpimport /openv/netbackup/bin/admincmd/bpnbaz /openv/netbackup/bin/admincmd/bppficorr /openv/netbackup/bin/admincmd/bpplinfo /openv/netbackup/bin/admincmd/bppllist /openv/netbackup/bin/admincmd/bpplsched /openv/netbackup/bin/admincmd/bpplschedrep /openv/netbackup/bin/admincmd/bprecover /openv/netbackup/bin/admincmd/bpschedulerep /openv/netbackup/bin/admincmd/bpverify /openv/netbackup/bin/admincmd/duplicatetrace /openv/netbackup/bin/admincmd/importtrace /openv/netbackup/bin/admincmd/restoretrace /openv/netbackup/bin/admincmd/verifytrace /openv/netbackup/bin/bpbrm /openv/netbackup/bin/bpcoord /openv/netbackup/bin/bpdbm /openv/netbackup/bin/bpdm /openv/netbackup/bin/bpjava-susvc /openv/netbackup/bin/bpjobd /openv/netbackup/bin/bpps /openv/netbackup/bin/bprd /openv/netbackup/bin/bpsched /openv/netbackup/bin/bpsynth /openv/netbackup/bin/bptm /openv/netbackup/bin/cat_convert /openv/netbackup/bin/cluster/cluster_config /openv/netbackup/bin/cluster/vcs/monitor /openv/netbackup/bin/cluster/vcs/offline /openv/netbackup/bin/cluster/vcs/online /openv/netbackup/bin/cluster/vcs/vcs_nbu_config /openv/netbackup/bin/goodies/available_media /openv/netbackup/bin/goodies/bp.kill_all /openv/netbackup/bin/goodies/check_coverage /openv/netbackup/bin/goodies/cleanstats /openv/netbackup/bin/goodies/duplicate_images /openv/netbackup/bin/goodies/fimselector /openv/netbackup/bin/goodies/mail_bp_reports /openv/netbackup/bin/goodies/nbac_cron /openv/netbackup/bin/goodies/nbac_install_helper /openv/netbackup/bin/goodies/nbac_install_helper.pl /openv/netbackup/bin/goodies/netbackup /openv/netbackup/bin/goodies/pltemplates /openv/netbackup/bin/goodies/support/support /openv/netbackup/bin/goodies/support/support_nbac /openv/netbackup/bin/goodies/verify_images /openv/netbackup/bin/index_clients /openv/netbackup/bin/install_bp /openv/netbackup/bin/install_client_files /openv/netbackup/bin/update_clients /openv/netbackup/bin/update_dbclients /openv/netbackup/client/Solaris/Solaris7/bpbackup /openv/netbackup/client/Solaris/Solaris7/bpbkar /openv/netbackup/client/Solaris/Solaris7/bpcd /openv/netbackup/client/Solaris/Solaris7/bpclntcmd /openv/netbackup/client/Solaris/Solaris7/bpfis /openv/netbackup/client/Solaris/Solaris7/bpjava-msvc /openv/netbackup/client/Solaris/Solaris7/bpjava-usvc /openv/netbackup/client/Solaris/Solaris7/bplist /openv/netbackup/client/Solaris/Solaris7/bpnbat /openv/netbackup/client/Solaris/Solaris7/client_config /openv/netbackup/client/Solaris/Solaris7/cp_to_client /openv/netbackup/client/Solaris/Solaris7/driver/snaplist /openv/netbackup/client/Solaris/Solaris7/fsanalyze /openv/netbackup/client/Solaris/Solaris7/ftp_to_client /openv/netbackup/client/Solaris/Solaris7/install_client /openv/netbackup/client/Solaris/Solaris7/libVnbat.so /openv/netbackup/client/Solaris/Solaris7/libVnbat64.so /openv/netbackup/client/Solaris/Solaris7/libVnbatST.so /openv/netbackup/client/Solaris/Solaris7/libVnbatST64.so /openv/netbackup/client/Solaris/Solaris7/libVxSS_helper.so /openv/netbackup/client/Solaris/Solaris7/libVxSS_helper64.so /openv/netbackup/client/Solaris/Solaris7/move_libs /openv/netbackup/client/Solaris/Solaris7/mtfrd /openv/netbackup/client/Solaris/Solaris7/tar /openv/netbackup/client/Solaris/Solaris7/version /openv/netbackup/client/Solaris/Solaris9/bpbackup /openv/netbackup/client/Solaris/Solaris9/bpbkar /openv/netbackup/client/Solaris/Solaris9/bpcd /openv/netbackup/client/Solaris/Solaris9/bpclntcmd /openv/netbackup/client/Solaris/Solaris9/bpfis /openv/netbackup/client/Solaris/Solaris9/bpjava-msvc /openv/netbackup/client/Solaris/Solaris9/bpjava-usvc /openv/netbackup/client/Solaris/Solaris9/bplist /openv/netbackup/client/Solaris/Solaris9/bpnbat /openv/netbackup/client/Solaris/Solaris9/client_config /openv/netbackup/client/Solaris/Solaris9/cp_to_client /openv/netbackup/client/Solaris/Solaris9/driver/snaplist /openv/netbackup/client/Solaris/Solaris9/fsanalyze /openv/netbackup/client/Solaris/Solaris9/ftp_to_client /openv/netbackup/client/Solaris/Solaris9/install_client /openv/netbackup/client/Solaris/Solaris9/libVnbat.so /openv/netbackup/client/Solaris/Solaris9/libVnbat64.so /openv/netbackup/client/Solaris/Solaris9/libVnbatST.so /openv/netbackup/client/Solaris/Solaris9/libVnbatST64.so /openv/netbackup/client/Solaris/Solaris9/libVxSS_helper.so /openv/netbackup/client/Solaris/Solaris9/libVxSS_helper64.so /openv/netbackup/client/Solaris/Solaris9/move_libs /openv/netbackup/client/Solaris/Solaris9/mtfrd /openv/netbackup/client/Solaris/Solaris9/tar /openv/netbackup/client/Solaris/Solaris9/version /openv/netbackup/client/Solaris/Solaris_x86_7/bpbackup /openv/netbackup/client/Solaris/Solaris_x86_7/bpbkar /openv/netbackup/client/Solaris/Solaris_x86_7/bpcd /openv/netbackup/client/Solaris/Solaris_x86_7/bpclntcmd /openv/netbackup/client/Solaris/Solaris_x86_7/bpjava-msvc /openv/netbackup/client/Solaris/Solaris_x86_7/bpjava-usvc /openv/netbackup/client/Solaris/Solaris_x86_7/bplist /openv/netbackup/client/Solaris/Solaris_x86_7/bpnbat /openv/netbackup/client/Solaris/Solaris_x86_7/client_config /openv/netbackup/client/Solaris/Solaris_x86_7/cp_to_client /openv/netbackup/client/Solaris/Solaris_x86_7/ftp_to_client /openv/netbackup/client/Solaris/Solaris_x86_7/install_client /openv/netbackup/client/Solaris/Solaris_x86_7/libVnbat.so /openv/netbackup/client/Solaris/Solaris_x86_7/libVnbatST.so /openv/netbackup/client/Solaris/Solaris_x86_7/libVxSS_helper.so /openv/netbackup/client/Solaris/Solaris_x86_7/move_libs /openv/netbackup/client/Solaris/Solaris_x86_7/mtfrd /openv/netbackup/client/Solaris/Solaris_x86_7/tar /openv/netbackup/client/Solaris/Solaris_x86_7/version /openv/share/Class_att_defs.txt /openv/share/device_mappings.txt /openv/volmgr/bin/acsd /openv/volmgr/bin/acsssi /openv/volmgr/bin/avrd /openv/volmgr/bin/goodies/vmconf /openv/volmgr/bin/ltid /openv/volmgr/bin/mmcrawl /openv/volmgr/bin/oprd /openv/volmgr/bin/scan /openv/volmgr/bin/tl8cd /openv/volmgr/bin/tl8d /openv/volmgr/bin/tldcd /openv/volmgr/bin/tldd /openv/volmgr/bin/tlhd /openv/volmgr/bin/tlhtest /openv/volmgr/bin/tpautoconf /openv/volmgr/bin/tpclean /openv/volmgr/bin/tpconfig /openv/volmgr/bin/vmadd /openv/volmgr/bin/vmchange /openv/volmgr/bin/vmcheckxxx /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/vmdb_merge /openv/volmgr/bin/vmdelete /openv/volmgr/bin/vmglob /openv/volmgr/bin/vminitlists /openv/volmgr/bin/vmmedia /openv/volmgr/bin/vmoprcmd /openv/volmgr/bin/vmphyinv /openv/volmgr/bin/vmpool /openv/volmgr/bin/vmquery /openv/volmgr/bin/vmrule Problem Description: 5032355 116264-02 needs to be respun (from 116264-02) 5022651 after applying 116264-01 netbackup fails to start (from 116264-01) 5020450 need nbu 5.0 MP1 (from 116263-01) 5008663 need NB_50_S0428 released as Sun patch ============================================ Patch Installation Instructions: ------------------------------------------------------------------------- Refer to the Install.info file within the patch for instructions on using the generic 'patchadd' and 'patchrm' scripts provided with each patch. Any other special or non-generic installation instructions should be described below. ------------------------------------------------------------------------- Special Install Instructions: ------------------------------------------------------------------------- NOTE: For Maintenance Pack installation on a UNIX Cluster Environment: 1) Ensure that prior to installing the maintenance pack, NetBackup is at release level 5.0 and configured to run in a cluster. 2) Freeze the NetBackup group (This will avoid a 'failover' during a patch installation). 3) Install this Maintenance Pack on the inactive node(s) of the cluster (follow steps 1-3 below) 4) Install this Maintenance Pack on the active node of the cluster (follow steps 1-3 below) 5) Unfreeze the NetBackup group. ------------------------------------------------------------------------- The Access Control feature available in NetBackup 5.0 MP1 release has a dependency on the VxSS software that is available on a separate CD free of charge. If you are interested in using the Access Control feature, you must first acquire the VxSS software CD and install the software. The VxSS software CD is labeled as: VERITAS Security Subsystem (VxSS 4.1.2.5) To acquire the VxSS software CD, please contact your local Support Center, phone number can be found at: http://www.sun.com/service/contacting/solution.html. ------------------------------------------------------------------------- As root on the NetBackup Master Server: 1) Stop the NetBackup and Media Manager daemons: /usr/openv/netbackup/bin/goodies/bp.kill_all 2) Install patched binaries via patchadd. 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 Solaris7 Solaris Solaris8 Solaris Solaris9 Solaris Solaris_x86_7 Solaris Solaris_x86_8 Remember to include the master server's type. Note: The /usr/openv/netbackup/bin/update_clients command without any parameters will update all the UNIX clients. Additional Notes: If nonroot users have been given permission to perform NetBackup or Media Manager administration, (NetBackup System Administrator's Guide, Allowing Nonroot Users to Administer NetBackup page 31 and Media Manager Administrator's Guide, Allowing Nonroot Users to Administer Media Manager, page 9), group and file permissions changes will have to be reapplied as installing this patch will reset the group and file permissions to their delivered value. For Solaris servers, this can be done by executing: /usr/openv/netbackup/bin/nonroot_admin ============================================ 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 patch, however, VERITAS strongly recommends the "best practice" of being at the latest patch level. Additional Notes Any additional information regarding this problem or feature. ============= 116264-03 ============= =============================== NetBackup Access Control (NBAC) =============================== The 5.0_M_1 release contains extensive upgrades to the NetBackup Access Control (NBAC) feature. This feature enables NetBackup administrators to protect their NetBackup configuration by enabling NBAC to control and/or restrict access to NetBackup. The following list identifies three factors that NBAC uses to control or restrict access. - Who may access NetBackup: Accomplished by defining users and user groups. - What functions a user group can perform: Accomplished by assigning users to various user groups. - What resources a user group may manage. If you are installing this release to utilize the NBAC capabilities, you will need to obtain the VxSS CD. In addition, if you would like more information about this feature, refer to TechNote 263650 on the VERITAS Support Web site. This TechNote contains such information as: - How to configure and deploy NBAC for the first time - Understanding standard NBAC configurations - Supported platform information specific to NBAC - Known product limitations ============= Server/Client ============= -------------------------------------------------------------------------------- Description: When starting a backup using the -i (immediate) and -L (logging) options, the job does not appear in the bpjobd monitor (Activity Monitor). The ability to use backup progress logging on clients when using the bpbackup -i command, which is currently disallowed by bprd and bpbackup, has been added. In addition, bpbkar is successfully receiving the -L option, indicating that bpsched is passing the log file successfully. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Add an exit 0 after checking for NBAR processes. If NBAR is present but not up, the grep causes bpps to end with a non-zero exit status. GDM, at a minimum, checks bpps' exit status. (All NetBackup Servers: HP RS6000 Solaris) -------------------------------------------------------------------------------- Description: bplist processes paths and interprets '..' and '.' in paths. This does not allow the use of a path such as 'x/./y', which NetWare uses. A change was made to allow '/\./' to be interpreted as '/./'. All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: The scheduler can get socket read failures if the shell script writes error messages to stderr. The bpsched log will have messages like the following: 12:26:41.325 [4427] <2> get_string: buffer space for 5121 bytes, but incoming data needs 1668248940 bytes 12:26:41.325 [4427] <2> get_string: (7) inadequate buffer space for data 12:26:41.325 [4427] <16> readstring: get_string failed: Error 0 (0), incoming data too large for buffer (-1) 12:26:41.325 [4427] <8> read_bpbrm_stderr: readstring failed: socket read failed (23) (All NetBackup Servers) -------------------------------------------------------------------------------- Description: After using the job monitor to terminate a backup, the bpbkar process on the client can sometimes hang in exit processing looking for a status message that was already sent. All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: Imports or verifies with detailed logging can take much longer than without detailed logging. Workaround: Don't request detailed logging. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Restores of remote clients initiated from a NetBackup server with detailed logging can take much longer than restores without detailed logging. Workaround: Don't request detailed logs or initiate the restore from the remote client. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: bptm core dumped when the TPC buffer size was set to 256K, and the backup included a directory with many files of less than 512 bytes. The TPC mover was a Pathlight, which advertises a maximum number of segments per command of 256, but will support over 4096. Workaround: To eliminate this failure, reduce the TPC buffer size to 128K or less. (All NetBackup Servers: HP RS6000 Solaris) -------------------------------------------------------------------------------- Description: Bad characters may appear in the Device Identifier field of the "scan" utility output for some devices. The "scan" utility now displays the correct Device Identifier information. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: An error message that indicates a failure to obtain device target information from the 3pc.conf file is being overwritten by a "device not found" error message, thus making it impossible to detect certain misconfiguration errors. (All NetBackup Servers: HP RS6000 Solaris) -------------------------------------------------------------------------------- Description: The parsing of bp.conf in some of the packaging and install scripts, when looking for SERVER entries, was not restrictive enough and extra entries were being pulled in. The parsing has been corrected. (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: The parsing of bp.conf in some of the packaging and install scripts, when looking for SERVER entries, was not restrictive enough and extra entries were being pulled in. The parsing has been corrected. All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: The bpsched process core dumped and left a child process still running. The remove_from_mpxgrp_activelist() function attempts to free pool information, but the pool pointers are really residue. Changed add_to_active_job_lists () function to initialize the malloc'd structure. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: FlashBackup does not restore VxFS meta data correctly. For example, if a file contains VxFS attributes (such as reserve or fixed extent size), the file restore will fail resulting in a zero length file. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Added functionality to check for and handle errors when converting from char to wchar_t. All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: The Q_CLIENT_FIM_LIST and Q_IMAGE_INCREMENT_RESUME in the header file are equal. Fortunately Q_CLIENT_FIM_LIST is NOT used to query bpdbm. It is only used locally in the source file. To resolve this issue, the Q_CLIENT_FIM_LIST has been reassigned. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: bpdgclone failed when a volume has dco log. online_util log: 09:33:22.155 [27646] <2> onlfi_vfms_logf: INF - make_new_vol: executing /usr/sbin/vxmake -g clone_hdsdg_clone < /var/tmp/DGCLBAAquaGd2 09:33:22.156 [27646] <2> onlfi_vfms_logf: INF - vxvm:vxmake: ERROR: Dco my_test_dco not in configuration 09:33:22.156 [27646] <2> onlfi_vfms_logf: INF - vxvm:vxmake: ERROR: getting associations of : 09:33:22.156 [27646] <2> onlfi_vfms_logf: INF - Bad record name 09:33:22.156 [27646] <2> onlfi_vfms_logf: INF - could not vxmake from input file /var/tmp/DGCLBAAquaGd2 (NetBackup Clients: Solaris ) -------------------------------------------------------------------------------- Description: Problems with barcode errors in exabyte libraries have been fixed. In addition, fixes for cleaning tape recognition in Compaq/DEC rebadges of Overland libraries and Sony CSM serialization are also included. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: In NetBackup 5.0, cluster_config would not start the daemons on a NetBackup media server or after a master server upgrade. This issue has been corrected so that cluster_config does start the daemons. Workaround: The user must start the cluster services manually using the appropriate command for their system. If /usr/openv/netbackup/bin/cluster/.do_templates is present, the user must run this script to configure the NetBackup templates and then delete it on all nodes of the cluster. (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: Changes have been made to use version 3.23.58 of MySQL for nbdbd. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The VCS monitor script would change the value of .NBU_STATE if it detected processes were offline. This resulted in cluster_active occasionally giving an incorrect status and causing failures during upgrades or reinstalls. To resolve this issue, changes were made to the monitor so the .NBU_STATE is not changed. The NBU_STATE is only changed during an online, offline, and clean now. (All NetBackup Servers: HP Linux RS6000 Solaris) -------------------------------------------------------------------------------- Description: NBU 5.0GA incorrectly allows the user to select the 'Use data mover' attribute for Microsoft Windows NT and FlashBackup-Windows policy types for Advanced Client. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: NBAC has required use of FQDN host names in the past. Now host names are accepted as short or long host names and are converted to long host names internally as needed. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If an inline tape copy job starts with multiplexing set to 1, another job with multiplexing set greater that one will attempt to multiplex with the first job. The multiplex setting of 1 on the first job caused the job to run without multiplexing enabled. The second job will fail because it cannot multiplex with the first job. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If a restore fails because of a media mount timeout, bprd may core dump when it finishes processing the restore. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Because of the complex nature of timezone and daylight savings time interaction, the timezone correction factor for daylight savings time was using the wrong value and caused an incorrect check to see if daylight savings time is currently in effect. Changes to the timezone correction macro were made to resolve this issue. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The log analysis utilities (backuptrace, backupdbtrace, importtrace, restoretrace, duplicatetrace, verifytrace) could not be executed by a non- root administartor in an NBAC configuration with NetBackup 5.0 GA. The problem was caused by the install permissions on these scripts. This patch will install these scripts with permissions that will allow them to be executed by a non-root administrator. The non-root administrator must be defined under NBAC. (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: A 134 status error would be displayed as an attempt or retry in the Activity Monitor even though they are not counted as tries. A change has been made to the scheduler to not send an "end_try" to bpjobd when a 134 status error is received. In addition, a message as been added that indicates the job was queued again because of a 134 status error. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: An imported backup of a backup copy other than copy 1 would base the expiration time on the backup time rather than the current time, which would result in the imported backup expiring too early. Workaround: The bpexpdate command may be used to change the expiration of the imported backup. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If the bpschedreq -predict command is executed with a time that is not the current day, the exclude dates will not be taken into account. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Generated a much smaller Synthetic Image than a previous TIR incremental image when the Synthetic image should have been about the same size as the TIR incremental image. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: FlashBackup for Windows does not support backup for cross-mounted volumes. This issue has been resolved and backups for cross-mounted volumes are now supported. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Several database files could be left open under certain rare error conditions. Over a long enough time, the vmd process could run out of file descriptors. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: A suspended restore can be restarted more than once if it takes a while to transition to the active state. Workaround: Even though the state doesn't change in the job monitor, don't try to resume a restore job more than once. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: On servers that do not support xbp, the resource files XNB* were not installed. The effect is not seen on the server, but when pushing client binaries to client platforms (using ftp_to_client) that DO support xbp, this caused an error because the XNB, XNB.dt were not available for a push. Workaround: After installing on a server, run: cp /usr/openv/netbackup/XNB* /usr/openv/netbackup/bin/ Then, push out client bins (such as, rerun ftp_to_client). All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: Use of the DISK keyword to specify that an extended copy command be sent to a disk involved in the backup does not work with HDLM managed disks because the algorithm to convert the disk path to the corresponding sg path does not work for the HDLM device. (All NetBackup Servers: Solaris) -------------------------------------------------------------------------------- Description: Collection of disaster recovery information from Windows clients fails. The symptoms of this problem include: 1) Policy is configured to collect disaster recovery information. 2) Server connections to the client are supposed to use vnetd. 3) A firewall is present between the servers and the client. When the server attempts to connect to the client to collect the disaster recovery information, it will not use vnetd and it will fail. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Auto path correction will down drives that have a valid path, but do not respond to commands. To address this issue, the auto path correction can now down drives that do not have valid paths. In addition, this change enables ltid to start even with missing paths. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: File promotion is a new feature of VxFS4.0 Storage Checkpoint. Using the file promotion feature, a deleted file can be recovered quickly from the the most recent checkpoint. Advanced Client Instant Recovery does not support VxFS file promotion in the 5.0 GA release. Additional Notes: You can turn off file promotion by touching a file /usr/openv/netbackup/DISABLE_VXFS_FILE_PROMOTE. (NetBackup Clients: Solaris Solaris9 ) -------------------------------------------------------------------------------- Description: Added the ACS_CSI_HOSTPORT and ACS_SSI_INET_PORT entries to vm.conf. This allows these variables to be set in the vm.conf and used to start acsssi when a firewall is between the NetBackup server and the ACSLS server. (All UNIX NetBackup Servers) -------------------------------------------------------------------------------- Description: Fix memory leak during tar restore of migrated files. All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: The restore paths are incorrect for NDMP path-based history. The list of files for an NDMP backup image are missing the original backup path. This occurs with path-based file history running NDMP V4. (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris) -------------------------------------------------------------------------------- Description: Enhance bptm to use MEDIA_UNMOUNT_DELAY for duplications to reduce unnecessary unmounts/re-mounts during Vault sessions. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Added support for the following Libraries: - ADIC Pathlight VX - Dell PV-136T and PV-160T - HP E-Series Library - Qualstar RLS-4221 - Quantum SDLT600 - Quantum ValueLdr - Quantum ValueLoader - Sepaton S2100 - Sony CSM Library Serialization In addition, several changes have been added to address serialization, library inventory, and extend/retract issues. The following list identifies the library and the issue that has been corrected. - Dell-PV-136T fixed inventory issue - Library Serialization on Sony CSM library series - Serialization for HP5597A - library inventory issue with Quantum M-Series libraries (missing magazine) - extend/retract issue on ADIC Scalar 1000 (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When automatic path correction is enabled, if the customer has a mix of serialized and unserialized robots, some robotic paths may be incorrectly changed. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When changing the drive type and the robotic residence of a drive, some combinations would yield the error message, "This robot does not support multiple media types." Workaround: To avoid this issue, the user can make the required change in two steps: 1) Change the drive's type. 2) Change the drive's residence. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: For FlashBackup on Windows, individual file restores of compressed files were not restoring the data correctly in all cases. The major problem existed when a single compression frame was split between extents, something that would occur with fragmented disk allocation. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Two issues caused the NDMP dump levels to always be 1. The issues were: 1 - When merging the STREAMS.alt file into the STREAMS file, the dump level of the last backup was over written. This caused incremental backups to repeatedly use dump level 1 instead of incrementing each time. 2 - If there was no previous full backup, the incremental backup dump level did not initialize correctly. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The Java restore interface cannot browse files beyond the mount point for a point-in-time rollback. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The "bpimagelist -l" command option in the NetBackup 5.0 release concatenates the 13th and 14th fields on the FRAG line. These fields are the Tape Allocation Date Timestamp and the Device Written On. For example, in the following example the 13th field on the FRAG line is 11 characters long and is actually the value "1062583209" and the value "0" is concatenated. FRAG 1 1 1856 0 2 12 1 T00000 zrp 65536 0 10625832090 0 *NULL* 1063188009 0 65536 0 0 0 0 0 0 0 Additional Notes: Scripts that use the "bpimagelist -l" output may fail or produce erroneous results. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Drives were being downed each time a system-imposed limit on the value of a semaphore ID was exceeded causing arvd to exit with an "Error in Semaphore Operation" error in /var/adm/message. Workaround: Down the NDMP drives that are not working. (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris) -------------------------------------------------------------------------------- Description: When a synthetic backup is being created, the program bpsynth suspends tape volumes that contain images needed for the synthetic backup. Afterwards, bpsynth unsuspends those volumes. Bpsynth is suspending and unsuspending even when a volume was originally suspended or frozen. The result is that previously frozen or suspended volumes are no longer frozen or suspended after the synthetic backup job completes. To correct this issue, bpsynth does not suspend or suspend tape volumes that were originally suspended or frozen or full. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: FlashBackup, either Unix or Windows, to can now use disk storage units as its backup medium. (All NetBackup Servers: Solaris) -------------------------------------------------------------------------------- Description: The data image, which is created by synthetic backup, will have a default retention level set to two weeks. The retention level that the user has set through the configuration was not used. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Synthetic coordinator failed to contact the bpdm process when it finished its reading task. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When using synthetic backup on a large number of disk fragments from a disk data image, it fails to communicate with the synthetic engine, bpsynth and the coordinator, bpcoord. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: FlashBackup for Windows does not support the backup of cross-mounted volumes and produces no error message. The backup succeeds but there is no catalog information visible for the file system mounted on the junction point. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If a client is down when the scheduler is doing autodiscovery, and the NetBackup Administration Console for Windows attempts to modify a policy, the policy may get deleted. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Performing multiple-map ejects to an ACS robot with more than two LSMs could fail if ADJ_LSM entries are not specified in the vm.conf file on the media servers connected to the robot. The default behavior of assuming the LSMs are interconnected in a line was not working. The workaround of specifying ADJ_LSM entries is no longer required when the LSM physical configuration is interconnected in a line. Workaround: Put ADJ_LSM entries into the vm.conf file on media servers connected to the robot describing the physical interconnections of the LSMs. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: An NDMP backup restore will fail if you do not use set the mount point inode number to 2. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: An Incremental backup, after a synthetic Full Backup, may cause bpdbm to core dump. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: A Synthetic Full backup takes too long to create a backup of more than 20,000,000 files. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: A function call to insert_key_list had parameters that were misplaced. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Running cron and/or jobs with NetBackup access control enabled requires that either the expire date of operating system credentials be lengthened using the VxSS utilities, or that accounts be created in the VERITAS private domain database with renewable credentials. nbac_cron is a new binary that simplifies the process of making unattended scripts NetBackup access control aware. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Updated acsssi to include the firewall support from STK for ACSLS. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The tldcd and tl8cd robotic daemons may not be very resilient to having connections opened and closed quickly with no data. This does not affect Windows NT systems. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The scheduler cancelled suspended jobs prematurely. The Windows Open File Backup does not reuse same snapshot when resuming. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Bpjava* executes (Unix) commands by forking and exec-ing " /bin/sh -c '' ". An anachronistic side effect of executing commands, was to coerce the form of to be: "LC_ALL=; export LC_ALL; /bin/ls -l filename" where the intent was to insure that the command was executed in the correct locale. This (currently) makes sense ONLY when the command is executed from the master server, which is running in its own locale and is oblivious to the locale requested by the Java client. The user server is the ONLY command executed by the master, and the intended locale of the user server is passed as an argument, and immediately set after the server starts, thus rendering the LC_ALL= environment assignment useless. All commands started by the user server will then (naturally) inherit the locale, further rendering the LC_ALL= form superfluous. Ordinarily, this (old) form is harmless at best, and redundant at worse... except for one level of AIX which issues bogus setlocale failures FROM the /bin/sh invocation... and spurious output from executed commands is not welcome by the Java client... so... remove the locale environment variable definition. Historically, it would still be necessary (or an alternate plan devised) if the master actually executed commands, more than the user server. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: Added capability to run bpbackup with both -i and -L options at the same time. In this case, a progress log will be created on each client machine in the policy, as well as on the server running bpbackup. All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: Added capability to run bpbackup with both -i and -L options at the same time. In this case, a progress log will be created on each client machine in the policy, as well as on the server running bpbackup. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When initiating an immediate backup from the NetBackup Administration Console for Windows, a warning is displayed if the policy's "go into effect time" is too close to the present. A query for the time on the server has been added to allow the user interface to determine the time to see if the policy can be initiated or not. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Non-stream in control frozen image jobs were not cancelled correctly when a frozen image failure occurred (bpfis error). This resulted in the non-stream in control jobs to backup the data multiple times. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Wildcards do not work with restores in multibyte character locales. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: NetBackup now uses the following date format when installed on a Japanese operating system: 2004/01/19. This format is consistent with the generally accepted format used in Japan. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When doing Oracle proxy copy, the Database (DB) files are treated as sparse files. When the proxy copy backup is combined with local host or alternate client off host backup, bpbkar reads the entire file to build the spares array. This, for large DB files, can take a long time to finish and cause a performance drop in comparison to a standard backup. (NetBackup Clients: HP Solaris Solaris9 ) -------------------------------------------------------------------------------- Description: Oracle Server free with alt-client does not work if multiplexing is enabled. This change also improves snapshot error handling during snapshot creation and deletion. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If a VxFS file with an extent over 1 terabyte is restored, the restore hangs at the beginning and eventually the server times out. All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: A cancelled Catalog Backup job leaves the media in the drive instead of unloading it and moving it back to its slot. Subsequent use of the drive fails because catalog media remains in the drive. Only a manual operation from the command line is able to move the media back to its slot and make the drive available for further NetBackup operations. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Verifying Network Data Management Protocol drives can fail because the end of media (EOM) marker is not recognized. Commands such as bprecover, when used with NDMP drives, may fail. Workaround: Use a non-NDMP drive. (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris) -------------------------------------------------------------------------------- Description: When a checkpointed job resumes, the Activity Monitor displays a 32-bit integer instead of a 64-bit integer for the block count. The bpsched debug log can contain very large values in its ESTIMATE and ESTIMATE_STR lines. Here is an example: log.102703:13:37:09.617 [11222] <2> readstring: ESTIMATE_STR: buf (ESTIMATE -1 -1 avocadocat_1067283424) backid 136924 files (-1), kb (18446744073709551615) This can happen when "Kilobytes Written" is set to its default value, -1. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Restoring from a FlashBackup backup on an HP-UX master server fails. (All NetBackup Servers: Solaris) -------------------------------------------------------------------------------- Description: The NetBackup-Java Administration Console fails if NetBackup Access Control is used to control access to NetBackup and users who are not administrators try to log into a NetBackup server on a Windows system. Users who are not administrators do not have the appropriate permissions to write to the log directories and files on the Windows system. Workaround: Non-administrator users must have write permission to the NetBackup log directories and files on the Windows system. The workaround is documented in the NetBackup 5.0 Release Notes for UNIX and Windows, "Operational Notes," "NetBackup Java Interfaces," "General Notes," item 5, Windows 2000 NetBackup host access from NetBackup-Java interface as a non-administrator. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: The NetBackup jobs database daemon (bpjobd) may fail when the bpdbjobs command, with the -report and -all_columns options, is used to query the database. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When resuming a suspended backup job with Windows Open File Backup enabled, the resumed backup will not re-use the original backup job's volume snapshots. Instead, if the WOFB Error Control configuration setting was set to Abort on Error, the resumed backup job will abort and a status 156- snapshot error will be encountered. If the WOFB Error Control configuration setting was set to Disable Snapshots & Continue, the resumed backup job will be resumed without any volume snapshots. This behavior is not correct and the resumed backup job should re-use the original, suspended backup job's snapshot volumes if they were successfully created. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: A number of manual steps are required in order to prepare hosts to use NetBackup Access Control and in configurations involving a large number of hosts, and a means of automating some of the preparation would ease the initial configuration process. The script "nbac_install_helper" installed in the goodies directory provides basic support for automating the initial Access Control configuration steps listed in the "Access Management" section of the System Administrator's Guide. An executable version is also provided for installations unable to take advantage of the scripted version. Documentation describing use of the script is provided by "-usage" and "- help" flags, by comments in the source code of the script, and by run-time notices when configuration is attempted. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When resuming a suspended backup job with Windows Open File Backup enabled, the resumed backup will not re-use the original backup job's volume snapshots. Instead, if the WOFB Error Control configuration setting was set to Abort on Error, the resumed backup job will abort and a status 156- snapshot error will be encountered. If the WOFB Error Control configuration setting was set to Disable Snapshots & Continue, the resumed backup job will be resumed without any volume snapshots. This behavior is not correct and the resumed backup job should re-use the original, suspended backup job's snapshot volumes if they were successfully created. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When resuming a suspended backup job with Windows Open File Backup enabled, the resumed backup will not re-use the original backup job's volume snapshots. Instead, if the WOFB Error Control configuration setting was set to Abort on Error, the resumed backup job will abort and a status 156- snapshot error will be encountered. If the WOFB Error Control configuration setting was set to Disable Snapshots & Continue, the resumed backup job will be resumed without any volume snapshots. This behavior is not correct and the resumed backup job should re-use the original, suspended backup job's snapshot volumes if they were successfully created. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When using the Java GUI to initiate drive cleaning, the drive names are truncated after 22 characters. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The NetBackup scheduler may core dump when it prepares to exit if it is trying to determine which storage units are busy. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Corrected numerous situations where a backup job could not be restarted/resumed because the necessary information was not retained. The most visible situations were the storage unit not available (219) errors, but there were a number of other conditions. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Suppose the master server and media server are different machines. Suppose that the media server and client are the same machine so that shared memory backups and restores are normally done. Suppose the master server is configured so that "connect backs" with the media server are done via VNETD. The typical bp.conf entry on the master server would look something like this: CONNECT_OPTIONS = mediax 0 1 2 where "mediax" is the hostname of the media server. The digit "1" signifiies that vnetd style connect backs are used. In this case, restores will fail. Typically, the job will fail with error code 5 and be marked as "incomplete" in the job monitor: Workaround: Don't use vnetd style connect backs with the media server if the media server is a client. All NetBackup Windows Clients All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: Customers using noauth authentication with the windows GUI would not be able to start manual backup jobs if they were not an Administrator on the system running the windows GUI. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: VMD on any volume database host can corrupt the volDB (media database), and may core dump. This is due to an error with the pool database, introduced with NetBackup 5.0. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Restores of Windows paths containing "\" don't work. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Bpdbm failure in SQL agent browse for FI backups (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Scheduler started multiple jobs instead of just one when restarting a job. This situation occurs when multiple multi-copy jobs are submitted for restart/resume. The GUI sends all the selected job IDs, but scheduler needs to perform a many to one mapping of the requests. Filtering is added to scheduler to perform this mapping. Workaround: select only one job of the multi-copy job set when performing a restart/resume (All NetBackup Servers) -------------------------------------------------------------------------------- Description: VxFS file promotion does not support alternate location restore. A check is required for Instant Recovery restore, for alternate location restore, file promotion method needs to be turned off. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Add recognition for the ACS_LTO_200G vm.conf entry. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: email notification of backup status is not being sent for Windows clients. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Multi-stripe SQL RFI backup isn't displayed in SQL image browser. It appears that bpbrm provides XBSA a bad restore list, setting the xbsa_flag to XBSA_DATA_EXTENSION for some objects that do contain data. The case occurs on multi-stripe retrievals, where the first set of objects contain data, the next set contains no data and the third set do contain data. After the second set starts using the XBSA_DATA_EXTENSION (-3), it continues to be used for the third set which do contain data. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Some conditions will cause bpplschedrep to crash when setting last day of the month. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: If a multi-stream Windows backup is suspended or cancelled prior to going "active" (for example: while the snapshot is being taken by stream number one), then it's possible the suspended/cancelled backup can not be resumed/restarted. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Jobs failing with a 134 status were not requeued. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Performing backups using an exclude list with non-fully-qualified path names could cause significantly slower backup performance. All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: tldd/tl8d dumping core when attempting to kill an orphaned child process. Only happens when running NetBackup Media Manager in VERBOSE mode. Workaround: Remove the "VERBOSE" entry from your vm.conf file and do not start ltid using the -v option. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: cancel job vxvm snapshot backup hanging (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Jobs ending with 134 and 59 exit codes were marked as incomplete and cancelled. correct operation would be to retry the job. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Multi-stream & multi-copy jobs fail if all storage units are of type disk Workaround: Use at least one tape when performing multi-copy backups (All NetBackup Servers) -------------------------------------------------------------------------------- Description: The vfm.conf and vfm_master.conf files do not list FlashBackup as a valid policy type as of 5.0. This was supported at 4.5FP3 and our documentation (and developers) state that FlashBackup is supported with VVR at 5.0. However, when 5.0 was shipped FlashBackup was omitted from the VVR fim section. (All NetBackup Servers: HP Solaris) -------------------------------------------------------------------------------- Description: libVnbconf and libVnbatST reported "Text file busy" when the client binaries were being laid down on an AIX machine. This is likely to "someone" making a bpcd request to the media server while the install was occurring. bpinst had been changed in 5.0GA to avoid this issue but it was not expected that we needed to change the other client pushing scripts too. Updated cp_to_client, ftp_to_client, install_client, client_config and move_libs to run slibclean, to put the affected files in *.new and then move them to their real locations. All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: PFI SQL images are not expiring properly (All NetBackup Servers) -------------------------------------------------------------------------------- Description: When the customer submits multiple jobs to a Disk STU with Max Jobs set to 1 all the Submitted jobs go active. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Unable to cancel, resume, or suspend using bpdbjobs (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Resuming a checkpointed backup job resulted in selection of a disk storage unit instead of a tape storage unit. This situation can arise at a site that has a media server with both tape and disk storage units. A resume needs to continue on the proper media. If initially tape, then resume on tape. If initially disk, the resume on disk. Workaround: Don't mix disk storage units and tape storage units on the same media server. (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Cannot resume Windows multi-streamed backup jobs after error 219 (storage unit not available). (All NetBackup Servers) -------------------------------------------------------------------------------- Description: Running backups using TIR with Move Detection can leave a hung bpbkar process when any errors occur during the job. All NetBackup Unix Clients -------------------------------------------------------------------------------- Description: Synthetic Backup image is bad and will not restore. When extent ends as fragments ends, synthetic engine didn't handle it well. Additional data is copied and causing catalog mismatch with image. (All NetBackup Servers) ================================================================================ ============= Java ============= Description: The storage unit group label would allow the user to input invalid characters, including spaces that would cause the group to be named incorrectly. This could also add nonexistent storage units to the group. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: Validation changes were made to ensure that a user cannot enter invalid characters in the storage unit label field. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: When a user attempts to change a storage unit on a media server that is different from the master server, the incorrect media server name is shown on the dialog. There is no way to change the media server name to the correct one, and if the user clicks OK, the storage unit is saved with an incorrect media server making it unusable. The only way to change this is to delete the storage unit and re-create it. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: In the case where there is a master server with no devices, and a media server with devices configured, the user cannot create a media manager storage unit using the new storage unit dialog. The drop-down box has a storage device listed, but the fields that list the details for the storage device, such as the robot number, are all blank. Workaround: Configuring the storage unit through the device wizard works correctly, as does bpstuadd. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: If the user had previously sorted on a number field that could be blank for some of the storage units, such as MAX_MPX, the next time that the storage unit node is clicked there is a traceback and the storage unit pane will not appear. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: When trying to create an NDMP storage unit, the storage device fields are not populated correctly on the new storage unit dialog. Workaround: Using bpstuadd works correctly. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: The NetBackup-Java Administration Console was unable to administer on a Windows machine because it had constructed command lines with a single quote. Windows machines require a double quote. Workaround: Command line (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: The containers configuration is visible in the Vault Dialog, in case the Vault interface is logged into a pre-NetBackup 5.0 master server. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: If there is a machine that has multiple name/IP address pairs configured on it, the storage unit GUI will only allow the customer to configure a Media storage unit type on the name/IP address that the devices were configured on. The only storage unit type allowed on the other name/IP address combinations are disk type. This does not allow customers to back up two or more networks with the same media server. Workaround: The customer can configure the storage units through the command line. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: With the NetBackup-Java Administration Console, if you try to add a VxSS network (Host Properties > Access Control > VxSS tab) that has a zero or 255 in the first or second octet (for example, 0.1.1.1, 1.0.1.1, 255.1.1.1, 1.255.1.1), you cannot edit the mask details (they remain inactive). (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: Storage unit GUI only sees the first robot in the list when trying to add a new Storage Unit. If attempting to change an existing storage unit, the use gets an error message stating that the storage unit no longer exists. Workaround: Using the command line to configure and change storage units works correctly. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: For pure media servers, incorrect NBAC-related information is presented in: Properties->Access Control->Authorization Service(TAB) The text indicates that specifying an Authorization Service is optional on an NBAC-enabled media server. In fact, it is mandatory for the correct functioning of an NBAC-enabled media server. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: Adjustments for daylight savings time for various policy data was not being calculated properly. It did not take into account the date when determining if in daylight savings time of the year. Workaround: There is a work around by unselecting "Use daylight savings time" in the adjust time zone dialog box during non-daylight months, but check it for daylight months. (All NetBackup Java GUI capable NetBackup servers and clients) -------------------------------------------------------------------------------- Description: JAVA activity monitor - job overview doesn't show paths backed up. (All NetBackup Java GUI capable NetBackup servers and clients) ================================================================================ ============= 116263-01 ============= Description: VMD on any volume database host can corrupt the volDB (media database), and may core dump. This is due to an error with the pool database, introduced with NetBackup 5.0. (All NetBackup Servers) ftp://ftp.support.veritas.com/pub/support/products/NetBackup_DataCenter/261792.pdf ================================================================================ README -- Last modified date: Tuesday, April 27, 2004