Maintenance Pack NB_60_3_M.alpha_5.tar provides fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 on TRU 64 servers. NetBackup UNIX Add-on products, Database Agents and Java GUI have separate Maintenance Packs.
| Article:TECH48334 | | | Created: 2006-01-29 | | | Updated: 2006-01-13 | | | Article URL http://www.symantec.com/docs/TECH48334 |
Problem
Maintenance Pack NB_60_3_M.alpha_5.tar provides fixes for Veritas NetBackup (tm) Enterprise Server / Server 6.0 on TRU 64 servers. NetBackup UNIX Add-on products, Database Agents and Java GUI have separate Maintenance Packs.
Solution
NB 6.0GA Pack NB_60_3_M
README
June 29, 2006
Requirement: NB_CLT_60_3_M
Corequirement: NB_BMR_60_3_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.
Symantec recommends that the backing up of active file systems be avoided,
or the use of snapshot technologies be implemented. The directory structure
reported back from the file system (to NetBackup) may not contain all of the
files available during the time of backup. NetBackup will not report errors
in many cases where the file's existence is not known to NetBackup as reported
by the file system.
================================================================================
=================
PACK DEPENDENCIES
=================
-- NB_CLT_60_3_M_<6 digit number>.tar must be installed before this
Maintenance Pack is installed.
-- Only if Bare Metal Restore is installed,
NB_BMR_60_3_M_<6 digit number>.<platform>.tar must be installed after
this Maintenance Pack is installed.
-- Installation of this Maintenance Pack requires version 1.33.4.13 of
the Vrts_pack.install script.
-- 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.
NOTE: The UNIX CLT pack, which is required to be installed with this server
pack, requires approximately 1.5-2GB in disk space to extract and install.
The CLT pack is a full replacement of all client binaries for all platforms.
For more information, please refer to the following TechNote:
http://seer.support.veritas.com/docs/280824.htm
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_3_M
Pack History
NB_60_2_M
NB_60_1_M
====================================
I. PRIMARY MAINTENANCE PACK UPDATES
====================================
This section identifies the primary changes, maintenance updates, and
enhancements that are contained in this Maintenance Pack.
- Sun cluster version 3.1 updates
- Oracle 10gR2 on Windows x64
- NetApp P2 concurrent transfers
- Improved ACS/TLH support
- BMR WinPE
NOTE: Symantec recommends that you refer to the NetBackup 6.0 Operating System
Compatibility Matrix for the latest information regarding supported
features: http://support.veritas.com/menu_ddProduct_NBUESVR_view_CL.htm
=========================
II. DOWNLOAD INSTRUCTIONS
=========================
1) Download the NB_CLT_60_3_M_<6 digit number>.tar and
NB_60_3_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_3_M_<6 digit number>.tar has the client binaries and
NB_60_3_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_3_M_<6 digit number>.<platform>.tar into the /tmp directory
and download and extract the NB_BBS_60_3_M_<6 digit number>.<platform>.tar
into the /tmp directory.
2) Extract the NB_CLT_60_3_M_<6 digit number>.tar and the
NB_60_3_M_<6 digit number>.<server>.tar files.
tar xvf NB_CLT_60_3_M_<6 digit number>.tar
tar xvf NB_60_3_M_<6 digit number>.<server>.tar
NB_60_3_M will create the files:
VrtsNB_60_3_M.README
VrtsNB_60_3_M.<server>.tar.Z
VrtsNB_60_3_M.preinstall
VrtsNB_60_3_M.preuninstall
VrtsNB_60_3_M.postinstall
VrtsNB_60_3_M.postuninstall
Vrts_pack.install
NB_CLT_60_3_M will create the files:
VrtsNB_CLT_60_3_M.README
VrtsNB_CLT_60_3_M.tar.Z
VrtsNB_CLT_60_3_M.preinstall
VrtsNB_CLT_60_3_M.postinstall
VrtsNB_CLT_60_3_M.postuninstall
Vrts_pack.install
==================
III. KNOWN ISSUES
==================
On certain AIX systems, the server pack (NB_60_3_M.rs6000.tar) may fail to
install due to a tar extract error. Therefore, on AIX it is recommended
that the two following steps be taken if this occurs, or even as a
preventive measure prior to running Vrts_pack.install:
-- /usr/openv/netbackup/bin/bp.kill_all
-- /usr/sbin/slibclean
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.
=============================
IV. INSTALLATION INSTRUCTIONS
=============================
NOTE: Click on the "Download Now" link, near the bottom of this document
prior to running the following installation procedure for this pack.
NOTE: Symantec recommends that you perform catalog backups before and after
you apply this maintenance pack.
NOTE: 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.
For Maintenance Pack installation on a UNIX Cluster Environment:
--------------------------------------------------------------------------------
1) Ensure that prior to installing the maintenance pack, NetBackup is at
release level 6.0 and configured to run in a cluster.
2) Freeze the NetBackup group (This will avoid a 'failover' during a patch
installation).
3) Install this Maintenance Pack on the inactive node(s) of the cluster
(follow steps 1-3 below).
4) Install this Maintenance Pack on the active node of the cluster (follow
steps 1-3 below).
5) Unfreeze the NetBackup group.
--------------------------------------------------------------------------------
As root on the NetBackup Master Server:
1) Install NB_60_3_M and NB_CLT_60_3_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.
2) 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
3) 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 = 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
================================================================================
============
Pack History
============
=========
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 NBU 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 NBU 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_3_M
Corequirement: NB_BMR_60_3_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.
Symantec recommends that the backing up of active file systems be avoided,
or the use of snapshot technologies be implemented. The directory structure
reported back from the file system (to NetBackup) may not contain all of the
files available during the time of backup. NetBackup will not report errors
in many cases where the file's existence is not known to NetBackup as reported
by the file system.
================================================================================
=================
PACK DEPENDENCIES
=================
-- NB_CLT_60_3_M_<6 digit number>.tar must be installed before this
Maintenance Pack is installed.
-- Only if Bare Metal Restore is installed,
NB_BMR_60_3_M_<6 digit number>.<platform>.tar must be installed after
this Maintenance Pack is installed.
-- Installation of this Maintenance Pack requires version 1.33.4.13 of
the Vrts_pack.install script.
-- 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.
NOTE: The UNIX CLT pack, which is required to be installed with this server
pack, requires approximately 1.5-2GB in disk space to extract and install.
The CLT pack is a full replacement of all client binaries for all platforms.
For more information, please refer to the following TechNote:
http://seer.support.veritas.com/docs/280824.htm
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_3_M
Pack History
NB_60_2_M
NB_60_1_M
====================================
I. PRIMARY MAINTENANCE PACK UPDATES
====================================
This section identifies the primary changes, maintenance updates, and
enhancements that are contained in this Maintenance Pack.
- Sun cluster version 3.1 updates
- Oracle 10gR2 on Windows x64
- NetApp P2 concurrent transfers
- Improved ACS/TLH support
- BMR WinPE
NOTE: Symantec recommends that you refer to the NetBackup 6.0 Operating System
Compatibility Matrix for the latest information regarding supported
features: http://support.veritas.com/menu_ddProduct_NBUESVR_view_CL.htm
=========================
II. DOWNLOAD INSTRUCTIONS
=========================
1) Download the NB_CLT_60_3_M_<6 digit number>.tar and
NB_60_3_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_3_M_<6 digit number>.tar has the client binaries and
NB_60_3_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_3_M_<6 digit number>.<platform>.tar into the /tmp directory
and download and extract the NB_BBS_60_3_M_<6 digit number>.<platform>.tar
into the /tmp directory.
2) Extract the NB_CLT_60_3_M_<6 digit number>.tar and the
NB_60_3_M_<6 digit number>.<server>.tar files.
tar xvf NB_CLT_60_3_M_<6 digit number>.tar
tar xvf NB_60_3_M_<6 digit number>.<server>.tar
NB_60_3_M will create the files:
VrtsNB_60_3_M.README
VrtsNB_60_3_M.<server>.tar.Z
VrtsNB_60_3_M.preinstall
VrtsNB_60_3_M.preuninstall
VrtsNB_60_3_M.postinstall
VrtsNB_60_3_M.postuninstall
Vrts_pack.install
NB_CLT_60_3_M will create the files:
VrtsNB_CLT_60_3_M.README
VrtsNB_CLT_60_3_M.tar.Z
VrtsNB_CLT_60_3_M.preinstall
VrtsNB_CLT_60_3_M.postinstall
VrtsNB_CLT_60_3_M.postuninstall
Vrts_pack.install
==================
III. KNOWN ISSUES
==================
On certain AIX systems, the server pack (NB_60_3_M.rs6000.tar) may fail to
install due to a tar extract error. Therefore, on AIX it is recommended
that the two following steps be taken if this occurs, or even as a
preventive measure prior to running Vrts_pack.install:
-- /usr/openv/netbackup/bin/bp.kill_all
-- /usr/sbin/slibclean
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.
=============================
IV. INSTALLATION INSTRUCTIONS
=============================
NOTE: Click on the "Download Now" link, near the bottom of this document
prior to running the following installation procedure for this pack.
NOTE: Symantec recommends that you perform catalog backups before and after
you apply this maintenance pack.
NOTE: 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.
For Maintenance Pack installation on a UNIX Cluster Environment:
--------------------------------------------------------------------------------
1) Ensure that prior to installing the maintenance pack, NetBackup is at
release level 6.0 and configured to run in a cluster.
2) Freeze the NetBackup group (This will avoid a 'failover' during a patch
installation).
3) Install this Maintenance Pack on the inactive node(s) of the cluster
(follow steps 1-3 below).
4) Install this Maintenance Pack on the active node of the cluster (follow
steps 1-3 below).
5) Unfreeze the NetBackup group.
--------------------------------------------------------------------------------
As root on the NetBackup Master Server:
1) Install NB_60_3_M and NB_CLT_60_3_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.
2) 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
3) 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 = 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
================================================================================
============
Pack History
============
=========
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 NBU 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 NBU 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
284108
Article URL http://www.symantec.com/docs/TECH48334
Terms of use for this information are found in Legal Notices
Thank you.