Maintenance Pack NB_60_5_M.hpia64.tar provides fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 on Itanium 64bit HP-UX servers. NetBackup UNIX Add-on products, Database Agents and Java GUI have separate Maintenance Packs.
| Article:TECH52949 | | | Created: 2007-01-03 | | | Updated: 2007-01-04 | | | Article URL http://www.symantec.com/docs/TECH52949 |
Problem
Maintenance Pack NB_60_5_M.hpia64.tar provides fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 on Itanium 64bit HP-UX servers. NetBackup UNIX Add-on products, Database Agents and Java GUI have separate Maintenance Packs.
Solution
NB 6.0GA Pack NB_60_5_M
README
July 20, 2007
Requirement: NB_CLT_60_5_M
Corequirement: NB_BMR_60_5_M
Directives: NBDB_Upgrade NBDB_Recover
================================================================================
This Maintenance Pack provides fixes for Veritas NetBackup (tm) UNIX servers.
NetBackup UNIX Add-on products, Database Agents, and the Java Interface have
separate Maintenance Packs.
The UNIX CLT pack, which is required to be installed with this server pack,
contains a full replacement of all client binaries for all platforms. The local
CLT binaries for this server may require as much as 50MB of free space in the
/usr partition to install, depending on platform. If client binaries are being
loaded on a server to be pushed to clients, as much as 400MB of free space may
be required in the /usr partition.
On AIX, installing this UNIX server pack requires more than 1.2GB of free space
in the /usr partition. For more information, please refer to the following
TechNote:
http://entsupport.symantec.com/docs/280824
================================================================================
=================
PACK DEPENDENCIES
=================
-- NB_CLT_60_5_M_<6 digit number>.tar must be installed before this
Maintenance Pack is installed.
-- Only if Bare Metal Restore is installed,
NB_BMR_60_5_<6 digit number>.<platform>.tar must be installed after
this Maintenance Pack is installed.
-- Installation of this Maintenance Pack requires version 1.33.10.14
of Vrts_pack.install script.
-- This Maintenance Pack contains runtime updates to Veritas Private
Branch Exchange (PBX). If you did not install PBX from a NetBackup
6.0 media kit (GA or 6.0MP4), you may have an older version of PBX
from another Veritas Product. This Maintenance Pack requires that
you have a minimum PBX level of 1.2.2.41. If you have an older version,
you must install 1.2.2.41 from a NetBackup 6.0 media kit. You can
determine your PBX version from the /opt/VRTSpbx/build_version
file. Newer versions are compatible with this Maintenance Pack.
-- Deliverables for the agents or options such as DB2, Oracle, Veritas
Storage Migrator (tm) (VSM) do not always change between patches and
could result in a patch not being delivered. When upgrading or patching
client software, any agent software must be upgraded or patched to the
latest or matching level at the same time as the client software.
-- Added support for multiple ACSLS servers to Windows. This requires
all Windows ACS customers upgrade to SUN/STK Libattach version 1.4.1.
I. PRIMARY MAINTENANCE PACK UPDATES
II. DOWNLOAD INSTRUCTIONS
III. KNOWN ISSUES
IV. INSTALLATION INSTRUCTIONS
V. UNINSTALL INSTRUCTIONS
VI. DESCRIPTION OF PROBLEMS FIXED
Current Pack
NB_60_5_M
Pack History
NB_60_4_M
NB_60_3_M
NB_60_2_M
NB_60_1_M
--------------------------------------------------------------------------------
The following information describes the upgrade and downgrade rules or scenarios
that apply to this maintenance pack.
- Upgrade scenarios:
The NetBackup 6.0 MP5 maintenance pack install:
- Can be applied on top of NetBackup 6.0 GA or any 6.0 MPx (prior to MP5).
- Cannot be applied directly to a NetBackup 5.x system. You must install
NetBackup 6.0 GA first.
- Cannot be applied directly to a NetBackup 6.0 MP5 Beta system. (The
Beta version of NetBackup must be uninstalled first.)
- Downgrade scenarios:
If the NetBackup 6.0 MP5 maintenance pack is uninstalled, you will roll
back to the version you had previously installed prior to installing
this maintenance pack, (such as 6.0 GA or 6.0 MPx).
====================================
I. PRIMARY MAINTENANCE PACK UPDATES
====================================
This section identifies the primary changes, maintenance updates, and
enhancements that are contained in this maintenance pack.
- This maintenance pack contains the following software upgrades:
- JRE 1.4.0.2v, which adds many security fixes for JAVA
- Sun Libattach version 1.4.2 for ACS robotics
- Veritas Unified Logging (VxUL) to 1.3.7.2
- All SIG components have been added and/or upgraded in this release:
- VxUL
- VxPBX
- VxPSP
- VxAT and VxAZ
- VxSched
- The following database proliferations and enhancements have been added
to this pack:
- Added NetBackup for DB2 support (DB2 v9) on 64-bit x86 Windows
operating systems.
- Added Oracle support for Windows 2003 x64. (Oracle 10gR2 for Windows x64)
- Providing x64 (AMD64/EM64T) support for SAP on the x64 Windows client.
- Added support for the HP-UX IA-64 platform to the Sybase package
(HP-UX 11.23 IA-64 - Sybase 12.5).
- With this maintenance pack, you can now compress Oracle and MSSQL
dataBases for backup.
- Provide the ability to restart a single failed MSSQL DB backup without
having to restart a full backup.
- Added new device and library support for the following:
- ACSLS - Titanium T1A, T9840C/D, DLT-S4
- New device supported for WORM
- New media and drive type for LTO4
- New library support - Panasonic/Matsushita AJ-CM100 Library
- There are many customers today who have multiple data centers and move
backup data between the centers by shipping backup images and copying or
replicating the image database. This feature removes one of their most
problematic steps for retreiving the data, changing copy number. They use
this data for both Data Recovery (DR) and production.
As more of users employ DR plans and now practice DR drills, the number
of users requiring the ability to restore from a non-primary copy at
their DR site is rapidly increasing.
DESCRIPTION:
Add a new option to bprestore:
bprestore -copy X
The copy number will need to be passed to bprd, so a new protocol will
need to be defined.
- The following enhancements have been made to Flashbackup:
- Support of up to 16 Terabytes.
- Support for Instant Recovery
- NetApp has a ShadowTape capability in their NearStore VTL. When virtual
media is ejected, NetApp makes a copy to a physical tape drive. However,
instead of deleting the image from their VTL, the copy is "hidden" from
NetBackup. A script has been added that will notify the appliance that
there is a request to restore from the ejected (hidden)media and will
mount the media on the VTL instead of the physical media.
- Support has been added to allow fail over to NearStore storage units to
a different NetApp filer that had been mirrored using NetApp's Volume Snap
Mirror technology.
- The new Single Instance Store (SIS) feature in Windows 2003 R2 Storage
Server extends SIS functionality to non-Remote Installation Service (RIS)
systems and multiple volumes. Changes contained in the pack ensures that
NetBackup protects RIS systems as well as the "first" SIS volume encountered
during backup.
- Changes have been added that allow Instant Recovery of Windows FlashBackup
using "Retain snapshots for Instant Recovery" on a policy.
- If a backup has terminated and if you do not want to repeat a complete
backup again, you can use the new command, BRBACKUP option -f / -fill. The
BRBACKUP command automatically determines the files that are still to be
backed up. If BRBACKUP is run with the -f/-fill option and the log name of
the failed job, it automatically checks which files were backed up
successfully and which failed and then starts a new job only for files for
which last backup failed.
- A new touch file has been added that enables you keep a TIR information
files longer than 10 days (<install path>/netbackup/TIR_INFO_KEEP_DAYS)
- An enhanced MFC VxLogView application enables you to create views of both
legacy and VxUL logs for Windows x86 systems. This application is located
in the goodies directory as, -lv.exe.
- In the PureDisk web user interface, a policy can now be created or a run
once job can now be executed to export the backup data in chosen data
selections to NetBackup storage. Once the data is exported into NetBackup
it will be treated like a "normal" NetBackup image and will be restored
like a regular file.
NOTE: Symantec recommends that you refer to the NetBackup 6.0 Operating System
Compatibility Matrix for the latest information regarding supported
features:
http://entsupport.symantec.com/menu_ddProduct_NBUESVR_view_CL.htm
=========================
II. DOWNLOAD INSTRUCTIONS
=========================
1) Download the NB_CLT_60_5_M_<6 digit number>.tar and
NB_60_5_M_<6 digit number>.<server>.tar files into the
/tmp directory,
where <6 digit number> is an internal tracking identifier
where <server> is alpha_5, hp_ux, hpia64,linux, linux64, rs6000, solaris
NOTE: NB_CLT_60_5_M_<6 digit number>.tar has the client binaries and
NB_60_5_M_<6 digit number>.<server>.tar has the server binaries and BOTH
must be installed.
NOTE: Only if Bare Metal Restore is installed, download and extract the
NB_BMR_60_5_M_<6 digit number>.<platform>.tar into the /tmp directory
and download and extract the NB_BBS_60_5_M_<6 digit number>.<platform>.tar
into the /tmp directory.
2) Extract the NB_CLT_60_5_M_<6 digit number>.tar and the
NB_60_5_M_<6 digit number>.<server>.tar files.
tar xvf NB_CLT_60_5_M_<6 digit number>.tar
tar xvf NB_60_5_M_<6 digit number>.<server>.tar
NB_60_5_M will create the files:
VrtsNB_60_5_M.README
VrtsNB_60_5_M.<server>.tar.Z
VrtsNB_60_5_M.preinstall
VrtsNB_60_5_M.preuninstall
VrtsNB_60_5_M.postinstall
VrtsNB_60_5_M.postuninstall
Vrts_pack.install
NB_CLT_60_5_M will create the files:
VrtsNB_CLT_60_5_M.README
VrtsNB_CLT_60_5_M.tar.Z
VrtsNB_CLT_60_5_M.preinstall
VrtsNB_CLT_60_5_M.postinstall
VrtsNB_CLT_60_5_M.postuninstall
Vrts_pack.install
==================
III. KNOWN ISSUES
==================
- The Veritas Private Branch Exchange (PBX) software is installed along with
Veritas NetBackup (tm) 6.x. By default, PBX logs messages to the system log
/var/adm/messages or /var/adm/syslog. This can cause additional system
logging that the system administrator may not desire. The messages written
to the system logs contain the same informational and warning messages that
are written to the PBX logs. For more information about this issue or
informaiton on how to disable the option, refer to the following TechNote on
the Symantec Support Web site.
http://support.veritas.com/docs/280746
- Changes were made to the Vault Operator Permissions. The Vault Operator
permissions are as follows:
- Host Properties permissions:
Browse and Read
- Job permissions:
Browse, Read, Suspend, Resume, Cancel, Delete, Restart, and New
- VolumeGroup permissions:
Browse, Read, New, and Delete
- VolumePool permissions:
Browse and Read
- DevHost permissions:
Browse and Read
- Media permissions:
Browse, Read, New, Delete, Eject, Move, UpdateBars, Assign, Deassign,
UpdateDatabase, and Expire
- Report permissions:
Browse and Read
- Robot permissions:
Browse, Read, Inventory, New, and Delete
- On all platforms, if the server pack install fails for any reason after the
Client pack has completed, be sure not to restart daemons before
retrying the pack installation.
- Reminder: Synthetics is not supported on Tru64 platforms.
- The NetBackup 6.0 Commands document contains some incorrect information for
the bplist command. The following accurately explains this command.
The bplist command shows a list of previously archived or backed up files
according to the options that you specify. You can choose the file or
directory and the time period that you want the listing to cover.
Directories can be recursively displayed to a specified depth.
The bplist command shows only the files that you have read access to. It
lists the files only if a user backup is performed by the user owning the
files (that is, an administrator account). A non-administrator or backup
operator cannot bplist the files. You also must own or have read access to
all directories in the file paths. You can list files that were backed up
or archived by another client only if you are validated to do so by the
NetBackup administrator.
If you create the following directory /usr/openv/netbackup/logs/bplist/
with public-write access, bplist creates an debug log file in this
directory that you can use for troubleshooting. The output of bplist goes
to standard output.
Issues that are associated with an ETrack number:
-------------------------------------------------
ET1018914 Discrepancy in Windows and UNIX Activity Monitor for an NetBackup
Access Control (NBAC) Vault Operator (vltop) user group.
Changes have been to the NBAC Vault_operator user group to ensure
proper functionality of the Activity Monitor for the Windows and
UNIX platforms.
=============================
IV. INSTALLATION INSTRUCTIONS
=============================
** The content of this online Readme supersedes the information in the Readme
contained in the download. **
NOTE: Click on the "Download Now" link, near the bottom of this document
prior to running the following installation procedure for this pack.
Before installing this maintenance pack, please review the following items:
- Symantec recommends that you perform catalog backups before and after you
apply this maintenance pack.
- If you are planning to install this Maintenance Pack as a part of an
upgrade from a 5.x release then it is important that you understand that the
existing NetBackup databases must be in a consistent state prior to beginning
the upgrade. Information and tools to assist you in determining the current
state of your database, as well as instructions to help you address any
inconsistencies that you might discover can be viewed on the NetBackup Upgrade
Portal, a part of the Symantec NetBackup Support Web site.
http://www.symantec.com/enterprise/support/overview.jsp?pid=15143
- If you are upgrading from 5.x to 6.0, you must install this Maintenance Pack
before you run nbpushdata. Failure to install this Maintenance Pack first
will result in a failed upgrade.
- On AIX, do not use a NetBackup GUI running on any other host to monitor the
NetBackup jobs/processes/daemons/devices on the host being patched during the
installation. On AIX this may cause text busy errors to occur during the
installation. The safest approach is to not have any GUIs running on remote
systems which are accessing an AIX host during pack application.
For Maintenance Pack installation on a UNIX Cluster Environment:
--------------------------------------------------------------------------------
1) Before you install this Maintenance Pack, make sure that NetBackup is at
release level 6.0 and configured to run in a cluster.
2) Freeze the NetBackup group. (By freezing the group, you will prevent a
'failover' from occurring during a patch installation).
3) Install this Maintenance Pack on the inactive node(s) of the cluster
(perform steps 1 through 3 below).
IMPORTANT: If you are using HP Service Guard and upgrading from a
pre-NetBackup 6.0 MP4 version, you must complete the installation of
this pack to the inactive node(s), and then copy the following file from
an inactive node to the active node before beginning the pack install on
the active node:
/usr/openv/netbackup/bin/cluster/util/monitor
4) Install this Maintenance Pack on the active node of the cluster (perform
steps listed below).
5) If the cluster is in a faulted state, clear the fault.
6) Unfreeze the NetBackup group.
--------------------------------------------------------------------------------
As root on the NetBackup Master Server:
1) Close the NetBackup user interfaces.
- Make sure the NetBackup server has no active jobs running (for example,
backups, restores, or duplications).
- If a database agent is being used, such as Oracle, ensure that the database
services are stopped.
2) Install NB_60_5_M and NB_CLT_60_5_M Maintenance Pack binaries.
cd /tmp
/bin/sh Vrts_pack.install
NOTE: Selecting the server Maintenance Pack will automatically install the
client maintenance pack if the client (CLT) .Z file and the README exist in
the installation directory. The server install will fail if the (CLT)
.Z file and the README are not present and the CLT pack has not been
previously installed. The client maintenance pack will NOT be installed
automatically during a reinstall of the server maintenance pack.
3) The Vrts_pack.install script will prompt you to restart daemons.
Otherwise, after the pack installation has completed, run:
/usr/openv/netbackup/bin/goodies/netbackup start
4) The pack install logs can be found in /usr/openv/pack/pack.history once the
installation is complete.
NOTE: Again, Symantec recommends that you perform catalog backups after you
have applied this maintenance pack.
=========================
V. UNINSTALL INSTRUCTIONS
=========================
Note: This will ONLY uninstall the Maintenance Pack from your local machine.
1) Close the NetBackup user interfaces.
- Make sure the NetBackup server has no active jobs running (for example,
backups, restores, or duplications).
- If a database agent is being used, such as Oracle, ensure that the database
services are stopped.
2) Change the directory to the patch save directory.
Substitute the pack name for ${PACK} in the following command:
cd /usr/openv/pack/${PACK}/save
3) Run the un-install script:
./Vrts_pack.uninstall
4) Verify that the pack uninstalled successfully by checking:
/usr/openv/pack/pack.history.
5) If necessary, restart the NetBackup and Media Manager daemons:
/usr/openv/netbackup/bin/goodies/netbackup start
=================================
VI. DESCRIPTION OF PROBLEMS FIXED
=================================
The following are descriptions of the problems fixed.
Please read the entire document before installing.
README Conventions:
Description
Describes a particular problem contained in this 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, Symantec strongly recommends
the "best practice" of being at the latest available patch level.
Additional Notes
Any additional information regarding a problem is included.
=============
Current pack
=============
================================================================================
Etrack Incident = ET644656
Description:
Backups to FSE-enabled Nearstore storage units require TIR to be enabled on
the policy. A change was made to enforce this requirement at run time.
--------------------------------------------------------------------------------
Etrack Incident = ET809090
Description:
If you were using vxlogview along with options –d and –t, vxlogview should
have accepted these options in any order, but it did not. The –d option
displays debug messages, and the –t option displays the most recent
messages. These are not related options, however, vxlogview did not honor
the –t option if it was listed after the –d option. A change was made to
correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET828552
Description:
Changes were made to this maintenance pack to update the PBX and ICSCO pbx
merge modules.
--------------------------------------------------------------------------------
Etrack Incident = ET605200
Description:
UNIX domain socket files with path names of the form /tmp/vnet*
were periodically created on UNIX/Linux NetBackup systems. Most
of these files were only needed for a few minutes and were quickly
deleted. If NetBackup processes terminate abnormally before the
/tmp/vnet* file can be deleted, then these files could accumulate
on the user's system.
This patch periodically deletes old (more than one hour) /tmp/vnet* UNIX
domain socket files.
Previously the Java server (bpjava) would also use UNIX domain socket file
paths of the form /tmp/vnet*. Since these files often need to exist for
several hours, the automated cleanup could cause problems. In this patch,
the form of the bpjava UNIX domain socket file path names has changed to
/tmp/jbp*.
--------------------------------------------------------------------------------
Etrack Incident = ET861571
Description:
Under certain circumstances, bpcd and vnetd services would be
put into maintenance mode on solaris10 systems. Changes were
made to disable/enable these services to make sure they respond.
--------------------------------------------------------------------------------
Etrack Incident = ET861550
Description:
If the NBDB database is not created properly during installation, the
install continues, however the user may not understand that there was
an issue creating the database. As a result, the user may encounter
errors in the command line and the user interfaces.
In addition, if during a patch installation that nbnd_upgrade fails,
the database winds up with the incorrect version. Again, nbemm will
not start because of the version mismatch.
Changes have been made so that the install will fail if the database
cannot be created or upgraded and installation warnings will be logged
in a new logging directory for nbnd commands. The new directories are:
UNIX: /usr/openv/netbackup/logs/nbdb
Windows: InstallPath\NetBackup\logs\nbdb
--------------------------------------------------------------------------------
Etrack Incident = ET862411
Description:
Made a change to unload tapes in a more timely manner on back-level media
Servers (for example, NetBackup 5.x).
--------------------------------------------------------------------------------
Etrack Incident = ET862341
Description:
Added support for 64-bit Linux on Power client.
--------------------------------------------------------------------------------
Etrack Incident = ET862518
Description:
Changes were made to fix potential memory leaks, while fetching pending
requests from the NetBackup Resource Broker.
--------------------------------------------------------------------------------
Etrack Incident = ET862534
Description:
Calls to emmlib_GetStorageUnitHosts no longer result in segmentation
violations.
--------------------------------------------------------------------------------
Etrack Incident = ET862464
Associated Primary Etrack = ET791864
Description:
Changes were added that prevent bpsynth from hanging on patched, Solaris 10
systems.
--------------------------------------------------------------------------------
Etrack Incident = ET862606
Description:
Changes have been made to ensure that all Chinese messages that are suppose
to appear in the Bare Metal Restore (BMR) command line interface (CLI)
output appear, no matter what locale is used.
--------------------------------------------------------------------------------
Etrack Incident = ET863136
Associated Primary Etrack = ET863127
Description:
On a busy UNIX NetBackup server, you may encounter defunct
bpcompatd processes that may appear at any time. These defunct
processes will eventually be cleaned up, but it might some time.
Workaround:
To avoid this issue, periodically, stop and restart bpcompatd:
/usr/openv/netbackup/bin/bpcompatd -terminate
/usr/openv/netbackup/bin/bpcompatd
--------------------------------------------------------------------------------
Etrack Incident = ET863123
Associated Primary Etrack = ET863120
Description:
A condition existed when the bprd service on the master server connected to
the hosts in its SERVER list and started a process on those servers to
remove old debug log files. If a host was in the MEDIA_SERVER list but not
in the SERVER list on the master server, bprd would not contact that host.
A change was made to ensure that bprd connects to hosts in both the SERVER
list and the MEDIA_SERVER list on the master server to remove old debug
log files.
--------------------------------------------------------------------------------
Etrack Incident = ET863150
Description:
NetBackup’s Release Broker's logging has been improved in the following
manner:
- The total amount of logging content has been reduced.
- The messages that are displayed have been enhanced to be more meaningful.
- Different debug levels are used for different purposes.
--------------------------------------------------------------------------------
Etrack Incident = ET863199
Description:
The SRCMEDIAID & DSTMEDIAID fields of the jobs database were not being
written to.
--------------------------------------------------------------------------------
Etrack Incident = ET861965
Description:
In some cases, when a request for a volume pended, the NetBackup-Java user
interface and vmoprcmd -xdpa would display an error when asked to show the
pending action.
--------------------------------------------------------------------------------
Etrack Incident = ET863314
Description:
The patch level of the (remote) client was wrong when Windows was configured
in the environment.
--------------------------------------------------------------------------------
Etrack Incident = ET861709
Associated Primary Etrack = ET701050
Description:
Network issues would cause tldd connect timeout issues that would result in
downed drives.
--------------------------------------------------------------------------------
Etrack Incident = ET861712 ET861714
Description:
Changes were made to ltid that corrected the following issues:
- ltid would stop and report the following message if it received a message
that were larger than 208 bytes.
Arg list too long
- Occasionally, ltid would not continue to run at startup.
--------------------------------------------------------------------------------
Etrack Incident = ET803746
Description:
Using the -i option for vmchange command resulted in an incorrect error
message that would indicate to users that this function is not implemented
in NetBackup Enterprise Media Manager (EMM).
--------------------------------------------------------------------------------
Etrack Incident = ET863393
Associated Primary Etrack = ET863378
Description:
Backup duplication errors would occur because of a timeout issue that caused
bptm to exit with 54 and 25 errors.
--------------------------------------------------------------------------------
Etrack Incident = ET862641
Associated Primary Etrack = ET702146
Description:
DSSU relocation (duplication) jobs no longer leave a bid_file_* on master
server.
--------------------------------------------------------------------------------
Etrack Incident = ET862648
Description:
Changes were added to correct a DSSU staging process issue that caused the
parent job to hang.
--------------------------------------------------------------------------------
Etrack Incident = ET862609
Description:
The fragment size set for a disk storage unit (DSU) was ignored when doing a
Synthetic backup.
--------------------------------------------------------------------------------
Etrack Incident = ET861978
Description:
Changes were made to eliminate potential race conditions between ltid and
vmd when adding a host entry to EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET862543
Description:
The bpplinclude command could not handle file paths that contain the %
character.
--------------------------------------------------------------------------------
Etrack Incident = ET574945
Description:
Snapshot client SAP backups would fail because no valid license key be
found on the server.
--------------------------------------------------------------------------------
Etrack Incident = ET862603
Description:
A change was made to ensure that bpbrmds no longer exits prior to
bpduplicate finishing (on Tru64 systems only).
--------------------------------------------------------------------------------
Etrack Incident = ET862491
Description:
The nbpushdata log files are now written to the following locations:
/usr/openv/var/nbpushdata (UNIX)
VERITAS\NetBackup\var\nbpushdata (Windows)
Log files are not pruned from these directories, so the files are available
for later review.
--------------------------------------------------------------------------------
Etrack Incident = ET863106
Description:
The MEDIA_UNMOUNT_DELAY is not honored consistently for standalone drives.
Workaround:
To avoid this issue, ensure an eligible tape is loaded in the drive before
You start a job.
--------------------------------------------------------------------------------
Etrack Incident = ET864928
Description:
A backup job would hang in the bpbrm process after the client read timeout
expired. The job would not finish and a 41 status (network connection
timed out) error would occur.
--------------------------------------------------------------------------------
Etrack Incident = ET865189 ET842864
Associated Primary Etrack = ET833467
Description:
Changes were made to enhance the performance and speed in which the list of
media servers would appear after a user selects Host Properties > Media
Servers from the NetBackup-Java Administration Console. The slow response
was caused by the following command, which would return the external
attribute settings for each media server.
vmoprcmd -h <server_name> -extall
--------------------------------------------------------------------------------
Etrack Incident = ET852905 ET850830
Associated Primary Etrack = ET832181
Description:
Changes were added to solve various issues in the Device Configuration
Wizard with respect to back-level media servers. In addition, a change
was made that solves a device configuration wizard defect that prevented
users from reconfiguring standalone drives as robotic.
--------------------------------------------------------------------------------
Etrack Incident = ET861980
Description:
Corrected a tape drive cleaning issue where the end user running the
NetBackup Administration Console on a UNIX server could not successfully
clean a tape drive using a path on a Windows server.
--------------------------------------------------------------------------------
Etrack Incident = ET865211 ET645838
Associated Primary Etrack = ET645838
Description:
A status 50 error would be shown in the Activity Monitor if a user tried to
perform a large duplication that was greater than 20 minutes. Similar
issues were reported in earlier versions of NetBackup. Smaller duplications
were not a problem.
--------------------------------------------------------------------------------
Etrack Incident = ET865184
Description:
Some languages use a comma, instead of a period, to delimit the fractional
portion of a floating point number. If the default language is set to one
of these language, some operations might fail. Specifically, any time a
floating point parameter is passed to the EMM server database it will
reject a floating point number delimited by a comma, instead of a period.
One example of this is attempting to change or set the cleaning frequency
of a drive.
Workaround:
To resolve this issue, change the decimal point character from a comma
to a period ('.'). This can be done by modifying the locale or switching
to a different locale, such as US English.
--------------------------------------------------------------------------------
Etrack Incident = ET865706
Description:
This maintenance pack contains multiple NB_SECURITY infrastructure changes.
--------------------------------------------------------------------------------
Etrack Incident = ET862283
Description:
Changes were made to correct the following issues with the nbemmcmd command.
- The nbemmcmd -getemmserver command would not always get the NetBackup
version.
- The nbemmcmd -setemmserver command would try to set the EMM server on
machines that were not in its domain.
- The nbemmcmd -setemmserver command would not set the EMM server of a master
server.
--------------------------------------------------------------------------------
Etrack Incident = ET865792
Description:
nbVersionNumber() would not return a zero (0) when there was an error
attempting to get the version number from the client. However, in certain
cases this does not happen.
--------------------------------------------------------------------------------
Etrack Incident = ET783403
Description:
The status collector daemon that NetBackup uses to monitor device and host
status for back-level media servers has been logging /vm/debug/reqlib.
This has made debugging for traditional media manager command lines
difficult. This change introduces a new media manager debug directory
/vm/debug/vmscd. This makes it much easier to obtain debugging information
for both vmscd and the media manager command lines.
--------------------------------------------------------------------------------
Etrack Incident = ET863402
Description:
A change was made to ensure the nbemmcmd -listmedia command prints out the
number of mounts, as well as the maximum mounts.
--------------------------------------------------------------------------------
Etrack Incident = ET863433
Description:
The message a user would receive when adding a host that already existed in
database was invalid hostname. A change has been made to correct this
message.
--------------------------------------------------------------------------------
Etrack Incident = ET847915
Associated Primary Etrack = ET820303
Description:
A change was made so that a READY standalone drive was not marked as
NOT-READY during a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET863427
Description:
bpmedialist now uses EMM to build the host list instead of using the storage
unit list.
--------------------------------------------------------------------------------
Etrack Incident = ET866829
Description:
Queuing jobs could not be canceled from bpdbjobs command.
--------------------------------------------------------------------------------
Etrack Incident = ET863413
Description:
A change was made to the nbemmcmd -help command. It now
returns an exit status of 0 instead of an error status.
--------------------------------------------------------------------------------
Etrack Incident = ET866997
Description:
If the NetBackup Request Daemon (bprd) terminated a backup before the
NetBackup Policy Execution Manager (nbpem) was invoked, the terminated
backup job may be reported with a "queued" status forever. This could
occur if a backup was initiated by the bpbackup command line and it
referenced an unwritable progress log file.
--------------------------------------------------------------------------------
Etrack Incident = ET569130
Description:
If the NetBackup Request Daemon (bprd) terminates a backup before the
NetBackup Policy Execution Manager (nbpem) is invoked, the terminated
backup job may be reported with a "queued" status forever. This can
occur if a backup is initiated by the bpbackup command line and it
references an unwritable progress log file.
--------------------------------------------------------------------------------
Etrack Incident = ET865243
Description:
If the NBDB database is not created properly during installation, the
install continues, however the user may not understand that there was an
issue creating the database. As a result, the user may encounter errors
in the command line and the user interfaces.
In addition, if during a patch installation that nbnd_upgrade fails, the
database ends up with the incorrect version. Again, nbemm will not start
because of the version mismatch.
Changes have been made so that the install will fail if the database
cannot be created or upgraded and installation warnings will be logged in
a new logging directory for nbnd commands. The new directories are:
UNIX: /usr/openv/netbackup/logs/nbdb
Windows: InstallPath\NetBackup\logs\nbdb
--------------------------------------------------------------------------------
Etrack Incident = ET865850
Description:
Erase job failures would occur because NDMP drives were being selected for
erase jobs.
Workaround:
To resolve this issue, down NDMP drives to prevent NetBackup from selecting
them for erase jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET865186
Description:
If you use the "Configure Multiple Copies" option before any storage units
are defined the following error message appears.
"Not all storage units are on the same media server"
A change was made to the message to correctly indicate that no storage units
exist.
--------------------------------------------------------------------------------
Etrack Incident = ET893223
Description:
When a server is configured to e-mail from the client after
a successful backup, the bpbrm process would hang and would
not exit because of an e-mail problem on the client.
--------------------------------------------------------------------------------
Etrack Incident = ET846230
Description:
A change was made to resolve an issue that caused NetBackup Release Broker
(NBRB) to crash randomly while performing a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET895177
Description:
A change was made to resolve an issue that caused NetBackup Policy
Execution Manager (NBPEM) to crash because of a shutdown during
clean_media_db operation.
--------------------------------------------------------------------------------
Etrack Incident = ET895170 ET895172
Description:
Changes were made to address scalability issues with NBPEM because
unnecessary computations were being performed of the "jobs due" time.
In addition, the internal queue management was a single thread to
handle multiple queues. This caused long waits to process requests on
some queues.
--------------------------------------------------------------------------------
Etrack Incident = ET834075
Description:
Improvements were added to the CPU utilization by bprd during restore
operations of a large numbers of files.
--------------------------------------------------------------------------------
Etrack Incident = ET862350
Description:
Jobs may queue instead of fail when all drives are down or not available
because of an onDemandOnly setting.
Workaround:
To avoid this issue, cancel the queued jobs if there is no possibility of
them getting drives.
--------------------------------------------------------------------------------
Etrack Incident = ET858772
Description:
Installer will verify that PBX service is running before attempting a server
patch install, and it will start the service if necessary.
--------------------------------------------------------------------------------
Etrack Incident = ET862424
Description:
Messages were added to the NetBackup log whenever media is
frozen/unfrozen/suspended/unsuspended.
--------------------------------------------------------------------------------
Etrack Incident = ET862425
Description:
A message has been added to the client log when the operator is about to
request a media that may be standalone. This message warns the operator
that they may need to manually load the requested media.
--------------------------------------------------------------------------------
Etrack Incident = ET862427
Description:
If a multiplexed job stopped during a tape span (on a standalone drive) the
Media Database for the next tape used would be incorrect, enabling this
tape to be used again and cause data to be overwritten.
--------------------------------------------------------------------------------
Etrack Incident = ET862428
Description:
Added a change to address the latest SCSI standard that changed a device
response to a Test Unit Ready command when the device is SCSI Reserved to
another initiator.
--------------------------------------------------------------------------------
Etrack Incident = ET862430
Description:
Added support for Quantum/Certance Ultrium 3 drive with WORM media.
--------------------------------------------------------------------------------
Etrack Incident = ET862431
Description:
Some tape drives on HP_UX would not perform an erase operation
from NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET862441
Description:
Canceled jobs no longer cause a future job to hang during a media mount.
--------------------------------------------------------------------------------
Etrack Incident = ET413285
Description:
A change was made to endure that timestamps were included in
the cluster agent debug.
--------------------------------------------------------------------------------
Etrack Incident = ET841107
Description:
During a synthetic backup job, one of the source images for the synthetic
may expire. If this happens, when the bptm or bpdm reader attempts to
read the image, it will experience a "no entity found" error from the
catalog. The bptm reader fails. For this particular case, the reader will
enter a code that causes it to hang up indefinitely.
--------------------------------------------------------------------------------
Etrack Incident = ET847324
Description:
Duplicate forms of the .ds file may be created as part of the NetBackup 5.x
to NetBackup 6.x upgrade process that cause bptm or bpbrmds to crash.
For example,
beany_1162489194_C1_F1.ds.info
beany_1162489194_C1_F1.ds.1162489194.img
beany_1162489194_C1_F1.ds.1162489194.info
beany_1162489194_C1_F1.ds
Workaround:
Normally, NetBackup perceives a .img and .info file as one "file" to its
I/O layer. There is a special compatibility mode that enables it to see
the extra .ds and its .info file as the same file in the previous pair.
To avoid this issue, remove one of the pairs, preferably the .img file and
its .info file.
--------------------------------------------------------------------------------
Etrack Incident = ET896802
Associated Primary Etrack = ET798913
Description:
An issue would occur when children jobs were retired due to exceeding the
time allowed in an incomplete state. The parent job, being resumed either
manually or automatically, resulted in an Frequent status code 805 error
because the invalid jobid was -1.
A change was added that prevents the child from starting since it is not
resumable. The new result will correctly be a 200 error if no children
can be started. An indication of this will be written to the policy
execution manager (pem) log.
--------------------------------------------------------------------------------
Etrack Incident = ET862590
Associated Primary Etrack = ET862589
Description:
Added the capability to open UNIX progress logs that are non-blocking.
--------------------------------------------------------------------------------
Etrack Incident = ET860837
Associated Primary Etrack = ET834130
Description:
Jobs would not be retried until all jobs associated with the parent job were
complete.
--------------------------------------------------------------------------------
Etrack Incident = ET860882
Associated Primary Etrack = ET845081
Description:
Restarting a job that was originally an immediate backup, may cause streams
of a different schedule type to be run.
--------------------------------------------------------------------------------
Etrack Incident = ET894249
Description:
NBJM was not forwarding the connect options to bpbrm. On a NetBackup 6.0
media server, bpbrm is able to obtain the connect options. Whereas on a
NetBackup 5.x media server, the connect options must be specified using the
command line.
--------------------------------------------------------------------------------
Etrack Incident = ET847976
Description:
If a synthetic backup job failed to get the requested resources, no
messages were displayed in the job details to explain the cause of a
job that appeared to be hung.
--------------------------------------------------------------------------------
Etrack Incident = ET860264
Associated Primary Etrack = ET860276
Description:
There was insufficient logging information provided when a
catastrophic failure occurred while accessing the UNIX
configuration (bp.conf). In addition, no re-try would be
attempted for such a failure.
--------------------------------------------------------------------------------
Etrack Incident = ET860844
Associated Primary Etrack = ET860273
Description:
Changes were made to resolve status 200 errors that occurred when a parent
job started when children were left active because PEM terminated or a
crash of a generic job occurred.
--------------------------------------------------------------------------------
Etrack Incident = ET860853
Associated Primary Etrack = ET858810
Description:
A change was made so that jobs no longer wait for resources after the window
is closed .
--------------------------------------------------------------------------------
Etrack Incident = ET860856
Associated Primary Etrack = ET860266
Description:
A change was made to address an issue that caused backups to fail with an
800 status.
--------------------------------------------------------------------------------
Etrack Incident = ET854621
Description:
Resolved an issue that caused scheduled, cold-catalog backups to not start.
--------------------------------------------------------------------------------
Etrack Incident = ET860879
Description:
Resolved an issue that caused PEM to run an incremental schedule instead of
a full schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET899176
Description:
Near the completion of a Synthetic backup, the following error message would
intermittently be issued to the Activity Monitor:
Error ACEMsgTran::handleOutput_u (pid=28968) write failed
from OUTPUT socket, errno=9(Bad file descriptor)
This error did not affect the successful completion of the backup, but it
did indicate a problem.
--------------------------------------------------------------------------------
Etrack Incident = ET592677
Associated Primary Etrack = ET808108
Description:
A change was added that resolves a segmentation fault that could occur while
performing Teradata backups on Linux platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET431952
Description:
This maintenance pack contains an enhancement that enables encryption for
Teradata backups.
--------------------------------------------------------------------------------
Etrack Incident = ET866750
Description:
The nbpushdata -modify_5x_hosts command now sets the standalone volume
database host to the EMM server on NetBackup 5.x hosts without standalone
drives.
--------------------------------------------------------------------------------
Etrack Incident = ET899837
Associated Primary Etrack = ET865853
Description:
There was a memory leak in the NetBackup Release Broker (nbrb) that caused
the memory utilization of nbrb to go very high after duplication/synthetic
jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET860860
Associated Primary Etrack = ET856242
Description:
The message queue between bprd and pem would fill up if the request to pem
was invalid.
--------------------------------------------------------------------------------
Etrack Incident = ET849248
Associated Primary Etrack = ET846190
Description:
Changes were made to resolve memory issues on immediate and user-backup
requests.
--------------------------------------------------------------------------------
Etrack Incident = ET832247
Description:
Deleting a cluster node no longer leaves invalid references.
--------------------------------------------------------------------------------
Etrack Incident = ET856478
Description:
The bptm -updatedb command would swap the number of images and the number of
valid images when inserting the data into the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET855644
Description:
A change was made to resolve a possible stack overflow issue that would
cause a system crash.
--------------------------------------------------------------------------------
Etrack Incident = ET850303
Description:
There is a timing issue with bringing the cluster online and running
runtpext. Bringing the cluster online (which can be slow), has an
adverse affect on the runtpext custom action that requests ltid.exe and
vmd.exe to be bounced. On some clustered NetBackup systems that have a
large number of devices (tape drives and robots) this can hang the
cluster install.
Workaround:
To resolve this issue, go into the Windows Task Manager and kill both the
"ltid.exe" and "vmd.exe" processes. The install will then continue and
complete successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET895259
Description:
Added support for PureDisk export to NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET850034
Description:
Changes were made to ensure that the device configuration analyzer utility,
mmcrawl, is working.
--------------------------------------------------------------------------------
Etrack Incident = ET863440
Description:
A change was made to ensure the nbemmcmd -errorsdb command no longer causes
a core dump on 64-bit machines.
--------------------------------------------------------------------------------
Etrack Incident = ET861373
Associated Primary Etrack = ET901494
Description:
Switches have been added to nbemmcmd to allow the use of a different
emmserver than those listed in the configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET863437
Description:
Formatting is now correct for strings on Windows x64 systems.
--------------------------------------------------------------------------------
Etrack Incident = ET794493
Associated Primary Etrack = ET777908
Description:
A restore would fail following a tape span due to attempting to position
to file number "0". The bptm logs show that a "STOP RESTORE" was received
for a restore that was already complete during the tape mount.
--------------------------------------------------------------------------------
Etrack Incident = ET792615
Associated Primary Etrack = ET781425
Description:
bpjobd script would hang sporadically causing the user to manually restart
to view the job monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET864935
Associated Primary Etrack = ET821288
Description:
If the client for a multiplexed backup could not be contacted, the job would
take nearly twice as long as to timeout.
--------------------------------------------------------------------------------
Etrack Incident = ET419594
Description:
Added a new touch-file (/usr/openv/netbackup/IGNORE_ACL) on UNIX client
machines to not back up ACLs.
--------------------------------------------------------------------------------
Etrack Incident = ET594838
Description:
On HP-UX clients, NetBackup now treats cifs file system mount points
as NFS rather than local. Therefore, policies with ALL_LOCAL_DRIVES
specified will no longer back them up.
--------------------------------------------------------------------------------
Etrack Incident = ET614569
Description:
True Image Restore Plus (TIR+) backups currently delete any
TIR information files that are 10 days old or more. Symantec
added a new touch file for UNIX clients to set the number of
days to keep the TIR information files. The default will
remain 10 days, but that can now be set to a value higher
than 10 if desired. In addition, setting this value to 0 (zero)
makes NetBackup never delete old TIR information files.
The touch file is called /usr/openv/netbackup/TIR_INFO_KEEP_DAYS.
Simply put an integer value in this file that represents the
number of days to keep the TIR information files. Numbers that
are less than 10 will set the value to 10 (other than 0).
--------------------------------------------------------------------------------
Etrack Incident = ET406353
Description:
Multi-streaming with wild-cards and NEW_STREAM directives would not
process correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET864177
Description:
The deletion of an application cluster would fail if there were storage
units (STU's) associated with it.
Workaround:
To avoid this issue, delete storage unit first.
--------------------------------------------------------------------------------
Etrack Incident = ET853592
Description:
An archive job may complete with the following error:
"EXIT STATUS 3: valid archive image produced, but no files
deleted due to non-fatal problems"
This is an issue in the underlying operating system and not
NetBackup. This patch detects the condition and takes the
additional steps necessary to handle it.
Workaround:
To resolve this issue, the user may manually remove the backed up
files after the archive completes. Note that care must be taken
not to remove files that are created or modified after the start
of the archive job.
--------------------------------------------------------------------------------
Etrack Incident = ET917548
Associated Primary Etrack = ET901564
Description:
If a window closes while a multiple data streams backup has children queued,
the resume of the parent may produce a 200 error.
--------------------------------------------------------------------------------
Etrack Incident = ET803831
Description:
Executing a bpps -a command on a RedHat 5.0 system would produce
the following NetBackup processes:
tail: cannot open `+2' for reading: No such file or directory
tail: cannot open `+2' for reading: No such file or directory
--------------------------------------------------------------------------------
Etrack Incident = ET918511
Associated Primary Etrack = ET860790
Description:
Changed Policy Execution Manager to log failure history message as an
informational message to avoid adding it to the error log report. Also log
failure history message based on failure history threshold (default
12 hours) instead of using the policy update interval (default 10 minutes)
thus reducing the number of entries logged.
Workaround:
To avoid this issue, increase the policy update interval threshold from
the default of 10 minutes.
--------------------------------------------------------------------------------
Etrack Incident = ET860802
Associated Primary Etrack = ET850162
** Description:
The disk storage unit (DSU) staging did not maintain a retention level on
secondary copies when using inline tape copy (ITC).
--------------------------------------------------------------------------------
Etrack Incident = ET849012
Description:
If nbemm is down and NOM connects to NBSL, then NBSL would
crash.
--------------------------------------------------------------------------------
Etrack Incident = ET764809
Associated Primary Etrack = ET764804
Description:
On Linux clients, raw partition backups of raw devices would
fail with a status 6 error when compression was enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET860288
Associated Primary Etrack = ET857531
Description:
Policy Execution Manager would stop processing manual backup jobs when
house keeping was performed (bptm delete_expired). The worst case
scenario was when the media server could not be reached. The Policy
Execution Manager would then wait for the time out
(CLIENT_CONNECT_TIMEOUT)to be exceeded before moving on.
Changed the Policy Execution Manager to start a third nbproxy which
processes only clean media database (db) commands to avoid a delay of
manual backups.
--------------------------------------------------------------------------------
Etrack Incident = ET914057
Description:
A problem existed that caused an error status on user backups to sometimes
return a 236 error when a 199 error was expected.
--------------------------------------------------------------------------------
Etrack Incident = ET867927
Description:
When using the bpsetconfig command to implement bp.conf entries for a
client, if stdin was used, the list could not exceed 1023 bytes. If
the list did exceed 1023 bytes, the entire list was ignored and the
update failed.
Workaround:
To avoid this issue, use the command with the filename as a parameter
and everything will work properly.
--------------------------------------------------------------------------------
Etrack Incident = ET919129
Associated Primary Etrack = ET848190
Description:
When Multiple Data Streams, DHCP and Windows Open File Backups (WOFB’s) are
enabled, jobs end with 48 status. To resolve this issue, the generic job
(nbgenjob) was changed to only pass a -hostname option if DHCP is enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET853612
Description:
The parent job would exit with a status 50 before starting any children. To
Resolve this issue, the parent job (nbgenjob) was changed to ping the job
manager as soon as possible after startup instead of waiting three minutes.
--------------------------------------------------------------------------------
Etrack Incident = ET832007
Description:
Logs were unclear on what the problem was when database operations were
performed on un-assigned media.
--------------------------------------------------------------------------------
Etrack Incident = ET505726
Description:
The "bpdbjobs -resume" command no longer reports an incorrect number of
restores that were resumed.
--------------------------------------------------------------------------------
Etrack Incident = ET845150
Description:
The machine update code has been updated so it no longer allows machines to
have invalid parent keys.
--------------------------------------------------------------------------------
Etrack Incident = ET591318
Description:
NetBackup now checks the file list to validate that UNIX
file paths begin with a "/" character. This will also
catch cases where extra characters are added to directives
(for example, "ALL_LOCAL_DRIVES;").
--------------------------------------------------------------------------------
Etrack Incident = ET856486
Associated Primary Etrack = ET997038
Description:
Added support for failing over NearStore storage units to a different NetApp
filer that had been mirrored using NetApp's Volume Snap Mirror technology.
--------------------------------------------------------------------------------
Etrack Incident = ET919043
Description:
A job that was configured to use a storage unit group, failed with a
status 129. The job details for a retry gives the appearance that it
retried the job with the STU from the previous try. In reality, all of
the STUs in the group were queried for the best possible candidate.
--------------------------------------------------------------------------------
Etrack Incident = ET838968
Description:
This maintenance pack contains new versions of ACE and TAO libraries. These
libraries contain fixes for race conditions and other problems.
--------------------------------------------------------------------------------
Etrack Incident = ET864163
Description:
A change was made so that nbrb no longer sends "bptm -rptdrv" to an
inactive node in a cluster. In addition, the output of the
nbemmcmd -listhost command has been changed. The description of
machine type for emmserver has been changed from "server" to
"emmserver".
--------------------------------------------------------------------------------
Etrack Incident = ET896185
Description:
When you log in on a node of master in cluster environment, the "Add STU"
operation did not show all of the available media servers.
Workaround:
To avoid this issue, log in using a virtual (cluster) name.
--------------------------------------------------------------------------------
Etrack Incident = ET901549
Associated Primary Etrack = ET857094
Description:
During testing, an active duplicate job was noticed in the Activity
Monitor. The job had a status 150 message in detailed status and it was
still at attempt 1. Its children appeared dead. (No activity in since
12:47 and they were being displayed as active).
The parent seemed active. It was not only displayed active but it was
doing a tape mount around 18:30. It had received a status 150 around
12:47 pm.
Workaround:
To avoid this situation, you can wait until the job state is active and
then cancel it. This will cause it to die correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET849073
Description:
Canceled mount/unmount requests would cause future unmount requests to hang
in BPTM.
--------------------------------------------------------------------------------
Etrack Incident = ET901476
Description:
Changes were made to keyword handling of user backups from
NetBackup 5.0 to 6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET814657
Description:
A backup job would potentially hang if bpbrm received a 174 error (media
manager - system error occurred) prior to receiving a "media ready"
indication from bptm.
--------------------------------------------------------------------------------
Etrack Incident = ET519708
Description:
The Perform Snapshot Backup option in Policy dialog should be disabled if
the Block level increment (BLI) is selected.
--------------------------------------------------------------------------------
Etrack Incident = ET922508
Associated Primary Etrack = ET854626
Description:
During multiplexed backups, multiple retention levels could be added to a
media, even if it was not configured to be allowed.
--------------------------------------------------------------------------------
Etrack Incident = ET515830
Description:
The SSO_SCAN_ABILITY option was not being used and has been removed to avoid
confusion.
--------------------------------------------------------------------------------
Etrack Incident = ET819221
Associated Primary Etrack = ET797322
Description:
Pegasus Software Drives on Windows did not work in NetBackup 6.0 as Disk
Storage Units.
--------------------------------------------------------------------------------
Etrack Incident = ET855357
Description:
NetBackup Enterprise Media Manager (EMM) was using the wrong directory when
checking for a disk full condition that affected the NetBackup Relational
Database (NBDB). If a mirrored transaction log was created, EMM was
checking the location of the main transaction log only.
--------------------------------------------------------------------------------
Etrack Incident = ET922513
Associated Primary Etrack = ET896030
Description:
FlashBackup restores would sometimes produce 252 errors when done with a
short file list.
--------------------------------------------------------------------------------
Etrack Incident = ET865177
Associated Primary Etrack = ET864919
Description:
Freeze scratch media that was found to have a Recorded Volume Serial Number
(RVSN) was not expected. Users must use bplabel to correct this problem
and make the media useable again.
--------------------------------------------------------------------------------
Etrack Incident = ET850088
Description:
Policy Execution Manager no longer passes unlocalized status descriptions
in the error database.
--------------------------------------------------------------------------------
Etrack Incident = ET848632
Associated Primary Etrack = ET841558
Description:
A fix was added so that nbgenjob no longer fails with status 25
and nbpem no longer receives a status 50 after a multi-streaming
job.
--------------------------------------------------------------------------------
Etrack Incident = ET858227
Description:
NetBackup-Java Administration Console Device Configuration wizard now
correctly updates the Robot Type of drives that are detected as stand
alone but drag-dropped by user to a robot.
--------------------------------------------------------------------------------
Etrack Incident = ET865805
Description:
On Windows systems, the Vault reports were not being localized.
--------------------------------------------------------------------------------
Etrack Incident = ET896510
Description:
A change was made to correct an issue that was causing code to appear in a
progress log.
--------------------------------------------------------------------------------
Etrack Incident = ET896531
Description:
A change was made to correct a core dump issue that occurred from vmdareq
when it was run from a command line with no switches.
--------------------------------------------------------------------------------
Etrack Incident = ET896568
Description:
The words "handling path" were not being recorded in the \db\error\ logs
file. The All Logs Entry and the bperror command both mine their results
from the \db\error\ logs and the words "handling path" could be used to
determine if the correct data is being backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET916389
Associated Primary Etrack = ET863109
Description:
Changes were added to resolve an nbpem core dump that would occur after a
successful backup.
--------------------------------------------------------------------------------
Etrack Incident = ET863396
Description:
NDMP backup fails when TIR data spans tapes. This failure occurs only for
NDMP local or NDMP 3-way (backup to an NDMP drive).
Workaround:
Rerunning the backup to a different media will likely work since it is
unlikely that tape spanning will occur during TIR data. (This is because
the TIR data is usually a fraction of the size of the backup image itself.)
Another approach is add the following line to the file
<installdir>/netbackup/db/config/ndmp.cfg
NDMP_MOVER_CLIENT_DISABLE
Adding this line will have a minimal impact on backups. However it will
cause a significant performance impact to dup/verify/import when using
NDMP drives.
--------------------------------------------------------------------------------
Etrack Incident = ET777981
Description:
nbpemreq would fail if a large time value was passed to the nbpemreq
predict option. If you specified a number that exceeded a long value
for the command, nbpemreq -predict -dateu <timevalue>, the results
would be undefined.
--------------------------------------------------------------------------------
Etrack Incident = ET821317
Description:
A misleading error status 48 (client hostname could not be found) may be
applied to a job if a communication problem occurred between the media and
the master server. A typical cause of the problem was an expired license
on the media server. In this case, the error status should have been 161
(Evaluation software has expired.)
--------------------------------------------------------------------------------
Etrack Incident = ET828730
Description:
In a rare situation, a FlashBackup job could not be cancelled.
--------------------------------------------------------------------------------
Etrack Incident = ET852018
Description:
Changes have been made to reduce the performance overhead when sending mail
to a client after a backup job completes.
--------------------------------------------------------------------------------
Etrack Incident = ET896769
Associated Primary Etrack = ET923399
Description:
The pem logs report a scheduled backup (SB) job type as an immediate (IB)
backup job type after a failed immediate backup.
--------------------------------------------------------------------------------
Etrack Incident = ET864933
Description:
On Windows media servers, restores from disk in some cases would potentially
read unneeded data instead of skipping it, which could affect performance.
--------------------------------------------------------------------------------
Etrack Incident = ET805992
Description:
In some cases, hot catalog backup would report success even though the
ASA backup was either not successful or conditionally successful.
--------------------------------------------------------------------------------
Etrack Incident = ET924798
Associated Primary Etrack = ET860296
Description:
Callers to bpdbm make unnecessary licensing checks that could lead to
misleading error messages.
--------------------------------------------------------------------------------
Etrack Incident = ET923799
Description:
With NetBackup running under NetBackup Access Control (NBAC), authorization
checks were skipped for some operation of corba daemons. This could have
enabled an unauthorized user to perform some privileged operations.
--------------------------------------------------------------------------------
Etrack Incident = ET924345
Associated Primary Etrack = ET856266
Description:
Jobs that were due to start, would not start if JobDefinition::checkDueness
took more than one second.
--------------------------------------------------------------------------------
Etrack Incident = ET901028
Description:
Changes were made that enable you to now use "./bpnbat -login -info" on
Linux systems.
Workaround:
You can also use bpnbat in interactive mode by using just the -login option.
--------------------------------------------------------------------------------
Etrack Incident = ET778927
Description:
A master could be renamed to a pre-existing media server. However, the
logs were recording the wrong name if a machine was renamed to a
pre-existing machine.
--------------------------------------------------------------------------------
Etrack Incident = ET417907
Description:
When vmquery was used with a prefix containing '_', the char '_' was used
as a wild card character and an out of order media id could be given.
--------------------------------------------------------------------------------
Etrack Incident = ET831182
Description:
The message, "database backup is currently disabled," appeared in the
Problems report even when a scheduled hot catalog backup was configured.
--------------------------------------------------------------------------------
Etrack Incident = ET924482
Description:
The parent key could be incorrectly set when adding a node of a cluster.
The parent key of a media server could be incorrectly set if node of master
cluster was given instead of cluster name.
--------------------------------------------------------------------------------
Etrack Incident = ET534073 ET534196 ET569931 ET592599
Description:
The following Windows updates have been added to this maintenance pack:
- Updated the support utility nbsupport to version 2.1.2
- Updated the Windows support utility nbsupport.exe to version 2.1.2
- Updated the Windows support utility nbsu_win_cmds.exe to version 2.0
- Added the Windows support script fs
--------------------------------------------------------------------------------
Etrack Incident = ET864934
Description:
A duplication may have been reported as successful if a defective tape
drive incorrectly reported a tape mark on the read operation, followed
by an I/O error. This maintenance pack detects this error condition.
--------------------------------------------------------------------------------
Etrack Incident = ET803724
Description:
Catalog recovery from a hot catalog backup failed if Bare Metal Restore
(BMR) was installed but not configured and/or running at the time of the
hot catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET648727
Description:
Added a new Automated Cartridge System (ACS) vendor for media and drive
types.
--------------------------------------------------------------------------------
Etrack Incident = ET616381
Description:
In NetBackup-Java Administration Console, inventory of a robot attached to
a cluster node resulted in volumes being added with the cluster node as the
robot control host and not the virtual host name. This behavior has been
changed to make the virtual host name as the control host. Doing this
avoids potential problems in inventory if a cluster fails over to a
different cluster node.
--------------------------------------------------------------------------------
Etrack Incident = ET916378
Associated Primary Etrack = ET915043
Description:
The bpdbjobs timestamp output is no longer truncated for STARTED and ENDED
fields.
--------------------------------------------------------------------------------
Etrack Incident = ET830327
Description:
Access failures to the Activity Monitor were occurring for the
Domino-partitioned, server backup reports file (exec.nbf).
However, the bpbrm log would exit with a Status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET895584
Associated Primary Etrack = ET786448
Description:
NetBackup for Lotus Notes parses all the paths in the
LOTUS_NOTES_PATH variable to determine the Lotus program
directory. The first path in the LOTUS_NOTES_PATH variable
in which "bin/server" is present is treated as a Lotus Program
directory. If any other path (for example, the Lotus data
directory) which is present in the beginning and "bin/server",
exists in that path then it is misinterpreted as Lotus program
directory. This causes the backup to fail with a status 9 error.
Workaround:
To resolve this issue, enter the path of the Lotus program
directory in the beginning of LOTUS_NOTES_PATH variable.
--------------------------------------------------------------------------------
Etrack Incident = ET842011
Description:
bpmedialist could not be killed from the Activity Monitor successfully.
A change was made to ensure the correct program name is being passed from
bpmedialist to the job manager (JM).
--------------------------------------------------------------------------------
Etrack Incident = ET639038
Description:
A correction was made to ensure the vulnerability test for
bprd (Vuln_bprd.tst) no longer generates a core dump issue.
--------------------------------------------------------------------------------
Etrack Incident = ET925564
Description:
The "bpdbm –consistency 2" command was removed from the
list of commands that nbsupport runs.
--------------------------------------------------------------------------------
Etrack Incident = ET926712
Description:
A small memory leak in Policy Execution Manager when processing change
events has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET926721
Description:
Changed the Policy Execution Manager to pass the locale attributes correctly
to the job manager instead of setting them all to lctype.
--------------------------------------------------------------------------------
Etrack Incident = ET852018
Description:
Changes were made to address some small performance issue due to unnecessary
string duplications in the Policy Execution Manager when mailing client
status upon job completion.
--------------------------------------------------------------------------------
Etrack Incident = ET498723
Description:
In the event that a shared standalone drive is updated to be robotic, other
hosts that share this drive will also be updated to robotic. If the robot
is not configured on any of those hosts, however, this results in an
illegal configuration.
Workaround:
To avoid this issue, manually create robotic entries or only use the Device
Configuration wizard.
--------------------------------------------------------------------------------
Etrack Incident = ET926699
Associated Primary Etrack = ET925811
Description:
When drives are selected for NDMP restores, NetBackup media servers are
preferred over NDMP tape servers that are not local to the NDMP host being
restored to.
Workaround:
If a media server has drives with paths to both NetBackup and NDMP servers,
you should down the NetBackup paths before initiating the restore.
--------------------------------------------------------------------------------
Etrack Incident = ET852171
Description:
The EMM server does not reject a client-provided media_id such as, '------'.
This is not a regression. The NetBackup 5.x behavior was exactly the same.
Workaround:
This issue is a client application error when such a name comes is used.
--------------------------------------------------------------------------------
Etrack Incident = ET851125
Associated Primary Etrack = ET793484
Description:
In some instances a job would receive an incorrect 24 status (socket write
failed) instead of the correct 84 status (media write error).
--------------------------------------------------------------------------------
Etrack Incident = ET846076
Description:
An incremental hot catalog backup would fail with a 190 error if the master
server name configured in the hot catalog backup policy differed from the
currently active master server name where each name is a valid name for the
host. This would occur if the long name was used in the policy, but the
short name was being used in the bp.conf file.
--------------------------------------------------------------------------------
Etrack Incident = ET863389
Description:
Duplication of NDMP image fails when using non-NDMP drives.
This problem only occurs when the duplication is using the shared memory
method (SHM) method. In NetBackup 6.0, this happens for any NDMP backup
that used MM (non-NDMP) drives (also known as, "Remote NDMP"). In addition,
this happens if an NDMP image is duplicated to a non-NDMP drive and then
the duplicated image is duplicated.
The progress log shows the following error:
ERR - Unable to create data socket to receive TIR data.
Workaround:
To avoid this issue, disable the shared memory method by adding the
following touch file:
<installdir>/netbackup/NOSHMDUP
Additional Notes:
This problem has been fixed in this maintenance pack, such that all
duplications of NDMP backup images using non-NDMP drives will now use
the shared memory method.
(This problem was solved by disabling shared memory method for all
NDMP images in the NetBackup 5.1 maintenance packs.)
--------------------------------------------------------------------------------
Etrack Incident = ET828441
Description:
NetBackup relational databases would not be restarted when a cold catalog
backup was canceled.
--------------------------------------------------------------------------------
Etrack Incident = ET930028
Description:
A hot catalog backup parent job no longer fails with a status 818 error
(retention level mismatch).
--------------------------------------------------------------------------------
Etrack Incident = ET893639 ET417284
Description:
When NetBackup is clustered, NOM would show the wrong information about
services and media.
--------------------------------------------------------------------------------
Etrack Incident = ET583036
Description:
Restoring a Lotus database link no longer results in a loss of data.
--------------------------------------------------------------------------------
Etrack Incident = ET922076
Description:
When a database link is restored on UNIX platform, it is restored with the
size of the original database it was pointing to when the backup was taken.
--------------------------------------------------------------------------------
Etrack Incident = ET865713
Description:
Under NBAC, 'bpnbaz -setupsecurity' could fail silently, potentially
compromising the desired access control hierarchy.
--------------------------------------------------------------------------------
Etrack Incident = ET854649
Description:
The shutdown and startup of the NetBackup relational databases, NBDB and
BMRDB, will be logged to the NetBackup error log.
--------------------------------------------------------------------------------
Etrack Incident = ET928712
Associated Primary Etrack = ET897092
Description:
NetBackup Job Manager (NBJM) could take a long time to unload drives,
or fail to unload drives because the media servers all had multiple
endpoints, many that were on unreachable networks.
For example, an unreachable network would take about 225 seconds to
fail on Solaris, and some callbacks would take about 10 to 15 minutes
to iterate all failed endpoints.
A change was added to the endpoint selection algorithm so that if
there is at least one endpoint that matches the server list, it will
only attempt those endpoints that match the server list.
--------------------------------------------------------------------------------
Etrack Incident = ET927755
Associated Primary Etrack = ET926665
Description:
On some Windows machines, any Firewall_in bpconf configuration would report
as "Malformed Firewall_in line" in the VxUL log files, and rendered the
NAT translation feature as not operational.
--------------------------------------------------------------------------------
Etrack Incident = ET926704
Associated Primary Etrack = ET926503
Description:
If a user backup submits a very large number of files, PEM may cause a
memory fragmentation and possibly a crash.
Workaround:
To resolve this issue, reduce the file list size by specifying directories
instead of individual files.
--------------------------------------------------------------------------------
Etrack Incident = ET857478
Associated Primary Etrack = ET838788
Description:
NetBackup currently treats all read-only HFS file systems
on Mac OS X as CD-ROMs and disallows the backup. This
change allows the backup of mounted read-only file systems
that are not CD-ROMs.
--------------------------------------------------------------------------------
Etrack Incident = ET515549 ET933307
Description:
The CIsActive function that is loaded from the NBClusterConfig.dll failed on
64-bit systems.
Additional Notes:
The use of VCS API calls, which did not support 64-bit platforms in the
past, have been removed. IsActive simply tests if the shared disk resource
is on the current system to determine if it is the active node.
--------------------------------------------------------------------------------
Etrack Incident = ET932016 ET988979 ET1002606
Description:
Buffer overflow areas have been identified and corrected in daemons that
run on Veritas NetBackup master, media, and client servers. Successful
access to a vulnerable Veritas NetBackup server and the ability to
successfully execute arbitrary code could potentially result in
unauthorized access with elevated privilege on a system.
--------------------------------------------------------------------------------
Etrack Incident = ET932003
Description:
A change was added to resolve a possible memory corruption issue in the
legacy DA process (vmd on EMM server).
--------------------------------------------------------------------------------
Etrack Incident = ET927553
Associated Primary Etrack = ET924626
Description:
Fixed an issue that caused bpbkar to hang on Linux systems if it encounters
an NFS mount point when the NFS server is down.
Workaround:
To resolve this issue, add the NFS mount point to the exclude list for the
client.
--------------------------------------------------------------------------------
Etrack Incident = ET854810
Description:
By using the bprestore command (/usr/openv/netbackup/bin/bprestore) it is
now possible to restore an image using a non-primary copy.
Workaround:
In addition, you can use the bpchangeprimary command
(/usr/openv/netbackup/bin/admincmd/bpchangeprimary) to change the primary
copy of the image.
--------------------------------------------------------------------------------
Etrack Incident = ET533389
Description:
For a True Image Restore (TIR) that is larger than 2GB, the following error
would occur when reading the TIR information.
Error occurred reading TIR information, expected -2103963310 bytes, read
2191003986
The bpdm log would show the following:
11:03:32.958 [20388] <16> read_data_tir: ERR - Error occurred reading TIR
information, expected -2103963310 bytes, read 2191003986
2191003986 is the size of the TIR file -
-rw------- 1 root root 2191003986 Dec 30 10:50
devnfs2-bkup_1135889406_C1_TIR.1135889406.img
The problem only occurred, when the TIR file was larger than 2GB.
--------------------------------------------------------------------------------
Etrack Incident = ET863133
Description:
A fix was added so that a hot catalog recovery from a hot catalog backup to
a new master server name no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET925227
Associated Primary Etrack = ET922389
Description:
When the client name is in upper case, a Windows backup uses WOFB even
though the clientDB entry disables the WOFB.
Workaround:
To resolve this issue, use the same case for client name in client
database and policy database.
--------------------------------------------------------------------------------
Etrack Incident = ET895746
Description:
The renewal of a machine credential issued by a non-root authentication
broker no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET932264
Associated Primary Etrack = ET893298
Description:
An issue existed that would sometimes cause a job to run on the exclude day
even if a frequency scheduling of 24 hours was used.
--------------------------------------------------------------------------------
Etrack Incident = ET829853
Description:
FlashSnap Instant Recovery rotation would fail on Linux
because of a bprd request popen failure.
--------------------------------------------------------------------------------
Etrack Incident = ET855922
Description:
Catalog archiving would fail intermittently with the following message:
bpcatarc: failure running catalog archiving backup policy: the specified
policy is not active (247)
Workaround:
This problem was observed with a mis-configured /etc/hosts file, which
caused excessively long DSN lookups. To avoid this situation, configure
the /etc/hosts file to avoid long DSN lookups.
--------------------------------------------------------------------------------
Etrack Incident = ET796521
Associated Primary Etrack = ET704676
Description:
A backup job would fail with a status 130 when a client path
exceeded 1023 characters.
Workaround:
To avoid this issue, add the long directory path to an exclude
list.
--------------------------------------------------------------------------------
Etrack Incident = ET893368 ET893377 ET893379
Description:
If a Catalog Cleanup operation is kicked off in the middle
of a Hot Catalog Backup, the operation may clean up expired
image catalog entries that were given to the Hot Catalog Backup
in its file list, causing the Hot Catalog Backup to finish
with a partial success.
Changes have been made so that a Hot Catalog Backup now completes with
success status of 0. In addition, it internally detects the cleaned up
image catalog entries, and quietly ignores them.
--------------------------------------------------------------------------------
Etrack Incident = ET930124
Description:
A change has been made to ensure that NBPEM finds all user-initiated jobs,
all of the time.
--------------------------------------------------------------------------------
Etrack Incident = ET933326
Associated Primary Etrack = ET917312
Description:
nbnos would core dump on an HP-UX master server with max_thread_proc set at
the default value of 64. Every nbpem restart would cause nbnos to create
more threads. Corrections were made to nbpem that prevent nbnos from
creating new threads every time nbpem is restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET649458
Description:
The VRTS VxFS file system does not support named data streams
that contain directory structures. A check was added to warn
users if a named data stream that contains a directory structure
is found during file processing. Such structures will not be
backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET933586
Associated Primary Etrack = ET932325
Description:
During a multi-streamed database backup (MS-SQL backup in this case), the
media gets unmounted/mounted again intermittently. Ideally, the NetBackup
resource broker (nbrb) should try to use the loaded media (preferably same
media) for all streams.
--------------------------------------------------------------------------------
Etrack Incident = ET915850
Associated Primary Etrack = ET915879
Description:
Changes were made to ensure that multi-threaded processes no longer crash.
--------------------------------------------------------------------------------
Etrack Incident = ET918766
Description:
Sorting would not work on some columns if the report contained one or more
hidden columns.
--------------------------------------------------------------------------------
Etrack Incident = ET933398
Associated Primary Etrack = ET933394
Description:
Backups may not run as expected if full and incremental had the same
frequency.
--------------------------------------------------------------------------------
Etrack Incident = ET926835
Associated Primary Etrack = ET794461
Description:
Corrected a possible truncation of a file's user or group name.
This change allows for a full 32 character user and group name.
--------------------------------------------------------------------------------
Etrack Incident = ET931959
Associated Primary Etrack = ET931900
Description:
Corrected errors that caused canceled backups to leave the tape media
without a valid empty header on it.
--------------------------------------------------------------------------------
Etrack Incident = ET850961
Associated Primary Etrack = ET809378
Description:
The restore of database and compressed files could fail with
a status 5 when "overwrite existing files" was not selected
and the files to be restored exist.
--------------------------------------------------------------------------------
Etrack Incident = ET819697
Description:
This maintenance pack contains enhancements and fixes to some minor errors
that were occurring in NOM (specifically in the Display Point version of
NetBackup in NOM).
--------------------------------------------------------------------------------
Etrack Incident = ET797596
Description:
On the NOM user interface, (Managing > Media > Details) the "Time Assigned"
filter was not functioning properly.
--------------------------------------------------------------------------------
Etrack Incident = ET896513
Description:
NBPEM e-mail function would send a secondary "additional information" e-mail
for some failed backups.
--------------------------------------------------------------------------------
Etrack Incident = ET892407
Description:
Corrected an issue that caused bplabel to fail if VxSS (NBAC) is enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET807751
Description:
The "import" feature would not work on a NOM Windows server after an
"export" database (DB) function was performed.
--------------------------------------------------------------------------------
Etrack Incident = ET852129
Description:
Under NBAC, a NetBackup 5.1 media server or client could not be configured
with NetBackup 6.0 master.
The bpnbat -loginmachine command would cause a hang or failure on a
NetBackup 5.1 media server or client. The following logs were produced.
14:52:27.578 [2035] <2> get_string: (7) inadequate buffer space for data
14:52:27.578 [2035] <2> get_string: read until the buffer was full; got:
14:52:27.578 [2035] <2> get_string: EXIT STATUS 13
14:52:27.578 [2035] <2> bprd_get_nbac_pdr_info: get_string() failed,
Error 0 (0), success
--------------------------------------------------------------------------------
Etrack Incident = ET794712
Associated Primary Etrack = ET785847
Description:
Changes were added to increase the efficiency of an image cleanup when the
disk-stage storage unit (DSSU) fills.
--------------------------------------------------------------------------------
Etrack Incident = ET934452
Description:
The machine state could be reported inaccurately from the
nbemmcmd -listhosts -verbose command if the machine state was inactive
for disk jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET853808 ET898992
Description:
A multi-streamed parent job may have been retried more than the configured
number of times if the parent job failed before the streams were created for
the first time.
--------------------------------------------------------------------------------
Etrack Incident = ET797314
Description:
Add VxUL Logging support for Activity Monitor module and as a result
a new log file with ID 263 will be generated in the logs folder.
--------------------------------------------------------------------------------
Etrack Incident = ET935814
Description:
Corrected the check used to determine if the local device_mappings.txt
is current.
--------------------------------------------------------------------------------
Etrack Incident = ET806878
Associated Primary Etrack = ET814738
Description:
A multi-threading issue would occasionally cause bpstsinfo
to core dump on some platform and operating system combinations.
--------------------------------------------------------------------------------
Etrack Incident = ET913578
Description:
NBSL is crashing due to the read only directory or invalid path of nbsl.xml.
--------------------------------------------------------------------------------
Etrack Incident = ET936802
Associated Primary Etrack = ET924495
Description:
The backup of a directory that contains a large number of
files using wild cards would fail with a STATUS 70.
Workaround:
To resolve this issue, specify the directory in question in
the file list rather than using wild cards.
--------------------------------------------------------------------------------
Etrack Incident = ET933518 ET933543 ET544382 ET933547 ET933544 ET933528 ET933537
ET830317 ET830319 ET916879
Associated Primary Etrack = ET814702 ET799749 ET647499 ET899240 ET851802
ET858011
Description:
The following changes were added to this maintenance pack in response to
customer escalations:
- Issues with pop-ups that occurred when FlashBackup terminated
- Restores from multiple images
- Multi-volume image and 32-bit overflow
- Incorrect handling of multi-byte characters
- Incomplete data being sent to catalog
- Ensure that directories are restored in descending order
- Hard-link restore problems
- Linux master and FlashBackup windows
--------------------------------------------------------------------------------
Etrack Incident = ET861506
Description:
The Job Manager must forward a snap ID from a non-streamed Windows open
file backup (WOFB) to the Policy Execution Manager for VSP cache files
to be cleaned. In addition, changed the Policy Execution Manager to add
SNAP_ID directives to include the file list.
--------------------------------------------------------------------------------
Etrack Incident = ET918477
Associated Primary Etrack = ET917028
Description:
This is limited to the Nearstore storage unit.
If an incremental backup was done after a synthetic full backup, and no
other full backups existed on that volume, then the incremental would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET899124
Associated Primary Etrack = ET899121
Description:
This issue only affected restores from Nearstore storage units.
Non-full backups (a subset of the entire backup ) where files were pulled
from fragments other than fragment 1 would fail. The issue was that the
image relative offset was not being tracked and NetBackup was seeking to
the incorrect offset within the image.
Workaround:
To resolve this issue, use the Nearstore File System Export functionality
or duplicate the entire backup to basic disk or some other media.
--------------------------------------------------------------------------------
Etrack Incident = ET924417
Associated Primary Etrack = ET917312
Description:
Please see etrack
--------------------------------------------------------------------------------
Etrack Incident = ET921795
Description:
Changes were made in this maintenance pack to ensure the Log Management
feature is working.
--------------------------------------------------------------------------------
Etrack Incident = ET932217
Description:
NBJM was failing jobs with a status 818 (retention level mismatch) because
of an incorrect check.
--------------------------------------------------------------------------------
Etrack Incident = ET937680
Description:
Some TLD libraries with barcode readers were unable to import or inventory
media with an unbarcoded media in the library.
--------------------------------------------------------------------------------
Etrack Incident = ET831697
Description:
Added some exception handling code to this maintenance pack.
--------------------------------------------------------------------------------
Etrack Incident = ET569949
Description:
This change enables the localization team to localize the XML files for VxUL
logs.
--------------------------------------------------------------------------------
Etrack Incident = ET831189
Description:
NetBackup shutdown would not terminate parent jobs (nbgenjob). A change
was made to the Policy Execution Manager to terminate all parent jobs
with a 50 status (EC_client_aborted).
Workaround:
To resolve this issue, manually terminate all nbgenjob processes.
--------------------------------------------------------------------------------
Etrack Incident = ET857404
Description:
Changes were added to correct possible null pointer issues.
--------------------------------------------------------------------------------
Etrack Incident = ET933508
Description:
Added the latest version of VxMS 4.3.018 in this maintenance
pack.
--------------------------------------------------------------------------------
Etrack Incident = ET851163
Associated Primary Etrack = ET849091
Description:
Changes have been added to ensure that send_mail() validates
all parameters it receives.
--------------------------------------------------------------------------------
Etrack Incident = ET866302 ET893368
Description:
The catalog cleanup process will not run to completion because it yields to
a catalog backup. If the cleanup process is long or if catalog backups are
frequent, the cleanup will not be able to delete expired images.
This maintenance pack contains a fix that enables catalog cleanup and
catalog backup to run in parallel. If a cleanup operation runs when a hot
catalog backup is in progress, it might delete images that were sent to
bpbkar earlier (in its image directive list), and cause the hot catalog
backup to finish with a partial success. This fix detects this situation
and returns the right error code to bpbkar.
The cleanup and catalog backup running in parallel is now the default
behavior. However, this can be disabled by creating a file called
"CLEANUP_WAIT_FOR_CATBKUP" in netbackup/db/config (for UNIX) and
\NetBackup\db\config (for Windows).
This fix also enables images to be expired and deleted using bpexpdate
even when a hot catalog backup is in progress.
Workaround:
To resolve this issue, disable hot catalog backups to allow cleanup to
run to completion.
--------------------------------------------------------------------------------
Etrack Incident = ET808281
Description:
bpdbm incorrectly sets the PFI_TYPE to 0. It must check if the copy being
deleted is a Persistent Frozen Image (PFI) or not and set the PFI_TYPE to 0
(only when the copy being deleted is a PFI).
--------------------------------------------------------------------------------
Etrack Incident = ET802974
Associated Primary Etrack = ET802966
Description:
The read_files_file queries would fail with a status of 249 because bpdbm
had not received the flist_complete yet.
--------------------------------------------------------------------------------
Etrack Incident = ET862545
Associated Primary Etrack = ET862538
Description:
Importing NetBackup 5.0 NDMP images would fail with an error code 42
from db_end().
--------------------------------------------------------------------------------
Etrack Incident = ET863352
Associated Primary Etrack = ET863351
Description:
The command "bperror -d <start date/time> -e <end date/time>" would not
give the correct result when daylight time saving was involved.
--------------------------------------------------------------------------------
Etrack Incident = ET542191
Description:
The success_fail_msg function in nb/media/bpbackupdb.c is for an offline
catalog backup on online catalog backups.
--------------------------------------------------------------------------------
Etrack Incident = ET863358
Associated Primary Etrack = ET848205
Description:
Internationalization (I18N): An NDMP restore with a Japanese directory
name no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET972452
Description:
Block Level Incremental (BLI) backups of DB2 databases
would fail on Linux.
--------------------------------------------------------------------------------
Etrack Incident = ET965811
Associated Primary Etrack = ET964501
Description:
Duplication (with multiplexing preserved) hangs for multiplexed TIR
images when using NetBackup 6.0 MP4.
Workaround:
To resolve this issue, do not preserve multiplexing when duplicating,
or do not use multiplexing. In addition, this may slow down performance.
--------------------------------------------------------------------------------
Etrack Incident = ET962923
Description:
NetBackup Service Layer (nbsl) no longer core dumps during install,
sched_bkup, and uninstall tests.
--------------------------------------------------------------------------------
Etrack Incident = ET965512
Description:
The VSS authorization tables were updated to include the new EMM interfaces.
--------------------------------------------------------------------------------
Etrack Incident = ET983962
Description:
An earlier change was made to keep track of open file
descriptors. Descriptors are pushed onto a stack as files
are opened and popped from the stack when they are closed.
For file pointers the fileno of the pointer is used. On
Linux, when a file pointer is closed, the pointer value is
reset by the operating system. This caused problems with
fileno and it is possible to cause segmentation violations.
The fix is to replace existing "close then pop" sequences
with a macro that does a "pop then close" sequence on Linux
and a "close then pop" on other platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET973985
Associated Primary Etrack = ET931484
Description:
Multiplexed SAP backups that were using (Standard) AES-128 Encryption
would fail with the following error: "ERR - backup failed 49 <client
did not start>".
--------------------------------------------------------------------------------
Etrack Incident = ET974342
Associated Primary Etrack = ET972826
Description:
A change has been made to ensure that a non-streamed, Windows open file
backup, runs the right schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET915448
Associated Primary Etrack = ET915442
Description:
Adding an operating system (OS) group to a Role in NBAC does not give the
Appropriate permissions to members of that OS group.
--------------------------------------------------------------------------------
Etrack Incident = ET928695 ET492823
Associated Primary Etrack = ET928687
Description:
In certain cases, PBX logs were not being pruned according to settings in
/etc/vx/VxICS/icsul.conf.
Additional Notes:
UNIX PBX runtime components are being updated in this maintenance pack along
with the NetBackup Server.
--------------------------------------------------------------------------------
Etrack Incident = ET990874
Associated Primary Etrack = ET974535
Description:
A timing problem was introduced in the last patch that could
cause multiplexed TIR backups to fail. This was due to a
backup ending as another was recording the TIR information.
--------------------------------------------------------------------------------
Etrack Incident = ET831965
Description:
NetBackup 6.0 disk staging storage unit’s high water mark (HWM) and low
water mark (LMW) are not changeable for an application cluster
(AppCluster) configuration. Currently, the AppCluster Configuration does
not have a NetBackup version so it is treated as a pre-NetBackup 6.0
storage unit, where the HWM is set to the previous behavior of 100 percent
and a LWM did not exist, therefore it is set to a default value of
80 percent. Both of these settings were new in NetBackup 6.0 and are not
configurable in pre-NetBackup 6.0 versions.
Workaround:
The AppCluster version number must be at the same version level as
the servers that make up the AppCluster. To resolve this issue, the
user should manually enter the NetBackup version number for the
AppCluster using the nbbemmcmd command. In addition, all of the
NetBackup servers in the AppCluster should be at the same, specified
version.
As an example, you would use the following command on the master
server to update the NetBackup version number for an AppCluster.
nbemmcmd -updatehost -machinename virtual_name -machinetype app_cluster
-netbackupversion 6.0
where virtual_name is the virtual name of the application (AppCluster).
--------------------------------------------------------------------------------
Etrack Incident = ET991906
Description:
Changes were made to ensure that a Vault operator could operate properly in
an NBAC environment.
--------------------------------------------------------------------------------
Etrack Incident = ET991647
Associated Primary Etrack = ET990896
Description:
After installing the BMR boot server to a Windows system with a
NetBackup 6.0 MP maintenance pack installed, and then performing a repair
on the pack to apply the BMR boot server binaries, the user should copy
the binaries to the correct directory location. If a NetBackup
installation was installed to a alternate location, the repair will not
correctly apply the patch binaries to the alternate location.
Workaround:
Again, to resolve this issue, copy the binaries, after performing the
"repair" option to the correct directory.
--------------------------------------------------------------------------------
Etrack Incident = ET992949
Description:
V_snprintf uses vsnprintf to implement a fix for uncommon strcat usage. On
the Windows platforms, vsnprintf did not guarantee a null terminated buffer.
Specifically, this was true if the data in the buffer exactly filled the
destination without leaving room for the null termination. In this case,
the buffer would not be null terminated and the function would crash when
V_strlcpy is called.
--------------------------------------------------------------------------------
Etrack Incident = ET990034
Description:
When an inline tape copy job with multiplexed protocol was resumed after a
checkpoint, the job was restarted instead of resumed.
--------------------------------------------------------------------------------
Etrack Incident = ET996117
Associated Primary Etrack = ET990855
Description:
Changes were made so that direct calls to the signal (),SBT implementation
no longer occurs.
--------------------------------------------------------------------------------
Etrack Incident = ET994229
Associated Primary Etrack = ET993986
Description:
A condition existed that caused failed jobs to exceed a configured number of
tries.
--------------------------------------------------------------------------------
Etrack Incident = ET992223
Description:
When checkpoint restart was enabled, and the "continue" flag was set in
the schedule, bptm terminated the copy when an error on that copy
occurred. When the copy terminates, for multiplexing, no more jobs were
scheduled for the multiplexed group. However, in rare cases there is a
timing window where jobs may have already been started but not yet
processed by bptm. In this case, incomplete fragment cleanup occurred
for the failed copy.
--------------------------------------------------------------------------------
Etrack Incident = ET997950
Associated Primary Etrack = ET984069
Description:
Oracle proxy copy incremental (CINC) backups are no longer running as full
Backups.
--------------------------------------------------------------------------------
Etrack Incident = ET992959
Associated Primary Etrack = ET993079
Description:
In some scenarios, the resource broker (RB) was orphaning resources that
were already marked to be released. This caused extra processing overhead
and communication overhead between nbrb and nbjm.
--------------------------------------------------------------------------------
Etrack Incident = ET999559
Description:
The pack installer will now log server system information such as EMMSERVER
(remote or local), media versus master server, and inactive cluster node.
--------------------------------------------------------------------------------
Etrack Incident = ET998728
Description:
The NetBackup version is now displayed in the nbemmcmd -listhosts -verbose
output.
--------------------------------------------------------------------------------
Etrack Incident = ET1000607
Description:
Symantec Code Repository Revision Tags was added to some files, to enable
better tracking.
--------------------------------------------------------------------------------
Etrack Incident = ET999754
Description:
If there were multiple copies of a backup, and a duplication was requested
for disk source copy 1 (or any disk copy other than the last), the
duplication might be started as a non-shared memory duplication. A shared
memory duplication is preferable for performance reasons.
--------------------------------------------------------------------------------
Etrack Incident = ET1001117
Description:
For Windows, added Sybase ASA service dependency to the NetBackup Resource
Broker.
--------------------------------------------------------------------------------
Etrack Incident = ET970398
Description:
In an NBAC setup, a volume configuration that uses the user interface wizard
would fail with an error 39.
--------------------------------------------------------------------------------
Etrack Incident = ET1008736
Associated Primary Etrack = ET966429
Description:
bpstart_notify would not get executed if the dos 8.3 pathname option was
turned off on NTFS partitions. After disabling dos 8.3 pathnames,
bpstart_notify would not run. bpbkar32.exe reports the bpstart_notify script
has started and ended, but the contents would not be executed.
--------------------------------------------------------------------------------
Etrack Incident = ET1005425
Description:
NetBackup pem would consistently terminate when an orphan job existed.
--------------------------------------------------------------------------------
Etrack Incident = ET1003200
Associated Primary Etrack = ET1003184
Description:
bprecover would crash during a recovery of a BMR database file that exceeded
2GB in size.
--------------------------------------------------------------------------------
Etrack Incident = ET990295
Description:
During multi-eject operations the vmchange program would return a
status code 0 (success) if another eject operation was in progress.
vmchange now returns a status code 223 (STATUS_ROBOT_BUSY) when another
eject operation is in progress. This problem primarily affected vault
eject operations.
--------------------------------------------------------------------------------
Etrack Incident = ET997925
Description:
Stream discovery would ignore the preprocess interval and use the default of
four hours. A change was made so that the preprocess interval is now passed
from Policy Execution Manager to the Job Manager and then to the parent job
(nbgenjob) on the command line using the -preprocessInterval option.
--------------------------------------------------------------------------------
Etrack Incident = ET1013849
Description:
The host list would be empty if a cluster node name was given instead of
virtual cluster name.
--------------------------------------------------------------------------------
Etrack Incident = ET1003608
Description:
Duplication to an FSE Nearstore storage unit failed if the
–stsdeletefiles process returned a status 1 (which is valid). A change
has been made that allows a duplicate to complete successfully if a
status 1 is encountered from -stsdeletefiles.
--------------------------------------------------------------------------------
Etrack Incident = ET1013509
Description:
A change was made to disable sorting on the Elapsed time and Active elapsed
time columns.
--------------------------------------------------------------------------------
Etrack Incident = ET1013882
Description:
Manual configuration of ACS libraries does not always record the library
serial number.
--------------------------------------------------------------------------------
Etrack Incident = ET1014147
Description:
In certain conditions a robotic daemon would become "UP" even though the
device monitor showed drives under AVR control.
--------------------------------------------------------------------------------
Etrack Incident = ET1010767
Associated Primary Etrack = ET990884
Description:
Immediate backups jobs would not initiate properly causing nbpem to return
the following statuses: msgsndd status = 0; send status 0; and bprd exit
status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET1016131
Description:
A change was made to implement support for Instant Recovery with Windows
FlashBackup policies.
--------------------------------------------------------------------------------
Etrack Incident = ET1014974
Associated Primary Etrack = ET892850
Description:
Backups written by 64-bit Linux servers were unreadable by non-64-bit Linux
servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1012144 ET1016961
Description:
Added support for a new Automated Cartridge System (ACS) vendor media and
drive type.
--------------------------------------------------------------------------------
Etrack Incident = ET1011704
Associated Primary Etrack = ET1015054
Description:
The robotic control daemon would not handle robots with more than
128 drives.
--------------------------------------------------------------------------------
Etrack Incident = ET1015612
Description:
Corrected an issue that would not allow you to write to disk and resulted
in an error code 84 (media write error).
--------------------------------------------------------------------------------
Etrack Incident = ET1018156 ET1016311
Associated Primary Etrack = ET1008244 ET1011211
Description:
The window checking routine would sometimes schedule jobs to run
multiple times in one window, or even skip a window.
--------------------------------------------------------------------------------
Etrack Incident = ET925285
Associated Primary Etrack = ET834682
Description:
Internationalization (I18N) issue: An issue existed that caused the content
of a notification e-mail to illegible.
--------------------------------------------------------------------------------
Etrack Incident = ET1017152
Associated Primary Etrack = ET1013059
Description:
If there are transient environmental hostname lookup issues, nbrb may
core dump near \"__nscd_get_map_ref\".
--------------------------------------------------------------------------------
Etrack Incident = ET1019073
Associated Primary Etrack = ET988955
Description:
TIR files that were than 2GB were not able to be read because the size was
stored in a 32-bit integer and the math used to turn that into a 64-bit
integer caused a large negative value to be stored on some platforms. This
maintenance pack contains a fix that contains explicit casts at appropriate
junctures. This issue was found on a Nearstore storage unit but would have
affected any disk storage unit if TIR was being used.
--------------------------------------------------------------------------------
Etrack Incident = ET1009036
Associated Primary Etrack = ET936732
Description:
A change was made to correct an nbpem core dump issue that occurred because
a null pointer was being passed to libc::strcmpstack.
--------------------------------------------------------------------------------
Etrack Incident = ET1020129
Associated Primary Etrack = ET1003895
Description:
It is possible for an NDMP restore to be successful and still produce a
status code 83 when media is write protected and spans media. The bptm
log will contain a messagesimilar to the following:
15:51:14.479 [6272.8404] <16> open_ndmp_device: cannot open ndmp device
nrst07a, error code 11 (NDMP_WRITE_PROTECT_ERR)
Workaround:
The restore completes successfully, so you can ignore the error status.
Or you can unmark the tape to make it write protected.
--------------------------------------------------------------------------------
Etrack Incident = ET1016884
Description:
Corrected the use of ejecting to the "any" cap (a function used by Vault)
when ejecting to ACS robotics. Also corrected use of -w option when
ejecting to ACS robotics from the command line.
--------------------------------------------------------------------------------
Etrack Incident = ET1015650
Description:
Lotus Notes user-directed backups were failing if the notes.ini path
specified through the user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1006573
Description:
A change was made so that the Managing -> Job Policies -> Details, user
backup & user archive policies are no longer shown twice.
--------------------------------------------------------------------------------
Etrack Incident = ET1012757
Description:
The server connection would fail while upgrading the Master
Server from NetBackup 60MP4 to NetBackup 60MP5 on a TRU64
system.
--------------------------------------------------------------------------------
Etrack Incident = ET1024918
Description:
Changes were added to resolve an intermittent pem core dump issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1021373
Description:
Corrected an issue that caused FlashBackup Windows single-file restores to
fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1022947 ET1062137
Associated Primary Etrack = ET984055
Description:
Status was being sent to the client after the stsdeletefiles
process was run. If that process took too long, the client
timed out. The backup was successful however the archive bits
on the client were not cleared, so the same files were backed
up in the next incremental, even though that was not necessary.
The result was that incremental backups were essentially running
as full backups.
--------------------------------------------------------------------------------
Etrack Incident = ET518074
Associated Primary Etrack = ET1009431
Description:
Upgraded the Sig Scheduler to 2.60.030 in this maintenance pack.
--------------------------------------------------------------------------------
Etrack Incident = ET1020081
Description:
A change was added so that when printDueJobs accesses the work list it will
lock the list to avoid potential issues with other threads trying to access
the work list.
--------------------------------------------------------------------------------
Etrack Incident = ET995592
Description:
Conversion of the policy include file-list entries failed resulting in
blank entries. A change was made to the nbproxy conversion code to use
language codeset setting of "utf8" for HP platforms, otherwise "UTF-8" for
all other platforms to prevent the conversion from returning an error saying
the input was invalid.
--------------------------------------------------------------------------------
Etrack Incident = ET1024066
Description:
Corrected a bpdm core dump that occurred with V_strverify on a Linux IA-64
System.
--------------------------------------------------------------------------------
Etrack Incident = ET1023729
Associated Primary Etrack = ET1027068
Description:
A storage unit update operation (from the NetBackup-Jave Administration
Console) will fail if the user is logged into the system using the node name
(not the virtual name).
Workaround:
To resolve this issue, use the virtual name.
--------------------------------------------------------------------------------
Etrack Incident = ET1027605
Associated Primary Etrack = ET1024835
Description:
ShadowImage snapshots failed on an AMS500 because the product
ID was set to DF6 and yet it was interpreted as a 9500.
Workaround:
To resolve this issue, set the Product ID to DF7 as the code
currently expects.
--------------------------------------------------------------------------------
Etrack Incident = ET1026332
Associated Primary Etrack = ET1018020
Description:
A restore attempt, using a duplicated copy of a standard backup image
that was duplicated using NDMP attached tape drive, would fail with exit
status 25 (cannot connect on socket). The failure occurred because bpdm
was started instead of bptm.
--------------------------------------------------------------------------------
Etrack Incident = ET1028083
Description:
The ltid reports that the user had configured more drives than they were
licensed for, when they were using multiple drive paths.
--------------------------------------------------------------------------------
Etrack Incident = ET1028405
Description:
A change was made to ensure that the Windows FlashBackup Policy Type is
disabled when the Advanced Client license key is not installed.
--------------------------------------------------------------------------------
Etrack Incident = ET1029379
Associated Primary Etrack = ET971543
Description:
For FlashBackup Windows incremental backups, the extents for named streams
associated with directories were not being examined and put in the bitmap.
--------------------------------------------------------------------------------
Etrack Incident = ET858201
Associated Primary Etrack = ET850921
Description:
A hot catalog backup with a large number of image catalog entries
can run out of memory.
Workaround:
For a temporary fix to the memory issue, contact Symantec Support and inquire
about Emergency Engineering Binaries (EEBs) that are available for this issue,
or perform an offline backup, or a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1028058
Description:
An incorrect group and ownership on a libdbjodbc9.so symbolic link file has
been corrected.
Additional Notes:
This change only affects HP-UX on RISC hardware.
--------------------------------------------------------------------------------
Etrack Incident = ET1026006
Description:
Under nb/idl/NBPolicyTypes.idl, many new fields were added for
NetBackup 6.5. This created problems for NOM 6.5 to support 6.0 MP5
masters. To avoid this issue, Symantec added the new fields in 6.0 MP5
as reserved fields which will resolve this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1028169
Description:
NetBackup will now be shutdown in runlevel 1 on Solaris systems.
--------------------------------------------------------------------------------
Etrack Incident = ET1032876
Associated Primary Etrack = ET963719
Description:
Changes were made to correct a Dr Watson error caused by bpbkar.
Bpbkar would cause a Dr Watson error on the client while backing up
encrypted files. The job consistently failed with an exit status 13
while backing up the following directory: E:\QuickBase\server\dbs\.
Files that were backed up were continuously changing. A third party
application would capture changes made from the end user (web user)
to a .delta file, the delta file was then written to the files in the
directory, "E:\QuickBase\server\dbs\", only after the user had closed
the web application. The .delta files were continuously changing, and
the changes made to the directory were approximately 10 gigabytes
an hour.
--------------------------------------------------------------------------------
Etrack Incident = ET1026986
Associated Primary Etrack = ET1005324
Description:
Cleaning jobs that were initiated because of a TapeAlert or frequency would
fail if they did not complete in six minutes.
--------------------------------------------------------------------------------
Etrack Incident = ET1036385
Associated Primary Etrack = ET1006915
Description:
A disk staging job that runs from one media server to another,
where the media server that is performing the write operation
is a UNIX system, will fail some of the jobs and/or hang.
Workaround:
To resolve this issue, create the following touch file on the
master server:
For UNIX:
/usr/openv/netbackup/NODTTSDUP
For Windows:
VERITAS\NetBackup\NODTTSDUP
--------------------------------------------------------------------------------
Etrack Incident = ET1035288
Description:
NetBackup 6.0 does not provide a way to perform device monitor queries for a
single media server. Users must sift through all servers' output for the
data needed. This maintenance pack adds the option -hostdevmon to the
vmoprcmd command line to provide a single server's device state.
--------------------------------------------------------------------------------
Etrack Incident = ET1040339
Associated Primary Etrack = ET1027138
Description:
Increased the drive ready timeout for TLD drives to 14 minutes to
incorporate a worst case scenario of 14 minutes for LTO drives in
an effort to remove bad media.
--------------------------------------------------------------------------------
Etrack Incident = ET1039797
Description:
When a full data directory is restored, the recovery was failing due to a
truncation of the database name.
--------------------------------------------------------------------------------
Etrack Incident = ET1038347
Associated Primary Etrack = ET996144
Description:
After a WOFB backup, bpbkar32 would clean up an active
FlashBackup- Windows snapshot - because PEM did not send the
SET SNAP_ID for snapshots that should be retained on the client.
Workaround:
To resolve this issue, reschedule the backups of the C: and D: drives so
that they start -and- complete at non-overlapping time periods
However, for some customers this is not practical because they may have
volumes that are in the range of 800GB ~ 1TB. In addition, some of their
servers may have more than one volume that needs to be protected using
Flashbackup
In this circumstance, Symantec suggests the customer sets the priority
of the C: drive backup to a higher value than the Flashbackup policy;
and then for the affected clients that are part of their Flashbackup
policies, using the Master Server Host Properties > Client Attributes >
Set Max jobs/client option and setting it to 1.
--------------------------------------------------------------------------------
Etrack Incident = ET1039117
Associated Primary Etrack = ET1038317
Description:
"bpmedia -movedb" starts bptm on the old server to move the media
database. If the old server and the new server are at NetBackup 6.0
(or post 6.0), then there is no need to start bptm. All the
operations can be done in bpmedia. This also helps the scenario
where one of the media server is offline or de-commissioned (and
all the steps for de-commissioning the media server are not followed).
--------------------------------------------------------------------------------
Etrack Incident = ET992572
Associated Primary Etrack = ET892420
Description:
The bppllist -allpolicies -U command would not return all policies.
In addition, when recreating the issue, an application fault
against bppllist was also found.
--------------------------------------------------------------------------------
Etrack Incident = ET1050190
Description:
Changes were made to correct the NetBackup 6.0 MP5 NetWare
build.
--------------------------------------------------------------------------------
Etrack Incident = ET1047982
Associated Primary Etrack = ET914734
Description:
The V_* functions would sometimes cause binaries with incorrect
signal handlers to core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET1050372
Associated Primary Etrack = ET1047809
Description:
Sybase 11.9.x backups no longer fail on HP-UX 11.00 after upgrading to
NetBackup 6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET1046813
Description:
Online catalog backup was failing with a status 50 when writing to a
password-protected DR path in an environment with NBAC installed.
Workaround:
To avoid this issue, store the DR file in a path which the running NetBackup
bpbdm process has write access to without changing credentials.
--------------------------------------------------------------------------------
Etrack Incident = ET1047911
Description:
A description of the new '-copy' option is missing from the bprestore
command line usage.
--------------------------------------------------------------------------------
Etrack Incident = ET1051657
Associated Primary Etrack = ET1045602
Description:
The NetBackup service layer (nbsl) would not start on a
master server using PA_RISC 1.1 architecture if nbsl was
compiled with PA_RISC 2.0.
--------------------------------------------------------------------------------
Etrack Incident = ET1050488
Description:
Corrected an issue that caused ltid to fault after it was started.
--------------------------------------------------------------------------------
Etrack Incident = ET1050393
Associated Primary Etrack = ET1036542
Description:
ACS robot pre-eject operations sometimes show volumes that are
NOT_IN_LIBRARY when they actually are. This is due to a buffer
length problem in the acsd robotic daemon. This primarily affects
Vault ejects to ACS robots.
--------------------------------------------------------------------------------
Etrack Incident = ET1052551
Description:
Intermittent issues were found when ejecting multiple CAP-fulls of
media with the latest ACSLS patch, PUT0701S.
--------------------------------------------------------------------------------
Etrack Incident = ET1051474
Description:
Some ACS_SDLT* media will not be mapped correctly to NetBackup media types
when specifying the mapping in vm.conf.
--------------------------------------------------------------------------------
Etrack Incident = ET1054463
Associated Primary Etrack = ET1039776
Description:
After changing the bp.conf SERVER entry from short name to FQDN
(or vice versa) and when performing a hot catalog backup with Vault,
the Vault job will fail with a status 294, even though the catalog
backup was successful.
Now, instead of using gethostname() results when vault performs a
validation, the client name (as configured in the policy) will be
used.
Workaround:
UNIX ONLY: In the imageDB directory, create a symbolic link between
FQDN and short names.
--------------------------------------------------------------------------------
Etrack Incident = ET1053444
Description:
A change was made that corrects a crash using bpplschedrep.
--------------------------------------------------------------------------------
Etrack Incident = ET1052430
Associated Primary Etrack = ET1032378
Description:
Added a fix to correct an nbjm crash in TAO_Transport::handle_input.
--------------------------------------------------------------------------------
Etrack Incident = ET1018993
Description:
On some SuSE 10 servers, when NetBackup asks the system if
it is the name listed as the EMM Server in the bp.conf file
at boot time, it incorrectly answers no. This correction asks
several times and usually the second attempt gives the correct
answer.
This causes a 55 second delay, with starting NetBackup daemons,
on SuSE 10 servers that are not MM Servers.
Workaround:
To resolve this issue, run the following start command after a
system has rebooted.
/usr/openv/netbackup/bin/goodies/netbackup
--------------------------------------------------------------------------------
Etrack Incident = ET1060972
Associated Primary Etrack = ET1038232
Description:
When Enterprise Vault performs backups to NetBackup using the
VxBSA file APIs, the backups can fail. Enterprise Vault posts
an event error entry saying Failed to send file (error 00000003:
System detected error, operation aborted.). Check the NetBackup
Activity Monitor.
Examination of the exten_client debug log shows that following
type of error being logged.
07:13:13.973 [9820.5196] <16> bsa_WriteFileList: ERR - filelist
file <C:\Program
Files\VERITAS\NetBackup\Logs\user_ops\dbext\logs\
vxbsa.1177038793.9820.5196.files.1> open() failed: Errno=24:
<Too many open files>
--------------------------------------------------------------------------------
Etrack Incident = ET1018093
Description:
An error occurred on a Windows setup that caused a failure to
occur when copying files.
--------------------------------------------------------------------------------
Etrack Incident = ET1047888
Associated Primary Etrack = ET1041180
Description:
The NDMP jobs' drives were sometimes pre-empted with a local
or incorrect drive path.
--------------------------------------------------------------------------------
Etrack Incident = ET1063773
Associated Primary Etrack = ET1063750
Description:
A crash in nbemm would occur if an inventory was attempted
while the database server was down. This would easily happen
if a site was performing a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1064798
Description:
A DB2 restore now has the ability to redirect a DB2 database
to a different owner from the original owner (both owners
being from the same group). A new backup of the source DB2
database is required so the correct group permission is on the
image to allow the alternate user to perform a restore to the
new instance, or database.
--------------------------------------------------------------------------------
Etrack Incident = ET1066935
Associated Primary Etrack = ET1062088
Description:
bpdbm crash can occur, during a recovery, if a damaged image
file exists prior to the recovery.
Workaround:
To avoid this issue, manually remove all damaged image files
before attempting a recovery.
--------------------------------------------------------------------------------
Etrack Incident = ET1066885
Description:
Listing storage unit groups were leaking memory. Changes were
added to resolve the memory leaks.
--------------------------------------------------------------------------------
Etrack Incident = ET1067176
Associated Primary Etrack = ET1001827
Description:
Jobs are not being cleaned from job database even after the
KEEP_JOBS_HOURS was run.
--------------------------------------------------------------------------------
Etrack Incident = ET1067996
Associated Primary Etrack = ET1058482
Description:
Changes were made to resolve memory leak issues in NBJM
and NBPEM.
--------------------------------------------------------------------------------
Etrack Incident = ET1070595
Description:
NOM no longer creates multiple NBProxy processes when there
is no job activity.
--------------------------------------------------------------------------------
Etrack Incident = ET1073038
Description:
An NetBackup EMM memory leak was detected in the xxxFetch()
implementation causing EMM to consume more memory over time.
Workaround:
To resolve this issue, restart the EMM process.
--------------------------------------------------------------------------------
Etrack Incident = ET1062791
Description:
Corrected an issue where the NetBackup Job Manager (NBJM) could
not be terminated and it had to be killed.
--------------------------------------------------------------------------------
Etrack Incident = ET1061742
Associated Primary Etrack = ET1058482
Description:
Added changes to correct a memory leak found in the NetBackup
policy execution manager (PEM).
--------------------------------------------------------------------------------
Etrack Incident = ET1066381
Associated Primary Etrack = ET1066374
Description:
The INCR frequency schedule would run multiple times within a
window with an incorrect snapid.
--------------------------------------------------------------------------------
Etrack Incident = ET1068635
Description:
The NetBackup service layer (NBSL) crashes on an HP-UX system.
Workaround:
To avoid this issue, default catch blocks were added to handle
all other exceptions in the Proxy client.
--------------------------------------------------------------------------------
Etrack Incident = ET1075834
Description:
An issue exited that caused jobs to remain queued when a
196 error should have occured.
--------------------------------------------------------------------------------
Etrack Incident = ET1076967
Associated Primary Etrack = ET1033590
Description:
A crash would sometimes occur in bpdbm when the cleanup process
was cleaning one of the images of a duplication, where the
duplication had failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1076060
Description:
The NetBackup PEM would terminate because of a timeout to the
nbproxy for getLastBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET1078998
Associated Primary Etrack = ET993531
Description:
The NetBackup Service Layer (NBSL) will not stay running and the
following error is produced.
Windows error 1063 - Windows SCM unable to start it as a service.
Workaround:
To avoid this issue, increase the service-registration timeout
from the Windows-registry.
--------------------------------------------------------------------------------
Etrack Incident = ET1078584
Description:
Running backups that have streaming enabled (and perform
incremental backups whose file list changes) may encountered
the following problem.
When stream discovery is done and some existing streams are shuffled
because new files are being added or existing streams being deleted,
the streams files are shuffled but the "lastbackup" time is saved for
the streams that remain. Therefore, when a new stream maps to a
preexisting stream with a date of zero (since there was no prior
backup) you want to avoid doing a query for "lastbackup" with that
stream number because it will return the "lastbackup" time for the
stream that was shuffled or deleted. If you avoid doing a query
for "lastbackup" when the date is zero you also keep the streams
from shuffling and the query returning a "lastbackup" time from a
different stream.
--------------------------------------------------------------------------------
Etrack Incident = ET1079359
Associated Primary Etrack = ET899380
Description:
A change was added that corrects a Status 805 error condition on
resubmitted, failed, multiple-data stream child jobs using snapshots.
--------------------------------------------------------------------------------
Etrack Incident = ET1079272
Associated Primary Etrack = ET1049382
Description:
AIX master servers were unable to restore Windows Flashbackup
images. This was because of a problem linking the VxMS libraries
in the AIX compile. A change has been added to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1083381
Description:
Policy Execution Manager would core dump when reading a policy because
of a configuration change event.
-------------------------------------------------------------------------------
Etrack Incident = ET1092076
Description:
NOM receives data from NBSL regarding changes in policy, storage units,
processes and services information, and so forth through events. When
the nbnos process is terminated, NBSL cannot deliver these events to NOM.
After restarting the nbnos process, the event delivery mechanism should
resume and NOM should continue to get data from NBSL, but it fails.
--------------------------------------------------------------------------------
Etrack Incident = ET1092060
Description:
When invoking the Device Configuration Wizard from the NetBackup-Java
Administration Console, a dialog box named "Device Configuration
Wizard - Initialization" shows the error "unknown error".
--------------------------------------------------------------------------------
Etrack Incident = ET1095578
Associated Primary Etrack = ET1094524
**Description:
If bpbrm/bptm terminates abnormally while executing multiple jobs and
another job is added to this multiplexed group by the Resource Broker, it is
possible that a data loss could occur.
================================================================================
============
Pack History
============
=========
NB_60_4_M
=========
--------------------------------------------------------------------------------
Etrack Incident = ET633295 ET617152 ET801824
Description:
Upgraded the version of Veritas Unified Logging (VxUL) to 1.3.7.2 to
enable users to recycle VxUL logs.
--------------------------------------------------------------------------------
Etrack Incident = ET633395
Description:
A change has been added that prevents bpduplicate from overwriting the
heap accounting information and causing the bpduplicate to crash by
copying a string into destination string that is too small.
--------------------------------------------------------------------------------
Etrack Incident = ET634272
Description:
Backup of multiple VxFS file systems using NetBackup's Advanced Clients
Frozen Image Backup method failed in close_vxfs_filesystem() of the
previous open VxFS checkpoint.
Workaround:
Backup one filesystem at a time for frozen image backups.
--------------------------------------------------------------------------------
Etrack Incident = ET638325
Description:
NetBackup log messages no longer show up in the /etc/security/password
file on AIX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET638699
Description:
The Policy Execution Manager (PEM) would crash while PEM was shutting down,
if it was shutting down at the same time a progress log was being updated.
--------------------------------------------------------------------------------
Etrack Incident = ET617254 ET617889 ET640121
Description:
Hot Catalog Backup would not backup images when IDIRSTRUCT equaled 1
because the code expected the master server had a second or later version
of the catalog image directory structure, for example, IDIRSTRUCT = 2.
In a UNIX cluster environment, the VAR_GLOBAL_PATH is linked to the shared
drive. The backup client (such as, bpbkar) does not follow symbolic links
currently and therefore the files inside the linked directory would not be
backed up in an online catalog backup.
Excessive bpdbm debug log entries were produced from a Hot Catalog Backup.
This fix ties the logging of libcatbackup debug messages to the following
setting.
BPDBM_VERBOSE setting.
Example of affected log message:
00:00:02.032 [8398] < 2> db_ImgUnlock: db_ImgUnlock(833d698) error(0)
--------------------------------------------------------------------------------
Etrack Incident = ET636334 ET636411 ET636414
Description:
The hot catalog backups would fail if the CRYPT_OPTION was set to REQUIRED
in bp.conf, where it could also be set through the GUI->Host Properties->
Clients->Encryption tab.
Workaround:
To avoid this issue, set CRYPT_OPTION to ALLOWED, which is the default.
--------------------------------------------------------------------------------
Etrack Incident = ET617892
Description:
For an imported catalog backup image, the command line instruction
"bprecover -r -nbdb" would not work because the parent image ID was
missing in imported ASA image header.
Workaround:
To avoid this issue, open the imported catalog image header file and
remove the PARENT_IMAGE_ID line so that the ASA and the catalog backup
image header files do not contain the field.
--------------------------------------------------------------------------------
Etrack Incident = ET642003
Associated Primary Etracks = ET841985
Description:
Changes were made to JobIMOMObject::CheckAndUpdateJobInfoData() in the
NetBackup Service Layer (NBSL) to correct a core dump situation.
--------------------------------------------------------------------------------
Etrack Incident = ET638313
Description:
The NetBackup Job Manager (NBJM) would crash when it received a message
from BPTM with a bad copy number.
--------------------------------------------------------------------------------
Etrack Incident = ET638320
Description:
The NetBackup Job Manager (NBJM) writes un-initialized data to the
JobParams file. When it reads the file again on a subsequent submission of
the job, it sometimes crashed because of un-initialized fields in the
JobParams file.
--------------------------------------------------------------------------------
Etrack Incident = ET638318
Description:
The NetBackup Policy Execution Manager (NBPEM) submitted a child job with
the option to inherit resources from the parent job after it released
resources from the parent job. The NBJM then crashed while trying to get
the resource from the parent job.
--------------------------------------------------------------------------------
Etrack Incident = ET633983 ET640407
Description:
Status 25 or 45 backup failures occurred under the following conditions:
- The master server is running NetBackup 6.0MP3.
- The media server is running NetBackup 5.x.
- The client is added to the NetBackup client database with the default
connect options.
Workaround:
To avoid this issue, explicitly set the connect_options value in the
client database to a value that is acceptable for a NetBackup 5.x version.
Do not use the default values:
admincmd/bpclient -update -client <client_name> -connect_options 0 0 2
--------------------------------------------------------------------------------
Etrack Incident = ET621772
Associated Primary Etracks = ET642018
Description:
Made changes to correct an NBSL core dump issue.
--------------------------------------------------------------------------------
Etrack Incident = ET642010
Description:
Changes were made to replace TreadSafeWrappers calls and to correct an
exception handling logic error in ServiceManagerCollector(). These issues
were causing a core dump issue in the NetBackup Service Layer (NBSL).
--------------------------------------------------------------------------------
Etrack Incident = ET628333
Description:
Mixing Dynamic Host Configuration Protocol (DHCP) clients and Dynamic Domain
Name Service (DNS) would cause potential data loss and security issues.
--------------------------------------------------------------------------------
Etrack Incident = ET627398
Description:
Hot catalog backup failed if the EMM server was installed on a remote
media server instead of on the master server, and BMR was installed on the
master server.
--------------------------------------------------------------------------------
Etrack Incident = ET579341
Description:
Added Encryption support to x64 NetBackup hosts.
--------------------------------------------------------------------------------
Etrack Incident = ET641058
Associated Primary Etracks = ET641055
Description:
A condition existed that caused NetBackup Service Layer (NBSL) to core
dump in HostSessionImpl::ping().
--------------------------------------------------------------------------------
Etrack Incident = ET638703
Associated Primary Etracks = ET638702
Description:
The NetBackup Policy Execution Manager (nbpem) process deadlocked while
doing bpexpdate -deassignempty -force >/dev/null.
--------------------------------------------------------------------------------
Etrack Incident = ET617887
Description:
An attempt to restore from a True Image Recovery (TIR) backup to tape after
the TIR data had been pruned from the catalog would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET630777
Associated Primary Etracks = ET630772
Description:
A change was made to the Policy Execution Manager to auto retry Vault jobs
on Status codes EC_vc_EjectFailed (287), EC_vc_EjectPartialSuccess (288),
and EC_vc_PartialSuccess (306). If one image failed to duplicate, Vault
would return a status 306. Also changed the parent job (nbgenjob) to
validate the image for a Vault job that returned an error status 306, 287,
or 288.
--------------------------------------------------------------------------------
Etrack Incident = ET618696
Description:
The following error would occur when trying to apply a patch when running
nbdb_upgrade:
Verifying the running version of NBDB ...
***** SQL error: Database server not found
Failed system call, '/usr/openv/db/bin//nbdb_unload -dbn NBDB -s /tmp'
Verification Failed.
When connecting to Sybase ASA using Open Database Connectivity (ODBC),
shared memory connections used space in /tmp by default. If there were
issues creating files in /tmp, the connection would fail. To resolve this
issue, the environment variable, ASTMP, is now set to /usr/openv/tmp.
--------------------------------------------------------------------------------
Etrack Incident = ET636795
Description:
Added the capability to do a step-wise downgrade of the NetBackup
Relational Database schema. This enables you to uninstall one or more
maintenance patches in the order in which they were applied.
--------------------------------------------------------------------------------
Etrack Incident = ET621857
Description:
Unable to create or modify disk staging storage units using the
NetBackup-Java Administration Console if a NetBackup 5.x system was
upgraded to NetBackup 6.0 or if a NetBackup 5.x license key was used
during a NetBackup 6.0 server installation.
This pack corrects this issue and enables you to create or modify disk
staging storage units using the NetBackup-Java Administration Console
if a NetBackup 5.x system is upgraded to NetBackup 6.0 using the 5.x
license or you could update to a NetBackup 6.0 license key.
--------------------------------------------------------------------------------
Etrack Incident = ET644627
Description:
On the active node, if the user has installed this pack on a secure
VCS Windows cluster environment that has a NetBackup server with EMM,
and are observing that NetBackup does not come online, the Enterprise
Media Manager (EMM) database schema did not update properly.
Workaround:
To avoid this issue, perform the following steps:
1. Take the NetBackup Server resource offline.
2. Freeze the NetBackup Service group.
3. Make sure that the Adaptive Server Anywhere – VERITAS_NB service is
started.
4. Execute the following command.
<install dir>/NetBackup/bin/nbdb_upgrade.exe –dbn NBDB
5. Execute the following command.
<install dir>/NetBackup/bin/admincmd/bpsyncinfo.exe
-add_paths NETBACKUP_RELATIONAL_DATABASE_FILES
6. Unfreeze the NetBackup Service group.
7. Bring NetBackup Server resource back online.
If you have experienced this issue on the install then you will also
experience it on the uninstall from the active node.
--------------------------------------------------------------------------------
Etrack Incident = ET636799
Description:
An error would occur when mixing FULL, Differential Incremental, and Vault
schedules in the "Hot_Catalog" backup policy. For example, if a Vault
schedule ran, followed by a Differential schedule (without any other jobs
running in between the two), the result would be the following:
JobID X = Catalog "Control" Job - Ends with Status 2
JobID X+1 = Differential Incremental Catalog Job - Ends with Status 227
--------------------------------------------------------------------------------
Etrack Incident = ET644077
Description:
In NetBackup 4.5, netbackup.dll was installed in the
C:\Program files\CommonFiles\VERITAS\Shared Directory. The NetBackup 6.0 GA
installer did not remove the old version of the file.
--------------------------------------------------------------------------------
Etrack Incident = ET618372
Description:
A change was made so that bpstsinfo correctly passes the
-filteronimagemodetype flag when used with the -remote flag.
--------------------------------------------------------------------------------
Etrack Incident = ET645645
Associated Primary Etracks = ET645697
Description:
A condition existed that caused the NetBackup resource Broker (nbrb) to
core dump under heavily loaded conditions. This problem had occurred
on AIX and HP-UX. There was lot of locking and unlocking involved in the
area where the resource broker (RB) sends the resources to the job manager.
RB was using reverse lock provided by ACE. Either RB was not using the
lock correctly or there was some issue in the ACE's implementation of
reverse lock which caused this core dump. To address the issue, the
lock/unlock logic was simplified.
--------------------------------------------------------------------------------
Etrack Incident = ET617893
Description:
TIR-enabled backups (including FlashBackup and NDMP) could fail in the
validation phase of the backup because of a miscalculated file size. This
patch provides earlier detection of the error and improved reporting on the
cause of the error.
--------------------------------------------------------------------------------
Etrack Incident = ET641172
Description:
Online catalog backups in configurations with cluster 5.x media servers
were creating a bpbackupdb process that looped infinitely.
--------------------------------------------------------------------------------
Etrack Incident = ET628709
Description:
A change was made so that EMM now verifies that all nodes in a cluster are
configured either as masters or media servers. EMM should not allow
media-master configurations among the cluster nodes.
--------------------------------------------------------------------------------
Etrack Incident = ET646623
Associated Primary Etracks = ET849324
Description:
The default method for NetBackup ODBC connections to the NetBackup database
(NBDB)/EMM database is to use shared memory followed by tcpip if shared
memory fails. This is controlled by the LINKS=shmem,tcpip{PORT=13785}
parameter in the database connection string.
On some platforms, there have been intermittent issues with shared memory
connections to the Sybase ASA database.
To work-around this issue, a new parameter has been aded to the vxdbms.conf
dfile to set the LINKS parameter in the connection string. To change this
parameter to only use tcpip connections, the following line
was added to vxdbms.conf:
VXDBMS_LINKS = tcpip{PORT=13785}
The vxdbms.conf file is located in /usr/openv/db/data (UNIX) and
InstallPath\VERITAS\NetBackupDB\data (Windows).
--------------------------------------------------------------------------------
Etrack Incident = ET641145
Description:
A problem existed that caused, in a few rare cases, f-list files in the
catstore subdirectories to have a mixed set of UNIX-style and Windows-style
path separators or even incorrect path entries. The code currently assumes
only one style of path separator was being used which caused problems for
hot catalog backup.
On Windows master servers this results in a partially successful
(status 1) hot catalog backup job.
On UNIX or Linux master servers this results in a failed (status 67)
hot catalog backup job on patch levels prior to MP4 and in a partially
successful (status 1) hot catalog backup job on patch levels MP4 and
later. (UNIX or Linux master servers are now consistent with Windows
master servers in the status for this condition.)
A message similar to the following should be seen in the bpbkar debug log
if this bug is encountered:
ERR - Unable to expand hot catalog backup directive: CATALOG_BACKUP
Workaround:
It is reasonably straightforward to manually identify, edit, and correct
the offending f-list files to avoid this problem.
--------------------------------------------------------------------------------
Etrack Incident = ET593700
Description:
Added a check so that any backups going to a file system export-enabled
Nearstore storage unit must have TIR enabled. This is because the
sts_delete_files process, which is part of the file system export backup,
requires the TIR data.
--------------------------------------------------------------------------------
Etrack Incident = ET632204
Description:
Media locations in ACS robotics were not updated properly after dismount
or during inventory when moving from standalone to robotic.
--------------------------------------------------------------------------------
Etrack Incident = ET644756 ET702144
Description:
In cases where a user authenticated against a non-root broker a failure to
load a credential from disk could occur. This would result in false
negative access checks for users leading to a Backup, Archive, and Restore
user interface rather than the NetBackup Administration console.
Workaround:
To avoid this issue, authenticate against the root broker on the master
server rather than another broker.
--------------------------------------------------------------------------------
Etrack Incident = ET630539
Description:
Corrected the vm.conf mapping of the ACS T10000 media types to HCART2.
--------------------------------------------------------------------------------
Etrack Incident = ET500024
Associated Primary Etracks = ET838966
Description:
Oracle backups no longer fail with a NetBackup status 227.
--------------------------------------------------------------------------------
Etrack Incident = ET646981
Description:
The NDMP agent caused a Dr. Watson error and a DUMP file when backing up
one volume.
This happens only on Windows and only when NDMP logging is enabled.
The problem is caused by "invalid" mtime/atime/ctime values sent by the
filer in the file history. This is not a normal situation.
Workaround:
To avoid this issue, turn NDMP logging off. This problem only occurs if
NDMP logging is enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET635017
Associated Primary Etracks = ET635016
Description:
Due to a memory management issue, the Volume Manager Daemon could
crash during certain media management operations.
--------------------------------------------------------------------------------
Etrack Incident = ET646985
Description:
NDMP backups failed with a status 84 when writing a TIR fragment.
The bptm log showed an error where the expected block position is one off.
This error occurred in the function write_data_tir().
Workaround:
To avoid this issue, add the following line to the file
<installdir>/netbackup/db/config/ndmp.cfg
NDMP_MOVER_CLIENT_DISABLE
This will have a minimal impact on backups. However it will cause a
significant performance impact to dup/verify/import when using
NDMP drives.
--------------------------------------------------------------------------------
Etrack Incident = ET640207
Description:
Allow the end user to specify pool numbers when creating a new volume pool.
A new option (-pnum) was added to the vmpool command to facilitate this.
The new usage is:
vmpool [-pnum <pool number>] -add <pool_name> "<description>" <host> <uid>
<gid>
The -pnum option must be specified before the -add option. The -pnum has
no effect when the -change option is specified.
--------------------------------------------------------------------------------
Etrack Incident = ET627870
Description:
The image will not be closed correctly and a data loss will occur during
duplication or staging where the following is true:
- The destination storage unit (STU) is a volume on a Nearstore with
version 7.2 of ONTAP.
- The disk storage unit option for 'enable block sharing' is set.
The first duplication or DSSU_POLICY backup to the Nearstore will complete
successfully, but subsequent operations using that image (such as, restore
and incremental backups) will not succeed.
--------------------------------------------------------------------------------
Etrack Incident = ET630303
Description:
If there was an error in a scheduled report, the report that caused the
error would not appear in the corresponding email.
--------------------------------------------------------------------------------
Etrack Incident = ET612141
Description:
The "File System Export" button on the Storage Unit dialog will be
available when NetBackup media server 6.0MP3 or higher version is
connected to a 7.2 ONTAP Nearstore or higher version as a
7.1 ONTAP Nearstore cannot export a file system.
--------------------------------------------------------------------------------
Etrack Incident = ET640456 ET632241 ET630393 ET632790
Associated Primary Etracks = ET640453
Description:
The nbpem showed scalability problems because of a recomputation of a
job’s due-time when not necessary. In addition, the internal queue
management was a single thread trying to handle multiple queues, which
caused long waits to process requests on some of the queues.
--------------------------------------------------------------------------------
Etrack Incident = ET641156
Description:
Hot catalog backup jobs fail with status 29 on Linux platforms.
In reality the backup did succeed, but the status is not being recorded
correctly resulting in the failed backup job.
Messages similar to the following will be seen in the admin debug log,
which show that the internal CLI used for the hot catalog backup job
did complete successfully:
<2> bpbackupdb: INITIATING: NetBackup 6.0
<2> logparams: -vxss -pjobid 672 -nodbpaths ...
<2> bpbackupdb: EXIT status = 0
But as message similar to these in the bpdbm debug log will indicate,
bpdbm thinks that the CLI operation failed:
<16> exec_vxss_backup: OVsystem(bpbackupdb -vxss -pjobid 672 -nodbpaths ...)
<16> exec_catalog_backup: exec_vxss_backup() failed (29)
--------------------------------------------------------------------------------
Etrack Incident = ET648677
Associated Primary Etracks = ET639374
Description:
The nbpem showed jobs were due but not queued.
--------------------------------------------------------------------------------
Etrack Incident = ET419599
Description:
NetBackup could get an error 130 when backing up VxFS file systems on AIX
platforms that were mounted under non-VxFS file systems that had Access
Control Lists (ACLs)on them.
--------------------------------------------------------------------------------
Etrack Incident = ET638703
Associated Primary Etracks = ET638702
Description:
Changes were made to keep nbpem from hanging or suspending on a
start_bpexpdate.
--------------------------------------------------------------------------------
Etrack Incident = ET649692 ET636127
Description:
Changes were incorporated to address slow start times on user backups.
--------------------------------------------------------------------------------
Etrack Incident = ET646015
Associated Primary Etracks = ET644582
Description:
Changes were made to fix an NBSL core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET641162 ET649541
Description:
Some new image data fields added in NetBackup 6.0 were missing in the
image index file and therefore an online catalog backup job could fail
if the image index feature was enabled for the master server. (The image
index feature was enabled by the "bpimage -create_image_list -client
<master-server-name>" command line utility.)
Running bpexpdate to change the expiration of a phase I imported image
could cause it to be deleted if the backup spans tapes AND the first
tape has not yet completed phase II of the import process.
Workaround:
To avoid this issue, do not enable the image index feature for the master
server (for example, do not run bpimage -create_image_list -client
<master-server-name>"). If the image index feature has already been
enabled for the master server, apply this patch or contact technical
support for assistance in disabling the image index feature for the
master server by removing the IMAGE_* files from the
/usr/openv/netbackup/db/images/<master-server-name> directory to disable
the image index feature for the master server.
--------------------------------------------------------------------------------
Etrack Incident = ET645336
Associated Primary Etracks = ET644082
Description:
The NBJM returns a normal status to NBPEM after the request to resubmit a
job failed.
--------------------------------------------------------------------------------
Etrack Incident = ET699915
Description:
When a backup failed and went from an incomplete to a failed state,
the child job would not run again. The Policy Execution Manager
would not run child jobs after a failure due to the Job Manager changing
the job type from a resume to a restart.
--------------------------------------------------------------------------------
Etrack Incident = ET699915
Description:
When a backup failed and went from incomplete to a failed state,
the child job would not run again.
--------------------------------------------------------------------------------
Etrack Incident = ET700003
Description:
A disk staging storage unit (DSSU) relocation job failed with a status 96,
in spite of available media.
--------------------------------------------------------------------------------
Etrack Incident = ET700745
Description:
Multiplexed restore jobs would possibly fail when the number of active
jobs reached the maximum of 32. When this error occurred, the bptm log
would have an entry similar to the following:
12:21:15.296 [3471] <16> bct_find_nonactive: FATAL - cannot find
non-active Backup Control Table entry
--------------------------------------------------------------------------------
Etrack Incident = ET626205
Description:
Added a call to Sybase's dbvalid command when NBDB or BMRDB databases
were started after a cold catalog backup, catalog recovery, or by
nbdb_admin -start. In addition, added an nbdb_admin -validate
option to call dbvalid at any time.
--------------------------------------------------------------------------------
Etrack Incident = ET700802
Description:
Prepare to restore failed on an AIX client if a volume group contained a
disk or disks that were multi-pathed.
--------------------------------------------------------------------------------
Etrack Incident = ET617061
Description:
Changes were made to ensure that NBSL no longer core dumps in
JobIMOMObject::CheckAndUpdateJobInfoData().
--------------------------------------------------------------------------------
Etrack Incident = ET644612
Description:
The VCS agent and configuration scripts were added for the following
platforms:
- HPIA64
- Linux64
Additional Notes:
To configure and run NetBackup as a VCS clustered application on
HPIA64 and Linux64 platforms, the base NetBackup must be installed along
with this patch. Without this patch, cluster configuration cannot be
performed on these platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET621934
Description:
When two or more DSSUs fill up, they are unable to independently reclaim
disk space. This could cause additional backup jobs to fail (error 129) to
these two unrelated DSSUs if space reclamation took too long.
--------------------------------------------------------------------------------
Etrack Incident = ET632300
Description:
The tpconfig manual user interface would not successfully add shared
robot/drives.
--------------------------------------------------------------------------------
Etrack Incident = ET627293 ET617051
Description:
The NetBackup Service Layer (NBSL) no longer core dumps when failing
over the cluster or if NBSL creates zombie threads.
--------------------------------------------------------------------------------
Etrack Incident = ET703004
Associated Primary Etracks = ET647573
Description:
If NetBackup Access Control (NBAC) was enabled prior to an upgrade
from 6.0GA (or 6.0MP1) to 6.0MP2, any non-Administrator, non-root
users in the NBU_Security Admin Group would lose their Access Control
privileges after the upgrade.
Workaround:
There are three workaround options available to you, that you can use
to avoid this issue:
First workaround option:
------------------------
Add the Non-admin user to the “Security Administrators” group in
VxAZ. To do this, perform the following steps:
1. Open the VxSS user interface (/opt/VRTSat/bin/runvssatgui.sh
2. Open the appropriate Authorization Server (top right button).
Connect to it using root.
3. Select the “Authorization Groups” button on the left panel.
4. Select the “Security Administrators” group in the tree.
5. Select the menu option Authorization > Authorization Groups >
Add Member.
6. Add the non-Admin user using the dialog that appears.
7. The non-Admin user should now have the necessary permission.
This should not circumvent any other security because this
user now has security privileges on VxAZ. If this is not
appropriate, contact Symantec Support for help in taking other
other measures, such as read-only access to Security
information.
Note: The non-Admin user SHOULD have permission without
taking this step.
Second workaround option:
------------------------
Uninstall the VxAZ installation and reinstall. Re-configure NBAC by
Running “bpnbaz –SetupSecurity <server>” and the appropriate
“bpnbaz –AllowAuthorization” commands.
Note: This option will cause any customization to be lost.
Third workaround option:
------------------------
Only use Admin users for Security Operations.
--------------------------------------------------------------------------------
Etrack Incident = ET621194
Description:
Hot Catalog Backups were not cleaning old logs in the
/usr/openv/netbackup/logs/user_ops/dbext/jobs and
/usr/openv/netbackup/logs/user_ops/dbext/logs folders.
--------------------------------------------------------------------------------
Etrack Incident = ET649659
Description:
A change has been made that makes it possible to correct old EMM database
entries in the device mappings file.
--------------------------------------------------------------------------------
Etrack Incident = ET703078
Associated Primary Etracks = ET648013
Description:
The Device auto-discovery wizard and acstest displayed only some of the
tape drives.
Additional Notes:
The problem only happened to a robot with a large number of drives.
--------------------------------------------------------------------------------
Etrack Incident = ET704572
Associated Primary Etracks = ET771586
** Description:
BPTM would overwrite a valid image if a backup was canceled during a
fragment break. This issue effected HP-UX and AIX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET703493
Description:
Changes were made to correct an error string collision that prevented the
L10N tools from working.
--------------------------------------------------------------------------------
Etrack Incident = ET704578
Description:
A change was added to correct an incorrect log message in the NetBackup
Tape Manager during a media expiration operation.
--------------------------------------------------------------------------------
Etrack Incident = ET648724 ET631626
Associated Primary Etracks = ET699996
Description:
Changes have been made for various problems that include named streams
associated with directories, and performance issues. In addition, these
changes fix a problem with an HP master that was not able to load the
restricted version of libxm.
--------------------------------------------------------------------------------
Etrack Incident = ET703215 ET771306
Description:
A change has been implemented that allows a local client install of a
Macintosh platform as well as other non-server platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET704832
Associated Primary Etracks = ET704822
Description:
When using virtual storage units and after a cluster application failover,
the active node was not being set correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET640484
Associated Primary Etracks = ET640481
Description:
When Endpoint_Selector tries to connect to profile_in_use () it is possible
that another thread closes the connection and resets profile_in_use.
--------------------------------------------------------------------------------
Etrack Incident = ET704957 ET704961 ET704980 ET704977
Description:
Changes have been made to correct issues relating to duplicate log message
numbers as well as a Linux loader problem.
--------------------------------------------------------------------------------
Etrack Incident = ET648557
Description:
Excessive resource usage no longer occurs during synthetic backups.
--------------------------------------------------------------------------------
Etrack Incident = ET704640 ET632758 ET763828
Associated Primary Etracks = ET610208 ET703589
Description:
If failure history was exceeded, it would recalculate jobs and continue to
retry; thus, not starting the children jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET609542
Description:
Certain VSP binaries were being laid down, even though VSP was not
installed on the machines. A check has been added to see if the VSP key
exists before laying down the binaries.
--------------------------------------------------------------------------------
Etrack Incident = ET538815 ET525797
Associated Primary Etracks = ET773470
Description:
The following two issues have been resolved:
- Systems that are up more than three days, no longer become unresponsive
on MSCS systems running NetBackup 6.0.
- Changes have been made to nbemm and nbrb processes to eliminate core
dumps when running with NBAC.
--------------------------------------------------------------------------------
Etrack Incident = ET766069
Description:
The NetBackup Job Manager (NBJM) had deallocated the resources of a
parent job because they were not consumed in time because the NetBackup
Policy Execution Manager (NBPEM) took longer to submit the first child.
This resulted in status 50 and status 801 errors. (Status 50 is a parent
job end error and status 801 is a children end error.)
--------------------------------------------------------------------------------
Etrack Incident = ET647920
Associated Primary Etracks = ET646600
Description:
A problem with the bpstsinfo -UPDATE command has been corrected and it
no longer causes a core dump when creating threads.
--------------------------------------------------------------------------------
Etrack Incident = ET764906 ET783411
Associated Primary Etracks = ET795340
Description:
Using the catalog archive process, files were not being removed from the
catstore directory. In addition, running the catalog archive process while
an online catalog backup was in process could have caused the catalog
backup to fail.
Additional Notes:
A new option, "-remove_dotf", has been added to the bpcatarc command. This
option eliminates the need to pipe the output from bpcatarc to bpcatrm to
remove .f files. If the new option is not used, you must continue to pipe
the output from bpcatarc to bpcatrm to remove .f files.
--------------------------------------------------------------------------------
Etrack Incident = ET768361
Associated Primary Etracks = ET768272
Description:
update_clients -Install_ADC no longer fails if the client HOME is something
other than /.
--------------------------------------------------------------------------------
Etrack Incident = ET633295 ET620589 ET767219 ET771458
Description:
Log Recycling enables NetBackup users to control the amount of disk space
that is used for logs. Prior to this change, the disk could fill with
log files.
Previous options available for controlling disk use was available via
either 1) user intervention with the vxlogmgr –d command, 2) a cron job
that called vxlogmgr -d, or 3) the ‘Keep Logs’ setting in the
NetBackup-Java Administration Console. These options were often inadequate
because they are time-based pruning, while VxUL log recycling is
continuous. Often, time-based pruning has been inadequate because the log
files filled the disk before the time-based pruning has chance to execute.
For more detailed information about Log Recycling, refer to the following
TechNote on the Symantec Support Web site.
http://entsupport.symantec.com/docs/279590
--------------------------------------------------------------------------------
Etrack Incident = ET766166
Description:
Block-level incremental (BLIB) backups were not working with the SAP
database agent.
--------------------------------------------------------------------------------
Etrack Incident = ET768448
Description:
Could not manually create NDMP or Media Manager storage units using the
NetBackup-Java Administration console. Using the bpstuadd –nodevhost
command would return the message, “Remote Media Servers not allowed for
NetBackup Server”.
--------------------------------------------------------------------------------
Etrack Incident = ET768441
Description:
vmphyinv no longer fails while changing media residence.
--------------------------------------------------------------------------------
Etrack Incident = ET769421
Description:
When selecting the preferred machine name for a cluster node, which will
be stored in the EMM database, ignore any REQUIRED_INTERFACE entries in
vm.conf or bp.conf (Registry on Windows).
Workaround:
To avoid this issue, remove the REQUIRED_INTERFACE entries from vm.conf and
bp.conf (Registry on Windows) before installing NetBackup 6.0. This only
pertains to cluster environments.
--------------------------------------------------------------------------------
Etrack Incident = ET768457
Description:
The nbemmcmd –deletehost command no longer fails if a storage unit is set
to, "Any Available Host".
--------------------------------------------------------------------------------
Etrack Incident = ET767144
Associated Primary Etracks = ET767131
Description:
No longer receive “Allocation Failed” errors when trying to connect to the
Activity Monitor. This occurred for all users using the Java Activity
Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET769437
Description:
A previous change was made to bpduplicate which could in some instances
result in creating a command string which bpdm could not parse. This
caused duplication to fail. This problem only existed for NearStore
storage units.
--------------------------------------------------------------------------------
Etrack Incident = ET649747
Associated Primary Etracks = ET648871
Description:
User-directed archives no longer delete files if warnings are generated
during the backup portion of the operation.
--------------------------------------------------------------------------------
Etrack Incident = ET770672
Description:
Storage unit changes could cause policy execution manager (PEM) to receive
unnecessary event notifications which would impact PEM performance.
--------------------------------------------------------------------------------
Etrack Incident = ET413513
Description:
For a policy that used wildcards (such as, *) in the file list and enabled
multiple data streams, NetBackup would not include any dot files (such as,
.rhosts) at that directory level in the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET769378
Description:
If the Hot Catalog Backup encountered an image catalog that was corrupted,
it would stop the hot catalog backup at that point and finish immediately
with an error code of 67 (file list read failed).
Now it continues past the corrupted image catalog, and backs up the rest of
the catalog, and finishes with a partial success status of 1.
Workaround:
To avoid this issue, fix the corruption in the image catalog, or take a
cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET767294
Associated Primary Etracks = ET763625
Description:
A new entry "MediaBlockSize" is provided in the nbsl.xml file to configure
fetch size. This option is useful for congested TCP/IP networks, where the
default fetch size of 1000 could fail.
--------------------------------------------------------------------------------
Etrack Incident = ET593547
Description:
The media_deassign_notify notification script, added to the
<install_path>/netbackup/bin/goodies directory, will execute if it is
moved into the <install_path>/netbackup/bin directory. This script is
executed every time a media is deassigned.
--------------------------------------------------------------------------------
Etrack Incident = ET774846 ET805115 ET818780 ET831242
Associated Primary Etracks = ET621934
Description:
On large file systems with a large number of images, disk staging would not
free space fast enough to prevent concurrent backups from failing with 129
errors.
Additional Notes:
When a backup to a disk storage unit with staging completes, the percent
used is compared with the high water mark. If the percent used is equal to
or greater than the high water mark, a bpdm process will be invoked which
will remove staged images until the low water mark is reached.
To disable this behavior, create the "IGNORE_HIGH_WATER_MARK" touch file in
the netbackup/bin directory.
--------------------------------------------------------------------------------
Etrack Incident = ET768910
Associated Primary Etracks = ET763868
Description:
update_clients did not recognize the invalid parameter Install_java. A
change to the parameter check has been made to catch this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET645067
Associated Primary Etracks = ET645064
Description:
Sun Cluster agent was reporting the following error when failing over the
resource group.
“Failed to retrieve the resource type handle: invalid resource type”
--------------------------------------------------------------------------------
Etrack Incident = ET770159
Description:
To determine the NetBackup server version, bpexpdate, bpdbm, and some other
components were using bpcd protocol. If one of the servers is down, it may
take a long time. In addition, the error handling of the failure was not
appropriate.
A change has been made to fetch the NetBackup server version from the EMM
database. This is a fast and more reliable way to determine NetBackup
server versions.
--------------------------------------------------------------------------------
Etrack Incident = ET770650
Description:
Changes have been made to correct various compile warnings.
--------------------------------------------------------------------------------
Etrack Incident = ET776562
Description:
The Problem’s Report shows, "SO_REUSEADDR failed, errno = 0, No error".
--------------------------------------------------------------------------------
Etrack Incident = ET772419
Description:
During normal termination using the bpdown command (on Windows), PEM's
JobScheduler::terminate was not called. This casued PEM to hang while
waiting for the Connection Factory to be closed and eventually lead to a
crash.
--------------------------------------------------------------------------------
Etrack Incident = ET777370
Associated Primary Etracks = ET649531
Description:
"bpstsinfo -UPDATE" no longer hangs on an exit.
--------------------------------------------------------------------------------
Etrack Incident = ET699903
Description:
Tapes that were not full were sometimes mistakenly ejected from standalone
drives after jobs completed.
--------------------------------------------------------------------------------
Etrack Incident = ET773419
Description:
Changes were added to fix warning errors when compiling jobmgr on
HP-UX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET772287
Description:
Changes were made to fix issues where synth backups were failing when going
to a File system, export-enabled, NearStore storage unit because they did
not "admit" to being TIR enabled even if the policy they are run out of is
TIR enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET768443
Description:
The user was able to change the pool type of the default none, NetBackup,
DataStore, and Catalog backup pools. This fixes the problem from the
server side.
--------------------------------------------------------------------------------
Etrack Incident = ET776697
Description:
Duplication failed if VERBOSE=5 was set and the destination storage unit
was a tape.
This problem was introduced by a previous fix in this pack and does not
exist in any released software.
Workaround:
To avoid this issue, do not set VERBOSE equal to 5.
--------------------------------------------------------------------------------
Etrack Incident = ET770273
Description:
Wildcard matching in image keywords does not work.
--------------------------------------------------------------------------------
Etrack Incident = ET777616
Description:
Failing synthetic backups would unintentionally perform a catalog cleanup
instead of deleting the single failed backup image.
--------------------------------------------------------------------------------
Etrack Incident = ET771311
Description:
Changes were made to resolve several small memory leaks that were possible
in infrequently encountered scenarios.
--------------------------------------------------------------------------------
Etrack Incident = ET773473
Description:
Added support for Linux, Red Hat 4, and SuSE 9, on Power PC from IBM.
Normal UNIX client support for these client types is also covered with
this maintenance pack.
File system support is limited to EXT2, EXT3, ReiserFS on SuSE SLES 9, and
NFS. Files that are greater than 2 Gigabytes are supported. Local user
interfaces are available through the command line or the menu interface
(using the bp command). Remote access is the same as all other UNIX
clients.
For the client binaries to be installed from the UNIX patch you must first
create the following directories:
/usr/openv/netbackup/client/Linux/IBMpSeriesRedHat2.6
/usr/openv/netbackup/client/Linux/IBMpSeriesSuSE2.6
The binaries for the Encryption licensed feature are available through
the Encryption patch. For the Encryption binaries to be installed from
the UNIX Encryption patch you must first create the following directories:
/usr/openv/netbackup/crypt/Linux/IBMpSeriesRedHat2.6
/usr/openv/netbackup/crypt/Linux/IBMpSeriesSuSE2.6
For additional information about Encryption, refer to the NetBackup
Encryption readme.
--------------------------------------------------------------------------------
Etrack Incident = ET579398 ET775062
Associated Primary Etracks = ET701785 ET701785
Description:
Synthetic Backup no longer fails when a component image spans tape volumes.
--------------------------------------------------------------------------------
Etrack Incident = ET774704
Associated Primary Etracks = ET774649
Description:
Restores of backups for clients that had FlashBackup policies (either alone
or in combination with other policy types) were slow to become active and
mount tapes.
--------------------------------------------------------------------------------
Etrack Incident = ET770151
Description:
The “bpexpdate –recalculate –backupid –ret” command correctly changed the
expiry date of an image, but not the image retention level.
--------------------------------------------------------------------------------
Etrack Incident = ET772390
Description:
In some scenarios, the NetBackup Resource Broker (NBRB) was orphaning
resources while waiting for tape span and then deallocating those
resources. This caused an erroneous job termination.
--------------------------------------------------------------------------------
Etrack Incident = ET775684
Description:
Vaulting (bpduplicate) failed with the second image in a batch job with a
“resource request failed” message.
Workaround:
This problem may occur if images are on media with an ID of less than six
characters. To avoid this issue, use six-character media ID’s.
--------------------------------------------------------------------------------
Etrack Incident = ET775681
Description:
Increased the mount timeout for TLH drives to accommodate drive cleaning by
the library between mounts.
--------------------------------------------------------------------------------
Etrack Incident = ET775677
Description:
Changes have been made to enable NetBackup to control TLH robotics with up
to 512 drives.
--------------------------------------------------------------------------------
Etrack Incident = ET775429
Description:
Changes were made to correct error message for invalid media type mapping.
--------------------------------------------------------------------------------
Etrack Incident = ET775427
Description:
Changes were added to correct syslog messages to print appropriate
information.
--------------------------------------------------------------------------------
Etrack Incident = ET775428
Description:
Resolved an issue with the TLD inventory with the empty_map option set by
correcting the algorithm so that if only the last slot is open, it can
still be used without failing.
--------------------------------------------------------------------------------
Etrack Incident = ET768449
Description:
Resolved an issue that would not allow you to delete a machine of
APP_CLUSTER type.
--------------------------------------------------------------------------------
Etrack Incident = ET776667
Description:
Changes were made to correct various compiler warnings.
--------------------------------------------------------------------------------
Etrack Incident = ET778780
Description:
A bad configuration could lead to thousands of monitor-provider allocations
in the database. The resource broker (RB), on startup, may consume a lot of
memory reading these database entries and may even dump core. Now the RB
removes all of the monitor-provider allocations at startup.
--------------------------------------------------------------------------------
Etrack Incident = ET775425
Description:
When downing a drive using the vmoprcmd -downbyname or vmoprcmd –down
comands, the drive's designated scan path was sometimes set back to "UP".
--------------------------------------------------------------------------------
Etrack Incident = ET775435
Description:
When a pre-NetBackup 6.0 media server was unassigned a drive that was
Scanned by a NetBackup 6.0 media server, it was not clearing the
RVSN/EVSN and Ready fields.
--------------------------------------------------------------------------------
Etrack Incident = ET780083
Associated Primary Etracks = ET780079
Description:
When changing a drive from not shared to shared using the wizard, and
the new host (the host that will now make it shared) was running
NetBackup 5.x, the wizard would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET777630
Description:
Back-level media servers are not able to DA-release the drives because
re-registration timers block the request.
--------------------------------------------------------------------------------
Etrack Incident = ET775426
Description:
The robotic test utility (robtest) would core dump and could not perform
an unload if multiple paths exist.
--------------------------------------------------------------------------------
Etrack Incident = ET770182
Description:
Long delays occurred when starting immediate backups because the Policy
Execution Manager calls getNextJob() when processing immediate requests.
Removed call to getNextJob() for immediate requests when searching for the
backup. It makes the time to find the job n squared instead of n, where n
is the number of entries in the worklist.
--------------------------------------------------------------------------------
Etrack Incident = ET770337
Description:
The Policy Execution Manager was using the wrong lock to extract entries
from the job queue when processing user, archive, or manual backup
requests. This issue has been resolved and will no longer result in
data corruption, a crash, or lost data.
--------------------------------------------------------------------------------
Etrack Incident = ET772631
Description:
The Job Manager CPU utilization was high while most of the user backup jobs
were queued. The Job Manager was busy sending WAITING messages to the
progress logs for the queued, user backup jobs. The WAITING message is sent
every 30 seconds.
To resolve this issue, Job Manager was changed to increase the interval
between these WAITING messages sent to the progress logs.
--------------------------------------------------------------------------------
Etrack Incident = ET770167
Description:
Because of changes in the startup process with NetBackup 6.0 MP4, the
Policy Execution Manager can not start jobs until the build worklist is
complete. This process can take a long time.
To compensate for this, the build worklist has been changed to not query
the last backup or compute the due times so that the list can be built very
quickly. After the list has been built it will then synchronize with the
NetBackup Job Manager so the jobs can be started, followed by the
calculation of all of the jobs due times.
By dividing the process of how the worklist is built into two steps, jobs
can be started much sooner.
--------------------------------------------------------------------------------
Etrack Incident = ET770655
Description:
User backup requests to the Policy Execution Manager appeared to be waiting
a long time for the worklist lock. A change was made to the Policy
Execution Manager to skip the due-time calculation for user, archive, or
immediate requests.
--------------------------------------------------------------------------------
Etrack Incident = ET781527
Associated Primary Etracks = ET703273
Description:
Changed the Policy Execution Manager to call the Job Manager restartJob
Interface which looks at restartSelection setting instead of
resourceSelection. When a parent job is resumed, it frees the resource.
Job Manager failed the job if it looked at the resourceSelection (that is
set to inherit parent resource) but would work if it used restartSelection
(that is, set to use standard resource).
--------------------------------------------------------------------------------
Etrack Incident = ET777064
Description:
The naming convention used by the Sun Solaris Leadville HBA driver has
changed.
--------------------------------------------------------------------------------
Etrack Incident = ET782623
Description:
A change was made to correct an uninitialized local variable as well as
remove an unused local variable within the code.
--------------------------------------------------------------------------------
Etrack Incident = ET778981
Description:
Changes were made to resolve NBPEM memory leaks.
--------------------------------------------------------------------------------
Etrack Incident = ET779116
Description:
NetBackup services NBPEM and NBJM would core dump if an attempt was made to
Start them on a media server.
--------------------------------------------------------------------------------
Etrack Incident = ET781175
Associated Primary Etracks = ET781185
Description:
The user-configurable, MEDIA_UNMOUNT_DELAY timeout, was not being honored
for database agents.
--------------------------------------------------------------------------------
Etrack Incident = ET773564
Description:
A problem with the command -delete_server_from_app_cluster, made it
impossible to unconfigure an application cluster and reconfigure it with
the correct name.
--------------------------------------------------------------------------------
Etrack Incident = ET778908
Description:
Made multiple Coverity fixes for PEM.
--------------------------------------------------------------------------------
Etrack Incident = ET771373
Description:
Fixed the potential access of pointers that were not initialized.
--------------------------------------------------------------------------------
Etrack Incident = ET784803 ET784808 ET784805 ET784804 ET784810 ET792742 ET784809 ET802855
Description:
Buffer overflow areas have been identified and corrected in daemons running
on Veritas NetBackup master, media, and client servers. Successful access
to a vulnerable Veritas NetBackup server and the ability to successfully
execute arbitrary code could potentially result in unauthorized access with
elevated privilege on a system.
--------------------------------------------------------------------------------
Etrack Incident = ET775510
Description:
A restore of a large backup image would potentially fail if a large number
of data buffers (for example, 1024) was configured. The number of data
buffers is configured on UNIX systems in
/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS, and for Windows
systems in <install_path>\NetBackup\db\config\NUMBER_DATA_BUFFERS.
Workaround:
To avoid this problem, do one of the following:
- Set the number of data buffers to a smaller value (For example, 128).
- Create the following file:
UNIX: /usr/openv/netbackup/db/config/MIN_RESTORE_SKIP
Windows: <install_path>\NetBackup\db\config\MIN_RESTORE_SKIP
Then enter a number greater than the following:
(size_data_buffers) * (number_data_buffers) / 512
--------------------------------------------------------------------------------
Etrack Incident = ET775517
Description:
Bpbrm would occasionally terminate abnormally without core on a very busy
media server, which would cause the backup job to hang. This could only
happen on UNIX media servers, and not on Windows media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET775513
Description:
Individual file restores would potentially fail in the following
circumstance:
- The original backup was done using Inline Copy, and at least one of the
copies was disk, and the backup was multiplexed.
- The backup had multiple fragments for the disk copy.
- A duplicate from a disk copy to tape was performed, and the source and
destination storage units are on the same machine.
- The restore is from the duplicated disk copy.
Workaround:
To avoid this issue, create the following file on the master server:
For UNIX Systems:
/usr/openv/netbackup/NOSHMDUP
For Windows Systems:
<installed_path>\NetBackup\NOSHMDUP
--------------------------------------------------------------------------------
Etrack Incident = ET771553
Description:
The NBPEM uses write locks instead of read/write locks to enhance
performance.
--------------------------------------------------------------------------------
Etrack Incident = ET770349
Description:
bprd and nbpem now exchange user backup startup parameters through the
use of a file named with a GUID instead of a process PID, eliminating the
possibility that the same filename will be used twice.
--------------------------------------------------------------------------------
Etrack Incident = ET774791
Description:
A missing log message was added for when FFREADtries are exceeded.
--------------------------------------------------------------------------------
Etrack Incident = ET775512
Description:
Verify, duplication, or import operations are not able to browse
images from the Windows NetBackup Remote Administration Client.
Workaround:
To avoid this issue, run the following command on the Remote Administration
Client:
<install_path>\volmgr\bin\vmglob -set_gdbhost <master server>
--------------------------------------------------------------------------------
Etrack Incident = ET781618
Associated Primary Etracks = ET771576
Description:
Destination media may incorrectly get unmounted and a new media chosen when
duplicating multiple images. This can occur when duplicating a mixture of
multiplexed and non-multiplexed backups.
--------------------------------------------------------------------------------
Etrack Incident = ET775591
Associated Primary Etracks = ET789993
Description:
The image file created for the parent job, while multi-streaming, was not
being validated. This would later cause status 200 failures.
--------------------------------------------------------------------------------
Etrack Incident = ET785921
Associated Primary Etracks = ET783614
Description:
Duplication was failing after successfully duplicating the first image.
This occurred because the server name in bp.conf file was different from
what was in the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET778008
Description:
When you run NBJM, built with a Windows debug build, it gets an assertion
failure because of variables that were not initialized.
--------------------------------------------------------------------------------
Etrack Incident = ET775486
Associated Primary Etracks = ET771394
Description:
LTID could not connect to the NBRB when VxSS was enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET786811
Description:
If a job is queued awaiting resources, the message displaying the reason
for queuing is not displayed in the job details in the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET775422
Description:
Linux servers, with SAN attached tape drives, can have trouble using drives
that are in use at the time of a service start.
--------------------------------------------------------------------------------
Etrack Incident = ET787735
Description:
Avoid closing an NDMP tape device, so that the filer does not unreserve
the drive.
--------------------------------------------------------------------------------
Etrack Incident = ET775430
Description:
Synthetic backups no longer cause bptm core dumps when all drives are down.
--------------------------------------------------------------------------------
Etrack Incident = ET775431
Description:
Occasionally, BPTM would not handle canceled jobs during NBJM waits.
--------------------------------------------------------------------------------
Etrack Incident = ET775433
Description:
TapeAlert data is no longer ignored after the media is unloaded.
--------------------------------------------------------------------------------
Etrack Incident = ET643875
Description:
Unloads would fail on NDMP drives if the raw open operation failed.
--------------------------------------------------------------------------------
Etrack Incident = ET770157
Associated Primary Etracks = ET794596
Description:
The cleanup process intermittently failed to remove image header files on
busy systems.
Workaround:
To avoid this issue, ignore the reported error and let a subsequent cleanup
process delete the file.
--------------------------------------------------------------------------------
Etrack Incident = ET783401
Description:
Restarting the device daemons on pre-NetBackup 6.0 media servers after a
device configuration change would inadvertently unregister the host with
the device allocator (DA).
--------------------------------------------------------------------------------
Etrack Incident = ET781676 ET781719
Description:
Made multiple Coverity fixes for the NetBackup Job Manager (NBJM).
--------------------------------------------------------------------------------
Etrack Incident = ET771614
Description:
Improved the nbpem performance when reading the failure history database.
--------------------------------------------------------------------------------
Etrack Incident = ET777662
Description:
Trying to change a configured device to partially configured on a
pre-6.0 media server in the device configuration wizard, may sometimes
cause devices to become "DISABLED" for a NetBackup 5.x media server.
For NetBackup 5.x media servers, there is no concept of "DISABLED".
--------------------------------------------------------------------------------
Etrack Incident = ET776871
Description:
Duplications would fail with status codes of 114 or 800. This occurred
when media with mixed multiplexed and non-multiplexed backups were
duplicated, and when using multiplexed duplication.
--------------------------------------------------------------------------------
Etrack Incident = ET778815
Description:
The nbpem restarts it’s timer for the next housekeeping activity only after
the previous housekeeping activity has completed
--------------------------------------------------------------------------------
Etrack Incident = ET772500
Description:
Changes were added to this pack to eliminate crashes and core dumps during
nbpem shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET781548
Description:
When moving a host to new hardware using nbemmcmd, not all of the database
entries were updated with the new hostname. A change was added that
verifies that all of the necessary database fields have been updated
correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET772510
Description:
Changes were made that improve performance when writing error history by
caching the Veritas Unified Logging (VxUL) configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET783370
Description:
The NetBackup Resource Broker (NBRB) no longer crashes while running
bplabel.
--------------------------------------------------------------------------------
Etrack Incident = ET787072
Description:
An object was being deleted incorrectly for an obscure end case that is
normally not encountered.
--------------------------------------------------------------------------------
Etrack Incident = ET784575
Associated Primary Etracks = ET624633
Description:
The bpbackup command, when used with the -L and -i options, did not
provide useful information in the progress log.
--------------------------------------------------------------------------------
Etrack Incident = ET790023
Associated Primary Etracks = ET782774
Description:
You can now backup NetBackup media servers using Storage Area Network (SAN)
media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET777633
Associated Primary Etracks = ET777631
Description:
In the Java user interface, the Activity Monitor’s Detailed Status did not
increment the percent complete. It jumped from 0% to 100% at the end of
the job.
--------------------------------------------------------------------------------
Etrack Incident = ET772618
Description:
Generic jobs would not start when a large number of them were initiated in
quick succession on Windows.
NetBackup Job Manager (NBJM) was changed to start an extra nbproxy on
startup that is used by all nbgenjob's. The only exception is that a
catalog backup job will start its own nbproxy because a cancel is
implemented by shutting down the nbproxy.
--------------------------------------------------------------------------------
Etrack Incident = ET790041
Associated Primary Etracks = ET790038
Description:
Generic job exited after a few retries when the Policy Execution Manager
did not respond to pings. The parent job would exit with a status 50 and
the children exits with a status 801.
To resolve this issue, a change was made to genericjob that forces it to
ping forever until the Policy Execution Manager responds or is restarted,
or an OBJECT_NOT_EXIST exception is returned.
--------------------------------------------------------------------------------
Etrack Incident = ET786951
Associated Primary Etracks = ET781181
Description:
The Policy Execution Manager would core dump on a resume due to not copying
last schedule used when the job was being deleted.
--------------------------------------------------------------------------------
Etrack Incident = ET786406
Associated Primary Etracks = ET784164
Description:
A problem existed in the "Media and Device Management > Media" section of
the Windows Administration Console and the Java user Interface. Whenever a
tape holds more than 2 Terabytes of data on it, the Kbytes number in the
"Kilobytes" column displays as a -ve number.
--------------------------------------------------------------------------------
Etrack Incident = ET789535
Description:
When the default robotic volume group is selected in "Change Vault" dialog,
it is not selecting the correct volume group.
--------------------------------------------------------------------------------
Etrack Incident = ET785497
Description:
Removed the new ORB created during a ServiceManager collection process.
--------------------------------------------------------------------------------
Etrack Incident = ET791064
Description:
Using long hostnames for NDMP hosts no longer results in the credentials
being added incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET787049
Description:
The install was starting the ASA database service on non-EMM media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET787586 ET786594 ET790483
Description:
The NetBackup service layer (NBSL) would crash when connected from a
user interface or NetBackup Operations Manager (NOM).
--------------------------------------------------------------------------------
Etrack Incident = ET789695
Description:
Adding a cleaning tape from the user interface would result in a “bad
Cleanings” remaining number.
--------------------------------------------------------------------------------
Etrack Incident = ET772403
Description:
Formatting of jobid in log files has been normalized to "jobid=" in all
reasonable cases. This format agrees with the use of context as well.
In some places where stringstreams were used to format jobid, an
.imbue(std::locale("C")) was added to prevent localized formatting of large
integers. For more information about this change, refer to the following
TechNote on the Symantec Support Web site.
http://entsupport.symantec.com/docs/284795
--------------------------------------------------------------------------------
Etrack Incident = ET787963
Description:
The nbpem no longer leaks memory with each CORBA connection.
--------------------------------------------------------------------------------
Etrack Incident = ET776946
Description:
The nbpem no longer uses memory that is not initialized that could result
in a random error message.
--------------------------------------------------------------------------------
Etrack Incident = ET777867
Description:
Changed the Policy Execution Manager objects to initialize all fields in
constructor.
--------------------------------------------------------------------------------
Etrack Incident = ET784609
Associated Primary Etracks = ET782395
Description:
When time falls back because daylight savings time ends, jobs may run
1 hour late.
--------------------------------------------------------------------------------
Etrack Incident = ET790574
Description:
When attempting to create a Vault profile on the Java user interface, the
Make Primary Checkbox was not functioning properly. If this was used on a
storage unit in the Duplication Rule Dialog, it would not be written
correctly in vault.xml file.
--------------------------------------------------------------------------------
Etrack Incident = ET791514
Description:
Changes were added to correct the AUTO_UPDATE_ROBOT feature for Windows.
--------------------------------------------------------------------------------
Etrack Incident = ET789971
Associated Primary Etracks = ET785700
Description:
Robot inventory reports a confusing error when it is run on a robot that
contains media that is marked "conflicted" in the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET788825
Associated Primary Etracks = ET647204
Description:
The tpautoconf -replace_drive command no longer corrupts the drive's
inquiry string in the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET787033
Description:
The nbpem no longer fails or crashes when processing Share Point backups.
--------------------------------------------------------------------------------
Etrack Incident = ET792594
Associated Primary Etracks = ET646858
Description:
The NetBackup Resource Broker (NBRB), under heavily loaded conditions with
many media servers, would take about 30 seconds to give resources to the
job.
To fix the problem the following improvements have been made:
- Improved drive cache in RB (RB no longer links with emmlib).
- If the maxmpx in the request is 1, do not try to join it to any group.
- Delete all MonitorProvider allocations using a single SQL statement.
- Prioritize the requests based on the birth time too.
- Some miscellaneous improvements.
--------------------------------------------------------------------------------
Etrack Incident = ET644674 ET427279
Associated Primary Etracks = ET644671
Description:
The cluster_config script was failing when a fully qualified domain name
was used as the virtual name. In addition, deleting and then re-adding
robot daemons using cluster_config -r caused the cluster monitoring to
fail.
--------------------------------------------------------------------------------
Etrack Incident = ET777893
Description:
Changed the Policy Execution Manager to not exit the application
if the restart request could not be satisfied because of a malloc failure.
--------------------------------------------------------------------------------
Etrack Incident = ET792609
Associated Primary Etracks = ET764790
Description:
The tpconfig command would fail with the following error when the range
of the CLIENT_PORT_WINDOW parameter was set between 1025 to 5000, for
example.
"EMM interface initialization failed, status = 77"
--------------------------------------------------------------------------------
Etrack Incident = ET786617 ET631392
Description:
bpsturep and bpstuadd did not have Nearstore version checking that was
present in the user interfaces. This brings them to the same level.
It is not permissible to configure an SOI storage unit on a ONTAP 7.1.x
Nearstore. (Refer to TechNote 282929 on the Symantec Support Web site for a
more detailed explanation.) It is also not permissible to have a Nearstore
staging storage unit that has any type of SIS (SOI or FSE) enabled for
ONTAP 7.2 and higher Nearstores.
--------------------------------------------------------------------------------
Etrack Incident = ET765029
Associated Primary Etracks = ET763562
Description:
The hot catalog backup feature did not work with images that had been
archived using the catalog archiving feature. Prior to this fix, if the
catalog archiving feature had been used to archive images, the backup job
generated from a hot catalog backup policy would fail with a status 67
on a UNIX or Linux master server and with a status 1 (partially
successful) on a Windows master server.
--------------------------------------------------------------------------------
Etrack Incident = ET791570
Description:
Added a call to nbproxyreq in a NetBackup script in case the nbproxy
commands are not shutting down gracefully.
--------------------------------------------------------------------------------
Etrack Incident = ET770171
Description:
Changes were made to improve performance on multiple data streams by not
generating streams again if stream discovery did not change the stream
content.
--------------------------------------------------------------------------------
Etrack Incident = ET597353
Description:
Changes have been made to limit support of VxFS File Change Log to FCLv3
during incremental backups.
--------------------------------------------------------------------------------
Etrack Incident = ET785820
Description:
bpclntcmd no longer fails on HP-UX systems with the following error.
"_main() not called"
--------------------------------------------------------------------------------
Etrack Incident = ET789170
Associated Primary Etracks = ET702600
Description:
Vault duplication jobs were forcing a dismount/re-mount of media in drives
while processing a batch of images on a tape. This was happening because
more than one duplication job was active at the same time in the system
and the media and device selection (MDS) was asking the resource broker
(RB) to unload drives so that the other job could use it. Now the
duplicate writer is not unloaded if told by MDS to do so.
If you want pre 6.0MP4 behavior, you can create the following touch file:
<install_path>/netbackup/db/config/RB_UNLOAD_DUP_WRITER_ON_DEMAND.
--------------------------------------------------------------------------------
Etrack Incident = ET792327 ET792328 ET803918 ET808971 ET843451 ET847076
Description:
A logic error has been identified and corrected in daemons that run on
Veritas NetBackup master, media, and client servers. Successful access to
and manipulation of this logic error could potentially lead to arbitrary
command execution with elevated privileges on a vulnerable system.
For customers who need to back out this patch and want to automate the
down-rev process on their clients using the Update_clients script can
contact Support to obtain a revised bpinst file for their respective
version.
The following scenarios do NOT require a new bpinst from Support:
- If you are downgrading to 50MP7 or higher, 51MP6 or higher,
or 6.0MP4 or higher.
- If you are running Windows on your server.
- If you are only downgrading any of the following addons:
- DB agents (DB2, Lotus Notes, Oracle, SAP, Sybase, or Informix)
- Encryption (all key lengths)
- Java
- Advanced Client
- BMR master or BMR boot server
- NDMP
- Vault
- GDM (5.x only)
- Advanced Reporter (5.x only)
- NetBackup Operations Manager (6.0 only)
- Storage Migrator
- Japanese or Chinese Language Packs
--------------------------------------------------------------------------------
Etrack Incident = ET795443
Associated Primary Etracks = ET794631
Description:
If a hot catalog backup policy (policy type NBU_Catalog) was set up for
a UNIX clustered NetBackup master server that included the Vault option
and the /usr/openv/netbackup/vault/sessions directory was a link pointing
to the shared drive in the cluster configuration, then the data in the
sessions directory was not properly included in the catalog backup image.
--------------------------------------------------------------------------------
Etrack Incident = ET795533 ET795523
Associated Primary Etracks = ET618799 ET791036
Description:
bptm would erroneously log an error, (either an error code 95 or an error
code 97), during image expiration.
--------------------------------------------------------------------------------
Etrack Incident = ET792470
Description:
nbproxy and nbgenjob had unnecessary CPU utilization because additional
logging operations were enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET784640
Description:
Changes were added to fix a memory leak in the PEM logging.
--------------------------------------------------------------------------------
Etrack Incident = ET792282
Description:
In some cases, if the resource broker (RB) was not shut down cleanly,
backups would not run until nbrbutil -resetAll was run.
--------------------------------------------------------------------------------
Etrack Incident = ET794270
Description:
Script-based BLI backups were not cleaning up checkpoint files properly.
Workaround:
To avoid this issue, you can manually delete the checkpoints using the
fsckptadm command. For example, fsckptadm remove <ckpt-name> <mountpoint>
--------------------------------------------------------------------------------
Etrack Incident = ET795345
Description:
Memory was being read after being freed in the job scheduler's work list.
--------------------------------------------------------------------------------
Etrack Incident = ET796051
Description:
Changes were made to correct a minor logic error.
--------------------------------------------------------------------------------
Etrack Incident = ET610398
Description:
When a suspended job is resumed, the bytes count and the file count in the
activity monitor job display is no longer incorrect.
--------------------------------------------------------------------------------
Etrack Incident = ET778923
Description:
When a job was retried immediately, the job status of the previous try
was lost.
--------------------------------------------------------------------------------
Etrack Incident = ET631436
Description:
A problem existed that caused NOM to not show bprd and bpdbm.
--------------------------------------------------------------------------------
Etrack Incident = ET777860
Description:
Changes were made to clean up the following Policy Execution Manager tasks:
- Switched data types from int to bool if used as a boolean.
- Added error checking to the job submission queue to fix a memory leak.
- Changed the Policy Execution Manager to return the status
EC_backup_error or EC_malloc_failed if an error is encountered
starting child jobs for a parent job.
--------------------------------------------------------------------------------
Etrack Incident = ET796104
Description:
A race condition occurred when two add_files queries were received
simultaneously and both attempted to create the catstore folder.
--------------------------------------------------------------------------------
Etrack Incident = ET784650
Associated Primary Etracks = ET829340
Description:
NetBackup communication between components that were separated by a
firewall did not work. For instance, when a master server was behind the
firewall and a media server was outside the firewall, all communication
from the master server had an internal host address that was not accessible
from outside systems.
This is the same when clients and other services are in question.
Additional Notes:
To activate NAT address replacement, systems outside of the firewall should
have the FIREWALL_IN parameter specified in their bp.conf/registry.
Format: FIREWALL_IN=hostname1,nat_address1|hostname2,nat_address2|...
Where: <hostname> is the name of the host system that needs to be accessed
and <nat_address> is the actual NAT address for the firewall to do
forwarding.
--------------------------------------------------------------------------------
Etrack Incident = ET795448
Description:
Changes were made to not send Storage Unit Events when only updating
capacity information. Too many of these events were being generated and
impacting performance.
--------------------------------------------------------------------------------
Etrack Incident = ET793447
Description:
Changes have been made to reduce the bpdbm CPU consumption by doing fewer
things on exit of child bpdbm processes.
--------------------------------------------------------------------------------
Etrack Incident = ET795436 ET796505 ET801859
Associated Primary Etracks = ET794344
Description:
VSP files would sometimes get deleted when they were needed to resume an
incomplete or suspended stream.
--------------------------------------------------------------------------------
Etrack Incident = ET795374 ET814653
Description:
BPTM failed a job with a 174 error when it should retry the
resource allocation.
--------------------------------------------------------------------------------
Etrack Incident = ET797992
Description:
NetBackup 5.x media servers fail when running tpautoconf -sync, if the
global database host is a 6.0 server.
Workaround:
To avoid this issue, delete the device configuration on the 5.x media
server and reconfigure.
--------------------------------------------------------------------------------
Etrack Incident = ET781386
Description:
There may be cases where configuring either shared libraries or shared
drives does not perform the necessary device configuration updates on all
hosts. For example, if host A has drive D1 configured, and then the wizard
is used to configure host B, host B will have the drive added as shared,
but host A's configuration will not be updated. This results in two hosts
scanning the drive.
Workaround:
To avoid this issue, do the following:
- Always use the wizard to configured devices.
- Always scan all media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET797150
Associated Primary Etracks = ET797162
Description:
The bptm process no longer crashes while duplicating data that has True
Image Restore (TIR) information associated with it.
--------------------------------------------------------------------------------
Etrack Incident = ET797080
Description:
When the parent job does stream discovery the
getRealAndVirtualPolicyByName() gives an error and sometimes fails
because the sig library was not initialized. Currently the sig library
is only initialized for catalog backups instead of for all backup types.
--------------------------------------------------------------------------------
Etrack Incident = ET802582
Associated Primary Etracks = ET793913
Description:
The NetBackup Java user interface no longer displays “square box”
characters in the Media “Side” column for the second AcsLsm.
--------------------------------------------------------------------------------
Etrack Incident = ET796480
Description:
Backup jobs would occasionally fail with error status 26 (client/server
handshaking failed). The bpbrm log would show the following:
08:34:12.336 [2764.3504] <2> bpbrm multiplexed_backup: calling
read_media_msg for media manager PID.
08:34:42.618 [2764.3504] <2> bpbrm read_media_msg: media manager pid 0 is
not alive
08:34:42.618 [2764.3504] <16> bpbrm multiplexed_backup: cannot get PID of
media manager
08:34:42.915 [2764.3504] <2> bpbrm Exit: ERROR 26 sent to parent process
--------------------------------------------------------------------------------
Etrack Incident = ET796392
Description:
The NBJM threads block while calling the proxy for BPDBM requests.
--------------------------------------------------------------------------------
Etrack Incident = ET794326
Description:
Changed a strncpy to a V_strlcpy to prevent the string not being null
terminated.
--------------------------------------------------------------------------------
Etrack Incident = ET797363
Description:
Increased the connection cache size for nbjm to reduce number of
Communication retries by bptm.
--------------------------------------------------------------------------------
Etrack Incident = ET784514
Description:
Synthetic backups no longer fail with the error message, "termination
requested by bpcoord(665)".
--------------------------------------------------------------------------------
Etrack Incident = ET797083
Description:
The parent job no longer core dumps upon exiting an application when trying
to log a VxUL message after an orb shutdown. The parent job was modified
to remove all VxUL messages that are being logged after an orb shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET797388 ET798930
Description:
Multiple backups for the same client and policy that were started at the
same time created a situation where an image was being validated at
the same time the previous backup for the client and policy was being
validated.
One of the final steps in image validation is to go back through previous
backups for the client and policy and update the TIR meta data to allow TIR
data to be pruned. However, since the previous backup for the client and
policy was still being validated, it could not be updated and the following
log message (and error report entry) were generated:
17:27:33.723 [11812] <16> get_last_backup_lock: Bad image header:
many-non-multi-stream_1158100028_FULL, error: file read failed (13)
bpdbm was exiting with a normal status, so the backup was successful.
Workaround:
To avoid this issue, wait before starting backups for the same client and
policy.
Additional Notes:
With this change, any failures in updating tir meta data in image
validation will result in a conditional success for the backup job.
--------------------------------------------------------------------------------
Etrack Incident = ET797999 ET797370
Description:
Changes were made to clarify error message that may have been unclear.
This involved no functional change.
--------------------------------------------------------------------------------
Etrack Incident = ET796292
Description:
Pending messages were not displayed in the Activity Monitor for spanned
backups.
--------------------------------------------------------------------------------
Etrack Incident = ET798366
Description:
EMM now logs a more accurate disk space message when space is below
the threshold.
--------------------------------------------------------------------------------
Etrack Incident = ET796332
Description:
Changes were made to bpbrmds to eliminate core dumps when performing a
manual or scheduled relocation of a DSSU on media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET800221
Description:
Parent images have no associated .f file, and as a result have a file count
of zero. When images with a zero file count are validated, a function to
tally the number of files is called. This function should not be called
when there is no associated .f file. The logic to determine whether there
is an associated .f file has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET800184
Associated Primary Etracks = ET798913
Description:
Resolved an issue that caused, "Frequent status code 805 - invalid jobid,"
errors to occur.
Additional Notes:
This condition occurred when children jobs were retired due to exceeding
the time allowed in incomplete state. The parent job being resumed either
manually or automatically resulted in an 805 error due to the job having
a jobid of -1. This fix prevents the child from starting since it is not
resumable. The new result will correctly be a 200 error if no children
can be started. An indication of this will be written to the pem log.
--------------------------------------------------------------------------------
Etrack Incident = ET801046
Description:
The job monitor would cancel the catalog backup job after 20 minutes.
The nbgenjob ping interval to the job manager was changed to three minutes
to keep the job from being cancelled.
--------------------------------------------------------------------------------
Etrack Incident = ET799129
Description:
The synthetic backups were not scheduling correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET800016
Description:
The nbpem would core dump because getECmsgl was not thread safe.
--------------------------------------------------------------------------------
Etrack Incident = ET802987
Description:
A Hot Catalog Backup of a large catalog with a large number of files can
sometimes end up in a deadlock between the NetBackup UNIX agent bpbkar and
the NetBackup media server process bpbrm.
--------------------------------------------------------------------------------
Etrack Incident = ET803630
Description:
Changes were added to correct an issue that casued the resource broker (RB)
to hang at startup.
--------------------------------------------------------------------------------
Etrack Incident = ET799867
Description:
The Policy Execution Manager inefficiently processes policy change
notifications when performing housekeeping tasks which may slow job
submission. This inefficiency can occur from the user interface if the
user selects all policies and then activates or deactivates the list of
policies.
Workaround:
To avoid this issue, do not generate a large number of policy changes all
at once before a window opens. Instead, amortize them over time to limit
the impact on the Policy Execution Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET800184
Associated Primary Etracks = ET798913
Description:
The jobid of a child checkpoint restart job would be set to -1 when
a 196 status occurred. The result was an 805 error if the parent was
resumed because the jobid -1 gets resumed.
--------------------------------------------------------------------------------
Etrack Incident = ET804921
Description:
The calendar schedule would not run when the available window spanned
across the specified day.
--------------------------------------------------------------------------------
Etrack Incident = ET805146
Description:
The NetBackup Job Manager (NBJM) was checking the connection to the proxy
before reading the global configuration to obtain attributes such as,
max vault jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET805407
Description:
The policy monitor would show as being down in Initial Data Load status
page.
--------------------------------------------------------------------------------
Etrack Incident = ET800841
Description:
Sometimes manual jobs would not start through either the user interface
or the command line. This would happen if PEM lost connection with NBJM.
--------------------------------------------------------------------------------
Etrack Incident = ET804850
Description:
An issue that caused catalog backups to hang on a retry have been fixed.
--------------------------------------------------------------------------------
Etrack Incident = ET805807
Description:
Cancelling an incomplete job that failed with a 196 error, then restarting
nbpem would cause the job to show as done in the Activity Monitor.
However, if the job is set to done in the Activity Monitor, a retry or
resume of the active job will not show up in the Activity Monitor.
Workaround:
If there are checkpoint restart jobs that show as complete but have a
status of 196 and pem needs to be restarted, remove the pempersist file
before pem is started again.
--------------------------------------------------------------------------------
Etrack Incident = ET806779
Description:
A timer was scheduled for a backup job even when throttling was not
configured.
--------------------------------------------------------------------------------
Etrack Incident = ET806051
Description:
NetBackup Maintenance Pack upgrades were failing on the active node of an
HP ServiceGuard cluster, due to the package monitor offlining the package
even with switching disabled. The capability to freeze the cluster agent
monitoring by touching a file (/usr/openv/netbackup/bin/cluster/frozen)
was added.
--------------------------------------------------------------------------------
Etrack Incident = ET806888
Description:
The bpinet services on media servers were being reported as an
"unknown" status in NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET806990
Description:
Service credentials had expired and because of that, the NOM client was
unable to log into the NOM server.
Workaround:
To avoid this issue, you can renew the credential using the command line
interface provided by vssat.
--------------------------------------------------------------------------------
Etrack Incident = ET803649
Description:
Jobs would queue indefinitely, following a media server reset while
pending resource requests were outstanding.
Workaround:
To avoid this issue, restart the resource broker, or run nbrbutil -resetall.
--------------------------------------------------------------------------------
Etrack Incident = ET798064
Description:
A problem existed when using the vxlogview command that caused the
–t option to be ignored if it followed a –d option.
--------------------------------------------------------------------------------
Etrack Incident = ET808318
Associated Primary Etracks = ET796499
Description:
The service called NetBackup Volume Manager (vmd) would stop unexpectedly
because of a network problem.
--------------------------------------------------------------------------------
Etrack Incident = ET808314
Associated Primary Etracks = ET804963
Description:
The Tape Library DLT Control Deamon (tldcd) service would unexpectedly
terminate because of network problems.
--------------------------------------------------------------------------------
Etrack Incident = ET808037 ET807124
Description:
The SharePoint Portal, when configured with a network name in a network,
load-balanced, medium farm configuration, would not relink the portal
databases after a restore.
Additional Notes:
Please refrain from using a local IP address when configuring portals and
team sites. SharePoint communicates to all the load-balanced, front-end
servers to get information about the Portal/Team Site when they are backed
up or restored. If there is a Portal/Team Site that is tied locally to one
of the load-balanced servers, then other front-end servers will not be
cognizant of the local names. It will result in backup and restore failures
for the local portals and team sites.
Please use fully qualified domain names or IP addresses (such as,
http://10.80.138.80 instead of http://vitualportal) when configuring
portals and team sites with a network name in a network, load-balanced
environment. A SharePoint application generates exceptions when virtual
servers that are specified that cannot be resolved by the application while
committing and reconnecting the restored databases. These errors can be
tracked with the help of tar logs in NetBackup\logs\tar on the database
client and spswrapper log files in NetBackup\logs\spps folder in the
sharepoint front end servers.
The workaround for this scenario is to use the IP address while
configuring the portal/team sites or restoring/reconnecting the databases
to the portal/team site using the SharePoint 2003 administration console
after the NetBackup restore has completed.
--------------------------------------------------------------------------------
Etrack Incident = ET814706
Description:
PEM no longer crashes when starting a bpduplicate job (or any job where
the client was not set).
--------------------------------------------------------------------------------
Etrack Incident = ET814644
Associated Primary Etracks = ET797945
Description:
The inventory operation, using vmphyinv, was failing with a network
protocol error (39). This was because oprd was crashing. After fixing the
core dump, other issues were encountered (and fixed) because of which tape
header was not being read correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET814692
Associated Primary Etracks = ET801982
Description:
A change was made to ensure that the volume expiration was not getting
reset after expiring all images on a tape.
--------------------------------------------------------------------------------
Etrack Incident = ET814762
Associated Primary Etracks = ET783819
Description:
An Oracle restore would fail if no drives were available within 900
seconds.
--------------------------------------------------------------------------------
Etrack Incident = ET814884
Description:
ExportedResourceMgr.cpp and ExportedResource.cpp do not show up in the
"what" output, making it impossible to verify the version of these files
in the nbjm binary.
--------------------------------------------------------------------------------
Etrack Incident = ET818259
Associated Primary Etracks = ET809337
Description:
Changes were made to correct an issue with adding an NDMP robot.
--------------------------------------------------------------------------------
Etrack Incident = ET818227
Description:
The text for status code 125 has been changed to reflect the use of this
status code in preventing some operations when an online catalog backup is
in progress.
--------------------------------------------------------------------------------
Etrack Incident = ET774674
Description:
When a bad drive or bad tape is mounted and the mount fails, the Media and
Device Selection (MDS) will down the drive and retry using other
drives/media. If this happened to be the scan host for this drive, MDS
would not clear the scanning assignment. Subsequently the device allocator
(DA) would bring the drive back up.
--------------------------------------------------------------------------------
Etrack Incident = ET771156 ET806039
Description:
When drive or library paths are swapped, and devices are re-discovered
using the wizard, users may see drives or libraries with an "empty" path.
This makes the device unusable and it must be deleted and reconfigured.
--------------------------------------------------------------------------------
Etrack Incident = ET772110
Description:
NetBackup would show the incorrect version number when it was installed as
Media Server. For example, bpgetconfig -s >host< (or the appropriate
bpjava* protocol) would not return the patch level if initiated across
UNIX <-> Windows boundaries, for instance,
On UNIX host A, execute bpgetconfig -s B -A
where B is Windows...
or vice-versa
--------------------------------------------------------------------------------
Etrack Incident = ET818369
Associated Primary Etracks = ET808850
Description:
A job could be canceled out of a window when the window was still open.
--------------------------------------------------------------------------------
Etrack Incident = ET818434
Associated Primary Etracks = ET802264
Description:
Scheduled backups did not always run in a window that was open for only
one day, and the freqency was set for less than one day.
--------------------------------------------------------------------------------
Etrack Incident = ET819178
Description:
The nbnos process no longer leaks memory with policy changes.
--------------------------------------------------------------------------------
Etrack Incident = ET818041
Description:
NetBackup would leave rogue/zombie processes running during the course of
the patch install/uninstall. The installer will now actively search for
these processes and terminate them before it continues with the install.
--------------------------------------------------------------------------------
Etrack Incident = ET821063
Description:
Java user interface would use the wrong authentication broker if it was
different from root broker.
--------------------------------------------------------------------------------
Etrack Incident = ET820406
Description:
In some cases, bptm was not exiting after job completion, making jobs
unavailable for other jobs.
Workaround:
Manually kill hung bptm processes.
--------------------------------------------------------------------------------
Etrack Incident = ET819158
Description:
A backup job would get retried even though it completed with a status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET818859
Description:
A change was made so that NBSL no longer core dumps when NetBackup is
accessed using NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET803700
Description:
Changes were made to ensure that parent jobs no longer exit with a
status 200.
--------------------------------------------------------------------------------
Etrack Incident = ET788999
Description:
In the Activity Monitor, the elapsed time for a job would sometimes appear
formatted incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET821035
Associated Primary Etracks = ET795266
Description:
Database backups or restores may fail (because of a timeout).
An examination of the debug logs showed that the EXIT STATUS was sent from
the client to bpbrm, however bpbrm did not receive the EXIT STATUS message.
--------------------------------------------------------------------------------
Etrack Incident = ET821355
Associated Primary Etracks = ET808950
Description:
nbemm will now allow alias functions with machinetypes cluster, app_cluster
and api.
--------------------------------------------------------------------------------
Etrack Incident = ET828665
Description:
A problem that occurred when the following conditions existed has been
fixed:
1) The schedule associated with the DSSU initiates relocation operations.
2) All completed images on the DSSU have already been relocated.
3) New, uncompleted images are in the process of being written to the
DSSU because of new backup operations.
There were no images that could be relocated and the job terminated with
an error status of 190. No errors had actually occurred but the resultant
messages gave the user the impression that something was wrong.
--------------------------------------------------------------------------------
Etrack Incident = ET828100
Description:
The cluster package and monitoring configuration was incorrect when
installing with a fully qualified virtual name on HP serviceGuard
and SunCluster clusters.
--------------------------------------------------------------------------------
Etrack Incident = ET827854
Description:
On the HP-UX IA64 platform, the "bpcatlist -id <backup id>" command could
core dump if the -id option is used.
Workaround:
To avoid this issue, do not use the "-id" option.
--------------------------------------------------------------------------------
Etrack Incident = ET819570
Description:
After you have attempted to stop a NetBackup Service, you may receive a
service stop failure.
Approximately 3 seconds after you have attempted to stop a NetBackup
Service you will notice that progress bar zooms across the screen and
disappears before the service has had a chance to do an orderly shutdown,
causing the stop failure to be reported.
--------------------------------------------------------------------------------
Etrack Incident = ET819159
Description:
An expire from the user interface of a snapshot-based backup image copy
failed with the following message in the bpfis log.
"fis_rebuild_from_db: cannot open"
--------------------------------------------------------------------------------
Etrack Incident = ET821071
Description:
A problem existed in Exchange VSS jobs that caused incremental backups to
act like FULL backups.
--------------------------------------------------------------------------------
Etrack Incident = ET820388
Description:
Added support to display filesystem capacities that are larger than
several Terabytes (TB).
--------------------------------------------------------------------------------
Etrack Incident = ET828735
Associated Primary Etracks = ET821288
Description:
When using vnetd only for client connect, all backups in the multiplexing
group would fail with a 41 status ("network connection timed out") if one
client cannot be contacted.
Workaround:
To avoid this issue, run the backups as non-multiplexed.
--------------------------------------------------------------------------------
Etrack Incident = ET802903
Description:
A problem existed where a catalog backup would run however it did not
appear in the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET828685
Description:
Changes have been made that ensures a Synthetic schedule will run at the
proper time.
--------------------------------------------------------------------------------
Etrack Incident = ET829045
Description:
Pem no longer crashes if there is an attempt to restart a done job from
the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET829683
Associated Primary Etracks = ET814470
Description:
Empty paths on file entries were causing backups to fail with a status 1
and an entry in the bpdbm log similar to the following:
11:29:18.781 [5216.3708] <32> add_files: File:
v:\src\common\libcatalog\nbe_string.h Line: 434: null pointerFunction:
utf8_strlen
With this patch, the backup will still fail if a null or empty path is
detected, but an entry similar to the following will appear in the
NetBackup error report:
A null or empty path was provided for policy1_1160000001_FULL at entry 2501
Additional Notes:
A null or empty path string is usually caused by a failure in the client
device. Check for patches from the device manufacturer to address the
root cause.
There is a known issue with NetApp filers configured for Chinese locales
that produces this problem. NetApp has a file history patch that addresses
the issue:
NetApp Bug ID: 195779
Title: NDMP DMA shows no file names after a backup with 7.0.x
Description:
Empty NFS pathnames will be returned in the file history for non-ASCII
filenames if the root volume's language is not set to C/POSIX or
the language setting of the volume being backed up differs from the
root volume's language setting.
Workaround:
Make sure the language setting of the root volume matches that of
the volume being backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET830269
Description:
A change has been made that ensures that after you have downed a drive on
the scan host, it will not come back up.
--------------------------------------------------------------------------------
Etrack Incident = ET805843
Description:
bpdbm uses the notification service to notify the PEM and JM components
when policies are updated. When the call to the notification service
failed, the bpdbm child process would terminate with little information on
the cause of the failure. With this patch, the cause of the failed call to
the notification service will be logged, and an entry will be made in the
NetBackup error report for the termination of the child bpdbm process.
--------------------------------------------------------------------------------
Etrack Incident = ET797083
Description:
A Parent job (nbgenjob) would core dump when an exception, thrown by
ORB, was not handled. This problem has been fixed in this pack.
--------------------------------------------------------------------------------
Etrack Incident = ET776675
Description:
The pem was referencing a function that was using strtok(), which was not
thread-safe on UNIX platforms. This change only affected UNIX platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET831186
Associated Primary Etracks = ET830464
Description:
Changes were made to resolve an intermittent crash in findByJobId.
--------------------------------------------------------------------------------
Etrack Incident = ET831242
Description:
On large file systems with a large number of images, disk staging would not
free space fast enough to prevent concurrent backups from failing with 129
errors. (Refer also to ET774846.)
Additional Notes:
When a backup to a disk storage unit with staging completes, the percent
used is compared with the high water mark. If the percent used is equal to
or greater than the high water mark, a bpdm process will be invoked which
will remove staged images until the low water mark is reached.
To disable this behavior, create the "IGNORE_HIGH_WATER_MARK" touch file in
the netbackup/bin directory.
--------------------------------------------------------------------------------
Etrack Incident = ET831331
Associated Primary Etracks = ET829395
Description:
The bpduplicate command would fail, resulting in a core dump. This would
occur if bpduplicate, while running on a media server, tried to invoke
bpduplicate on the master using a bidfile. This would happen most
frequently as part of disk staging.
--------------------------------------------------------------------------------
Etrack Incident = ET831415
Description:
When a request to the EMM server to change an expiration date for a media
failed, an unreadable message would appear in the NetBackup error report.
--------------------------------------------------------------------------------
Etrack Incident = ET819040
Description:
A job that was added to a multiplexed group would show an incorrect
operation in the Activity Monitor. For example, the Job operation would
remain as CONNECTING during a successful backup. However, if the backup
job spans tape, the operation would remain as POSITIONING until the job
completes.
--------------------------------------------------------------------------------
Etrack Incident = ET831231
Associated Primary Etracks = ET613789
Description:
Oracle and Informix restores may hang or fail (via a timeout). In one
situation bptm log would contain the following message:
08:40:54.944 [20370] <2> mpx_read_backup: waiting for children to
terminate so exit status can be sent to bpbrm
In another situation the bpbrm log would contain the following message:
16:13:00.835 [173273] <8> bpbrm process_media_msg: unknown media message:
RCD_STOP_DB_RESTORE_STR
--------------------------------------------------------------------------------
Etrack Incident = ET831977
Description:
When an inline tape copy job failed due to un-availability of resources,
the reason string was not displayed in jobd for all copies.
--------------------------------------------------------------------------------
Etrack Incident = ET832116
Associated Primary Etracks = ET829088
Description:
Calendar schedules would not run if another backup ran the same calender
day, even if the backup was in a window that opened on the previous day.
Workaround:
To avoid this issue, use a frequency scheduling of 24 hours.
--------------------------------------------------------------------------------
Etrack Incident = ET833015
Description:
A timeout of a clean or an unload when ltid was not running in verbose
mode would not be cleaned up.
--------------------------------------------------------------------------------
Etrack Incident = ET831472
Description:
NBPEM and NBJM code did not handle exceptions from all ORB calls.
--------------------------------------------------------------------------------
Etrack Incident = ET833885
Associated Primary Etracks = ET833782
Description:
After a pem crash with multistreamed jobs active, the job may not get
scheduled to run again.
--------------------------------------------------------------------------------
Etrack Incident = ET834141
Description:
NBJM would crash on shutdown if there was an active connection in the
connection factory and the timing was such that one thread was destroying
the connection factory while another was working with the connection object.
--------------------------------------------------------------------------------
Etrack Incident = ET834475
Description:
NetBackup Job Manager no longer hangs while running backups for clients
with throttling configured.
--------------------------------------------------------------------------------
Etrack Incident = ET834802
Description:
Catalog recovery from a hot catalog backup would fail with the following
error when the entry for EMMSERVER in bp.conf was different than the
SERVER name for the master server, but, they were actually the same
machine. This would occur when there were two NICs in the master server.
"Failed to find last NBDB backup image record for client serverName
with policy policyName (227)"
--------------------------------------------------------------------------------
Etrack Incident = ET834080
Associated Primary Etracks = ET646858
Description:
A change has been that keeps a bogus STU (such as, a STU pointing to
non-existing device) from causing the NetBackup Resource Broker's cache
to become invalid.
--------------------------------------------------------------------------------
Etrack Incident = ET831475
Description:
Changes were made that enable Vault VCCS Portal libraries to handle
exceptions such as, CORBA::Exception.
--------------------------------------------------------------------------------
Etrack Incident = ET836865
Description:
A change was made to resolve and issue that caused database backups to fail
with a status 13 (file read failed) error. The Job Details would show the
following types of messages:
Error bpbrm (pid=xxxx) socket read failed: errno = 131 - Connection reset
by peer
end writing; write time: 2:04:24
file read failed (13)
--------------------------------------------------------------------------------
Etrack Incident = ET837124
Description:
A change was made that resolves an issue that caused scheduled jobs to not
run.
--------------------------------------------------------------------------------
Etrack Incident = ET829247
Description:
The vmoprcmd -devmon command may incorrectly display multiple drive paths
under a drive name.
--------------------------------------------------------------------------------
Etrack Incident = ET834952
Description:
When a longer frequency backup (such as a full backup) for a client failed
and could not be retried due to an exceeded failure history, nbpem would
initiate a shorter frequency backup, if one was configured and due at the
same time (such as an incremental). This job would also be retried if it
failed.
A change was made to the failure history to resolve this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET831460
Description:
Changed the location of the pempersist file so it is shared in a
clustered setup.
--------------------------------------------------------------------------------
Etrack Incident = ET837657
Description:
Some of the connections between the media server and client were not
affected by the CLIENT_CONNECT_TIMEOUT configuration value for database
agent backups. A hard-coded value of one minute was used instead.
This patch fixes the media server to use the CLIENT_CONNECT_TIMEOUT for
database agent backups as well as file system backups.
--------------------------------------------------------------------------------
Etrack Incident = ET840396
Description:
The Cluster Server Agent for Storage Migrator now installs on Solaris 10.
--------------------------------------------------------------------------------
Etrack Incident = ET840432
Associated Primary Etracks = ET838346
Description:
After a status 129 failure occurred, the retry was not picking a different
DSU in the stunit group.
--------------------------------------------------------------------------------
Etrack Incident = ET837609
Description:
A problem existed that caused jobs to be stuck in a waiting-for-retry state
for multiple days.
--------------------------------------------------------------------------------
Etrack Incident = ET841713
Description:
A change was made to correct the NetWare Loadable Module (NLM) Version
numbers from 5.0 to 6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET840460
Associated Primary Etracks = ET837021
Description:
The pending requests output of the vmoprcmd command no longer prints the
volume group for pending mount requests.
--------------------------------------------------------------------------------
Etrack Incident = ET841261
Description:
Vault sessions and ejects failed under NetBackup Access Control (NBAC).
--------------------------------------------------------------------------------
Etrack Incident = ET841643
Description:
bpmedialist -mcontents command terminated abnormally without notifying NBJM.
The job was declared abandoned after a while. As a result, NBJM failed on
an assertion check while cancelling the job.
After NBJM was restarted, NBPEM could not communicate with NBJM because all
of its threads were hung on a corba call to ping NBJM.
--------------------------------------------------------------------------------
Etrack Incident = ET841711
Description:
In certain conditions where bpmedialist does not get updates from bptm for
more than an hour, NBJM could terminate bpmedialist.
--------------------------------------------------------------------------------
Etrack Incident = ET837077
Description:
A problem existed that caused a catalog backup child job to fail and
remain in "Waiting for Retry" state indefinitely.
Workaround:
To avoid this issue, cancel the job.
--------------------------------------------------------------------------------
Etrack Incident = ET839365
Associated Primary Etracks = ET829855
Description:
The status backup report would report no data or it would report data only
with the wrong hostname.
--------------------------------------------------------------------------------
Etrack Incident = ET844039
Description:
In some instances, it is possible for a media server to have a robotic
drive configured but no corresponding robot entry in the database. In this
case, the device monitor request to the database is "short-circuiting". In
other words, whatever has been retrieved up until the offending record is
displayed, subsequent data is lost.
The fix for this problem is to mark the drive as "AVR" control and continue
normally. Therefore, if such a configuration occurs, these drives will
always have a status of robot DOWN. If you see this, you need to make sure
that the host for the "AVR" drive path has a robotic entry which matches
the drive's residence.
--------------------------------------------------------------------------------
Etrack Incident = ET844043
Description:
When device configuration changes are made, occasionally this will require
that all hosts sharing a drive, be restarted. Previous to this patch, the
device monitor is showing "RESTART" for all the paths - even those paths on
hosts that have had their Device Management Service or Daemon restarted.
This patch changes the device monitor so that the RESTART status is
displayed only for the paths on hosts whose Device Manager have not yet
been restarted.
NOTE: NetBackup may still not use this drive until all hosts' Device
Manager have been restarted.
In addition, the unsupported option for vmoprcmd "-reset_ltid_restarted_bit"
has been changed so that it works on back-rev media servers. Also, a new
option "-get_host_restart_list" has been added to provide a list of all
the hosts for which NetBackup is waiting to have the Device Manager
restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET842109
Description:
After executing bpdown or NetBackup stop, the bpdbm cleanup process was
continuing to run. It was attempting to notify other processes that were
terminated. With this fix, the bpdbm cleanup process checks the status of
the parent bpdbm process and terminates the cleanup if the parent bpdbm
process has been terminated.
Workaround:
To resolve this issue, make sure cleanup is not running before you shut
down NetBackup. You can so this by running bpps and looking for a child
bpdbm process, or by inspecting the bpdbm log for Q_IMAGE_DELETE queries
that have not finished.
--------------------------------------------------------------------------------
Etrack Incident = ET843993
Associated Primary Etracks = ET795418
Description:
It was possible to create a media server and cluster with the same name.
However, depending on which one was used first could create problems at
run time.
Workaround:
To avoid this issue, clean the database with the nbemmcmd command or
direct SQL.
--------------------------------------------------------------------------------
Etrack Incident = ET846970
Description:
NBRB would crash in some situations while running duplicate, synth or
Inline Tape Copy jobs.
--------------------------------------------------------------------------------
=========
NB_60_3_M
=========
Etrack Incident = ET421741
Description:
A user-directed backup for Exchange Volume Shadow Copy Service (VSS)
Transportable failed with a status 200. To resolve this issue, the Policy
Execution Manager (PEM) was changed to start a child Exchange VSS
Transportable job instead of another parent job.
Additional Notes:
Refer also to ET612121.
--------------------------------------------------------------------------------
Etrack Incident = ET616093
Description:
Backup types, such as Network Data Management Protocol (NDMP) and True Image
Recovery (TIR)-enabled, that use the read_files_file query may fail when the
backup contains enough files to cause any of the component .f files to grow
larger than 2 GB. (The .f files are the files in
/usr/openv/netbackup/db/images/<client>/<date>/tmp/catstore.)
Additional Notes:
Refer also to ET546411.
--------------------------------------------------------------------------------
Etrack Incident = ET417355
Description:
The Policy Execution Manager (PEM) retries a failed inline tape copy job a
specific (configured) number of times, after which, it expired the primary
jobid. As a result, the primary jobid was marked as DONE. However, the
secondary jobids remained in the "waiting for retry" state.
--------------------------------------------------------------------------------
Etrack Incident = ET614605
Description:
The NetBackup Policy Execution Manager (nbpem) process no longer dies with
a segmentation violation.
Additional Notes:
Refer also to ET585964.
--------------------------------------------------------------------------------
Etrack Incident = ET614650 ET614416
Description:
Changes were added to replace calls to non-thread-safe functions with
thread-safe versions.
Additional Notes:
Refer also to ET581111.
--------------------------------------------------------------------------------
Etrack Incident = ET614698
Description:
Unable to turn off tracing in job objects-problem.
Additional Notes:
Refer also to ET584481.
--------------------------------------------------------------------------------
Etrack Incident = ET614664
Description:
A change was added to correct the order in which the reference count is
decremented.
Additional Notes:
Refer also to ET582313.
--------------------------------------------------------------------------------
Etrack Incident = ET614641
Description:
Made changes to send the connect options to NetBackup 5.x and NetBackup 6.x
media servers.
Additional Notes:
Refer also to ET577874.
--------------------------------------------------------------------------------
Etrack Incident = ET614589
Description:
Resolved a "read from parent" infinite loop condition in bpbrm.
Additional Notes:
Refer also to ET495890.
--------------------------------------------------------------------------------
Etrack Incident = ET614416
Description:
Corrected numerous thread-unsafe calls, both direct and indirect, in nbjm
and nbpem.
Additional Notes:
Refer also to ET579996 and ET580009.
--------------------------------------------------------------------------------
Etrack Incident = ET614590
Description:
New e-mail functionality has been added to NBPEM to correct some previous
behavior issues.
Additional Notes:
Refer also to ET544252.
--------------------------------------------------------------------------------
Etrack Incident = ET615409
Description:
Jobs no longer fail with a status 25 on the NBJM server side.
Additional Notes:
Refer also to ET593372 and ET611468.
--------------------------------------------------------------------------------
Etrack Incident = ET614699
Description:
Changes were added to always attempt to call the Job Manager to determine
if a Job is active for an invalidated image.
Additional Notes:
Refer also to ET585957.
--------------------------------------------------------------------------------
Etrack Incident = ET614648
Description:
The NetBackup Policy Execution Manager (nbpem) uses strtok to parse various
things. Changes were added to use strtok_r instead for additional safety
reasons.
Additional Notes:
Refer also to ET611478 and ET580000.
--------------------------------------------------------------------------------
Etrack Incident = ET614605
Description:
Fixed an overflow check for INFINITY in nbpem that produced a core file
that pointed to a segmentation violation (signal 11).
Additional Notes:
Refer also to ET585964.
--------------------------------------------------------------------------------
Etrack Incident = ET615640
Description:
Corrected an issue that caused Share point 2001 directives to exit with a
status 69.
Additional Notes:
Refer also to ET615641.
--------------------------------------------------------------------------------
Etrack Incident = ET615654
Description:
Fixed a problem that caused backup jobs to end with "status 200" when they
should not.
Additional Notes:
Refer also to ET610214.
--------------------------------------------------------------------------------
Etrack Incident = ET615652
Description:
The NetBackup Policy Execution Manager (nbpem) would core when it called
convert2unixdate which then called local time which is a non-safe thread.
Additional Notes:
Refer also to ET610206 and ET200604.
--------------------------------------------------------------------------------
Etrack Incident = ET610473
Description:
Child jobs for Catalog backups no longer fail intermittently with a
status 25.
--------------------------------------------------------------------------------
Etrack Incident = ET615656
Description:
Changes were made to fix nbgenjob crashes (affects Windows only).
Additional Notes:
Refer also to ET563727.
--------------------------------------------------------------------------------
Etrack Incident = ET614617
Description:
A problem existed that caused assigned resources to not be reused if the
Media ID's were less than six characters long.
Additional Notes:
Refer also to ET574590.
--------------------------------------------------------------------------------
Etrack Incident = ET614566
Description:
The Backup, Archive, and Restore (BAR) user interface did not notify users
if a pending request had been sent.
Additional Notes:
Refer also to ET568559, ET611457, and ET609552.
--------------------------------------------------------------------------------
Etrack Incident = ET614695
**Description:
When using Veritas NetBackup (tm) 6.0 through 6.0 MP2, if a multiplexed
backup receives an end of media (EOM) message, and before it can get new
media, another backup to the same drive fails, there is the potential for
data loss.
--------------------------------------------------------------------------------
Etrack Incident = ET614611
Description:
Double-free in rfile/wfile pointers, and cleanup -mtd memory problems with
bptm.
Additional Notes:
Refer also to ET586506.
--------------------------------------------------------------------------------
Etrack Incident = ET614611
Description:
Duplication jobs would fail with Status code 174; some contained the
following message:
*** glibc detected *** double free or corruption (fasttop):
Additional Notes:
Refer also to ET586506.
--------------------------------------------------------------------------------
Etrack Incident = ET614623
Description:
The NetBackup Resource Broker (nbrb) was not cleaning up the media
reservations after a job completed.
Additional Notes:
Refer also to ET576637.
--------------------------------------------------------------------------------
Etrack Incident = ET614595
Description:
The Ltid.exe executable no longer causes an exception fault when the mount
requests were disabled.
Additional Notes:
Refer also to ET582349 and ET568524.
--------------------------------------------------------------------------------
Etrack Incident = ET615412
Description:
A problem existed that caused duplication to fail with an error code of
114 and the following error message:
errorCode=114 not enough valid resources
Additional Notes:
Refer also to ET593538.
--------------------------------------------------------------------------------
Etrack Incident = ET615416
Description:
An change was made to correct a double-free problem that was occurring in
bptm.
Additional Notes:
Refer also to ET606797.
--------------------------------------------------------------------------------
Etrack Incident = ET615644
Description:
bptm was logging an informational message that was killing Vault
duplication jobs.
Additional Notes:
Refer also to ET615646 and ET579399.
--------------------------------------------------------------------------------
Etrack Incident = ET617303
Description:
A problem existed with the nbpushdata -add command that caused it to fail
to populate the globDB information into Enterprise Media Manager (EMM)
Database.
Additional Notes:
Refer also to ET597444.
--------------------------------------------------------------------------------
Etrack Incident = ET617304
Description:
The "nbpushdata -remove <host>" command failed when no media was assigned
to the host.
Additional Notes:
Refer also to ET599789.
--------------------------------------------------------------------------------
Etrack Incident = ET617298
Description:
Media was not being ejected from partially successful vaults after
installing the NetBackup 6.0 MP2 pack.
--------------------------------------------------------------------------------
Etrack Incident = ET606288 ET620428
Description:
The NetBackup Job Manager (NBJM) deadlocked while running jobs that backup
to tape.
Additional Notes:
Refer also to ET615617 and ET620561.
--------------------------------------------------------------------------------
Etrack Incident = ET613056 ET625106
Description:
The following ACSLS changes were added in this pack:
- Added multiple ACSLS support to Windows media servers. This requires
Sun (STK) Libattach version 1.4.1 be installed on all media servers
with ACS robotics.
- Added the latest Automated Cartridge System (ACS) media types.
- Upgraded to the latest IBM API for TLH robotics and added the latest
media types. Refer to the Support matrix on the Support Web site for
the latest versions.
- Corrected an ACS inventory query_clean failure when using LibStation.
- Corrected how Windows uses ACSLS ACS numbers that are greater than 0.
- Added TLH robotics support to Linux IA64. Refer again, to the Support
matrix on the Support Web site for the latest versions.
Additional Notes:
Refer also to ET571008.
--------------------------------------------------------------------------------
Etrack Incident = ET613063
Description:
The tpconfig menu user interface was unable to add shared robots or shared
robotic drives.
Workaround:
To avoid this issue, use the tpconfig command line interface instead of
the menu user interface.
Additional Notes:
Refer also to ET574537.
--------------------------------------------------------------------------------
Etrack Incident = ET613069
Description:
Enhanced the media selection algorithm for Automated Cartridge System (ACS)
libraries, to pick a media and drive in the same Library Storage
Module (LSM).
Additional Notes:
Refer also to ET580847.
--------------------------------------------------------------------------------
Etrack Incident = ET613070
Description:
Corrected an ACS library inventory with ACS_LTO_400G mapped to HCART2 in
the vm.conf.
Additional Notes:
Refer also to ET580782.
--------------------------------------------------------------------------------
Etrack Incident = ET613046
Description:
Enhancements have been made that enable the File System Export feature
with ONTAP 7.2. A new backup "mode" (space optimized image or SOI)has
been added along with multiple other changes.
Additional Notes:
Refer also to ET583099.
--------------------------------------------------------------------------------
Etrack Incident = ET613059
Description:
From the tpconfig menu user interface, you could not add a robot with
Shared Storage Option (SSO) drives.
Additional Notes:
Refer also to ET585032.
--------------------------------------------------------------------------------
Etrack Incident = ET613795
Description:
Oracle and Informix restores may hang or fail (via a timeout). In one
situation bptm log would contain the following message:
08:40:54.944 [20370] <2> mpx_read_backup: waiting for children to
terminate so exit status can be sent to bpbrm
In another situation the bpbrm log would contain the following message:
16:13:00.835 [173273] <8> bpbrm process_media_msg: unknown media message:
RCD_STOP_DB_RESTORE_STR
Additional Notes:
Refer also to ET565959 and ET519758.
--------------------------------------------------------------------------------
Etrack Incident = ET612145
Description:
A change has been added making it possible to move media from the merge
table when no media records exists.
Additional Notes:
Refer also to ET540166.
--------------------------------------------------------------------------------
Etrack Incident = ET613071
Description:
When configuring an ACS robot on LibStation, an API Display command was
not available when interfacing to an ACSLS Server.
Additional Notes:
Refer also to ET576449.
--------------------------------------------------------------------------------
Etrack Incident = ET613577
Description:
Duplication jobs may fail if the master server and media
server have intermixed fully-qualified-domain-names and
non-fully-qualified-domain-names for servers.
Additional Notes:
Refer also to ET613685.
--------------------------------------------------------------------------------
Etrack Incident = ET614680
Description:
NetBackup Policy Execution Manager (nbpem) would run deassignempty every
minute on some platforms.
Additional Notes:
Refer also to ET535910.
--------------------------------------------------------------------------------
Etrack Incident = ET614721
Description:
bmrsavecfg failed to collect system information on servers that were
running some versions of MSSQL server.
Additional Notes:
Refer also to ET598114.
--------------------------------------------------------------------------------
Etrack Incident = ET614711
Description:
In previous versions, to get the BMR bootserver patched binaries, you
would need to install the maintenance pack, install the BMR boot server,
then uninstall and reinstall the maintenance pack.
In this pack a repair options has been added that requires you to only
reapply the maintenance pack.
Additional Notes:
Refer also to ET595031.
--------------------------------------------------------------------------------
Etrack Incident = ET612154
Description:
To resolve media conflict issues, the following command can be used.
"nbemmcmd -deletemedia -mediaid <> -originhost NONE"
Changes have been added in this pack that accept "NONE" as a valid origin
host and as a special name.
Additional Notes:
Refer also to ET602232.
--------------------------------------------------------------------------------
Etrack Incident = ET614666 ET613688
Description:
If catalog compression was used on a UNIX master server, the bpdbm
process would not remove client images properly during catalog cleanup if
those images were compressed.
Over time, the disk space consumed by these images that were not removed
properly during catalog cleanup can be significant, although the exact
amount of extra disk space is highly dependant on retention level and
catalog compression configurable settings. (This problem does not affect
Windows master servers.)
Additional Notes:
Avoiding a "disk full" condition by having sufficient available disk space
for the image catalog prevents any operational problems.
If NetBackup 6.0 has been in use for some time and this problem has been
encountered, it is possible that the disk space consumed by the image
catalog (the /usr/openv/netbackup/db/images directory) will shrink
noticeably the first time that catalog cleanup is run after this fix is
applied. Because this is an expected result of applying this fix, do not
be concerned about this reduction in disk space consumption, no usable
files have been deleted.
Symantec recommends that a current catalog backup be completed and
available for recovery before applying the fix in case something unexpected
happens and there is a need to recover the catalog from the current catalog
backup image be encountered.
--------------------------------------------------------------------------------
Etrack Incident = ET615534
Description:
Jobs would fail with a status 25 because bptm could not communicate with
nbjm on the master server when going through a firewall.
Workaround:
To avoid this issue, configure the firewall so that it will wait a longer
time before closing idle connections.
Additional Notes:
Refer also to ET609217.
--------------------------------------------------------------------------------
Etrack Incident = ET615304
Description:
Fixed a problem that caused the NetBackup Policy Execution Manager (nbpem)
to crash with a "60patches/ENG/NB_60MP2_EEB_20060425" in place, when Vault
started.
Additional Notes:
Refer also to ET615305 and ET200604.
--------------------------------------------------------------------------------
Etrack Incident = ET615531
Description:
The MEDIA_UNMOUNT_DELAY function was not always honored for standalone
drives.
Workaround:
Before starting the job, make sure an eligible tape is loaded in the drive
to avoid this issue.
Additional Notes:
Refer also to ET514664.
--------------------------------------------------------------------------------
Etrack Incident = ET615336
Description:
The parent job, nbgenjob, was not completing properly, even though the
child jobs did complete.
Additional Notes:
Refer also to ET611441.
--------------------------------------------------------------------------------
Etrack Incident = ET615646
Description:
The Windows Backup, Archive and Restore user interface did not display all
images for restore (the older backup images were not displayed). Also,
when browsing a client which has a large number of non-standard backups,
bprd would core dump.
Workaround:
To avoid this issue, use the Java user interface and manually select the
start date to browse older images.
Additional Notes:
Refer also to ET579399.
--------------------------------------------------------------------------------
Etrack Incident = ET589069
Description:
Expired media was not being returned to the scratch pool, causing a bptm
status 220 error.
Additional Notes:
Refer also to ET589083.
--------------------------------------------------------------------------------
Etrack Incident = ET615560
Description:
Added the capability to retry immediate backups and allow multiple
schedules of the same policy to be suspended, or incomplete and resumable.
Additional Notes:
Refer also to ET615568.
--------------------------------------------------------------------------------
Etrack Incident = ET614778
Description:
Tracing messages that should appear at level 6 would appear at level 5 and
make the logs less readable.
--------------------------------------------------------------------------------
Etrack Incident = ET614736
**Description:
The Enterprise Media Manager (EMM) server uses a relational database to
store media and device configurations. When the file system runs out of
disk space, the relational database files that the EMM database uses can
become corrupt. This can cause the EMM database to fail to start and
cause backups to fail on the master server. To correct this situation,
the EMM server process monitors disk space and safely shuts down the
EMM database in the event of a disk-full condition.
Additional Notes:
Refer also to ET392256.
--------------------------------------------------------------------------------
Etrack Incident = ET615287
**Description:
Changes were made to the retention levels in Host Properties to resolve
issues that affected the Retention mapping settings in VAULT. This change
corrects a potential data loss issue for Vault customers who use the Vault
retention mappings feature via the user interface. For additional
information, refer to TechNote 282996, on the Symantec Support Web site.
Workaround:
To avoid this issue, disable the use of the Vault retention mappings.
Additional Notes:
This is a data loss issue that could cause vaulted media to expire sooner
than might be expected. Again, refer to TechNote 282996 for additional
details.
--------------------------------------------------------------------------------
Etrack Incident = ET616343
Description:
Media will now be deallocated after a failed multiple copy backup and
duplicated jobs.
Additional Notes:
Refer also to ET567364.
--------------------------------------------------------------------------------
Etrack Incident = ET613180
Description:
VSS Transportable backup of an Exchange server will fail eseutil
validation for Exchange data that exists on a mountpoint volume.
Additional Notes:
Refer also to ET536641.
--------------------------------------------------------------------------------
Etrack Incident = ET618092
Description:
NetBackup Policy Execution Manager (nbpem) crashed because of problems
with the pem persist file read and write.
Additional Notes:
When reading the pem persist file, the first line that could be read was
shifted off by 1 character. This could cause inconsistencies in the first
job in the file and occasionally even a crash.
Refer also to ET543123.
--------------------------------------------------------------------------------
Etrack Incident = ET614250
Description:
Jobs would sometimes not run when they were scheduled to run.
Additional Notes:
Policy Execution Manager (pem) would calculate the scheduled time of a
job. If the job did not run during the window, it may not run in the
next. This could happen with calendar or frequency scheduling.
Refer also to ET622829.
--------------------------------------------------------------------------------
Etrack Incident = ET619764
Description:
Policy Execution Manager would core dump when shuting down due to
nbproxy being shutdown when house cleaning tasks that use nbproxy were
still running.
--------------------------------------------------------------------------------
Etrack Incident = ET622846
Description:
When processing failure history, the Policy Execution Manger would core
dump when calling a library function that was not thread safe.
--------------------------------------------------------------------------------
Etrack Incident = ET624768
Description:
Fixed the About NetBackup dialog from Backup, Archive and Restore window
and the splash screan to display the proper version of the product.
--------------------------------------------------------------------------------
Etrack Incident = ET626204
Description:
The NetBackup Job Manager (nbjm) would crash when resources were obtained
for a generic job.
--------------------------------------------------------------------------------
Etrack Incident = ET626991
Description:
Removed a change to the Windows user interface that caused a regression.
--------------------------------------------------------------------------------
Etrack Incident = ET626960
Description:
Correted an issue that caused information to not be written to the
pem persist file consistently.
--------------------------------------------------------------------------------
Etrack Incident = ET626343
Description:
The NetBackup Job Manager (nbjm) would leak memory with every reference to
the job params file.
--------------------------------------------------------------------------------
Etrack Incident = ET627313
Description:
Policy Execution Manager would leak memory when reading failure history.
--------------------------------------------------------------------------------
Etrack Incident = ET627716
Description:
A change was made because the bprd executable (bprd.exe) was not being
replaced properly on an uninstall of NB_60MP3.
--------------------------------------------------------------------------------
Etrack Incident = ET630431
Description:
Changes have been made to remove the pempersist file before the services
are restarted during the pack installation.
--------------------------------------------------------------------------------
Etrack Incident = ET628695
Description:
A change has been added that prevents bpduplicate from corrupting heap
memory and crashing by copying a string into a too small destination string.
--------------------------------------------------------------------------------
Etrack Incident = ET613657
Description:
All Windows BMR Boot Servers now contain a new wizard to assist in
creating a CD image to be used for the Fast Restore feature.
This new feature is an exciting fast-windows-restore feature to the Bare
Metal Restore (BMR) option. This feature can perform a complete restore
of a Windows system in as little as 15 minutes. This feature means it is
no longer necessary to create DOS-based floppies or CDs. In addition,
this new feature enables BMR to operate in a low-infrastructure mode,
where the BMR Boot Server, Windows Shared Resource Tree, and the
Prepare-To-Restore step are no longer mandatory to restore a Windows
System.
For a description of how to use this new feature, along with feature
requirements and limitations, please refer to the Symantec TechDoc #283726.
This document can be accessed on the Symantec Support Web site using the
following URL:
http://support.veritas.com/docs/283726
================================================================================
=========
NB_60_2_M
=========
Etrack Incident = ET425117
Description:
Potential access violations, due to a (possibly) incorrect printf argument
list, are now averted.
--------------------------------------------------------------------------------
Etrack Incident = ET425322
Description:
There were a few instances in the code where the image query protocol
version was set to 0, which was a pre-NetBackup 5.0 image version ID.
Some image queries would fail if the size of the total data being backed
up was larger than 2 Terabytes in one job.
This issue has been corrected, thus enabling image queries on backups
greater than 2 Terabytes to work properly.
--------------------------------------------------------------------------------
Etrack Incident = ET427178
Description:
When sharing tape drives between media servers running both NetBackup 6.0
and NetBackup 5.x, a problem existed with the NetBackup 6.0 Scan Hosts.
If the drive being scanned was assigned to a NetBackup 5.x media server,
then the NetBackup 6.0 Scan Host might not stop scanning. This resulted
in SCSI reservation conflicts and DOWN'ed drives on the NetBackup 5.x
assigned host.
Workaround:
To avoid this issue, do not share drives between media servers running
different versions of NetBackup. Instead, pool your drives such that all
of your NetBackup 5.x media servers share one pool of drives and all of
your NetBackup 6.0 media servers share a pool of different drives.
--------------------------------------------------------------------------------
Etrack Incident = ET428597
Description:
When running multi-streamed Windows Open File Backup backups to back up
open or active files, some Volume Snapshot Provider (VSP) cachefiles in the
format of, _vxfiVspCacheFile_1.VSP, may be left behind by backup jobs that
have already completed. This does not occur with non-streamed backup jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET429921
Description:
When upgrading from NetBackup 5.x to NetBackup 6.0, the
NETBACKUP_RELATIONAL_DATABASE_FILES directive was not added to the list of
files included in cold catalog backup. The command, bpsyncinfo -add_paths
"NETBACKUP_RELATIONAL_DATABASE_FILES," is run automatically during the
patch installation to add this directive to the cold catalog backup
configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET430039
Description:
NBDB (for Enterprise Media Manager (EMM) and BMR) database recovery failed
if the master server had a newer catalog backup image than the one used in
Disaster Recovery (DR). On Windows platforms, it logged an error message
in the progress log and displayed a error message dialog. On UNIX
platforms, because of a defect in the Java user interface, it would only
report an error message in the log and all restore jobs appeared in job
monitor as successful.
Additional Notes:
With this fix, a user is able to recover from an older catalog backup even
though the user has a newer catalog backup image on the master server.
Full catalog disaster recovering from an older catalog backup is a
“roll-back” operation, that has potential of losing data. Users should
understand the implications and use it with caution.
--------------------------------------------------------------------------------
Etrack Incident = ET414315
Description:
When performing an Optical backup, the optical media will not use side B
once side A becomes filled. Instead a new platter is used. Once all
of the platters are filled on side A, side B of the platters is filled.
--------------------------------------------------------------------------------
Etrack Incident = ET431050
Description:
This pack corrects the frequency mode scheduling algorithm to function the
same as it did in the pre-NetBackup 6.0 product, when the frequency was a
multiple of 24 hours.
--------------------------------------------------------------------------------
Etrack Incident = ET422114
Description:
A problem was corrected that caused the NetBackup Policy Execution
Manager (nbpem) to dump a core file on shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET425135
Description:
Failed snapshots no longer cause "job retires" to become "new jobs".
--------------------------------------------------------------------------------
Etrack Incident = ET421439
Description:
Manual backups would not start immediately if the NetBackup Policy
Execution Manager (PEM) was started first.
--------------------------------------------------------------------------------
Etrack Incident = ET432263
Description:
For a Hot Catalog Backup, the relational database (NBDB/Sybase ASA) backup
job treated a cumulative and differential incremental backup the same and
only included the transaction log in the backup. This could create
problems when recovering the ASA database if the differential backup media
created before the last cumulative had expired. The differential backups
contain the transaction logs that are necessary to roll forward from the
last full backup. To fix this problem, the cumulative incremental backup
will be a full backup for the ASA files.
--------------------------------------------------------------------------------
Etrack Incident = ET430274
Description:
Because of a logic error in the handling of "bptm -delete_all_expired",
the expired media was not being deleted. This prevented recycling of the
media.
--------------------------------------------------------------------------------
Etrack Incident = ET428121
Description:
Upon de-allocating a drive, the Device Allocator (DA) was selecting a Scan
Host as if there had been no previous or existing Scan Host.
--------------------------------------------------------------------------------
Etrack Incident = ET421579
Description:
NetBackup tracks the media manufacturer and serial number in the
EMM database. Some drives do not support this data while some do.
If drives that do not support this type of data are added into a library
with drives that do support this type data, the database can end up with
multiple media with the same manufacturer and serial number information.
This condition would lead to problems loading the media at a future time.
--------------------------------------------------------------------------------
Etrack Incident = ET430429
Description:
The transport of log messages from NBSL to the NOM Server was failing and
causing the Host Session to go down.
POSIX-based systems can set either EWOULDBLOCK or EAGAIN when send() fails.
TAO (part of PSP) was testing just for EWOULDBLOCK. All other errnos were
considered harmful. This prevented the rest of the data from being flushed
out when send () raised EAGAIN. The clients never received the whole data
which caused the hang. A fix for PSP was provided that prevents this
issue from happening again.
--------------------------------------------------------------------------------
Etrack Incident = ET411601
Description:
An error occurred while creating a SUSE Shared Resource Tree (SRT).
Cleanup of this SRT would fail and display the following incorrect message:
[Error] V-125-376 No space left on device. Please ensure that the
specified target location for the Shared Resource Tree has adequate free
space, and retry the command.
Please refer to the Bare Metal Restore System Administrator's Guide
for the space requirements for creating Shared Resource Trees.
--------------------------------------------------------------------------------
Etrack Incident = ET430203
Description:
Expiring a non-multiplexed image should reduce the vimages and kbytes on
the media record. Because of a data conversion error, this reduction is
not taking place.
--------------------------------------------------------------------------------
Etrack Incident = ET429917
Description:
The vmd process no longer core dumps if the EMM service (nbemm) is not
running.
--------------------------------------------------------------------------------
Etrack Incident = ET427169
Description:
The nbpushdata operation fails when “pool name” has a hyphen in the pool
name.
--------------------------------------------------------------------------------
Etrack Incident = ET494938
Description:
Data tapes are no longer be treated as cleaning tapes and are FROZEN by
NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET495033
Description:
The Device Monitor shows the same tape mounted in multiple drives. This
tape is assigned to a NetBackup 5.x media server.
Workaround:
To avoid this issue, do not share drives between NetBackup 6.0 media
servers and NetBackup 5.x media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET492433
Description:
A race condition existed between NBRB and BPTM that would lead to jobs
getting 174 errors.
--------------------------------------------------------------------------------
Etrack Incident = ET430477
Description:
It is now possible to import Backup Exec images that have files with
filenames that contain embedded new-lines in them.
--------------------------------------------------------------------------------
Etrack Incident = ET496071
Description:
Some Oracle backups ended prematurely with status 25.
--------------------------------------------------------------------------------
Etrack Incident = ET495475
Description:
nbpushdata would fail with the following messages in the nbpushdata log
file:
<4> get_host_info: CEMM_MACHINE_DISK_ACTIVE being set for <your_host>
<16> emmlib_UpdateHost: (0) UpdateMachine failed, emmError = 2007079,
nbError = 0
<16> get_host_info: (-) Translating
EMM_ERROR_SQLSyntaxErrorOrAccessViolation(2007079) to 193 in the
Media context
--------------------------------------------------------------------------------
Etrack Incident = ET496956
Description:
A problem was causing the Windows open file backup to not show retries in
the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET420304
Description:
Originally, vmscd, was a single process that serviced requests from the
EMM server synchronously. Because of this, the EMM server was not
receiving the request response in a timely manner. In some cases, the
EMM server thinks that vmscd has exited, thus, triggering certain
operations that were redundant and in some cases harmful.
Now there are two vmscd processes. The parent vmscd process receives
requests from the EMM server and services them as soon as possible. The
child vmscd process collects the drive status from back level media
servers.
--------------------------------------------------------------------------------
Etrack Incident = ET496080
Description:
For media with image expiration set to infinity, nbpushdata would pass an
incorrect value for infinity to the EMM database; thus, the media could
not be queried.
nbemmcmd -listmedia -mediaid <media_id>
NBEMMCMD, Version:6.0(20050906)
The function returned the following failure status:
generic EMM SQL error (193)
Command did not complete successfully.
vmquery -m <media_id>
Could not query by media ID A00001 with debug: generic EMM SQL error (193)
--------------------------------------------------------------------------------
Etrack Incident = ET496958
Description:
The Data Lifecycle Manager consolidation jobs will now complete
successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET428319
Description:
A problem existed that caused the nbpushdata -remove command to fail.
Workaround:
To avoid this issue, the EMM data base was dropped and recreated.
--------------------------------------------------------------------------------
Etrack Incident = ET495345
Description:
The default start date, 01/01/1970 will not work for 'bpchangeprimary' in
any locale that does not display dates as mm/dd/yyyy.
Workaround:
If the start date is entered in the correct format for the locale it will
be accepted.
For example:
bpchangeprimary -copy 1 -sl sName -pn cjPName-st FULL -pt MS-Windows-NT
-sd 1070-01-01
--------------------------------------------------------------------------------
Etrack Incident = ET495866 ET496960
Description:
Changed bprd and pem so that the bprd child could terminate and not wait
for a job exit status from pem unless the -w flag was used on the request.
--------------------------------------------------------------------------------
Etrack Incident = ET428657
Description:
When you perform a raw backup with the encryption option enabled, using
the block device, and then you attempt a restore of the raw image to the
block device, the restore job would finish with a zero (0), however, the
data was not restored correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET497777
Description:
Could not inventory legacy TS8 libraries as TL8.
--------------------------------------------------------------------------------
Etrack Incident = ET497271
Description:
If any inetd entry is missing on a client and update_clients is used to
push NetBackup client software to it, update_clients will show an error
message in the log file. Corrections were made to the temporary file names
so that inet.conf on the client is updated properly and no error is
generated.
--------------------------------------------------------------------------------
Etrack Incident = ET497944
Description:
Under extremely heavy load in the Device Allocator, the DA may crash EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET496962
Description:
Some vital logs were not displaying correctly.
The form that Log:DbLogMsg is being called in emmserver source files was
incorrect whenever it was multi-lined in the code. As a result, only part
of the log message would survive and the important log information was
lost.
Currently many are in the wrong form of:
Log::DbLogMsg( EMMLOG_DEBUG3, who,
"<MANUALCONF> Control host name is NOT passed in, "
"Assuming incoming host < %s > as the control host",
machineName.c_str() ) ;
The quotes were not being processed correctly so the line starting with
"Assuming” would not appear.
--------------------------------------------------------------------------------
Etrack Incident = ET498496
Description:
Non-robotic tape drives that contain unlabelled media are no longer
automatically assigned to non-robotic media specific mount requests.
--------------------------------------------------------------------------------
Etrack Incident = ET498519
Description:
In a rare condition, one or more backups would be corrupt when using
Inline Tape Copy (ITC) with multiplexed backups. This could happen under
the following conditions:
- ITC was enabled with two or more active copies.
- Multiplexing was enabled with two or more active backups.
- The schedule configuration had "continue if the copy fails" flag
set for the copy that failed in the next step.
- A copy other than the first active copy encountered "end of media", so
a new media was needed for this copy. Then, there was a problem getting
or configuring media (for example, writing the media header) such that
this copy failed before continuing the backup.
- The last buffer written to the first active copy prior to the "end of
media" on the other copy was not the first active backup.
Workaround:
To avoid this problem, do one of the following:
- Edit the schedule configuration to disable the "continue if copy fails"
flag.
- Disable multiplexing.
- Disable ITC.
--------------------------------------------------------------------------------
Etrack Incident = ET428317
Description:
The back-level media server request, V_QUERY_CLEAN_BYROBNUM, would cause
an SQL error.
--------------------------------------------------------------------------------
Etrack Incident = ET420766
Description:
The vmoprcmd -devmon ds command is failing with a Corba exception.
--------------------------------------------------------------------------------
Etrack Incident = ET499611
Description:
Synthetic backup could have potential data loss in following cases:
- Last full/synthetic, full expired/deleted backup, followed by one or
more incremental backups, and a synthetic backup.
- Last incremental/full backup catalog was compressed before the next
incremental backup takes place.
- TIR records in the last incremental backup are missing for various
reasons
--------------------------------------------------------------------------------
Etrack Incident = ET506459
Description:
Media Servers that share drives on versions of NetBackup older than
NetBackup 6.0 receive host_not_registered errors when attempting to
decree another media server is unavailable.
--------------------------------------------------------------------------------
Etrack Incident = ET495457
Description:
The base NetBackup UNIX Agent has now been integrated with VxFS
Checkpoints. It has been modified to detect VxFS checkpoints using the
mount table's special options, and then use VxFS supplied APIs to detect
sparseness in them, and handle it accordingly.
Without these changes, a base NetBackup UNIX Agent could not tell if the
zero or smaller physical size of VxFS checkpoints, as compared to the
reported file size, is due to actual sparseness of the file or not. The
result was the base NetBackup UNIX Agent had to look through the whole
file and try to determine sparseness; thus, slowing down the backups
considerably.
--------------------------------------------------------------------------------
Etrack Incident = ET293930
Description:
This fix improves the performance of the NetBackup Error log collection
logic because the NBLogCollector was not seeking to a known spot for
performance reasons. To address this issue, logic was changed to get
newly-added error log messages by using a stat() system call to learn the
modified time of the error log file and keeping the opened file for the
next collect() call to maintain the current read position of the file.
--------------------------------------------------------------------------------
Etrack Incident = ET496560
Description:
The NetBackup Service Layer (NBSL) no longer causes a core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET507270 ET507266 ET507656
Description:
The following three issues have been address:
- Under certain conditions backups may not schedule. This would happen
because of a problem in computing the next time a job is due. Windows
were not processed correctly if a backup should have run in a previous
window and if the next window opened or closed at a different time.
- The Advanced Client VSS snapshot backup produced an 805 error. A
mistake in nbpem's logic would cause a child job to be resumed or
restarted using an old job id. It would use the jobid of the parent,
resulting in and an invalid jobid.
- The scheduler would always execute full backups, even for incremental
backups, if the BMR option was on. nbpem would use the wrong criteria
for a last backup query made for a parent job that did not have
multiple data streams enabled. The result was no last full backup
being found, so a full backup would be run instead of an incremental.
--------------------------------------------------------------------------------
Etrack Incident = ET506080 ET566045
Description:
In a cluster under NetBackup Access Control the credential associated with
the physical node name is no longer picked up rather than the virtual host
name associated with NetBackup. And in a cluster, an attempt will be made
to use a credential created using bpnbat -loginmachine for the virtual
host name.
Workaround:
To avoid this issue, create credential files for both the physical host
names and the virtual hostnames for each node in the cluster. For details
on how to create credentials, refer to the NetBackup System Administrator's
Guide Volume II, Chapter 1, "Access Management".
--------------------------------------------------------------------------------
Etrack Incident = ET495479
Description:
The NetBackup Service Layer (NBSL) no longer causes a core dump when NOM
is configured. The core dump would occur when NetBackup 5.x media servers
were configured to a NetBackup 6.0 master server and NBSL would attempt to
collect data from the 5.x media server.
--------------------------------------------------------------------------------
Etrack Incident = ET507657
Description:
An error would occur when nbpushdata used emmlib_DeleteHost to remove the
NDMP host server. An error similar to the following was written to the
nbemm log.
11/11/05 15:54:41.185 [Debug] NB 51216 nbemm 111 PID:13393 TID:1196157872
[No context] 1 [DbConnection::Execute] SQL - retval=2007085(2007085)
retdal=-1 native=<-143> sqlerror=<[Sybase][ODBC Driver][Adaptive Server
Anywhere]Column 'FQMachineName' not found> sqlstate=<42S22>
--------------------------------------------------------------------------------
Etrack Incident = ET498714
Description:
A change was made to address conflicts in the EMM_Media table
after an upgrade. An EMM server change was made in the
helperAssignUpgradeImageInfoToMergeTable to accept "NONE" as
a valid assigned host name. This change was needed for the
following command:
# /bp/bin/admincmd/nbemmcmd -forcemerge -assignedhost NONE -mediaid A00000
-originhost pjcbk001 -reversemerge
--------------------------------------------------------------------------------
Etrack Incident = ET498037
Description:
User names and group names longer than 32 characters were not supported.
Workaround:
To avoid this issue, you should use group names and user names that are
smaller than 32 characters.
Additional Notes:
Even with this fix, max possible gname and uname allocated is 1024 chars
--------------------------------------------------------------------------------
Etrack Incident = ET507646
Description:
In certain cases when NetBackup Access Control was enabled, long-lived
processes, such as, nbemm, nbpem, nbjm, nbrb, nbproxy, nbsl, and vmd may
have leaked memory.
--------------------------------------------------------------------------------
Etrack Incident = ET509198
Description:
The SQL SERVER backup would complete normally, however, the client user
interface would display -1 status. Improper progress log updates caused
this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET506666
Description:
A Linux client with an empty or non-existent /etc/resolv.conf file would
halt at restore time even though the client's original configuration did
not use the /etc/resolv.conf file.
Additional Notes:
Linux Shared Resource Trees (SRT) created after this pack is applied will
correctly handle an empty or non-existent /etc/resolv.conf file.
--------------------------------------------------------------------------------
Etrack Incident = ET509505
Description:
Spanning media jobs occasionally appeared to be hung, the request would
continually fail with the message, "ROBOTIC LIBRARY IS DOWN ON SERVER".
This typically occurred after an earlier failure of,
"MEDIA SERVER IS CURRENTLY NOT CONNECTED TO MASTER SERVER". However, the
media server would show the robot as being up and the host as ACTIVE or
ACTIVE-TAPE.
--------------------------------------------------------------------------------
Etrack Incident = ET367776
Description:
The NetBackup Service Layer (NBSL) no longer hangs in a "stopping" state
in the Windows Service Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET506668
Description:
For Linux clients, some S-ATA devices were not being handled correctly
at restore time. Changes contained in this pack load the proper modules
correctly in the restore environment so the restoration can be performed.
Additional Notes:
The original problem presents itself when the restore environment boots.
After loading the SRT, the restoration will stop, requesting for a reboot
of the client, with a boot order string that contains the ata_piix module.
Even if the client is rebooted and the order string is passed from the boot
prompt, the message appears again and the restoration can never proceed.
Once this patch is applied on the Boot Server, the SRT needs to be
recreated for this fix to be available. SRTs created with bmrsrtadm
versions prior to the one contained in this patch will have the problem.
--------------------------------------------------------------------------------
Etrack Incident = ET509087
Description:
A change was made that enables vmd to retry and make the connection to
EMM indefinitely, instead of shutting down if it could not make the
connection.
--------------------------------------------------------------------------------
Etrack Incident = ET500512
Description:
There are end case situations especially when a master server cluster node
goes inactive where the bprdreq -terminate and bpdbm -terminate commands
in bp.kill_all might take several minutes to complete. This can cause
inconsistencies in a cluster enviroment.
--------------------------------------------------------------------------------
Etrack Incident = ET511942
Description:
From the NOM user interface, it is not possible to start a service/deamon
when NetBackup is on UNIX operating systems.
--------------------------------------------------------------------------------
Etrack Incident = ET509733
Description:
NBSL was occasionally sending negative values for the “free space” and
“total capacity” of a storage unit (particularly if the values are
greater than 2^32-1).
--------------------------------------------------------------------------------
Etrack Incident = ET499203
Description:
bpdbjobs -all_columns takes a segmentation fault in either the FreeJobs()
or PrintJobs() function with a stack overflow.
--------------------------------------------------------------------------------
Etrack Incident = ET511981
Description:
It is now possible for SAN media servers to be used as write hosts for
duplicate jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET419837
Description:
Some keys generated by bpkeyutil for standard encryption would cause
backups to fail. The failure status is 40 - network connection broken.
About one out of 256 keys caused this failure.
--------------------------------------------------------------------------------
Etrack Incident = ET512393
Description:
VxUL queries no longer fail on AIX platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET509994
Description:
Changed the way NetBackup package versions are stored in SRT records so
that the history of maintenance is preserved.
--------------------------------------------------------------------------------
Etrack Incident = ET509547
Description:
A problem existed that was limited to a DSSU duplication (not a vault or
manual duplication issue) that would take more than 59 minutes to
complete. After 20 minutes, a status 50 occurred, but the underlying
duplication still had 39 more minutes to finish. After 59 minutes,
EMM noticed the "problem" and shut down the job.
--------------------------------------------------------------------------------
Etrack Incident = ET513419
Description:
NBNos no longer runs in single-threaded mode only.
--------------------------------------------------------------------------------
Etrack Incident = ET511008
Description:
If there is more that one user schedule in a policy, and a schedule is
not specified in the backup request, the job may fail with a 199 error
(no open windows).
Workaround:
To avoid this issue, either specify the schedule name in the backup
request, or do not create more that one user schedule in a policy.
--------------------------------------------------------------------------------
Etrack Incident = ET510797
Description:
A job that fails with a 196 error (EC_no_attemp_window_close) will be left
in a “waiting for retry” state instead of being done.
--------------------------------------------------------------------------------
Etrack Incident = ET499144
Description:
When running multi-streamed Windows Open File Backup backups, jobs would
fail with a status 200 error.
--------------------------------------------------------------------------------
Etrack Incident = ET513486
Description:
The following back-level SSO interoperability issues have occurred:
- Numerous re-registrations were consuming all of vmd's bandwidth on the
EMM server.
- Registration failures would occur because the no-scan-host setting,
registration retry timer would block back-level servers from releasing
drives.
- Back-level remote scanning of NetBackup 6.0 media servers was failing
with ENOTSCANHOST and forcing even more registrations to occur.
Workaround:
DO NOT SHARE DRIVES BETWEEN 6.0 AND 5.X MEDIA SERVERS.
--------------------------------------------------------------------------------
Etrack Incident = ET516562
Description:
nbemm no longer core dumps with a clustered master server.
--------------------------------------------------------------------------------
Etrack Incident = ET511445
Description:
To improve performance of nbpem, all sorting has been removed.
--------------------------------------------------------------------------------
Etrack Incident = ET506661
Description:
After installing NetBackup into a Solaris Shared Resource Tree (SRT), if
the source of the installation is a CD-ROM, the device is left mounted and
the CD-ROM cannot be ejected.
Workaround:
After installing NetBackup into the Shared Resource Tree, exit bmrsrtadm,
start bmrsrtadm again, and this time choose the Share Resource Tree that
was just created.
--------------------------------------------------------------------------------
Etrack Incident = ET516645
Description:
If nbpem received a request to terminate while a terminate request was
being processed, the Policy Execution Manager (pem) would crash.
--------------------------------------------------------------------------------
Etrack Incident = ET326958 ET518198 ET424885 ET387319 ET415289 ET414469 ET422797
ET424915 ET515462 ET499211 ET520460 ET427072
Description:
Added support for the following libraries:
EMC NDMP VTLU
Falcon Stor
IBM 3576 Library
IBM TS7510 Virtualization Engine
HP MSL-2024 G3 Series
Added support for the following drives:
IBM 3592E05
Sony SDX 800v
Updated support for the following libraries:
ADIC Scalar i2000
Quantum TZ Media Changer
Updated support for the following drive:
ADIC i500
IBM 3592
--------------------------------------------------------------------------------
Etrack Incident = ET421278
Description:
Force the UNIX implementations of the BPCD_FORK_CMD_W_STAT_RQST,
BPCD_FORK_OTHER_CMD_RQST, and BPCD_EXECUTE_CLIENT_CONFIG_RQST protocols
to wait as long as necessary for the [child] command to complete.
Previously, the command would have been killed if it did not complete
within BPCD_TIMEOUT seconds (300). This behavior was unwarranted, and
was inconsistent with the Windows implementation, which already waits an
indefinite time. In addition, supporting code that was not necessary
was removed.
--------------------------------------------------------------------------------
Etrack Incident = ET515306
Description:
At “fall-back time” for daylight savings time, the calendar scheduling
may repeatedly run the same job.
--------------------------------------------------------------------------------
Etrack Incident = ET514752 ET563731
Description:
A change made to bpexpdate such that, media IDs that are less than six
characters, and returned from EMM, were not padded with spaces. This
caused bpexpdate -deassignempty to mistakenly deassign media that still
had valid images on them.
Workaround:
To avoid this issue, turn off the automatic start of
bpexpdate -deassignempty by performing one of the following items:
- On a UNIX master server, create the file,
/usr/openv/netbackup/bin/bpsched.d/CHECK_EXPIRED_MEDIA_INTERVAL,
and enter a 0 (zero) on the first and only line of the file.
- On a Windows master server, create the file,
<install_path>\NetBackup\bin\bpsched.d\CHECK_EXPIRED_MEDIA_INTERVAL,
and enter a 0 (zero) on the first and only line of the file.
--------------------------------------------------------------------------------
Etrack Incident = ET507316
Description:
The bprd log message was off-by-one for process_command(). This lead to
log messages like:
15:23:10.035 [115624.76592] <2> process_request: command unlisted command
(114) received (where 114 is actually get_hostinfo)
--------------------------------------------------------------------------------
Etrack Incident = ET519755
Description:
The partial restore of a database backup fails. For example, restoring
a single Oracle tablespace from a backup set.
The following types of messages will be found in the bptm log:
14:50:59.752 [19995] <2> read_brm_msg: STOP RESTORE algol_1134518480 EXIT=0
14:50:59.752 [19995] <2> process_brm_msg: GCACTIVE but CHILD_PID not alive
The following types of messages will be found in the dbclient log:
14:50:59.718 [1932.1552] <4> closeApi: INF - FORCED EXIT STATUS 0: the
requested operation was successfully completed
14:50:59.718 [1932.1552] <4> closeApi: INF - closing commSock 220
14:50:59.718 [1932.1552] <4> closeApi: INF - Do not close dataSock
14:50:59.718 [1932.1552] <4> closeApi: INF - closing nameSock 952
14:50:59.718 [1932.1552] <4> serverExitStatus: entering serverExitStatus.
14:50:59.718 [1932.1552] <4> readCommMessages: Entering readCommMessages
15:06:04.724 [1932.1552] <16> readCommFile: ERR - timed out after
900 seconds while reading from C:\Program Files\VERITAS\
NetBackup\Logs\user_ops\dbext\logs\1552.0.1135025111
--------------------------------------------------------------------------------
Etrack Incident = ET518079
Description:
The vmscd's time-out while communicating with back-level servers was too
small. Because of this, vmscd would think that the back-level server was
not running and it used to decree that the host was unavailable.
As part of this fix, the time-out value was raised.
--------------------------------------------------------------------------------
Etrack Incident = ET511741
Description:
vlteject no longer fails with the following error when tapes are taken
out of the map after long time.
"vmchange eject verify not responding[300]"
--------------------------------------------------------------------------------
Etrack Incident = ET512872
Description:
Removed the change events for Error LogMonitoring. For example, the error
log collection functionality was removed. In addition, the
getLogMessages() idl method supports the error log source; thus, NOM call
this method for getting error logs. Finally, the getEventChannel()
functionality has been removed, resulting in an AFException.
Additional Notes:
Because of this fix, log monitoring of NOM 6.0 MP2 only works with
NetBackup 6.0 MP1 or MP2.
--------------------------------------------------------------------------------
Etrack Incident = ET511772
Description:
Pagination on the report in myportal did not work if table was accessed
after long duration of time.
--------------------------------------------------------------------------------
Etrack Incident = ET413396
Description:
The LANG environment variable was not being properly inherited from the
master's invocation. Because the locale was passed as an argument to the
user server invocation, there was no harm in redundantly performing a
putenv() from the user server.
--------------------------------------------------------------------------------
Etrack Incident = ET522065
Description:
Restore to an alternate client (not a master or media server) by a
media server fails with error status 159:
The licensed features for this system do not permit the backup of a
remote client (<client> ). Make sure that the license key is entered
properly. In addition, SAN media server licensing should be enforced
for backup but not for restore to allow maximum flexibility for DRM
data restoration.
--------------------------------------------------------------------------------
Etrack Incident = ET522555
Description:
Vault failed to run properly from the user interface in VxSS/NBAC
configuration. While in a start session from the user interface, the job
failed to execute, and nothing appeared in the Activity Monitor. This was
observed for any valid user (Administrator) with all the required
permissions. This fix enables executions that originate from the user
interface to be processed properly.
--------------------------------------------------------------------------------
Etrack Incident = ET432239 ET508863
Description:
Corrected ACS timeouts when the ACSLS server had communication problems
with the media server.
To correct this problem, a 20 second wait was removed before checking for
drive readiness on an ACS mount.
--------------------------------------------------------------------------------
Etrack Incident = ET520519
Description:
A stack-based buffer overflow vulnerability existed in the volume manager
daemon (vmd) running on NetBackup servers. If an attacker was able to
gain access to a vulnerable NetBackup server and successfully exploit this
issue, it could have lead to arbitrary code execution and resulted in
unauthorized access with elevated privileges on the targeted system.
This vulnerability impacted only NetBackup server systems and did not
impact NetBackup client systems.
--------------------------------------------------------------------------------
Etrack Incident = ET432236
Description:
Corrected the use of access bits with the mailslot and with the storage
slots in the robotic libraries.
To correct this issue, add a wait before an eject for Vault-style ejects
for libraries that take extra long for the mailslot to come ready after
being accessed.
Additional Notes:
Access bit checking may require a new device_mappings file, it depends on
the robot.
--------------------------------------------------------------------------------
Etrack Incident = ET512890
Description:
Support 24 character drive serial numbers.
--------------------------------------------------------------------------------
Etrack Incident = ET523022
Description:
NetBackup Resource Broker (NBRB) may hang at startup time if database
records have been corrupted.
--------------------------------------------------------------------------------
Etrack Incident = ET511782
Description:
Thread handles were not being released properly in NBSL, when a new
thread pre-fetched a block of media and volume records from EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET522971
Description:
NBSL no longer sends deletion events for Jobs to NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET516605
Description:
Under certain conditions, NetBackup Job Manager (NBJM) runs out of
threads. As a result no new jobs can be initiated and the existing
jobs do not complete.
Workaround:
To avoid this issue, kill and restart the NBJM service.
--------------------------------------------------------------------------------
Etrack Incident = ET493991 ET431087
Description:
An Incremental NetBackup Catalog Backup ends up backing more data
than necessary.
NetBackup Catalog Backup was re-architected in NetBackup 6.0. The plan
was to also support NetBackup Catalog Move Detection. While supporting
that for UNIX by using ctime, in addition to mtime, for deciding on
which files to backup, inadverently opened the door for more directories
to be backed up, since the ctime gets changed for parent directories
of directories under which new catalog is being created. This resulted
in entire client catalog to be backed up again, if there was any other
backup done for that client.
The solution provided in this patch is to use NBU's existing TIR w/Move
Detection logic for NetBackup Catalog Move Detection.
--------------------------------------------------------------------------------
Etrack Incident = ET523400
Description:
In a cluster, Disk staging (duplication to tape) uses the local node name
as the media server instead of the virtual name. Because of this,
bpduplicate may fail with the error, “host is unreachable (47)”.
--------------------------------------------------------------------------------
Etrack Incident = ET496959
Description:
NetBackup Job Manager (NBJM) would deadlock or halt when the connection to
bpbrm breaks in the middle of a backup job.
--------------------------------------------------------------------------------
Etrack Incident = ET516377
Description:
NBPEM would crash if a thread referenced a deleted object. This is a
timing problem and can happen when:
- A thread decrements the ref count on an object
- The thread is stalled
- The object is destroyed (ref count = 0)
- The stalled thread starts running and it references the destroyed object
The above problem has been corrected by ensuring that the object is not
referenced after the reference count has been decremented.
--------------------------------------------------------------------------------
Etrack Incident = ET496074
Description:
Restores failed with the following errors in the job log and tar debug log:
job log:
22:16:27 (4753.046) data buffers out of sequence, expected number 157884,
received 157886
23:32:46 (4753.053) data buffers out of sequence, expected number 404927,
received 404932
debug log:
22:16:27 (4753.046) data buffers out of sequence, expected number 157884,
received 157886
23:32:47 (4753.053) data buffers out of sequence, expected number 404927,
received 404932
This issue occurred because the HP-UX 11.23 compiler optimized-out
references to the shared memory control variables.
--------------------------------------------------------------------------------
Etrack Incident = ET425567
Description:
Fixed memory leak in Policy Execution Manager. The leak occurred when
processing any configuration change event sent by NBNos, which passes a
sequence of name value pairs.
--------------------------------------------------------------------------------
Etrack Incident = ET516907
Description:
An exception occurred in NetBackup Generic Job (nbgenjob), where getting
a policy from nbproxy while performing a stream discovery forced a retry.
The first retry resulted in a core dump because the internal file list was
not cleared before rereading the STREAMS file. To resolve this core
problem, the stream discovery was changed to clear the internal file list
before reading the STREAMS file, and to only read the STREAMS file once.
--------------------------------------------------------------------------------
Etrack Incident = ET431505
Description:
Changed nbproxy to catch exceptions when either of the IOR files listed
below in the var directory are empty to prevent the Policy Execution
Manager (nbpem) from exiting on startup.
IOR files in var directory are:
- nbproxy_pem.ior
- nbproxy_pem_email.ior
Workaround:
To avoid this issue, remove the empty IOR files nbproxy_pem.ior and
nbproxy_pem_email.ior from the var directory. On UNIX, the var directory
resides in /usr/openv, and on Windows, it resides in VERITAS\NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET425565
Description:
For user and manual backups, changes have been made that prevent Policy
Execution Manager (nbpem) core dumps by fixing the message queue locking
function.
--------------------------------------------------------------------------------
Etrack Incident = ET423142
Description:
Fix CT_EXCHANGE backup job when streaming is not enabled. Changed Policy
Execution Manager (nbpem) to set stream number to zero for the child
CT_EXCHANGE job. Nbpem was setting it to -1, which made the delta time
option (-dt) that was passed to Bpbrm, zero.
--------------------------------------------------------------------------------
Etrack Incident = ET427069
Description:
Parent job (nbgenjob) did not detect that the Policy Execution Manager
(nbpem) went down so it waited indefinitely for a response. Changed
nbgenjob to ping nbpem using the birth time that was returned to determine
if Policy Execution Manager was running.
--------------------------------------------------------------------------------
Etrack Incident = ET518632
Description:
Fixed NetBackup Resource Broker (nbrb) so that it disconnects from
Sybase ASA when it receives a suspend before a cold catalog backup.
If nbrb does not disconnect from ASA, when Sybase ASA is shutdown for
the cold catalog backup, warnings similar to the following appear in
the Sybase server.log file: Connection terminated abnormally.
--------------------------------------------------------------------------------
Etrack Incident = ET498975
Description:
Idle media servers no longer go offline (such as, "ACTIVE-DISK", "OFFLINE").
--------------------------------------------------------------------------------
Etrack Incident = ET520924
Description:
The function, decree_host_unavailable, from NetBackup 5.x media servers
was causing the NetBackup 6.0 media servers to go offline.
--------------------------------------------------------------------------------
Etrack Incident = ET520279
Description:
The scanability setting of media servers in the EMM database is being
overwritten by the ltid processes of the media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET518557
Description:
Using the wizard to reconfigure NDMP-attached tape drives no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET519239
Description:
"bpexpdate –recalculate" and "bpexpdate -backupid" both allow image
expiration dates to be changed while an image duplication is in progress.
If the image spans tapes, this can result in different expiration dates
for the individual fragments.
Workaround:
To avoid this issue, do not run "bpexpdate –recalculate" or
"bpexpdate -backupid" while an image duplication is in progress.
--------------------------------------------------------------------------------
Etrack Incident = ET520937
Description:
This fix eliminates a program fault that attempts to get the media server
catalog path list from a NetBackup 5.x media server when the back-level
server has become unresponsive.
Workaround:
To avoid this issue, make certain all the back-level servers are
functioning.
--------------------------------------------------------------------------------
Etrack Incident = ET508741
Description:
Robot Name is now displayed correctly in NOM user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET517878
Description:
Over time, the NBJM process grew in size as jobs were run. The system was
configured to use security.
Workaround:
To avoid this issue, disable security or restart NBJM periodically.
--------------------------------------------------------------------------------
Etrack Incident = ET515457
Description:
Eliminated a potential memory leak when retrieving a list of hosts that
are sharing drives and list of shared drives in a master server domain.
--------------------------------------------------------------------------------
Etrack Incident = ET417455
Description:
BPTM may report an incorrect error at the end of some restore and
duplication jobs that is similar to the following error.
"invalid job id (805)"
--------------------------------------------------------------------------------
Etrack Incident = ET424097
Description:
Synthethic backups would fail or hang on Solaris systems with a low
resource limit for the maximum file descriptor. The bpsynth log would
contain the following:
ACEMsgTran::updateReactor_u: unable to register handle with the reactor
On a few HP-UX systems, bpsynth may core dump if the maximum file
descriptor resource limits are not configured properly.
Workaround:
To avoid this issue, configure the system so that the maximum number of
open files per process is at least 512.
--------------------------------------------------------------------------------
Etrack Incident = ET431087 ET493991
Description:
On UNIX platforms, the catalog moving detection that used ctime and mtime
in an incremental catalog backup, was not always reliable. This resulted
in backing up catalog files that were modified since the last full backup.
To resolve this issue, use the TIR moving detection capabilities in bpbkar
and remove the catalog moving detection code from the catalog backup
library.
--------------------------------------------------------------------------------
Etrack Incident = ET524813
Description:
For Disk-to-Tape duplications, with disk images that were fragmented,
several problems would occur, for example:
- Duplication operations would get this error, "unable to read bpduplicate
message, premature end of file encountered (errno = I/O error)", which was
incorrect.
- Duplication operations could inadvertently mix retention levels on the
output media.
Workaround:
To avoid these duplication issues, touch the following file:
/usr/openv/netbackup/NODTTSDUP.
--------------------------------------------------------------------------------
Etrack Incident = ET431511
Description:
After importing a certain type of NDMP backup, the restore would fail
because the NUM_FILES in the catalog image header was set to zero (0).
The cause was that bpdbm did not count the extra directory entries and
NDMP environmental variables during importing process.
--------------------------------------------------------------------------------
Etrack Incident = ET522253
Description:
Changes have been made the enables the use of FORCE_RESTORE_MEDIA_SERVER
for Basic Disk storage units.
--------------------------------------------------------------------------------
Etrack Incident = ET525778
Description:
Long delays, of as much as 20 minutes, can occur before the Policy
Execution Manager starts a job. The Policy Execution Manager submit
function calls hosts_equal, which sets the maxJobsPerClient value that
is sent to Job Manager, and this may cause a long delay if you have a
lot of clients that are not accessible.
To avoid a long delay in the job submission, you must first determine
if any client is timing out. To do this, change the Policy Execution
Manager debug level to 4 or higher so that the Policy Execution Manager
debug messages are displayed when setting the maxJobPerClient field
during job submission. The debug statements enable you to determine
which clients are timing out. A timeout condition means a client no
longer exists or it is not accessible. After you have determined which
client(s) is timing out, either remove the client from the policy or
make sure it is accessible.
--------------------------------------------------------------------------------
Etrack Incident = ET513067
Description:
Changes have been made to correct a potential core dump when attempting
to get an application cluster list.
--------------------------------------------------------------------------------
Etrack Incident = ET507870
Description:
The Media IDs were not converted to upper case correctly and caused
unexpected mismatches.
--------------------------------------------------------------------------------
Etrack Incident = ET524628 ET533634
Description:
Exchange Transportable backups would fail with a status 69 and resulted
in no parent jobs (nbgenjob) starting. To correct this problem, a changed
was made to the Policy Execution Manager to start a parent job (nbgenjob)
if the policy fields "frozenImage" and "off host backup" are enabled and
streaming is disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET524690
Description:
When executing update_clients to push NetBackup client software to a
Linux x86 machine running a 2.4 kernel, it may fail with a message
that libvxstlportST.so is busy. That library is now being installed
as libvxstlportST.so_new and has been added to move_libs similar
to how some other key binaries are handled.
--------------------------------------------------------------------------------
Etrack Incident = ET525328
Description:
update_clients currently fails when using the <HW> <OS> method of
execution. The check that caused this error has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET527265
Description:
If USE_VXSS is set to automatic, it was possible that a copy of the
originator credential would be leaked when negotiating a secure
connection. In addition, an address buffer is no longer leaked if an
insecure connection is received.
--------------------------------------------------------------------------------
Etrack Incident = ET523630
Description:
On HP-UX IA64 platforms, the command bpclntcmd -ip <xxx.xxx.xxx.xxx> would
return the following:
unrecoverable, sorry
host <xxx.xxx.xxx.xxx>: not found.
Changes have been made to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET514064
Description:
Changes have been made to eliminate a code vulnerability that would lead
to a potential core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET527481
Description:
NBJM no longer leaks small amounts of memory while running multi-streamed
jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET512447
Description:
A failed bmrsavecfg on the client will now correctly show a non-zero
status in the job monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET429756
Description:
A change has been made to resolve the problem of media remaining mounted
after a synthetic backup. This would only happen if the following
conditions applied:
- The incremental image is very small (assuming the image is on A00001)
- The mount of tape for writing fails the first time (for example, the
tape A00002 was selected first and then the mount of this tape failed).
- The tape, given for the write (the second time after the mount failure)
is the same as the one where the small incremental image exists
(such as, A00001 in this case).
--------------------------------------------------------------------------------
Etrack Incident = ET495489
Description:
A non-multiplexed duplication of a TIR backup written to tape would fail
if the last fragment was zero bytes in length.
--------------------------------------------------------------------------------
Etrack Incident = ET527391
Description:
A potential race condition existed in which the log roll-over at midnight
in ltid could cause NBAC-related log messages to be written to the wrong
file descriptor.
--------------------------------------------------------------------------------
Etrack Incident = ET507962
Description:
bprd has a relatively large memory footprint at start up.
Workaround:
To avoid this issue, do not save large number of VxUL logs.
--------------------------------------------------------------------------------
Etrack Incident = ET521857
Description:
The NOM server no longer consumes large amounts of memory during the
Media Data Load. Part of this problem was caused by NBSL returning all
the media data to NOM when NOM reconnected instead of changing media data.
To resolve this issue, a change was made to the media collector design so
that NBSL sends only changed media instead of all media.
--------------------------------------------------------------------------------
Etrack Incident = ET519432
Description:
Deleting media by volume group would not update the conflicts flags in
EMM_Media.UpgradeConflictsFlag.
--------------------------------------------------------------------------------
Etrack Incident = ET509879
Description:
Changes have been made that prevent a user from configuring devices,
media, media pools, and barcode rules after an upgrade from NetBackup 5.x
to NetBackup 6.0 until nbpushdata has been run.
--------------------------------------------------------------------------------
Etrack Incident = ET526256
Description:
Changes have been made to improve the policy data collection's performance.
--------------------------------------------------------------------------------
Etrack Incident = ET492321
Description:
Fixed an issue with AIX 5.3 and later so that ACLs are now correctly
backed up and restored.
--------------------------------------------------------------------------------
Etrack Incident = ET519253 ET530848
Description:
Bpverify limits the amount of errors it logs to a maximum of 10 entries.
In certain cases, it is useful to log all of the errors and to be able to
manually adjust the catalog file to allow a successful restore. A new
option, -dml, was added to bpverify that disables the maximum amount of
error logging.
--------------------------------------------------------------------------------
Etrack Incident = ET355520
Description:
If a backup mounts a filesystem in bpstart_notify, starts a backup, and is
interrupted, it will not be able to unmount the fileystem in a bpend_notify
script.
--------------------------------------------------------------------------------
Etrack Incident = ET522347
Description:
A 134 status code (unable to process request because the server resources
are busy) was occasionally reported incorrectly as a 24 status code
(socket write failed). This issue could cause a job to fail instead of
being retried if resources were available.
--------------------------------------------------------------------------------
Etrack Incident = ET421374
Description:
Backups no longer fail with a status 12 because it could not open a
NetBackup-created file.
--------------------------------------------------------------------------------
Etrack Incident = ET521820
Description:
The NOM server no longer becomes unstable while retrieving catalog data.
--------------------------------------------------------------------------------
Etrack Incident = ET528831
Description:
The NOM media summary page no longer counts incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET529847
Description:
A change was made to eliminate a code vulnerability/error that would
cause a process core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET530131
Description:
Setting "RANDOM_PORTS = NO" in bp.conf prevents "nbpushdata -add" from
working.
Workaround:
To avoid this issue, do not use RANDOM_PORTS=NO.
--------------------------------------------------------------------------------
Etrack Incident = ET514845 ET530821 ET530802
Description:
In environments where DNS is not available for fully resolving a host's
name, NBAC would require additional configuration steps. Therefore, in
some cases, it is not possible to get NBAC to work.
Workaround:
In some cases it is possible to specify the correct fully-qualified host
name with the bpnbat and bpnbaz command lines. The user is prompted for
the correct value when a problem is found in this regard.
Additional Notes:
A new command line has been added for bpnbat. The bpnbat -ShowMachines
command displays the exact names of the Machine principals that were
added with bpnbat -AddMachine. This indicates whether or not a Short Host
name has been resolved. It also enables the user to see which machines
have thus far been added to the NBAC machine list.
--------------------------------------------------------------------------------
Etrack Incident = ET514845 ET530821
Description:
In environments where DNS is not available for fully resolving a host's
name, NBAC would require additional configuration steps. Therefore, in
some cases, it is not possible to get NBAC to work.
Workaround:
In some cases it is possible to specify the correct fully-qualified host
name with the bpnbat and bpnbaz command lines. The user is prompted for
the correct value when a problem is found in this regard.
Additional Notes:
A new command line has been added for bpnbat. The bpnbat -ShowMachines
command displays the exact names of the Machine principals that were added
with bpnbat -AddMachine. This indicates whether or not a Short Host name
has been resolved. It also enables the user to see which machines have
thus far been added to the NBAC machine list.
--------------------------------------------------------------------------------
Etrack Incident = ET497075
Description:
When submitting a user, archive, or manual backup job with NONE specified
for the progress log, a progress log in the root directory /NONE is
created. Changed bprd to not set progress log parameter passed to Policy
Execution Manager if NONE specified.
--------------------------------------------------------------------------------
Etrack Incident = ET524767
Description:
When bprestore is run with the option to wait for the completion of the
restore job, a firewall between bprestore and bprd can shut down the
socket. This causes bprestore to wait for the completion status which
never comes.
Workaround:
Increase the timeout on the firewall.
--------------------------------------------------------------------------------
Etrack Incident = ET516108
Description:
The VxFS named data-stream processing caused a debug log error when
performing Advanced Client for DB2 backups. The backup completes
successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET519732
Description:
Image header files do not have the correct permissions and are world
writeable in NetBackup 6.0.
Workaround:
Permission on the image files can be changed using operating system tools.
A cron or at job could be used to automate this functionality. Other
options could include automating this with a bpend script.
Additional Notes:
After installation of NetBackup 6.0 MP2, please change the permission of
the appropriate header file to 644.
--------------------------------------------------------------------------------
Etrack Incident = ET519795
Description:
When running a backup with a large number of streams, the image header
files may not be removed correctly from the tmp directory when the image
is validated. This will cause a bpverify request to read the image header
twice - once from the parent directory and once from the tmp directory.
It will see twice the number of expected files and fail to verify the
image.
Additional Notes:
This patch also addresses a similar issue with deleted image header files,
where the image header file is not successfully deleted initially, and is
retained until a subsequent clean-up operation is done.
--------------------------------------------------------------------------------
Etrack Incident = ET523646
Description:
Master server went offline in NOM even though
master servers were running fine.
--------------------------------------------------------------------------------
Etrack Incident = ET530110
Description:
You can now copy and paste file names between include/exclude lists and an
external application like Notepad, in the Host Properties Include/Exclude
page for a Windows client.
Additional Notes:
Following new I18N messages have been added:
- Copy
- Paste
- Change
--------------------------------------------------------------------------------
Etrack Incident = ET492363
Description:
Entire HostSession was being destroyed if error in any single manager.
--------------------------------------------------------------------------------
Etrack Incident = ET416423
Description:
If you create a DB2 policy using a backup script whose name contains
Chinese characters and then run the backup, the backup fails with a
status of 6.
Workaround:
To avoid this issue, modify the path name to not include four-byte,
Chinese characters or include more non Chinese characters.
--------------------------------------------------------------------------------
Etrack Incident = ET530318
Description:
The bpcoverage binary crashes in NetBackup 5.1 MP4 .
Workaround:
To avoid this issue, use the bpcoverage binary prior to NetBackup 5.1 mp4.
--------------------------------------------------------------------------------
Etrack Incident = ET517651 ET526726 ET526745
Description:
Added a software utility (nbsupport 2.1.1) that creates a support package
that consists of multiple reports most often asked for by NetBackup support
personnel.
--------------------------------------------------------------------------------
Etrack Incident = ET526967
Description:
A problem would occur when an Archive was run using NBWin. There was a
change in the behavior that caused data loss when only one file exists
within the directory at the start of an archive job and new files were
added to that directory before the archive completed. BPCD showed that
at the end of the job, the archive was called with 'rm -rf' that removed
the directory and all files resulting in a data loss of the new files
added.
--------------------------------------------------------------------------------
Etrack Incident = ET521720
Description:
one can see many nbproxy.exe hanging around even
after the destruction of its Manager or nbsl.exe itself
--------------------------------------------------------------------------------
Etrack Incident = ET517955
Description:
NBSL no longer sends invalid fields in the Job and Job-attempt data.
--------------------------------------------------------------------------------
Etrack Incident = ET521892
Description:
Running asyncronous I/O on large files can lead to delays in servicing
requests. The design should have handled this uncommon issue, however,
if an error, such as a read error, was encountered with an errno of
EAGAIN, it was treated as a generic error instead of a retry, so the
backup failed.
Workaround:
To avoid this issue, turn off asyncronous I/O.
--------------------------------------------------------------------------------
Etrack Incident = ET497175
Description:
Added new PC-x64 client type.
--------------------------------------------------------------------------------
Etrack Incident = ET517406
Description:
Multiple leak issues in TAO have been fixed in this maintenance pack.
--------------------------------------------------------------------------------
Etrack Incident = ET532659
Description:
The SG driver can cause a kernel panic due to a NULL pointer dereference.
--------------------------------------------------------------------------------
Etrack Incident = ET522386
Description:
An issue existed where in some cases, a job would not schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET497997 ET500067 ET506604 ET515440 ET523577 ET526811 ET533446
ET530687 ET395009 ET401372 ET413319 ET413325 ET413510 ET418654 ET492409 ET426777
ET536105
Description:
Added support for the following libraries:
- ADIC FastStor 2.1
- ADIC FastStor2
- BDT ThinStor
- Copan VTL
- Fujitsu LT270
- NETAPP VTL
- Overland Reo 4000 VTL
- Quantum DLT V4
- Quantum PX50
- Sony CSM-20
Added support for the following drives:
- Exabyte VXA-2
Updated the following libraries:
- Exabyte 480
- HP A5597A
- Quantum MSL6000
Updated the following drives:
- STK T10000
--------------------------------------------------------------------------------
Etrack Incident = ET425635
Description:
This maintenance pack contains error handling enhancements for license
failures in vlteject, vltinject, and vltopmenu.
--------------------------------------------------------------------------------
Etrack Incident = ET533242
Description:
Changes were made to the notify scripts to only call “date” once for
performance reasons. In addition, changes were made to add the missing
parent_start_notify and parent_end_notify scripts that the parent job
(nbgenjob) uses.
--------------------------------------------------------------------------------
Etrack Incident = ET527834
Description:
The NetBackup API that retrieves Catalog DB images was not returning
records in the ascending order of date (backuptime). This caused a
problem because NOM requires the backuptime to be in the ascending order
of date.
--------------------------------------------------------------------------------
Etrack Incident = ET533333
Description:
Hot Catalog Backups were taking too long. For a customer that has a very
large catalog (about 44GB) that contains about 117000 file list entries
(for image catalog directives), the backups were taking in excess of
24 hours.
Workaround:
To avoid this issue, run cold catalog backups, if the hot catalog backups
take too long.
--------------------------------------------------------------------------------
Etrack Incident = ET496741 ET537300 ET570640
Description:
Backups with infinite retention use a specific expiration date value to
mark them as infinite retention. This value was changed in the
NetBackup 6.0 release to deal with some limitations in third party
components. This new value created some reporting issues for backups
that were done on or reported using media servers with the NetBackup 5.0
or 5.1 versions. The backups would be listed as expiring on a specific
date, rather than showing "INFINITY" as their expiration date. This pack
addresses the third party date limitations and reverts the value used to
designate infinite retention to the pre-NetBackup 6.0 value.
--------------------------------------------------------------------------------
Etrack Incident = ET520323
Description:
Windows Hot Catalog Backups would periodically fail with a
status 67: client backup failed to read the file list. This only
occurred if there were client names with multiple underscore ("_")
characters in their NetBackup policy definitions.
Workaround:
To avoid this issue, rename the clients defined in NetBackup backup
policies to client names without underscore characters.
--------------------------------------------------------------------------------
Etrack Incident = ET414828
Description:
This pack contains a fix to a memory leak in Policy Execution Manager when
reading a policy or when sending mail upon job completion (for example,
when the mailAdmin field is specified).
Workaround:
A partial workaround for this issue is to not set the mailAdmin field in
the policy so that no mail will be sent upon job completion.
--------------------------------------------------------------------------------
Etrack Incident = ET519705 ET519368
Description:
After some amount of time, NetBackup EMM would become unresponsive;
requests to EMM would timeout. To corret this issue, the rollovermode is
set to the filesize (which is the default NetBackup configuration).
--------------------------------------------------------------------------------
Etrack Incident = ET533725
Description:
Corrected a problem that caused NBJM to crash intermittently. The problem
was caused by two threads working on the same object concurrently.
--------------------------------------------------------------------------------
Etrack Incident = ET422446
Description:
Corrected the drive unload function in acstest.
--------------------------------------------------------------------------------
Etrack Incident = ET533119
Description:
A change has been made to bpdbjobs to ignore PROCESS lines that appear in
trylogs before the Try line to insure that the correct data is interpreted.
--------------------------------------------------------------------------------
Etrack Incident = ET534333
Description:
Multiple changes have been added to handle a number of sscanf() calls in an
effort to gaurd against potential problems that are similar to buffer
overflow issues.
--------------------------------------------------------------------------------
Etrack Incident = ET532668
Description:
A TIR backup would create a corrupted tape image if the amount of TIR data
received did not match the amount expected.
--------------------------------------------------------------------------------
Etrack Incident = ET407677 ET432231 ET493475 ET493479
Description:
Vault components are now supported in an NBAC environment.
--------------------------------------------------------------------------------
Etrack Incident = ET533084
Description:
If an inline tape copy backup job was suspended before the first
checkpoint was taken and subsequently resumed, the job failed to start.
--------------------------------------------------------------------------------
Etrack Incident = ET530747
Description:
BPTM would sometimes corrupt the on-disk image when recovering from a
disk-full condition. To encounter this problem, a backup policy that uses
inline copy and multiplexing to a DSU/DSSU must be active.
--------------------------------------------------------------------------------
Etrack Incident = ET534512
Description:
Exchange VSS restores were failing because of a regression that was
introduced in an earlier release.
--------------------------------------------------------------------------------
Etrack Incident = ET535998
Description:
"bpdbm -consistency 2", useful to check database consistency, no longer
fails.
--------------------------------------------------------------------------------
Etrack Incident = ET496660
Description:
If a backup image was the same exact size as the defined max fragment size,
a zero-length fragment would be listed in the image header and cause bpdm
to hang while attempting to read the fragment.
--------------------------------------------------------------------------------
Etrack Incident = ET431225
Description:
When a disk full condition occurred while writing the fragment header, an
error would also occur during the same period that did not get cleared and
caused all eligible image candidates to be deleted beyond the disk storage
unit’s low water mark.
--------------------------------------------------------------------------------
Etrack Incident = ET538466
Description:
If a single job in a multiplexed group received a 41 status error
(network connection timed out), then all of the jobs in the group would
incorrectly error with this same status.
--------------------------------------------------------------------------------
Etrack Incident = ET539671
Description:
A change has been made to set the debuglogday to currentlogday every time
the debug log file is opened. For robust logging, this fix creates the
first log file for the current day. For legacy logging, this fix prevents
the current log file from getting reopened for every debug log entry.
Workaround:
To resolve this issue, touch the next file in the sequence, then the
robust logging starts to write to the newly created log file.
--------------------------------------------------------------------------------
Etrack Incident = ET534453
Description:
Shared standalone drives did not work if media servers were started while
a tape was loading.
--------------------------------------------------------------------------------
Etrack Incident = ET535036
Description:
A change has been made to resolved an nbproxy build break in addition to
a race condition error in nbsl.
--------------------------------------------------------------------------------
Etrack Incident = ET540019
Description:
NetBackup Catalog images are now retrieved in ascending order.
--------------------------------------------------------------------------------
Etrack Incident = ET539558
Description:
A change was made to greatly reduce the startup time for multi-stream
backup jobs with many streams.
--------------------------------------------------------------------------------
Etrack Incident = ET540913
Description:
An immediate backup would cause the removal and rebuilding of jobs in the
work list, even if the policy has not been changed, resulting in delays
with starting the jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET540910
Description:
The startup time of backup jobs would slow down when entries existed in
the client database.
--------------------------------------------------------------------------------
Etrack Incident = ET514169
Description:
The pack install provides customers with a new option to perform cleanup
of previously saved patch images. This will alleviate concerns because
of an increased footprint and full replacement of all NetBackup client
binaries in maintenance packs. The pack installer will present an
additional prompt on every install to enable or disable this feature.
--------------------------------------------------------------------------------
Etrack Incident = ET538179 ET534458 ET538172 ET538164 ET537437 ET537416 ET537513
ET537486 ET537664 ET537522 ET537530 ET537476 ET537539 ET537559 ET542506 ET536735
Description:
Multiple buffer overflow vulnerabilities have been identified in daemons
that run on Veritas NetBackup master, media, and client servers. An
attacker, if able to access a vulnerable Veritas NetBackup server and
successfully exploit these issues, could potentially execute arbitrary
code resulting in possible unauthorized and elevated privilege access
to the targeted system.
For more information about this vulnerability, refer to TechNote 281521 on
the Symantec Support Web site (http://support.veritas.com/docs/281521).
--------------------------------------------------------------------------------
Etrack Incident = ET540445
Description:
Directory paths longer than 1024 characters can cause a core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET539395
Description:
A lock was inadvertently removed in DeviceManagerImpl::getEventChannel ()
that caused a race condition when invoking the
CollectorBase::getEventChannel () call. This lock has been added back
in to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET542685
Description:
The catalog cleanup process was not resetting the image header level
expiration date on a multi-copy image when the first copy expired. This
caused the expiration date for the image to be incorrectly reported.
This problem affects only image reporting, because the determination to
retain data is based on the copy-level expiration date.
Workaround:
This pack will ensure that the catalog cleanup operation correctly sets
the image header level expiration date. Additionally, it will ensure that
queries against images that were affected by the original problem will
return the correct expiration date. Images affected by the original
problem may continue to show an incorrect expiration date and primary
copy when viewed through a text editor, but will be handled correctly by
the application.
--------------------------------------------------------------------------------
Etrack Incident = ET542894
Description:
A change has been made that enables you to do a Media Freeze and
Unfreeze in NOM user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET413496
Description:
Added an ACS toolkit port to the ACS toolkit 2.3.
Added ACS support to Linux IA64 and HP-UX IA64.
Additional Notes:
HP-UX IA64 does not currently support ACS_TCP_SERVICE mode which also
means there is no ACS firewall support for HP-UX IA64. Symantec is
working with Hewlitt Packard to acquire a new operating system library
for this support.
--------------------------------------------------------------------------------
Etrack Incident = ET541879
Description:
Added support for the new Quantum DLT-S drives.
--------------------------------------------------------------------------------
Etrack Incident = ET533487
Description:
A change has been made to correct known NBSL core dump issues.
--------------------------------------------------------------------------------
Etrack Incident = ET545651
Description:
A scan-host failover to the NDMP path caused the drive to be DOWNED.
--------------------------------------------------------------------------------
Etrack Incident = ET544406
Description:
Backups of Windows clients using standard encryption would corrupt the
backup image. This caused some restores from this image and bpverify to
fail.
--------------------------------------------------------------------------------
Etrack Incident = ET546171
Description:
Added a configurable option to disable validation of the host name
(chars used to form the name).
--------------------------------------------------------------------------------
Etrack Incident = ET541896
Description:
Changes were made to correct core dump issues when performing a
bpdbjobs –cancel function.
--------------------------------------------------------------------------------
Etrack Incident = ET541878
Description:
Changes were made to correct core dump issues when performing a
bpdbjobs -report -all_columns function.
--------------------------------------------------------------------------------
Etrack Incident = ET419277
Description:
Reduced the number of times bpdbm reads NetBackup configuration information.
--------------------------------------------------------------------------------
Etrack Incident = ET541505 ET566045
Description:
Enhanced the level of support for multi-NIC authentication brokers
under NBAC.
--------------------------------------------------------------------------------
Etrack Incident = ET546839
Description:
Back-level media servers remote scanning drives that are active on 6.0
media servers, may cause the drive to be downed on the scan host.
--------------------------------------------------------------------------------
Etrack Incident = ET542650
Description:
Added "-move" into the "bpdbm -consistency" check to explicitly move out
the corrupted catalog images. "bpdbm -consistency" no longer moves
corrupted images without the option being explicitly specified.
--------------------------------------------------------------------------------
Etrack Incident = ET565075
Description:
Changes have been made to resolve an NBSL core dump on an AIX 5.3 master
server.
--------------------------------------------------------------------------------
Etrack Incident = ET579151
Description:
Drive status info (i.e. EVSN, RVSN, Labelled, Ready) not showing up
in device monitor and vmoprcmd output.
================================================================================
=========
NB_60_1_M
==========
Etrack Incident = ET415495
Description:
Do not allow a down/disabled media server to block the entire Device
Allocator (DA) thread pool.
--------------------------------------------------------------------------------
Etrack Incident = ET423713
Description:
There were a few places in the code where the image query protocol version
was set to 0, which is a pre-NetBackup 5.0 image version ID. Some image
queries would fail if the size of the total data being backed up was larger
than 2TB in one job.
This issue has been corrected enabling image queries on backups greater
than 2TB work properly.
--------------------------------------------------------------------------------
Etrack Incident = ET424051
Description:
A change has been made to avert a potential vulnerability in a Java
authentication service that runs on Veritas NetBackup servers and clients.
This change prohibits remote attackers from executing arbitrary code on a
targeted system. In addition, Symantec recommends that users block the
affected ports from external network access.
--------------------------------------------------------------------------------
Etrack Incident = ET423045
Description:
When sharing tape drives between media servers that were running both
NetBackup 6.0 and NetBackup 5.x, a problem existed with the NetBackup 6.0
Scan Hosts. If the drive being scanned was assigned to a 5.x media server,
the 6.0 Scan Host might not stop scanning. This resulted in SCSI
reservation conflicts and DOWN'ed drives on the NetBackup 5.x assigned host.
Workaround:
To avoid this issue, do not share drives between media servers running
different versions of NetBackup. Instead, pool your drives such that all
of your NetBackup 5.x media servers are sharing one pool of drives and all
of your NetBackup 6.0 media servers are sharing a pool of different drives.
--------------------------------------------------------------------------------
Etrack Incident = ET422837
Description:
When running multi-streamed Windows Open File Backup backups to back up
open and/or active files, some VSP cache files in the format of
_vxfiVspCacheFile_1.VSP, for example, may have been left behind by the
backup jobs that had already completed. This did not occur with
non-streamed backup jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET428719
Description:
Because of a logic error in the handling of "bptm –delete_all_expired",
the expired media was not getting deleted. This would prevent recycling
of the media.
Workaround:
To avoid this issue, the user can expire the media using bpexpdate.
--------------------------------------------------------------------------------
Etrack Incident = ET424660
Description:
If a hot catalog backup fails and retries, an end of session function is
executed when jobs are still active. This could result in extra catalog
backups to run, extra start and session scripts to run in addition to
extra catalog cleanup operations.
--------------------------------------------------------------------------------
Etrack Incident = ET429008
Description:
When upgrading from NetBackup 5.x to NetBackup 6.0, the
NETBACKUP_RELATIONAL_DATABASE_FILES directive was not added to the list of
files included in cold catalog backup. The command, bpsyncinfo -add_paths,
"NETBACKUP_RELATIONAL_DATABASE_FILES" is run automatically during patch
installation to add this directive to the cold catalog backup configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET421370
**Description:
The NBDB database recovery (for Enterprise Media Manager (EMM) and Bare
Metal Restore (BMR)) will fail if the master server has a newer catalog
backup image than the one used in disaster recovery (DR). On Windows
platforms, it logged an error message in the progress log and displayed an
error message box. On UNIX platforms, because of a defect in the Java
user interface, it reported an error message in the log and all of the
restore jobs appeared in the job monitor as being successful.
Additional Notes:
This maintenance pack enables a user to recover from an older catalog
backup even though a newer catalog backup image exists on the master
server.
Full catalog disaster recovering from an older catalog backup is a
“roll-back” operation that has the risk of data loss. Users should fully
understand the implications and use it with caution.
--------------------------------------------------------------------------------
Etrack Incident = ET431863
Description:
For a Hot Catalog Backup, the relational database (NBDB/Sybase ASA) backup
job treated a cumulative and differential incremental backup the same and
only included the transaction log in the backup. This can create problems
recovering the ASA database if the differential backup media created before
the last cumulative has expired. These differential backups contained the
transaction logs that were necessary to roll forward from the last full
backup.
Workaround:
To resolves this issue, the cumulative incremental backup is actually a
full backup for the ASA files.
--------------------------------------------------------------------------------
Etrack Incident = ET406999
Description:
Transport of log messages from NBSL to NOM Server was failing and causing
the Host Session to go down. PSP's TAO_Transport was not checking for
EAGAIN.
--------------------------------------------------------------------------------
Etrack Incident = ET428760
Description:
The vmd process would dump core if the EMM service (nbemm) was not running.
--------------------------------------------------------------------------------
Etrack Incident = ET425765
Description:
The nbpushdata function failed when a pool name had a hyphen in the actual
pool name.
--------------------------------------------------------------------------------
Etrack Incident = ET492438
Description:
Data tapes are no longer treated as cleaning tapes and be FROZEN by
NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET494547
Description:
Device monitor showed the same tape mounted in multiple drives. This tape
in this scenario was also assigned to a NetBackup 5.x media server.
Workaround:
To avoid this issue, do not share drives between NetBackup 6.0 media
servers and NetBackup 5.x media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET492704
Description:
A Null Reference Exception is produced when creating a custom filter for
the Driver Detail table (Monitoring -> Drivers -> Details table).
--------------------------------------------------------------------------------
Etrack Incident = ET425186
Description:
Oracle backups no longer end prematurely with a status 25.
--------------------------------------------------------------------------------
Etrack Incident = ET495004
Description:
The nbpushdata function failed with the following messages in the
nbpushdata log file:
<4> get_host_info: CEMM_MACHINE_DISK_ACTIVE being set for <your_host>
<16> emmlib_UpdateHost: (0) UpdateMachine failed, emmError = 2007079,
nbError = 0
<16> get_host_info: (-) Translating
EMM_ERROR_SQLSyntaxErrorOrAccessViolation(2007079) to 193 in
the media context
--------------------------------------------------------------------------------
Etrack Incident = ET418546
Description:
The NOM database server uses less CPU utilization over GA.
--------------------------------------------------------------------------------
Etrack Incident = ET495339
Description:
The Windows Open File Backup was not showing retries in the Activity
Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET495403 ET497074
Description:
For media with image expiration set to infinity, nbpushdata passed an
incorrect value for infinity to the EMM database. This resulted in the
media not being queried.
nbemmcmd -listmedia -mediaid <media_id> NBEMMCMD, Version:6.0(20050906)
The function returned the following failure status:
generic EMM SQL error (193)
Command did not complete successfully.
vmquery -m <media_id>
Could not query by media ID A00001 with debug: generic EMM SQL error (193)
--------------------------------------------------------------------------------
Etrack Incident = ET425768
Description:
An issue in nbpushdata caused the nbpushdata –remove function to fail.
Workaround:
To avoid this issue, drop the EMM data base and then recreate it.
--------------------------------------------------------------------------------
Etrack Incident = ET496010
Description:
Restores failed with the following errors in the job log and tar debug log:
job log:
22:16:27 (4753.046) data buffers out of sequence, expected number 157884,
received 157886
23:32:46 (4753.053) data buffers out of sequence, expected number 404927,
received 404932
debug log:
22:16:27 (4753.046) data buffers out of sequence, expected number 157884,
received 157886
23:32:47 (4753.053) data buffers out of sequence, expected number 404927,
received 404932
This issue occurred because the HP 11.23 compiler optimized out references
to the shared memory control variables.
--------------------------------------------------------------------------------
Etrack Incident = ET425178
Description:
Data Lifecycle Manager consolidation jobs now complete successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET430806 ET419127
Description:
Changed bprd and the Policy Execution Manager (PEM) so that the bprd child
could terminate and not wait for the job exit status from PEM, unless
the -w flag was used on the request.
--------------------------------------------------------------------------------
Etrack Incident = ET493607
Description:
Could not inventory legacy TS8 libraries as TL8.
--------------------------------------------------------------------------------
Etrack Incident = ET497080
Description:
If any inetd entry is missing on a client and update_clients is used to
push NetBackup client software to it, update_clients will show an error
message in the log file. A change was made that corrected the temporary
file names so that inet.conf on the client will be updated properly and no
error will be generated.
--------------------------------------------------------------------------------
Etrack Incident = ET497761
Description:
An extremely heavy load in the Device Allocator (DA) may cause EMM to crash.
--------------------------------------------------------------------------------
Etrack Incident = ET496437
Description:
Some vital logs were not displaying correctly. To be more specific, the
form that Log:DbLogMsg is being called in the emmserver source files was
incorrect whenever it was multi-lined in the code. As a result, only part
of the log message survived and important log information was lost.
--------------------------------------------------------------------------------
Etrack Incident = ET496608
Description:
Non-robotic tape drives that contain unlabelled media will no longer be
automatically assigned to non-robotic media specific mount requests.
--------------------------------------------------------------------------------
Etrack Incident = ET498523
**Description:
In a rare condition one or more backups would be corrupt when using Inline
Tape Copy (ITC) with multiplexed backups. This would potentially happen
under the following conditions:
- ITC was enabled with two or more active copies.
- Multiplexing was enabled with two or more active backups.
- The schedule configuration had the "continue if the copy fails" flag set
for the copy that failed in the next step.
- A copy other than the first active copy encountered an "end of media", so
a new media was needed for this copy. In addition, there was a problem
of getting or setting up media (for example, writing the media header)
such that this copy failed before continuing the backup.
- The last buffer written to the first active copy prior to the "end of
media" on the other copy was not the first active backup.
Workaround:
To avoid this problem, do one of the following:
- Edit the schedule configuration to disable the "continue if copy fails"
flag.
- Disable multiplexing.
- Disable ITC.
--------------------------------------------------------------------------------
Etrack Incident = ET423206
Description:
The back-level media server V_QUERY_CLEAN_BYROBNUM request caused an SQL
error.
--------------------------------------------------------------------------------
Etrack Incident = ET424796
Description:
NetBackup Job Manager (NBJM) deadlocks or halts when the connection to
bpbrm breaks in the middle of a backup job.
--------------------------------------------------------------------------------
Etrack Incident = ET431510
Description:
On initial install the Policy Execution Manager failed to start the first
time because no IOR file existed for nbproxy. Once an IOR file existed
and it is not empty, then the NetBackup Service Monitor was able to restart
the Policy Execution Manager.
Workaround:
To avoid this issue, delete the IOR files listed below before starting the
Policy Execution Manager.
On UNIX:
/usr/openv/var/nbproxy_pem.ior
/usr/openv/var/nbproxy_pem_email.ior
On Windows:
Veritas\NetBackup\var\nbproxy_pem.ior
Veritas\NetBackup\var\nbproxy_pem_email.ior
--------------------------------------------------------------------------------
Etrack Incident = ET425564
Description:
The Policy Execution Manager would crash after submitting a user-directed
or manual backup.
--------------------------------------------------------------------------------
Etrack Incident = ET499610
**Description:
Synthetic backup had potential data loss issues in following cases:
- The last full/synthetic or full expired/deleted occurred,
followed by one or more incrementals and a synthetic backup.
- The last incremental/full backup catalog was compressed before
next incremental backup took place.
- The TIR records in the last incremental backup are missing for
various reasons.
--------------------------------------------------------------------------------
Etrack Incident = ET505873
Description:
Media servers sharing drives on versions of NetBackup older than
NetBackup 6.0 will receive host_not_registered errors when attempting to
determine if another media server is unavailable.
--------------------------------------------------------------------------------
Etrack Incident = ET506551 ET499474 ET506690
Description:
This entry resolves three seperate issues described in the following list:
- Under certain conditions backups would not schedule. This happened
because of a problem in computing the next time a job was due. Windows
were not processed correctly if a backup should have run in a previous
window if the next window opened or closed at a different time.
- Advanced client VSS snapshot backup no longer causes an 805 error to
occur.
- The scheduler always executes Full backups, even for incrementals, if the
BMR option is on. nbpem would use the wrong criteria for the last
backup query made for a parent job that did not have multiple data
streams enabled. The result was no last full backup being found, so a
full would be run instead of an incremental.
--------------------------------------------------------------------------------
Etrack Incident = ET496102
Description:
As the number of VxUL log files grew, the start-up performance of bprd
would degrade.
Workaround:
To avoid this issue, delete the log files on a regular basis.
--------------------------------------------------------------------------------
Etrack Incident = ET506045
Description:
nbpushdata was using emmlib_DeleteHost to remove the NDMP host when the
following error occurred in the nbemm log. The following is a portion of
the log associated with the delete. Although log-level 6 was used, it
appeared that some log messages were missing.
11/11/05 15:54:41.185 [Debug] NB 51216 nbemm 111 PID:13393 TID:1196157872
[No context] 1 [DbConnection::Execute] SQL - retval=2007085(2007085)
retdal=-1native=<-143> sqlerror=<[Sybase][ODBC Driver][Adaptive Server
Anywhere]Column 'FQMachineName' not found> sqlstate=<42S22>
--------------------------------------------------------------------------------
Etrack Incident = ET507645
Description:
In certain cases, when NetBackup Access Control is enabled, long-lived
processes such as nbemm, nbpem, nbjm, nbrb, nbproxy, nbsl and vmd would
leak memory.
--------------------------------------------------------------------------------
Etrack Incident = ET500006
Description:
The Policy Execution Manager VxUL message catalog was missing some messages
causing it to crash when trying to log the new messages.
--------------------------------------------------------------------------------
Etrack Incident = ET500061
Description:
SQL SERVER backup completes normally but the client interface Displayed
a -1 status. This was caused by improper progress log updates.
--------------------------------------------------------------------------------
Etrack Incident = ET509509
Description:
When spanning media, jobs occasionally appeared to be hung and the request
was continually failing with the message, "ROBOTIC LIBRARY IS DOWN ON
SERVER". This would happen after an earlier failure causing the message,
"MEDIA SERVER IS CURRENTLY NOT CONNECTED TO MASTER SERVER". However, the
media server properly showed the robot as up and the host as ACTIVE or
ACTIVE-TAPE.
--------------------------------------------------------------------------------
Etrack Incident = ET509293
Description:
The NetBackup Service Layer (NBSL) occasionally sent negative values for
freespace and totalcapacity of a storage unit (if the values are greater
than 2^32-1).
--------------------------------------------------------------------------------
Etrack Incident = ET508191
Description:
vmd now retries the connection to EMM forever, instead of shutting down
if it cannot connect to EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET511728
Description:
From the NOM user interface, it is not possible to start the service/deamon
when NetBackup is on a UNIX Operating System.
--------------------------------------------------------------------------------
Etrack Incident = ET512560
Description:
It is now be possible for SAN media servers to be used as write hosts for
duplicate jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET510335
Description:
VxUL queries were failing on AIX platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET510255
Description:
Appending parentheses in the NOM filtering criteria is no longer an issue.
--------------------------------------------------------------------------------
Etrack Incident = ET510415
Description:
New DRIVE and ROBOT Reports have now been created along with multiple
entries for some column names.
--------------------------------------------------------------------------------
Etrack Incident = ET512866
Description:
Removed change events for Error LogMonitoring. For example, error log
collection functionality is removed. In addition, the getLogMessages()
idle method supports the error log source too; thus, NOM will call this
method for getting error logs. Finally, the getEventChannel()
functionality has been removed, resulting in an AFException.
Additional Notes:
Because of this fix, log monitoring of NOM 6.0 MP1 will only work with
NetBackup 6.0 MP1.
--------------------------------------------------------------------------------
Etrack Incident = ET513093
Description:
vmscd no longer dumps core. This occurred because vmscd received an invalid
drive type for one of the drives while polling the drive status and vmscd
was not handling the invalid drive type properly.
--------------------------------------------------------------------------------
Etrack Incident = ET513390
Description:
The NetBackup Notification Service (NBNos) was running in single-threaded
mode.
--------------------------------------------------------------------------------
Etrack Incident = ET514603
Description:
Change made to bpexpdate such that media IDs that are less than six
characters returned from EMM were not padded with spaces. This caused
bpexpdate -deassignempty to mistakenly deassign media that still had
valid images on them.
Workaround:
To avoid this issue, turn off the automatic start of
bpexpdate -deassignempty by performing one of the following items:
- On a UNIX master servers, create the file,
/usr/openv/netbackup/bin/bpsched.d/CHECK_EXPIRED_MEDIA_INTERVAL,
and enter a 0 (zero) on the first and only line of the file.
- On a Windows master server, create the file,
<install_path>\NetBackup\bin\bpsched.d\CHECK_EXPIRED_MEDIA_INTERVAL,
and enter a 0 (zero) on the first and only line of the file.
--------------------------------------------------------------------------------
Etrack Incident = ET514622
Description:
An NBSL core dump happened while stopping it when it was connected to a
client (NOM). The core dump would occur on Solaris and AIX platforms.
On Windows platforms, it would hang in a 'stopping' state in the Windows
Service Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET515553 ET515559
Description:
vmscd, before the fix, was a single process and it used to service
requests from the EMM server synchronously. Because of this, the EMM server
was not receiving the request response in a timely manner. In some cases,
the EMM server would think that vmscd had exited and which then triggered
certain operations that were redundant, and in some, cases harmful.
--------------------------------------------------------------------------------
Etrack Incident = ET511340
Description:
Several issues have been fixed that related to back-level SSO
interoperability:
- Numerous re-registrations were consuming all of vmd's bandwidth on
the EMM server.
- Registration failures due to no scan host setting registration retry
timer which would block back-level servers from releasing drives.
- Back-level remote scanning of NetBackup 6.0 media servers was failing
with ENOTSCANHOST and forcing still more re-registrations.
Workaround:
To avoid these issues, do not share drives between NetBackup 6.0 and
NetBackup 5.X media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET516440
Description:
nbemm no longer core dumps on a clustered master server.
--------------------------------------------------------------------------------
Etrack Incident = ET516103
Description:
Vault can fail while logging very long strings.
Workaround:
Disable Vault logging.
--------------------------------------------------------------------------------
Etrack Incident = ET515838
Description:
When the parent job (nbgenjob) performed stream discovery and it received
an exception asking for policy information through nbproxy, it would then
perform several retries. On the first retry attempt the parent job would
core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET429245
Description:
On HP-UX platforms, scheduled backups with file lists that contain
multi-byte characters failed with an error 71 (None of the files in the
files list exist). On the Activity Monitor, the multi-byte characters
were unreadable in the file lists within job properties.
Workaround:
To prevent this issue, please apply the following patches:
- HP-UX 11.23
Patch Name: PHCO_30072
Patch Description: s700_800 11.11 iconv cumulative patch
- HP-UX 11.11
Patch Name: PHCO_29903
Patch Description: s700_800 11.11 iconv cumulative patch
- HP-UX 11.00
Patch Name: PHCO_29924
Patch Description: s700_800 11.00 iconv cumulative patch
================================================================================
Requirement: NB_CLT_60_5_M
Corequirement: NB_BMR_60_5_M
Directives: NBDB_Upgrade NBDB_Recover
================================================================================
This Maintenance Pack provides fixes for Veritas NetBackup (tm) UNIX servers.
NetBackup UNIX Add-on products, Database Agents, and the Java Interface have
separate Maintenance Packs.
The UNIX CLT pack, which is required to be installed with this server pack,
contains a full replacement of all client binaries for all platforms. The local
CLT binaries for this server may require as much as 50MB of free space in the
/usr partition to install, depending on platform. If client binaries are being
loaded on a server to be pushed to clients, as much as 400MB of free space may
be required in the /usr partition.
On AIX, installing this UNIX server pack requires more than 1.2GB of free space
in the /usr partition. For more information, please refer to the following
TechNote:
http://entsupport.symantec.com/docs/280824
================================================================================
=================
PACK DEPENDENCIES
=================
-- NB_CLT_60_5_M_<6 digit number>.tar must be installed before this
Maintenance Pack is installed.
-- Only if Bare Metal Restore is installed,
NB_BMR_60_5_<6 digit number>.<platform>.tar must be installed after
this Maintenance Pack is installed.
-- Installation of this Maintenance Pack requires version 1.33.10.14
of Vrts_pack.install script.
-- This Maintenance Pack contains runtime updates to Veritas Private
Branch Exchange (PBX). If you did not install PBX from a NetBackup
6.0 media kit (GA or 6.0MP4), you may have an older version of PBX
from another Veritas Product. This Maintenance Pack requires that
you have a minimum PBX level of 1.2.2.41. If you have an older version,
you must install 1.2.2.41 from a NetBackup 6.0 media kit. You can
determine your PBX version from the /opt/VRTSpbx/build_version
file. Newer versions are compatible with this Maintenance Pack.
-- Deliverables for the agents or options such as DB2, Oracle, Veritas
Storage Migrator (tm) (VSM) do not always change between patches and
could result in a patch not being delivered. When upgrading or patching
client software, any agent software must be upgraded or patched to the
latest or matching level at the same time as the client software.
-- Added support for multiple ACSLS servers to Windows. This requires
all Windows ACS customers upgrade to SUN/STK Libattach version 1.4.1.
I. PRIMARY MAINTENANCE PACK UPDATES
II. DOWNLOAD INSTRUCTIONS
III. KNOWN ISSUES
IV. INSTALLATION INSTRUCTIONS
V. UNINSTALL INSTRUCTIONS
VI. DESCRIPTION OF PROBLEMS FIXED
Current Pack
NB_60_5_M
Pack History
NB_60_4_M
NB_60_3_M
NB_60_2_M
NB_60_1_M
--------------------------------------------------------------------------------
The following information describes the upgrade and downgrade rules or scenarios
that apply to this maintenance pack.
- Upgrade scenarios:
The NetBackup 6.0 MP5 maintenance pack install:
- Can be applied on top of NetBackup 6.0 GA or any 6.0 MPx (prior to MP5).
- Cannot be applied directly to a NetBackup 5.x system. You must install
NetBackup 6.0 GA first.
- Cannot be applied directly to a NetBackup 6.0 MP5 Beta system. (The
Beta version of NetBackup must be uninstalled first.)
- Downgrade scenarios:
If the NetBackup 6.0 MP5 maintenance pack is uninstalled, you will roll
back to the version you had previously installed prior to installing
this maintenance pack, (such as 6.0 GA or 6.0 MPx).
====================================
I. PRIMARY MAINTENANCE PACK UPDATES
====================================
This section identifies the primary changes, maintenance updates, and
enhancements that are contained in this maintenance pack.
- This maintenance pack contains the following software upgrades:
- JRE 1.4.0.2v, which adds many security fixes for JAVA
- Sun Libattach version 1.4.2 for ACS robotics
- Veritas Unified Logging (VxUL) to 1.3.7.2
- All SIG components have been added and/or upgraded in this release:
- VxUL
- VxPBX
- VxPSP
- VxAT and VxAZ
- VxSched
- The following database proliferations and enhancements have been added
to this pack:
- Added NetBackup for DB2 support (DB2 v9) on 64-bit x86 Windows
operating systems.
- Added Oracle support for Windows 2003 x64. (Oracle 10gR2 for Windows x64)
- Providing x64 (AMD64/EM64T) support for SAP on the x64 Windows client.
- Added support for the HP-UX IA-64 platform to the Sybase package
(HP-UX 11.23 IA-64 - Sybase 12.5).
- With this maintenance pack, you can now compress Oracle and MSSQL
dataBases for backup.
- Provide the ability to restart a single failed MSSQL DB backup without
having to restart a full backup.
- Added new device and library support for the following:
- ACSLS - Titanium T1A, T9840C/D, DLT-S4
- New device supported for WORM
- New media and drive type for LTO4
- New library support - Panasonic/Matsushita AJ-CM100 Library
- There are many customers today who have multiple data centers and move
backup data between the centers by shipping backup images and copying or
replicating the image database. This feature removes one of their most
problematic steps for retreiving the data, changing copy number. They use
this data for both Data Recovery (DR) and production.
As more of users employ DR plans and now practice DR drills, the number
of users requiring the ability to restore from a non-primary copy at
their DR site is rapidly increasing.
DESCRIPTION:
Add a new option to bprestore:
bprestore -copy X
The copy number will need to be passed to bprd, so a new protocol will
need to be defined.
- The following enhancements have been made to Flashbackup:
- Support of up to 16 Terabytes.
- Support for Instant Recovery
- NetApp has a ShadowTape capability in their NearStore VTL. When virtual
media is ejected, NetApp makes a copy to a physical tape drive. However,
instead of deleting the image from their VTL, the copy is "hidden" from
NetBackup. A script has been added that will notify the appliance that
there is a request to restore from the ejected (hidden)media and will
mount the media on the VTL instead of the physical media.
- Support has been added to allow fail over to NearStore storage units to
a different NetApp filer that had been mirrored using NetApp's Volume Snap
Mirror technology.
- The new Single Instance Store (SIS) feature in Windows 2003 R2 Storage
Server extends SIS functionality to non-Remote Installation Service (RIS)
systems and multiple volumes. Changes contained in the pack ensures that
NetBackup protects RIS systems as well as the "first" SIS volume encountered
during backup.
- Changes have been added that allow Instant Recovery of Windows FlashBackup
using "Retain snapshots for Instant Recovery" on a policy.
- If a backup has terminated and if you do not want to repeat a complete
backup again, you can use the new command, BRBACKUP option -f / -fill. The
BRBACKUP command automatically determines the files that are still to be
backed up. If BRBACKUP is run with the -f/-fill option and the log name of
the failed job, it automatically checks which files were backed up
successfully and which failed and then starts a new job only for files for
which last backup failed.
- A new touch file has been added that enables you keep a TIR information
files longer than 10 days (<install path>/netbackup/TIR_INFO_KEEP_DAYS)
- An enhanced MFC VxLogView application enables you to create views of both
legacy and VxUL logs for Windows x86 systems. This application is located
in the goodies directory as, -lv.exe.
- In the PureDisk web user interface, a policy can now be created or a run
once job can now be executed to export the backup data in chosen data
selections to NetBackup storage. Once the data is exported into NetBackup
it will be treated like a "normal" NetBackup image and will be restored
like a regular file.
NOTE: Symantec recommends that you refer to the NetBackup 6.0 Operating System
Compatibility Matrix for the latest information regarding supported
features:
http://entsupport.symantec.com/menu_ddProduct_NBUESVR_view_CL.htm
=========================
II. DOWNLOAD INSTRUCTIONS
=========================
1) Download the NB_CLT_60_5_M_<6 digit number>.tar and
NB_60_5_M_<6 digit number>.<server>.tar files into the
/tmp directory,
where <6 digit number> is an internal tracking identifier
where <server> is alpha_5, hp_ux, hpia64,linux, linux64, rs6000, solaris
NOTE: NB_CLT_60_5_M_<6 digit number>.tar has the client binaries and
NB_60_5_M_<6 digit number>.<server>.tar has the server binaries and BOTH
must be installed.
NOTE: Only if Bare Metal Restore is installed, download and extract the
NB_BMR_60_5_M_<6 digit number>.<platform>.tar into the /tmp directory
and download and extract the NB_BBS_60_5_M_<6 digit number>.<platform>.tar
into the /tmp directory.
2) Extract the NB_CLT_60_5_M_<6 digit number>.tar and the
NB_60_5_M_<6 digit number>.<server>.tar files.
tar xvf NB_CLT_60_5_M_<6 digit number>.tar
tar xvf NB_60_5_M_<6 digit number>.<server>.tar
NB_60_5_M will create the files:
VrtsNB_60_5_M.README
VrtsNB_60_5_M.<server>.tar.Z
VrtsNB_60_5_M.preinstall
VrtsNB_60_5_M.preuninstall
VrtsNB_60_5_M.postinstall
VrtsNB_60_5_M.postuninstall
Vrts_pack.install
NB_CLT_60_5_M will create the files:
VrtsNB_CLT_60_5_M.README
VrtsNB_CLT_60_5_M.tar.Z
VrtsNB_CLT_60_5_M.preinstall
VrtsNB_CLT_60_5_M.postinstall
VrtsNB_CLT_60_5_M.postuninstall
Vrts_pack.install
==================
III. KNOWN ISSUES
==================
- The Veritas Private Branch Exchange (PBX) software is installed along with
Veritas NetBackup (tm) 6.x. By default, PBX logs messages to the system log
/var/adm/messages or /var/adm/syslog. This can cause additional system
logging that the system administrator may not desire. The messages written
to the system logs contain the same informational and warning messages that
are written to the PBX logs. For more information about this issue or
informaiton on how to disable the option, refer to the following TechNote on
the Symantec Support Web site.
http://support.veritas.com/docs/280746
- Changes were made to the Vault Operator Permissions. The Vault Operator
permissions are as follows:
- Host Properties permissions:
Browse and Read
- Job permissions:
Browse, Read, Suspend, Resume, Cancel, Delete, Restart, and New
- VolumeGroup permissions:
Browse, Read, New, and Delete
- VolumePool permissions:
Browse and Read
- DevHost permissions:
Browse and Read
- Media permissions:
Browse, Read, New, Delete, Eject, Move, UpdateBars, Assign, Deassign,
UpdateDatabase, and Expire
- Report permissions:
Browse and Read
- Robot permissions:
Browse, Read, Inventory, New, and Delete
- On all platforms, if the server pack install fails for any reason after the
Client pack has completed, be sure not to restart daemons before
retrying the pack installation.
- Reminder: Synthetics is not supported on Tru64 platforms.
- The NetBackup 6.0 Commands document contains some incorrect information for
the bplist command. The following accurately explains this command.
The bplist command shows a list of previously archived or backed up files
according to the options that you specify. You can choose the file or
directory and the time period that you want the listing to cover.
Directories can be recursively displayed to a specified depth.
The bplist command shows only the files that you have read access to. It
lists the files only if a user backup is performed by the user owning the
files (that is, an administrator account). A non-administrator or backup
operator cannot bplist the files. You also must own or have read access to
all directories in the file paths. You can list files that were backed up
or archived by another client only if you are validated to do so by the
NetBackup administrator.
If you create the following directory /usr/openv/netbackup/logs/bplist/
with public-write access, bplist creates an debug log file in this
directory that you can use for troubleshooting. The output of bplist goes
to standard output.
Issues that are associated with an ETrack number:
-------------------------------------------------
ET1018914 Discrepancy in Windows and UNIX Activity Monitor for an NetBackup
Access Control (NBAC) Vault Operator (vltop) user group.
Changes have been to the NBAC Vault_operator user group to ensure
proper functionality of the Activity Monitor for the Windows and
UNIX platforms.
=============================
IV. INSTALLATION INSTRUCTIONS
=============================
** The content of this online Readme supersedes the information in the Readme
contained in the download. **
NOTE: Click on the "Download Now" link, near the bottom of this document
prior to running the following installation procedure for this pack.
Before installing this maintenance pack, please review the following items:
- Symantec recommends that you perform catalog backups before and after you
apply this maintenance pack.
- If you are planning to install this Maintenance Pack as a part of an
upgrade from a 5.x release then it is important that you understand that the
existing NetBackup databases must be in a consistent state prior to beginning
the upgrade. Information and tools to assist you in determining the current
state of your database, as well as instructions to help you address any
inconsistencies that you might discover can be viewed on the NetBackup Upgrade
Portal, a part of the Symantec NetBackup Support Web site.
http://www.symantec.com/enterprise/support/overview.jsp?pid=15143
- If you are upgrading from 5.x to 6.0, you must install this Maintenance Pack
before you run nbpushdata. Failure to install this Maintenance Pack first
will result in a failed upgrade.
- On AIX, do not use a NetBackup GUI running on any other host to monitor the
NetBackup jobs/processes/daemons/devices on the host being patched during the
installation. On AIX this may cause text busy errors to occur during the
installation. The safest approach is to not have any GUIs running on remote
systems which are accessing an AIX host during pack application.
For Maintenance Pack installation on a UNIX Cluster Environment:
--------------------------------------------------------------------------------
1) Before you install this Maintenance Pack, make sure that NetBackup is at
release level 6.0 and configured to run in a cluster.
2) Freeze the NetBackup group. (By freezing the group, you will prevent a
'failover' from occurring during a patch installation).
3) Install this Maintenance Pack on the inactive node(s) of the cluster
(perform steps 1 through 3 below).
IMPORTANT: If you are using HP Service Guard and upgrading from a
pre-NetBackup 6.0 MP4 version, you must complete the installation of
this pack to the inactive node(s), and then copy the following file from
an inactive node to the active node before beginning the pack install on
the active node:
/usr/openv/netbackup/bin/cluster/util/monitor
4) Install this Maintenance Pack on the active node of the cluster (perform
steps listed below).
5) If the cluster is in a faulted state, clear the fault.
6) Unfreeze the NetBackup group.
--------------------------------------------------------------------------------
As root on the NetBackup Master Server:
1) Close the NetBackup user interfaces.
- Make sure the NetBackup server has no active jobs running (for example,
backups, restores, or duplications).
- If a database agent is being used, such as Oracle, ensure that the database
services are stopped.
2) Install NB_60_5_M and NB_CLT_60_5_M Maintenance Pack binaries.
cd /tmp
/bin/sh Vrts_pack.install
NOTE: Selecting the server Maintenance Pack will automatically install the
client maintenance pack if the client (CLT) .Z file and the README exist in
the installation directory. The server install will fail if the (CLT)
.Z file and the README are not present and the CLT pack has not been
previously installed. The client maintenance pack will NOT be installed
automatically during a reinstall of the server maintenance pack.
3) The Vrts_pack.install script will prompt you to restart daemons.
Otherwise, after the pack installation has completed, run:
/usr/openv/netbackup/bin/goodies/netbackup start
4) The pack install logs can be found in /usr/openv/pack/pack.history once the
installation is complete.
NOTE: Again, Symantec recommends that you perform catalog backups after you
have applied this maintenance pack.
=========================
V. UNINSTALL INSTRUCTIONS
=========================
Note: This will ONLY uninstall the Maintenance Pack from your local machine.
1) Close the NetBackup user interfaces.
- Make sure the NetBackup server has no active jobs running (for example,
backups, restores, or duplications).
- If a database agent is being used, such as Oracle, ensure that the database
services are stopped.
2) Change the directory to the patch save directory.
Substitute the pack name for ${PACK} in the following command:
cd /usr/openv/pack/${PACK}/save
3) Run the un-install script:
./Vrts_pack.uninstall
4) Verify that the pack uninstalled successfully by checking:
/usr/openv/pack/pack.history.
5) If necessary, restart the NetBackup and Media Manager daemons:
/usr/openv/netbackup/bin/goodies/netbackup start
=================================
VI. DESCRIPTION OF PROBLEMS FIXED
=================================
The following are descriptions of the problems fixed.
Please read the entire document before installing.
README Conventions:
Description
Describes a particular problem contained in this 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, Symantec strongly recommends
the "best practice" of being at the latest available patch level.
Additional Notes
Any additional information regarding a problem is included.
=============
Current pack
=============
================================================================================
Etrack Incident = ET644656
Description:
Backups to FSE-enabled Nearstore storage units require TIR to be enabled on
the policy. A change was made to enforce this requirement at run time.
--------------------------------------------------------------------------------
Etrack Incident = ET809090
Description:
If you were using vxlogview along with options –d and –t, vxlogview should
have accepted these options in any order, but it did not. The –d option
displays debug messages, and the –t option displays the most recent
messages. These are not related options, however, vxlogview did not honor
the –t option if it was listed after the –d option. A change was made to
correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET828552
Description:
Changes were made to this maintenance pack to update the PBX and ICSCO pbx
merge modules.
--------------------------------------------------------------------------------
Etrack Incident = ET605200
Description:
UNIX domain socket files with path names of the form /tmp/vnet*
were periodically created on UNIX/Linux NetBackup systems. Most
of these files were only needed for a few minutes and were quickly
deleted. If NetBackup processes terminate abnormally before the
/tmp/vnet* file can be deleted, then these files could accumulate
on the user's system.
This patch periodically deletes old (more than one hour) /tmp/vnet* UNIX
domain socket files.
Previously the Java server (bpjava) would also use UNIX domain socket file
paths of the form /tmp/vnet*. Since these files often need to exist for
several hours, the automated cleanup could cause problems. In this patch,
the form of the bpjava UNIX domain socket file path names has changed to
/tmp/jbp*.
--------------------------------------------------------------------------------
Etrack Incident = ET861571
Description:
Under certain circumstances, bpcd and vnetd services would be
put into maintenance mode on solaris10 systems. Changes were
made to disable/enable these services to make sure they respond.
--------------------------------------------------------------------------------
Etrack Incident = ET861550
Description:
If the NBDB database is not created properly during installation, the
install continues, however the user may not understand that there was
an issue creating the database. As a result, the user may encounter
errors in the command line and the user interfaces.
In addition, if during a patch installation that nbnd_upgrade fails,
the database winds up with the incorrect version. Again, nbemm will
not start because of the version mismatch.
Changes have been made so that the install will fail if the database
cannot be created or upgraded and installation warnings will be logged
in a new logging directory for nbnd commands. The new directories are:
UNIX: /usr/openv/netbackup/logs/nbdb
Windows: InstallPath\NetBackup\logs\nbdb
--------------------------------------------------------------------------------
Etrack Incident = ET862411
Description:
Made a change to unload tapes in a more timely manner on back-level media
Servers (for example, NetBackup 5.x).
--------------------------------------------------------------------------------
Etrack Incident = ET862341
Description:
Added support for 64-bit Linux on Power client.
--------------------------------------------------------------------------------
Etrack Incident = ET862518
Description:
Changes were made to fix potential memory leaks, while fetching pending
requests from the NetBackup Resource Broker.
--------------------------------------------------------------------------------
Etrack Incident = ET862534
Description:
Calls to emmlib_GetStorageUnitHosts no longer result in segmentation
violations.
--------------------------------------------------------------------------------
Etrack Incident = ET862464
Associated Primary Etrack = ET791864
Description:
Changes were added that prevent bpsynth from hanging on patched, Solaris 10
systems.
--------------------------------------------------------------------------------
Etrack Incident = ET862606
Description:
Changes have been made to ensure that all Chinese messages that are suppose
to appear in the Bare Metal Restore (BMR) command line interface (CLI)
output appear, no matter what locale is used.
--------------------------------------------------------------------------------
Etrack Incident = ET863136
Associated Primary Etrack = ET863127
Description:
On a busy UNIX NetBackup server, you may encounter defunct
bpcompatd processes that may appear at any time. These defunct
processes will eventually be cleaned up, but it might some time.
Workaround:
To avoid this issue, periodically, stop and restart bpcompatd:
/usr/openv/netbackup/bin/bpcompatd -terminate
/usr/openv/netbackup/bin/bpcompatd
--------------------------------------------------------------------------------
Etrack Incident = ET863123
Associated Primary Etrack = ET863120
Description:
A condition existed when the bprd service on the master server connected to
the hosts in its SERVER list and started a process on those servers to
remove old debug log files. If a host was in the MEDIA_SERVER list but not
in the SERVER list on the master server, bprd would not contact that host.
A change was made to ensure that bprd connects to hosts in both the SERVER
list and the MEDIA_SERVER list on the master server to remove old debug
log files.
--------------------------------------------------------------------------------
Etrack Incident = ET863150
Description:
NetBackup’s Release Broker's logging has been improved in the following
manner:
- The total amount of logging content has been reduced.
- The messages that are displayed have been enhanced to be more meaningful.
- Different debug levels are used for different purposes.
--------------------------------------------------------------------------------
Etrack Incident = ET863199
Description:
The SRCMEDIAID & DSTMEDIAID fields of the jobs database were not being
written to.
--------------------------------------------------------------------------------
Etrack Incident = ET861965
Description:
In some cases, when a request for a volume pended, the NetBackup-Java user
interface and vmoprcmd -xdpa would display an error when asked to show the
pending action.
--------------------------------------------------------------------------------
Etrack Incident = ET863314
Description:
The patch level of the (remote) client was wrong when Windows was configured
in the environment.
--------------------------------------------------------------------------------
Etrack Incident = ET861709
Associated Primary Etrack = ET701050
Description:
Network issues would cause tldd connect timeout issues that would result in
downed drives.
--------------------------------------------------------------------------------
Etrack Incident = ET861712 ET861714
Description:
Changes were made to ltid that corrected the following issues:
- ltid would stop and report the following message if it received a message
that were larger than 208 bytes.
Arg list too long
- Occasionally, ltid would not continue to run at startup.
--------------------------------------------------------------------------------
Etrack Incident = ET803746
Description:
Using the -i option for vmchange command resulted in an incorrect error
message that would indicate to users that this function is not implemented
in NetBackup Enterprise Media Manager (EMM).
--------------------------------------------------------------------------------
Etrack Incident = ET863393
Associated Primary Etrack = ET863378
Description:
Backup duplication errors would occur because of a timeout issue that caused
bptm to exit with 54 and 25 errors.
--------------------------------------------------------------------------------
Etrack Incident = ET862641
Associated Primary Etrack = ET702146
Description:
DSSU relocation (duplication) jobs no longer leave a bid_file_* on master
server.
--------------------------------------------------------------------------------
Etrack Incident = ET862648
Description:
Changes were added to correct a DSSU staging process issue that caused the
parent job to hang.
--------------------------------------------------------------------------------
Etrack Incident = ET862609
Description:
The fragment size set for a disk storage unit (DSU) was ignored when doing a
Synthetic backup.
--------------------------------------------------------------------------------
Etrack Incident = ET861978
Description:
Changes were made to eliminate potential race conditions between ltid and
vmd when adding a host entry to EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET862543
Description:
The bpplinclude command could not handle file paths that contain the %
character.
--------------------------------------------------------------------------------
Etrack Incident = ET574945
Description:
Snapshot client SAP backups would fail because no valid license key be
found on the server.
--------------------------------------------------------------------------------
Etrack Incident = ET862603
Description:
A change was made to ensure that bpbrmds no longer exits prior to
bpduplicate finishing (on Tru64 systems only).
--------------------------------------------------------------------------------
Etrack Incident = ET862491
Description:
The nbpushdata log files are now written to the following locations:
/usr/openv/var/nbpushdata (UNIX)
VERITAS\NetBackup\var\nbpushdata (Windows)
Log files are not pruned from these directories, so the files are available
for later review.
--------------------------------------------------------------------------------
Etrack Incident = ET863106
Description:
The MEDIA_UNMOUNT_DELAY is not honored consistently for standalone drives.
Workaround:
To avoid this issue, ensure an eligible tape is loaded in the drive before
You start a job.
--------------------------------------------------------------------------------
Etrack Incident = ET864928
Description:
A backup job would hang in the bpbrm process after the client read timeout
expired. The job would not finish and a 41 status (network connection
timed out) error would occur.
--------------------------------------------------------------------------------
Etrack Incident = ET865189 ET842864
Associated Primary Etrack = ET833467
Description:
Changes were made to enhance the performance and speed in which the list of
media servers would appear after a user selects Host Properties > Media
Servers from the NetBackup-Java Administration Console. The slow response
was caused by the following command, which would return the external
attribute settings for each media server.
vmoprcmd -h <server_name> -extall
--------------------------------------------------------------------------------
Etrack Incident = ET852905 ET850830
Associated Primary Etrack = ET832181
Description:
Changes were added to solve various issues in the Device Configuration
Wizard with respect to back-level media servers. In addition, a change
was made that solves a device configuration wizard defect that prevented
users from reconfiguring standalone drives as robotic.
--------------------------------------------------------------------------------
Etrack Incident = ET861980
Description:
Corrected a tape drive cleaning issue where the end user running the
NetBackup Administration Console on a UNIX server could not successfully
clean a tape drive using a path on a Windows server.
--------------------------------------------------------------------------------
Etrack Incident = ET865211 ET645838
Associated Primary Etrack = ET645838
Description:
A status 50 error would be shown in the Activity Monitor if a user tried to
perform a large duplication that was greater than 20 minutes. Similar
issues were reported in earlier versions of NetBackup. Smaller duplications
were not a problem.
--------------------------------------------------------------------------------
Etrack Incident = ET865184
Description:
Some languages use a comma, instead of a period, to delimit the fractional
portion of a floating point number. If the default language is set to one
of these language, some operations might fail. Specifically, any time a
floating point parameter is passed to the EMM server database it will
reject a floating point number delimited by a comma, instead of a period.
One example of this is attempting to change or set the cleaning frequency
of a drive.
Workaround:
To resolve this issue, change the decimal point character from a comma
to a period ('.'). This can be done by modifying the locale or switching
to a different locale, such as US English.
--------------------------------------------------------------------------------
Etrack Incident = ET865706
Description:
This maintenance pack contains multiple NB_SECURITY infrastructure changes.
--------------------------------------------------------------------------------
Etrack Incident = ET862283
Description:
Changes were made to correct the following issues with the nbemmcmd command.
- The nbemmcmd -getemmserver command would not always get the NetBackup
version.
- The nbemmcmd -setemmserver command would try to set the EMM server on
machines that were not in its domain.
- The nbemmcmd -setemmserver command would not set the EMM server of a master
server.
--------------------------------------------------------------------------------
Etrack Incident = ET865792
Description:
nbVersionNumber() would not return a zero (0) when there was an error
attempting to get the version number from the client. However, in certain
cases this does not happen.
--------------------------------------------------------------------------------
Etrack Incident = ET783403
Description:
The status collector daemon that NetBackup uses to monitor device and host
status for back-level media servers has been logging /vm/debug/reqlib.
This has made debugging for traditional media manager command lines
difficult. This change introduces a new media manager debug directory
/vm/debug/vmscd. This makes it much easier to obtain debugging information
for both vmscd and the media manager command lines.
--------------------------------------------------------------------------------
Etrack Incident = ET863402
Description:
A change was made to ensure the nbemmcmd -listmedia command prints out the
number of mounts, as well as the maximum mounts.
--------------------------------------------------------------------------------
Etrack Incident = ET863433
Description:
The message a user would receive when adding a host that already existed in
database was invalid hostname. A change has been made to correct this
message.
--------------------------------------------------------------------------------
Etrack Incident = ET847915
Associated Primary Etrack = ET820303
Description:
A change was made so that a READY standalone drive was not marked as
NOT-READY during a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET863427
Description:
bpmedialist now uses EMM to build the host list instead of using the storage
unit list.
--------------------------------------------------------------------------------
Etrack Incident = ET866829
Description:
Queuing jobs could not be canceled from bpdbjobs command.
--------------------------------------------------------------------------------
Etrack Incident = ET863413
Description:
A change was made to the nbemmcmd -help command. It now
returns an exit status of 0 instead of an error status.
--------------------------------------------------------------------------------
Etrack Incident = ET866997
Description:
If the NetBackup Request Daemon (bprd) terminated a backup before the
NetBackup Policy Execution Manager (nbpem) was invoked, the terminated
backup job may be reported with a "queued" status forever. This could
occur if a backup was initiated by the bpbackup command line and it
referenced an unwritable progress log file.
--------------------------------------------------------------------------------
Etrack Incident = ET569130
Description:
If the NetBackup Request Daemon (bprd) terminates a backup before the
NetBackup Policy Execution Manager (nbpem) is invoked, the terminated
backup job may be reported with a "queued" status forever. This can
occur if a backup is initiated by the bpbackup command line and it
references an unwritable progress log file.
--------------------------------------------------------------------------------
Etrack Incident = ET865243
Description:
If the NBDB database is not created properly during installation, the
install continues, however the user may not understand that there was an
issue creating the database. As a result, the user may encounter errors
in the command line and the user interfaces.
In addition, if during a patch installation that nbnd_upgrade fails, the
database ends up with the incorrect version. Again, nbemm will not start
because of the version mismatch.
Changes have been made so that the install will fail if the database
cannot be created or upgraded and installation warnings will be logged in
a new logging directory for nbnd commands. The new directories are:
UNIX: /usr/openv/netbackup/logs/nbdb
Windows: InstallPath\NetBackup\logs\nbdb
--------------------------------------------------------------------------------
Etrack Incident = ET865850
Description:
Erase job failures would occur because NDMP drives were being selected for
erase jobs.
Workaround:
To resolve this issue, down NDMP drives to prevent NetBackup from selecting
them for erase jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET865186
Description:
If you use the "Configure Multiple Copies" option before any storage units
are defined the following error message appears.
"Not all storage units are on the same media server"
A change was made to the message to correctly indicate that no storage units
exist.
--------------------------------------------------------------------------------
Etrack Incident = ET893223
Description:
When a server is configured to e-mail from the client after
a successful backup, the bpbrm process would hang and would
not exit because of an e-mail problem on the client.
--------------------------------------------------------------------------------
Etrack Incident = ET846230
Description:
A change was made to resolve an issue that caused NetBackup Release Broker
(NBRB) to crash randomly while performing a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET895177
Description:
A change was made to resolve an issue that caused NetBackup Policy
Execution Manager (NBPEM) to crash because of a shutdown during
clean_media_db operation.
--------------------------------------------------------------------------------
Etrack Incident = ET895170 ET895172
Description:
Changes were made to address scalability issues with NBPEM because
unnecessary computations were being performed of the "jobs due" time.
In addition, the internal queue management was a single thread to
handle multiple queues. This caused long waits to process requests on
some queues.
--------------------------------------------------------------------------------
Etrack Incident = ET834075
Description:
Improvements were added to the CPU utilization by bprd during restore
operations of a large numbers of files.
--------------------------------------------------------------------------------
Etrack Incident = ET862350
Description:
Jobs may queue instead of fail when all drives are down or not available
because of an onDemandOnly setting.
Workaround:
To avoid this issue, cancel the queued jobs if there is no possibility of
them getting drives.
--------------------------------------------------------------------------------
Etrack Incident = ET858772
Description:
Installer will verify that PBX service is running before attempting a server
patch install, and it will start the service if necessary.
--------------------------------------------------------------------------------
Etrack Incident = ET862424
Description:
Messages were added to the NetBackup log whenever media is
frozen/unfrozen/suspended/unsuspended.
--------------------------------------------------------------------------------
Etrack Incident = ET862425
Description:
A message has been added to the client log when the operator is about to
request a media that may be standalone. This message warns the operator
that they may need to manually load the requested media.
--------------------------------------------------------------------------------
Etrack Incident = ET862427
Description:
If a multiplexed job stopped during a tape span (on a standalone drive) the
Media Database for the next tape used would be incorrect, enabling this
tape to be used again and cause data to be overwritten.
--------------------------------------------------------------------------------
Etrack Incident = ET862428
Description:
Added a change to address the latest SCSI standard that changed a device
response to a Test Unit Ready command when the device is SCSI Reserved to
another initiator.
--------------------------------------------------------------------------------
Etrack Incident = ET862430
Description:
Added support for Quantum/Certance Ultrium 3 drive with WORM media.
--------------------------------------------------------------------------------
Etrack Incident = ET862431
Description:
Some tape drives on HP_UX would not perform an erase operation
from NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET862441
Description:
Canceled jobs no longer cause a future job to hang during a media mount.
--------------------------------------------------------------------------------
Etrack Incident = ET413285
Description:
A change was made to endure that timestamps were included in
the cluster agent debug.
--------------------------------------------------------------------------------
Etrack Incident = ET841107
Description:
During a synthetic backup job, one of the source images for the synthetic
may expire. If this happens, when the bptm or bpdm reader attempts to
read the image, it will experience a "no entity found" error from the
catalog. The bptm reader fails. For this particular case, the reader will
enter a code that causes it to hang up indefinitely.
--------------------------------------------------------------------------------
Etrack Incident = ET847324
Description:
Duplicate forms of the .ds file may be created as part of the NetBackup 5.x
to NetBackup 6.x upgrade process that cause bptm or bpbrmds to crash.
For example,
beany_1162489194_C1_F1.ds.info
beany_1162489194_C1_F1.ds.1162489194.img
beany_1162489194_C1_F1.ds.1162489194.info
beany_1162489194_C1_F1.ds
Workaround:
Normally, NetBackup perceives a .img and .info file as one "file" to its
I/O layer. There is a special compatibility mode that enables it to see
the extra .ds and its .info file as the same file in the previous pair.
To avoid this issue, remove one of the pairs, preferably the .img file and
its .info file.
--------------------------------------------------------------------------------
Etrack Incident = ET896802
Associated Primary Etrack = ET798913
Description:
An issue would occur when children jobs were retired due to exceeding the
time allowed in an incomplete state. The parent job, being resumed either
manually or automatically, resulted in an Frequent status code 805 error
because the invalid jobid was -1.
A change was added that prevents the child from starting since it is not
resumable. The new result will correctly be a 200 error if no children
can be started. An indication of this will be written to the policy
execution manager (pem) log.
--------------------------------------------------------------------------------
Etrack Incident = ET862590
Associated Primary Etrack = ET862589
Description:
Added the capability to open UNIX progress logs that are non-blocking.
--------------------------------------------------------------------------------
Etrack Incident = ET860837
Associated Primary Etrack = ET834130
Description:
Jobs would not be retried until all jobs associated with the parent job were
complete.
--------------------------------------------------------------------------------
Etrack Incident = ET860882
Associated Primary Etrack = ET845081
Description:
Restarting a job that was originally an immediate backup, may cause streams
of a different schedule type to be run.
--------------------------------------------------------------------------------
Etrack Incident = ET894249
Description:
NBJM was not forwarding the connect options to bpbrm. On a NetBackup 6.0
media server, bpbrm is able to obtain the connect options. Whereas on a
NetBackup 5.x media server, the connect options must be specified using the
command line.
--------------------------------------------------------------------------------
Etrack Incident = ET847976
Description:
If a synthetic backup job failed to get the requested resources, no
messages were displayed in the job details to explain the cause of a
job that appeared to be hung.
--------------------------------------------------------------------------------
Etrack Incident = ET860264
Associated Primary Etrack = ET860276
Description:
There was insufficient logging information provided when a
catastrophic failure occurred while accessing the UNIX
configuration (bp.conf). In addition, no re-try would be
attempted for such a failure.
--------------------------------------------------------------------------------
Etrack Incident = ET860844
Associated Primary Etrack = ET860273
Description:
Changes were made to resolve status 200 errors that occurred when a parent
job started when children were left active because PEM terminated or a
crash of a generic job occurred.
--------------------------------------------------------------------------------
Etrack Incident = ET860853
Associated Primary Etrack = ET858810
Description:
A change was made so that jobs no longer wait for resources after the window
is closed .
--------------------------------------------------------------------------------
Etrack Incident = ET860856
Associated Primary Etrack = ET860266
Description:
A change was made to address an issue that caused backups to fail with an
800 status.
--------------------------------------------------------------------------------
Etrack Incident = ET854621
Description:
Resolved an issue that caused scheduled, cold-catalog backups to not start.
--------------------------------------------------------------------------------
Etrack Incident = ET860879
Description:
Resolved an issue that caused PEM to run an incremental schedule instead of
a full schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET899176
Description:
Near the completion of a Synthetic backup, the following error message would
intermittently be issued to the Activity Monitor:
Error ACEMsgTran::handleOutput_u (pid=28968) write failed
from OUTPUT socket, errno=9(Bad file descriptor)
This error did not affect the successful completion of the backup, but it
did indicate a problem.
--------------------------------------------------------------------------------
Etrack Incident = ET592677
Associated Primary Etrack = ET808108
Description:
A change was added that resolves a segmentation fault that could occur while
performing Teradata backups on Linux platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET431952
Description:
This maintenance pack contains an enhancement that enables encryption for
Teradata backups.
--------------------------------------------------------------------------------
Etrack Incident = ET866750
Description:
The nbpushdata -modify_5x_hosts command now sets the standalone volume
database host to the EMM server on NetBackup 5.x hosts without standalone
drives.
--------------------------------------------------------------------------------
Etrack Incident = ET899837
Associated Primary Etrack = ET865853
Description:
There was a memory leak in the NetBackup Release Broker (nbrb) that caused
the memory utilization of nbrb to go very high after duplication/synthetic
jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET860860
Associated Primary Etrack = ET856242
Description:
The message queue between bprd and pem would fill up if the request to pem
was invalid.
--------------------------------------------------------------------------------
Etrack Incident = ET849248
Associated Primary Etrack = ET846190
Description:
Changes were made to resolve memory issues on immediate and user-backup
requests.
--------------------------------------------------------------------------------
Etrack Incident = ET832247
Description:
Deleting a cluster node no longer leaves invalid references.
--------------------------------------------------------------------------------
Etrack Incident = ET856478
Description:
The bptm -updatedb command would swap the number of images and the number of
valid images when inserting the data into the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET855644
Description:
A change was made to resolve a possible stack overflow issue that would
cause a system crash.
--------------------------------------------------------------------------------
Etrack Incident = ET850303
Description:
There is a timing issue with bringing the cluster online and running
runtpext. Bringing the cluster online (which can be slow), has an
adverse affect on the runtpext custom action that requests ltid.exe and
vmd.exe to be bounced. On some clustered NetBackup systems that have a
large number of devices (tape drives and robots) this can hang the
cluster install.
Workaround:
To resolve this issue, go into the Windows Task Manager and kill both the
"ltid.exe" and "vmd.exe" processes. The install will then continue and
complete successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET895259
Description:
Added support for PureDisk export to NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET850034
Description:
Changes were made to ensure that the device configuration analyzer utility,
mmcrawl, is working.
--------------------------------------------------------------------------------
Etrack Incident = ET863440
Description:
A change was made to ensure the nbemmcmd -errorsdb command no longer causes
a core dump on 64-bit machines.
--------------------------------------------------------------------------------
Etrack Incident = ET861373
Associated Primary Etrack = ET901494
Description:
Switches have been added to nbemmcmd to allow the use of a different
emmserver than those listed in the configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET863437
Description:
Formatting is now correct for strings on Windows x64 systems.
--------------------------------------------------------------------------------
Etrack Incident = ET794493
Associated Primary Etrack = ET777908
Description:
A restore would fail following a tape span due to attempting to position
to file number "0". The bptm logs show that a "STOP RESTORE" was received
for a restore that was already complete during the tape mount.
--------------------------------------------------------------------------------
Etrack Incident = ET792615
Associated Primary Etrack = ET781425
Description:
bpjobd script would hang sporadically causing the user to manually restart
to view the job monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET864935
Associated Primary Etrack = ET821288
Description:
If the client for a multiplexed backup could not be contacted, the job would
take nearly twice as long as to timeout.
--------------------------------------------------------------------------------
Etrack Incident = ET419594
Description:
Added a new touch-file (/usr/openv/netbackup/IGNORE_ACL) on UNIX client
machines to not back up ACLs.
--------------------------------------------------------------------------------
Etrack Incident = ET594838
Description:
On HP-UX clients, NetBackup now treats cifs file system mount points
as NFS rather than local. Therefore, policies with ALL_LOCAL_DRIVES
specified will no longer back them up.
--------------------------------------------------------------------------------
Etrack Incident = ET614569
Description:
True Image Restore Plus (TIR+) backups currently delete any
TIR information files that are 10 days old or more. Symantec
added a new touch file for UNIX clients to set the number of
days to keep the TIR information files. The default will
remain 10 days, but that can now be set to a value higher
than 10 if desired. In addition, setting this value to 0 (zero)
makes NetBackup never delete old TIR information files.
The touch file is called /usr/openv/netbackup/TIR_INFO_KEEP_DAYS.
Simply put an integer value in this file that represents the
number of days to keep the TIR information files. Numbers that
are less than 10 will set the value to 10 (other than 0).
--------------------------------------------------------------------------------
Etrack Incident = ET406353
Description:
Multi-streaming with wild-cards and NEW_STREAM directives would not
process correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET864177
Description:
The deletion of an application cluster would fail if there were storage
units (STU's) associated with it.
Workaround:
To avoid this issue, delete storage unit first.
--------------------------------------------------------------------------------
Etrack Incident = ET853592
Description:
An archive job may complete with the following error:
"EXIT STATUS 3: valid archive image produced, but no files
deleted due to non-fatal problems"
This is an issue in the underlying operating system and not
NetBackup. This patch detects the condition and takes the
additional steps necessary to handle it.
Workaround:
To resolve this issue, the user may manually remove the backed up
files after the archive completes. Note that care must be taken
not to remove files that are created or modified after the start
of the archive job.
--------------------------------------------------------------------------------
Etrack Incident = ET917548
Associated Primary Etrack = ET901564
Description:
If a window closes while a multiple data streams backup has children queued,
the resume of the parent may produce a 200 error.
--------------------------------------------------------------------------------
Etrack Incident = ET803831
Description:
Executing a bpps -a command on a RedHat 5.0 system would produce
the following NetBackup processes:
tail: cannot open `+2' for reading: No such file or directory
tail: cannot open `+2' for reading: No such file or directory
--------------------------------------------------------------------------------
Etrack Incident = ET918511
Associated Primary Etrack = ET860790
Description:
Changed Policy Execution Manager to log failure history message as an
informational message to avoid adding it to the error log report. Also log
failure history message based on failure history threshold (default
12 hours) instead of using the policy update interval (default 10 minutes)
thus reducing the number of entries logged.
Workaround:
To avoid this issue, increase the policy update interval threshold from
the default of 10 minutes.
--------------------------------------------------------------------------------
Etrack Incident = ET860802
Associated Primary Etrack = ET850162
** Description:
The disk storage unit (DSU) staging did not maintain a retention level on
secondary copies when using inline tape copy (ITC).
--------------------------------------------------------------------------------
Etrack Incident = ET849012
Description:
If nbemm is down and NOM connects to NBSL, then NBSL would
crash.
--------------------------------------------------------------------------------
Etrack Incident = ET764809
Associated Primary Etrack = ET764804
Description:
On Linux clients, raw partition backups of raw devices would
fail with a status 6 error when compression was enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET860288
Associated Primary Etrack = ET857531
Description:
Policy Execution Manager would stop processing manual backup jobs when
house keeping was performed (bptm delete_expired). The worst case
scenario was when the media server could not be reached. The Policy
Execution Manager would then wait for the time out
(CLIENT_CONNECT_TIMEOUT)to be exceeded before moving on.
Changed the Policy Execution Manager to start a third nbproxy which
processes only clean media database (db) commands to avoid a delay of
manual backups.
--------------------------------------------------------------------------------
Etrack Incident = ET914057
Description:
A problem existed that caused an error status on user backups to sometimes
return a 236 error when a 199 error was expected.
--------------------------------------------------------------------------------
Etrack Incident = ET867927
Description:
When using the bpsetconfig command to implement bp.conf entries for a
client, if stdin was used, the list could not exceed 1023 bytes. If
the list did exceed 1023 bytes, the entire list was ignored and the
update failed.
Workaround:
To avoid this issue, use the command with the filename as a parameter
and everything will work properly.
--------------------------------------------------------------------------------
Etrack Incident = ET919129
Associated Primary Etrack = ET848190
Description:
When Multiple Data Streams, DHCP and Windows Open File Backups (WOFB’s) are
enabled, jobs end with 48 status. To resolve this issue, the generic job
(nbgenjob) was changed to only pass a -hostname option if DHCP is enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET853612
Description:
The parent job would exit with a status 50 before starting any children. To
Resolve this issue, the parent job (nbgenjob) was changed to ping the job
manager as soon as possible after startup instead of waiting three minutes.
--------------------------------------------------------------------------------
Etrack Incident = ET832007
Description:
Logs were unclear on what the problem was when database operations were
performed on un-assigned media.
--------------------------------------------------------------------------------
Etrack Incident = ET505726
Description:
The "bpdbjobs -resume" command no longer reports an incorrect number of
restores that were resumed.
--------------------------------------------------------------------------------
Etrack Incident = ET845150
Description:
The machine update code has been updated so it no longer allows machines to
have invalid parent keys.
--------------------------------------------------------------------------------
Etrack Incident = ET591318
Description:
NetBackup now checks the file list to validate that UNIX
file paths begin with a "/" character. This will also
catch cases where extra characters are added to directives
(for example, "ALL_LOCAL_DRIVES;").
--------------------------------------------------------------------------------
Etrack Incident = ET856486
Associated Primary Etrack = ET997038
Description:
Added support for failing over NearStore storage units to a different NetApp
filer that had been mirrored using NetApp's Volume Snap Mirror technology.
--------------------------------------------------------------------------------
Etrack Incident = ET919043
Description:
A job that was configured to use a storage unit group, failed with a
status 129. The job details for a retry gives the appearance that it
retried the job with the STU from the previous try. In reality, all of
the STUs in the group were queried for the best possible candidate.
--------------------------------------------------------------------------------
Etrack Incident = ET838968
Description:
This maintenance pack contains new versions of ACE and TAO libraries. These
libraries contain fixes for race conditions and other problems.
--------------------------------------------------------------------------------
Etrack Incident = ET864163
Description:
A change was made so that nbrb no longer sends "bptm -rptdrv" to an
inactive node in a cluster. In addition, the output of the
nbemmcmd -listhost command has been changed. The description of
machine type for emmserver has been changed from "server" to
"emmserver".
--------------------------------------------------------------------------------
Etrack Incident = ET896185
Description:
When you log in on a node of master in cluster environment, the "Add STU"
operation did not show all of the available media servers.
Workaround:
To avoid this issue, log in using a virtual (cluster) name.
--------------------------------------------------------------------------------
Etrack Incident = ET901549
Associated Primary Etrack = ET857094
Description:
During testing, an active duplicate job was noticed in the Activity
Monitor. The job had a status 150 message in detailed status and it was
still at attempt 1. Its children appeared dead. (No activity in since
12:47 and they were being displayed as active).
The parent seemed active. It was not only displayed active but it was
doing a tape mount around 18:30. It had received a status 150 around
12:47 pm.
Workaround:
To avoid this situation, you can wait until the job state is active and
then cancel it. This will cause it to die correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET849073
Description:
Canceled mount/unmount requests would cause future unmount requests to hang
in BPTM.
--------------------------------------------------------------------------------
Etrack Incident = ET901476
Description:
Changes were made to keyword handling of user backups from
NetBackup 5.0 to 6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET814657
Description:
A backup job would potentially hang if bpbrm received a 174 error (media
manager - system error occurred) prior to receiving a "media ready"
indication from bptm.
--------------------------------------------------------------------------------
Etrack Incident = ET519708
Description:
The Perform Snapshot Backup option in Policy dialog should be disabled if
the Block level increment (BLI) is selected.
--------------------------------------------------------------------------------
Etrack Incident = ET922508
Associated Primary Etrack = ET854626
Description:
During multiplexed backups, multiple retention levels could be added to a
media, even if it was not configured to be allowed.
--------------------------------------------------------------------------------
Etrack Incident = ET515830
Description:
The SSO_SCAN_ABILITY option was not being used and has been removed to avoid
confusion.
--------------------------------------------------------------------------------
Etrack Incident = ET819221
Associated Primary Etrack = ET797322
Description:
Pegasus Software Drives on Windows did not work in NetBackup 6.0 as Disk
Storage Units.
--------------------------------------------------------------------------------
Etrack Incident = ET855357
Description:
NetBackup Enterprise Media Manager (EMM) was using the wrong directory when
checking for a disk full condition that affected the NetBackup Relational
Database (NBDB). If a mirrored transaction log was created, EMM was
checking the location of the main transaction log only.
--------------------------------------------------------------------------------
Etrack Incident = ET922513
Associated Primary Etrack = ET896030
Description:
FlashBackup restores would sometimes produce 252 errors when done with a
short file list.
--------------------------------------------------------------------------------
Etrack Incident = ET865177
Associated Primary Etrack = ET864919
Description:
Freeze scratch media that was found to have a Recorded Volume Serial Number
(RVSN) was not expected. Users must use bplabel to correct this problem
and make the media useable again.
--------------------------------------------------------------------------------
Etrack Incident = ET850088
Description:
Policy Execution Manager no longer passes unlocalized status descriptions
in the error database.
--------------------------------------------------------------------------------
Etrack Incident = ET848632
Associated Primary Etrack = ET841558
Description:
A fix was added so that nbgenjob no longer fails with status 25
and nbpem no longer receives a status 50 after a multi-streaming
job.
--------------------------------------------------------------------------------
Etrack Incident = ET858227
Description:
NetBackup-Java Administration Console Device Configuration wizard now
correctly updates the Robot Type of drives that are detected as stand
alone but drag-dropped by user to a robot.
--------------------------------------------------------------------------------
Etrack Incident = ET865805
Description:
On Windows systems, the Vault reports were not being localized.
--------------------------------------------------------------------------------
Etrack Incident = ET896510
Description:
A change was made to correct an issue that was causing code to appear in a
progress log.
--------------------------------------------------------------------------------
Etrack Incident = ET896531
Description:
A change was made to correct a core dump issue that occurred from vmdareq
when it was run from a command line with no switches.
--------------------------------------------------------------------------------
Etrack Incident = ET896568
Description:
The words "handling path" were not being recorded in the \db\error\ logs
file. The All Logs Entry and the bperror command both mine their results
from the \db\error\ logs and the words "handling path" could be used to
determine if the correct data is being backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET916389
Associated Primary Etrack = ET863109
Description:
Changes were added to resolve an nbpem core dump that would occur after a
successful backup.
--------------------------------------------------------------------------------
Etrack Incident = ET863396
Description:
NDMP backup fails when TIR data spans tapes. This failure occurs only for
NDMP local or NDMP 3-way (backup to an NDMP drive).
Workaround:
Rerunning the backup to a different media will likely work since it is
unlikely that tape spanning will occur during TIR data. (This is because
the TIR data is usually a fraction of the size of the backup image itself.)
Another approach is add the following line to the file
<installdir>/netbackup/db/config/ndmp.cfg
NDMP_MOVER_CLIENT_DISABLE
Adding this line will have a minimal impact on backups. However it will
cause a significant performance impact to dup/verify/import when using
NDMP drives.
--------------------------------------------------------------------------------
Etrack Incident = ET777981
Description:
nbpemreq would fail if a large time value was passed to the nbpemreq
predict option. If you specified a number that exceeded a long value
for the command, nbpemreq -predict -dateu <timevalue>, the results
would be undefined.
--------------------------------------------------------------------------------
Etrack Incident = ET821317
Description:
A misleading error status 48 (client hostname could not be found) may be
applied to a job if a communication problem occurred between the media and
the master server. A typical cause of the problem was an expired license
on the media server. In this case, the error status should have been 161
(Evaluation software has expired.)
--------------------------------------------------------------------------------
Etrack Incident = ET828730
Description:
In a rare situation, a FlashBackup job could not be cancelled.
--------------------------------------------------------------------------------
Etrack Incident = ET852018
Description:
Changes have been made to reduce the performance overhead when sending mail
to a client after a backup job completes.
--------------------------------------------------------------------------------
Etrack Incident = ET896769
Associated Primary Etrack = ET923399
Description:
The pem logs report a scheduled backup (SB) job type as an immediate (IB)
backup job type after a failed immediate backup.
--------------------------------------------------------------------------------
Etrack Incident = ET864933
Description:
On Windows media servers, restores from disk in some cases would potentially
read unneeded data instead of skipping it, which could affect performance.
--------------------------------------------------------------------------------
Etrack Incident = ET805992
Description:
In some cases, hot catalog backup would report success even though the
ASA backup was either not successful or conditionally successful.
--------------------------------------------------------------------------------
Etrack Incident = ET924798
Associated Primary Etrack = ET860296
Description:
Callers to bpdbm make unnecessary licensing checks that could lead to
misleading error messages.
--------------------------------------------------------------------------------
Etrack Incident = ET923799
Description:
With NetBackup running under NetBackup Access Control (NBAC), authorization
checks were skipped for some operation of corba daemons. This could have
enabled an unauthorized user to perform some privileged operations.
--------------------------------------------------------------------------------
Etrack Incident = ET924345
Associated Primary Etrack = ET856266
Description:
Jobs that were due to start, would not start if JobDefinition::checkDueness
took more than one second.
--------------------------------------------------------------------------------
Etrack Incident = ET901028
Description:
Changes were made that enable you to now use "./bpnbat -login -info" on
Linux systems.
Workaround:
You can also use bpnbat in interactive mode by using just the -login option.
--------------------------------------------------------------------------------
Etrack Incident = ET778927
Description:
A master could be renamed to a pre-existing media server. However, the
logs were recording the wrong name if a machine was renamed to a
pre-existing machine.
--------------------------------------------------------------------------------
Etrack Incident = ET417907
Description:
When vmquery was used with a prefix containing '_', the char '_' was used
as a wild card character and an out of order media id could be given.
--------------------------------------------------------------------------------
Etrack Incident = ET831182
Description:
The message, "database backup is currently disabled," appeared in the
Problems report even when a scheduled hot catalog backup was configured.
--------------------------------------------------------------------------------
Etrack Incident = ET924482
Description:
The parent key could be incorrectly set when adding a node of a cluster.
The parent key of a media server could be incorrectly set if node of master
cluster was given instead of cluster name.
--------------------------------------------------------------------------------
Etrack Incident = ET534073 ET534196 ET569931 ET592599
Description:
The following Windows updates have been added to this maintenance pack:
- Updated the support utility nbsupport to version 2.1.2
- Updated the Windows support utility nbsupport.exe to version 2.1.2
- Updated the Windows support utility nbsu_win_cmds.exe to version 2.0
- Added the Windows support script fs
--------------------------------------------------------------------------------
Etrack Incident = ET864934
Description:
A duplication may have been reported as successful if a defective tape
drive incorrectly reported a tape mark on the read operation, followed
by an I/O error. This maintenance pack detects this error condition.
--------------------------------------------------------------------------------
Etrack Incident = ET803724
Description:
Catalog recovery from a hot catalog backup failed if Bare Metal Restore
(BMR) was installed but not configured and/or running at the time of the
hot catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET648727
Description:
Added a new Automated Cartridge System (ACS) vendor for media and drive
types.
--------------------------------------------------------------------------------
Etrack Incident = ET616381
Description:
In NetBackup-Java Administration Console, inventory of a robot attached to
a cluster node resulted in volumes being added with the cluster node as the
robot control host and not the virtual host name. This behavior has been
changed to make the virtual host name as the control host. Doing this
avoids potential problems in inventory if a cluster fails over to a
different cluster node.
--------------------------------------------------------------------------------
Etrack Incident = ET916378
Associated Primary Etrack = ET915043
Description:
The bpdbjobs timestamp output is no longer truncated for STARTED and ENDED
fields.
--------------------------------------------------------------------------------
Etrack Incident = ET830327
Description:
Access failures to the Activity Monitor were occurring for the
Domino-partitioned, server backup reports file (exec.nbf).
However, the bpbrm log would exit with a Status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET895584
Associated Primary Etrack = ET786448
Description:
NetBackup for Lotus Notes parses all the paths in the
LOTUS_NOTES_PATH variable to determine the Lotus program
directory. The first path in the LOTUS_NOTES_PATH variable
in which "bin/server" is present is treated as a Lotus Program
directory. If any other path (for example, the Lotus data
directory) which is present in the beginning and "bin/server",
exists in that path then it is misinterpreted as Lotus program
directory. This causes the backup to fail with a status 9 error.
Workaround:
To resolve this issue, enter the path of the Lotus program
directory in the beginning of LOTUS_NOTES_PATH variable.
--------------------------------------------------------------------------------
Etrack Incident = ET842011
Description:
bpmedialist could not be killed from the Activity Monitor successfully.
A change was made to ensure the correct program name is being passed from
bpmedialist to the job manager (JM).
--------------------------------------------------------------------------------
Etrack Incident = ET639038
Description:
A correction was made to ensure the vulnerability test for
bprd (Vuln_bprd.tst) no longer generates a core dump issue.
--------------------------------------------------------------------------------
Etrack Incident = ET925564
Description:
The "bpdbm –consistency 2" command was removed from the
list of commands that nbsupport runs.
--------------------------------------------------------------------------------
Etrack Incident = ET926712
Description:
A small memory leak in Policy Execution Manager when processing change
events has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET926721
Description:
Changed the Policy Execution Manager to pass the locale attributes correctly
to the job manager instead of setting them all to lctype.
--------------------------------------------------------------------------------
Etrack Incident = ET852018
Description:
Changes were made to address some small performance issue due to unnecessary
string duplications in the Policy Execution Manager when mailing client
status upon job completion.
--------------------------------------------------------------------------------
Etrack Incident = ET498723
Description:
In the event that a shared standalone drive is updated to be robotic, other
hosts that share this drive will also be updated to robotic. If the robot
is not configured on any of those hosts, however, this results in an
illegal configuration.
Workaround:
To avoid this issue, manually create robotic entries or only use the Device
Configuration wizard.
--------------------------------------------------------------------------------
Etrack Incident = ET926699
Associated Primary Etrack = ET925811
Description:
When drives are selected for NDMP restores, NetBackup media servers are
preferred over NDMP tape servers that are not local to the NDMP host being
restored to.
Workaround:
If a media server has drives with paths to both NetBackup and NDMP servers,
you should down the NetBackup paths before initiating the restore.
--------------------------------------------------------------------------------
Etrack Incident = ET852171
Description:
The EMM server does not reject a client-provided media_id such as, '------'.
This is not a regression. The NetBackup 5.x behavior was exactly the same.
Workaround:
This issue is a client application error when such a name comes is used.
--------------------------------------------------------------------------------
Etrack Incident = ET851125
Associated Primary Etrack = ET793484
Description:
In some instances a job would receive an incorrect 24 status (socket write
failed) instead of the correct 84 status (media write error).
--------------------------------------------------------------------------------
Etrack Incident = ET846076
Description:
An incremental hot catalog backup would fail with a 190 error if the master
server name configured in the hot catalog backup policy differed from the
currently active master server name where each name is a valid name for the
host. This would occur if the long name was used in the policy, but the
short name was being used in the bp.conf file.
--------------------------------------------------------------------------------
Etrack Incident = ET863389
Description:
Duplication of NDMP image fails when using non-NDMP drives.
This problem only occurs when the duplication is using the shared memory
method (SHM) method. In NetBackup 6.0, this happens for any NDMP backup
that used MM (non-NDMP) drives (also known as, "Remote NDMP"). In addition,
this happens if an NDMP image is duplicated to a non-NDMP drive and then
the duplicated image is duplicated.
The progress log shows the following error:
ERR - Unable to create data socket to receive TIR data.
Workaround:
To avoid this issue, disable the shared memory method by adding the
following touch file:
<installdir>/netbackup/NOSHMDUP
Additional Notes:
This problem has been fixed in this maintenance pack, such that all
duplications of NDMP backup images using non-NDMP drives will now use
the shared memory method.
(This problem was solved by disabling shared memory method for all
NDMP images in the NetBackup 5.1 maintenance packs.)
--------------------------------------------------------------------------------
Etrack Incident = ET828441
Description:
NetBackup relational databases would not be restarted when a cold catalog
backup was canceled.
--------------------------------------------------------------------------------
Etrack Incident = ET930028
Description:
A hot catalog backup parent job no longer fails with a status 818 error
(retention level mismatch).
--------------------------------------------------------------------------------
Etrack Incident = ET893639 ET417284
Description:
When NetBackup is clustered, NOM would show the wrong information about
services and media.
--------------------------------------------------------------------------------
Etrack Incident = ET583036
Description:
Restoring a Lotus database link no longer results in a loss of data.
--------------------------------------------------------------------------------
Etrack Incident = ET922076
Description:
When a database link is restored on UNIX platform, it is restored with the
size of the original database it was pointing to when the backup was taken.
--------------------------------------------------------------------------------
Etrack Incident = ET865713
Description:
Under NBAC, 'bpnbaz -setupsecurity' could fail silently, potentially
compromising the desired access control hierarchy.
--------------------------------------------------------------------------------
Etrack Incident = ET854649
Description:
The shutdown and startup of the NetBackup relational databases, NBDB and
BMRDB, will be logged to the NetBackup error log.
--------------------------------------------------------------------------------
Etrack Incident = ET928712
Associated Primary Etrack = ET897092
Description:
NetBackup Job Manager (NBJM) could take a long time to unload drives,
or fail to unload drives because the media servers all had multiple
endpoints, many that were on unreachable networks.
For example, an unreachable network would take about 225 seconds to
fail on Solaris, and some callbacks would take about 10 to 15 minutes
to iterate all failed endpoints.
A change was added to the endpoint selection algorithm so that if
there is at least one endpoint that matches the server list, it will
only attempt those endpoints that match the server list.
--------------------------------------------------------------------------------
Etrack Incident = ET927755
Associated Primary Etrack = ET926665
Description:
On some Windows machines, any Firewall_in bpconf configuration would report
as "Malformed Firewall_in line" in the VxUL log files, and rendered the
NAT translation feature as not operational.
--------------------------------------------------------------------------------
Etrack Incident = ET926704
Associated Primary Etrack = ET926503
Description:
If a user backup submits a very large number of files, PEM may cause a
memory fragmentation and possibly a crash.
Workaround:
To resolve this issue, reduce the file list size by specifying directories
instead of individual files.
--------------------------------------------------------------------------------
Etrack Incident = ET857478
Associated Primary Etrack = ET838788
Description:
NetBackup currently treats all read-only HFS file systems
on Mac OS X as CD-ROMs and disallows the backup. This
change allows the backup of mounted read-only file systems
that are not CD-ROMs.
--------------------------------------------------------------------------------
Etrack Incident = ET515549 ET933307
Description:
The CIsActive function that is loaded from the NBClusterConfig.dll failed on
64-bit systems.
Additional Notes:
The use of VCS API calls, which did not support 64-bit platforms in the
past, have been removed. IsActive simply tests if the shared disk resource
is on the current system to determine if it is the active node.
--------------------------------------------------------------------------------
Etrack Incident = ET932016 ET988979 ET1002606
Description:
Buffer overflow areas have been identified and corrected in daemons that
run on Veritas NetBackup master, media, and client servers. Successful
access to a vulnerable Veritas NetBackup server and the ability to
successfully execute arbitrary code could potentially result in
unauthorized access with elevated privilege on a system.
--------------------------------------------------------------------------------
Etrack Incident = ET932003
Description:
A change was added to resolve a possible memory corruption issue in the
legacy DA process (vmd on EMM server).
--------------------------------------------------------------------------------
Etrack Incident = ET927553
Associated Primary Etrack = ET924626
Description:
Fixed an issue that caused bpbkar to hang on Linux systems if it encounters
an NFS mount point when the NFS server is down.
Workaround:
To resolve this issue, add the NFS mount point to the exclude list for the
client.
--------------------------------------------------------------------------------
Etrack Incident = ET854810
Description:
By using the bprestore command (/usr/openv/netbackup/bin/bprestore) it is
now possible to restore an image using a non-primary copy.
Workaround:
In addition, you can use the bpchangeprimary command
(/usr/openv/netbackup/bin/admincmd/bpchangeprimary) to change the primary
copy of the image.
--------------------------------------------------------------------------------
Etrack Incident = ET533389
Description:
For a True Image Restore (TIR) that is larger than 2GB, the following error
would occur when reading the TIR information.
Error occurred reading TIR information, expected -2103963310 bytes, read
2191003986
The bpdm log would show the following:
11:03:32.958 [20388] <16> read_data_tir: ERR - Error occurred reading TIR
information, expected -2103963310 bytes, read 2191003986
2191003986 is the size of the TIR file -
-rw------- 1 root root 2191003986 Dec 30 10:50
devnfs2-bkup_1135889406_C1_TIR.1135889406.img
The problem only occurred, when the TIR file was larger than 2GB.
--------------------------------------------------------------------------------
Etrack Incident = ET863133
Description:
A fix was added so that a hot catalog recovery from a hot catalog backup to
a new master server name no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET925227
Associated Primary Etrack = ET922389
Description:
When the client name is in upper case, a Windows backup uses WOFB even
though the clientDB entry disables the WOFB.
Workaround:
To resolve this issue, use the same case for client name in client
database and policy database.
--------------------------------------------------------------------------------
Etrack Incident = ET895746
Description:
The renewal of a machine credential issued by a non-root authentication
broker no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET932264
Associated Primary Etrack = ET893298
Description:
An issue existed that would sometimes cause a job to run on the exclude day
even if a frequency scheduling of 24 hours was used.
--------------------------------------------------------------------------------
Etrack Incident = ET829853
Description:
FlashSnap Instant Recovery rotation would fail on Linux
because of a bprd request popen failure.
--------------------------------------------------------------------------------
Etrack Incident = ET855922
Description:
Catalog archiving would fail intermittently with the following message:
bpcatarc: failure running catalog archiving backup policy: the specified
policy is not active (247)
Workaround:
This problem was observed with a mis-configured /etc/hosts file, which
caused excessively long DSN lookups. To avoid this situation, configure
the /etc/hosts file to avoid long DSN lookups.
--------------------------------------------------------------------------------
Etrack Incident = ET796521
Associated Primary Etrack = ET704676
Description:
A backup job would fail with a status 130 when a client path
exceeded 1023 characters.
Workaround:
To avoid this issue, add the long directory path to an exclude
list.
--------------------------------------------------------------------------------
Etrack Incident = ET893368 ET893377 ET893379
Description:
If a Catalog Cleanup operation is kicked off in the middle
of a Hot Catalog Backup, the operation may clean up expired
image catalog entries that were given to the Hot Catalog Backup
in its file list, causing the Hot Catalog Backup to finish
with a partial success.
Changes have been made so that a Hot Catalog Backup now completes with
success status of 0. In addition, it internally detects the cleaned up
image catalog entries, and quietly ignores them.
--------------------------------------------------------------------------------
Etrack Incident = ET930124
Description:
A change has been made to ensure that NBPEM finds all user-initiated jobs,
all of the time.
--------------------------------------------------------------------------------
Etrack Incident = ET933326
Associated Primary Etrack = ET917312
Description:
nbnos would core dump on an HP-UX master server with max_thread_proc set at
the default value of 64. Every nbpem restart would cause nbnos to create
more threads. Corrections were made to nbpem that prevent nbnos from
creating new threads every time nbpem is restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET649458
Description:
The VRTS VxFS file system does not support named data streams
that contain directory structures. A check was added to warn
users if a named data stream that contains a directory structure
is found during file processing. Such structures will not be
backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET933586
Associated Primary Etrack = ET932325
Description:
During a multi-streamed database backup (MS-SQL backup in this case), the
media gets unmounted/mounted again intermittently. Ideally, the NetBackup
resource broker (nbrb) should try to use the loaded media (preferably same
media) for all streams.
--------------------------------------------------------------------------------
Etrack Incident = ET915850
Associated Primary Etrack = ET915879
Description:
Changes were made to ensure that multi-threaded processes no longer crash.
--------------------------------------------------------------------------------
Etrack Incident = ET918766
Description:
Sorting would not work on some columns if the report contained one or more
hidden columns.
--------------------------------------------------------------------------------
Etrack Incident = ET933398
Associated Primary Etrack = ET933394
Description:
Backups may not run as expected if full and incremental had the same
frequency.
--------------------------------------------------------------------------------
Etrack Incident = ET926835
Associated Primary Etrack = ET794461
Description:
Corrected a possible truncation of a file's user or group name.
This change allows for a full 32 character user and group name.
--------------------------------------------------------------------------------
Etrack Incident = ET931959
Associated Primary Etrack = ET931900
Description:
Corrected errors that caused canceled backups to leave the tape media
without a valid empty header on it.
--------------------------------------------------------------------------------
Etrack Incident = ET850961
Associated Primary Etrack = ET809378
Description:
The restore of database and compressed files could fail with
a status 5 when "overwrite existing files" was not selected
and the files to be restored exist.
--------------------------------------------------------------------------------
Etrack Incident = ET819697
Description:
This maintenance pack contains enhancements and fixes to some minor errors
that were occurring in NOM (specifically in the Display Point version of
NetBackup in NOM).
--------------------------------------------------------------------------------
Etrack Incident = ET797596
Description:
On the NOM user interface, (Managing > Media > Details) the "Time Assigned"
filter was not functioning properly.
--------------------------------------------------------------------------------
Etrack Incident = ET896513
Description:
NBPEM e-mail function would send a secondary "additional information" e-mail
for some failed backups.
--------------------------------------------------------------------------------
Etrack Incident = ET892407
Description:
Corrected an issue that caused bplabel to fail if VxSS (NBAC) is enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET807751
Description:
The "import" feature would not work on a NOM Windows server after an
"export" database (DB) function was performed.
--------------------------------------------------------------------------------
Etrack Incident = ET852129
Description:
Under NBAC, a NetBackup 5.1 media server or client could not be configured
with NetBackup 6.0 master.
The bpnbat -loginmachine command would cause a hang or failure on a
NetBackup 5.1 media server or client. The following logs were produced.
14:52:27.578 [2035] <2> get_string: (7) inadequate buffer space for data
14:52:27.578 [2035] <2> get_string: read until the buffer was full; got:
14:52:27.578 [2035] <2> get_string: EXIT STATUS 13
14:52:27.578 [2035] <2> bprd_get_nbac_pdr_info: get_string() failed,
Error 0 (0), success
--------------------------------------------------------------------------------
Etrack Incident = ET794712
Associated Primary Etrack = ET785847
Description:
Changes were added to increase the efficiency of an image cleanup when the
disk-stage storage unit (DSSU) fills.
--------------------------------------------------------------------------------
Etrack Incident = ET934452
Description:
The machine state could be reported inaccurately from the
nbemmcmd -listhosts -verbose command if the machine state was inactive
for disk jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET853808 ET898992
Description:
A multi-streamed parent job may have been retried more than the configured
number of times if the parent job failed before the streams were created for
the first time.
--------------------------------------------------------------------------------
Etrack Incident = ET797314
Description:
Add VxUL Logging support for Activity Monitor module and as a result
a new log file with ID 263 will be generated in the logs folder.
--------------------------------------------------------------------------------
Etrack Incident = ET935814
Description:
Corrected the check used to determine if the local device_mappings.txt
is current.
--------------------------------------------------------------------------------
Etrack Incident = ET806878
Associated Primary Etrack = ET814738
Description:
A multi-threading issue would occasionally cause bpstsinfo
to core dump on some platform and operating system combinations.
--------------------------------------------------------------------------------
Etrack Incident = ET913578
Description:
NBSL is crashing due to the read only directory or invalid path of nbsl.xml.
--------------------------------------------------------------------------------
Etrack Incident = ET936802
Associated Primary Etrack = ET924495
Description:
The backup of a directory that contains a large number of
files using wild cards would fail with a STATUS 70.
Workaround:
To resolve this issue, specify the directory in question in
the file list rather than using wild cards.
--------------------------------------------------------------------------------
Etrack Incident = ET933518 ET933543 ET544382 ET933547 ET933544 ET933528 ET933537
ET830317 ET830319 ET916879
Associated Primary Etrack = ET814702 ET799749 ET647499 ET899240 ET851802
ET858011
Description:
The following changes were added to this maintenance pack in response to
customer escalations:
- Issues with pop-ups that occurred when FlashBackup terminated
- Restores from multiple images
- Multi-volume image and 32-bit overflow
- Incorrect handling of multi-byte characters
- Incomplete data being sent to catalog
- Ensure that directories are restored in descending order
- Hard-link restore problems
- Linux master and FlashBackup windows
--------------------------------------------------------------------------------
Etrack Incident = ET861506
Description:
The Job Manager must forward a snap ID from a non-streamed Windows open
file backup (WOFB) to the Policy Execution Manager for VSP cache files
to be cleaned. In addition, changed the Policy Execution Manager to add
SNAP_ID directives to include the file list.
--------------------------------------------------------------------------------
Etrack Incident = ET918477
Associated Primary Etrack = ET917028
Description:
This is limited to the Nearstore storage unit.
If an incremental backup was done after a synthetic full backup, and no
other full backups existed on that volume, then the incremental would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET899124
Associated Primary Etrack = ET899121
Description:
This issue only affected restores from Nearstore storage units.
Non-full backups (a subset of the entire backup ) where files were pulled
from fragments other than fragment 1 would fail. The issue was that the
image relative offset was not being tracked and NetBackup was seeking to
the incorrect offset within the image.
Workaround:
To resolve this issue, use the Nearstore File System Export functionality
or duplicate the entire backup to basic disk or some other media.
--------------------------------------------------------------------------------
Etrack Incident = ET924417
Associated Primary Etrack = ET917312
Description:
Please see etrack
--------------------------------------------------------------------------------
Etrack Incident = ET921795
Description:
Changes were made in this maintenance pack to ensure the Log Management
feature is working.
--------------------------------------------------------------------------------
Etrack Incident = ET932217
Description:
NBJM was failing jobs with a status 818 (retention level mismatch) because
of an incorrect check.
--------------------------------------------------------------------------------
Etrack Incident = ET937680
Description:
Some TLD libraries with barcode readers were unable to import or inventory
media with an unbarcoded media in the library.
--------------------------------------------------------------------------------
Etrack Incident = ET831697
Description:
Added some exception handling code to this maintenance pack.
--------------------------------------------------------------------------------
Etrack Incident = ET569949
Description:
This change enables the localization team to localize the XML files for VxUL
logs.
--------------------------------------------------------------------------------
Etrack Incident = ET831189
Description:
NetBackup shutdown would not terminate parent jobs (nbgenjob). A change
was made to the Policy Execution Manager to terminate all parent jobs
with a 50 status (EC_client_aborted).
Workaround:
To resolve this issue, manually terminate all nbgenjob processes.
--------------------------------------------------------------------------------
Etrack Incident = ET857404
Description:
Changes were added to correct possible null pointer issues.
--------------------------------------------------------------------------------
Etrack Incident = ET933508
Description:
Added the latest version of VxMS 4.3.018 in this maintenance
pack.
--------------------------------------------------------------------------------
Etrack Incident = ET851163
Associated Primary Etrack = ET849091
Description:
Changes have been added to ensure that send_mail() validates
all parameters it receives.
--------------------------------------------------------------------------------
Etrack Incident = ET866302 ET893368
Description:
The catalog cleanup process will not run to completion because it yields to
a catalog backup. If the cleanup process is long or if catalog backups are
frequent, the cleanup will not be able to delete expired images.
This maintenance pack contains a fix that enables catalog cleanup and
catalog backup to run in parallel. If a cleanup operation runs when a hot
catalog backup is in progress, it might delete images that were sent to
bpbkar earlier (in its image directive list), and cause the hot catalog
backup to finish with a partial success. This fix detects this situation
and returns the right error code to bpbkar.
The cleanup and catalog backup running in parallel is now the default
behavior. However, this can be disabled by creating a file called
"CLEANUP_WAIT_FOR_CATBKUP" in netbackup/db/config (for UNIX) and
\NetBackup\db\config (for Windows).
This fix also enables images to be expired and deleted using bpexpdate
even when a hot catalog backup is in progress.
Workaround:
To resolve this issue, disable hot catalog backups to allow cleanup to
run to completion.
--------------------------------------------------------------------------------
Etrack Incident = ET808281
Description:
bpdbm incorrectly sets the PFI_TYPE to 0. It must check if the copy being
deleted is a Persistent Frozen Image (PFI) or not and set the PFI_TYPE to 0
(only when the copy being deleted is a PFI).
--------------------------------------------------------------------------------
Etrack Incident = ET802974
Associated Primary Etrack = ET802966
Description:
The read_files_file queries would fail with a status of 249 because bpdbm
had not received the flist_complete yet.
--------------------------------------------------------------------------------
Etrack Incident = ET862545
Associated Primary Etrack = ET862538
Description:
Importing NetBackup 5.0 NDMP images would fail with an error code 42
from db_end().
--------------------------------------------------------------------------------
Etrack Incident = ET863352
Associated Primary Etrack = ET863351
Description:
The command "bperror -d <start date/time> -e <end date/time>" would not
give the correct result when daylight time saving was involved.
--------------------------------------------------------------------------------
Etrack Incident = ET542191
Description:
The success_fail_msg function in nb/media/bpbackupdb.c is for an offline
catalog backup on online catalog backups.
--------------------------------------------------------------------------------
Etrack Incident = ET863358
Associated Primary Etrack = ET848205
Description:
Internationalization (I18N): An NDMP restore with a Japanese directory
name no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET972452
Description:
Block Level Incremental (BLI) backups of DB2 databases
would fail on Linux.
--------------------------------------------------------------------------------
Etrack Incident = ET965811
Associated Primary Etrack = ET964501
Description:
Duplication (with multiplexing preserved) hangs for multiplexed TIR
images when using NetBackup 6.0 MP4.
Workaround:
To resolve this issue, do not preserve multiplexing when duplicating,
or do not use multiplexing. In addition, this may slow down performance.
--------------------------------------------------------------------------------
Etrack Incident = ET962923
Description:
NetBackup Service Layer (nbsl) no longer core dumps during install,
sched_bkup, and uninstall tests.
--------------------------------------------------------------------------------
Etrack Incident = ET965512
Description:
The VSS authorization tables were updated to include the new EMM interfaces.
--------------------------------------------------------------------------------
Etrack Incident = ET983962
Description:
An earlier change was made to keep track of open file
descriptors. Descriptors are pushed onto a stack as files
are opened and popped from the stack when they are closed.
For file pointers the fileno of the pointer is used. On
Linux, when a file pointer is closed, the pointer value is
reset by the operating system. This caused problems with
fileno and it is possible to cause segmentation violations.
The fix is to replace existing "close then pop" sequences
with a macro that does a "pop then close" sequence on Linux
and a "close then pop" on other platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET973985
Associated Primary Etrack = ET931484
Description:
Multiplexed SAP backups that were using (Standard) AES-128 Encryption
would fail with the following error: "ERR - backup failed 49 <client
did not start>".
--------------------------------------------------------------------------------
Etrack Incident = ET974342
Associated Primary Etrack = ET972826
Description:
A change has been made to ensure that a non-streamed, Windows open file
backup, runs the right schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET915448
Associated Primary Etrack = ET915442
Description:
Adding an operating system (OS) group to a Role in NBAC does not give the
Appropriate permissions to members of that OS group.
--------------------------------------------------------------------------------
Etrack Incident = ET928695 ET492823
Associated Primary Etrack = ET928687
Description:
In certain cases, PBX logs were not being pruned according to settings in
/etc/vx/VxICS/icsul.conf.
Additional Notes:
UNIX PBX runtime components are being updated in this maintenance pack along
with the NetBackup Server.
--------------------------------------------------------------------------------
Etrack Incident = ET990874
Associated Primary Etrack = ET974535
Description:
A timing problem was introduced in the last patch that could
cause multiplexed TIR backups to fail. This was due to a
backup ending as another was recording the TIR information.
--------------------------------------------------------------------------------
Etrack Incident = ET831965
Description:
NetBackup 6.0 disk staging storage unit’s high water mark (HWM) and low
water mark (LMW) are not changeable for an application cluster
(AppCluster) configuration. Currently, the AppCluster Configuration does
not have a NetBackup version so it is treated as a pre-NetBackup 6.0
storage unit, where the HWM is set to the previous behavior of 100 percent
and a LWM did not exist, therefore it is set to a default value of
80 percent. Both of these settings were new in NetBackup 6.0 and are not
configurable in pre-NetBackup 6.0 versions.
Workaround:
The AppCluster version number must be at the same version level as
the servers that make up the AppCluster. To resolve this issue, the
user should manually enter the NetBackup version number for the
AppCluster using the nbbemmcmd command. In addition, all of the
NetBackup servers in the AppCluster should be at the same, specified
version.
As an example, you would use the following command on the master
server to update the NetBackup version number for an AppCluster.
nbemmcmd -updatehost -machinename virtual_name -machinetype app_cluster
-netbackupversion 6.0
where virtual_name is the virtual name of the application (AppCluster).
--------------------------------------------------------------------------------
Etrack Incident = ET991906
Description:
Changes were made to ensure that a Vault operator could operate properly in
an NBAC environment.
--------------------------------------------------------------------------------
Etrack Incident = ET991647
Associated Primary Etrack = ET990896
Description:
After installing the BMR boot server to a Windows system with a
NetBackup 6.0 MP maintenance pack installed, and then performing a repair
on the pack to apply the BMR boot server binaries, the user should copy
the binaries to the correct directory location. If a NetBackup
installation was installed to a alternate location, the repair will not
correctly apply the patch binaries to the alternate location.
Workaround:
Again, to resolve this issue, copy the binaries, after performing the
"repair" option to the correct directory.
--------------------------------------------------------------------------------
Etrack Incident = ET992949
Description:
V_snprintf uses vsnprintf to implement a fix for uncommon strcat usage. On
the Windows platforms, vsnprintf did not guarantee a null terminated buffer.
Specifically, this was true if the data in the buffer exactly filled the
destination without leaving room for the null termination. In this case,
the buffer would not be null terminated and the function would crash when
V_strlcpy is called.
--------------------------------------------------------------------------------
Etrack Incident = ET990034
Description:
When an inline tape copy job with multiplexed protocol was resumed after a
checkpoint, the job was restarted instead of resumed.
--------------------------------------------------------------------------------
Etrack Incident = ET996117
Associated Primary Etrack = ET990855
Description:
Changes were made so that direct calls to the signal (),SBT implementation
no longer occurs.
--------------------------------------------------------------------------------
Etrack Incident = ET994229
Associated Primary Etrack = ET993986
Description:
A condition existed that caused failed jobs to exceed a configured number of
tries.
--------------------------------------------------------------------------------
Etrack Incident = ET992223
Description:
When checkpoint restart was enabled, and the "continue" flag was set in
the schedule, bptm terminated the copy when an error on that copy
occurred. When the copy terminates, for multiplexing, no more jobs were
scheduled for the multiplexed group. However, in rare cases there is a
timing window where jobs may have already been started but not yet
processed by bptm. In this case, incomplete fragment cleanup occurred
for the failed copy.
--------------------------------------------------------------------------------
Etrack Incident = ET997950
Associated Primary Etrack = ET984069
Description:
Oracle proxy copy incremental (CINC) backups are no longer running as full
Backups.
--------------------------------------------------------------------------------
Etrack Incident = ET992959
Associated Primary Etrack = ET993079
Description:
In some scenarios, the resource broker (RB) was orphaning resources that
were already marked to be released. This caused extra processing overhead
and communication overhead between nbrb and nbjm.
--------------------------------------------------------------------------------
Etrack Incident = ET999559
Description:
The pack installer will now log server system information such as EMMSERVER
(remote or local), media versus master server, and inactive cluster node.
--------------------------------------------------------------------------------
Etrack Incident = ET998728
Description:
The NetBackup version is now displayed in the nbemmcmd -listhosts -verbose
output.
--------------------------------------------------------------------------------
Etrack Incident = ET1000607
Description:
Symantec Code Repository Revision Tags was added to some files, to enable
better tracking.
--------------------------------------------------------------------------------
Etrack Incident = ET999754
Description:
If there were multiple copies of a backup, and a duplication was requested
for disk source copy 1 (or any disk copy other than the last), the
duplication might be started as a non-shared memory duplication. A shared
memory duplication is preferable for performance reasons.
--------------------------------------------------------------------------------
Etrack Incident = ET1001117
Description:
For Windows, added Sybase ASA service dependency to the NetBackup Resource
Broker.
--------------------------------------------------------------------------------
Etrack Incident = ET970398
Description:
In an NBAC setup, a volume configuration that uses the user interface wizard
would fail with an error 39.
--------------------------------------------------------------------------------
Etrack Incident = ET1008736
Associated Primary Etrack = ET966429
Description:
bpstart_notify would not get executed if the dos 8.3 pathname option was
turned off on NTFS partitions. After disabling dos 8.3 pathnames,
bpstart_notify would not run. bpbkar32.exe reports the bpstart_notify script
has started and ended, but the contents would not be executed.
--------------------------------------------------------------------------------
Etrack Incident = ET1005425
Description:
NetBackup pem would consistently terminate when an orphan job existed.
--------------------------------------------------------------------------------
Etrack Incident = ET1003200
Associated Primary Etrack = ET1003184
Description:
bprecover would crash during a recovery of a BMR database file that exceeded
2GB in size.
--------------------------------------------------------------------------------
Etrack Incident = ET990295
Description:
During multi-eject operations the vmchange program would return a
status code 0 (success) if another eject operation was in progress.
vmchange now returns a status code 223 (STATUS_ROBOT_BUSY) when another
eject operation is in progress. This problem primarily affected vault
eject operations.
--------------------------------------------------------------------------------
Etrack Incident = ET997925
Description:
Stream discovery would ignore the preprocess interval and use the default of
four hours. A change was made so that the preprocess interval is now passed
from Policy Execution Manager to the Job Manager and then to the parent job
(nbgenjob) on the command line using the -preprocessInterval option.
--------------------------------------------------------------------------------
Etrack Incident = ET1013849
Description:
The host list would be empty if a cluster node name was given instead of
virtual cluster name.
--------------------------------------------------------------------------------
Etrack Incident = ET1003608
Description:
Duplication to an FSE Nearstore storage unit failed if the
–stsdeletefiles process returned a status 1 (which is valid). A change
has been made that allows a duplicate to complete successfully if a
status 1 is encountered from -stsdeletefiles.
--------------------------------------------------------------------------------
Etrack Incident = ET1013509
Description:
A change was made to disable sorting on the Elapsed time and Active elapsed
time columns.
--------------------------------------------------------------------------------
Etrack Incident = ET1013882
Description:
Manual configuration of ACS libraries does not always record the library
serial number.
--------------------------------------------------------------------------------
Etrack Incident = ET1014147
Description:
In certain conditions a robotic daemon would become "UP" even though the
device monitor showed drives under AVR control.
--------------------------------------------------------------------------------
Etrack Incident = ET1010767
Associated Primary Etrack = ET990884
Description:
Immediate backups jobs would not initiate properly causing nbpem to return
the following statuses: msgsndd status = 0; send status 0; and bprd exit
status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET1016131
Description:
A change was made to implement support for Instant Recovery with Windows
FlashBackup policies.
--------------------------------------------------------------------------------
Etrack Incident = ET1014974
Associated Primary Etrack = ET892850
Description:
Backups written by 64-bit Linux servers were unreadable by non-64-bit Linux
servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1012144 ET1016961
Description:
Added support for a new Automated Cartridge System (ACS) vendor media and
drive type.
--------------------------------------------------------------------------------
Etrack Incident = ET1011704
Associated Primary Etrack = ET1015054
Description:
The robotic control daemon would not handle robots with more than
128 drives.
--------------------------------------------------------------------------------
Etrack Incident = ET1015612
Description:
Corrected an issue that would not allow you to write to disk and resulted
in an error code 84 (media write error).
--------------------------------------------------------------------------------
Etrack Incident = ET1018156 ET1016311
Associated Primary Etrack = ET1008244 ET1011211
Description:
The window checking routine would sometimes schedule jobs to run
multiple times in one window, or even skip a window.
--------------------------------------------------------------------------------
Etrack Incident = ET925285
Associated Primary Etrack = ET834682
Description:
Internationalization (I18N) issue: An issue existed that caused the content
of a notification e-mail to illegible.
--------------------------------------------------------------------------------
Etrack Incident = ET1017152
Associated Primary Etrack = ET1013059
Description:
If there are transient environmental hostname lookup issues, nbrb may
core dump near \"__nscd_get_map_ref\".
--------------------------------------------------------------------------------
Etrack Incident = ET1019073
Associated Primary Etrack = ET988955
Description:
TIR files that were than 2GB were not able to be read because the size was
stored in a 32-bit integer and the math used to turn that into a 64-bit
integer caused a large negative value to be stored on some platforms. This
maintenance pack contains a fix that contains explicit casts at appropriate
junctures. This issue was found on a Nearstore storage unit but would have
affected any disk storage unit if TIR was being used.
--------------------------------------------------------------------------------
Etrack Incident = ET1009036
Associated Primary Etrack = ET936732
Description:
A change was made to correct an nbpem core dump issue that occurred because
a null pointer was being passed to libc::strcmpstack.
--------------------------------------------------------------------------------
Etrack Incident = ET1020129
Associated Primary Etrack = ET1003895
Description:
It is possible for an NDMP restore to be successful and still produce a
status code 83 when media is write protected and spans media. The bptm
log will contain a messagesimilar to the following:
15:51:14.479 [6272.8404] <16> open_ndmp_device: cannot open ndmp device
nrst07a, error code 11 (NDMP_WRITE_PROTECT_ERR)
Workaround:
The restore completes successfully, so you can ignore the error status.
Or you can unmark the tape to make it write protected.
--------------------------------------------------------------------------------
Etrack Incident = ET1016884
Description:
Corrected the use of ejecting to the "any" cap (a function used by Vault)
when ejecting to ACS robotics. Also corrected use of -w option when
ejecting to ACS robotics from the command line.
--------------------------------------------------------------------------------
Etrack Incident = ET1015650
Description:
Lotus Notes user-directed backups were failing if the notes.ini path
specified through the user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1006573
Description:
A change was made so that the Managing -> Job Policies -> Details, user
backup & user archive policies are no longer shown twice.
--------------------------------------------------------------------------------
Etrack Incident = ET1012757
Description:
The server connection would fail while upgrading the Master
Server from NetBackup 60MP4 to NetBackup 60MP5 on a TRU64
system.
--------------------------------------------------------------------------------
Etrack Incident = ET1024918
Description:
Changes were added to resolve an intermittent pem core dump issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1021373
Description:
Corrected an issue that caused FlashBackup Windows single-file restores to
fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1022947 ET1062137
Associated Primary Etrack = ET984055
Description:
Status was being sent to the client after the stsdeletefiles
process was run. If that process took too long, the client
timed out. The backup was successful however the archive bits
on the client were not cleared, so the same files were backed
up in the next incremental, even though that was not necessary.
The result was that incremental backups were essentially running
as full backups.
--------------------------------------------------------------------------------
Etrack Incident = ET518074
Associated Primary Etrack = ET1009431
Description:
Upgraded the Sig Scheduler to 2.60.030 in this maintenance pack.
--------------------------------------------------------------------------------
Etrack Incident = ET1020081
Description:
A change was added so that when printDueJobs accesses the work list it will
lock the list to avoid potential issues with other threads trying to access
the work list.
--------------------------------------------------------------------------------
Etrack Incident = ET995592
Description:
Conversion of the policy include file-list entries failed resulting in
blank entries. A change was made to the nbproxy conversion code to use
language codeset setting of "utf8" for HP platforms, otherwise "UTF-8" for
all other platforms to prevent the conversion from returning an error saying
the input was invalid.
--------------------------------------------------------------------------------
Etrack Incident = ET1024066
Description:
Corrected a bpdm core dump that occurred with V_strverify on a Linux IA-64
System.
--------------------------------------------------------------------------------
Etrack Incident = ET1023729
Associated Primary Etrack = ET1027068
Description:
A storage unit update operation (from the NetBackup-Jave Administration
Console) will fail if the user is logged into the system using the node name
(not the virtual name).
Workaround:
To resolve this issue, use the virtual name.
--------------------------------------------------------------------------------
Etrack Incident = ET1027605
Associated Primary Etrack = ET1024835
Description:
ShadowImage snapshots failed on an AMS500 because the product
ID was set to DF6 and yet it was interpreted as a 9500.
Workaround:
To resolve this issue, set the Product ID to DF7 as the code
currently expects.
--------------------------------------------------------------------------------
Etrack Incident = ET1026332
Associated Primary Etrack = ET1018020
Description:
A restore attempt, using a duplicated copy of a standard backup image
that was duplicated using NDMP attached tape drive, would fail with exit
status 25 (cannot connect on socket). The failure occurred because bpdm
was started instead of bptm.
--------------------------------------------------------------------------------
Etrack Incident = ET1028083
Description:
The ltid reports that the user had configured more drives than they were
licensed for, when they were using multiple drive paths.
--------------------------------------------------------------------------------
Etrack Incident = ET1028405
Description:
A change was made to ensure that the Windows FlashBackup Policy Type is
disabled when the Advanced Client license key is not installed.
--------------------------------------------------------------------------------
Etrack Incident = ET1029379
Associated Primary Etrack = ET971543
Description:
For FlashBackup Windows incremental backups, the extents for named streams
associated with directories were not being examined and put in the bitmap.
--------------------------------------------------------------------------------
Etrack Incident = ET858201
Associated Primary Etrack = ET850921
Description:
A hot catalog backup with a large number of image catalog entries
can run out of memory.
Workaround:
For a temporary fix to the memory issue, contact Symantec Support and inquire
about Emergency Engineering Binaries (EEBs) that are available for this issue,
or perform an offline backup, or a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1028058
Description:
An incorrect group and ownership on a libdbjodbc9.so symbolic link file has
been corrected.
Additional Notes:
This change only affects HP-UX on RISC hardware.
--------------------------------------------------------------------------------
Etrack Incident = ET1026006
Description:
Under nb/idl/NBPolicyTypes.idl, many new fields were added for
NetBackup 6.5. This created problems for NOM 6.5 to support 6.0 MP5
masters. To avoid this issue, Symantec added the new fields in 6.0 MP5
as reserved fields which will resolve this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1028169
Description:
NetBackup will now be shutdown in runlevel 1 on Solaris systems.
--------------------------------------------------------------------------------
Etrack Incident = ET1032876
Associated Primary Etrack = ET963719
Description:
Changes were made to correct a Dr Watson error caused by bpbkar.
Bpbkar would cause a Dr Watson error on the client while backing up
encrypted files. The job consistently failed with an exit status 13
while backing up the following directory: E:\QuickBase\server\dbs\.
Files that were backed up were continuously changing. A third party
application would capture changes made from the end user (web user)
to a .delta file, the delta file was then written to the files in the
directory, "E:\QuickBase\server\dbs\", only after the user had closed
the web application. The .delta files were continuously changing, and
the changes made to the directory were approximately 10 gigabytes
an hour.
--------------------------------------------------------------------------------
Etrack Incident = ET1026986
Associated Primary Etrack = ET1005324
Description:
Cleaning jobs that were initiated because of a TapeAlert or frequency would
fail if they did not complete in six minutes.
--------------------------------------------------------------------------------
Etrack Incident = ET1036385
Associated Primary Etrack = ET1006915
Description:
A disk staging job that runs from one media server to another,
where the media server that is performing the write operation
is a UNIX system, will fail some of the jobs and/or hang.
Workaround:
To resolve this issue, create the following touch file on the
master server:
For UNIX:
/usr/openv/netbackup/NODTTSDUP
For Windows:
VERITAS\NetBackup\NODTTSDUP
--------------------------------------------------------------------------------
Etrack Incident = ET1035288
Description:
NetBackup 6.0 does not provide a way to perform device monitor queries for a
single media server. Users must sift through all servers' output for the
data needed. This maintenance pack adds the option -hostdevmon to the
vmoprcmd command line to provide a single server's device state.
--------------------------------------------------------------------------------
Etrack Incident = ET1040339
Associated Primary Etrack = ET1027138
Description:
Increased the drive ready timeout for TLD drives to 14 minutes to
incorporate a worst case scenario of 14 minutes for LTO drives in
an effort to remove bad media.
--------------------------------------------------------------------------------
Etrack Incident = ET1039797
Description:
When a full data directory is restored, the recovery was failing due to a
truncation of the database name.
--------------------------------------------------------------------------------
Etrack Incident = ET1038347
Associated Primary Etrack = ET996144
Description:
After a WOFB backup, bpbkar32 would clean up an active
FlashBackup- Windows snapshot - because PEM did not send the
SET SNAP_ID for snapshots that should be retained on the client.
Workaround:
To resolve this issue, reschedule the backups of the C: and D: drives so
that they start -and- complete at non-overlapping time periods
However, for some customers this is not practical because they may have
volumes that are in the range of 800GB ~ 1TB. In addition, some of their
servers may have more than one volume that needs to be protected using
Flashbackup
In this circumstance, Symantec suggests the customer sets the priority
of the C: drive backup to a higher value than the Flashbackup policy;
and then for the affected clients that are part of their Flashbackup
policies, using the Master Server Host Properties > Client Attributes >
Set Max jobs/client option and setting it to 1.
--------------------------------------------------------------------------------
Etrack Incident = ET1039117
Associated Primary Etrack = ET1038317
Description:
"bpmedia -movedb" starts bptm on the old server to move the media
database. If the old server and the new server are at NetBackup 6.0
(or post 6.0), then there is no need to start bptm. All the
operations can be done in bpmedia. This also helps the scenario
where one of the media server is offline or de-commissioned (and
all the steps for de-commissioning the media server are not followed).
--------------------------------------------------------------------------------
Etrack Incident = ET992572
Associated Primary Etrack = ET892420
Description:
The bppllist -allpolicies -U command would not return all policies.
In addition, when recreating the issue, an application fault
against bppllist was also found.
--------------------------------------------------------------------------------
Etrack Incident = ET1050190
Description:
Changes were made to correct the NetBackup 6.0 MP5 NetWare
build.
--------------------------------------------------------------------------------
Etrack Incident = ET1047982
Associated Primary Etrack = ET914734
Description:
The V_* functions would sometimes cause binaries with incorrect
signal handlers to core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET1050372
Associated Primary Etrack = ET1047809
Description:
Sybase 11.9.x backups no longer fail on HP-UX 11.00 after upgrading to
NetBackup 6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET1046813
Description:
Online catalog backup was failing with a status 50 when writing to a
password-protected DR path in an environment with NBAC installed.
Workaround:
To avoid this issue, store the DR file in a path which the running NetBackup
bpbdm process has write access to without changing credentials.
--------------------------------------------------------------------------------
Etrack Incident = ET1047911
Description:
A description of the new '-copy' option is missing from the bprestore
command line usage.
--------------------------------------------------------------------------------
Etrack Incident = ET1051657
Associated Primary Etrack = ET1045602
Description:
The NetBackup service layer (nbsl) would not start on a
master server using PA_RISC 1.1 architecture if nbsl was
compiled with PA_RISC 2.0.
--------------------------------------------------------------------------------
Etrack Incident = ET1050488
Description:
Corrected an issue that caused ltid to fault after it was started.
--------------------------------------------------------------------------------
Etrack Incident = ET1050393
Associated Primary Etrack = ET1036542
Description:
ACS robot pre-eject operations sometimes show volumes that are
NOT_IN_LIBRARY when they actually are. This is due to a buffer
length problem in the acsd robotic daemon. This primarily affects
Vault ejects to ACS robots.
--------------------------------------------------------------------------------
Etrack Incident = ET1052551
Description:
Intermittent issues were found when ejecting multiple CAP-fulls of
media with the latest ACSLS patch, PUT0701S.
--------------------------------------------------------------------------------
Etrack Incident = ET1051474
Description:
Some ACS_SDLT* media will not be mapped correctly to NetBackup media types
when specifying the mapping in vm.conf.
--------------------------------------------------------------------------------
Etrack Incident = ET1054463
Associated Primary Etrack = ET1039776
Description:
After changing the bp.conf SERVER entry from short name to FQDN
(or vice versa) and when performing a hot catalog backup with Vault,
the Vault job will fail with a status 294, even though the catalog
backup was successful.
Now, instead of using gethostname() results when vault performs a
validation, the client name (as configured in the policy) will be
used.
Workaround:
UNIX ONLY: In the imageDB directory, create a symbolic link between
FQDN and short names.
--------------------------------------------------------------------------------
Etrack Incident = ET1053444
Description:
A change was made that corrects a crash using bpplschedrep.
--------------------------------------------------------------------------------
Etrack Incident = ET1052430
Associated Primary Etrack = ET1032378
Description:
Added a fix to correct an nbjm crash in TAO_Transport::handle_input.
--------------------------------------------------------------------------------
Etrack Incident = ET1018993
Description:
On some SuSE 10 servers, when NetBackup asks the system if
it is the name listed as the EMM Server in the bp.conf file
at boot time, it incorrectly answers no. This correction asks
several times and usually the second attempt gives the correct
answer.
This causes a 55 second delay, with starting NetBackup daemons,
on SuSE 10 servers that are not MM Servers.
Workaround:
To resolve this issue, run the following start command after a
system has rebooted.
/usr/openv/netbackup/bin/goodies/netbackup
--------------------------------------------------------------------------------
Etrack Incident = ET1060972
Associated Primary Etrack = ET1038232
Description:
When Enterprise Vault performs backups to NetBackup using the
VxBSA file APIs, the backups can fail. Enterprise Vault posts
an event error entry saying Failed to send file (error 00000003:
System detected error, operation aborted.). Check the NetBackup
Activity Monitor.
Examination of the exten_client debug log shows that following
type of error being logged.
07:13:13.973 [9820.5196] <16> bsa_WriteFileList: ERR - filelist
file <C:\Program
Files\VERITAS\NetBackup\Logs\user_ops\dbext\logs\
vxbsa.1177038793.9820.5196.files.1> open() failed: Errno=24:
<Too many open files>
--------------------------------------------------------------------------------
Etrack Incident = ET1018093
Description:
An error occurred on a Windows setup that caused a failure to
occur when copying files.
--------------------------------------------------------------------------------
Etrack Incident = ET1047888
Associated Primary Etrack = ET1041180
Description:
The NDMP jobs' drives were sometimes pre-empted with a local
or incorrect drive path.
--------------------------------------------------------------------------------
Etrack Incident = ET1063773
Associated Primary Etrack = ET1063750
Description:
A crash in nbemm would occur if an inventory was attempted
while the database server was down. This would easily happen
if a site was performing a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1064798
Description:
A DB2 restore now has the ability to redirect a DB2 database
to a different owner from the original owner (both owners
being from the same group). A new backup of the source DB2
database is required so the correct group permission is on the
image to allow the alternate user to perform a restore to the
new instance, or database.
--------------------------------------------------------------------------------
Etrack Incident = ET1066935
Associated Primary Etrack = ET1062088
Description:
bpdbm crash can occur, during a recovery, if a damaged image
file exists prior to the recovery.
Workaround:
To avoid this issue, manually remove all damaged image files
before attempting a recovery.
--------------------------------------------------------------------------------
Etrack Incident = ET1066885
Description:
Listing storage unit groups were leaking memory. Changes were
added to resolve the memory leaks.
--------------------------------------------------------------------------------
Etrack Incident = ET1067176
Associated Primary Etrack = ET1001827
Description:
Jobs are not being cleaned from job database even after the
KEEP_JOBS_HOURS was run.
--------------------------------------------------------------------------------
Etrack Incident = ET1067996
Associated Primary Etrack = ET1058482
Description:
Changes were made to resolve memory leak issues in NBJM
and NBPEM.
--------------------------------------------------------------------------------
Etrack Incident = ET1070595
Description:
NOM no longer creates multiple NBProxy processes when there
is no job activity.
--------------------------------------------------------------------------------
Etrack Incident = ET1073038
Description:
An NetBackup EMM memory leak was detected in the xxxFetch()
implementation causing EMM to consume more memory over time.
Workaround:
To resolve this issue, restart the EMM process.
--------------------------------------------------------------------------------
Etrack Incident = ET1062791
Description:
Corrected an issue where the NetBackup Job Manager (NBJM) could
not be terminated and it had to be killed.
--------------------------------------------------------------------------------
Etrack Incident = ET1061742
Associated Primary Etrack = ET1058482
Description:
Added changes to correct a memory leak found in the NetBackup
policy execution manager (PEM).
--------------------------------------------------------------------------------
Etrack Incident = ET1066381
Associated Primary Etrack = ET1066374
Description:
The INCR frequency schedule would run multiple times within a
window with an incorrect snapid.
--------------------------------------------------------------------------------
Etrack Incident = ET1068635
Description:
The NetBackup service layer (NBSL) crashes on an HP-UX system.
Workaround:
To avoid this issue, default catch blocks were added to handle
all other exceptions in the Proxy client.
--------------------------------------------------------------------------------
Etrack Incident = ET1075834
Description:
An issue exited that caused jobs to remain queued when a
196 error should have occured.
--------------------------------------------------------------------------------
Etrack Incident = ET1076967
Associated Primary Etrack = ET1033590
Description:
A crash would sometimes occur in bpdbm when the cleanup process
was cleaning one of the images of a duplication, where the
duplication had failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1076060
Description:
The NetBackup PEM would terminate because of a timeout to the
nbproxy for getLastBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET1078998
Associated Primary Etrack = ET993531
Description:
The NetBackup Service Layer (NBSL) will not stay running and the
following error is produced.
Windows error 1063 - Windows SCM unable to start it as a service.
Workaround:
To avoid this issue, increase the service-registration timeout
from the Windows-registry.
--------------------------------------------------------------------------------
Etrack Incident = ET1078584
Description:
Running backups that have streaming enabled (and perform
incremental backups whose file list changes) may encountered
the following problem.
When stream discovery is done and some existing streams are shuffled
because new files are being added or existing streams being deleted,
the streams files are shuffled but the "lastbackup" time is saved for
the streams that remain. Therefore, when a new stream maps to a
preexisting stream with a date of zero (since there was no prior
backup) you want to avoid doing a query for "lastbackup" with that
stream number because it will return the "lastbackup" time for the
stream that was shuffled or deleted. If you avoid doing a query
for "lastbackup" when the date is zero you also keep the streams
from shuffling and the query returning a "lastbackup" time from a
different stream.
--------------------------------------------------------------------------------
Etrack Incident = ET1079359
Associated Primary Etrack = ET899380
Description:
A change was added that corrects a Status 805 error condition on
resubmitted, failed, multiple-data stream child jobs using snapshots.
--------------------------------------------------------------------------------
Etrack Incident = ET1079272
Associated Primary Etrack = ET1049382
Description:
AIX master servers were unable to restore Windows Flashbackup
images. This was because of a problem linking the VxMS libraries
in the AIX compile. A change has been added to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1083381
Description:
Policy Execution Manager would core dump when reading a policy because
of a configuration change event.
-------------------------------------------------------------------------------
Etrack Incident = ET1092076
Description:
NOM receives data from NBSL regarding changes in policy, storage units,
processes and services information, and so forth through events. When
the nbnos process is terminated, NBSL cannot deliver these events to NOM.
After restarting the nbnos process, the event delivery mechanism should
resume and NOM should continue to get data from NBSL, but it fails.
--------------------------------------------------------------------------------
Etrack Incident = ET1092060
Description:
When invoking the Device Configuration Wizard from the NetBackup-Java
Administration Console, a dialog box named "Device Configuration
Wizard - Initialization" shows the error "unknown error".
--------------------------------------------------------------------------------
Etrack Incident = ET1095578
Associated Primary Etrack = ET1094524
**Description:
If bpbrm/bptm terminates abnormally while executing multiple jobs and
another job is added to this multiplexed group by the Resource Broker, it is
possible that a data loss could occur.
================================================================================
============
Pack History
============
=========
NB_60_4_M
=========
--------------------------------------------------------------------------------
Etrack Incident = ET633295 ET617152 ET801824
Description:
Upgraded the version of Veritas Unified Logging (VxUL) to 1.3.7.2 to
enable users to recycle VxUL logs.
--------------------------------------------------------------------------------
Etrack Incident = ET633395
Description:
A change has been added that prevents bpduplicate from overwriting the
heap accounting information and causing the bpduplicate to crash by
copying a string into destination string that is too small.
--------------------------------------------------------------------------------
Etrack Incident = ET634272
Description:
Backup of multiple VxFS file systems using NetBackup's Advanced Clients
Frozen Image Backup method failed in close_vxfs_filesystem() of the
previous open VxFS checkpoint.
Workaround:
Backup one filesystem at a time for frozen image backups.
--------------------------------------------------------------------------------
Etrack Incident = ET638325
Description:
NetBackup log messages no longer show up in the /etc/security/password
file on AIX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET638699
Description:
The Policy Execution Manager (PEM) would crash while PEM was shutting down,
if it was shutting down at the same time a progress log was being updated.
--------------------------------------------------------------------------------
Etrack Incident = ET617254 ET617889 ET640121
Description:
Hot Catalog Backup would not backup images when IDIRSTRUCT equaled 1
because the code expected the master server had a second or later version
of the catalog image directory structure, for example, IDIRSTRUCT = 2.
In a UNIX cluster environment, the VAR_GLOBAL_PATH is linked to the shared
drive. The backup client (such as, bpbkar) does not follow symbolic links
currently and therefore the files inside the linked directory would not be
backed up in an online catalog backup.
Excessive bpdbm debug log entries were produced from a Hot Catalog Backup.
This fix ties the logging of libcatbackup debug messages to the following
setting.
BPDBM_VERBOSE setting.
Example of affected log message:
00:00:02.032 [8398] < 2> db_ImgUnlock: db_ImgUnlock(833d698) error(0)
--------------------------------------------------------------------------------
Etrack Incident = ET636334 ET636411 ET636414
Description:
The hot catalog backups would fail if the CRYPT_OPTION was set to REQUIRED
in bp.conf, where it could also be set through the GUI->Host Properties->
Clients->Encryption tab.
Workaround:
To avoid this issue, set CRYPT_OPTION to ALLOWED, which is the default.
--------------------------------------------------------------------------------
Etrack Incident = ET617892
Description:
For an imported catalog backup image, the command line instruction
"bprecover -r -nbdb" would not work because the parent image ID was
missing in imported ASA image header.
Workaround:
To avoid this issue, open the imported catalog image header file and
remove the PARENT_IMAGE_ID line so that the ASA and the catalog backup
image header files do not contain the field.
--------------------------------------------------------------------------------
Etrack Incident = ET642003
Associated Primary Etracks = ET841985
Description:
Changes were made to JobIMOMObject::CheckAndUpdateJobInfoData() in the
NetBackup Service Layer (NBSL) to correct a core dump situation.
--------------------------------------------------------------------------------
Etrack Incident = ET638313
Description:
The NetBackup Job Manager (NBJM) would crash when it received a message
from BPTM with a bad copy number.
--------------------------------------------------------------------------------
Etrack Incident = ET638320
Description:
The NetBackup Job Manager (NBJM) writes un-initialized data to the
JobParams file. When it reads the file again on a subsequent submission of
the job, it sometimes crashed because of un-initialized fields in the
JobParams file.
--------------------------------------------------------------------------------
Etrack Incident = ET638318
Description:
The NetBackup Policy Execution Manager (NBPEM) submitted a child job with
the option to inherit resources from the parent job after it released
resources from the parent job. The NBJM then crashed while trying to get
the resource from the parent job.
--------------------------------------------------------------------------------
Etrack Incident = ET633983 ET640407
Description:
Status 25 or 45 backup failures occurred under the following conditions:
- The master server is running NetBackup 6.0MP3.
- The media server is running NetBackup 5.x.
- The client is added to the NetBackup client database with the default
connect options.
Workaround:
To avoid this issue, explicitly set the connect_options value in the
client database to a value that is acceptable for a NetBackup 5.x version.
Do not use the default values:
admincmd/bpclient -update -client <client_name> -connect_options 0 0 2
--------------------------------------------------------------------------------
Etrack Incident = ET621772
Associated Primary Etracks = ET642018
Description:
Made changes to correct an NBSL core dump issue.
--------------------------------------------------------------------------------
Etrack Incident = ET642010
Description:
Changes were made to replace TreadSafeWrappers calls and to correct an
exception handling logic error in ServiceManagerCollector(). These issues
were causing a core dump issue in the NetBackup Service Layer (NBSL).
--------------------------------------------------------------------------------
Etrack Incident = ET628333
Description:
Mixing Dynamic Host Configuration Protocol (DHCP) clients and Dynamic Domain
Name Service (DNS) would cause potential data loss and security issues.
--------------------------------------------------------------------------------
Etrack Incident = ET627398
Description:
Hot catalog backup failed if the EMM server was installed on a remote
media server instead of on the master server, and BMR was installed on the
master server.
--------------------------------------------------------------------------------
Etrack Incident = ET579341
Description:
Added Encryption support to x64 NetBackup hosts.
--------------------------------------------------------------------------------
Etrack Incident = ET641058
Associated Primary Etracks = ET641055
Description:
A condition existed that caused NetBackup Service Layer (NBSL) to core
dump in HostSessionImpl::ping().
--------------------------------------------------------------------------------
Etrack Incident = ET638703
Associated Primary Etracks = ET638702
Description:
The NetBackup Policy Execution Manager (nbpem) process deadlocked while
doing bpexpdate -deassignempty -force >/dev/null.
--------------------------------------------------------------------------------
Etrack Incident = ET617887
Description:
An attempt to restore from a True Image Recovery (TIR) backup to tape after
the TIR data had been pruned from the catalog would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET630777
Associated Primary Etracks = ET630772
Description:
A change was made to the Policy Execution Manager to auto retry Vault jobs
on Status codes EC_vc_EjectFailed (287), EC_vc_EjectPartialSuccess (288),
and EC_vc_PartialSuccess (306). If one image failed to duplicate, Vault
would return a status 306. Also changed the parent job (nbgenjob) to
validate the image for a Vault job that returned an error status 306, 287,
or 288.
--------------------------------------------------------------------------------
Etrack Incident = ET618696
Description:
The following error would occur when trying to apply a patch when running
nbdb_upgrade:
Verifying the running version of NBDB ...
***** SQL error: Database server not found
Failed system call, '/usr/openv/db/bin//nbdb_unload -dbn NBDB -s /tmp'
Verification Failed.
When connecting to Sybase ASA using Open Database Connectivity (ODBC),
shared memory connections used space in /tmp by default. If there were
issues creating files in /tmp, the connection would fail. To resolve this
issue, the environment variable, ASTMP, is now set to /usr/openv/tmp.
--------------------------------------------------------------------------------
Etrack Incident = ET636795
Description:
Added the capability to do a step-wise downgrade of the NetBackup
Relational Database schema. This enables you to uninstall one or more
maintenance patches in the order in which they were applied.
--------------------------------------------------------------------------------
Etrack Incident = ET621857
Description:
Unable to create or modify disk staging storage units using the
NetBackup-Java Administration Console if a NetBackup 5.x system was
upgraded to NetBackup 6.0 or if a NetBackup 5.x license key was used
during a NetBackup 6.0 server installation.
This pack corrects this issue and enables you to create or modify disk
staging storage units using the NetBackup-Java Administration Console
if a NetBackup 5.x system is upgraded to NetBackup 6.0 using the 5.x
license or you could update to a NetBackup 6.0 license key.
--------------------------------------------------------------------------------
Etrack Incident = ET644627
Description:
On the active node, if the user has installed this pack on a secure
VCS Windows cluster environment that has a NetBackup server with EMM,
and are observing that NetBackup does not come online, the Enterprise
Media Manager (EMM) database schema did not update properly.
Workaround:
To avoid this issue, perform the following steps:
1. Take the NetBackup Server resource offline.
2. Freeze the NetBackup Service group.
3. Make sure that the Adaptive Server Anywhere – VERITAS_NB service is
started.
4. Execute the following command.
<install dir>/NetBackup/bin/nbdb_upgrade.exe –dbn NBDB
5. Execute the following command.
<install dir>/NetBackup/bin/admincmd/bpsyncinfo.exe
-add_paths NETBACKUP_RELATIONAL_DATABASE_FILES
6. Unfreeze the NetBackup Service group.
7. Bring NetBackup Server resource back online.
If you have experienced this issue on the install then you will also
experience it on the uninstall from the active node.
--------------------------------------------------------------------------------
Etrack Incident = ET636799
Description:
An error would occur when mixing FULL, Differential Incremental, and Vault
schedules in the "Hot_Catalog" backup policy. For example, if a Vault
schedule ran, followed by a Differential schedule (without any other jobs
running in between the two), the result would be the following:
JobID X = Catalog "Control" Job - Ends with Status 2
JobID X+1 = Differential Incremental Catalog Job - Ends with Status 227
--------------------------------------------------------------------------------
Etrack Incident = ET644077
Description:
In NetBackup 4.5, netbackup.dll was installed in the
C:\Program files\CommonFiles\VERITAS\Shared Directory. The NetBackup 6.0 GA
installer did not remove the old version of the file.
--------------------------------------------------------------------------------
Etrack Incident = ET618372
Description:
A change was made so that bpstsinfo correctly passes the
-filteronimagemodetype flag when used with the -remote flag.
--------------------------------------------------------------------------------
Etrack Incident = ET645645
Associated Primary Etracks = ET645697
Description:
A condition existed that caused the NetBackup resource Broker (nbrb) to
core dump under heavily loaded conditions. This problem had occurred
on AIX and HP-UX. There was lot of locking and unlocking involved in the
area where the resource broker (RB) sends the resources to the job manager.
RB was using reverse lock provided by ACE. Either RB was not using the
lock correctly or there was some issue in the ACE's implementation of
reverse lock which caused this core dump. To address the issue, the
lock/unlock logic was simplified.
--------------------------------------------------------------------------------
Etrack Incident = ET617893
Description:
TIR-enabled backups (including FlashBackup and NDMP) could fail in the
validation phase of the backup because of a miscalculated file size. This
patch provides earlier detection of the error and improved reporting on the
cause of the error.
--------------------------------------------------------------------------------
Etrack Incident = ET641172
Description:
Online catalog backups in configurations with cluster 5.x media servers
were creating a bpbackupdb process that looped infinitely.
--------------------------------------------------------------------------------
Etrack Incident = ET628709
Description:
A change was made so that EMM now verifies that all nodes in a cluster are
configured either as masters or media servers. EMM should not allow
media-master configurations among the cluster nodes.
--------------------------------------------------------------------------------
Etrack Incident = ET646623
Associated Primary Etracks = ET849324
Description:
The default method for NetBackup ODBC connections to the NetBackup database
(NBDB)/EMM database is to use shared memory followed by tcpip if shared
memory fails. This is controlled by the LINKS=shmem,tcpip{PORT=13785}
parameter in the database connection string.
On some platforms, there have been intermittent issues with shared memory
connections to the Sybase ASA database.
To work-around this issue, a new parameter has been aded to the vxdbms.conf
dfile to set the LINKS parameter in the connection string. To change this
parameter to only use tcpip connections, the following line
was added to vxdbms.conf:
VXDBMS_LINKS = tcpip{PORT=13785}
The vxdbms.conf file is located in /usr/openv/db/data (UNIX) and
InstallPath\VERITAS\NetBackupDB\data (Windows).
--------------------------------------------------------------------------------
Etrack Incident = ET641145
Description:
A problem existed that caused, in a few rare cases, f-list files in the
catstore subdirectories to have a mixed set of UNIX-style and Windows-style
path separators or even incorrect path entries. The code currently assumes
only one style of path separator was being used which caused problems for
hot catalog backup.
On Windows master servers this results in a partially successful
(status 1) hot catalog backup job.
On UNIX or Linux master servers this results in a failed (status 67)
hot catalog backup job on patch levels prior to MP4 and in a partially
successful (status 1) hot catalog backup job on patch levels MP4 and
later. (UNIX or Linux master servers are now consistent with Windows
master servers in the status for this condition.)
A message similar to the following should be seen in the bpbkar debug log
if this bug is encountered:
ERR - Unable to expand hot catalog backup directive: CATALOG_BACKUP
Workaround:
It is reasonably straightforward to manually identify, edit, and correct
the offending f-list files to avoid this problem.
--------------------------------------------------------------------------------
Etrack Incident = ET593700
Description:
Added a check so that any backups going to a file system export-enabled
Nearstore storage unit must have TIR enabled. This is because the
sts_delete_files process, which is part of the file system export backup,
requires the TIR data.
--------------------------------------------------------------------------------
Etrack Incident = ET632204
Description:
Media locations in ACS robotics were not updated properly after dismount
or during inventory when moving from standalone to robotic.
--------------------------------------------------------------------------------
Etrack Incident = ET644756 ET702144
Description:
In cases where a user authenticated against a non-root broker a failure to
load a credential from disk could occur. This would result in false
negative access checks for users leading to a Backup, Archive, and Restore
user interface rather than the NetBackup Administration console.
Workaround:
To avoid this issue, authenticate against the root broker on the master
server rather than another broker.
--------------------------------------------------------------------------------
Etrack Incident = ET630539
Description:
Corrected the vm.conf mapping of the ACS T10000 media types to HCART2.
--------------------------------------------------------------------------------
Etrack Incident = ET500024
Associated Primary Etracks = ET838966
Description:
Oracle backups no longer fail with a NetBackup status 227.
--------------------------------------------------------------------------------
Etrack Incident = ET646981
Description:
The NDMP agent caused a Dr. Watson error and a DUMP file when backing up
one volume.
This happens only on Windows and only when NDMP logging is enabled.
The problem is caused by "invalid" mtime/atime/ctime values sent by the
filer in the file history. This is not a normal situation.
Workaround:
To avoid this issue, turn NDMP logging off. This problem only occurs if
NDMP logging is enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET635017
Associated Primary Etracks = ET635016
Description:
Due to a memory management issue, the Volume Manager Daemon could
crash during certain media management operations.
--------------------------------------------------------------------------------
Etrack Incident = ET646985
Description:
NDMP backups failed with a status 84 when writing a TIR fragment.
The bptm log showed an error where the expected block position is one off.
This error occurred in the function write_data_tir().
Workaround:
To avoid this issue, add the following line to the file
<installdir>/netbackup/db/config/ndmp.cfg
NDMP_MOVER_CLIENT_DISABLE
This will have a minimal impact on backups. However it will cause a
significant performance impact to dup/verify/import when using
NDMP drives.
--------------------------------------------------------------------------------
Etrack Incident = ET640207
Description:
Allow the end user to specify pool numbers when creating a new volume pool.
A new option (-pnum) was added to the vmpool command to facilitate this.
The new usage is:
vmpool [-pnum <pool number>] -add <pool_name> "<description>" <host> <uid>
<gid>
The -pnum option must be specified before the -add option. The -pnum has
no effect when the -change option is specified.
--------------------------------------------------------------------------------
Etrack Incident = ET627870
Description:
The image will not be closed correctly and a data loss will occur during
duplication or staging where the following is true:
- The destination storage unit (STU) is a volume on a Nearstore with
version 7.2 of ONTAP.
- The disk storage unit option for 'enable block sharing' is set.
The first duplication or DSSU_POLICY backup to the Nearstore will complete
successfully, but subsequent operations using that image (such as, restore
and incremental backups) will not succeed.
--------------------------------------------------------------------------------
Etrack Incident = ET630303
Description:
If there was an error in a scheduled report, the report that caused the
error would not appear in the corresponding email.
--------------------------------------------------------------------------------
Etrack Incident = ET612141
Description:
The "File System Export" button on the Storage Unit dialog will be
available when NetBackup media server 6.0MP3 or higher version is
connected to a 7.2 ONTAP Nearstore or higher version as a
7.1 ONTAP Nearstore cannot export a file system.
--------------------------------------------------------------------------------
Etrack Incident = ET640456 ET632241 ET630393 ET632790
Associated Primary Etracks = ET640453
Description:
The nbpem showed scalability problems because of a recomputation of a
job’s due-time when not necessary. In addition, the internal queue
management was a single thread trying to handle multiple queues, which
caused long waits to process requests on some of the queues.
--------------------------------------------------------------------------------
Etrack Incident = ET641156
Description:
Hot catalog backup jobs fail with status 29 on Linux platforms.
In reality the backup did succeed, but the status is not being recorded
correctly resulting in the failed backup job.
Messages similar to the following will be seen in the admin debug log,
which show that the internal CLI used for the hot catalog backup job
did complete successfully:
<2> bpbackupdb: INITIATING: NetBackup 6.0
<2> logparams: -vxss -pjobid 672 -nodbpaths ...
<2> bpbackupdb: EXIT status = 0
But as message similar to these in the bpdbm debug log will indicate,
bpdbm thinks that the CLI operation failed:
<16> exec_vxss_backup: OVsystem(bpbackupdb -vxss -pjobid 672 -nodbpaths ...)
<16> exec_catalog_backup: exec_vxss_backup() failed (29)
--------------------------------------------------------------------------------
Etrack Incident = ET648677
Associated Primary Etracks = ET639374
Description:
The nbpem showed jobs were due but not queued.
--------------------------------------------------------------------------------
Etrack Incident = ET419599
Description:
NetBackup could get an error 130 when backing up VxFS file systems on AIX
platforms that were mounted under non-VxFS file systems that had Access
Control Lists (ACLs)on them.
--------------------------------------------------------------------------------
Etrack Incident = ET638703
Associated Primary Etracks = ET638702
Description:
Changes were made to keep nbpem from hanging or suspending on a
start_bpexpdate.
--------------------------------------------------------------------------------
Etrack Incident = ET649692 ET636127
Description:
Changes were incorporated to address slow start times on user backups.
--------------------------------------------------------------------------------
Etrack Incident = ET646015
Associated Primary Etracks = ET644582
Description:
Changes were made to fix an NBSL core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET641162 ET649541
Description:
Some new image data fields added in NetBackup 6.0 were missing in the
image index file and therefore an online catalog backup job could fail
if the image index feature was enabled for the master server. (The image
index feature was enabled by the "bpimage -create_image_list -client
<master-server-name>" command line utility.)
Running bpexpdate to change the expiration of a phase I imported image
could cause it to be deleted if the backup spans tapes AND the first
tape has not yet completed phase II of the import process.
Workaround:
To avoid this issue, do not enable the image index feature for the master
server (for example, do not run bpimage -create_image_list -client
<master-server-name>"). If the image index feature has already been
enabled for the master server, apply this patch or contact technical
support for assistance in disabling the image index feature for the
master server by removing the IMAGE_* files from the
/usr/openv/netbackup/db/images/<master-server-name> directory to disable
the image index feature for the master server.
--------------------------------------------------------------------------------
Etrack Incident = ET645336
Associated Primary Etracks = ET644082
Description:
The NBJM returns a normal status to NBPEM after the request to resubmit a
job failed.
--------------------------------------------------------------------------------
Etrack Incident = ET699915
Description:
When a backup failed and went from an incomplete to a failed state,
the child job would not run again. The Policy Execution Manager
would not run child jobs after a failure due to the Job Manager changing
the job type from a resume to a restart.
--------------------------------------------------------------------------------
Etrack Incident = ET699915
Description:
When a backup failed and went from incomplete to a failed state,
the child job would not run again.
--------------------------------------------------------------------------------
Etrack Incident = ET700003
Description:
A disk staging storage unit (DSSU) relocation job failed with a status 96,
in spite of available media.
--------------------------------------------------------------------------------
Etrack Incident = ET700745
Description:
Multiplexed restore jobs would possibly fail when the number of active
jobs reached the maximum of 32. When this error occurred, the bptm log
would have an entry similar to the following:
12:21:15.296 [3471] <16> bct_find_nonactive: FATAL - cannot find
non-active Backup Control Table entry
--------------------------------------------------------------------------------
Etrack Incident = ET626205
Description:
Added a call to Sybase's dbvalid command when NBDB or BMRDB databases
were started after a cold catalog backup, catalog recovery, or by
nbdb_admin -start. In addition, added an nbdb_admin -validate
option to call dbvalid at any time.
--------------------------------------------------------------------------------
Etrack Incident = ET700802
Description:
Prepare to restore failed on an AIX client if a volume group contained a
disk or disks that were multi-pathed.
--------------------------------------------------------------------------------
Etrack Incident = ET617061
Description:
Changes were made to ensure that NBSL no longer core dumps in
JobIMOMObject::CheckAndUpdateJobInfoData().
--------------------------------------------------------------------------------
Etrack Incident = ET644612
Description:
The VCS agent and configuration scripts were added for the following
platforms:
- HPIA64
- Linux64
Additional Notes:
To configure and run NetBackup as a VCS clustered application on
HPIA64 and Linux64 platforms, the base NetBackup must be installed along
with this patch. Without this patch, cluster configuration cannot be
performed on these platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET621934
Description:
When two or more DSSUs fill up, they are unable to independently reclaim
disk space. This could cause additional backup jobs to fail (error 129) to
these two unrelated DSSUs if space reclamation took too long.
--------------------------------------------------------------------------------
Etrack Incident = ET632300
Description:
The tpconfig manual user interface would not successfully add shared
robot/drives.
--------------------------------------------------------------------------------
Etrack Incident = ET627293 ET617051
Description:
The NetBackup Service Layer (NBSL) no longer core dumps when failing
over the cluster or if NBSL creates zombie threads.
--------------------------------------------------------------------------------
Etrack Incident = ET703004
Associated Primary Etracks = ET647573
Description:
If NetBackup Access Control (NBAC) was enabled prior to an upgrade
from 6.0GA (or 6.0MP1) to 6.0MP2, any non-Administrator, non-root
users in the NBU_Security Admin Group would lose their Access Control
privileges after the upgrade.
Workaround:
There are three workaround options available to you, that you can use
to avoid this issue:
First workaround option:
------------------------
Add the Non-admin user to the “Security Administrators” group in
VxAZ. To do this, perform the following steps:
1. Open the VxSS user interface (/opt/VRTSat/bin/runvssatgui.sh
2. Open the appropriate Authorization Server (top right button).
Connect to it using root.
3. Select the “Authorization Groups” button on the left panel.
4. Select the “Security Administrators” group in the tree.
5. Select the menu option Authorization > Authorization Groups >
Add Member.
6. Add the non-Admin user using the dialog that appears.
7. The non-Admin user should now have the necessary permission.
This should not circumvent any other security because this
user now has security privileges on VxAZ. If this is not
appropriate, contact Symantec Support for help in taking other
other measures, such as read-only access to Security
information.
Note: The non-Admin user SHOULD have permission without
taking this step.
Second workaround option:
------------------------
Uninstall the VxAZ installation and reinstall. Re-configure NBAC by
Running “bpnbaz –SetupSecurity <server>” and the appropriate
“bpnbaz –AllowAuthorization” commands.
Note: This option will cause any customization to be lost.
Third workaround option:
------------------------
Only use Admin users for Security Operations.
--------------------------------------------------------------------------------
Etrack Incident = ET621194
Description:
Hot Catalog Backups were not cleaning old logs in the
/usr/openv/netbackup/logs/user_ops/dbext/jobs and
/usr/openv/netbackup/logs/user_ops/dbext/logs folders.
--------------------------------------------------------------------------------
Etrack Incident = ET649659
Description:
A change has been made that makes it possible to correct old EMM database
entries in the device mappings file.
--------------------------------------------------------------------------------
Etrack Incident = ET703078
Associated Primary Etracks = ET648013
Description:
The Device auto-discovery wizard and acstest displayed only some of the
tape drives.
Additional Notes:
The problem only happened to a robot with a large number of drives.
--------------------------------------------------------------------------------
Etrack Incident = ET704572
Associated Primary Etracks = ET771586
** Description:
BPTM would overwrite a valid image if a backup was canceled during a
fragment break. This issue effected HP-UX and AIX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET703493
Description:
Changes were made to correct an error string collision that prevented the
L10N tools from working.
--------------------------------------------------------------------------------
Etrack Incident = ET704578
Description:
A change was added to correct an incorrect log message in the NetBackup
Tape Manager during a media expiration operation.
--------------------------------------------------------------------------------
Etrack Incident = ET648724 ET631626
Associated Primary Etracks = ET699996
Description:
Changes have been made for various problems that include named streams
associated with directories, and performance issues. In addition, these
changes fix a problem with an HP master that was not able to load the
restricted version of libxm.
--------------------------------------------------------------------------------
Etrack Incident = ET703215 ET771306
Description:
A change has been implemented that allows a local client install of a
Macintosh platform as well as other non-server platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET704832
Associated Primary Etracks = ET704822
Description:
When using virtual storage units and after a cluster application failover,
the active node was not being set correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET640484
Associated Primary Etracks = ET640481
Description:
When Endpoint_Selector tries to connect to profile_in_use () it is possible
that another thread closes the connection and resets profile_in_use.
--------------------------------------------------------------------------------
Etrack Incident = ET704957 ET704961 ET704980 ET704977
Description:
Changes have been made to correct issues relating to duplicate log message
numbers as well as a Linux loader problem.
--------------------------------------------------------------------------------
Etrack Incident = ET648557
Description:
Excessive resource usage no longer occurs during synthetic backups.
--------------------------------------------------------------------------------
Etrack Incident = ET704640 ET632758 ET763828
Associated Primary Etracks = ET610208 ET703589
Description:
If failure history was exceeded, it would recalculate jobs and continue to
retry; thus, not starting the children jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET609542
Description:
Certain VSP binaries were being laid down, even though VSP was not
installed on the machines. A check has been added to see if the VSP key
exists before laying down the binaries.
--------------------------------------------------------------------------------
Etrack Incident = ET538815 ET525797
Associated Primary Etracks = ET773470
Description:
The following two issues have been resolved:
- Systems that are up more than three days, no longer become unresponsive
on MSCS systems running NetBackup 6.0.
- Changes have been made to nbemm and nbrb processes to eliminate core
dumps when running with NBAC.
--------------------------------------------------------------------------------
Etrack Incident = ET766069
Description:
The NetBackup Job Manager (NBJM) had deallocated the resources of a
parent job because they were not consumed in time because the NetBackup
Policy Execution Manager (NBPEM) took longer to submit the first child.
This resulted in status 50 and status 801 errors. (Status 50 is a parent
job end error and status 801 is a children end error.)
--------------------------------------------------------------------------------
Etrack Incident = ET647920
Associated Primary Etracks = ET646600
Description:
A problem with the bpstsinfo -UPDATE command has been corrected and it
no longer causes a core dump when creating threads.
--------------------------------------------------------------------------------
Etrack Incident = ET764906 ET783411
Associated Primary Etracks = ET795340
Description:
Using the catalog archive process, files were not being removed from the
catstore directory. In addition, running the catalog archive process while
an online catalog backup was in process could have caused the catalog
backup to fail.
Additional Notes:
A new option, "-remove_dotf", has been added to the bpcatarc command. This
option eliminates the need to pipe the output from bpcatarc to bpcatrm to
remove .f files. If the new option is not used, you must continue to pipe
the output from bpcatarc to bpcatrm to remove .f files.
--------------------------------------------------------------------------------
Etrack Incident = ET768361
Associated Primary Etracks = ET768272
Description:
update_clients -Install_ADC no longer fails if the client HOME is something
other than /.
--------------------------------------------------------------------------------
Etrack Incident = ET633295 ET620589 ET767219 ET771458
Description:
Log Recycling enables NetBackup users to control the amount of disk space
that is used for logs. Prior to this change, the disk could fill with
log files.
Previous options available for controlling disk use was available via
either 1) user intervention with the vxlogmgr –d command, 2) a cron job
that called vxlogmgr -d, or 3) the ‘Keep Logs’ setting in the
NetBackup-Java Administration Console. These options were often inadequate
because they are time-based pruning, while VxUL log recycling is
continuous. Often, time-based pruning has been inadequate because the log
files filled the disk before the time-based pruning has chance to execute.
For more detailed information about Log Recycling, refer to the following
TechNote on the Symantec Support Web site.
http://entsupport.symantec.com/docs/279590
--------------------------------------------------------------------------------
Etrack Incident = ET766166
Description:
Block-level incremental (BLIB) backups were not working with the SAP
database agent.
--------------------------------------------------------------------------------
Etrack Incident = ET768448
Description:
Could not manually create NDMP or Media Manager storage units using the
NetBackup-Java Administration console. Using the bpstuadd –nodevhost
command would return the message, “Remote Media Servers not allowed for
NetBackup Server”.
--------------------------------------------------------------------------------
Etrack Incident = ET768441
Description:
vmphyinv no longer fails while changing media residence.
--------------------------------------------------------------------------------
Etrack Incident = ET769421
Description:
When selecting the preferred machine name for a cluster node, which will
be stored in the EMM database, ignore any REQUIRED_INTERFACE entries in
vm.conf or bp.conf (Registry on Windows).
Workaround:
To avoid this issue, remove the REQUIRED_INTERFACE entries from vm.conf and
bp.conf (Registry on Windows) before installing NetBackup 6.0. This only
pertains to cluster environments.
--------------------------------------------------------------------------------
Etrack Incident = ET768457
Description:
The nbemmcmd –deletehost command no longer fails if a storage unit is set
to, "Any Available Host".
--------------------------------------------------------------------------------
Etrack Incident = ET767144
Associated Primary Etracks = ET767131
Description:
No longer receive “Allocation Failed” errors when trying to connect to the
Activity Monitor. This occurred for all users using the Java Activity
Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET769437
Description:
A previous change was made to bpduplicate which could in some instances
result in creating a command string which bpdm could not parse. This
caused duplication to fail. This problem only existed for NearStore
storage units.
--------------------------------------------------------------------------------
Etrack Incident = ET649747
Associated Primary Etracks = ET648871
Description:
User-directed archives no longer delete files if warnings are generated
during the backup portion of the operation.
--------------------------------------------------------------------------------
Etrack Incident = ET770672
Description:
Storage unit changes could cause policy execution manager (PEM) to receive
unnecessary event notifications which would impact PEM performance.
--------------------------------------------------------------------------------
Etrack Incident = ET413513
Description:
For a policy that used wildcards (such as, *) in the file list and enabled
multiple data streams, NetBackup would not include any dot files (such as,
.rhosts) at that directory level in the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET769378
Description:
If the Hot Catalog Backup encountered an image catalog that was corrupted,
it would stop the hot catalog backup at that point and finish immediately
with an error code of 67 (file list read failed).
Now it continues past the corrupted image catalog, and backs up the rest of
the catalog, and finishes with a partial success status of 1.
Workaround:
To avoid this issue, fix the corruption in the image catalog, or take a
cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET767294
Associated Primary Etracks = ET763625
Description:
A new entry "MediaBlockSize" is provided in the nbsl.xml file to configure
fetch size. This option is useful for congested TCP/IP networks, where the
default fetch size of 1000 could fail.
--------------------------------------------------------------------------------
Etrack Incident = ET593547
Description:
The media_deassign_notify notification script, added to the
<install_path>/netbackup/bin/goodies directory, will execute if it is
moved into the <install_path>/netbackup/bin directory. This script is
executed every time a media is deassigned.
--------------------------------------------------------------------------------
Etrack Incident = ET774846 ET805115 ET818780 ET831242
Associated Primary Etracks = ET621934
Description:
On large file systems with a large number of images, disk staging would not
free space fast enough to prevent concurrent backups from failing with 129
errors.
Additional Notes:
When a backup to a disk storage unit with staging completes, the percent
used is compared with the high water mark. If the percent used is equal to
or greater than the high water mark, a bpdm process will be invoked which
will remove staged images until the low water mark is reached.
To disable this behavior, create the "IGNORE_HIGH_WATER_MARK" touch file in
the netbackup/bin directory.
--------------------------------------------------------------------------------
Etrack Incident = ET768910
Associated Primary Etracks = ET763868
Description:
update_clients did not recognize the invalid parameter Install_java. A
change to the parameter check has been made to catch this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET645067
Associated Primary Etracks = ET645064
Description:
Sun Cluster agent was reporting the following error when failing over the
resource group.
“Failed to retrieve the resource type handle: invalid resource type”
--------------------------------------------------------------------------------
Etrack Incident = ET770159
Description:
To determine the NetBackup server version, bpexpdate, bpdbm, and some other
components were using bpcd protocol. If one of the servers is down, it may
take a long time. In addition, the error handling of the failure was not
appropriate.
A change has been made to fetch the NetBackup server version from the EMM
database. This is a fast and more reliable way to determine NetBackup
server versions.
--------------------------------------------------------------------------------
Etrack Incident = ET770650
Description:
Changes have been made to correct various compile warnings.
--------------------------------------------------------------------------------
Etrack Incident = ET776562
Description:
The Problem’s Report shows, "SO_REUSEADDR failed, errno = 0, No error".
--------------------------------------------------------------------------------
Etrack Incident = ET772419
Description:
During normal termination using the bpdown command (on Windows), PEM's
JobScheduler::terminate was not called. This casued PEM to hang while
waiting for the Connection Factory to be closed and eventually lead to a
crash.
--------------------------------------------------------------------------------
Etrack Incident = ET777370
Associated Primary Etracks = ET649531
Description:
"bpstsinfo -UPDATE" no longer hangs on an exit.
--------------------------------------------------------------------------------
Etrack Incident = ET699903
Description:
Tapes that were not full were sometimes mistakenly ejected from standalone
drives after jobs completed.
--------------------------------------------------------------------------------
Etrack Incident = ET773419
Description:
Changes were added to fix warning errors when compiling jobmgr on
HP-UX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET772287
Description:
Changes were made to fix issues where synth backups were failing when going
to a File system, export-enabled, NearStore storage unit because they did
not "admit" to being TIR enabled even if the policy they are run out of is
TIR enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET768443
Description:
The user was able to change the pool type of the default none, NetBackup,
DataStore, and Catalog backup pools. This fixes the problem from the
server side.
--------------------------------------------------------------------------------
Etrack Incident = ET776697
Description:
Duplication failed if VERBOSE=5 was set and the destination storage unit
was a tape.
This problem was introduced by a previous fix in this pack and does not
exist in any released software.
Workaround:
To avoid this issue, do not set VERBOSE equal to 5.
--------------------------------------------------------------------------------
Etrack Incident = ET770273
Description:
Wildcard matching in image keywords does not work.
--------------------------------------------------------------------------------
Etrack Incident = ET777616
Description:
Failing synthetic backups would unintentionally perform a catalog cleanup
instead of deleting the single failed backup image.
--------------------------------------------------------------------------------
Etrack Incident = ET771311
Description:
Changes were made to resolve several small memory leaks that were possible
in infrequently encountered scenarios.
--------------------------------------------------------------------------------
Etrack Incident = ET773473
Description:
Added support for Linux, Red Hat 4, and SuSE 9, on Power PC from IBM.
Normal UNIX client support for these client types is also covered with
this maintenance pack.
File system support is limited to EXT2, EXT3, ReiserFS on SuSE SLES 9, and
NFS. Files that are greater than 2 Gigabytes are supported. Local user
interfaces are available through the command line or the menu interface
(using the bp command). Remote access is the same as all other UNIX
clients.
For the client binaries to be installed from the UNIX patch you must first
create the following directories:
/usr/openv/netbackup/client/Linux/IBMpSeriesRedHat2.6
/usr/openv/netbackup/client/Linux/IBMpSeriesSuSE2.6
The binaries for the Encryption licensed feature are available through
the Encryption patch. For the Encryption binaries to be installed from
the UNIX Encryption patch you must first create the following directories:
/usr/openv/netbackup/crypt/Linux/IBMpSeriesRedHat2.6
/usr/openv/netbackup/crypt/Linux/IBMpSeriesSuSE2.6
For additional information about Encryption, refer to the NetBackup
Encryption readme.
--------------------------------------------------------------------------------
Etrack Incident = ET579398 ET775062
Associated Primary Etracks = ET701785 ET701785
Description:
Synthetic Backup no longer fails when a component image spans tape volumes.
--------------------------------------------------------------------------------
Etrack Incident = ET774704
Associated Primary Etracks = ET774649
Description:
Restores of backups for clients that had FlashBackup policies (either alone
or in combination with other policy types) were slow to become active and
mount tapes.
--------------------------------------------------------------------------------
Etrack Incident = ET770151
Description:
The “bpexpdate –recalculate –backupid –ret” command correctly changed the
expiry date of an image, but not the image retention level.
--------------------------------------------------------------------------------
Etrack Incident = ET772390
Description:
In some scenarios, the NetBackup Resource Broker (NBRB) was orphaning
resources while waiting for tape span and then deallocating those
resources. This caused an erroneous job termination.
--------------------------------------------------------------------------------
Etrack Incident = ET775684
Description:
Vaulting (bpduplicate) failed with the second image in a batch job with a
“resource request failed” message.
Workaround:
This problem may occur if images are on media with an ID of less than six
characters. To avoid this issue, use six-character media ID’s.
--------------------------------------------------------------------------------
Etrack Incident = ET775681
Description:
Increased the mount timeout for TLH drives to accommodate drive cleaning by
the library between mounts.
--------------------------------------------------------------------------------
Etrack Incident = ET775677
Description:
Changes have been made to enable NetBackup to control TLH robotics with up
to 512 drives.
--------------------------------------------------------------------------------
Etrack Incident = ET775429
Description:
Changes were made to correct error message for invalid media type mapping.
--------------------------------------------------------------------------------
Etrack Incident = ET775427
Description:
Changes were added to correct syslog messages to print appropriate
information.
--------------------------------------------------------------------------------
Etrack Incident = ET775428
Description:
Resolved an issue with the TLD inventory with the empty_map option set by
correcting the algorithm so that if only the last slot is open, it can
still be used without failing.
--------------------------------------------------------------------------------
Etrack Incident = ET768449
Description:
Resolved an issue that would not allow you to delete a machine of
APP_CLUSTER type.
--------------------------------------------------------------------------------
Etrack Incident = ET776667
Description:
Changes were made to correct various compiler warnings.
--------------------------------------------------------------------------------
Etrack Incident = ET778780
Description:
A bad configuration could lead to thousands of monitor-provider allocations
in the database. The resource broker (RB), on startup, may consume a lot of
memory reading these database entries and may even dump core. Now the RB
removes all of the monitor-provider allocations at startup.
--------------------------------------------------------------------------------
Etrack Incident = ET775425
Description:
When downing a drive using the vmoprcmd -downbyname or vmoprcmd –down
comands, the drive's designated scan path was sometimes set back to "UP".
--------------------------------------------------------------------------------
Etrack Incident = ET775435
Description:
When a pre-NetBackup 6.0 media server was unassigned a drive that was
Scanned by a NetBackup 6.0 media server, it was not clearing the
RVSN/EVSN and Ready fields.
--------------------------------------------------------------------------------
Etrack Incident = ET780083
Associated Primary Etracks = ET780079
Description:
When changing a drive from not shared to shared using the wizard, and
the new host (the host that will now make it shared) was running
NetBackup 5.x, the wizard would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET777630
Description:
Back-level media servers are not able to DA-release the drives because
re-registration timers block the request.
--------------------------------------------------------------------------------
Etrack Incident = ET775426
Description:
The robotic test utility (robtest) would core dump and could not perform
an unload if multiple paths exist.
--------------------------------------------------------------------------------
Etrack Incident = ET770182
Description:
Long delays occurred when starting immediate backups because the Policy
Execution Manager calls getNextJob() when processing immediate requests.
Removed call to getNextJob() for immediate requests when searching for the
backup. It makes the time to find the job n squared instead of n, where n
is the number of entries in the worklist.
--------------------------------------------------------------------------------
Etrack Incident = ET770337
Description:
The Policy Execution Manager was using the wrong lock to extract entries
from the job queue when processing user, archive, or manual backup
requests. This issue has been resolved and will no longer result in
data corruption, a crash, or lost data.
--------------------------------------------------------------------------------
Etrack Incident = ET772631
Description:
The Job Manager CPU utilization was high while most of the user backup jobs
were queued. The Job Manager was busy sending WAITING messages to the
progress logs for the queued, user backup jobs. The WAITING message is sent
every 30 seconds.
To resolve this issue, Job Manager was changed to increase the interval
between these WAITING messages sent to the progress logs.
--------------------------------------------------------------------------------
Etrack Incident = ET770167
Description:
Because of changes in the startup process with NetBackup 6.0 MP4, the
Policy Execution Manager can not start jobs until the build worklist is
complete. This process can take a long time.
To compensate for this, the build worklist has been changed to not query
the last backup or compute the due times so that the list can be built very
quickly. After the list has been built it will then synchronize with the
NetBackup Job Manager so the jobs can be started, followed by the
calculation of all of the jobs due times.
By dividing the process of how the worklist is built into two steps, jobs
can be started much sooner.
--------------------------------------------------------------------------------
Etrack Incident = ET770655
Description:
User backup requests to the Policy Execution Manager appeared to be waiting
a long time for the worklist lock. A change was made to the Policy
Execution Manager to skip the due-time calculation for user, archive, or
immediate requests.
--------------------------------------------------------------------------------
Etrack Incident = ET781527
Associated Primary Etracks = ET703273
Description:
Changed the Policy Execution Manager to call the Job Manager restartJob
Interface which looks at restartSelection setting instead of
resourceSelection. When a parent job is resumed, it frees the resource.
Job Manager failed the job if it looked at the resourceSelection (that is
set to inherit parent resource) but would work if it used restartSelection
(that is, set to use standard resource).
--------------------------------------------------------------------------------
Etrack Incident = ET777064
Description:
The naming convention used by the Sun Solaris Leadville HBA driver has
changed.
--------------------------------------------------------------------------------
Etrack Incident = ET782623
Description:
A change was made to correct an uninitialized local variable as well as
remove an unused local variable within the code.
--------------------------------------------------------------------------------
Etrack Incident = ET778981
Description:
Changes were made to resolve NBPEM memory leaks.
--------------------------------------------------------------------------------
Etrack Incident = ET779116
Description:
NetBackup services NBPEM and NBJM would core dump if an attempt was made to
Start them on a media server.
--------------------------------------------------------------------------------
Etrack Incident = ET781175
Associated Primary Etracks = ET781185
Description:
The user-configurable, MEDIA_UNMOUNT_DELAY timeout, was not being honored
for database agents.
--------------------------------------------------------------------------------
Etrack Incident = ET773564
Description:
A problem with the command -delete_server_from_app_cluster, made it
impossible to unconfigure an application cluster and reconfigure it with
the correct name.
--------------------------------------------------------------------------------
Etrack Incident = ET778908
Description:
Made multiple Coverity fixes for PEM.
--------------------------------------------------------------------------------
Etrack Incident = ET771373
Description:
Fixed the potential access of pointers that were not initialized.
--------------------------------------------------------------------------------
Etrack Incident = ET784803 ET784808 ET784805 ET784804 ET784810 ET792742 ET784809 ET802855
Description:
Buffer overflow areas have been identified and corrected in daemons running
on Veritas NetBackup master, media, and client servers. Successful access
to a vulnerable Veritas NetBackup server and the ability to successfully
execute arbitrary code could potentially result in unauthorized access with
elevated privilege on a system.
--------------------------------------------------------------------------------
Etrack Incident = ET775510
Description:
A restore of a large backup image would potentially fail if a large number
of data buffers (for example, 1024) was configured. The number of data
buffers is configured on UNIX systems in
/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS, and for Windows
systems in <install_path>\NetBackup\db\config\NUMBER_DATA_BUFFERS.
Workaround:
To avoid this problem, do one of the following:
- Set the number of data buffers to a smaller value (For example, 128).
- Create the following file:
UNIX: /usr/openv/netbackup/db/config/MIN_RESTORE_SKIP
Windows: <install_path>\NetBackup\db\config\MIN_RESTORE_SKIP
Then enter a number greater than the following:
(size_data_buffers) * (number_data_buffers) / 512
--------------------------------------------------------------------------------
Etrack Incident = ET775517
Description:
Bpbrm would occasionally terminate abnormally without core on a very busy
media server, which would cause the backup job to hang. This could only
happen on UNIX media servers, and not on Windows media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET775513
Description:
Individual file restores would potentially fail in the following
circumstance:
- The original backup was done using Inline Copy, and at least one of the
copies was disk, and the backup was multiplexed.
- The backup had multiple fragments for the disk copy.
- A duplicate from a disk copy to tape was performed, and the source and
destination storage units are on the same machine.
- The restore is from the duplicated disk copy.
Workaround:
To avoid this issue, create the following file on the master server:
For UNIX Systems:
/usr/openv/netbackup/NOSHMDUP
For Windows Systems:
<installed_path>\NetBackup\NOSHMDUP
--------------------------------------------------------------------------------
Etrack Incident = ET771553
Description:
The NBPEM uses write locks instead of read/write locks to enhance
performance.
--------------------------------------------------------------------------------
Etrack Incident = ET770349
Description:
bprd and nbpem now exchange user backup startup parameters through the
use of a file named with a GUID instead of a process PID, eliminating the
possibility that the same filename will be used twice.
--------------------------------------------------------------------------------
Etrack Incident = ET774791
Description:
A missing log message was added for when FFREADtries are exceeded.
--------------------------------------------------------------------------------
Etrack Incident = ET775512
Description:
Verify, duplication, or import operations are not able to browse
images from the Windows NetBackup Remote Administration Client.
Workaround:
To avoid this issue, run the following command on the Remote Administration
Client:
<install_path>\volmgr\bin\vmglob -set_gdbhost <master server>
--------------------------------------------------------------------------------
Etrack Incident = ET781618
Associated Primary Etracks = ET771576
Description:
Destination media may incorrectly get unmounted and a new media chosen when
duplicating multiple images. This can occur when duplicating a mixture of
multiplexed and non-multiplexed backups.
--------------------------------------------------------------------------------
Etrack Incident = ET775591
Associated Primary Etracks = ET789993
Description:
The image file created for the parent job, while multi-streaming, was not
being validated. This would later cause status 200 failures.
--------------------------------------------------------------------------------
Etrack Incident = ET785921
Associated Primary Etracks = ET783614
Description:
Duplication was failing after successfully duplicating the first image.
This occurred because the server name in bp.conf file was different from
what was in the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET778008
Description:
When you run NBJM, built with a Windows debug build, it gets an assertion
failure because of variables that were not initialized.
--------------------------------------------------------------------------------
Etrack Incident = ET775486
Associated Primary Etracks = ET771394
Description:
LTID could not connect to the NBRB when VxSS was enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET786811
Description:
If a job is queued awaiting resources, the message displaying the reason
for queuing is not displayed in the job details in the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET775422
Description:
Linux servers, with SAN attached tape drives, can have trouble using drives
that are in use at the time of a service start.
--------------------------------------------------------------------------------
Etrack Incident = ET787735
Description:
Avoid closing an NDMP tape device, so that the filer does not unreserve
the drive.
--------------------------------------------------------------------------------
Etrack Incident = ET775430
Description:
Synthetic backups no longer cause bptm core dumps when all drives are down.
--------------------------------------------------------------------------------
Etrack Incident = ET775431
Description:
Occasionally, BPTM would not handle canceled jobs during NBJM waits.
--------------------------------------------------------------------------------
Etrack Incident = ET775433
Description:
TapeAlert data is no longer ignored after the media is unloaded.
--------------------------------------------------------------------------------
Etrack Incident = ET643875
Description:
Unloads would fail on NDMP drives if the raw open operation failed.
--------------------------------------------------------------------------------
Etrack Incident = ET770157
Associated Primary Etracks = ET794596
Description:
The cleanup process intermittently failed to remove image header files on
busy systems.
Workaround:
To avoid this issue, ignore the reported error and let a subsequent cleanup
process delete the file.
--------------------------------------------------------------------------------
Etrack Incident = ET783401
Description:
Restarting the device daemons on pre-NetBackup 6.0 media servers after a
device configuration change would inadvertently unregister the host with
the device allocator (DA).
--------------------------------------------------------------------------------
Etrack Incident = ET781676 ET781719
Description:
Made multiple Coverity fixes for the NetBackup Job Manager (NBJM).
--------------------------------------------------------------------------------
Etrack Incident = ET771614
Description:
Improved the nbpem performance when reading the failure history database.
--------------------------------------------------------------------------------
Etrack Incident = ET777662
Description:
Trying to change a configured device to partially configured on a
pre-6.0 media server in the device configuration wizard, may sometimes
cause devices to become "DISABLED" for a NetBackup 5.x media server.
For NetBackup 5.x media servers, there is no concept of "DISABLED".
--------------------------------------------------------------------------------
Etrack Incident = ET776871
Description:
Duplications would fail with status codes of 114 or 800. This occurred
when media with mixed multiplexed and non-multiplexed backups were
duplicated, and when using multiplexed duplication.
--------------------------------------------------------------------------------
Etrack Incident = ET778815
Description:
The nbpem restarts it’s timer for the next housekeeping activity only after
the previous housekeeping activity has completed
--------------------------------------------------------------------------------
Etrack Incident = ET772500
Description:
Changes were added to this pack to eliminate crashes and core dumps during
nbpem shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET781548
Description:
When moving a host to new hardware using nbemmcmd, not all of the database
entries were updated with the new hostname. A change was added that
verifies that all of the necessary database fields have been updated
correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET772510
Description:
Changes were made that improve performance when writing error history by
caching the Veritas Unified Logging (VxUL) configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET783370
Description:
The NetBackup Resource Broker (NBRB) no longer crashes while running
bplabel.
--------------------------------------------------------------------------------
Etrack Incident = ET787072
Description:
An object was being deleted incorrectly for an obscure end case that is
normally not encountered.
--------------------------------------------------------------------------------
Etrack Incident = ET784575
Associated Primary Etracks = ET624633
Description:
The bpbackup command, when used with the -L and -i options, did not
provide useful information in the progress log.
--------------------------------------------------------------------------------
Etrack Incident = ET790023
Associated Primary Etracks = ET782774
Description:
You can now backup NetBackup media servers using Storage Area Network (SAN)
media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET777633
Associated Primary Etracks = ET777631
Description:
In the Java user interface, the Activity Monitor’s Detailed Status did not
increment the percent complete. It jumped from 0% to 100% at the end of
the job.
--------------------------------------------------------------------------------
Etrack Incident = ET772618
Description:
Generic jobs would not start when a large number of them were initiated in
quick succession on Windows.
NetBackup Job Manager (NBJM) was changed to start an extra nbproxy on
startup that is used by all nbgenjob's. The only exception is that a
catalog backup job will start its own nbproxy because a cancel is
implemented by shutting down the nbproxy.
--------------------------------------------------------------------------------
Etrack Incident = ET790041
Associated Primary Etracks = ET790038
Description:
Generic job exited after a few retries when the Policy Execution Manager
did not respond to pings. The parent job would exit with a status 50 and
the children exits with a status 801.
To resolve this issue, a change was made to genericjob that forces it to
ping forever until the Policy Execution Manager responds or is restarted,
or an OBJECT_NOT_EXIST exception is returned.
--------------------------------------------------------------------------------
Etrack Incident = ET786951
Associated Primary Etracks = ET781181
Description:
The Policy Execution Manager would core dump on a resume due to not copying
last schedule used when the job was being deleted.
--------------------------------------------------------------------------------
Etrack Incident = ET786406
Associated Primary Etracks = ET784164
Description:
A problem existed in the "Media and Device Management > Media" section of
the Windows Administration Console and the Java user Interface. Whenever a
tape holds more than 2 Terabytes of data on it, the Kbytes number in the
"Kilobytes" column displays as a -ve number.
--------------------------------------------------------------------------------
Etrack Incident = ET789535
Description:
When the default robotic volume group is selected in "Change Vault" dialog,
it is not selecting the correct volume group.
--------------------------------------------------------------------------------
Etrack Incident = ET785497
Description:
Removed the new ORB created during a ServiceManager collection process.
--------------------------------------------------------------------------------
Etrack Incident = ET791064
Description:
Using long hostnames for NDMP hosts no longer results in the credentials
being added incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET787049
Description:
The install was starting the ASA database service on non-EMM media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET787586 ET786594 ET790483
Description:
The NetBackup service layer (NBSL) would crash when connected from a
user interface or NetBackup Operations Manager (NOM).
--------------------------------------------------------------------------------
Etrack Incident = ET789695
Description:
Adding a cleaning tape from the user interface would result in a “bad
Cleanings” remaining number.
--------------------------------------------------------------------------------
Etrack Incident = ET772403
Description:
Formatting of jobid in log files has been normalized to "jobid=" in all
reasonable cases. This format agrees with the use of context as well.
In some places where stringstreams were used to format jobid, an
.imbue(std::locale("C")) was added to prevent localized formatting of large
integers. For more information about this change, refer to the following
TechNote on the Symantec Support Web site.
http://entsupport.symantec.com/docs/284795
--------------------------------------------------------------------------------
Etrack Incident = ET787963
Description:
The nbpem no longer leaks memory with each CORBA connection.
--------------------------------------------------------------------------------
Etrack Incident = ET776946
Description:
The nbpem no longer uses memory that is not initialized that could result
in a random error message.
--------------------------------------------------------------------------------
Etrack Incident = ET777867
Description:
Changed the Policy Execution Manager objects to initialize all fields in
constructor.
--------------------------------------------------------------------------------
Etrack Incident = ET784609
Associated Primary Etracks = ET782395
Description:
When time falls back because daylight savings time ends, jobs may run
1 hour late.
--------------------------------------------------------------------------------
Etrack Incident = ET790574
Description:
When attempting to create a Vault profile on the Java user interface, the
Make Primary Checkbox was not functioning properly. If this was used on a
storage unit in the Duplication Rule Dialog, it would not be written
correctly in vault.xml file.
--------------------------------------------------------------------------------
Etrack Incident = ET791514
Description:
Changes were added to correct the AUTO_UPDATE_ROBOT feature for Windows.
--------------------------------------------------------------------------------
Etrack Incident = ET789971
Associated Primary Etracks = ET785700
Description:
Robot inventory reports a confusing error when it is run on a robot that
contains media that is marked "conflicted" in the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET788825
Associated Primary Etracks = ET647204
Description:
The tpautoconf -replace_drive command no longer corrupts the drive's
inquiry string in the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET787033
Description:
The nbpem no longer fails or crashes when processing Share Point backups.
--------------------------------------------------------------------------------
Etrack Incident = ET792594
Associated Primary Etracks = ET646858
Description:
The NetBackup Resource Broker (NBRB), under heavily loaded conditions with
many media servers, would take about 30 seconds to give resources to the
job.
To fix the problem the following improvements have been made:
- Improved drive cache in RB (RB no longer links with emmlib).
- If the maxmpx in the request is 1, do not try to join it to any group.
- Delete all MonitorProvider allocations using a single SQL statement.
- Prioritize the requests based on the birth time too.
- Some miscellaneous improvements.
--------------------------------------------------------------------------------
Etrack Incident = ET644674 ET427279
Associated Primary Etracks = ET644671
Description:
The cluster_config script was failing when a fully qualified domain name
was used as the virtual name. In addition, deleting and then re-adding
robot daemons using cluster_config -r caused the cluster monitoring to
fail.
--------------------------------------------------------------------------------
Etrack Incident = ET777893
Description:
Changed the Policy Execution Manager to not exit the application
if the restart request could not be satisfied because of a malloc failure.
--------------------------------------------------------------------------------
Etrack Incident = ET792609
Associated Primary Etracks = ET764790
Description:
The tpconfig command would fail with the following error when the range
of the CLIENT_PORT_WINDOW parameter was set between 1025 to 5000, for
example.
"EMM interface initialization failed, status = 77"
--------------------------------------------------------------------------------
Etrack Incident = ET786617 ET631392
Description:
bpsturep and bpstuadd did not have Nearstore version checking that was
present in the user interfaces. This brings them to the same level.
It is not permissible to configure an SOI storage unit on a ONTAP 7.1.x
Nearstore. (Refer to TechNote 282929 on the Symantec Support Web site for a
more detailed explanation.) It is also not permissible to have a Nearstore
staging storage unit that has any type of SIS (SOI or FSE) enabled for
ONTAP 7.2 and higher Nearstores.
--------------------------------------------------------------------------------
Etrack Incident = ET765029
Associated Primary Etracks = ET763562
Description:
The hot catalog backup feature did not work with images that had been
archived using the catalog archiving feature. Prior to this fix, if the
catalog archiving feature had been used to archive images, the backup job
generated from a hot catalog backup policy would fail with a status 67
on a UNIX or Linux master server and with a status 1 (partially
successful) on a Windows master server.
--------------------------------------------------------------------------------
Etrack Incident = ET791570
Description:
Added a call to nbproxyreq in a NetBackup script in case the nbproxy
commands are not shutting down gracefully.
--------------------------------------------------------------------------------
Etrack Incident = ET770171
Description:
Changes were made to improve performance on multiple data streams by not
generating streams again if stream discovery did not change the stream
content.
--------------------------------------------------------------------------------
Etrack Incident = ET597353
Description:
Changes have been made to limit support of VxFS File Change Log to FCLv3
during incremental backups.
--------------------------------------------------------------------------------
Etrack Incident = ET785820
Description:
bpclntcmd no longer fails on HP-UX systems with the following error.
"_main() not called"
--------------------------------------------------------------------------------
Etrack Incident = ET789170
Associated Primary Etracks = ET702600
Description:
Vault duplication jobs were forcing a dismount/re-mount of media in drives
while processing a batch of images on a tape. This was happening because
more than one duplication job was active at the same time in the system
and the media and device selection (MDS) was asking the resource broker
(RB) to unload drives so that the other job could use it. Now the
duplicate writer is not unloaded if told by MDS to do so.
If you want pre 6.0MP4 behavior, you can create the following touch file:
<install_path>/netbackup/db/config/RB_UNLOAD_DUP_WRITER_ON_DEMAND.
--------------------------------------------------------------------------------
Etrack Incident = ET792327 ET792328 ET803918 ET808971 ET843451 ET847076
Description:
A logic error has been identified and corrected in daemons that run on
Veritas NetBackup master, media, and client servers. Successful access to
and manipulation of this logic error could potentially lead to arbitrary
command execution with elevated privileges on a vulnerable system.
For customers who need to back out this patch and want to automate the
down-rev process on their clients using the Update_clients script can
contact Support to obtain a revised bpinst file for their respective
version.
The following scenarios do NOT require a new bpinst from Support:
- If you are downgrading to 50MP7 or higher, 51MP6 or higher,
or 6.0MP4 or higher.
- If you are running Windows on your server.
- If you are only downgrading any of the following addons:
- DB agents (DB2, Lotus Notes, Oracle, SAP, Sybase, or Informix)
- Encryption (all key lengths)
- Java
- Advanced Client
- BMR master or BMR boot server
- NDMP
- Vault
- GDM (5.x only)
- Advanced Reporter (5.x only)
- NetBackup Operations Manager (6.0 only)
- Storage Migrator
- Japanese or Chinese Language Packs
--------------------------------------------------------------------------------
Etrack Incident = ET795443
Associated Primary Etracks = ET794631
Description:
If a hot catalog backup policy (policy type NBU_Catalog) was set up for
a UNIX clustered NetBackup master server that included the Vault option
and the /usr/openv/netbackup/vault/sessions directory was a link pointing
to the shared drive in the cluster configuration, then the data in the
sessions directory was not properly included in the catalog backup image.
--------------------------------------------------------------------------------
Etrack Incident = ET795533 ET795523
Associated Primary Etracks = ET618799 ET791036
Description:
bptm would erroneously log an error, (either an error code 95 or an error
code 97), during image expiration.
--------------------------------------------------------------------------------
Etrack Incident = ET792470
Description:
nbproxy and nbgenjob had unnecessary CPU utilization because additional
logging operations were enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET784640
Description:
Changes were added to fix a memory leak in the PEM logging.
--------------------------------------------------------------------------------
Etrack Incident = ET792282
Description:
In some cases, if the resource broker (RB) was not shut down cleanly,
backups would not run until nbrbutil -resetAll was run.
--------------------------------------------------------------------------------
Etrack Incident = ET794270
Description:
Script-based BLI backups were not cleaning up checkpoint files properly.
Workaround:
To avoid this issue, you can manually delete the checkpoints using the
fsckptadm command. For example, fsckptadm remove <ckpt-name> <mountpoint>
--------------------------------------------------------------------------------
Etrack Incident = ET795345
Description:
Memory was being read after being freed in the job scheduler's work list.
--------------------------------------------------------------------------------
Etrack Incident = ET796051
Description:
Changes were made to correct a minor logic error.
--------------------------------------------------------------------------------
Etrack Incident = ET610398
Description:
When a suspended job is resumed, the bytes count and the file count in the
activity monitor job display is no longer incorrect.
--------------------------------------------------------------------------------
Etrack Incident = ET778923
Description:
When a job was retried immediately, the job status of the previous try
was lost.
--------------------------------------------------------------------------------
Etrack Incident = ET631436
Description:
A problem existed that caused NOM to not show bprd and bpdbm.
--------------------------------------------------------------------------------
Etrack Incident = ET777860
Description:
Changes were made to clean up the following Policy Execution Manager tasks:
- Switched data types from int to bool if used as a boolean.
- Added error checking to the job submission queue to fix a memory leak.
- Changed the Policy Execution Manager to return the status
EC_backup_error or EC_malloc_failed if an error is encountered
starting child jobs for a parent job.
--------------------------------------------------------------------------------
Etrack Incident = ET796104
Description:
A race condition occurred when two add_files queries were received
simultaneously and both attempted to create the catstore folder.
--------------------------------------------------------------------------------
Etrack Incident = ET784650
Associated Primary Etracks = ET829340
Description:
NetBackup communication between components that were separated by a
firewall did not work. For instance, when a master server was behind the
firewall and a media server was outside the firewall, all communication
from the master server had an internal host address that was not accessible
from outside systems.
This is the same when clients and other services are in question.
Additional Notes:
To activate NAT address replacement, systems outside of the firewall should
have the FIREWALL_IN parameter specified in their bp.conf/registry.
Format: FIREWALL_IN=hostname1,nat_address1|hostname2,nat_address2|...
Where: <hostname> is the name of the host system that needs to be accessed
and <nat_address> is the actual NAT address for the firewall to do
forwarding.
--------------------------------------------------------------------------------
Etrack Incident = ET795448
Description:
Changes were made to not send Storage Unit Events when only updating
capacity information. Too many of these events were being generated and
impacting performance.
--------------------------------------------------------------------------------
Etrack Incident = ET793447
Description:
Changes have been made to reduce the bpdbm CPU consumption by doing fewer
things on exit of child bpdbm processes.
--------------------------------------------------------------------------------
Etrack Incident = ET795436 ET796505 ET801859
Associated Primary Etracks = ET794344
Description:
VSP files would sometimes get deleted when they were needed to resume an
incomplete or suspended stream.
--------------------------------------------------------------------------------
Etrack Incident = ET795374 ET814653
Description:
BPTM failed a job with a 174 error when it should retry the
resource allocation.
--------------------------------------------------------------------------------
Etrack Incident = ET797992
Description:
NetBackup 5.x media servers fail when running tpautoconf -sync, if the
global database host is a 6.0 server.
Workaround:
To avoid this issue, delete the device configuration on the 5.x media
server and reconfigure.
--------------------------------------------------------------------------------
Etrack Incident = ET781386
Description:
There may be cases where configuring either shared libraries or shared
drives does not perform the necessary device configuration updates on all
hosts. For example, if host A has drive D1 configured, and then the wizard
is used to configure host B, host B will have the drive added as shared,
but host A's configuration will not be updated. This results in two hosts
scanning the drive.
Workaround:
To avoid this issue, do the following:
- Always use the wizard to configured devices.
- Always scan all media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET797150
Associated Primary Etracks = ET797162
Description:
The bptm process no longer crashes while duplicating data that has True
Image Restore (TIR) information associated with it.
--------------------------------------------------------------------------------
Etrack Incident = ET797080
Description:
When the parent job does stream discovery the
getRealAndVirtualPolicyByName() gives an error and sometimes fails
because the sig library was not initialized. Currently the sig library
is only initialized for catalog backups instead of for all backup types.
--------------------------------------------------------------------------------
Etrack Incident = ET802582
Associated Primary Etracks = ET793913
Description:
The NetBackup Java user interface no longer displays “square box”
characters in the Media “Side” column for the second AcsLsm.
--------------------------------------------------------------------------------
Etrack Incident = ET796480
Description:
Backup jobs would occasionally fail with error status 26 (client/server
handshaking failed). The bpbrm log would show the following:
08:34:12.336 [2764.3504] <2> bpbrm multiplexed_backup: calling
read_media_msg for media manager PID.
08:34:42.618 [2764.3504] <2> bpbrm read_media_msg: media manager pid 0 is
not alive
08:34:42.618 [2764.3504] <16> bpbrm multiplexed_backup: cannot get PID of
media manager
08:34:42.915 [2764.3504] <2> bpbrm Exit: ERROR 26 sent to parent process
--------------------------------------------------------------------------------
Etrack Incident = ET796392
Description:
The NBJM threads block while calling the proxy for BPDBM requests.
--------------------------------------------------------------------------------
Etrack Incident = ET794326
Description:
Changed a strncpy to a V_strlcpy to prevent the string not being null
terminated.
--------------------------------------------------------------------------------
Etrack Incident = ET797363
Description:
Increased the connection cache size for nbjm to reduce number of
Communication retries by bptm.
--------------------------------------------------------------------------------
Etrack Incident = ET784514
Description:
Synthetic backups no longer fail with the error message, "termination
requested by bpcoord(665)".
--------------------------------------------------------------------------------
Etrack Incident = ET797083
Description:
The parent job no longer core dumps upon exiting an application when trying
to log a VxUL message after an orb shutdown. The parent job was modified
to remove all VxUL messages that are being logged after an orb shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET797388 ET798930
Description:
Multiple backups for the same client and policy that were started at the
same time created a situation where an image was being validated at
the same time the previous backup for the client and policy was being
validated.
One of the final steps in image validation is to go back through previous
backups for the client and policy and update the TIR meta data to allow TIR
data to be pruned. However, since the previous backup for the client and
policy was still being validated, it could not be updated and the following
log message (and error report entry) were generated:
17:27:33.723 [11812] <16> get_last_backup_lock: Bad image header:
many-non-multi-stream_1158100028_FULL, error: file read failed (13)
bpdbm was exiting with a normal status, so the backup was successful.
Workaround:
To avoid this issue, wait before starting backups for the same client and
policy.
Additional Notes:
With this change, any failures in updating tir meta data in image
validation will result in a conditional success for the backup job.
--------------------------------------------------------------------------------
Etrack Incident = ET797999 ET797370
Description:
Changes were made to clarify error message that may have been unclear.
This involved no functional change.
--------------------------------------------------------------------------------
Etrack Incident = ET796292
Description:
Pending messages were not displayed in the Activity Monitor for spanned
backups.
--------------------------------------------------------------------------------
Etrack Incident = ET798366
Description:
EMM now logs a more accurate disk space message when space is below
the threshold.
--------------------------------------------------------------------------------
Etrack Incident = ET796332
Description:
Changes were made to bpbrmds to eliminate core dumps when performing a
manual or scheduled relocation of a DSSU on media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET800221
Description:
Parent images have no associated .f file, and as a result have a file count
of zero. When images with a zero file count are validated, a function to
tally the number of files is called. This function should not be called
when there is no associated .f file. The logic to determine whether there
is an associated .f file has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET800184
Associated Primary Etracks = ET798913
Description:
Resolved an issue that caused, "Frequent status code 805 - invalid jobid,"
errors to occur.
Additional Notes:
This condition occurred when children jobs were retired due to exceeding
the time allowed in incomplete state. The parent job being resumed either
manually or automatically resulted in an 805 error due to the job having
a jobid of -1. This fix prevents the child from starting since it is not
resumable. The new result will correctly be a 200 error if no children
can be started. An indication of this will be written to the pem log.
--------------------------------------------------------------------------------
Etrack Incident = ET801046
Description:
The job monitor would cancel the catalog backup job after 20 minutes.
The nbgenjob ping interval to the job manager was changed to three minutes
to keep the job from being cancelled.
--------------------------------------------------------------------------------
Etrack Incident = ET799129
Description:
The synthetic backups were not scheduling correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET800016
Description:
The nbpem would core dump because getECmsgl was not thread safe.
--------------------------------------------------------------------------------
Etrack Incident = ET802987
Description:
A Hot Catalog Backup of a large catalog with a large number of files can
sometimes end up in a deadlock between the NetBackup UNIX agent bpbkar and
the NetBackup media server process bpbrm.
--------------------------------------------------------------------------------
Etrack Incident = ET803630
Description:
Changes were added to correct an issue that casued the resource broker (RB)
to hang at startup.
--------------------------------------------------------------------------------
Etrack Incident = ET799867
Description:
The Policy Execution Manager inefficiently processes policy change
notifications when performing housekeeping tasks which may slow job
submission. This inefficiency can occur from the user interface if the
user selects all policies and then activates or deactivates the list of
policies.
Workaround:
To avoid this issue, do not generate a large number of policy changes all
at once before a window opens. Instead, amortize them over time to limit
the impact on the Policy Execution Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET800184
Associated Primary Etracks = ET798913
Description:
The jobid of a child checkpoint restart job would be set to -1 when
a 196 status occurred. The result was an 805 error if the parent was
resumed because the jobid -1 gets resumed.
--------------------------------------------------------------------------------
Etrack Incident = ET804921
Description:
The calendar schedule would not run when the available window spanned
across the specified day.
--------------------------------------------------------------------------------
Etrack Incident = ET805146
Description:
The NetBackup Job Manager (NBJM) was checking the connection to the proxy
before reading the global configuration to obtain attributes such as,
max vault jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET805407
Description:
The policy monitor would show as being down in Initial Data Load status
page.
--------------------------------------------------------------------------------
Etrack Incident = ET800841
Description:
Sometimes manual jobs would not start through either the user interface
or the command line. This would happen if PEM lost connection with NBJM.
--------------------------------------------------------------------------------
Etrack Incident = ET804850
Description:
An issue that caused catalog backups to hang on a retry have been fixed.
--------------------------------------------------------------------------------
Etrack Incident = ET805807
Description:
Cancelling an incomplete job that failed with a 196 error, then restarting
nbpem would cause the job to show as done in the Activity Monitor.
However, if the job is set to done in the Activity Monitor, a retry or
resume of the active job will not show up in the Activity Monitor.
Workaround:
If there are checkpoint restart jobs that show as complete but have a
status of 196 and pem needs to be restarted, remove the pempersist file
before pem is started again.
--------------------------------------------------------------------------------
Etrack Incident = ET806779
Description:
A timer was scheduled for a backup job even when throttling was not
configured.
--------------------------------------------------------------------------------
Etrack Incident = ET806051
Description:
NetBackup Maintenance Pack upgrades were failing on the active node of an
HP ServiceGuard cluster, due to the package monitor offlining the package
even with switching disabled. The capability to freeze the cluster agent
monitoring by touching a file (/usr/openv/netbackup/bin/cluster/frozen)
was added.
--------------------------------------------------------------------------------
Etrack Incident = ET806888
Description:
The bpinet services on media servers were being reported as an
"unknown" status in NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET806990
Description:
Service credentials had expired and because of that, the NOM client was
unable to log into the NOM server.
Workaround:
To avoid this issue, you can renew the credential using the command line
interface provided by vssat.
--------------------------------------------------------------------------------
Etrack Incident = ET803649
Description:
Jobs would queue indefinitely, following a media server reset while
pending resource requests were outstanding.
Workaround:
To avoid this issue, restart the resource broker, or run nbrbutil -resetall.
--------------------------------------------------------------------------------
Etrack Incident = ET798064
Description:
A problem existed when using the vxlogview command that caused the
–t option to be ignored if it followed a –d option.
--------------------------------------------------------------------------------
Etrack Incident = ET808318
Associated Primary Etracks = ET796499
Description:
The service called NetBackup Volume Manager (vmd) would stop unexpectedly
because of a network problem.
--------------------------------------------------------------------------------
Etrack Incident = ET808314
Associated Primary Etracks = ET804963
Description:
The Tape Library DLT Control Deamon (tldcd) service would unexpectedly
terminate because of network problems.
--------------------------------------------------------------------------------
Etrack Incident = ET808037 ET807124
Description:
The SharePoint Portal, when configured with a network name in a network,
load-balanced, medium farm configuration, would not relink the portal
databases after a restore.
Additional Notes:
Please refrain from using a local IP address when configuring portals and
team sites. SharePoint communicates to all the load-balanced, front-end
servers to get information about the Portal/Team Site when they are backed
up or restored. If there is a Portal/Team Site that is tied locally to one
of the load-balanced servers, then other front-end servers will not be
cognizant of the local names. It will result in backup and restore failures
for the local portals and team sites.
Please use fully qualified domain names or IP addresses (such as,
http://10.80.138.80 instead of http://vitualportal) when configuring
portals and team sites with a network name in a network, load-balanced
environment. A SharePoint application generates exceptions when virtual
servers that are specified that cannot be resolved by the application while
committing and reconnecting the restored databases. These errors can be
tracked with the help of tar logs in NetBackup\logs\tar on the database
client and spswrapper log files in NetBackup\logs\spps folder in the
sharepoint front end servers.
The workaround for this scenario is to use the IP address while
configuring the portal/team sites or restoring/reconnecting the databases
to the portal/team site using the SharePoint 2003 administration console
after the NetBackup restore has completed.
--------------------------------------------------------------------------------
Etrack Incident = ET814706
Description:
PEM no longer crashes when starting a bpduplicate job (or any job where
the client was not set).
--------------------------------------------------------------------------------
Etrack Incident = ET814644
Associated Primary Etracks = ET797945
Description:
The inventory operation, using vmphyinv, was failing with a network
protocol error (39). This was because oprd was crashing. After fixing the
core dump, other issues were encountered (and fixed) because of which tape
header was not being read correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET814692
Associated Primary Etracks = ET801982
Description:
A change was made to ensure that the volume expiration was not getting
reset after expiring all images on a tape.
--------------------------------------------------------------------------------
Etrack Incident = ET814762
Associated Primary Etracks = ET783819
Description:
An Oracle restore would fail if no drives were available within 900
seconds.
--------------------------------------------------------------------------------
Etrack Incident = ET814884
Description:
ExportedResourceMgr.cpp and ExportedResource.cpp do not show up in the
"what" output, making it impossible to verify the version of these files
in the nbjm binary.
--------------------------------------------------------------------------------
Etrack Incident = ET818259
Associated Primary Etracks = ET809337
Description:
Changes were made to correct an issue with adding an NDMP robot.
--------------------------------------------------------------------------------
Etrack Incident = ET818227
Description:
The text for status code 125 has been changed to reflect the use of this
status code in preventing some operations when an online catalog backup is
in progress.
--------------------------------------------------------------------------------
Etrack Incident = ET774674
Description:
When a bad drive or bad tape is mounted and the mount fails, the Media and
Device Selection (MDS) will down the drive and retry using other
drives/media. If this happened to be the scan host for this drive, MDS
would not clear the scanning assignment. Subsequently the device allocator
(DA) would bring the drive back up.
--------------------------------------------------------------------------------
Etrack Incident = ET771156 ET806039
Description:
When drive or library paths are swapped, and devices are re-discovered
using the wizard, users may see drives or libraries with an "empty" path.
This makes the device unusable and it must be deleted and reconfigured.
--------------------------------------------------------------------------------
Etrack Incident = ET772110
Description:
NetBackup would show the incorrect version number when it was installed as
Media Server. For example, bpgetconfig -s >host< (or the appropriate
bpjava* protocol) would not return the patch level if initiated across
UNIX <-> Windows boundaries, for instance,
On UNIX host A, execute bpgetconfig -s B -A
where B is Windows...
or vice-versa
--------------------------------------------------------------------------------
Etrack Incident = ET818369
Associated Primary Etracks = ET808850
Description:
A job could be canceled out of a window when the window was still open.
--------------------------------------------------------------------------------
Etrack Incident = ET818434
Associated Primary Etracks = ET802264
Description:
Scheduled backups did not always run in a window that was open for only
one day, and the freqency was set for less than one day.
--------------------------------------------------------------------------------
Etrack Incident = ET819178
Description:
The nbnos process no longer leaks memory with policy changes.
--------------------------------------------------------------------------------
Etrack Incident = ET818041
Description:
NetBackup would leave rogue/zombie processes running during the course of
the patch install/uninstall. The installer will now actively search for
these processes and terminate them before it continues with the install.
--------------------------------------------------------------------------------
Etrack Incident = ET821063
Description:
Java user interface would use the wrong authentication broker if it was
different from root broker.
--------------------------------------------------------------------------------
Etrack Incident = ET820406
Description:
In some cases, bptm was not exiting after job completion, making jobs
unavailable for other jobs.
Workaround:
Manually kill hung bptm processes.
--------------------------------------------------------------------------------
Etrack Incident = ET819158
Description:
A backup job would get retried even though it completed with a status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET818859
Description:
A change was made so that NBSL no longer core dumps when NetBackup is
accessed using NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET803700
Description:
Changes were made to ensure that parent jobs no longer exit with a
status 200.
--------------------------------------------------------------------------------
Etrack Incident = ET788999
Description:
In the Activity Monitor, the elapsed time for a job would sometimes appear
formatted incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET821035
Associated Primary Etracks = ET795266
Description:
Database backups or restores may fail (because of a timeout).
An examination of the debug logs showed that the EXIT STATUS was sent from
the client to bpbrm, however bpbrm did not receive the EXIT STATUS message.
--------------------------------------------------------------------------------
Etrack Incident = ET821355
Associated Primary Etracks = ET808950
Description:
nbemm will now allow alias functions with machinetypes cluster, app_cluster
and api.
--------------------------------------------------------------------------------
Etrack Incident = ET828665
Description:
A problem that occurred when the following conditions existed has been
fixed:
1) The schedule associated with the DSSU initiates relocation operations.
2) All completed images on the DSSU have already been relocated.
3) New, uncompleted images are in the process of being written to the
DSSU because of new backup operations.
There were no images that could be relocated and the job terminated with
an error status of 190. No errors had actually occurred but the resultant
messages gave the user the impression that something was wrong.
--------------------------------------------------------------------------------
Etrack Incident = ET828100
Description:
The cluster package and monitoring configuration was incorrect when
installing with a fully qualified virtual name on HP serviceGuard
and SunCluster clusters.
--------------------------------------------------------------------------------
Etrack Incident = ET827854
Description:
On the HP-UX IA64 platform, the "bpcatlist -id <backup id>" command could
core dump if the -id option is used.
Workaround:
To avoid this issue, do not use the "-id" option.
--------------------------------------------------------------------------------
Etrack Incident = ET819570
Description:
After you have attempted to stop a NetBackup Service, you may receive a
service stop failure.
Approximately 3 seconds after you have attempted to stop a NetBackup
Service you will notice that progress bar zooms across the screen and
disappears before the service has had a chance to do an orderly shutdown,
causing the stop failure to be reported.
--------------------------------------------------------------------------------
Etrack Incident = ET819159
Description:
An expire from the user interface of a snapshot-based backup image copy
failed with the following message in the bpfis log.
"fis_rebuild_from_db: cannot open"
--------------------------------------------------------------------------------
Etrack Incident = ET821071
Description:
A problem existed in Exchange VSS jobs that caused incremental backups to
act like FULL backups.
--------------------------------------------------------------------------------
Etrack Incident = ET820388
Description:
Added support to display filesystem capacities that are larger than
several Terabytes (TB).
--------------------------------------------------------------------------------
Etrack Incident = ET828735
Associated Primary Etracks = ET821288
Description:
When using vnetd only for client connect, all backups in the multiplexing
group would fail with a 41 status ("network connection timed out") if one
client cannot be contacted.
Workaround:
To avoid this issue, run the backups as non-multiplexed.
--------------------------------------------------------------------------------
Etrack Incident = ET802903
Description:
A problem existed where a catalog backup would run however it did not
appear in the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET828685
Description:
Changes have been made that ensures a Synthetic schedule will run at the
proper time.
--------------------------------------------------------------------------------
Etrack Incident = ET829045
Description:
Pem no longer crashes if there is an attempt to restart a done job from
the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET829683
Associated Primary Etracks = ET814470
Description:
Empty paths on file entries were causing backups to fail with a status 1
and an entry in the bpdbm log similar to the following:
11:29:18.781 [5216.3708] <32> add_files: File:
v:\src\common\libcatalog\nbe_string.h Line: 434: null pointerFunction:
utf8_strlen
With this patch, the backup will still fail if a null or empty path is
detected, but an entry similar to the following will appear in the
NetBackup error report:
A null or empty path was provided for policy1_1160000001_FULL at entry 2501
Additional Notes:
A null or empty path string is usually caused by a failure in the client
device. Check for patches from the device manufacturer to address the
root cause.
There is a known issue with NetApp filers configured for Chinese locales
that produces this problem. NetApp has a file history patch that addresses
the issue:
NetApp Bug ID: 195779
Title: NDMP DMA shows no file names after a backup with 7.0.x
Description:
Empty NFS pathnames will be returned in the file history for non-ASCII
filenames if the root volume's language is not set to C/POSIX or
the language setting of the volume being backed up differs from the
root volume's language setting.
Workaround:
Make sure the language setting of the root volume matches that of
the volume being backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET830269
Description:
A change has been made that ensures that after you have downed a drive on
the scan host, it will not come back up.
--------------------------------------------------------------------------------
Etrack Incident = ET805843
Description:
bpdbm uses the notification service to notify the PEM and JM components
when policies are updated. When the call to the notification service
failed, the bpdbm child process would terminate with little information on
the cause of the failure. With this patch, the cause of the failed call to
the notification service will be logged, and an entry will be made in the
NetBackup error report for the termination of the child bpdbm process.
--------------------------------------------------------------------------------
Etrack Incident = ET797083
Description:
A Parent job (nbgenjob) would core dump when an exception, thrown by
ORB, was not handled. This problem has been fixed in this pack.
--------------------------------------------------------------------------------
Etrack Incident = ET776675
Description:
The pem was referencing a function that was using strtok(), which was not
thread-safe on UNIX platforms. This change only affected UNIX platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET831186
Associated Primary Etracks = ET830464
Description:
Changes were made to resolve an intermittent crash in findByJobId.
--------------------------------------------------------------------------------
Etrack Incident = ET831242
Description:
On large file systems with a large number of images, disk staging would not
free space fast enough to prevent concurrent backups from failing with 129
errors. (Refer also to ET774846.)
Additional Notes:
When a backup to a disk storage unit with staging completes, the percent
used is compared with the high water mark. If the percent used is equal to
or greater than the high water mark, a bpdm process will be invoked which
will remove staged images until the low water mark is reached.
To disable this behavior, create the "IGNORE_HIGH_WATER_MARK" touch file in
the netbackup/bin directory.
--------------------------------------------------------------------------------
Etrack Incident = ET831331
Associated Primary Etracks = ET829395
Description:
The bpduplicate command would fail, resulting in a core dump. This would
occur if bpduplicate, while running on a media server, tried to invoke
bpduplicate on the master using a bidfile. This would happen most
frequently as part of disk staging.
--------------------------------------------------------------------------------
Etrack Incident = ET831415
Description:
When a request to the EMM server to change an expiration date for a media
failed, an unreadable message would appear in the NetBackup error report.
--------------------------------------------------------------------------------
Etrack Incident = ET819040
Description:
A job that was added to a multiplexed group would show an incorrect
operation in the Activity Monitor. For example, the Job operation would
remain as CONNECTING during a successful backup. However, if the backup
job spans tape, the operation would remain as POSITIONING until the job
completes.
--------------------------------------------------------------------------------
Etrack Incident = ET831231
Associated Primary Etracks = ET613789
Description:
Oracle and Informix restores may hang or fail (via a timeout). In one
situation bptm log would contain the following message:
08:40:54.944 [20370] <2> mpx_read_backup: waiting for children to
terminate so exit status can be sent to bpbrm
In another situation the bpbrm log would contain the following message:
16:13:00.835 [173273] <8> bpbrm process_media_msg: unknown media message:
RCD_STOP_DB_RESTORE_STR
--------------------------------------------------------------------------------
Etrack Incident = ET831977
Description:
When an inline tape copy job failed due to un-availability of resources,
the reason string was not displayed in jobd for all copies.
--------------------------------------------------------------------------------
Etrack Incident = ET832116
Associated Primary Etracks = ET829088
Description:
Calendar schedules would not run if another backup ran the same calender
day, even if the backup was in a window that opened on the previous day.
Workaround:
To avoid this issue, use a frequency scheduling of 24 hours.
--------------------------------------------------------------------------------
Etrack Incident = ET833015
Description:
A timeout of a clean or an unload when ltid was not running in verbose
mode would not be cleaned up.
--------------------------------------------------------------------------------
Etrack Incident = ET831472
Description:
NBPEM and NBJM code did not handle exceptions from all ORB calls.
--------------------------------------------------------------------------------
Etrack Incident = ET833885
Associated Primary Etracks = ET833782
Description:
After a pem crash with multistreamed jobs active, the job may not get
scheduled to run again.
--------------------------------------------------------------------------------
Etrack Incident = ET834141
Description:
NBJM would crash on shutdown if there was an active connection in the
connection factory and the timing was such that one thread was destroying
the connection factory while another was working with the connection object.
--------------------------------------------------------------------------------
Etrack Incident = ET834475
Description:
NetBackup Job Manager no longer hangs while running backups for clients
with throttling configured.
--------------------------------------------------------------------------------
Etrack Incident = ET834802
Description:
Catalog recovery from a hot catalog backup would fail with the following
error when the entry for EMMSERVER in bp.conf was different than the
SERVER name for the master server, but, they were actually the same
machine. This would occur when there were two NICs in the master server.
"Failed to find last NBDB backup image record for client serverName
with policy policyName (227)"
--------------------------------------------------------------------------------
Etrack Incident = ET834080
Associated Primary Etracks = ET646858
Description:
A change has been that keeps a bogus STU (such as, a STU pointing to
non-existing device) from causing the NetBackup Resource Broker's cache
to become invalid.
--------------------------------------------------------------------------------
Etrack Incident = ET831475
Description:
Changes were made that enable Vault VCCS Portal libraries to handle
exceptions such as, CORBA::Exception.
--------------------------------------------------------------------------------
Etrack Incident = ET836865
Description:
A change was made to resolve and issue that caused database backups to fail
with a status 13 (file read failed) error. The Job Details would show the
following types of messages:
Error bpbrm (pid=xxxx) socket read failed: errno = 131 - Connection reset
by peer
end writing; write time: 2:04:24
file read failed (13)
--------------------------------------------------------------------------------
Etrack Incident = ET837124
Description:
A change was made that resolves an issue that caused scheduled jobs to not
run.
--------------------------------------------------------------------------------
Etrack Incident = ET829247
Description:
The vmoprcmd -devmon command may incorrectly display multiple drive paths
under a drive name.
--------------------------------------------------------------------------------
Etrack Incident = ET834952
Description:
When a longer frequency backup (such as a full backup) for a client failed
and could not be retried due to an exceeded failure history, nbpem would
initiate a shorter frequency backup, if one was configured and due at the
same time (such as an incremental). This job would also be retried if it
failed.
A change was made to the failure history to resolve this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET831460
Description:
Changed the location of the pempersist file so it is shared in a
clustered setup.
--------------------------------------------------------------------------------
Etrack Incident = ET837657
Description:
Some of the connections between the media server and client were not
affected by the CLIENT_CONNECT_TIMEOUT configuration value for database
agent backups. A hard-coded value of one minute was used instead.
This patch fixes the media server to use the CLIENT_CONNECT_TIMEOUT for
database agent backups as well as file system backups.
--------------------------------------------------------------------------------
Etrack Incident = ET840396
Description:
The Cluster Server Agent for Storage Migrator now installs on Solaris 10.
--------------------------------------------------------------------------------
Etrack Incident = ET840432
Associated Primary Etracks = ET838346
Description:
After a status 129 failure occurred, the retry was not picking a different
DSU in the stunit group.
--------------------------------------------------------------------------------
Etrack Incident = ET837609
Description:
A problem existed that caused jobs to be stuck in a waiting-for-retry state
for multiple days.
--------------------------------------------------------------------------------
Etrack Incident = ET841713
Description:
A change was made to correct the NetWare Loadable Module (NLM) Version
numbers from 5.0 to 6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET840460
Associated Primary Etracks = ET837021
Description:
The pending requests output of the vmoprcmd command no longer prints the
volume group for pending mount requests.
--------------------------------------------------------------------------------
Etrack Incident = ET841261
Description:
Vault sessions and ejects failed under NetBackup Access Control (NBAC).
--------------------------------------------------------------------------------
Etrack Incident = ET841643
Description:
bpmedialist -mcontents command terminated abnormally without notifying NBJM.
The job was declared abandoned after a while. As a result, NBJM failed on
an assertion check while cancelling the job.
After NBJM was restarted, NBPEM could not communicate with NBJM because all
of its threads were hung on a corba call to ping NBJM.
--------------------------------------------------------------------------------
Etrack Incident = ET841711
Description:
In certain conditions where bpmedialist does not get updates from bptm for
more than an hour, NBJM could terminate bpmedialist.
--------------------------------------------------------------------------------
Etrack Incident = ET837077
Description:
A problem existed that caused a catalog backup child job to fail and
remain in "Waiting for Retry" state indefinitely.
Workaround:
To avoid this issue, cancel the job.
--------------------------------------------------------------------------------
Etrack Incident = ET839365
Associated Primary Etracks = ET829855
Description:
The status backup report would report no data or it would report data only
with the wrong hostname.
--------------------------------------------------------------------------------
Etrack Incident = ET844039
Description:
In some instances, it is possible for a media server to have a robotic
drive configured but no corresponding robot entry in the database. In this
case, the device monitor request to the database is "short-circuiting". In
other words, whatever has been retrieved up until the offending record is
displayed, subsequent data is lost.
The fix for this problem is to mark the drive as "AVR" control and continue
normally. Therefore, if such a configuration occurs, these drives will
always have a status of robot DOWN. If you see this, you need to make sure
that the host for the "AVR" drive path has a robotic entry which matches
the drive's residence.
--------------------------------------------------------------------------------
Etrack Incident = ET844043
Description:
When device configuration changes are made, occasionally this will require
that all hosts sharing a drive, be restarted. Previous to this patch, the
device monitor is showing "RESTART" for all the paths - even those paths on
hosts that have had their Device Management Service or Daemon restarted.
This patch changes the device monitor so that the RESTART status is
displayed only for the paths on hosts whose Device Manager have not yet
been restarted.
NOTE: NetBackup may still not use this drive until all hosts' Device
Manager have been restarted.
In addition, the unsupported option for vmoprcmd "-reset_ltid_restarted_bit"
has been changed so that it works on back-rev media servers. Also, a new
option "-get_host_restart_list" has been added to provide a list of all
the hosts for which NetBackup is waiting to have the Device Manager
restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET842109
Description:
After executing bpdown or NetBackup stop, the bpdbm cleanup process was
continuing to run. It was attempting to notify other processes that were
terminated. With this fix, the bpdbm cleanup process checks the status of
the parent bpdbm process and terminates the cleanup if the parent bpdbm
process has been terminated.
Workaround:
To resolve this issue, make sure cleanup is not running before you shut
down NetBackup. You can so this by running bpps and looking for a child
bpdbm process, or by inspecting the bpdbm log for Q_IMAGE_DELETE queries
that have not finished.
--------------------------------------------------------------------------------
Etrack Incident = ET843993
Associated Primary Etracks = ET795418
Description:
It was possible to create a media server and cluster with the same name.
However, depending on which one was used first could create problems at
run time.
Workaround:
To avoid this issue, clean the database with the nbemmcmd command or
direct SQL.
--------------------------------------------------------------------------------
Etrack Incident = ET846970
Description:
NBRB would crash in some situations while running duplicate, synth or
Inline Tape Copy jobs.
--------------------------------------------------------------------------------
=========
NB_60_3_M
=========
Etrack Incident = ET421741
Description:
A user-directed backup for Exchange Volume Shadow Copy Service (VSS)
Transportable failed with a status 200. To resolve this issue, the Policy
Execution Manager (PEM) was changed to start a child Exchange VSS
Transportable job instead of another parent job.
Additional Notes:
Refer also to ET612121.
--------------------------------------------------------------------------------
Etrack Incident = ET616093
Description:
Backup types, such as Network Data Management Protocol (NDMP) and True Image
Recovery (TIR)-enabled, that use the read_files_file query may fail when the
backup contains enough files to cause any of the component .f files to grow
larger than 2 GB. (The .f files are the files in
/usr/openv/netbackup/db/images/<client>/<date>/tmp/catstore.)
Additional Notes:
Refer also to ET546411.
--------------------------------------------------------------------------------
Etrack Incident = ET417355
Description:
The Policy Execution Manager (PEM) retries a failed inline tape copy job a
specific (configured) number of times, after which, it expired the primary
jobid. As a result, the primary jobid was marked as DONE. However, the
secondary jobids remained in the "waiting for retry" state.
--------------------------------------------------------------------------------
Etrack Incident = ET614605
Description:
The NetBackup Policy Execution Manager (nbpem) process no longer dies with
a segmentation violation.
Additional Notes:
Refer also to ET585964.
--------------------------------------------------------------------------------
Etrack Incident = ET614650 ET614416
Description:
Changes were added to replace calls to non-thread-safe functions with
thread-safe versions.
Additional Notes:
Refer also to ET581111.
--------------------------------------------------------------------------------
Etrack Incident = ET614698
Description:
Unable to turn off tracing in job objects-problem.
Additional Notes:
Refer also to ET584481.
--------------------------------------------------------------------------------
Etrack Incident = ET614664
Description:
A change was added to correct the order in which the reference count is
decremented.
Additional Notes:
Refer also to ET582313.
--------------------------------------------------------------------------------
Etrack Incident = ET614641
Description:
Made changes to send the connect options to NetBackup 5.x and NetBackup 6.x
media servers.
Additional Notes:
Refer also to ET577874.
--------------------------------------------------------------------------------
Etrack Incident = ET614589
Description:
Resolved a "read from parent" infinite loop condition in bpbrm.
Additional Notes:
Refer also to ET495890.
--------------------------------------------------------------------------------
Etrack Incident = ET614416
Description:
Corrected numerous thread-unsafe calls, both direct and indirect, in nbjm
and nbpem.
Additional Notes:
Refer also to ET579996 and ET580009.
--------------------------------------------------------------------------------
Etrack Incident = ET614590
Description:
New e-mail functionality has been added to NBPEM to correct some previous
behavior issues.
Additional Notes:
Refer also to ET544252.
--------------------------------------------------------------------------------
Etrack Incident = ET615409
Description:
Jobs no longer fail with a status 25 on the NBJM server side.
Additional Notes:
Refer also to ET593372 and ET611468.
--------------------------------------------------------------------------------
Etrack Incident = ET614699
Description:
Changes were added to always attempt to call the Job Manager to determine
if a Job is active for an invalidated image.
Additional Notes:
Refer also to ET585957.
--------------------------------------------------------------------------------
Etrack Incident = ET614648
Description:
The NetBackup Policy Execution Manager (nbpem) uses strtok to parse various
things. Changes were added to use strtok_r instead for additional safety
reasons.
Additional Notes:
Refer also to ET611478 and ET580000.
--------------------------------------------------------------------------------
Etrack Incident = ET614605
Description:
Fixed an overflow check for INFINITY in nbpem that produced a core file
that pointed to a segmentation violation (signal 11).
Additional Notes:
Refer also to ET585964.
--------------------------------------------------------------------------------
Etrack Incident = ET615640
Description:
Corrected an issue that caused Share point 2001 directives to exit with a
status 69.
Additional Notes:
Refer also to ET615641.
--------------------------------------------------------------------------------
Etrack Incident = ET615654
Description:
Fixed a problem that caused backup jobs to end with "status 200" when they
should not.
Additional Notes:
Refer also to ET610214.
--------------------------------------------------------------------------------
Etrack Incident = ET615652
Description:
The NetBackup Policy Execution Manager (nbpem) would core when it called
convert2unixdate which then called local time which is a non-safe thread.
Additional Notes:
Refer also to ET610206 and ET200604.
--------------------------------------------------------------------------------
Etrack Incident = ET610473
Description:
Child jobs for Catalog backups no longer fail intermittently with a
status 25.
--------------------------------------------------------------------------------
Etrack Incident = ET615656
Description:
Changes were made to fix nbgenjob crashes (affects Windows only).
Additional Notes:
Refer also to ET563727.
--------------------------------------------------------------------------------
Etrack Incident = ET614617
Description:
A problem existed that caused assigned resources to not be reused if the
Media ID's were less than six characters long.
Additional Notes:
Refer also to ET574590.
--------------------------------------------------------------------------------
Etrack Incident = ET614566
Description:
The Backup, Archive, and Restore (BAR) user interface did not notify users
if a pending request had been sent.
Additional Notes:
Refer also to ET568559, ET611457, and ET609552.
--------------------------------------------------------------------------------
Etrack Incident = ET614695
**Description:
When using Veritas NetBackup (tm) 6.0 through 6.0 MP2, if a multiplexed
backup receives an end of media (EOM) message, and before it can get new
media, another backup to the same drive fails, there is the potential for
data loss.
--------------------------------------------------------------------------------
Etrack Incident = ET614611
Description:
Double-free in rfile/wfile pointers, and cleanup -mtd memory problems with
bptm.
Additional Notes:
Refer also to ET586506.
--------------------------------------------------------------------------------
Etrack Incident = ET614611
Description:
Duplication jobs would fail with Status code 174; some contained the
following message:
*** glibc detected *** double free or corruption (fasttop):
Additional Notes:
Refer also to ET586506.
--------------------------------------------------------------------------------
Etrack Incident = ET614623
Description:
The NetBackup Resource Broker (nbrb) was not cleaning up the media
reservations after a job completed.
Additional Notes:
Refer also to ET576637.
--------------------------------------------------------------------------------
Etrack Incident = ET614595
Description:
The Ltid.exe executable no longer causes an exception fault when the mount
requests were disabled.
Additional Notes:
Refer also to ET582349 and ET568524.
--------------------------------------------------------------------------------
Etrack Incident = ET615412
Description:
A problem existed that caused duplication to fail with an error code of
114 and the following error message:
errorCode=114 not enough valid resources
Additional Notes:
Refer also to ET593538.
--------------------------------------------------------------------------------
Etrack Incident = ET615416
Description:
An change was made to correct a double-free problem that was occurring in
bptm.
Additional Notes:
Refer also to ET606797.
--------------------------------------------------------------------------------
Etrack Incident = ET615644
Description:
bptm was logging an informational message that was killing Vault
duplication jobs.
Additional Notes:
Refer also to ET615646 and ET579399.
--------------------------------------------------------------------------------
Etrack Incident = ET617303
Description:
A problem existed with the nbpushdata -add command that caused it to fail
to populate the globDB information into Enterprise Media Manager (EMM)
Database.
Additional Notes:
Refer also to ET597444.
--------------------------------------------------------------------------------
Etrack Incident = ET617304
Description:
The "nbpushdata -remove <host>" command failed when no media was assigned
to the host.
Additional Notes:
Refer also to ET599789.
--------------------------------------------------------------------------------
Etrack Incident = ET617298
Description:
Media was not being ejected from partially successful vaults after
installing the NetBackup 6.0 MP2 pack.
--------------------------------------------------------------------------------
Etrack Incident = ET606288 ET620428
Description:
The NetBackup Job Manager (NBJM) deadlocked while running jobs that backup
to tape.
Additional Notes:
Refer also to ET615617 and ET620561.
--------------------------------------------------------------------------------
Etrack Incident = ET613056 ET625106
Description:
The following ACSLS changes were added in this pack:
- Added multiple ACSLS support to Windows media servers. This requires
Sun (STK) Libattach version 1.4.1 be installed on all media servers
with ACS robotics.
- Added the latest Automated Cartridge System (ACS) media types.
- Upgraded to the latest IBM API for TLH robotics and added the latest
media types. Refer to the Support matrix on the Support Web site for
the latest versions.
- Corrected an ACS inventory query_clean failure when using LibStation.
- Corrected how Windows uses ACSLS ACS numbers that are greater than 0.
- Added TLH robotics support to Linux IA64. Refer again, to the Support
matrix on the Support Web site for the latest versions.
Additional Notes:
Refer also to ET571008.
--------------------------------------------------------------------------------
Etrack Incident = ET613063
Description:
The tpconfig menu user interface was unable to add shared robots or shared
robotic drives.
Workaround:
To avoid this issue, use the tpconfig command line interface instead of
the menu user interface.
Additional Notes:
Refer also to ET574537.
--------------------------------------------------------------------------------
Etrack Incident = ET613069
Description:
Enhanced the media selection algorithm for Automated Cartridge System (ACS)
libraries, to pick a media and drive in the same Library Storage
Module (LSM).
Additional Notes:
Refer also to ET580847.
--------------------------------------------------------------------------------
Etrack Incident = ET613070
Description:
Corrected an ACS library inventory with ACS_LTO_400G mapped to HCART2 in
the vm.conf.
Additional Notes:
Refer also to ET580782.
--------------------------------------------------------------------------------
Etrack Incident = ET613046
Description:
Enhancements have been made that enable the File System Export feature
with ONTAP 7.2. A new backup "mode" (space optimized image or SOI)has
been added along with multiple other changes.
Additional Notes:
Refer also to ET583099.
--------------------------------------------------------------------------------
Etrack Incident = ET613059
Description:
From the tpconfig menu user interface, you could not add a robot with
Shared Storage Option (SSO) drives.
Additional Notes:
Refer also to ET585032.
--------------------------------------------------------------------------------
Etrack Incident = ET613795
Description:
Oracle and Informix restores may hang or fail (via a timeout). In one
situation bptm log would contain the following message:
08:40:54.944 [20370] <2> mpx_read_backup: waiting for children to
terminate so exit status can be sent to bpbrm
In another situation the bpbrm log would contain the following message:
16:13:00.835 [173273] <8> bpbrm process_media_msg: unknown media message:
RCD_STOP_DB_RESTORE_STR
Additional Notes:
Refer also to ET565959 and ET519758.
--------------------------------------------------------------------------------
Etrack Incident = ET612145
Description:
A change has been added making it possible to move media from the merge
table when no media records exists.
Additional Notes:
Refer also to ET540166.
--------------------------------------------------------------------------------
Etrack Incident = ET613071
Description:
When configuring an ACS robot on LibStation, an API Display command was
not available when interfacing to an ACSLS Server.
Additional Notes:
Refer also to ET576449.
--------------------------------------------------------------------------------
Etrack Incident = ET613577
Description:
Duplication jobs may fail if the master server and media
server have intermixed fully-qualified-domain-names and
non-fully-qualified-domain-names for servers.
Additional Notes:
Refer also to ET613685.
--------------------------------------------------------------------------------
Etrack Incident = ET614680
Description:
NetBackup Policy Execution Manager (nbpem) would run deassignempty every
minute on some platforms.
Additional Notes:
Refer also to ET535910.
--------------------------------------------------------------------------------
Etrack Incident = ET614721
Description:
bmrsavecfg failed to collect system information on servers that were
running some versions of MSSQL server.
Additional Notes:
Refer also to ET598114.
--------------------------------------------------------------------------------
Etrack Incident = ET614711
Description:
In previous versions, to get the BMR bootserver patched binaries, you
would need to install the maintenance pack, install the BMR boot server,
then uninstall and reinstall the maintenance pack.
In this pack a repair options has been added that requires you to only
reapply the maintenance pack.
Additional Notes:
Refer also to ET595031.
--------------------------------------------------------------------------------
Etrack Incident = ET612154
Description:
To resolve media conflict issues, the following command can be used.
"nbemmcmd -deletemedia -mediaid <> -originhost NONE"
Changes have been added in this pack that accept "NONE" as a valid origin
host and as a special name.
Additional Notes:
Refer also to ET602232.
--------------------------------------------------------------------------------
Etrack Incident = ET614666 ET613688
Description:
If catalog compression was used on a UNIX master server, the bpdbm
process would not remove client images properly during catalog cleanup if
those images were compressed.
Over time, the disk space consumed by these images that were not removed
properly during catalog cleanup can be significant, although the exact
amount of extra disk space is highly dependant on retention level and
catalog compression configurable settings. (This problem does not affect
Windows master servers.)
Additional Notes:
Avoiding a "disk full" condition by having sufficient available disk space
for the image catalog prevents any operational problems.
If NetBackup 6.0 has been in use for some time and this problem has been
encountered, it is possible that the disk space consumed by the image
catalog (the /usr/openv/netbackup/db/images directory) will shrink
noticeably the first time that catalog cleanup is run after this fix is
applied. Because this is an expected result of applying this fix, do not
be concerned about this reduction in disk space consumption, no usable
files have been deleted.
Symantec recommends that a current catalog backup be completed and
available for recovery before applying the fix in case something unexpected
happens and there is a need to recover the catalog from the current catalog
backup image be encountered.
--------------------------------------------------------------------------------
Etrack Incident = ET615534
Description:
Jobs would fail with a status 25 because bptm could not communicate with
nbjm on the master server when going through a firewall.
Workaround:
To avoid this issue, configure the firewall so that it will wait a longer
time before closing idle connections.
Additional Notes:
Refer also to ET609217.
--------------------------------------------------------------------------------
Etrack Incident = ET615304
Description:
Fixed a problem that caused the NetBackup Policy Execution Manager (nbpem)
to crash with a "60patches/ENG/NB_60MP2_EEB_20060425" in place, when Vault
started.
Additional Notes:
Refer also to ET615305 and ET200604.
--------------------------------------------------------------------------------
Etrack Incident = ET615531
Description:
The MEDIA_UNMOUNT_DELAY function was not always honored for standalone
drives.
Workaround:
Before starting the job, make sure an eligible tape is loaded in the drive
to avoid this issue.
Additional Notes:
Refer also to ET514664.
--------------------------------------------------------------------------------
Etrack Incident = ET615336
Description:
The parent job, nbgenjob, was not completing properly, even though the
child jobs did complete.
Additional Notes:
Refer also to ET611441.
--------------------------------------------------------------------------------
Etrack Incident = ET615646
Description:
The Windows Backup, Archive and Restore user interface did not display all
images for restore (the older backup images were not displayed). Also,
when browsing a client which has a large number of non-standard backups,
bprd would core dump.
Workaround:
To avoid this issue, use the Java user interface and manually select the
start date to browse older images.
Additional Notes:
Refer also to ET579399.
--------------------------------------------------------------------------------
Etrack Incident = ET589069
Description:
Expired media was not being returned to the scratch pool, causing a bptm
status 220 error.
Additional Notes:
Refer also to ET589083.
--------------------------------------------------------------------------------
Etrack Incident = ET615560
Description:
Added the capability to retry immediate backups and allow multiple
schedules of the same policy to be suspended, or incomplete and resumable.
Additional Notes:
Refer also to ET615568.
--------------------------------------------------------------------------------
Etrack Incident = ET614778
Description:
Tracing messages that should appear at level 6 would appear at level 5 and
make the logs less readable.
--------------------------------------------------------------------------------
Etrack Incident = ET614736
**Description:
The Enterprise Media Manager (EMM) server uses a relational database to
store media and device configurations. When the file system runs out of
disk space, the relational database files that the EMM database uses can
become corrupt. This can cause the EMM database to fail to start and
cause backups to fail on the master server. To correct this situation,
the EMM server process monitors disk space and safely shuts down the
EMM database in the event of a disk-full condition.
Additional Notes:
Refer also to ET392256.
--------------------------------------------------------------------------------
Etrack Incident = ET615287
**Description:
Changes were made to the retention levels in Host Properties to resolve
issues that affected the Retention mapping settings in VAULT. This change
corrects a potential data loss issue for Vault customers who use the Vault
retention mappings feature via the user interface. For additional
information, refer to TechNote 282996, on the Symantec Support Web site.
Workaround:
To avoid this issue, disable the use of the Vault retention mappings.
Additional Notes:
This is a data loss issue that could cause vaulted media to expire sooner
than might be expected. Again, refer to TechNote 282996 for additional
details.
--------------------------------------------------------------------------------
Etrack Incident = ET616343
Description:
Media will now be deallocated after a failed multiple copy backup and
duplicated jobs.
Additional Notes:
Refer also to ET567364.
--------------------------------------------------------------------------------
Etrack Incident = ET613180
Description:
VSS Transportable backup of an Exchange server will fail eseutil
validation for Exchange data that exists on a mountpoint volume.
Additional Notes:
Refer also to ET536641.
--------------------------------------------------------------------------------
Etrack Incident = ET618092
Description:
NetBackup Policy Execution Manager (nbpem) crashed because of problems
with the pem persist file read and write.
Additional Notes:
When reading the pem persist file, the first line that could be read was
shifted off by 1 character. This could cause inconsistencies in the first
job in the file and occasionally even a crash.
Refer also to ET543123.
--------------------------------------------------------------------------------
Etrack Incident = ET614250
Description:
Jobs would sometimes not run when they were scheduled to run.
Additional Notes:
Policy Execution Manager (pem) would calculate the scheduled time of a
job. If the job did not run during the window, it may not run in the
next. This could happen with calendar or frequency scheduling.
Refer also to ET622829.
--------------------------------------------------------------------------------
Etrack Incident = ET619764
Description:
Policy Execution Manager would core dump when shuting down due to
nbproxy being shutdown when house cleaning tasks that use nbproxy were
still running.
--------------------------------------------------------------------------------
Etrack Incident = ET622846
Description:
When processing failure history, the Policy Execution Manger would core
dump when calling a library function that was not thread safe.
--------------------------------------------------------------------------------
Etrack Incident = ET624768
Description:
Fixed the About NetBackup dialog from Backup, Archive and Restore window
and the splash screan to display the proper version of the product.
--------------------------------------------------------------------------------
Etrack Incident = ET626204
Description:
The NetBackup Job Manager (nbjm) would crash when resources were obtained
for a generic job.
--------------------------------------------------------------------------------
Etrack Incident = ET626991
Description:
Removed a change to the Windows user interface that caused a regression.
--------------------------------------------------------------------------------
Etrack Incident = ET626960
Description:
Correted an issue that caused information to not be written to the
pem persist file consistently.
--------------------------------------------------------------------------------
Etrack Incident = ET626343
Description:
The NetBackup Job Manager (nbjm) would leak memory with every reference to
the job params file.
--------------------------------------------------------------------------------
Etrack Incident = ET627313
Description:
Policy Execution Manager would leak memory when reading failure history.
--------------------------------------------------------------------------------
Etrack Incident = ET627716
Description:
A change was made because the bprd executable (bprd.exe) was not being
replaced properly on an uninstall of NB_60MP3.
--------------------------------------------------------------------------------
Etrack Incident = ET630431
Description:
Changes have been made to remove the pempersist file before the services
are restarted during the pack installation.
--------------------------------------------------------------------------------
Etrack Incident = ET628695
Description:
A change has been added that prevents bpduplicate from corrupting heap
memory and crashing by copying a string into a too small destination string.
--------------------------------------------------------------------------------
Etrack Incident = ET613657
Description:
All Windows BMR Boot Servers now contain a new wizard to assist in
creating a CD image to be used for the Fast Restore feature.
This new feature is an exciting fast-windows-restore feature to the Bare
Metal Restore (BMR) option. This feature can perform a complete restore
of a Windows system in as little as 15 minutes. This feature means it is
no longer necessary to create DOS-based floppies or CDs. In addition,
this new feature enables BMR to operate in a low-infrastructure mode,
where the BMR Boot Server, Windows Shared Resource Tree, and the
Prepare-To-Restore step are no longer mandatory to restore a Windows
System.
For a description of how to use this new feature, along with feature
requirements and limitations, please refer to the Symantec TechDoc #283726.
This document can be accessed on the Symantec Support Web site using the
following URL:
http://support.veritas.com/docs/283726
================================================================================
=========
NB_60_2_M
=========
Etrack Incident = ET425117
Description:
Potential access violations, due to a (possibly) incorrect printf argument
list, are now averted.
--------------------------------------------------------------------------------
Etrack Incident = ET425322
Description:
There were a few instances in the code where the image query protocol
version was set to 0, which was a pre-NetBackup 5.0 image version ID.
Some image queries would fail if the size of the total data being backed
up was larger than 2 Terabytes in one job.
This issue has been corrected, thus enabling image queries on backups
greater than 2 Terabytes to work properly.
--------------------------------------------------------------------------------
Etrack Incident = ET427178
Description:
When sharing tape drives between media servers running both NetBackup 6.0
and NetBackup 5.x, a problem existed with the NetBackup 6.0 Scan Hosts.
If the drive being scanned was assigned to a NetBackup 5.x media server,
then the NetBackup 6.0 Scan Host might not stop scanning. This resulted
in SCSI reservation conflicts and DOWN'ed drives on the NetBackup 5.x
assigned host.
Workaround:
To avoid this issue, do not share drives between media servers running
different versions of NetBackup. Instead, pool your drives such that all
of your NetBackup 5.x media servers share one pool of drives and all of
your NetBackup 6.0 media servers share a pool of different drives.
--------------------------------------------------------------------------------
Etrack Incident = ET428597
Description:
When running multi-streamed Windows Open File Backup backups to back up
open or active files, some Volume Snapshot Provider (VSP) cachefiles in the
format of, _vxfiVspCacheFile_1.VSP, may be left behind by backup jobs that
have already completed. This does not occur with non-streamed backup jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET429921
Description:
When upgrading from NetBackup 5.x to NetBackup 6.0, the
NETBACKUP_RELATIONAL_DATABASE_FILES directive was not added to the list of
files included in cold catalog backup. The command, bpsyncinfo -add_paths
"NETBACKUP_RELATIONAL_DATABASE_FILES," is run automatically during the
patch installation to add this directive to the cold catalog backup
configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET430039
Description:
NBDB (for Enterprise Media Manager (EMM) and BMR) database recovery failed
if the master server had a newer catalog backup image than the one used in
Disaster Recovery (DR). On Windows platforms, it logged an error message
in the progress log and displayed a error message dialog. On UNIX
platforms, because of a defect in the Java user interface, it would only
report an error message in the log and all restore jobs appeared in job
monitor as successful.
Additional Notes:
With this fix, a user is able to recover from an older catalog backup even
though the user has a newer catalog backup image on the master server.
Full catalog disaster recovering from an older catalog backup is a
“roll-back” operation, that has potential of losing data. Users should
understand the implications and use it with caution.
--------------------------------------------------------------------------------
Etrack Incident = ET414315
Description:
When performing an Optical backup, the optical media will not use side B
once side A becomes filled. Instead a new platter is used. Once all
of the platters are filled on side A, side B of the platters is filled.
--------------------------------------------------------------------------------
Etrack Incident = ET431050
Description:
This pack corrects the frequency mode scheduling algorithm to function the
same as it did in the pre-NetBackup 6.0 product, when the frequency was a
multiple of 24 hours.
--------------------------------------------------------------------------------
Etrack Incident = ET422114
Description:
A problem was corrected that caused the NetBackup Policy Execution
Manager (nbpem) to dump a core file on shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET425135
Description:
Failed snapshots no longer cause "job retires" to become "new jobs".
--------------------------------------------------------------------------------
Etrack Incident = ET421439
Description:
Manual backups would not start immediately if the NetBackup Policy
Execution Manager (PEM) was started first.
--------------------------------------------------------------------------------
Etrack Incident = ET432263
Description:
For a Hot Catalog Backup, the relational database (NBDB/Sybase ASA) backup
job treated a cumulative and differential incremental backup the same and
only included the transaction log in the backup. This could create
problems when recovering the ASA database if the differential backup media
created before the last cumulative had expired. The differential backups
contain the transaction logs that are necessary to roll forward from the
last full backup. To fix this problem, the cumulative incremental backup
will be a full backup for the ASA files.
--------------------------------------------------------------------------------
Etrack Incident = ET430274
Description:
Because of a logic error in the handling of "bptm -delete_all_expired",
the expired media was not being deleted. This prevented recycling of the
media.
--------------------------------------------------------------------------------
Etrack Incident = ET428121
Description:
Upon de-allocating a drive, the Device Allocator (DA) was selecting a Scan
Host as if there had been no previous or existing Scan Host.
--------------------------------------------------------------------------------
Etrack Incident = ET421579
Description:
NetBackup tracks the media manufacturer and serial number in the
EMM database. Some drives do not support this data while some do.
If drives that do not support this type of data are added into a library
with drives that do support this type data, the database can end up with
multiple media with the same manufacturer and serial number information.
This condition would lead to problems loading the media at a future time.
--------------------------------------------------------------------------------
Etrack Incident = ET430429
Description:
The transport of log messages from NBSL to the NOM Server was failing and
causing the Host Session to go down.
POSIX-based systems can set either EWOULDBLOCK or EAGAIN when send() fails.
TAO (part of PSP) was testing just for EWOULDBLOCK. All other errnos were
considered harmful. This prevented the rest of the data from being flushed
out when send () raised EAGAIN. The clients never received the whole data
which caused the hang. A fix for PSP was provided that prevents this
issue from happening again.
--------------------------------------------------------------------------------
Etrack Incident = ET411601
Description:
An error occurred while creating a SUSE Shared Resource Tree (SRT).
Cleanup of this SRT would fail and display the following incorrect message:
[Error] V-125-376 No space left on device. Please ensure that the
specified target location for the Shared Resource Tree has adequate free
space, and retry the command.
Please refer to the Bare Metal Restore System Administrator's Guide
for the space requirements for creating Shared Resource Trees.
--------------------------------------------------------------------------------
Etrack Incident = ET430203
Description:
Expiring a non-multiplexed image should reduce the vimages and kbytes on
the media record. Because of a data conversion error, this reduction is
not taking place.
--------------------------------------------------------------------------------
Etrack Incident = ET429917
Description:
The vmd process no longer core dumps if the EMM service (nbemm) is not
running.
--------------------------------------------------------------------------------
Etrack Incident = ET427169
Description:
The nbpushdata operation fails when “pool name” has a hyphen in the pool
name.
--------------------------------------------------------------------------------
Etrack Incident = ET494938
Description:
Data tapes are no longer be treated as cleaning tapes and are FROZEN by
NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET495033
Description:
The Device Monitor shows the same tape mounted in multiple drives. This
tape is assigned to a NetBackup 5.x media server.
Workaround:
To avoid this issue, do not share drives between NetBackup 6.0 media
servers and NetBackup 5.x media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET492433
Description:
A race condition existed between NBRB and BPTM that would lead to jobs
getting 174 errors.
--------------------------------------------------------------------------------
Etrack Incident = ET430477
Description:
It is now possible to import Backup Exec images that have files with
filenames that contain embedded new-lines in them.
--------------------------------------------------------------------------------
Etrack Incident = ET496071
Description:
Some Oracle backups ended prematurely with status 25.
--------------------------------------------------------------------------------
Etrack Incident = ET495475
Description:
nbpushdata would fail with the following messages in the nbpushdata log
file:
<4> get_host_info: CEMM_MACHINE_DISK_ACTIVE being set for <your_host>
<16> emmlib_UpdateHost: (0) UpdateMachine failed, emmError = 2007079,
nbError = 0
<16> get_host_info: (-) Translating
EMM_ERROR_SQLSyntaxErrorOrAccessViolation(2007079) to 193 in the
Media context
--------------------------------------------------------------------------------
Etrack Incident = ET496956
Description:
A problem was causing the Windows open file backup to not show retries in
the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET420304
Description:
Originally, vmscd, was a single process that serviced requests from the
EMM server synchronously. Because of this, the EMM server was not
receiving the request response in a timely manner. In some cases, the
EMM server thinks that vmscd has exited, thus, triggering certain
operations that were redundant and in some cases harmful.
Now there are two vmscd processes. The parent vmscd process receives
requests from the EMM server and services them as soon as possible. The
child vmscd process collects the drive status from back level media
servers.
--------------------------------------------------------------------------------
Etrack Incident = ET496080
Description:
For media with image expiration set to infinity, nbpushdata would pass an
incorrect value for infinity to the EMM database; thus, the media could
not be queried.
nbemmcmd -listmedia -mediaid <media_id>
NBEMMCMD, Version:6.0(20050906)
The function returned the following failure status:
generic EMM SQL error (193)
Command did not complete successfully.
vmquery -m <media_id>
Could not query by media ID A00001 with debug: generic EMM SQL error (193)
--------------------------------------------------------------------------------
Etrack Incident = ET496958
Description:
The Data Lifecycle Manager consolidation jobs will now complete
successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET428319
Description:
A problem existed that caused the nbpushdata -remove command to fail.
Workaround:
To avoid this issue, the EMM data base was dropped and recreated.
--------------------------------------------------------------------------------
Etrack Incident = ET495345
Description:
The default start date, 01/01/1970 will not work for 'bpchangeprimary' in
any locale that does not display dates as mm/dd/yyyy.
Workaround:
If the start date is entered in the correct format for the locale it will
be accepted.
For example:
bpchangeprimary -copy 1 -sl sName -pn cjPName-st FULL -pt MS-Windows-NT
-sd 1070-01-01
--------------------------------------------------------------------------------
Etrack Incident = ET495866 ET496960
Description:
Changed bprd and pem so that the bprd child could terminate and not wait
for a job exit status from pem unless the -w flag was used on the request.
--------------------------------------------------------------------------------
Etrack Incident = ET428657
Description:
When you perform a raw backup with the encryption option enabled, using
the block device, and then you attempt a restore of the raw image to the
block device, the restore job would finish with a zero (0), however, the
data was not restored correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET497777
Description:
Could not inventory legacy TS8 libraries as TL8.
--------------------------------------------------------------------------------
Etrack Incident = ET497271
Description:
If any inetd entry is missing on a client and update_clients is used to
push NetBackup client software to it, update_clients will show an error
message in the log file. Corrections were made to the temporary file names
so that inet.conf on the client is updated properly and no error is
generated.
--------------------------------------------------------------------------------
Etrack Incident = ET497944
Description:
Under extremely heavy load in the Device Allocator, the DA may crash EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET496962
Description:
Some vital logs were not displaying correctly.
The form that Log:DbLogMsg is being called in emmserver source files was
incorrect whenever it was multi-lined in the code. As a result, only part
of the log message would survive and the important log information was
lost.
Currently many are in the wrong form of:
Log::DbLogMsg( EMMLOG_DEBUG3, who,
"<MANUALCONF> Control host name is NOT passed in, "
"Assuming incoming host < %s > as the control host",
machineName.c_str() ) ;
The quotes were not being processed correctly so the line starting with
"Assuming” would not appear.
--------------------------------------------------------------------------------
Etrack Incident = ET498496
Description:
Non-robotic tape drives that contain unlabelled media are no longer
automatically assigned to non-robotic media specific mount requests.
--------------------------------------------------------------------------------
Etrack Incident = ET498519
Description:
In a rare condition, one or more backups would be corrupt when using
Inline Tape Copy (ITC) with multiplexed backups. This could happen under
the following conditions:
- ITC was enabled with two or more active copies.
- Multiplexing was enabled with two or more active backups.
- The schedule configuration had "continue if the copy fails" flag
set for the copy that failed in the next step.
- A copy other than the first active copy encountered "end of media", so
a new media was needed for this copy. Then, there was a problem getting
or configuring media (for example, writing the media header) such that
this copy failed before continuing the backup.
- The last buffer written to the first active copy prior to the "end of
media" on the other copy was not the first active backup.
Workaround:
To avoid this problem, do one of the following:
- Edit the schedule configuration to disable the "continue if copy fails"
flag.
- Disable multiplexing.
- Disable ITC.
--------------------------------------------------------------------------------
Etrack Incident = ET428317
Description:
The back-level media server request, V_QUERY_CLEAN_BYROBNUM, would cause
an SQL error.
--------------------------------------------------------------------------------
Etrack Incident = ET420766
Description:
The vmoprcmd -devmon ds command is failing with a Corba exception.
--------------------------------------------------------------------------------
Etrack Incident = ET499611
Description:
Synthetic backup could have potential data loss in following cases:
- Last full/synthetic, full expired/deleted backup, followed by one or
more incremental backups, and a synthetic backup.
- Last incremental/full backup catalog was compressed before the next
incremental backup takes place.
- TIR records in the last incremental backup are missing for various
reasons
--------------------------------------------------------------------------------
Etrack Incident = ET506459
Description:
Media Servers that share drives on versions of NetBackup older than
NetBackup 6.0 receive host_not_registered errors when attempting to
decree another media server is unavailable.
--------------------------------------------------------------------------------
Etrack Incident = ET495457
Description:
The base NetBackup UNIX Agent has now been integrated with VxFS
Checkpoints. It has been modified to detect VxFS checkpoints using the
mount table's special options, and then use VxFS supplied APIs to detect
sparseness in them, and handle it accordingly.
Without these changes, a base NetBackup UNIX Agent could not tell if the
zero or smaller physical size of VxFS checkpoints, as compared to the
reported file size, is due to actual sparseness of the file or not. The
result was the base NetBackup UNIX Agent had to look through the whole
file and try to determine sparseness; thus, slowing down the backups
considerably.
--------------------------------------------------------------------------------
Etrack Incident = ET293930
Description:
This fix improves the performance of the NetBackup Error log collection
logic because the NBLogCollector was not seeking to a known spot for
performance reasons. To address this issue, logic was changed to get
newly-added error log messages by using a stat() system call to learn the
modified time of the error log file and keeping the opened file for the
next collect() call to maintain the current read position of the file.
--------------------------------------------------------------------------------
Etrack Incident = ET496560
Description:
The NetBackup Service Layer (NBSL) no longer causes a core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET507270 ET507266 ET507656
Description:
The following three issues have been address:
- Under certain conditions backups may not schedule. This would happen
because of a problem in computing the next time a job is due. Windows
were not processed correctly if a backup should have run in a previous
window and if the next window opened or closed at a different time.
- The Advanced Client VSS snapshot backup produced an 805 error. A
mistake in nbpem's logic would cause a child job to be resumed or
restarted using an old job id. It would use the jobid of the parent,
resulting in and an invalid jobid.
- The scheduler would always execute full backups, even for incremental
backups, if the BMR option was on. nbpem would use the wrong criteria
for a last backup query made for a parent job that did not have
multiple data streams enabled. The result was no last full backup
being found, so a full backup would be run instead of an incremental.
--------------------------------------------------------------------------------
Etrack Incident = ET506080 ET566045
Description:
In a cluster under NetBackup Access Control the credential associated with
the physical node name is no longer picked up rather than the virtual host
name associated with NetBackup. And in a cluster, an attempt will be made
to use a credential created using bpnbat -loginmachine for the virtual
host name.
Workaround:
To avoid this issue, create credential files for both the physical host
names and the virtual hostnames for each node in the cluster. For details
on how to create credentials, refer to the NetBackup System Administrator's
Guide Volume II, Chapter 1, "Access Management".
--------------------------------------------------------------------------------
Etrack Incident = ET495479
Description:
The NetBackup Service Layer (NBSL) no longer causes a core dump when NOM
is configured. The core dump would occur when NetBackup 5.x media servers
were configured to a NetBackup 6.0 master server and NBSL would attempt to
collect data from the 5.x media server.
--------------------------------------------------------------------------------
Etrack Incident = ET507657
Description:
An error would occur when nbpushdata used emmlib_DeleteHost to remove the
NDMP host server. An error similar to the following was written to the
nbemm log.
11/11/05 15:54:41.185 [Debug] NB 51216 nbemm 111 PID:13393 TID:1196157872
[No context] 1 [DbConnection::Execute] SQL - retval=2007085(2007085)
retdal=-1 native=<-143> sqlerror=<[Sybase][ODBC Driver][Adaptive Server
Anywhere]Column 'FQMachineName' not found> sqlstate=<42S22>
--------------------------------------------------------------------------------
Etrack Incident = ET498714
Description:
A change was made to address conflicts in the EMM_Media table
after an upgrade. An EMM server change was made in the
helperAssignUpgradeImageInfoToMergeTable to accept "NONE" as
a valid assigned host name. This change was needed for the
following command:
# /bp/bin/admincmd/nbemmcmd -forcemerge -assignedhost NONE -mediaid A00000
-originhost pjcbk001 -reversemerge
--------------------------------------------------------------------------------
Etrack Incident = ET498037
Description:
User names and group names longer than 32 characters were not supported.
Workaround:
To avoid this issue, you should use group names and user names that are
smaller than 32 characters.
Additional Notes:
Even with this fix, max possible gname and uname allocated is 1024 chars
--------------------------------------------------------------------------------
Etrack Incident = ET507646
Description:
In certain cases when NetBackup Access Control was enabled, long-lived
processes, such as, nbemm, nbpem, nbjm, nbrb, nbproxy, nbsl, and vmd may
have leaked memory.
--------------------------------------------------------------------------------
Etrack Incident = ET509198
Description:
The SQL SERVER backup would complete normally, however, the client user
interface would display -1 status. Improper progress log updates caused
this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET506666
Description:
A Linux client with an empty or non-existent /etc/resolv.conf file would
halt at restore time even though the client's original configuration did
not use the /etc/resolv.conf file.
Additional Notes:
Linux Shared Resource Trees (SRT) created after this pack is applied will
correctly handle an empty or non-existent /etc/resolv.conf file.
--------------------------------------------------------------------------------
Etrack Incident = ET509505
Description:
Spanning media jobs occasionally appeared to be hung, the request would
continually fail with the message, "ROBOTIC LIBRARY IS DOWN ON SERVER".
This typically occurred after an earlier failure of,
"MEDIA SERVER IS CURRENTLY NOT CONNECTED TO MASTER SERVER". However, the
media server would show the robot as being up and the host as ACTIVE or
ACTIVE-TAPE.
--------------------------------------------------------------------------------
Etrack Incident = ET367776
Description:
The NetBackup Service Layer (NBSL) no longer hangs in a "stopping" state
in the Windows Service Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET506668
Description:
For Linux clients, some S-ATA devices were not being handled correctly
at restore time. Changes contained in this pack load the proper modules
correctly in the restore environment so the restoration can be performed.
Additional Notes:
The original problem presents itself when the restore environment boots.
After loading the SRT, the restoration will stop, requesting for a reboot
of the client, with a boot order string that contains the ata_piix module.
Even if the client is rebooted and the order string is passed from the boot
prompt, the message appears again and the restoration can never proceed.
Once this patch is applied on the Boot Server, the SRT needs to be
recreated for this fix to be available. SRTs created with bmrsrtadm
versions prior to the one contained in this patch will have the problem.
--------------------------------------------------------------------------------
Etrack Incident = ET509087
Description:
A change was made that enables vmd to retry and make the connection to
EMM indefinitely, instead of shutting down if it could not make the
connection.
--------------------------------------------------------------------------------
Etrack Incident = ET500512
Description:
There are end case situations especially when a master server cluster node
goes inactive where the bprdreq -terminate and bpdbm -terminate commands
in bp.kill_all might take several minutes to complete. This can cause
inconsistencies in a cluster enviroment.
--------------------------------------------------------------------------------
Etrack Incident = ET511942
Description:
From the NOM user interface, it is not possible to start a service/deamon
when NetBackup is on UNIX operating systems.
--------------------------------------------------------------------------------
Etrack Incident = ET509733
Description:
NBSL was occasionally sending negative values for the “free space” and
“total capacity” of a storage unit (particularly if the values are
greater than 2^32-1).
--------------------------------------------------------------------------------
Etrack Incident = ET499203
Description:
bpdbjobs -all_columns takes a segmentation fault in either the FreeJobs()
or PrintJobs() function with a stack overflow.
--------------------------------------------------------------------------------
Etrack Incident = ET511981
Description:
It is now possible for SAN media servers to be used as write hosts for
duplicate jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET419837
Description:
Some keys generated by bpkeyutil for standard encryption would cause
backups to fail. The failure status is 40 - network connection broken.
About one out of 256 keys caused this failure.
--------------------------------------------------------------------------------
Etrack Incident = ET512393
Description:
VxUL queries no longer fail on AIX platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET509994
Description:
Changed the way NetBackup package versions are stored in SRT records so
that the history of maintenance is preserved.
--------------------------------------------------------------------------------
Etrack Incident = ET509547
Description:
A problem existed that was limited to a DSSU duplication (not a vault or
manual duplication issue) that would take more than 59 minutes to
complete. After 20 minutes, a status 50 occurred, but the underlying
duplication still had 39 more minutes to finish. After 59 minutes,
EMM noticed the "problem" and shut down the job.
--------------------------------------------------------------------------------
Etrack Incident = ET513419
Description:
NBNos no longer runs in single-threaded mode only.
--------------------------------------------------------------------------------
Etrack Incident = ET511008
Description:
If there is more that one user schedule in a policy, and a schedule is
not specified in the backup request, the job may fail with a 199 error
(no open windows).
Workaround:
To avoid this issue, either specify the schedule name in the backup
request, or do not create more that one user schedule in a policy.
--------------------------------------------------------------------------------
Etrack Incident = ET510797
Description:
A job that fails with a 196 error (EC_no_attemp_window_close) will be left
in a “waiting for retry” state instead of being done.
--------------------------------------------------------------------------------
Etrack Incident = ET499144
Description:
When running multi-streamed Windows Open File Backup backups, jobs would
fail with a status 200 error.
--------------------------------------------------------------------------------
Etrack Incident = ET513486
Description:
The following back-level SSO interoperability issues have occurred:
- Numerous re-registrations were consuming all of vmd's bandwidth on the
EMM server.
- Registration failures would occur because the no-scan-host setting,
registration retry timer would block back-level servers from releasing
drives.
- Back-level remote scanning of NetBackup 6.0 media servers was failing
with ENOTSCANHOST and forcing even more registrations to occur.
Workaround:
DO NOT SHARE DRIVES BETWEEN 6.0 AND 5.X MEDIA SERVERS.
--------------------------------------------------------------------------------
Etrack Incident = ET516562
Description:
nbemm no longer core dumps with a clustered master server.
--------------------------------------------------------------------------------
Etrack Incident = ET511445
Description:
To improve performance of nbpem, all sorting has been removed.
--------------------------------------------------------------------------------
Etrack Incident = ET506661
Description:
After installing NetBackup into a Solaris Shared Resource Tree (SRT), if
the source of the installation is a CD-ROM, the device is left mounted and
the CD-ROM cannot be ejected.
Workaround:
After installing NetBackup into the Shared Resource Tree, exit bmrsrtadm,
start bmrsrtadm again, and this time choose the Share Resource Tree that
was just created.
--------------------------------------------------------------------------------
Etrack Incident = ET516645
Description:
If nbpem received a request to terminate while a terminate request was
being processed, the Policy Execution Manager (pem) would crash.
--------------------------------------------------------------------------------
Etrack Incident = ET326958 ET518198 ET424885 ET387319 ET415289 ET414469 ET422797
ET424915 ET515462 ET499211 ET520460 ET427072
Description:
Added support for the following libraries:
EMC NDMP VTLU
Falcon Stor
IBM 3576 Library
IBM TS7510 Virtualization Engine
HP MSL-2024 G3 Series
Added support for the following drives:
IBM 3592E05
Sony SDX 800v
Updated support for the following libraries:
ADIC Scalar i2000
Quantum TZ Media Changer
Updated support for the following drive:
ADIC i500
IBM 3592
--------------------------------------------------------------------------------
Etrack Incident = ET421278
Description:
Force the UNIX implementations of the BPCD_FORK_CMD_W_STAT_RQST,
BPCD_FORK_OTHER_CMD_RQST, and BPCD_EXECUTE_CLIENT_CONFIG_RQST protocols
to wait as long as necessary for the [child] command to complete.
Previously, the command would have been killed if it did not complete
within BPCD_TIMEOUT seconds (300). This behavior was unwarranted, and
was inconsistent with the Windows implementation, which already waits an
indefinite time. In addition, supporting code that was not necessary
was removed.
--------------------------------------------------------------------------------
Etrack Incident = ET515306
Description:
At “fall-back time” for daylight savings time, the calendar scheduling
may repeatedly run the same job.
--------------------------------------------------------------------------------
Etrack Incident = ET514752 ET563731
Description:
A change made to bpexpdate such that, media IDs that are less than six
characters, and returned from EMM, were not padded with spaces. This
caused bpexpdate -deassignempty to mistakenly deassign media that still
had valid images on them.
Workaround:
To avoid this issue, turn off the automatic start of
bpexpdate -deassignempty by performing one of the following items:
- On a UNIX master server, create the file,
/usr/openv/netbackup/bin/bpsched.d/CHECK_EXPIRED_MEDIA_INTERVAL,
and enter a 0 (zero) on the first and only line of the file.
- On a Windows master server, create the file,
<install_path>\NetBackup\bin\bpsched.d\CHECK_EXPIRED_MEDIA_INTERVAL,
and enter a 0 (zero) on the first and only line of the file.
--------------------------------------------------------------------------------
Etrack Incident = ET507316
Description:
The bprd log message was off-by-one for process_command(). This lead to
log messages like:
15:23:10.035 [115624.76592] <2> process_request: command unlisted command
(114) received (where 114 is actually get_hostinfo)
--------------------------------------------------------------------------------
Etrack Incident = ET519755
Description:
The partial restore of a database backup fails. For example, restoring
a single Oracle tablespace from a backup set.
The following types of messages will be found in the bptm log:
14:50:59.752 [19995] <2> read_brm_msg: STOP RESTORE algol_1134518480 EXIT=0
14:50:59.752 [19995] <2> process_brm_msg: GCACTIVE but CHILD_PID not alive
The following types of messages will be found in the dbclient log:
14:50:59.718 [1932.1552] <4> closeApi: INF - FORCED EXIT STATUS 0: the
requested operation was successfully completed
14:50:59.718 [1932.1552] <4> closeApi: INF - closing commSock 220
14:50:59.718 [1932.1552] <4> closeApi: INF - Do not close dataSock
14:50:59.718 [1932.1552] <4> closeApi: INF - closing nameSock 952
14:50:59.718 [1932.1552] <4> serverExitStatus: entering serverExitStatus.
14:50:59.718 [1932.1552] <4> readCommMessages: Entering readCommMessages
15:06:04.724 [1932.1552] <16> readCommFile: ERR - timed out after
900 seconds while reading from C:\Program Files\VERITAS\
NetBackup\Logs\user_ops\dbext\logs\1552.0.1135025111
--------------------------------------------------------------------------------
Etrack Incident = ET518079
Description:
The vmscd's time-out while communicating with back-level servers was too
small. Because of this, vmscd would think that the back-level server was
not running and it used to decree that the host was unavailable.
As part of this fix, the time-out value was raised.
--------------------------------------------------------------------------------
Etrack Incident = ET511741
Description:
vlteject no longer fails with the following error when tapes are taken
out of the map after long time.
"vmchange eject verify not responding[300]"
--------------------------------------------------------------------------------
Etrack Incident = ET512872
Description:
Removed the change events for Error LogMonitoring. For example, the error
log collection functionality was removed. In addition, the
getLogMessages() idl method supports the error log source; thus, NOM call
this method for getting error logs. Finally, the getEventChannel()
functionality has been removed, resulting in an AFException.
Additional Notes:
Because of this fix, log monitoring of NOM 6.0 MP2 only works with
NetBackup 6.0 MP1 or MP2.
--------------------------------------------------------------------------------
Etrack Incident = ET511772
Description:
Pagination on the report in myportal did not work if table was accessed
after long duration of time.
--------------------------------------------------------------------------------
Etrack Incident = ET413396
Description:
The LANG environment variable was not being properly inherited from the
master's invocation. Because the locale was passed as an argument to the
user server invocation, there was no harm in redundantly performing a
putenv() from the user server.
--------------------------------------------------------------------------------
Etrack Incident = ET522065
Description:
Restore to an alternate client (not a master or media server) by a
media server fails with error status 159:
The licensed features for this system do not permit the backup of a
remote client (<client> ). Make sure that the license key is entered
properly. In addition, SAN media server licensing should be enforced
for backup but not for restore to allow maximum flexibility for DRM
data restoration.
--------------------------------------------------------------------------------
Etrack Incident = ET522555
Description:
Vault failed to run properly from the user interface in VxSS/NBAC
configuration. While in a start session from the user interface, the job
failed to execute, and nothing appeared in the Activity Monitor. This was
observed for any valid user (Administrator) with all the required
permissions. This fix enables executions that originate from the user
interface to be processed properly.
--------------------------------------------------------------------------------
Etrack Incident = ET432239 ET508863
Description:
Corrected ACS timeouts when the ACSLS server had communication problems
with the media server.
To correct this problem, a 20 second wait was removed before checking for
drive readiness on an ACS mount.
--------------------------------------------------------------------------------
Etrack Incident = ET520519
Description:
A stack-based buffer overflow vulnerability existed in the volume manager
daemon (vmd) running on NetBackup servers. If an attacker was able to
gain access to a vulnerable NetBackup server and successfully exploit this
issue, it could have lead to arbitrary code execution and resulted in
unauthorized access with elevated privileges on the targeted system.
This vulnerability impacted only NetBackup server systems and did not
impact NetBackup client systems.
--------------------------------------------------------------------------------
Etrack Incident = ET432236
Description:
Corrected the use of access bits with the mailslot and with the storage
slots in the robotic libraries.
To correct this issue, add a wait before an eject for Vault-style ejects
for libraries that take extra long for the mailslot to come ready after
being accessed.
Additional Notes:
Access bit checking may require a new device_mappings file, it depends on
the robot.
--------------------------------------------------------------------------------
Etrack Incident = ET512890
Description:
Support 24 character drive serial numbers.
--------------------------------------------------------------------------------
Etrack Incident = ET523022
Description:
NetBackup Resource Broker (NBRB) may hang at startup time if database
records have been corrupted.
--------------------------------------------------------------------------------
Etrack Incident = ET511782
Description:
Thread handles were not being released properly in NBSL, when a new
thread pre-fetched a block of media and volume records from EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET522971
Description:
NBSL no longer sends deletion events for Jobs to NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET516605
Description:
Under certain conditions, NetBackup Job Manager (NBJM) runs out of
threads. As a result no new jobs can be initiated and the existing
jobs do not complete.
Workaround:
To avoid this issue, kill and restart the NBJM service.
--------------------------------------------------------------------------------
Etrack Incident = ET493991 ET431087
Description:
An Incremental NetBackup Catalog Backup ends up backing more data
than necessary.
NetBackup Catalog Backup was re-architected in NetBackup 6.0. The plan
was to also support NetBackup Catalog Move Detection. While supporting
that for UNIX by using ctime, in addition to mtime, for deciding on
which files to backup, inadverently opened the door for more directories
to be backed up, since the ctime gets changed for parent directories
of directories under which new catalog is being created. This resulted
in entire client catalog to be backed up again, if there was any other
backup done for that client.
The solution provided in this patch is to use NBU's existing TIR w/Move
Detection logic for NetBackup Catalog Move Detection.
--------------------------------------------------------------------------------
Etrack Incident = ET523400
Description:
In a cluster, Disk staging (duplication to tape) uses the local node name
as the media server instead of the virtual name. Because of this,
bpduplicate may fail with the error, “host is unreachable (47)”.
--------------------------------------------------------------------------------
Etrack Incident = ET496959
Description:
NetBackup Job Manager (NBJM) would deadlock or halt when the connection to
bpbrm breaks in the middle of a backup job.
--------------------------------------------------------------------------------
Etrack Incident = ET516377
Description:
NBPEM would crash if a thread referenced a deleted object. This is a
timing problem and can happen when:
- A thread decrements the ref count on an object
- The thread is stalled
- The object is destroyed (ref count = 0)
- The stalled thread starts running and it references the destroyed object
The above problem has been corrected by ensuring that the object is not
referenced after the reference count has been decremented.
--------------------------------------------------------------------------------
Etrack Incident = ET496074
Description:
Restores failed with the following errors in the job log and tar debug log:
job log:
22:16:27 (4753.046) data buffers out of sequence, expected number 157884,
received 157886
23:32:46 (4753.053) data buffers out of sequence, expected number 404927,
received 404932
debug log:
22:16:27 (4753.046) data buffers out of sequence, expected number 157884,
received 157886
23:32:47 (4753.053) data buffers out of sequence, expected number 404927,
received 404932
This issue occurred because the HP-UX 11.23 compiler optimized-out
references to the shared memory control variables.
--------------------------------------------------------------------------------
Etrack Incident = ET425567
Description:
Fixed memory leak in Policy Execution Manager. The leak occurred when
processing any configuration change event sent by NBNos, which passes a
sequence of name value pairs.
--------------------------------------------------------------------------------
Etrack Incident = ET516907
Description:
An exception occurred in NetBackup Generic Job (nbgenjob), where getting
a policy from nbproxy while performing a stream discovery forced a retry.
The first retry resulted in a core dump because the internal file list was
not cleared before rereading the STREAMS file. To resolve this core
problem, the stream discovery was changed to clear the internal file list
before reading the STREAMS file, and to only read the STREAMS file once.
--------------------------------------------------------------------------------
Etrack Incident = ET431505
Description:
Changed nbproxy to catch exceptions when either of the IOR files listed
below in the var directory are empty to prevent the Policy Execution
Manager (nbpem) from exiting on startup.
IOR files in var directory are:
- nbproxy_pem.ior
- nbproxy_pem_email.ior
Workaround:
To avoid this issue, remove the empty IOR files nbproxy_pem.ior and
nbproxy_pem_email.ior from the var directory. On UNIX, the var directory
resides in /usr/openv, and on Windows, it resides in VERITAS\NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET425565
Description:
For user and manual backups, changes have been made that prevent Policy
Execution Manager (nbpem) core dumps by fixing the message queue locking
function.
--------------------------------------------------------------------------------
Etrack Incident = ET423142
Description:
Fix CT_EXCHANGE backup job when streaming is not enabled. Changed Policy
Execution Manager (nbpem) to set stream number to zero for the child
CT_EXCHANGE job. Nbpem was setting it to -1, which made the delta time
option (-dt) that was passed to Bpbrm, zero.
--------------------------------------------------------------------------------
Etrack Incident = ET427069
Description:
Parent job (nbgenjob) did not detect that the Policy Execution Manager
(nbpem) went down so it waited indefinitely for a response. Changed
nbgenjob to ping nbpem using the birth time that was returned to determine
if Policy Execution Manager was running.
--------------------------------------------------------------------------------
Etrack Incident = ET518632
Description:
Fixed NetBackup Resource Broker (nbrb) so that it disconnects from
Sybase ASA when it receives a suspend before a cold catalog backup.
If nbrb does not disconnect from ASA, when Sybase ASA is shutdown for
the cold catalog backup, warnings similar to the following appear in
the Sybase server.log file: Connection terminated abnormally.
--------------------------------------------------------------------------------
Etrack Incident = ET498975
Description:
Idle media servers no longer go offline (such as, "ACTIVE-DISK", "OFFLINE").
--------------------------------------------------------------------------------
Etrack Incident = ET520924
Description:
The function, decree_host_unavailable, from NetBackup 5.x media servers
was causing the NetBackup 6.0 media servers to go offline.
--------------------------------------------------------------------------------
Etrack Incident = ET520279
Description:
The scanability setting of media servers in the EMM database is being
overwritten by the ltid processes of the media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET518557
Description:
Using the wizard to reconfigure NDMP-attached tape drives no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET519239
Description:
"bpexpdate –recalculate" and "bpexpdate -backupid" both allow image
expiration dates to be changed while an image duplication is in progress.
If the image spans tapes, this can result in different expiration dates
for the individual fragments.
Workaround:
To avoid this issue, do not run "bpexpdate –recalculate" or
"bpexpdate -backupid" while an image duplication is in progress.
--------------------------------------------------------------------------------
Etrack Incident = ET520937
Description:
This fix eliminates a program fault that attempts to get the media server
catalog path list from a NetBackup 5.x media server when the back-level
server has become unresponsive.
Workaround:
To avoid this issue, make certain all the back-level servers are
functioning.
--------------------------------------------------------------------------------
Etrack Incident = ET508741
Description:
Robot Name is now displayed correctly in NOM user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET517878
Description:
Over time, the NBJM process grew in size as jobs were run. The system was
configured to use security.
Workaround:
To avoid this issue, disable security or restart NBJM periodically.
--------------------------------------------------------------------------------
Etrack Incident = ET515457
Description:
Eliminated a potential memory leak when retrieving a list of hosts that
are sharing drives and list of shared drives in a master server domain.
--------------------------------------------------------------------------------
Etrack Incident = ET417455
Description:
BPTM may report an incorrect error at the end of some restore and
duplication jobs that is similar to the following error.
"invalid job id (805)"
--------------------------------------------------------------------------------
Etrack Incident = ET424097
Description:
Synthethic backups would fail or hang on Solaris systems with a low
resource limit for the maximum file descriptor. The bpsynth log would
contain the following:
ACEMsgTran::updateReactor_u: unable to register handle with the reactor
On a few HP-UX systems, bpsynth may core dump if the maximum file
descriptor resource limits are not configured properly.
Workaround:
To avoid this issue, configure the system so that the maximum number of
open files per process is at least 512.
--------------------------------------------------------------------------------
Etrack Incident = ET431087 ET493991
Description:
On UNIX platforms, the catalog moving detection that used ctime and mtime
in an incremental catalog backup, was not always reliable. This resulted
in backing up catalog files that were modified since the last full backup.
To resolve this issue, use the TIR moving detection capabilities in bpbkar
and remove the catalog moving detection code from the catalog backup
library.
--------------------------------------------------------------------------------
Etrack Incident = ET524813
Description:
For Disk-to-Tape duplications, with disk images that were fragmented,
several problems would occur, for example:
- Duplication operations would get this error, "unable to read bpduplicate
message, premature end of file encountered (errno = I/O error)", which was
incorrect.
- Duplication operations could inadvertently mix retention levels on the
output media.
Workaround:
To avoid these duplication issues, touch the following file:
/usr/openv/netbackup/NODTTSDUP.
--------------------------------------------------------------------------------
Etrack Incident = ET431511
Description:
After importing a certain type of NDMP backup, the restore would fail
because the NUM_FILES in the catalog image header was set to zero (0).
The cause was that bpdbm did not count the extra directory entries and
NDMP environmental variables during importing process.
--------------------------------------------------------------------------------
Etrack Incident = ET522253
Description:
Changes have been made the enables the use of FORCE_RESTORE_MEDIA_SERVER
for Basic Disk storage units.
--------------------------------------------------------------------------------
Etrack Incident = ET525778
Description:
Long delays, of as much as 20 minutes, can occur before the Policy
Execution Manager starts a job. The Policy Execution Manager submit
function calls hosts_equal, which sets the maxJobsPerClient value that
is sent to Job Manager, and this may cause a long delay if you have a
lot of clients that are not accessible.
To avoid a long delay in the job submission, you must first determine
if any client is timing out. To do this, change the Policy Execution
Manager debug level to 4 or higher so that the Policy Execution Manager
debug messages are displayed when setting the maxJobPerClient field
during job submission. The debug statements enable you to determine
which clients are timing out. A timeout condition means a client no
longer exists or it is not accessible. After you have determined which
client(s) is timing out, either remove the client from the policy or
make sure it is accessible.
--------------------------------------------------------------------------------
Etrack Incident = ET513067
Description:
Changes have been made to correct a potential core dump when attempting
to get an application cluster list.
--------------------------------------------------------------------------------
Etrack Incident = ET507870
Description:
The Media IDs were not converted to upper case correctly and caused
unexpected mismatches.
--------------------------------------------------------------------------------
Etrack Incident = ET524628 ET533634
Description:
Exchange Transportable backups would fail with a status 69 and resulted
in no parent jobs (nbgenjob) starting. To correct this problem, a changed
was made to the Policy Execution Manager to start a parent job (nbgenjob)
if the policy fields "frozenImage" and "off host backup" are enabled and
streaming is disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET524690
Description:
When executing update_clients to push NetBackup client software to a
Linux x86 machine running a 2.4 kernel, it may fail with a message
that libvxstlportST.so is busy. That library is now being installed
as libvxstlportST.so_new and has been added to move_libs similar
to how some other key binaries are handled.
--------------------------------------------------------------------------------
Etrack Incident = ET525328
Description:
update_clients currently fails when using the <HW> <OS> method of
execution. The check that caused this error has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET527265
Description:
If USE_VXSS is set to automatic, it was possible that a copy of the
originator credential would be leaked when negotiating a secure
connection. In addition, an address buffer is no longer leaked if an
insecure connection is received.
--------------------------------------------------------------------------------
Etrack Incident = ET523630
Description:
On HP-UX IA64 platforms, the command bpclntcmd -ip <xxx.xxx.xxx.xxx> would
return the following:
unrecoverable, sorry
host <xxx.xxx.xxx.xxx>: not found.
Changes have been made to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET514064
Description:
Changes have been made to eliminate a code vulnerability that would lead
to a potential core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET527481
Description:
NBJM no longer leaks small amounts of memory while running multi-streamed
jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET512447
Description:
A failed bmrsavecfg on the client will now correctly show a non-zero
status in the job monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET429756
Description:
A change has been made to resolve the problem of media remaining mounted
after a synthetic backup. This would only happen if the following
conditions applied:
- The incremental image is very small (assuming the image is on A00001)
- The mount of tape for writing fails the first time (for example, the
tape A00002 was selected first and then the mount of this tape failed).
- The tape, given for the write (the second time after the mount failure)
is the same as the one where the small incremental image exists
(such as, A00001 in this case).
--------------------------------------------------------------------------------
Etrack Incident = ET495489
Description:
A non-multiplexed duplication of a TIR backup written to tape would fail
if the last fragment was zero bytes in length.
--------------------------------------------------------------------------------
Etrack Incident = ET527391
Description:
A potential race condition existed in which the log roll-over at midnight
in ltid could cause NBAC-related log messages to be written to the wrong
file descriptor.
--------------------------------------------------------------------------------
Etrack Incident = ET507962
Description:
bprd has a relatively large memory footprint at start up.
Workaround:
To avoid this issue, do not save large number of VxUL logs.
--------------------------------------------------------------------------------
Etrack Incident = ET521857
Description:
The NOM server no longer consumes large amounts of memory during the
Media Data Load. Part of this problem was caused by NBSL returning all
the media data to NOM when NOM reconnected instead of changing media data.
To resolve this issue, a change was made to the media collector design so
that NBSL sends only changed media instead of all media.
--------------------------------------------------------------------------------
Etrack Incident = ET519432
Description:
Deleting media by volume group would not update the conflicts flags in
EMM_Media.UpgradeConflictsFlag.
--------------------------------------------------------------------------------
Etrack Incident = ET509879
Description:
Changes have been made that prevent a user from configuring devices,
media, media pools, and barcode rules after an upgrade from NetBackup 5.x
to NetBackup 6.0 until nbpushdata has been run.
--------------------------------------------------------------------------------
Etrack Incident = ET526256
Description:
Changes have been made to improve the policy data collection's performance.
--------------------------------------------------------------------------------
Etrack Incident = ET492321
Description:
Fixed an issue with AIX 5.3 and later so that ACLs are now correctly
backed up and restored.
--------------------------------------------------------------------------------
Etrack Incident = ET519253 ET530848
Description:
Bpverify limits the amount of errors it logs to a maximum of 10 entries.
In certain cases, it is useful to log all of the errors and to be able to
manually adjust the catalog file to allow a successful restore. A new
option, -dml, was added to bpverify that disables the maximum amount of
error logging.
--------------------------------------------------------------------------------
Etrack Incident = ET355520
Description:
If a backup mounts a filesystem in bpstart_notify, starts a backup, and is
interrupted, it will not be able to unmount the fileystem in a bpend_notify
script.
--------------------------------------------------------------------------------
Etrack Incident = ET522347
Description:
A 134 status code (unable to process request because the server resources
are busy) was occasionally reported incorrectly as a 24 status code
(socket write failed). This issue could cause a job to fail instead of
being retried if resources were available.
--------------------------------------------------------------------------------
Etrack Incident = ET421374
Description:
Backups no longer fail with a status 12 because it could not open a
NetBackup-created file.
--------------------------------------------------------------------------------
Etrack Incident = ET521820
Description:
The NOM server no longer becomes unstable while retrieving catalog data.
--------------------------------------------------------------------------------
Etrack Incident = ET528831
Description:
The NOM media summary page no longer counts incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET529847
Description:
A change was made to eliminate a code vulnerability/error that would
cause a process core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET530131
Description:
Setting "RANDOM_PORTS = NO" in bp.conf prevents "nbpushdata -add" from
working.
Workaround:
To avoid this issue, do not use RANDOM_PORTS=NO.
--------------------------------------------------------------------------------
Etrack Incident = ET514845 ET530821 ET530802
Description:
In environments where DNS is not available for fully resolving a host's
name, NBAC would require additional configuration steps. Therefore, in
some cases, it is not possible to get NBAC to work.
Workaround:
In some cases it is possible to specify the correct fully-qualified host
name with the bpnbat and bpnbaz command lines. The user is prompted for
the correct value when a problem is found in this regard.
Additional Notes:
A new command line has been added for bpnbat. The bpnbat -ShowMachines
command displays the exact names of the Machine principals that were
added with bpnbat -AddMachine. This indicates whether or not a Short Host
name has been resolved. It also enables the user to see which machines
have thus far been added to the NBAC machine list.
--------------------------------------------------------------------------------
Etrack Incident = ET514845 ET530821
Description:
In environments where DNS is not available for fully resolving a host's
name, NBAC would require additional configuration steps. Therefore, in
some cases, it is not possible to get NBAC to work.
Workaround:
In some cases it is possible to specify the correct fully-qualified host
name with the bpnbat and bpnbaz command lines. The user is prompted for
the correct value when a problem is found in this regard.
Additional Notes:
A new command line has been added for bpnbat. The bpnbat -ShowMachines
command displays the exact names of the Machine principals that were added
with bpnbat -AddMachine. This indicates whether or not a Short Host name
has been resolved. It also enables the user to see which machines have
thus far been added to the NBAC machine list.
--------------------------------------------------------------------------------
Etrack Incident = ET497075
Description:
When submitting a user, archive, or manual backup job with NONE specified
for the progress log, a progress log in the root directory /NONE is
created. Changed bprd to not set progress log parameter passed to Policy
Execution Manager if NONE specified.
--------------------------------------------------------------------------------
Etrack Incident = ET524767
Description:
When bprestore is run with the option to wait for the completion of the
restore job, a firewall between bprestore and bprd can shut down the
socket. This causes bprestore to wait for the completion status which
never comes.
Workaround:
Increase the timeout on the firewall.
--------------------------------------------------------------------------------
Etrack Incident = ET516108
Description:
The VxFS named data-stream processing caused a debug log error when
performing Advanced Client for DB2 backups. The backup completes
successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET519732
Description:
Image header files do not have the correct permissions and are world
writeable in NetBackup 6.0.
Workaround:
Permission on the image files can be changed using operating system tools.
A cron or at job could be used to automate this functionality. Other
options could include automating this with a bpend script.
Additional Notes:
After installation of NetBackup 6.0 MP2, please change the permission of
the appropriate header file to 644.
--------------------------------------------------------------------------------
Etrack Incident = ET519795
Description:
When running a backup with a large number of streams, the image header
files may not be removed correctly from the tmp directory when the image
is validated. This will cause a bpverify request to read the image header
twice - once from the parent directory and once from the tmp directory.
It will see twice the number of expected files and fail to verify the
image.
Additional Notes:
This patch also addresses a similar issue with deleted image header files,
where the image header file is not successfully deleted initially, and is
retained until a subsequent clean-up operation is done.
--------------------------------------------------------------------------------
Etrack Incident = ET523646
Description:
Master server went offline in NOM even though
master servers were running fine.
--------------------------------------------------------------------------------
Etrack Incident = ET530110
Description:
You can now copy and paste file names between include/exclude lists and an
external application like Notepad, in the Host Properties Include/Exclude
page for a Windows client.
Additional Notes:
Following new I18N messages have been added:
- Copy
- Paste
- Change
--------------------------------------------------------------------------------
Etrack Incident = ET492363
Description:
Entire HostSession was being destroyed if error in any single manager.
--------------------------------------------------------------------------------
Etrack Incident = ET416423
Description:
If you create a DB2 policy using a backup script whose name contains
Chinese characters and then run the backup, the backup fails with a
status of 6.
Workaround:
To avoid this issue, modify the path name to not include four-byte,
Chinese characters or include more non Chinese characters.
--------------------------------------------------------------------------------
Etrack Incident = ET530318
Description:
The bpcoverage binary crashes in NetBackup 5.1 MP4 .
Workaround:
To avoid this issue, use the bpcoverage binary prior to NetBackup 5.1 mp4.
--------------------------------------------------------------------------------
Etrack Incident = ET517651 ET526726 ET526745
Description:
Added a software utility (nbsupport 2.1.1) that creates a support package
that consists of multiple reports most often asked for by NetBackup support
personnel.
--------------------------------------------------------------------------------
Etrack Incident = ET526967
Description:
A problem would occur when an Archive was run using NBWin. There was a
change in the behavior that caused data loss when only one file exists
within the directory at the start of an archive job and new files were
added to that directory before the archive completed. BPCD showed that
at the end of the job, the archive was called with 'rm -rf' that removed
the directory and all files resulting in a data loss of the new files
added.
--------------------------------------------------------------------------------
Etrack Incident = ET521720
Description:
one can see many nbproxy.exe hanging around even
after the destruction of its Manager or nbsl.exe itself
--------------------------------------------------------------------------------
Etrack Incident = ET517955
Description:
NBSL no longer sends invalid fields in the Job and Job-attempt data.
--------------------------------------------------------------------------------
Etrack Incident = ET521892
Description:
Running asyncronous I/O on large files can lead to delays in servicing
requests. The design should have handled this uncommon issue, however,
if an error, such as a read error, was encountered with an errno of
EAGAIN, it was treated as a generic error instead of a retry, so the
backup failed.
Workaround:
To avoid this issue, turn off asyncronous I/O.
--------------------------------------------------------------------------------
Etrack Incident = ET497175
Description:
Added new PC-x64 client type.
--------------------------------------------------------------------------------
Etrack Incident = ET517406
Description:
Multiple leak issues in TAO have been fixed in this maintenance pack.
--------------------------------------------------------------------------------
Etrack Incident = ET532659
Description:
The SG driver can cause a kernel panic due to a NULL pointer dereference.
--------------------------------------------------------------------------------
Etrack Incident = ET522386
Description:
An issue existed where in some cases, a job would not schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET497997 ET500067 ET506604 ET515440 ET523577 ET526811 ET533446
ET530687 ET395009 ET401372 ET413319 ET413325 ET413510 ET418654 ET492409 ET426777
ET536105
Description:
Added support for the following libraries:
- ADIC FastStor 2.1
- ADIC FastStor2
- BDT ThinStor
- Copan VTL
- Fujitsu LT270
- NETAPP VTL
- Overland Reo 4000 VTL
- Quantum DLT V4
- Quantum PX50
- Sony CSM-20
Added support for the following drives:
- Exabyte VXA-2
Updated the following libraries:
- Exabyte 480
- HP A5597A
- Quantum MSL6000
Updated the following drives:
- STK T10000
--------------------------------------------------------------------------------
Etrack Incident = ET425635
Description:
This maintenance pack contains error handling enhancements for license
failures in vlteject, vltinject, and vltopmenu.
--------------------------------------------------------------------------------
Etrack Incident = ET533242
Description:
Changes were made to the notify scripts to only call “date” once for
performance reasons. In addition, changes were made to add the missing
parent_start_notify and parent_end_notify scripts that the parent job
(nbgenjob) uses.
--------------------------------------------------------------------------------
Etrack Incident = ET527834
Description:
The NetBackup API that retrieves Catalog DB images was not returning
records in the ascending order of date (backuptime). This caused a
problem because NOM requires the backuptime to be in the ascending order
of date.
--------------------------------------------------------------------------------
Etrack Incident = ET533333
Description:
Hot Catalog Backups were taking too long. For a customer that has a very
large catalog (about 44GB) that contains about 117000 file list entries
(for image catalog directives), the backups were taking in excess of
24 hours.
Workaround:
To avoid this issue, run cold catalog backups, if the hot catalog backups
take too long.
--------------------------------------------------------------------------------
Etrack Incident = ET496741 ET537300 ET570640
Description:
Backups with infinite retention use a specific expiration date value to
mark them as infinite retention. This value was changed in the
NetBackup 6.0 release to deal with some limitations in third party
components. This new value created some reporting issues for backups
that were done on or reported using media servers with the NetBackup 5.0
or 5.1 versions. The backups would be listed as expiring on a specific
date, rather than showing "INFINITY" as their expiration date. This pack
addresses the third party date limitations and reverts the value used to
designate infinite retention to the pre-NetBackup 6.0 value.
--------------------------------------------------------------------------------
Etrack Incident = ET520323
Description:
Windows Hot Catalog Backups would periodically fail with a
status 67: client backup failed to read the file list. This only
occurred if there were client names with multiple underscore ("_")
characters in their NetBackup policy definitions.
Workaround:
To avoid this issue, rename the clients defined in NetBackup backup
policies to client names without underscore characters.
--------------------------------------------------------------------------------
Etrack Incident = ET414828
Description:
This pack contains a fix to a memory leak in Policy Execution Manager when
reading a policy or when sending mail upon job completion (for example,
when the mailAdmin field is specified).
Workaround:
A partial workaround for this issue is to not set the mailAdmin field in
the policy so that no mail will be sent upon job completion.
--------------------------------------------------------------------------------
Etrack Incident = ET519705 ET519368
Description:
After some amount of time, NetBackup EMM would become unresponsive;
requests to EMM would timeout. To corret this issue, the rollovermode is
set to the filesize (which is the default NetBackup configuration).
--------------------------------------------------------------------------------
Etrack Incident = ET533725
Description:
Corrected a problem that caused NBJM to crash intermittently. The problem
was caused by two threads working on the same object concurrently.
--------------------------------------------------------------------------------
Etrack Incident = ET422446
Description:
Corrected the drive unload function in acstest.
--------------------------------------------------------------------------------
Etrack Incident = ET533119
Description:
A change has been made to bpdbjobs to ignore PROCESS lines that appear in
trylogs before the Try line to insure that the correct data is interpreted.
--------------------------------------------------------------------------------
Etrack Incident = ET534333
Description:
Multiple changes have been added to handle a number of sscanf() calls in an
effort to gaurd against potential problems that are similar to buffer
overflow issues.
--------------------------------------------------------------------------------
Etrack Incident = ET532668
Description:
A TIR backup would create a corrupted tape image if the amount of TIR data
received did not match the amount expected.
--------------------------------------------------------------------------------
Etrack Incident = ET407677 ET432231 ET493475 ET493479
Description:
Vault components are now supported in an NBAC environment.
--------------------------------------------------------------------------------
Etrack Incident = ET533084
Description:
If an inline tape copy backup job was suspended before the first
checkpoint was taken and subsequently resumed, the job failed to start.
--------------------------------------------------------------------------------
Etrack Incident = ET530747
Description:
BPTM would sometimes corrupt the on-disk image when recovering from a
disk-full condition. To encounter this problem, a backup policy that uses
inline copy and multiplexing to a DSU/DSSU must be active.
--------------------------------------------------------------------------------
Etrack Incident = ET534512
Description:
Exchange VSS restores were failing because of a regression that was
introduced in an earlier release.
--------------------------------------------------------------------------------
Etrack Incident = ET535998
Description:
"bpdbm -consistency 2", useful to check database consistency, no longer
fails.
--------------------------------------------------------------------------------
Etrack Incident = ET496660
Description:
If a backup image was the same exact size as the defined max fragment size,
a zero-length fragment would be listed in the image header and cause bpdm
to hang while attempting to read the fragment.
--------------------------------------------------------------------------------
Etrack Incident = ET431225
Description:
When a disk full condition occurred while writing the fragment header, an
error would also occur during the same period that did not get cleared and
caused all eligible image candidates to be deleted beyond the disk storage
unit’s low water mark.
--------------------------------------------------------------------------------
Etrack Incident = ET538466
Description:
If a single job in a multiplexed group received a 41 status error
(network connection timed out), then all of the jobs in the group would
incorrectly error with this same status.
--------------------------------------------------------------------------------
Etrack Incident = ET539671
Description:
A change has been made to set the debuglogday to currentlogday every time
the debug log file is opened. For robust logging, this fix creates the
first log file for the current day. For legacy logging, this fix prevents
the current log file from getting reopened for every debug log entry.
Workaround:
To resolve this issue, touch the next file in the sequence, then the
robust logging starts to write to the newly created log file.
--------------------------------------------------------------------------------
Etrack Incident = ET534453
Description:
Shared standalone drives did not work if media servers were started while
a tape was loading.
--------------------------------------------------------------------------------
Etrack Incident = ET535036
Description:
A change has been made to resolved an nbproxy build break in addition to
a race condition error in nbsl.
--------------------------------------------------------------------------------
Etrack Incident = ET540019
Description:
NetBackup Catalog images are now retrieved in ascending order.
--------------------------------------------------------------------------------
Etrack Incident = ET539558
Description:
A change was made to greatly reduce the startup time for multi-stream
backup jobs with many streams.
--------------------------------------------------------------------------------
Etrack Incident = ET540913
Description:
An immediate backup would cause the removal and rebuilding of jobs in the
work list, even if the policy has not been changed, resulting in delays
with starting the jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET540910
Description:
The startup time of backup jobs would slow down when entries existed in
the client database.
--------------------------------------------------------------------------------
Etrack Incident = ET514169
Description:
The pack install provides customers with a new option to perform cleanup
of previously saved patch images. This will alleviate concerns because
of an increased footprint and full replacement of all NetBackup client
binaries in maintenance packs. The pack installer will present an
additional prompt on every install to enable or disable this feature.
--------------------------------------------------------------------------------
Etrack Incident = ET538179 ET534458 ET538172 ET538164 ET537437 ET537416 ET537513
ET537486 ET537664 ET537522 ET537530 ET537476 ET537539 ET537559 ET542506 ET536735
Description:
Multiple buffer overflow vulnerabilities have been identified in daemons
that run on Veritas NetBackup master, media, and client servers. An
attacker, if able to access a vulnerable Veritas NetBackup server and
successfully exploit these issues, could potentially execute arbitrary
code resulting in possible unauthorized and elevated privilege access
to the targeted system.
For more information about this vulnerability, refer to TechNote 281521 on
the Symantec Support Web site (http://support.veritas.com/docs/281521).
--------------------------------------------------------------------------------
Etrack Incident = ET540445
Description:
Directory paths longer than 1024 characters can cause a core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET539395
Description:
A lock was inadvertently removed in DeviceManagerImpl::getEventChannel ()
that caused a race condition when invoking the
CollectorBase::getEventChannel () call. This lock has been added back
in to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET542685
Description:
The catalog cleanup process was not resetting the image header level
expiration date on a multi-copy image when the first copy expired. This
caused the expiration date for the image to be incorrectly reported.
This problem affects only image reporting, because the determination to
retain data is based on the copy-level expiration date.
Workaround:
This pack will ensure that the catalog cleanup operation correctly sets
the image header level expiration date. Additionally, it will ensure that
queries against images that were affected by the original problem will
return the correct expiration date. Images affected by the original
problem may continue to show an incorrect expiration date and primary
copy when viewed through a text editor, but will be handled correctly by
the application.
--------------------------------------------------------------------------------
Etrack Incident = ET542894
Description:
A change has been made that enables you to do a Media Freeze and
Unfreeze in NOM user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET413496
Description:
Added an ACS toolkit port to the ACS toolkit 2.3.
Added ACS support to Linux IA64 and HP-UX IA64.
Additional Notes:
HP-UX IA64 does not currently support ACS_TCP_SERVICE mode which also
means there is no ACS firewall support for HP-UX IA64. Symantec is
working with Hewlitt Packard to acquire a new operating system library
for this support.
--------------------------------------------------------------------------------
Etrack Incident = ET541879
Description:
Added support for the new Quantum DLT-S drives.
--------------------------------------------------------------------------------
Etrack Incident = ET533487
Description:
A change has been made to correct known NBSL core dump issues.
--------------------------------------------------------------------------------
Etrack Incident = ET545651
Description:
A scan-host failover to the NDMP path caused the drive to be DOWNED.
--------------------------------------------------------------------------------
Etrack Incident = ET544406
Description:
Backups of Windows clients using standard encryption would corrupt the
backup image. This caused some restores from this image and bpverify to
fail.
--------------------------------------------------------------------------------
Etrack Incident = ET546171
Description:
Added a configurable option to disable validation of the host name
(chars used to form the name).
--------------------------------------------------------------------------------
Etrack Incident = ET541896
Description:
Changes were made to correct core dump issues when performing a
bpdbjobs –cancel function.
--------------------------------------------------------------------------------
Etrack Incident = ET541878
Description:
Changes were made to correct core dump issues when performing a
bpdbjobs -report -all_columns function.
--------------------------------------------------------------------------------
Etrack Incident = ET419277
Description:
Reduced the number of times bpdbm reads NetBackup configuration information.
--------------------------------------------------------------------------------
Etrack Incident = ET541505 ET566045
Description:
Enhanced the level of support for multi-NIC authentication brokers
under NBAC.
--------------------------------------------------------------------------------
Etrack Incident = ET546839
Description:
Back-level media servers remote scanning drives that are active on 6.0
media servers, may cause the drive to be downed on the scan host.
--------------------------------------------------------------------------------
Etrack Incident = ET542650
Description:
Added "-move" into the "bpdbm -consistency" check to explicitly move out
the corrupted catalog images. "bpdbm -consistency" no longer moves
corrupted images without the option being explicitly specified.
--------------------------------------------------------------------------------
Etrack Incident = ET565075
Description:
Changes have been made to resolve an NBSL core dump on an AIX 5.3 master
server.
--------------------------------------------------------------------------------
Etrack Incident = ET579151
Description:
Drive status info (i.e. EVSN, RVSN, Labelled, Ready) not showing up
in device monitor and vmoprcmd output.
================================================================================
=========
NB_60_1_M
==========
Etrack Incident = ET415495
Description:
Do not allow a down/disabled media server to block the entire Device
Allocator (DA) thread pool.
--------------------------------------------------------------------------------
Etrack Incident = ET423713
Description:
There were a few places in the code where the image query protocol version
was set to 0, which is a pre-NetBackup 5.0 image version ID. Some image
queries would fail if the size of the total data being backed up was larger
than 2TB in one job.
This issue has been corrected enabling image queries on backups greater
than 2TB work properly.
--------------------------------------------------------------------------------
Etrack Incident = ET424051
Description:
A change has been made to avert a potential vulnerability in a Java
authentication service that runs on Veritas NetBackup servers and clients.
This change prohibits remote attackers from executing arbitrary code on a
targeted system. In addition, Symantec recommends that users block the
affected ports from external network access.
--------------------------------------------------------------------------------
Etrack Incident = ET423045
Description:
When sharing tape drives between media servers that were running both
NetBackup 6.0 and NetBackup 5.x, a problem existed with the NetBackup 6.0
Scan Hosts. If the drive being scanned was assigned to a 5.x media server,
the 6.0 Scan Host might not stop scanning. This resulted in SCSI
reservation conflicts and DOWN'ed drives on the NetBackup 5.x assigned host.
Workaround:
To avoid this issue, do not share drives between media servers running
different versions of NetBackup. Instead, pool your drives such that all
of your NetBackup 5.x media servers are sharing one pool of drives and all
of your NetBackup 6.0 media servers are sharing a pool of different drives.
--------------------------------------------------------------------------------
Etrack Incident = ET422837
Description:
When running multi-streamed Windows Open File Backup backups to back up
open and/or active files, some VSP cache files in the format of
_vxfiVspCacheFile_1.VSP, for example, may have been left behind by the
backup jobs that had already completed. This did not occur with
non-streamed backup jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET428719
Description:
Because of a logic error in the handling of "bptm –delete_all_expired",
the expired media was not getting deleted. This would prevent recycling
of the media.
Workaround:
To avoid this issue, the user can expire the media using bpexpdate.
--------------------------------------------------------------------------------
Etrack Incident = ET424660
Description:
If a hot catalog backup fails and retries, an end of session function is
executed when jobs are still active. This could result in extra catalog
backups to run, extra start and session scripts to run in addition to
extra catalog cleanup operations.
--------------------------------------------------------------------------------
Etrack Incident = ET429008
Description:
When upgrading from NetBackup 5.x to NetBackup 6.0, the
NETBACKUP_RELATIONAL_DATABASE_FILES directive was not added to the list of
files included in cold catalog backup. The command, bpsyncinfo -add_paths,
"NETBACKUP_RELATIONAL_DATABASE_FILES" is run automatically during patch
installation to add this directive to the cold catalog backup configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET421370
**Description:
The NBDB database recovery (for Enterprise Media Manager (EMM) and Bare
Metal Restore (BMR)) will fail if the master server has a newer catalog
backup image than the one used in disaster recovery (DR). On Windows
platforms, it logged an error message in the progress log and displayed an
error message box. On UNIX platforms, because of a defect in the Java
user interface, it reported an error message in the log and all of the
restore jobs appeared in the job monitor as being successful.
Additional Notes:
This maintenance pack enables a user to recover from an older catalog
backup even though a newer catalog backup image exists on the master
server.
Full catalog disaster recovering from an older catalog backup is a
“roll-back” operation that has the risk of data loss. Users should fully
understand the implications and use it with caution.
--------------------------------------------------------------------------------
Etrack Incident = ET431863
Description:
For a Hot Catalog Backup, the relational database (NBDB/Sybase ASA) backup
job treated a cumulative and differential incremental backup the same and
only included the transaction log in the backup. This can create problems
recovering the ASA database if the differential backup media created before
the last cumulative has expired. These differential backups contained the
transaction logs that were necessary to roll forward from the last full
backup.
Workaround:
To resolves this issue, the cumulative incremental backup is actually a
full backup for the ASA files.
--------------------------------------------------------------------------------
Etrack Incident = ET406999
Description:
Transport of log messages from NBSL to NOM Server was failing and causing
the Host Session to go down. PSP's TAO_Transport was not checking for
EAGAIN.
--------------------------------------------------------------------------------
Etrack Incident = ET428760
Description:
The vmd process would dump core if the EMM service (nbemm) was not running.
--------------------------------------------------------------------------------
Etrack Incident = ET425765
Description:
The nbpushdata function failed when a pool name had a hyphen in the actual
pool name.
--------------------------------------------------------------------------------
Etrack Incident = ET492438
Description:
Data tapes are no longer treated as cleaning tapes and be FROZEN by
NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET494547
Description:
Device monitor showed the same tape mounted in multiple drives. This tape
in this scenario was also assigned to a NetBackup 5.x media server.
Workaround:
To avoid this issue, do not share drives between NetBackup 6.0 media
servers and NetBackup 5.x media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET492704
Description:
A Null Reference Exception is produced when creating a custom filter for
the Driver Detail table (Monitoring -> Drivers -> Details table).
--------------------------------------------------------------------------------
Etrack Incident = ET425186
Description:
Oracle backups no longer end prematurely with a status 25.
--------------------------------------------------------------------------------
Etrack Incident = ET495004
Description:
The nbpushdata function failed with the following messages in the
nbpushdata log file:
<4> get_host_info: CEMM_MACHINE_DISK_ACTIVE being set for <your_host>
<16> emmlib_UpdateHost: (0) UpdateMachine failed, emmError = 2007079,
nbError = 0
<16> get_host_info: (-) Translating
EMM_ERROR_SQLSyntaxErrorOrAccessViolation(2007079) to 193 in
the media context
--------------------------------------------------------------------------------
Etrack Incident = ET418546
Description:
The NOM database server uses less CPU utilization over GA.
--------------------------------------------------------------------------------
Etrack Incident = ET495339
Description:
The Windows Open File Backup was not showing retries in the Activity
Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET495403 ET497074
Description:
For media with image expiration set to infinity, nbpushdata passed an
incorrect value for infinity to the EMM database. This resulted in the
media not being queried.
nbemmcmd -listmedia -mediaid <media_id> NBEMMCMD, Version:6.0(20050906)
The function returned the following failure status:
generic EMM SQL error (193)
Command did not complete successfully.
vmquery -m <media_id>
Could not query by media ID A00001 with debug: generic EMM SQL error (193)
--------------------------------------------------------------------------------
Etrack Incident = ET425768
Description:
An issue in nbpushdata caused the nbpushdata –remove function to fail.
Workaround:
To avoid this issue, drop the EMM data base and then recreate it.
--------------------------------------------------------------------------------
Etrack Incident = ET496010
Description:
Restores failed with the following errors in the job log and tar debug log:
job log:
22:16:27 (4753.046) data buffers out of sequence, expected number 157884,
received 157886
23:32:46 (4753.053) data buffers out of sequence, expected number 404927,
received 404932
debug log:
22:16:27 (4753.046) data buffers out of sequence, expected number 157884,
received 157886
23:32:47 (4753.053) data buffers out of sequence, expected number 404927,
received 404932
This issue occurred because the HP 11.23 compiler optimized out references
to the shared memory control variables.
--------------------------------------------------------------------------------
Etrack Incident = ET425178
Description:
Data Lifecycle Manager consolidation jobs now complete successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET430806 ET419127
Description:
Changed bprd and the Policy Execution Manager (PEM) so that the bprd child
could terminate and not wait for the job exit status from PEM, unless
the -w flag was used on the request.
--------------------------------------------------------------------------------
Etrack Incident = ET493607
Description:
Could not inventory legacy TS8 libraries as TL8.
--------------------------------------------------------------------------------
Etrack Incident = ET497080
Description:
If any inetd entry is missing on a client and update_clients is used to
push NetBackup client software to it, update_clients will show an error
message in the log file. A change was made that corrected the temporary
file names so that inet.conf on the client will be updated properly and no
error will be generated.
--------------------------------------------------------------------------------
Etrack Incident = ET497761
Description:
An extremely heavy load in the Device Allocator (DA) may cause EMM to crash.
--------------------------------------------------------------------------------
Etrack Incident = ET496437
Description:
Some vital logs were not displaying correctly. To be more specific, the
form that Log:DbLogMsg is being called in the emmserver source files was
incorrect whenever it was multi-lined in the code. As a result, only part
of the log message survived and important log information was lost.
--------------------------------------------------------------------------------
Etrack Incident = ET496608
Description:
Non-robotic tape drives that contain unlabelled media will no longer be
automatically assigned to non-robotic media specific mount requests.
--------------------------------------------------------------------------------
Etrack Incident = ET498523
**Description:
In a rare condition one or more backups would be corrupt when using Inline
Tape Copy (ITC) with multiplexed backups. This would potentially happen
under the following conditions:
- ITC was enabled with two or more active copies.
- Multiplexing was enabled with two or more active backups.
- The schedule configuration had the "continue if the copy fails" flag set
for the copy that failed in the next step.
- A copy other than the first active copy encountered an "end of media", so
a new media was needed for this copy. In addition, there was a problem
of getting or setting up media (for example, writing the media header)
such that this copy failed before continuing the backup.
- The last buffer written to the first active copy prior to the "end of
media" on the other copy was not the first active backup.
Workaround:
To avoid this problem, do one of the following:
- Edit the schedule configuration to disable the "continue if copy fails"
flag.
- Disable multiplexing.
- Disable ITC.
--------------------------------------------------------------------------------
Etrack Incident = ET423206
Description:
The back-level media server V_QUERY_CLEAN_BYROBNUM request caused an SQL
error.
--------------------------------------------------------------------------------
Etrack Incident = ET424796
Description:
NetBackup Job Manager (NBJM) deadlocks or halts when the connection to
bpbrm breaks in the middle of a backup job.
--------------------------------------------------------------------------------
Etrack Incident = ET431510
Description:
On initial install the Policy Execution Manager failed to start the first
time because no IOR file existed for nbproxy. Once an IOR file existed
and it is not empty, then the NetBackup Service Monitor was able to restart
the Policy Execution Manager.
Workaround:
To avoid this issue, delete the IOR files listed below before starting the
Policy Execution Manager.
On UNIX:
/usr/openv/var/nbproxy_pem.ior
/usr/openv/var/nbproxy_pem_email.ior
On Windows:
Veritas\NetBackup\var\nbproxy_pem.ior
Veritas\NetBackup\var\nbproxy_pem_email.ior
--------------------------------------------------------------------------------
Etrack Incident = ET425564
Description:
The Policy Execution Manager would crash after submitting a user-directed
or manual backup.
--------------------------------------------------------------------------------
Etrack Incident = ET499610
**Description:
Synthetic backup had potential data loss issues in following cases:
- The last full/synthetic or full expired/deleted occurred,
followed by one or more incrementals and a synthetic backup.
- The last incremental/full backup catalog was compressed before
next incremental backup took place.
- The TIR records in the last incremental backup are missing for
various reasons.
--------------------------------------------------------------------------------
Etrack Incident = ET505873
Description:
Media servers sharing drives on versions of NetBackup older than
NetBackup 6.0 will receive host_not_registered errors when attempting to
determine if another media server is unavailable.
--------------------------------------------------------------------------------
Etrack Incident = ET506551 ET499474 ET506690
Description:
This entry resolves three seperate issues described in the following list:
- Under certain conditions backups would not schedule. This happened
because of a problem in computing the next time a job was due. Windows
were not processed correctly if a backup should have run in a previous
window if the next window opened or closed at a different time.
- Advanced client VSS snapshot backup no longer causes an 805 error to
occur.
- The scheduler always executes Full backups, even for incrementals, if the
BMR option is on. nbpem would use the wrong criteria for the last
backup query made for a parent job that did not have multiple data
streams enabled. The result was no last full backup being found, so a
full would be run instead of an incremental.
--------------------------------------------------------------------------------
Etrack Incident = ET496102
Description:
As the number of VxUL log files grew, the start-up performance of bprd
would degrade.
Workaround:
To avoid this issue, delete the log files on a regular basis.
--------------------------------------------------------------------------------
Etrack Incident = ET506045
Description:
nbpushdata was using emmlib_DeleteHost to remove the NDMP host when the
following error occurred in the nbemm log. The following is a portion of
the log associated with the delete. Although log-level 6 was used, it
appeared that some log messages were missing.
11/11/05 15:54:41.185 [Debug] NB 51216 nbemm 111 PID:13393 TID:1196157872
[No context] 1 [DbConnection::Execute] SQL - retval=2007085(2007085)
retdal=-1native=<-143> sqlerror=<[Sybase][ODBC Driver][Adaptive Server
Anywhere]Column 'FQMachineName' not found> sqlstate=<42S22>
--------------------------------------------------------------------------------
Etrack Incident = ET507645
Description:
In certain cases, when NetBackup Access Control is enabled, long-lived
processes such as nbemm, nbpem, nbjm, nbrb, nbproxy, nbsl and vmd would
leak memory.
--------------------------------------------------------------------------------
Etrack Incident = ET500006
Description:
The Policy Execution Manager VxUL message catalog was missing some messages
causing it to crash when trying to log the new messages.
--------------------------------------------------------------------------------
Etrack Incident = ET500061
Description:
SQL SERVER backup completes normally but the client interface Displayed
a -1 status. This was caused by improper progress log updates.
--------------------------------------------------------------------------------
Etrack Incident = ET509509
Description:
When spanning media, jobs occasionally appeared to be hung and the request
was continually failing with the message, "ROBOTIC LIBRARY IS DOWN ON
SERVER". This would happen after an earlier failure causing the message,
"MEDIA SERVER IS CURRENTLY NOT CONNECTED TO MASTER SERVER". However, the
media server properly showed the robot as up and the host as ACTIVE or
ACTIVE-TAPE.
--------------------------------------------------------------------------------
Etrack Incident = ET509293
Description:
The NetBackup Service Layer (NBSL) occasionally sent negative values for
freespace and totalcapacity of a storage unit (if the values are greater
than 2^32-1).
--------------------------------------------------------------------------------
Etrack Incident = ET508191
Description:
vmd now retries the connection to EMM forever, instead of shutting down
if it cannot connect to EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET511728
Description:
From the NOM user interface, it is not possible to start the service/deamon
when NetBackup is on a UNIX Operating System.
--------------------------------------------------------------------------------
Etrack Incident = ET512560
Description:
It is now be possible for SAN media servers to be used as write hosts for
duplicate jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET510335
Description:
VxUL queries were failing on AIX platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET510255
Description:
Appending parentheses in the NOM filtering criteria is no longer an issue.
--------------------------------------------------------------------------------
Etrack Incident = ET510415
Description:
New DRIVE and ROBOT Reports have now been created along with multiple
entries for some column names.
--------------------------------------------------------------------------------
Etrack Incident = ET512866
Description:
Removed change events for Error LogMonitoring. For example, error log
collection functionality is removed. In addition, the getLogMessages()
idle method supports the error log source too; thus, NOM will call this
method for getting error logs. Finally, the getEventChannel()
functionality has been removed, resulting in an AFException.
Additional Notes:
Because of this fix, log monitoring of NOM 6.0 MP1 will only work with
NetBackup 6.0 MP1.
--------------------------------------------------------------------------------
Etrack Incident = ET513093
Description:
vmscd no longer dumps core. This occurred because vmscd received an invalid
drive type for one of the drives while polling the drive status and vmscd
was not handling the invalid drive type properly.
--------------------------------------------------------------------------------
Etrack Incident = ET513390
Description:
The NetBackup Notification Service (NBNos) was running in single-threaded
mode.
--------------------------------------------------------------------------------
Etrack Incident = ET514603
Description:
Change made to bpexpdate such that media IDs that are less than six
characters returned from EMM were not padded with spaces. This caused
bpexpdate -deassignempty to mistakenly deassign media that still had
valid images on them.
Workaround:
To avoid this issue, turn off the automatic start of
bpexpdate -deassignempty by performing one of the following items:
- On a UNIX master servers, create the file,
/usr/openv/netbackup/bin/bpsched.d/CHECK_EXPIRED_MEDIA_INTERVAL,
and enter a 0 (zero) on the first and only line of the file.
- On a Windows master server, create the file,
<install_path>\NetBackup\bin\bpsched.d\CHECK_EXPIRED_MEDIA_INTERVAL,
and enter a 0 (zero) on the first and only line of the file.
--------------------------------------------------------------------------------
Etrack Incident = ET514622
Description:
An NBSL core dump happened while stopping it when it was connected to a
client (NOM). The core dump would occur on Solaris and AIX platforms.
On Windows platforms, it would hang in a 'stopping' state in the Windows
Service Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET515553 ET515559
Description:
vmscd, before the fix, was a single process and it used to service
requests from the EMM server synchronously. Because of this, the EMM server
was not receiving the request response in a timely manner. In some cases,
the EMM server would think that vmscd had exited and which then triggered
certain operations that were redundant, and in some, cases harmful.
--------------------------------------------------------------------------------
Etrack Incident = ET511340
Description:
Several issues have been fixed that related to back-level SSO
interoperability:
- Numerous re-registrations were consuming all of vmd's bandwidth on
the EMM server.
- Registration failures due to no scan host setting registration retry
timer which would block back-level servers from releasing drives.
- Back-level remote scanning of NetBackup 6.0 media servers was failing
with ENOTSCANHOST and forcing still more re-registrations.
Workaround:
To avoid these issues, do not share drives between NetBackup 6.0 and
NetBackup 5.X media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET516440
Description:
nbemm no longer core dumps on a clustered master server.
--------------------------------------------------------------------------------
Etrack Incident = ET516103
Description:
Vault can fail while logging very long strings.
Workaround:
Disable Vault logging.
--------------------------------------------------------------------------------
Etrack Incident = ET515838
Description:
When the parent job (nbgenjob) performed stream discovery and it received
an exception asking for policy information through nbproxy, it would then
perform several retries. On the first retry attempt the parent job would
core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET429245
Description:
On HP-UX platforms, scheduled backups with file lists that contain
multi-byte characters failed with an error 71 (None of the files in the
files list exist). On the Activity Monitor, the multi-byte characters
were unreadable in the file lists within job properties.
Workaround:
To prevent this issue, please apply the following patches:
- HP-UX 11.23
Patch Name: PHCO_30072
Patch Description: s700_800 11.11 iconv cumulative patch
- HP-UX 11.11
Patch Name: PHCO_29903
Patch Description: s700_800 11.11 iconv cumulative patch
- HP-UX 11.00
Patch Name: PHCO_29924
Patch Description: s700_800 11.00 iconv cumulative patch
================================================================================
Attachments
|
|
Related Articles
Legacy ID
290380
Article URL http://www.symantec.com/docs/TECH52949
Terms of use for this information are found in Legal Notices
Thank you.