Maintenance Pack NB_60_7_M.winnt.x64.exe provides fixes to the Veritas NetBackup (tm) Enterprise Server / Server 6.0 on Windows XP/2003 X64 server and clients. It also contains fixes for NetBackup Add-on products and Database Agents.

Article:TECH63285  |  Created: 2008-01-15  |  Updated: 2008-01-23  |  Article URL http://www.symantec.com/docs/TECH63285
Article Type
Technical Solution


Environment

Issue



Maintenance Pack NB_60_7_M.winnt.x64.exe provides fixes to the Veritas NetBackup (tm) Enterprise Server / Server 6.0 on Windows XP/2003 X64 server and clients. It also contains fixes for NetBackup Add-on products and Database Agents.

Solution



NB 6.0GA Pack NB_60_7_M README September 15, 2008
================================================================================
This Maintenance Pack provides fixes to the Veritas NetBackup(tm)
Windows x64-bit server and clients.

================================================================================


=================
PACK DEPENDENCIES
=================

-- 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.



I. NEW FEATURES AND PLATFORM PROLIFERATIONS
II. KNOWN ISSUES
III. DOWNLOAD INSTRUCTIONS
IV. INSTALLATION INSTRUCTIONS
V. UNINSTALL INSTRUCTIONS
VI. CURRENT MAINTENANCE PACK INDEX
VII. MAINTENANCE PACK CONTENT
Conventions
Current Maintenance Pack
NB_60_7_M
Maintenance Pack History
NB_60_6_M
NB_60_5_M
NB_60_4_M
NB_60_3_M
NB_60_2_M
NB_60_1_M


--------------------------------------------------------------------------------
The following information describes the upgrade and downgrade rules or scenarios
that apply to this maintenance pack.

- Upgrade scenarios:
The NetBackup 6.0 MP7 maintenance pack install:
- Can be applied on top of NetBackup 6.0 GA or any 6.0 MPx (prior to MP7).
- Cannot be applied directly to a NetBackup 5.x system. You must install
NetBackup 6.0 GA first.
- Cannot be applied directly to a NetBackup 6.0 MPx Beta system. (The
Beta version of NetBackup must be uninstalled first.)

- Downgrade scenarios:
If the NetBackup 6.0 MP7 maintenance pack is uninstalled, you will roll
back to the version you had previously installed prior to installing
this maintenance pack, (such as 6.0 GA or 6.0 MPx).



============================================
I. NEW FEATURES AND PLATFORM PROLIFERATIONS
============================================
This section describes the new UNIX and Windows features and platform
proliferations that are being released in NetBackup 6.0 MP7. The following lists
provide brief descriptions of the platform proliferations, and the new features.
For those new features that have more detailed information available, a link is
provided to a corresponding TechNote.


Platform Proliferations:
------------------------
This maintenance pack supports the following new platform proliferations.
Symantec recommends that you refer to the NetBackup 6.0 Operating System
Compatibility Matrix for the latest information regarding supported platforms:
http://entsupport.symantec.com/menu_ddProduct_NBUESVR_view_CL.htm

The following Operating System proliferations have been added with this release.

+ Added AIX 6.1 Client support.

+ Added support for OpenAFS 1.4.1 Client however, this release will not
support AES 128 Encryption.

The following database agent proliferations have been added in this release.

+ DB2 9.1 - AIX 6.1

+ Informix 11.1 - AIX 6.1, HP-UX PA-RISC 11.31, HP-UX IA64 11.31

+ Oracle 11G - AIX 6.1

+ Sybase 15 - AIX 6.1, HP-UX PA-RISC 11.31, HP-UX IA64 11.31




New Features and Enhancements:
------------------------------
This maintenance pack primarily focuses on fixes to known issues that
include customer-specific issues that have been documented in the form of
a Titan Case. This release does not contain any major new enhancements.




==================
II. KNOWN ISSUES
==================
This section contains known issues with this maintenance pack that have not
yet been fixed in NetBackup. These issues will likely be fixed in future
maintenance packs for this version of NetBackup.

+ The Veritas Private Branch Exchange (PBX) software is installed along with
Veritas NetBackup 6.0. Depending on how NetBackup is installed, PBX may log
messages by default to the UNIX system logs /var/adm/messages or
/var/adm/syslog, or to the Windows Event Log. This can cause additional
system logging that the system administrator may not desire. The messages
written to the system logs are the same as those written to the PBX logs
(/opt/VRTSpbx/log on UNIX and <install_path>\VxPBX\log on Windows).

To disable PBX logging to the system or event logs after NetBackup has been
installed, enter the following commands:

UNIX:
cd /opt/VRTSicsco/bin
./vxlogcfg -a -p 50936 -o 103 -s LogToOslog=false

Windows:
cd <install_path>\VERITAS\VRTSicsco
vxlogcfg �a �p 50936 �o 103 �s LogToOslog=false

It should not be necessary to restart PBX for this setting to take effect.
Any future PBX log information should no longer appear in the system logs.

For more information about this issue or information on how to disable the
option, refer to the following TechNote on the Symantec Support Web site.

http://entsupport.symantec.com/docs/280746

+ (ET1314642) An issue exists so that you are unable to stop the NetBackup
services using the NetBackup Administration Console on the master server.
For more detailed information about this issue and a possible work-around,
refer to the following TechNote on the Symantec Support Web site.

http://entsupport.symantec.com/docs/308303

+ (ET1365680) A Microsoft SharePoint issue exists that causes multiple
database site-redirect restores to fail to recover all sites. For more
detailed information about this issue and a possible work-around, refer
to the following TechNote on the Symantec Support Web site.

http://entsupport.symantec.com/docs/308304

+ (ET1297796) An error may occur when attempting to connect the restored
databases to the Microsoft SharePoint Portal Farm. For more detailed
information about this issue and a possible work-around, refer to the
following TechNote on the Symantec Support Web site.

http://entsupport.symantec.com/docs/308305

+ (ET1249029) Product dependency notification for customers running Microsoft
Windows Vista or Windows 2008 server.

If you are protecting client (or server) systems that are running either
Microsoft Windows Vista or Windows 2008 server, you may need to install
Microsoft hot-fix number KB952696. If you are attempting to back up any
protected files that have been encrypted by the operating system, NetBackup
will not be able to back these files up. NetBackup will report that it is
unable to access the encrypted files and the backup will continue with all
of the remaining files.

NOTE: This does not apply to NetBackup encryption. NetBackup encryption
is separate from the file system encryption, meaning NetBackup-encrypted
files will be backed up. In addition, this hot-fix is not needed for any
Windows version prior to Microsoft Windows Vista or Windows 2008 server. If
you are running Vista or Server 2008, please refer to KB952696 to see if
this hot-fix is required for your operating system version.

+ A failed NetBackup 6.0 MP4 install or uninstall may not rollback properly

During an install or uninstall process, if a failure occurs, it is normal
procedure for the installer to stop and begin a rollback operation. The
purpose of the rollback is to return NetBackup to your previously installed
version.

If a failure occurs during an install or uninstall of this maintenance pack,
the rollback may not complete properly. The following list describes how you
can determine if the rollback failed to complete properly:

- Open your Windows Explorer and verify that the �Product Versions� of the
files are not named with the current Maintenance Pack name. For
example, none of the files should have a product version name of 6.0MP4.

- After the rollback completes, try starting the EMM service. If it does
not run, then the rollback failed.

If you encounter any of these symptoms and need more information about this
issue and how to resolve it, refer to TechNote 285743 on the Symantec Support
Web site. You can also contact your Symantec Support representative for
assistance on regaining functionality within your system configuration.

+ Customers interested in the Bare Metal Restore (BMR) Boot Server, should
first install the BMR Boot Server, and then apply the NetBackup 6.0MP7 patch.

Customers that have already upgraded to NetBackup 6.0MP4 and are interested
in the BMR Boot Server, may do so by first installing the BMR Boot Server and
then replying the 6.0MP7 patch. The 6.0MP7 patch will not need to be
uninstalled prior to the installation of the BMR Boot Server.

+ When restoring on a Windows system that uses the Broadcom NetExtreme II chip
set, the Bare Metal Restore (BMR) cleanup process may hang. Self Restores that
use a "Current" Configuration will work. However, you may encounter problems
while attempting a Dissimilar Restores (DSR ) or a Self Restores using "copied"
configuration.

Before you attempt any such restores, Symantec recommends that you refer to
the following TechNote on the Symantec Support Web site for more details.
http://entsupport.symantec.com/docs/289611

+ For Volume Snapshot Provider (VSP) users, a reboot will be required before
the latest VSP fixes will take effect.

+ The NetBackup 6.0 Commands document contains some incorrect information for
the bplist command. The following accurately explains this command.

The bplist command shows a list of previously archived or backed up files
according to the options that you specify. You can choose the file or
directory and the time period that you want the listing to cover.
Directories can be recursively displayed to a specified depth.

The bplist command shows only the files that you have read access to. It
lists the files only if a user backup is performed by the user owning the
files (that is, an administrator account). A non-administrator or backup
operator cannot bplist the files. You also must own or have read access to
all directories in the file paths. You can list files that were backed up
or archived by another client only if you are validated to do so by the
NetBackup administrator.

If you create the following directory /usr/openv/netbackup/logs/bplist/
with public-write access, bplist creates an debug log file in this
directory that you can use for troubleshooting. The output of bplist goes
to standard output.

+ (ET1212445) NetBackup will not import tapes in an ACSLS library when the
barcode label is different than the media ID or recorded volume serial
number (RVSN). A mismatch occurs when the barcode and media ID do not
match in the volume database.

A mismatch can occur for multiple reasons. Two examples include:
1. When using tapes previously written by a different barcode, labels
are placed into an ACSLS library using a new barcode label.
2. The administrator attempts to change the media ID field (using
vmchange) to match the RVSN. In this example when the inventory is
updated, the barcode and media ID will be synchronized.

To be able to restore from these tapes, the media ID used when mounting
the tapes using the automatic cartridge system daemon (ACSD) needs to
match the recorded media ID as found in the header on the tape (RVSN).

The recommended approach is to use a barcode label that matches the
recorded media ID. Tapes can then be mounted in a drive with AVRD
running so that the recorded media ID is displayed. Then, a barcode
with that label needs to be placed on the tape. For more information
on how to resolve this issue, refer to the following TechNote on the
Symantec Support Web site.

http://entsupport.symantec.com/docs/279257

+ (ET1065162) A backup job that requires the use of the Storage Foundation for
Windows (SFW) 5.0 VSS (Volume Shadow Copy Service) may fail because of an
access violation issue. Applications that use this technology are the
NetBackup Advanced Client Backup and Alternate Client Backup features. For
more information on how to successfully perform a snapshot backup using the
SFW VSS method in NetBackup 6.0 MP7, refer to the following TechNote on the
Symantec Support Web site.

http://entsupport.symantec.com/docs/287298

+ (ET1013914) Installing a NetBackup 6.0GA BMR boot server on a system that
currently has NetBackup 6.0 MP7 installed, will not install correctly. When
this occurs, install the NetBackup 6.0 MP7 maintenance pack again, this time,
select the Repair option to reapply the BMR boot server binaries. After the
patch is reapplied, the command run the following command to register the
Boot Server.

<InstallDir>\Program Files\VERITAS\Netbackup\bin\bmrsetupboot.exe

+ (ET1065797) The NetBackup Administrator's Guide explains that list entries
that end with a backward slash (\) will exclude only directories with that
path name (for example, C:\users\test\). If the pattern does not end in \
(for example, C:\users\test), then NetBackup excludes both files and
directories with that path name. However, an issue exists where list entries
that do end in \ still cause the files and directories to be excluded.

In addition to this issue, the Backup, Archive and Restore (BAR) user
interface removes the trailing backslash to newly added entries after an
exclude entry has been entered in the Exclude field.

+ (ET1055007) For push installations, it is important to remember to have
NetBackup 6.0 MP7 uninstalled before you attempt to push NetBackup to other
machines.

+ (ET1058484) It is possible for the install process to fail if a service
was running during the install and caused a conflict to occur. If this
happens, manually stop the afflicting service and restart the install.

+ (ET1150218) A problem exists when attempting to perform Instant Recovery
backups on an SQL server. The problem occurs if you change the Instant
Recovery option in any automatic application schedule from the default value.
The default value is "Snapshots and copy snapshots to storage unit". Symantec
recommends that you do not change the value in the automatic schedule.

To avoid this issue and create a snapshot-only Instant Recovery for SQL
Server, you must set the application schedule to snapshot-only. (Select the
Instant Recovery option, Snapshot only".) Note, that any automatic schedules
that you create for the policy must remain at the default value, which is,
"Snapshots and copy snapshots to a storage unit."

+ (ET1178148) The Windows NetBackup Administration Console uses the operating
system functions within the SCM to determine what services are running. When
running under NBAC a user must also have the appropriate operating system
privileges to query the SCM to determine the state of the running processes.




==========================
III. DOWNLOAD INSTRUCTIONS
==========================
The following procedure explains how to download this maintenance pack, which
is an update to NetBackup/Media Manager products with the latest fixes for
Windows NetBackup servers.

Download instructions:
1) Download the NB_60_7_M.winnt.x64_<6 digit number>.exe file into a
temporary directory.

where <6 digit number> is an internal tracking identifier

2) Extract the NB_60_7_M.winnt.x64_<6 digit number>.exe by
double-clicking on it.

This will create a number of files that include:
README.x64
and
Setup.exe




=============================
IV. INSTALLATION INSTRUCTIONS
=============================
Before you install, review the following list of notes:

- When installing and uninstalling this pack, the instructions contained
in the Online Readme always supersede the instructions contained in the
installed version.

- Click on the "Download Now" link, near the bottom of this document
prior to running the following installation procedure for this pack.

- Symantec recommends that you perform a catalog backup before and after
you apply this maintenance pack.

For Maintenance Pack installation on Windows CLUSTER Environment:

1) Install this Maintenance Pack locally on the nodes of the cluster where
the NetBackup group is inactive. (follow steps 1-4 below)

NOTE: When installing on a VCS cluster, complete the installation of this
pack on a single node before you begin installing on another node.

2) Install this Maintenance Pack locally on the active node.
This should be done when the NetBackup system is quiet, for example,
no backups or restores running.

NOTE: Do not freeze or off-line the cluster before installing in a
clustered environment. The NetBackup maintenance pack installation
will perform these operations for you.

CAUTION: Do not failover the NetBackup Group until all NetBackup nodes
(including the active NetBackup node) have the maintenance pack
installed.

--------------------------------------------------------------------------------

Maintenance Pack Installation steps:

1) Close all NetBackup Windows.
Make sure the NetBackup system has no active backups, restores,
duplications, etc., running. If there are NetBackup activities in process,
the Maintenance Pack will require a reboot if the file to update is busy.

If a database client is being used, such as Oracle, ensure that the
database services are stopped. Database services can be stopped using the
ControlPanel -> Services tool. Repeat this until all databases have been
stopped. These services must be restarted once the patch is successfully
installed.

2) Run Setup.exe (Double-click on the icon from File Manager or Explorer or run
it from the command prompt)

Setup.exe begins by stopping the appropriate NetBackup Services required for
the Maintenance Pack installation. Next, it will install the necessary files
into their correct locations. Lastly, Setup.exe will restart the appropriate
NetBackup services.

3) Examine the install log located under the user profile that completed the
install. The following is an example of the user administrator that
completed the install. This path may be hidden and you may need to unhide
hidden or system files to view the log.

C:\Documents and Settings\administrator\Local Settings\Temp\
NetBackup Install...log

Search the install log for the following string to determine if an error has
occurred. "Return Value 3".

4) Remove the temporary directory created in the download instructions.

NOTE: If you are installing the Maintenance Pack using the silent install script,
please review the <TEMP>.Log after the installation is finished,
a reboot maybe required to complete the installation of the Maintenance Pack. A
search of the log for the key words "in use" will indicate which files were busy
during the installation.

NOTE: Symantec recommends that you perform a catalog backup after you have
applied this maintenance pack.

--------------------------------------------------------------------------------

The following procedure is only for users who want to install NetBackup 6.0 MP7
client on a Windows Vista system:

NOTE: Remote installations are not supported for Vista on Windows 32- and 64-bit
Systems.

To install NetBackup 6.0 MP7 client on a Vista system:
1. Install NetBackup 6.0 GA or 6.0 MP4 from a CD. You must use the custom
install option and choose to NOT to install VSP.
2. Install the NetBackup 6.0 MP7 pack.
3. If you are given a list of client platforms from which to select, select the
Windows 2003 with the chipset, either x86 or x64, that matches your system.

NOTE: After installing NetBackup on a Windows Vista client platform and starting
the Backup, Restore and Archive GUI, you may receive a dialog warning you
that the GUI is not compatible with Vista. You can disregard the warning
and proceed with using the GUI.

To add a Windows Vista client to a policy:
1. Create a Windows policy or use an existing Windows policy.
2. If you are given a list of client platforms from which to select, select the
Windows 2003 with the chipset, either x86 or x64, that matches your system.

To use Open File Backup:

1. VSP is not supported on Vista. If Open File Backup is enabled for a Vista
client (this is the default), VSS will always be used to create the snapshot.




=========================
V. UNINSTALL INSTRUCTIONS
=========================
To uninstall the Maintenance Pack from a Windows CLUSTER Environment:

NOTE: When uninstalling on a VCS cluster, complete the uninstall of this
pack on a single node before you begin uninstalling on another node.

1) Uninstall this Maintenance Pack from the nodes of the cluster where the
NetBackup group is inactive. (follow steps 1-2 below)

2) Uninstall this Maintenance Pack from the active NetBackup node.
This should be done when the NetBackup system is quiet, for example,
no backups or restores running.

CAUTION:
Do not failover the NetBackup Group until all NetBackup nodes (including
the active NetBackup node) have the Maintenance Pack uninstalled.


**Important notice regarding un-installs on Windows**
Only the last Maintenance Pack installed on a Windows system
can be un-installed.

1) Close all NetBackup Windows.
Make sure the NetBackup server has no active backups, restores,
duplications, etc., running. If there are NetBackup activities in process,
the Maintenance Pack will not install if the file to update is busy.

If a database client is being used, such as Oracle, ensure that the
database services are stopped. Database services can be stopped via the
Control Panel -> Services tool. Repeat this until all databases have been
stopped. These services must be restarted once the patch is successfully
uninstalled.

2) Go to Add/Remove programs dialog box and select the correct Pack to be
uninstalled.




==================================
VI. CURRENT MAINTENANCE PACK INDEX
==================================

This section contains a master index for all Windows packages of Etracks that
have been fixed in this release, sorted according to the containers that
they comprise.


NB_60_7_M.x64
-------------
1128726 1146635 1150657 1172971 1178481 1179426 1194284 1175361 1196200 1160439
1191148 1193696 1197056 1201124 1186553 1201301 1201289 1200945 1193183 1186256
1202780 1181024 1046203 1188094 1194900 1200911 1196151 1201741 1201794 1204133
1194711 1203203 1203315 1204149 1203341 855882 1196108 1206982 1198174 1149072
1203743 1206988 1209668 1141942 1210324 1181990 1205097 1028523 1193739 1196100
1180342 1202703 1213186 1210997 1213398 1212630 1213219 1194467 1198779 1208591
1186713 1159797 1215592 1213931 1146675 1213936 1217081 1019035 1003076 1199328
1173094 1200608 1211957 1175256 936910 1187728 1027786 1186721 1172465 1152587
1219899 1219751 1205924 1220903 1206849 1204494 852979 1168028 1190482 1223027
1223019 1222733 1213695 1202533 1204661 1222845 1222258 633166 1041153 1228196
1229928 1159536 1200897 1231109 1228989 1224637 1234803 1201393 1152608 1042411
1226336 1211653 1137917 1135737 1227823 814704 1175373 1236186 1237077 1237818
1209710 918372 1200166 1216170 1039111 1238630 1229969 1238369 1142467 1210594
1175891 1239178 1166277 1158729 420683 1236032 1214070 1235538 1227575 1232742
1240183 1233401 1239595 1242512 1145850 1235529 1195956 1245566 1244766 1245997
1244622 1226883 1224664 1221477 1036931 1200190 1249754 1245529 1252379 1089296
1251778 1252326 1219002 1252345 1257025 1259059 1257297 1195231 1260503 1259252
1262091 1150199 1240367 1261507 1261430 1239561 1254551 1269061 1209043 1273387
1235591 1223290 1174882 1275369 1134888 1269918 1261282 1097416 1275549 1239073
1278935 1281153 1271278 1211678 1270235 1283692 1253532 1283873 1283865 1275147
1277786 1077528 1189875 1227541 1190428 1291060 1260324 1287242 1292773 1296513
1294647 1291761 1297162 1295792 1298901 1302098 1251842 1316727 1316894 1314264
1321914 1364465 1178607 1361434 1385494




=============================
VII. MAINTENANCE PACK CONTENT
=============================
This section contains the Maintenance Pack conventions, content, and historical
content that is applicable to the release.

Conventions:
------------
The following list describes the conventions used in the subsections that
following this section. Each item listed in the Current Maintenance Pack
subsection describes a feature, enhancement, or issue fixed with this
Maintenance Pack.

Description
Describes a particular problem contained in this Maintenance Pack.

** Description **
Describes a problem that can lead to potential data loss. Please
read these problem descriptions carefully.

Workaround
Any available workarounds to a problem are also listed. Workarounds can be
used INSTEAD of applying the patch, however, 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 Maintenance Pack
------------------------
Each item listed in this section describes a feature, enhancement, or change
that comprises this Maintenance Pack. Please read this section thoroughly to
understand the contents of this update.
--------------------------------------------------------------------------------
Etrack Incident = ET1128726
Associated Primary Etrack = ET1125756
Titan cases: 320-063-046

Description:
The bprd daemon would prematurely terminate during startup if bpdbm took
too long to come up.
--------------------------------------------------------------------------------
Etrack Incident = ET1146635
Associated Primary Etrack = ET1112853
Titan cases: 281-124-171

Description:
The bpjava bplist protocol (BPRD_GET_BPLIST == 224 ) was not providing
results consistent with the 'mirror' bplist command. In addition, bpjava
could not handle the output of commands that were of 'largefile' size.
--------------------------------------------------------------------------------
Etrack Incident = ET1150657
Titan cases: 320-071-197

Description:
The bprd daemon would core dump after receiving a SIGPIPE and invoking an
undefined signal handler.

Additional Notes:
This problem has existed forever, and only it exposed itself through the
narrowest of timing windows.

Since bpcr is a library component, the negative effects transcend bprd
on Windows.
--------------------------------------------------------------------------------
Etrack Incident = ET1172971
Associated Primary Etrack = ET1162893
Titan cases: 240-666-528

Description:
The LIMIT_BANDWIDTH setting was not working on an HP-UX system that was
running on an IA64 platform. In addition, the THROTTLE was not defined,
as appropriate, on bpbkar invocations.
--------------------------------------------------------------------------------
Etrack Incident = ET1178481
Associated Primary Etrack = ET1175871
Titan cases: 290-898-929

Description:
A change has been made to ensure that a user is not able to log in and
run any UNIX OS command under a root account while being logged in as
a normal user.
--------------------------------------------------------------------------------
Etrack Incident = ET1179426

Description:
The ltid daemon would become unresponsive on a master server and cause the
master to be unavailable for tape backups. A change was made to ltid to
unlock shared memory before the EMM call, to avoid a deadlock with the
robotics parent process.
--------------------------------------------------------------------------------
Etrack Incident = ET1194284

Description:
Changes were added to address issues within the NetBackup Service
Layer (nbsl) that would cause it to crash.
--------------------------------------------------------------------------------
Etrack Incident = ET1175361

Description:
The user was unable to log in and use the NetBackup-Java Administration
Console because of the following error.
status: 511 NB-Java application server interface error

Additional Notes:
glibc would not accept multiple fclose() of the same stream.
--------------------------------------------------------------------------------
Etrack Incident = ET1196200

Description:
Jobs that were waiting for a retry are not terminating properly.
--------------------------------------------------------------------------------
Etrack Incident = ET1160439
Associated Primary Etrack = ET1086600
Titan cases: 281-150-442

Description:
Multiple streams would not go active from an RMAN client if the destination
was a NearStore storage unit (STU).
--------------------------------------------------------------------------------
Etrack Incident = ET1191148
Associated Primary Etrack = ET1170576
Titan cases: 320-063-472

Description:
In the NetBackup-Java Administration Console, the Activity Monitor backup
detail would not increment the percent complete. The percent complete goes
from 0% to 100% for multiplexing (mpx) jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1193696
Associated Primary Etrack = ET1191174
Titan cases: 311-794-388

Description:
The NetBackup Policy Execution Manager (nbpem) would abort (or core dump)
when performing pre-processing for a FlashBackup Windows policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1197056

Description:
A change was made to address an nbpem core dump that would occur on a
Solaris master server.

Workaround:
If you encounter this issue, and you have two hot catalog backup policies
created, do not delete the two backups within 10 minutes of each other.
--------------------------------------------------------------------------------
Etrack Incident = ET1201124

Description:
The stream discovery was not honoring the preprocess interval. A change
was made to the stream discovery to honor the preprocess interval on a
per-policy basis by creating a separate stream file for each policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1186553
Associated Primary Etrack = ET1166575
Titan cases: 290-896-837 320-074-061

Description:
Cold Catalog backups would run after user-backup jobs were complete even
though it was set to run after each session of scheduled backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1201301
Associated Primary Etrack = ET1122811
Titan cases: 230-430-097 281-211-845 290-845-354

Description:
The bpdbjobs output would truncate for the STARTED and ENDED fields.
--------------------------------------------------------------------------------
Etrack Incident = ET1201289
Associated Primary Etrack = ET1196977
Titan cases: 311-791-892

Description:
When performing Synthetic backups, bpdbjobs would report a blank for the
media server and storage unit.
--------------------------------------------------------------------------------
Etrack Incident = ET1200945
Associated Primary Etrack = ET999515
Titan cases: 281-010-333

Description:
The bpduplicate jobs would fail with a status code error 96. The log
file would end with the following line:

00:00:00 INF - Cannot obtain resources for this job : error [96]

A change was made to address failures that would occur with backups that
had True Image Restore (TIR) fragments that spanned media because of an
issue in the media reservation calculation.
--------------------------------------------------------------------------------
Etrack Incident = ET1193183
Associated Primary Etrack = ET1179480
Titan cases: 240-682-949

Description:
The command, tpconfig -add -drpath, will add paths with an invalid drive
status.

Workaround:
After adding the drive path, use the following command to "UP" the drive
path.

tpconfig -update -drpath -drstatus up
--------------------------------------------------------------------------------
Etrack Incident = ET1186256

Description:
Multiple data streams jobs would fail with an 815 status code, (retention
level mismatch).

Additional Notes:
When verifying this issue, the following conditions were required to
ensure the issue had been fixed:

- The policy is multi-streamed, checkpoint restart, full and incremental
schedule is set, and has it has more than 1 stream configured.
A storage unit must be disk based and the retention level is
different in the two schedules.
- Stream 1 succeeds.(full schedule)
- Stream 2 or higher fails with a disk full and exceeds failure
history. (full schedule)
- The incremental frequency is less than the configured time period.
- Moving the incomplete job to a done state is longer that the
incremental frequency.
- The parent job retries, however Stream 1 now tries to run an
incremental backup. (failure would occur)
--------------------------------------------------------------------------------
Etrack Incident = ET1202780

Description:
A change was made so a parent job (nbgenjob) can obtain the file list from
the job manager prior to executing the stream discovery step. This avoids
the file list from being empty and cause the job to fail with a 112 status.
--------------------------------------------------------------------------------
Etrack Incident = ET1181024
Associated Primary Etrack = ET1162500
Titan cases: 220-131-929

Description:
A -preview_range option has been added for the bpclimagelist command that
accepts a range of dates, versus a singular date that the -preview option
provides.

Additional Notes:
Like -preview, the -preview_range is not documented.
--------------------------------------------------------------------------------
Etrack Incident = ET1046203
Associated Primary Etrack = ET1014208
Titan cases: 230-276-677

Description:
A change was made that ensures the KEEP_LOGS setting works on client logs.
--------------------------------------------------------------------------------
Etrack Incident = ET1188094
Associated Primary Etrack = ET925827
Titan cases: 280-912-721

Description:
Catalog compression routines were attempting to compress images which had
been archived. This resulted in unnecessary entries in the NetBackup Error
report.
--------------------------------------------------------------------------------
Etrack Incident = ET1194900
Associated Primary Etrack = ET1194009
Titan cases: 281-270-328

Description:
When the client has multiple NIC cards, and the BMR client configuration
(on the server) is changed such that the first NIC entry has NULL values
for IP and netmask, preparing to restore with that configuration fails with
the following log error message on the boot-server:
"Unable to get Network information for Client <client_name>."

Workaround:
If you encounter this issue, check for NULL IP/netmask values that could be
removed and have been removed.
--------------------------------------------------------------------------------
Etrack Incident = ET1200911
Associated Primary Etrack = ET1114189
Titan cases: 220-091-399

Description:
Corrected an issue where TLDCD would lose a handle when attempting to talk
to a robot that was controlled through an NDMP filer and the robot was down.
--------------------------------------------------------------------------------
Etrack Incident = ET1196151

Description:
Backup of a volume to snapshot (with "Snapshot Only" set in the schedule)
would not run until a tape drive was available.
--------------------------------------------------------------------------------
Etrack Incident = ET1201741

Description:
Prepare to restore failed on a client that had shared (or restricted)
disks in VxVM disk groups when specifying a shared resource tree (SRT)
that did not contain VxVM and/or VxFS.

Workaround:
If you encounter this issue, install VxVM and/or VxFS into the shared
resource tree.
--------------------------------------------------------------------------------
Etrack Incident = ET1201794

Description:
If a shared resource tree (SRT) copy session was interrupted after the
destination directory for the ISO image was chosen, the proper cleanup
did not occur. The result was stale SRT entries were left in the database.

Workaround:
If you should encounter an issue like this, use one the following
commands to remove the stale SRT entries.
bmrs -o delete -r srt -name <SRTName>
or,
bmrsrtadm and choose to unlock and delete the SRT.
--------------------------------------------------------------------------------
Etrack Incident = ET1204133

Description:
Media mount operations would get core files from bptm if they were
canceled.
--------------------------------------------------------------------------------
Etrack Incident = ET1194711

Description:
A BMR parent job would fail with a status 96 error. After the error occurs,
and a child job waits for a retry, another parent job would start and
inherit the waiting child.
--------------------------------------------------------------------------------
Etrack Incident = ET1203203
Associated Primary Etrack = ET1198296
Titan cases: 290-887-434

Description:
The "exceeded configured number of tries" value was being written to the
error log for multistream parent jobs when it should not have been.
--------------------------------------------------------------------------------
Etrack Incident = ET1203315

Description:
Changes were made to correct Coverity issues.
--------------------------------------------------------------------------------
Etrack Incident = ET1204149
Associated Primary Etrack = ET1182905
Titan cases: 320-055-726

Description:
An issue existed where users were unable to cancel certain jobs and the
active job would exit with a status -1. A change has been made to address
this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1203341
Associated Primary Etrack = ET1164811
Titan cases: 290-847-180

Description:
bperror would report the following during a successful cold catalog backup
after an upgrade from NetBackup 6.0MP4 to 6.0MP5.

Failed to perform database backup
--------------------------------------------------------------------------------
Etrack Incident = ET855882

Description:
A change was made to the "Duplicate smaller images first" check box label
on the Vault Profile Duplicate tab. The label now reads, "Duplicate
smaller images first (applies only to disk backup images)". This change was
added so the user would understand why smaller tape images are not being
duplicated first and that this function only applies to disk backup images.
--------------------------------------------------------------------------------
Etrack Incident = ET1196108
Titan cases: 290-652-172

Description:
Changes were added to fix NBConsole crashes that would occur with the
Activity Monitor or when switching servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1206982

Description:
A change was made to the stream discovery in generic job (nbgenjob) so
that a job will fail with a 112 status if filelist is empty.

For example, a filelist such as "NEW_STREAM NEW_STREAM" will result in the
job failing with a 112 status instead of using the existing streams file.

Workaround:
To resolve this issue, remove any extra NEW_STREAM directives from the
file list that have no corresponding files.
--------------------------------------------------------------------------------
Etrack Incident = ET1198174
Associated Primary Etrack = ET1191488
Titan cases: 320-074-680

Description:
Shared NDMP drives with the same drive path on multiple hosts would only
show one host in the Device Monitor user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1149072
Associated Primary Etrack = ET1147612
Titan cases: 320-071-197

Description:
Jobs that failed with a status code 247 or 198 were not being passed by
the NetBackup Policy Execution Manager (nbpem) to the NetBackup Job
Manager (nbjm).
--------------------------------------------------------------------------------
Etrack Incident = ET1203743
Associated Primary Etrack = ET1195316
Titan cases: 311-783-307

Description:
A backup job with the DISABLE_JOB_LOGGING option enabled would fail with
a status 53.

Workaround:
If you encounter this issue, turn the DISABLE_JOB_LOGGING off.
--------------------------------------------------------------------------------
Etrack Incident = ET1206988
Associated Primary Etrack = ET1174189
Titan cases: 281-213-649

Description:
Backup jobs that were due would not be run. A change was made to pempersist
to ensure it is updated correctly upon completion of the jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1209668

Description:
A change was made that ensures the ocx gets unregistered properly and that
the proper message appears accordingly.
--------------------------------------------------------------------------------
Etrack Incident = ET1141942
Associated Primary Etrack = ET1046705
Titan cases: 240576707

Description:
Hot catalog recovery would display an error message when no actual error
occurred.

Additional Notes:
When no files were recovered because no files met the criteria, a large
warning would appear.
--------------------------------------------------------------------------------
Etrack Incident = ET1210324

Description:
A backup would fail trying to use unlabeled media that was placed in a
standalone drive.

Workaround:
To avoid this issue, label media using bplabel before its first use in a
standalone drive.
--------------------------------------------------------------------------------
Etrack Incident = ET1181990
Associated Primary Etrack = ET1181987

Description:
When a child job of a multistreamed job was canceled all peer child jobs
were canceled too.
--------------------------------------------------------------------------------
Etrack Incident = ET1205097
Associated Primary Etrack = ET1118180
Titan cases: 320-063-212

Description:
A change was made to address an issue that caused the NetBackup 6.0 MP5
nbpem startup to take more than two hours.
--------------------------------------------------------------------------------
Etrack Incident = ET1028523
Associated Primary Etrack = ET964511
Titan cases: 220-128-684 220-136-126 240411626

Description:
Enhancements were made to the performance of running the following
bpdbjobs command.
bpdbjobs -M <master> -report -all_columns
--------------------------------------------------------------------------------
Etrack Incident = ET1193739
Associated Primary Etrack = ET1187817
Titan cases: 281-276-313 290-860-580

Description:
A change has been made to enable large-file support while opening the error
logs: /usr/openv/netbackup/db/error/log_<ctime>.

Workaround:
If the daily error log grows larger than 2GB in size, you can remove or
rename it and then restart the daemons.
--------------------------------------------------------------------------------
Etrack Incident = ET1196100

Description:
For duplication, a bptm that does the write operation would crash on a
Windows media server if it could not open the file created by the read
operation bptm to get the shared memory information.
--------------------------------------------------------------------------------
Etrack Incident = ET1180342
Titan cases: 220-211-061

Description:
The Versioinfo.exe was not detecting all of the proper source files.

Workaround:
If you encounter an issue like this, use strings or a text editor to
search the file.
--------------------------------------------------------------------------------
Etrack Incident = ET1202703
Associated Primary Etrack = ET1183708
Titan cases: 311-776-100

Description:
The nbpemreq -updatepolicies command could not be run from the command
line with VxSS/NBAC enabled.

Workaround:
If you encounter this issue, disable NBAC.
--------------------------------------------------------------------------------
Etrack Incident = ET1213186

Description:
Changes were added to ensure issues found in NetBackup 6.0 MP6 are covered
in this release.
--------------------------------------------------------------------------------
Etrack Incident = ET1210997

Description:
The Policy Execution Manager would repeatedly start SharePoint jobs
because the SharePoint placeholder image was not validated. A change was
made to SharePoint to validate the SharePoint placeholder image.
--------------------------------------------------------------------------------
Etrack Incident = ET1213398

Description:
Snapshots were not being deleted for Windows Open File Backup (WOFB) jobs
that had streaming disabled. Now Policy Execution Manager (PEM) controls
the snapshot cleanup instead of bpbkar which then requires Job Manager to
save the snapshot ID to the params file so that when PEM calls Job Managers
expireJobResume() interface it can delete the snapshot using the snapshot
ID from the params file.
--------------------------------------------------------------------------------
Etrack Incident = ET1212630
Associated Primary Etrack = ET1211879
Titan cases: 281-285-629

Description:
Mirroring of a Solaris client VxVM encapsulated root disk to a second
disk fails. This happens after a BMR restoration where the original client
configuration is a two copy mirror and the mirror is broken in the
configuration because of dissimilar disk restore mapping. It exhibits the
following error (post-restore) after adding the mirror disk back into the
disk group:

# /etc/vx/bin/vxmirror -g rootdg -a
! vxassist -g rootdg mirror export
! vxassist -g rootdg mirror rootvol
! vxassist -g rootdg mirror swapvol
! vxbootsetup -g rootdg
VxVM vxmksdpart ERROR V-5-2-3612 Partition 0 is not available on device
c0t0d0s2

Workaround:
To resolve this issue, delete the VTOC on the second disk and re-initialize
the disk into the disk group with vxdiskadm.
--------------------------------------------------------------------------------
Etrack Incident = ET1213219

Description:
A user no longer needs to capture a screen shot of disk comparisons when a
restore triggers the auto-discovery mode.
--------------------------------------------------------------------------------
Etrack Incident = ET1194467 ET1198779

Description:
A change was made to address a bpjobd core dump issue originally discovered
on a Tru64 master server that actually spans all platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET1208591
Associated Primary Etrack = ET1208588

Description:
Versioninfo can sometimes report the incorrect version if Emergency
Engineering Binaries (EEBs) are present on the system.

Workaround:
If you encounter this issue, run strings or analyze the files manually to
determine what NetBackup static strings are present.

Additional Notes:
This only occurs in a very limited set of events.
--------------------------------------------------------------------------------
Etrack Incident = ET1186713

Description:
bpmedialist would list media multiple times if it was assigned to a cluster.
--------------------------------------------------------------------------------
Etrack Incident = ET1159797
Associated Primary Etrack = ET1159696
Titan cases: 220-129-851

Description:
An NBAC job (nbac_cron) fails with a "One or more of Name, Password and
domain are incorrect" error.

Workaround:
To resolve this issue, perform the following:

1. Run ./nbac_cron -Add[At|Cron]
Username: <user>
Password: <pass>
Password: <pass>
Access Control Group: <group>

2. Register account locally as root [Y/N]?: N <-- !!!!

3. Replace ./nbac_cron -Setup[At|Cron] with:
export VXSS_CREDENTIAL_PATH=~/.vxss/credential.crat
bpnbat -login
Broker: <broker>
Port: <enter, probably>
Authentication Type: vx
Authentication Domain: CronAt_<user> <-- same <user> as above
Name: CronAt_<user> <-- same <user> as above
Password: <pass> <-- same <pass as above Operation completed
successfully

4. Once this is finished, set the env var VXSS_CREDENTIAL_PATH as above
for the vbr agent.
--------------------------------------------------------------------------------
Etrack Incident = ET1215592

Description:
A change was made to address an NBEMM core dump issue (parallel requests
into a result set iterator).
--------------------------------------------------------------------------------
Etrack Incident = ET1213931
Associated Primary Etrack = ET1204166
Titan cases: 240-705-491

Description:
The EXCLUDE DATE was not being honored in a frequency-based schedule that
also use the nbpemreq -predict feature.
--------------------------------------------------------------------------------
Etrack Incident = ET1146675
Associated Primary Etrack = ET1143471
Titan cases: 281-221-795

Description:
Changing a machine's type would leave conflicting records in the database.
--------------------------------------------------------------------------------
Etrack Incident = ET1213936
Associated Primary Etrack = ET1181868
Titan cases: 290-861-616

Description:
After a NetBackup 6.0 MP5 upgrade, the multiple full schedules (for
example, a Monthly Full backup and a Weekly Full backup) would overlap and\
run on the last Saturday of the month. The expected behavior is that the
Monthly Full backup should run and the Weekly Full should not. A change has
been made to address this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1217081
Associated Primary Etrack = ET1154544
Titan cases: 220-122-694

Description:
A change has been made to provide the capability to reset an active drive.

Workaround:
If you encounter this issue, manually identify all jobs using a drive
(through the Activity Monitor or using nbrbutil) and remove those jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1019035

Description:
When trying to assign the pending request for mount and having the media be
write protected, an error stating, "EMM library call failure" occurs in the
user interface. The fact that the media is write protected is buried in the
volmgr/daemon log if that log exists.
--------------------------------------------------------------------------------
Etrack Incident = ET1003076 ET1199328

Description:
Changes have been made to address Coverity-reported issues.
--------------------------------------------------------------------------------
Etrack Incident = ET1173094

Description:
The revision strings were incorrect for some files in NBEMM.
--------------------------------------------------------------------------------
Etrack Incident = ET1200608
Associated Primary Etrack = ET1176914
Titan cases: 290-879-206

Description:
The Device configuration wizard in NetBackup Administration Console for
Windows would set ACS drives as standalone.
--------------------------------------------------------------------------------
Etrack Incident = ET1211957

Description:
The BPBRM started flag was not sent reliably to NBPEM from NBJM. Because
NBPEM needs to send administration emails (if configured), if BPBRM is not
started, duplicate emails were sometimes being sent.
--------------------------------------------------------------------------------
Etrack Incident = ET1175256

Description:
Upon Refresh, the Media listing would temporarily show an invalid error.
--------------------------------------------------------------------------------
Etrack Incident = ET936910

Description:
A change was made to correct the information displayed on Snapshot Policy
Configuration wizard summary screen.
--------------------------------------------------------------------------------
Etrack Incident = ET1187728

Description:
A correction was made to the user interface component controls for the
Attributes tab when creating a new schedule in an Instant Recovery policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1027786
Titan cases: 320-046-463

Description:
A correction was made that enables you to change the MPX value on the
policy schedules when viewing the policy details through the Summary of
all of the policies.
--------------------------------------------------------------------------------
Etrack Incident = ET1186721

Description:
The NetBackup Administration Console for Windows would show the frequency
of a catalog policy for an incremental schedule as either "0 hour" or as
"session end". The same is true for a hot catalog backup policy that is
scheduled to run after each backup session for a differential incremental
backup schedule.

A change has been made to ensure the Frequency column displays the value
for a catalog backup policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1172465

Description:
A change was made to display the correct start time in the Start Window tab
in Change Schedule window. The default start time should be 12.00A.M.
--------------------------------------------------------------------------------
Etrack Incident = ET1152587
Associated Primary Etrack = ET1142525
Titan cases: 311-685-600

Description:
bptm would generate a Dr. Watson error when drive cleaning was run on
NDMP drives. When attempting to run drive cleaning on an NDMP drive, the
cleaning job is completed with a status 0, but bptm would generate a
Dr.Watson log.
--------------------------------------------------------------------------------
Etrack Incident = ET1219899
Associated Primary Etrack = ET1220320
Titan cases: 220-216-339

Description:
The bppllist -inventory option would fail to detect deleted policies, and
schedule and clients that were deleted from clients.
--------------------------------------------------------------------------------
Etrack Incident = ET1219751
Associated Primary Etrack = ET1211325
Titan cases: 240-699-368

Description:
BMR would sometimes fail to restore clients with configurations that utilize
VxVM with disk multipathing (DMP) because it was not choosing a previously
active path to restore to.
--------------------------------------------------------------------------------
Etrack Incident = ET1205924
Associated Primary Etrack = ET1203294
Titan cases: 290-924-279

Description:
When performing a restore of an encrypted backup using the XBSA SDK, the
incorrect data size was returned if the data backed up was not a multiple
of 512 bytes.
--------------------------------------------------------------------------------
Etrack Incident = ET1220903
Associated Primary Etrack = ET1218116
Titan cases: 311-842-209

Description:
Offline catalog backups were failing with a status 124 when the IGNORE_XATTR
setting was configured on the Master server.

Workaround:
If you encounter this issue, remove the IGNORE_XATTR setting on the Master
server when performing the cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1206849
Associated Primary Etrack = ET1134318
Titan cases: 311-682-546

Description:
An SQL-Server Automatic job would unnecessarily allocate and unload a tape
which then affected current and other backups jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1204494
Associated Primary Etrack = ET1204113
Titan cases: 240-713-639

Description:
Individual file restores from Flashbackup images were failing with a
status 5 when a full path within the image exceeded 1024 characters.

Workaround:
To avoid this issue, perform a full restore of the image.
--------------------------------------------------------------------------------
Etrack Incident = ET852979

Description:
PEM additions to progress logs would allow users access to system files.
--------------------------------------------------------------------------------
Etrack Incident = ET1168028
Associated Primary Etrack = ET1143995
Titan cases: 230-438-228 290-891-616 290-913-205 320-080-024 220-107-441

Description:
Changes were added to ensure users who are using admin email and
multistreaming do not receive too many e-mails on a failed backup. In
addition, changes were made to ensure those users who use USEMAIL receive
the emails that they should receive.
--------------------------------------------------------------------------------
Etrack Incident = ET1190482 ET1223027

Description:
The NetBackup version was not set for cluster records.
--------------------------------------------------------------------------------
Etrack Incident = ET1223019

Description:
Resources were being leaked during device monitor fetches. The client
performing the fetches would crash in low memory situations.
--------------------------------------------------------------------------------
Etrack Incident = ET1222733
Associated Primary Etrack = ET1220159
Titan cases: 290-932-689

Description:
Moving from a smaller disk to a larger disk would fail in mklv allocation.

In the case of an AIX 5.3 client OS, if the original client rootvg was
installed on a smaller disk size of about 10GB and later during a restore
the large disk was selected to have install rootvg on it (around 80GB),
then the restore would fail while creating logical volumes on the rootvg
volume group.

Workaround:
Perform the following steps to resolve this problem.
1. This workaround requires you to modify the restore script that is
generated after bmrprep and stored in the BMR master server database.

2. Pull the <client_hex_addr>.restore script from master server using
the bmrc command line interface (CLI)

3. The bmrc CLI syntax is:
/usr/openv/netbackup/bin/bmrc/bmrc -o pull -r INFO -client <cl_name>

4. The source is:
<client_hex_addr.restore file name> -destination /tmp/foo
5. Open the /tmp/foo file for editing.

6. In the function MkVg(), which creates a rootvg volume group, before
the creation of each logical volume under rootvg (for example, just
before mklv command) write the following two lines.

let LVPartitions=LVPartitions+PPSizeMultiplier-1
let LVPartitions=LVPartitions/PPSizeMultiplier

7. Upload the /tmp/foo file into the master server database using the
bmrc CLI.

/usr/openv/netbackup/bin/bmrc/bmrc -o push -r INFO -client <cl_name>
-source /tmp/foo -destination <client_hex_addr.restore file name>

8. Try to restore the client machine. This should resolve the problem.
--------------------------------------------------------------------------------
Etrack Incident = ET1213695
Associated Primary Etrack = ET1173896
Titan cases: 220-203-493 220-288-767 240-631-316 240-654-553 240-717-856
281-257-682 281-274-501 281-289-315 281-329-183 281-337-228 290-904-083
290-906-114 290-926-355 290-940-579 311-881-843 311-882-571 311-895-561
311-966-172 320-103-859

Description:
An NDMP backup would fail with the following tape positioning error.

Error:bptm:too many data blocks written, check tape/driver block size
configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET1202533

Description:
The SQL log mark name was not being handled properly. A change was made to
convert it to UNICODE.
--------------------------------------------------------------------------------
Etrack Incident = ET1204661
Titan cases: 240-647-369 281-178-937

Description:
Restore jobs would fail with a status error 5. A change has been made to
ensure jobs complete successfully, and mailboxes and folders are restored
for the Exchange server.
--------------------------------------------------------------------------------
Etrack Incident = ET1222845
Associated Primary Etrack = ET1176922
Titan cases: 290-897-933

Description:
The XDOO stream header size was not being handled properly during the BE
Exchange 2003 image restores from NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET1222258
Associated Primary Etrack = ET1118175
Titan cases: 240-620-995 281-127-394

Description:
Changes were added to address many malloc errors that were reported when
using NDMP, such as: ndmp_tape_execute_cdb: malloc(0) failed.

The following error occurred when running the set_ndmp_attr command:
ndmp_config_get_ext_list: malloc() failed

During normal backup activity, the following error appeared in the NDMP
log:
[ndmp_logger_vxul] ndmp_tape_execute_cdb: malloc(0) failed

This was a platform dependent issue and occurred only on AIX 5.2.
--------------------------------------------------------------------------------
Etrack Incident = ET633166

Description:
Changes were made in the user interface to address grayed-out policy icons
in tree when a policy was disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET1041153

Description:
An application that uses the XBSA SDK may encounter a random restore failure
when the NBBSA_POLICY environment variable is specified.

Workaround:
If you encounter this issue, do not specify the NBBSA_POLICY environment
variable for the restore transaction.
--------------------------------------------------------------------------------
Etrack Incident = ET1228196

Description:
A NetBackup-Java Administration Console error would occur with a log on
status 509, cannot execute program.

When the CreateProcess() was used in lieu of CreateProcessAsUser(), due
to a failure (or another failure), ensure that the default desktop is
used, as the defualt user may not have access to the desktop associated
with the User (CreateProcessAsUser()) invocation. In this case,
LoadProfile() failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1229928

Description:
The device allocator (DA) would not respect a NetBackup 5.1 host's
SSO_SCAN_ABILITY zero setting. A host's scanability must be set using
nbemmcmd on the EMM server. The vm.conf entry is no longer honored.
--------------------------------------------------------------------------------
Etrack Incident = ET1159536 ET1200897
Associated Primary Etrack = ET1126744 ET1162053
Titan cases: 220-105-996 220-131-742

Description:
The NetBackup Notification Service would terminate unexpectedly.
--------------------------------------------------------------------------------
Etrack Incident = ET1231109

Description:
If an expired VxVM or VxFS license key is encountered during restoration
of an AIX client, the restoration process does not prompt the user to enter
an updated key.

Workaround:
If you encounter this issue, update the license key in an editable
configuration for the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1228989

Description:
Self-restores on RHEL 2.4 and 2.6 BMR clients would go into Dissimilar Disk
Restore (DDR) mode. This problem was encountered when the BMR client had
HBA- and USB-based storage devices.
--------------------------------------------------------------------------------
Etrack Incident = ET1224637

Description:
The following enhancements were added in this release to ensure that
NetBackup 6.x supports back-revision 5.x media servers.

Vmscd - Clear the restart bit if ltid is confirmed to not be running.
- Increased the 45 second timeout to 5 minutes.

vmd - Global DB and DA requests now handled in child vmd process.
- Fix for master that does not have any drives (respond to
registration with no scan host)

mmcrawl - Added an option to display ltid restart status on all
drives and drive paths
- Updated the repair option to clear the restart bit

Vmoprcmd - Display a list of hosts that need to be restarted using the
-show_restart option.
--------------------------------------------------------------------------------
Etrack Incident = ET1234803

Description:
The policy windows in the NetBackup-Java Administration Console would hang
on Windows because of an issue in the BPPLINFO_CMD protocol.
--------------------------------------------------------------------------------
Etrack Incident = ET1201393
Associated Primary Etrack = ET1135157
Titan cases: 230-436-303

Description:
bpdbjobs was not showing Kbytes information for duplicate jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1152608
Associated Primary Etrack = ET1136267
Titan cases: 320-064-173

Description:
The first stream of a multistream backup would end with a Status Code 815.
Trying the backup again could produce a successful backup. This was a
random error that never occurred consecutively on the same policy or
client. The error would occur when using disk and tape storage units.
--------------------------------------------------------------------------------
Etrack Incident = ET1042411

Description:
NetBackup would sometimes add multiple tape libraries in the database while
configuring a shared non-serialized tape library.
--------------------------------------------------------------------------------
Etrack Incident = ET1226336
Associated Primary Etrack = ET1209045
Titan cases: 220-177-120

Description:
If the backup image was multiplexed (doing a multiplex restore), and the
client connect options were set to 2,1,1 (meaning: (2) Use Default ports -
which is the reserved port, (1) VNETD port for connect back, and (1) VNETD
for the Daemon Connection port, respectively) then the BMR restore to the
client would fail with bptm unable to connect to the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1211653
Associated Primary Etrack = ET1174784
Titan cases: 220-147-432

Description:
In certain instances on HP-UX systems, pipe file descriptors may be
incorrectly flushed. This was initially observed in VSM, and has not been
seen in NetBackup. Symantec is proactively correcting this issue in this
release of NetBackup as a preventative measure.
--------------------------------------------------------------------------------
Etrack Incident = ET1137917
Titan cases: 320-067-351

Description:
Could not remove drives with missing drive index records.
--------------------------------------------------------------------------------
Etrack Incident = ET1135737

Description:
A 163 error (media block size changed prior to resume) would be returned
if the schedule or storage unit configuration changed prior to a resume of
a backup job such that multiplexing was disabled or enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET1227823

Description:
Running vmphyinv on some hosts would result in the following error:

Unable to get global device list: invalid host name (136)6)
--------------------------------------------------------------------------------
Etrack Incident = ET814704

Description:
bpplinfo would core dump when changing policies that require a snapshot
configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET1175373
Associated Primary Etrack = ET1177238
Titan cases: 290-881-887

Description:
bpmedia -movedb -allvolumes -newserver <hostname> -oldserver <hostname>

When decommissioning a media server, a user may need a more efficient way
of moving multiple tapes between media servers when the image database is
very large.

Workaround:
Run the following command for each volume assigned to the media server you
are decommissioning.

bpmedia -movedb -m <media_id> -newserver <hostname>
--------------------------------------------------------------------------------
Etrack Incident = ET1236186
Associated Primary Etrack = ET1217146
Titan cases: 311-824-283

Description:
AIT-4 and AIT-5 drives were being downed while cleaning was in progress.
--------------------------------------------------------------------------------
Etrack Incident = ET1237077

Description:
Could not perform an autodiscover for ACS robots on ACSLS servers without
ACS 0 defined on the ACSLS server.
--------------------------------------------------------------------------------
Etrack Incident = ET1237818

Description:
A change was made to address an issue that caused the NetBackup-Java
Administration Console to hang.
--------------------------------------------------------------------------------
Etrack Incident = ET1209710
Associated Primary Etrack = ET1204922
Titan cases: 311-817-301

Description:
In NetBackup 6.x, a backup taken using backint.exe would contain a
non-unique "keyword". If you depended on this "keyword" value to run
scripts, such as a verify script or a restore script, then those scripts
would not run correctly. A change has been made to ensure a unique
"keyword" is generated so user scripts will not fail.
--------------------------------------------------------------------------------
Etrack Incident = ET918372

Description:
After enabling NBAC, then running bpnbat -login for the first time and
providing an empty domain value would cause it to abort and dump core.
--------------------------------------------------------------------------------
Etrack Incident = ET1200166
Associated Primary Etrack = ET1169657
Titan cases: 290-843-958

Description:
Received the following warning message when deassignempty was run on an
unassigned media and image indexing was in use.

Could not deassign media due to Media Manager error (177)

Workaround:
Do not use image indexing.

Additional Notes:
When image indexing was in use (via the command "bpimage
create_image_index"), in-process images were not considered when
"bpexpdate -deassignempty" was run. If a media for an in-process job was
not previously used, bpexpdate would attempt to deassign it and receive
this message. With this fix, bpexpdate will include in-process images
even if image indexing is in use.
--------------------------------------------------------------------------------
Etrack Incident = ET1216170

Description:
The NetBackup Service Layer (NBSL) would sometimes perform multiple fetches
in two threads on the same result set for media, which would cause EMM to
crash.
--------------------------------------------------------------------------------
Etrack Incident = ET1039111
Associated Primary Etrack = ET1019103
Titan cases: 290-706-957

Description:
The bpexpdate -deassignempty command would not work if one or more media
servers were offline.
--------------------------------------------------------------------------------
Etrack Incident = ET1238630
Titan cases: 290-960-740

Description:
User backup operations that were multiplexed would not respect the media
unload delay.
--------------------------------------------------------------------------------
Etrack Incident = ET1229969
Associated Primary Etrack = ET1149038
Titan cases: 311-714-377 311-903-136

Description:
The online catalog backup email report and disaster recovery file were
not listing all of media for critical policies.
--------------------------------------------------------------------------------
Etrack Incident = ET1238369
Associated Primary Etrack = ET1235243
Titan cases: 290-944-808

Description:
Vault would log a successful session status as an error.
--------------------------------------------------------------------------------
Etrack Incident = ET1142467

Description:
When running disaster recovery using BRRECOVER, if the init<DBSID>.sap
file was not present, BRRECOVER would call BACKINT without the
-p init<DBSID>.utl parameter.

If NetBackup for SAP is called without the util file parameter, it checks
for the SAP_RECOVERY environment variable. If the environment variable is
set to "disaster", the restore is allowed without util file parameter. In
this case NetBackup for SAP does the restore using the default SAP policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1210594
Associated Primary Etrack = ET1202943
Titan cases: 281-258-932

Description:
6.x Media server (bpbrm) would skip encryption for a 5.x SAP agent.

--------------------------------------------------------------------------------
Etrack Incident = ET1175891

Description:
In Windows, while creating a new Shared Resource Tree (SRT), if an
existing SRT's name was given (case insensitive), then the older SRT was
overwritten and became unusable.

A change was made so that the Shared Resource Tree (SRT) name is now
case-insensitive for UNIX. It was already case-insensitive for Windows.
This change was made to maintain a similar structure across all platforms
in BMR.

Additional Notes:
If you are upgrading a server and if multiple SRTs with a same name but
a different case already exist, some operations, such as deleting an
SRT, would behave in an ambiguous manner and a wrong operation might be
performed. However, a change has been made that does not allow the
creation of SRTs with the same name (with a different case).
--------------------------------------------------------------------------------
Etrack Incident = ET1239178

Description:
Make messages would fail because of the duplicated ID, CerRba0065N, in the
commands.c file.
--------------------------------------------------------------------------------
Etrack Incident = ET1166277
Associated Primary Etrack = ET1163499
Titan cases: 311-751-032

Description:
A consolidated eject operation through vltopmenu would dump core if a
profile that had "deferred eject" enabled and was disabled later. Any
sessions that were created while the eject was ON would be selected for an
eject but it would fail to proceed if the eject was disabled currently.

A change has been added to skip those sessions for which an eject is
currently disabled.

Workaround:
If however you encounter an issue like this, delete the session entries
from vlteject.mstr for which an eject time stamp (column 3) is marked as
ZERO and the eject step is currently disabled for its corresponding profile.
--------------------------------------------------------------------------------
Etrack Incident = ET1158729

Description:
A change was made to ensure the NetBackup Administration Console shows
Media on the media node.
--------------------------------------------------------------------------------
Etrack Incident = ET420683
Titan cases: 280-448-226

Description:
Changes have been made to address issues when setting the policy schedule
time using the Newfoundland (GMT = 03:30) time zone.
--------------------------------------------------------------------------------
Etrack Incident = ET1236032
Associated Primary Etrack = ET1225889
Titan cases: 320-091-983

Description:
When a backup is started using the wait (-w) option, the bprd child
process is alive during backup execution and pings pem to check that it
is alive. This ping mechanism prints a log message every second and can
cause the bprd log to fill quickly and unnecessarily.

A change has been added that ensures the message queue is read only when
there is a message in the queue, and not reading message queue every
second.
--------------------------------------------------------------------------------
Etrack Incident = ET1214070

Description:
An NDMP DAR restore fails when file names contain non-ASCII characters.

If the list of files to restore contain the special characters '{' or '}'
the restore may fail. The ndmpagent log (orgid 134) showed that the fh_info
and node values for the files is 0.

Workaround:
To avoid this issue, disable DAR for NDMP restores.
--------------------------------------------------------------------------------
Etrack Incident = ET1235538

Description:
NDMP backups would fail when there was a percent (%) character in the
backup path name.
--------------------------------------------------------------------------------
Etrack Incident = ET1227575
Associated Primary Etrack = ET1195987
Titan cases: 240-666-425 311-859-827

Description:
In NDMP backups, if the master server was only reachable using Internet
or WAN communication, some backups of large volumes would fail with a
status 23. This failure occurred because a five-minute timeout was reached.

To resolve this issue, add a new touch file in the NetBackup directory
and name the file "ndmp_connect_timeout". Add a value of the number of
minutes in seconds to the file (initial suggestion is 480).

When the value is present the following message with the specified timeout
will appear in the logs.

ndmp_net_connect: Timeout Value:
--------------------------------------------------------------------------------
Etrack Incident = ET1232742

Description:
A fix has been made that resolves an issue where SQL Server backups would
intermittently fail with a status code 2. The dbclient logs showed an
error message similar to the following:

00:55:51.072 [2864.2740] <16> ReadBatch: USER - You provided an illegal
keyword: <PERATION>
--------------------------------------------------------------------------------
Etrack Incident = ET1240183
Associated Primary Etrack = ET1211323
Titan cases: 290-900-314 290-919-097

Description:
When the BMR boot server is started it tries to register itself with BMR
master server. If the BMR master server is down or the BMR database is
not up it tries to register itself, it gets either a Network Failure
error or a registration failed error.

If registration is not successful then BMR boot server sends a
registration request to the master server every 30 seconds. For each
registration request the BMR boot server produces a memory leak and it
decreases the performance in the machine.

Workaround:
If you encounter this issue do one of the following:

- If the BMR master server daemon "bmrd" is down then shut down the BMR
boot server daemon "bmrbd".

OR

- If BMR database is not yet configured then run bmrsetupmaster on the
command line interface (CLI) to configure the database and then
re-start the bmrd and bmrbd daemons.
--------------------------------------------------------------------------------
Etrack Incident = ET1233401

Description:
Verifying an NDMP backup that is greater than 4TB will fail with the
following error message.

Raw partition size gigabytes does not match for file

Workaround:
If you receive this error message, ignore it. The backup data is correct
and restores from the backup will work okay.
--------------------------------------------------------------------------------
Etrack Incident = ET1239595

Description:
In a network environment that was experiencing connection issues, such as
one where a router failed, the communication between bpbrm and bpfis could
be such that when bpfis attempted to read the file list it would
continually get a null string. In this case, bpfis continues to try and
read the file list, resulting in an endless loop that would quickly
exhaust disk space if logging was turned on. This change caused an empty
string to be treated like a timeout on the read.
--------------------------------------------------------------------------------
Etrack Incident = ET1242512
Associated Primary Etrack = ET1225587
Titan cases: 240-705-124

Description:
Corrected a display issue for Drive and Robot diagnostics to display the
status of a test back to a remote user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1145850

Description:
A change has been added that implements fast object positioning for
NBBSAGetMultipleObject API restores. Fast object positioning improves
restore performance by enabling XBSA to position the media server to
the exact location of an object in an image. This enables XBSA to
restore the object without having to read through the entire image.

This feature enhances the XBSA multiple object restore interface and
allows it to position bptm/bpdm to the starting offset of an object
within an image. Previously the XBSA interface would read through the
entire image until the starting offset of the desired object was reached.

This feature is only available through the NBBSAGetMultipleObjects API
for images that contain multiple XBSA objects. The image must be
non-multiplex if it resides on tape. The XBSA interface will only
position bptm/bpdm if the number of blocks between the current offset
and the starting offset of the object being restored is greater than a
certain number of data blocks. The number of blocks is determined by
bptm/bpdm depending on the type of media that the image is stored on.
Typically, the number of block is 90000 for tape and 40000 for disk.
These values may change in future releases.
--------------------------------------------------------------------------------
Etrack Incident = ET1235529
Associated Primary Etrack = ET1182999
Titan cases: 311-769-409

Description:
In some cases, restores of multiple Flashbackup volumes would fail when
doing single-file restores.
--------------------------------------------------------------------------------
Etrack Incident = ET1195956

Description:
A BMR client entry would show duplicates with case sensitivity.

After performing a backup of a BMR client, if the client name case was
changed, the next backup would add another client entry, and the case
sensitivity would give an impression that there were now two different
clients.
--------------------------------------------------------------------------------
Etrack Incident = ET1245566

Description:
bpdbjobs was showing incorrect sizes for cold catalog backups to tape when
the /usr/openv/netbackup/db folder exceeded 2GB.
--------------------------------------------------------------------------------
Etrack Incident = ET1244766

Description:
Added support for the Sun/STK SL3000 robot for TLD and ACS control.
--------------------------------------------------------------------------------
Etrack Incident = ET1245997

Description:
The Oracle Backup stream jobs would remain queued because the parent Oracle
job had consumed the max jobs per client resource. The max jobs per client
was set to 1.
--------------------------------------------------------------------------------
Etrack Incident = ET1244622

Description:
PBXIOP upcalls would go through even if VxSS is set to REQUIRED mode.

Even when VxSS=REQUIRED, calls made to the insecure endpoint of NBSL
would go through. Changes have been added to ensure calls do not reach an
insecure end point.
--------------------------------------------------------------------------------
Etrack Incident = ET1226883
Associated Primary Etrack = ET1226682
Titan cases: 230-501-996

Description:
Running the "bpubsora -U user/password -b Oracle:SID:" command in a 64-bit
configuration can results in a core file. The problem could also be
generated when attempting to connect to the Oracle database with the Backup
Archive and Restore (BAR) user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1224664
Associated Primary Etrack = ET1204253
Titan cases: 290-908-445

Description:
An Oracle RMAN restore would core dump when entering sbtread2. The Oracle
restore would run for a period of time (2 to 12 hours) before the failure.
--------------------------------------------------------------------------------
Etrack Incident = ET1221477
Associated Primary Etrack = ET1135854
Titan cases: 281-213-06 281-213-065

Description:
The slow mounting of tapes would cause the backup window to be exceeded.
A change has been made to address some deadlock issues that would occur in
the NetBackup Resource Broker (nbrb).
--------------------------------------------------------------------------------
Etrack Incident = ET1036931
Associated Primary Etrack = ET1036799
Titan cases: 230-377-381

Description:
In NOM, job types such as Drive Cleaning and Tape Mount Request would
appear as NONE in the user interface.

Workaround:
Added those job types.
--------------------------------------------------------------------------------
Etrack Incident = ET1200190
Associated Primary Etrack = ET1177307
Titan cases: 220-153-246

Description:
nbemm would shutdown with no obvious reason and without logging a cause.

This fix corrects a race condition between the server sending a response
to a client, and the server detecting the client closed the connection.
--------------------------------------------------------------------------------
Etrack Incident = ET1249754
Associated Primary Etrack = ET1249433
Titan cases: 220-264-336

Description:
An NDMP backup would fail with a status 99 after 24 hours. A change has
been made to increase the maximum value of the NDMP_PROGRESS_TIMEOUT
timeout to seven days.
--------------------------------------------------------------------------------
Etrack Incident = ET1245529
Associated Primary Etrack = ET1235042
Titan cases: 220-126-921

Description:
A Lotus Notes restore was successful but the recovery would fail with a
Status 5 when the transaction log path ends with a backward slash
character "\".
--------------------------------------------------------------------------------
Etrack Incident = ET1252379

Description:
A change was made to stop installing msvcr71.dll and msvcp71.dll into the
VxFI\bin directory.
--------------------------------------------------------------------------------
Etrack Incident = ET1089296
Titan cases: 290-807-298

Description:
Copies in the catalog that are missing their first fragments are not
cleaned up. A fix has been added that allows automatic cleanup of orphaned
fragments. It occurs as part of the same operation that cleans up expired
copies.

Workaround:
If you were to encounter this issue, you can use the bpimage -deletecopy
command to remove the copies manually.
--------------------------------------------------------------------------------
Etrack Incident = ET1251778
Associated Primary Etrack = ET1242682
Titan cases: 240816306 290-962-969

Description:
The bpexpdate -deassignempty command would de-assign non empty tapes and
cause data loss if the user specified a cluster name, as well as node names,
in the storage unit configurations.
--------------------------------------------------------------------------------
Etrack Incident = ET1252326
Titan cases: 290-875-177

Description:
All robotic drives on a media server would enter into AVR mode and not
attempt to go back up to robotic mode.
--------------------------------------------------------------------------------
Etrack Incident = ET1219002
Associated Primary Etrack = ET1130589
Titan cases: 290-822-170

Description:
Using bpexpdate via EMM to expire a backup could take a long time.
--------------------------------------------------------------------------------
Etrack Incident = ET1252345

Description:
After upgrading from NetBackup 5.x or manually configuring an ACS robot on
NetBackup a 6.x server, running auto-discovery will add a new NetBackup ACS
robot to the configuration instead of using the one already configured.
--------------------------------------------------------------------------------
Etrack Incident = ET1257025

Description:
A change has been made to ensure that users are able to create a VMware
snapshot backup. These backups were failing with a 509 error.
--------------------------------------------------------------------------------
Etrack Incident = ET1259059
Associated Primary Etrack = ET1175415
Titan cases: 220-148-833

Description:
A change was made to address a bpbrmds application error popup (faulting
module) that would occur randomly and reported on Windows.
--------------------------------------------------------------------------------
Etrack Incident = ET1257297

Description:
Duplicating a backup image over 2 TB in size would fail if you used NDMP
tape devices. The progress log would report a status 85 - media read error.
--------------------------------------------------------------------------------
Etrack Incident = ET1195231
Associated Primary Etrack = ET1160602
Titan cases: 290-869-698

Description:
The bpplcatdrinfo command ignores the "-set" and "-modify" commands when
changing policy information on remote master servers.

Workaround:
To resolve this issue, create a catalog-backup policy on the local master
server with the same name as the policy on the target (remote) master
server. It will not get updated itself, but its presence will allow changes
on the remote server to proceed.
--------------------------------------------------------------------------------
Etrack Incident = ET1260503
Associated Primary Etrack = ET1180335
Titan cases: 320-076-645

Description:
User-directed backups would fail with a status 12 when using bpdm with
permissions set (root umask = 066). The corresponding error message would
appear in the log file.

ERR - Could not open file <filename> to get shared memory information.
--------------------------------------------------------------------------------
Etrack Incident = ET1259252

Description:
bpdbm was terminating abruptly in some situations when it could not
retrieve a backup image file.
--------------------------------------------------------------------------------
Etrack Incident = ET1262091
Associated Primary Etrack = ET1262089

Description:
The nbproxy would hang while waiting for images that were locked by other
processes that were doing image-list queries to be released.
--------------------------------------------------------------------------------
Etrack Incident = ET1150199

Description:
In clusters with NBAC enabled, if the AB subject name did not match its
hostname the NetBackup-Java Administration Console would not be able to
contact it to obtain a certificate.
--------------------------------------------------------------------------------
Etrack Incident = ET1240367
Associated Primary Etrack = ET1235462
Titan cases: 311-875-604

Description:
Timezones that switch dst at midnight instead of after midnight (for
example, Egypt) would sometimes cause nbpem to hang.
--------------------------------------------------------------------------------
Etrack Incident = ET1261507
Titan cases: 240-724-837

Description:
The nbpushdata -add command fails while contacting media servers to get
the host information. The following is the error information that appears
in the nbpushdata log:

RetrieveFile: fdopen <filename> failed: Too many open files (24)

Workaround:
To work around this issue, run nbpushdata -add again. A second attempt
will be successful when contacting the media servers that were not
successfully contacted previously.
--------------------------------------------------------------------------------
Etrack Incident = ET1261430
Associated Primary Etrack = ET1172014
Titan cases: 281-252-766

Description:
A change was made to add logging to the Storage Server (STS) core.
In addition, a touchfile was added that allows the timeout between the P3
plugin and the NetApp filer to be manually adjusted (the default timeout
is 10 seconds).
--------------------------------------------------------------------------------
Etrack Incident = ET1239561 ET1254551
Associated Primary Etrack = ET1199214
Titan cases: 290-906-878

Description:
An Exchange Mailbox backup would fail after reporting that some message
attachments were corrupt. This failure was triggered when there were many
(250 or more) e-mail messages with OLE attachments that were empty (zero
bytes), or attachments that were references to OLE objects that did not
exist.

After the failure "access is denied" messages would appear in the bpbkar
log on the client, and MSExchangeIS writes one or more 9646 events to the
Application Event Log.
--------------------------------------------------------------------------------
Etrack Incident = ET1269061
Associated Primary Etrack = ET1264484
Titan cases: 240-753-236

Description:
The NetBackup Resource Broker (nbrb) would core dump using
NetBackup 6.0 MP6 when in the following function:

EMMProvider::deallocateUnpersistedAllocation
--------------------------------------------------------------------------------
Etrack Incident = ET1209043
Associated Primary Etrack = ET1200758
Titan cases: 281-265-332

Description:
Virtual and non-Broadcom NIC drivers are not compatible with the WinPe
environment.
--------------------------------------------------------------------------------
Etrack Incident = ET1273387
Associated Primary Etrack = ET1273308
Titan cases: 311-885-685

Description:
The bptm program would core dump and the vault catalog backup would fail
with a status 294 error. The occurrence of this issue was rare and
occurred on AIX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET1235591
Associated Primary Etrack = ET1227411
Titan cases: 290-937-938

Description:
The Windows client restore log would show the following message when
restoring folder names that were longer than nine characters to an
alternate location while maintaining the existing structure.

WRN - unable to set short name on restore: (err=000000b7)
--------------------------------------------------------------------------------
Etrack Incident = ET1223290
Associated Primary Etrack = ET1184825
Titan cases: 281-258-087

Description:
FlashBackup would fail with the following error:

Unable to read metadata for index: 490296, VFM error = 5

--------------------------------------------------------------------------------
Etrack Incident = ET1174882
Associated Primary Etrack = ET1131327
Titan cases: 320-066-187

Description:
Some FlashBackup restores would fail with the following status 5 error,
bpdbm reports, "nbe_cat_image.h Line...invalid index".

--------------------------------------------------------------------------------
Etrack Incident = ET1275369
Associated Primary Etrack = ET1262893
Titan cases: 220-256-279

Description:
A change was made to address an issue that cause nbpem to stop submitting
jobs to the job manager (nbjm) on AIX systems only.
--------------------------------------------------------------------------------
Etrack Incident = ET1134888

Description:
True Image Restore (TIR) is required for a backup to a NearStore storage
unit with filesystem export enabled. The filesystem export feature
provides a filesystem export of the data set as well as improved data
de-duplication on the filer. Some users may want the improved data
de-duplication but are not interested in the filesystem export. They
also may not want to configure their policies with the overhead of TIR.
This change allows TIR to be optional for backups to a NearStore storage
unit with filesystem export.
--------------------------------------------------------------------------------
Etrack Incident = ET1269918
Associated Primary Etrack = ET1263586
Titan cases: 311-882-092

Description:
Attempting to restart an Inline Tape Copy (ITC) job would result in the job
being restarted as it was on the original submission. This would not work
because the original job had been deleted. A change was made so that a
restart causes a new job to be submitted to the job manager instead of
attempting to restart the original job.
--------------------------------------------------------------------------------
Etrack Incident = ET1261282

Description:
A change was added to address an issue that caused bpdbm to hang on some
queries.
--------------------------------------------------------------------------------
Etrack Incident = ET1097416
Titan cases: 311-569-042

Description:
Some Linux directories have incorrect ACL's assigned. This fix rectifies
the issue by looking at each of three values separately instead of all
together.
--------------------------------------------------------------------------------
Etrack Incident = ET1275549
Associated Primary Etrack = ET1135854
Titan cases: 281-213-06 281-213-065

Description:
The firewall would cause idle connections to close during long backup
jobs between media and master server.

Workaround:
If you encounter this issue, disable the firewall idle connection timeout.
--------------------------------------------------------------------------------
Etrack Incident = ET1239073

Description:
Some NetBackup services did not stop after issuing a fail-over or offline
command in VCS. In addition, VCS did not attempt to "clean" or "offline"
these services again.

Workaround:
While upgrading to 6.0MP7 on the active-node in a clustered environment,
some of the NetBackup services may not stop cleanly and this can cause the
installation to abort.

To resolve this situation in a VCS cluster, perform the following steps.
1. Freeze the corresponding NetBackup group from VCS cluster console.
2. Manually shutdown NetBackup on the active node by calling bpdown.
From the service control manager, verify that all the NetBackup
services are down.
3. Apply the patch.
4. Unfreeze the group manually.
--------------------------------------------------------------------------------
Etrack Incident = ET1278935
Associated Primary Etrack = ET1273708
Titan cases: 281329229

Description:
The Windows client was not displaying volumes during the mapping screen
during FastBoot ISO.
--------------------------------------------------------------------------------
Etrack Incident = ET1281153
Associated Primary Etrack = ET1271291
Titan cases: 240-757-535

Description:
An issue existed that that caused nbjm to receive CORBA exceptions during
a resource allocation. In addition, connection timeouts would occur.
--------------------------------------------------------------------------------
Etrack Incident = ET1271278

Description:
The release contains an updated nbsu (version 1.2.6) that includes the
following:
- Added the NBU_server_groups, NBU_evtmgr and MM_get_ltid_tables
diagnostic checks.
- Modified the default nbsu behavior to avoid running the bpcoverage
command unless the NB_bpcoverage diagnostic is explicitly specified.
This will improve the performance of this utility when run in an
environment with a large number of backup clients.
- On Solaris, altered the NET_ndd diagnostic to include additional
information.
- Added the -L bpplist command line option to the NBU_bpplist
diagnostic.
- Modified the default nbsu behavior to always collect troubleshooting
diagnostics along with the configuration diagnostics. This will help
guarantee that this utility will not have to be re-run to gather
additional data, but it will increase the time needed to run nbsu.

For additional information about these enhancements, refer to the
following TechNote on the Symantec Support Web site.
http://entsupport.symantec.com/docs/303813
--------------------------------------------------------------------------------
Etrack Incident = ET1211678

Description:
A NAS_Snapshot copy-back restore would fail with a truncated snapshot
pathname in the REMAP directive.
--------------------------------------------------------------------------------
Etrack Incident = ET1270235

Description:
A change was made to address an issue that caused a large number of,
fprintf(" ") failed: Bad file number (9), messages.
--------------------------------------------------------------------------------
Etrack Incident = ET1283692
Associated Primary Etrack = ET1270507
Titan cases: 311-914-328

Description:
Image selection would take longer to run than previous versions.

A different approach to compare hosts used in 60MP6 caused this issue.
A fix was added to improve the image selection performance so that it is
equal to the performance in 60MP5.
--------------------------------------------------------------------------------
Etrack Incident = ET1253532
Associated Primary Etrack = ET1251645
Titan cases: 290-960-008

Description:
If the settings MUST_USE_LOCAL_DRIVE and DONT_USE_SLAVE are enabled on a
master server this should ensure that all backup jobs for a given media
server run on that media server. If there are no resources available on
that system, then the jobs should queue (this is the behavior under
NetBackup 6.0). NetBackup 6.5 is ignoring this setting and running jobs
on a different media server - such that the behavior is the same with or
without these settings in the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET1283873 ET1283865
Associated Primary Etrack = ET1230140 ET1254219
Titan cases: 320-092-763 290-975-130

Description:
A change was made to correct an issue that caused nbjm to sometimes crash
on shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET1275147
Associated Primary Etrack = ET1114023
Titan cases: 240611709

Description:
A change was made to address a Status 190 error received from bpduplicate
when using Disk Staging and doing VxVM Offhost backups with Instant
Recovery Enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET1277786
Titan cases: 290-914-792

Description:
A NetBackup process may core dump, and the connectToObject() call is in
the stack trace. This artifact was seen on AIX systems.

Additional Notes:
The use of NBAC where security was optional would sometimes exacerbate
this behavior, because connections were tried twice, once in secure mode,
and the second time in insecure mode, depending on the configuration.
A High Availability (HA) cluster configuration would be affected by this
problem if an affected NetBackup process core dumped and prevented a
proper fail-over.
--------------------------------------------------------------------------------
Etrack Incident = ET1077528
Associated Primary Etrack = ET1074890
Titan cases: 220-100-546

Description:
Decommissioned media servers do not get removed from the NetBackup
remote_versions directory which would cause communication delays when the
media servers were removed from networking services like DNS.

This directory is cleaned once a day now.

Workaround:
A "cron" or "at" job could be created to run a program that removes files
that are older than a day in the %install_path%/netbackup/remote_versions
directory.
--------------------------------------------------------------------------------
Etrack Incident = ET1189875

Description:
Robot details were not visible in the NOM Server. This would happen
sometimes when the Robot Monitor, Drive Monitor, Media Monitor, and Volume
group monitors would go down and then come back up after some time.
--------------------------------------------------------------------------------
Etrack Incident = ET1227541
Associated Primary Etrack = ET1145949
Titan cases: 290-840-787

Description:
Duplicate jobs would not launch because the bpduplicate command would
ignore the priority switch.
--------------------------------------------------------------------------------
Etrack Incident = ET1190428
Associated Primary Etrack = ET828558
Titan cases: 280-735-711

Description:
NetBackup 5.x client backups to a NetBackup 6.0 MP3 Master/media server
would fail with a Status 41 when multiplexing was enabled.

--------------------------------------------------------------------------------
Etrack Incident = ET1291060
Associated Primary Etrack = ET1032373
Titan cases: 240-540-817

Description:
bpstuadd creates a SERVER entry in the master bp.conf file even though
the MEDIA_SERVER entry already exists.

Workaround:
After running bpstuadd, manually modify the server list to remove the
SERVER entry.
--------------------------------------------------------------------------------
Etrack Incident = ET1260324
Associated Primary Etrack = ET1198882
Titan cases: 281-230-867

Description:
The DstMediaID field was not populated for all jobs in the
bpdbjobs -report output.
--------------------------------------------------------------------------------
Etrack Incident = ET1287242

Description:
A change was made to address an issue that caused NBJM to crash during
shutdown on an AIX system.
--------------------------------------------------------------------------------
Etrack Incident = ET1292773
Associated Primary Etrack = ET1281452
Titan cases: 230-535-095

Description:
After activating or deactivating policies in NOM, the NetBackup-Java
Administration Console was unable to read policies.
--------------------------------------------------------------------------------
Etrack Incident = ET1296513

Description:
Changes made in VxMS 4.3.020 address the following issues:
- Extent failure that occurred while extracting extents of
resident data.
- The VxMS setup.exe was not being used by NetBackup.
- The NTFS plugin would cause a log error in event log if the
vfm_make_file was called to create an existing file.

Changes made in VxFS address the following issues:
- A change was made to address an issue that caused a crash in bpfis
during the cleanup phase.
- VSS would fail with an error 6 on DataGramClient.
- Jobs would reamin active after three days on an MSCS cluster
configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET1294647

Description:
The SharePoint backup parent job would run indefinitely in the Activity
Monitor after child jobs complete.
--------------------------------------------------------------------------------
Etrack Incident = ET1291761

Description:
A change was made to address an issue where a user was unable to perform a
synthetic backup to tape.
--------------------------------------------------------------------------------
Etrack Incident = ET1297162
Associated Primary Etrack = ET1270507
Titan cases: 311-914-328

Description:
Image selection would take longer to run than previous versions.

A different approach to compare hosts used in 60MP6 caused this issue.
A fix was added to improve the image selection performance so that it is
equal to the performance in 60MP5.
--------------------------------------------------------------------------------
Etrack Incident = ET1295792
Associated Primary Etrack = ET1293550
Titan cases: 220-322-223 220-334-354

Description:
A change was made to address an issue that caused an incremental backup
to run as a full backup the first time an incremental was attempted after
upgrading to 6.5.2 or 6.0MP6

For more information about this change, refer to the following TechNote
on the Symantec Support Web site.
http://entsupport.symantec.com/docs/304269
--------------------------------------------------------------------------------
Etrack Incident = ET1298901
Associated Primary Etrack = ET1286267
Titan cases: 320-103-488

Description:
SQL server snapshot client backups would fail on Windows x64 systems
with a status 69: invalid filelist specification error, that was recorded
in the bpfis log.
--------------------------------------------------------------------------------
Etrack Incident = ET1302098
Associated Primary Etrack = ET1296912
Titan cases: 220-325-975

Description:
A change was made to address an issue that caused a multiple copy backup
of an Oracle database to fail in some situations.
--------------------------------------------------------------------------------
Etrack Incident = ET1251842
Associated Primary Etrack = ET1248033
Titan cases: 311-825-444

Description:
Immediate backups that fail would retry the backup and attempt to use the
wrong schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET1316727

Description:
A change was made to address an issue that caused manually resumed jobs
to be restarted instead of resuming.
--------------------------------------------------------------------------------
Etrack Incident = ET1316894
Associated Primary Etrack = ET1295660
Titan cases: 311-944-025

Description:
On Windows master servers, the online catalog backup was failing with a
status of 2 for the parent job and 42 for one of the child jobs when
non-multi-streamed policies were configured as critical policies in the
catalog backup policy.

Workaround:
If you encounter this issue, remove the critical policies from the online
catalog backup policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1314264
Associated Primary Etrack = ET1275903
Titan cases: 290-991-173

Description:
Lotus Notes databases that were larger than 2GB would be treated as links
and skipped from the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1321914

Description:
A change has been added to address a data Loss issue that affected
NetBackup 6.0. The issue that was fixed caused an image to be deleted
from the disk storage unit if the last fragment was close to the maximum
fragment size and would result in a successful backup (status 0 or 1).

For more information about this issue, refer to the following TechNote
on the Symantec Support Web site.

http://entsupport.symantec.com/docs/304860
--------------------------------------------------------------------------------
Etrack Incident = ET1364465

Description:
The SharePoint Portal/Web Application in a federated configuration with
additional content databases would produce multiple images for a single
portal/web application.
--------------------------------------------------------------------------------
Etrack Incident = ET1178607
Associated Primary Etrack = ET1178542
Titan cases: 281-250-638

Description:
The bpdm log would show that the "bpdm -d -p" operation failed with a
status 83. The bpdbm log noted this issue and then proceeded to delete the
imageDB entry anyway.

This release contains scalability and performance Catalog Cleanup Disk
image expiration solutions to address to address issues similar to this.
--------------------------------------------------------------------------------
Etrack Incident = ET1361434

Description:
A multiple copy backup to a Nearstore P3 storage unit would fail with a
status 83 - media open error (final status 40).
--------------------------------------------------------------------------------
Etrack Incident = ET1385494
Associated Primary Etrack = ET1270507
Titan cases: 311-914-328

Description:
Vault would fail to duplicate images if the media server name of the
images was different from the media server name in vault selection's
media server filter.

A fix was added to treat media server names case in-sensitively.

Workaround:
If you were to encounter this issue, use the Vault Global preferences to
establish the host name aliases.
--------------------------------------------------------------------------------



Maintenance Pack History
------------------------

This section contains an accumulative list of all Maintenance Pack information
contained in previous releases.

=========
NB_60_6_M
=========
Etrack Incident = ET819221
Associated Primary Etrack = ET797322
Titan cases: 280-670-054

Description:
Pegasus Software Drives on Windows did not work in NetBackup 6.0 as Disk
Storage Units.
--------------------------------------------------------------------------------
Etrack Incident = ET1106653

Description:
Added support for StorageGroup, Database, and Mailbox backup and restore
operations of Exchange 2007 on x64 platforms. Users will continue to use
the MS_Exchange_2000 directive Set and Microsoft Information Store:\
directive to create a backup list.

Additional Notes:
This Exchange 2007 support is for non-Advanced Client backup schedules only.
--------------------------------------------------------------------------------
Etrack Incident = ET1065715 ET1133900

Description:
For additional platform support and for security reasons, the Sybase ASA
level needs to be updated to 9.0.2+3526 EBF.

--------------------------------------------------------------------------------
Etrack Incident = ET1051431

Description:
The NetBackup-Java Administration Console would not configure a TLD
robot with 255 drives. More specifically, the device configuration
wizard would not configure the robot controller, stating that it has
too many drives.

The media server would build 128 tape paths, leaving the other 128
with only a sg path. This made only 128 tape drives available for
the server to use.
--------------------------------------------------------------------------------
Etrack Incident = ET1064859

Description:
The Device Allocator (DA) was not handling back-level Windows media
server paths correctly.

Back-level media servers could be brought up by going to the device
manager > devices > media servers user interface and restart the
device manager service. The server would display as active for tape
and disk, and the vmoprcmd command would also show them. However,
within a few minutes, the vmoprcmd command would no longer show at
least some of the server and after performing a refresh on the user
interface, they would appear only as active on for disk.

A change was made to address this issue in this pack.
--------------------------------------------------------------------------------
Etrack Incident = ET917571

Description:
The serial number of a newly discovered drive was being used while
forming the MISSING_DRIVE path name.

--------------------------------------------------------------------------------
Etrack Incident = ET1100826
Associated Primary Etrack = ET1100064
Titan cases: 320-060-202

Description:
Performing a relayout of VxVM volumes that are on an encapsulated root
disk group on a Solaris client creates a situation where the machine
will not boot after restoration. This is due to a defect where the VxVM
volume field use_type for both the rootvol and swapvol are set to
"fsgen" instead of "root" and "swap" respectively.

Workaround:
To resolve this issue, perform the following procedure:

1) On the master server, after running Prepare To Restore, run the
following:
bmrs -o query -r database -t restoreconfigfile
2) Note the name of the <hex_address>.restore file name for the client
from the output
3) Enter the following:
bmrc -o pull -r info -client <client> -source <hex_address>.
restore -dest /tmp/client.restore
4) Edit /tmp/client.restore and find shell script code for "rootvol"
and "swapvol". Once you find those entries for creating those
volumes, search for use_type for each and change "fsgen" in each to
"root" and "swap" respectively.
5) Enter the following:
bmrc -o push -r info -c client -source /tmp/client.restore -dest
<hex_address>.restore
6) Continue with normal restoration.
--------------------------------------------------------------------------------
Etrack Incident = ET1050256

Description:
The Device Configuration Cache would configure drives with no paths
as enabled.

--------------------------------------------------------------------------------
Etrack Incident = ET1077696
Associated Primary Etrack = ET936099
Titan cases: 220-084-917 220-097-471

Description:
A change has been made to address some deadlock issues that would
occur in the NetBackup Resource Broker (nbrb).
--------------------------------------------------------------------------------
Etrack Incident = ET995889
Associated Primary Etrack = ET967686
Titan cases: 230-267-566

Description:
If one job (Copy 1) was failed using the following configuration, then
all of the ITC jobs would be failed. The configuration encompasses an
ITC backup (Multiple Copies) to a Nearstore STU with the "File System
Export" option enabled.

For example:
Copy 1: use Nearstore Storage and "File System Export" is enabled
Copy 2: use Nearstore Storage and "File System Export" is enabled
Copy 3: use Basic Disk Storage

All copies are set "For each image if this copy fails" to "continue"

If Copy1 job fails, Copy2 and Copy3 jobs also fail, however, the other
jobs (Copy2 and Copy3) should NOT be failed.

A user can duplicate in the following configurations.
1) Copy1 use Nearstore Storage with "File System Export" option
2) Copy1 use MM Storage and another copy use Nearstore Storage with
"File System Export" option
--------------------------------------------------------------------------------
Etrack Incident = ET1104857
Associated Primary Etrack = ET1091014
Titan cases: 281-141-577 290-931-682

Description:
In case of TLH library, In-use tapes are not being flagged as
"Not Ejected" in the Picking List Report. A change has been made to
ensure that In-use tapes are not marked as ejected.
--------------------------------------------------------------------------------
Etrack Incident = ET1075835
Associated Primary Etrack = ET1074555
Titan cases: 220-100-495

Description:
As per the NetBackup Vault Administrator's Guide, the output of the
Pick List for Robot should be sorted by the media ID. The output was
being sorted by the slot ID. A change has been added that ensures that
the output of the Pick List for Robot adheres to how it is documented
in the NetBackup Vault Administrator's Guide.
--------------------------------------------------------------------------------
Etrack Incident = ET1047273
Associated Primary Etrack = ET1044565
Titan cases: 290-777-895

Description:
After catalog recovery, the Sybase ASA server name that is stored in
NetBackup configuration files will be checked to make sure that all
copies are consistent with each other.
--------------------------------------------------------------------------------
Etrack Incident = ET786040 ET1086515
Associated Primary Etrack = ET648063
Titan cases: 290-267-752

Description:
Changes have been added to this pack to address the following issues.

- The bpdbm -consistency command would always move corrupt images to
the db.corrupt folder, even if the -move option was not specified.

- The bpdbm -consistency command produced confusing and duplicate
messages while moving corrupt images to the db.corrupt folder.

- The bpdbm -consistency -move command failed when db.corrupt was
mounted on a different volume.
--------------------------------------------------------------------------------
Etrack Incident = ET962767

Description:
tpext now allows you to load a new version of the external_types.txt
file into the EMM database from only the EMM server or the master server.
--------------------------------------------------------------------------------
Etrack Incident = ET937157 ET971736 ET1019102 ET1060918 ET1075048 ET1075976

Description:
The nbpushdata functionality has been updated to match the level of
functionality released in the NetBackup 6.5 version of nbpushdata.
--------------------------------------------------------------------------------
Etrack Incident = ET1101998

Description:
Shutdown of the NBDB and BMRDB databases was prevented if the vxdbms.conf
file did not exist. This caused bprecover from a cold catalog backup to
fail. This issue has been fixed in this pack.
--------------------------------------------------------------------------------
Etrack Incident = ET1110609
Associated Primary Etrack = ET1094524
Titan cases: 240-610-300

Description:
If the NetBackup Job Manager (nbjm) crashed for some reason, a job
from the new nbjm could join a multiplexed group created by the old
nbjm. This, in some extreme scenarios, would cause media to be
over-written.
--------------------------------------------------------------------------------
Etrack Incident = ET1016302
Titan cases: 311-336-415

Description:
During a synthetic backup, the "Files Written" field was incorrectly
updated in the Activity Monitor. In addition, the "begin synthetic reader"
messages were missing.
--------------------------------------------------------------------------------
Etrack Incident = ET1102522

Description:
Under NetBackup Access Control (NBAC) in a cluster, the credentials
for the server may not be renewed properly.

Workaround:
To resolve this issue, run bpnbat -loginmachine on the target host
once every 14 days.
--------------------------------------------------------------------------------
Etrack Incident = ET1111554
Associated Primary Etrack = ET1107730
Titan cases: 220-104-078

Description:
Automatic device configuration was not handling drive and robot path swaps
correctly. If a drive and a library swapped paths (SCSI coordinates) on a
Windows system, the automatic device configuration code in EMM would not
handle the swap correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET1108542
Titan cases: 220-104-989 220-107-219 220-118-323 220-195-299 220-215-215
220-216-305 230-456-808 240-634-362 240-701-437 281-195-128 281-197-694
281-198-343 281-239-493 281-261-204 281-275-450 290-866-679 290-891-360
311-673-460 311-684-296 320-076-458 320-080-650

Description:
When trying to restore, either from the bprestore command on the client
or from the NetBackup Administration Console on the master, the restore
would fail with a status 25 error. Bpbrm would dump a core file and then
exit, and bptm would report a connection failure to bpbrm.
--------------------------------------------------------------------------------
Etrack Incident = ET1112393

Description:
Robotic drive 128 was treated as a negative number in tldd and tldcd.

--------------------------------------------------------------------------------
Etrack Incident = ET1111632
Associated Primary Etrack = ET1110560
Titan cases: 220-106-633 220-107-647 220-123-952 220-124-005 220-128-090
220-134-360 220-135-424 220-141-611 220-166-641 220-195-865 230-465-751
230-486-709 240-636-320 240-638-126 240-679-234 281-188-518 281-194-083
281-218-316 281-225-395 281-226-360 281-228-919 281-229-734 281-232-785
281-251-406 290-838-026 290-849-196 290-852-756 290-879-214 290-885-868
311-667-624 311-721-571 311-757-726 320-075-784 320-080-207

Description:
NDMP Backups would fail with an error code 27 if the NUMBER_DATA_BUFFERS
file was present.

Workaround:
To resolve this issue, remove the NUMBERS_DATA_BUFFERS file.
--------------------------------------------------------------------------------
Etrack Incident = ET1099114
Associated Primary Etrack = ET1073973
Titan cases: 281-138-275

Description:
Jobs were being started slowly causing delays. Thus, a change was made
so that other threads that are waiting to get time can be processed.
--------------------------------------------------------------------------------
Etrack Incident = ET1116059

Description:
Linux restoration could break into auto-DDR mode and not allow the
user to restore the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1089269
Associated Primary Etrack = ET1089215
Titan cases: 240-603-428

Description:
Nbpemreq was not correctly predicting backups in policies that did not
have a window open spanning when a schedule was due.
--------------------------------------------------------------------------------
Etrack Incident = ET1081386
Associated Primary Etrack = ET916709
Titan cases: 280-859-612

Description:
In certain circumstances, the delay between bptm/bpdm sending their
exit status to bpduplicate and bpduplicate receiving it could be great
enough to cause bptm/bpdm to shutdown before the transaction was
complete. This caused bpduplicate to wait beyond the end of the actual
job and eventually failed the entire job.
--------------------------------------------------------------------------------
Etrack Incident = ET1109594
Associated Primary Etrack = ET1109590
Titan cases: 290834099

Description:
The post-restoration boot of a Solaris client fails with the error,
"No boot block install target device is specified".

If the client originally had a VxVM encapsulated root disk that was
mirrored and a plex on any of the encapsulated volumes was disabled,
the import of the client configuration would not recognize the disk
encapsulation and fail to recreate the underlying disk slices.
--------------------------------------------------------------------------------
Etrack Incident = ET1118215
Associated Primary Etrack = ET1114229
Titan cases: 230-413-472

Description:
Snapvault backups would fail with a status code 156 after several hours.
In some cases, large Qtree backups would fail because a timer was reached
prematurely.
--------------------------------------------------------------------------------
Etrack Incident = ET1118152
Associated Primary Etrack = ET1081398
Titan cases: 220-101-140

Description:
This changes what is deleted during disk backup errors. Previously,
the current working fragment was the only fragment that was removed
before bpXm exits. It was left to the catalog to remove any other
fragments as part of the expiration and cleanup process.

With this change, the bpXm process removes all fragments it can safely
remove for the backup in progress in addition to the fragment in
progress. An exception is the case when backup checkpoints exist. The
cleanup process does not remove backup checkpoints.
--------------------------------------------------------------------------------
Etrack Incident = ET1115944
Associated Primary Etrack = ET1115544
Titan cases: 320063430

Description:
AIX restores fail if any of the logical volumes being restored have an
Intra-Disk policy of "inner middle" or "inner edge"

Workaround:
To avoid this issue, use DDR to exclude such volumes from the
restoration, if possible.

Additional Notes:
After you install this pack, you must run a new backup on the client, or
use Point-In-Time retrieval for that client before this fix is effective.
This includes retrieving the "current" configuration from the client
backup, in case the client is unavailable for a new backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1119044

Description:
Running a Point-in-Time (PIT) configuration retrieval for a Windows
client that is utilizing a UNIX or Linux Master Server could fail due
to a difference in the NetBackup client installation path versus the
INSTALLDIR setting in the registry. The installation path uses
"VERITAS" and the registry entry uses "Veritas". This becomes a
case-sensitivity issue when performing this type of operation on a UNIX
or Linux Master Server.
--------------------------------------------------------------------------------
Etrack Incident = ET1053711
Associated Primary Etrack = ET1044565
Titan cases: 290-777-895

Description:
During a hot catalog recovery, if the NBDB and BMRDB databases have
been recreated (a clean install) before recovering from the backup, the
current online transaction log would not be able to be applied. This
was normal and expected behavior, however, the debug and progress logs
did not give an adequate explanation on what was happening.

A change has been made to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET863161
Associated Primary Etrack = ET850048
Titan cases: 240-306-456

Description:
When a quota is filled on a disk storage unit, the disk as a whole is not
considered to be full. As a result, staged images were not deleted to
allow the backup to finish and the backup would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1122376

Description:
The bpsyncinfo -add_paths command did not add any paths to the cold
catalog backup sync file.
--------------------------------------------------------------------------------
Etrack Incident = ET1056577

Description:
Network Data Management Protocol (NDMP) incremental backups that
included two or more paths, where the first path had no changed files,
were failing to verify.

Additional Notes:
A change was added that prevents the problem from occurring with
backups taken after this fix is installed. Backups that were taken
prior to installing this pack could still fail to verify. The problem
does not prevent a successful restore.
--------------------------------------------------------------------------------
Etrack Incident = ET1016205
Titan cases: Allstate

Description:
A problem existed that caused many drives go into Automatic Volume
Recognition (AVR) mode for a period of time, then return to normal mode.
--------------------------------------------------------------------------------
Etrack Incident = ET1103635
Associated Primary Etrack = ET1103581
Titan cases: 240-620-126

Description:
bpbackupdb would return a status code 50 when issued from the
command line interface (CLI) when VxSS was enabled. The administration
log reports success. A status 0 would be returned when initiated from
pbadm or NetBackup-Java Administration Console.

Workaround:
To resolve this issue, disable VxSS and bpbackupdb will return a status 0
from the CLI.
--------------------------------------------------------------------------------
Etrack Incident = ET1116287
Associated Primary Etrack = ET1095286
Titan cases: 240-626-756 281-142-668

Description:
The SnapVault secondary incremental image is not removed when the NetBackup
image expires. This issue only occurs when the images are retained for
30 days or longer.

Clean-up logic in the code would remove reference files from the NetBackup
Server. Without these files NetBackup cannot remove the snapshot images
from the secondary.

Workaround:
To avoid this issue, reduce the retention periods for Snapvault policies to
less than 30 days.
--------------------------------------------------------------------------------
Etrack Incident = ET1032459

Description:
If the NetBackup configuration includes NetBackup 5.x media servers that
are inactive, the Hot Catalog Backup policy would fail with a status 25:
cannot connect on socket. For example, this could occur if the 5.x media
server was registered in EMM, but, there was no NetBackup software
installed or configured on the media server.
--------------------------------------------------------------------------------
Etrack Incident = ET1122873

Description:
Incremental Hot Catalog backups could hang.
--------------------------------------------------------------------------------
Etrack Incident = ET1078507

Description:
Zero-byte image header files could be created when two bpdbm processes
requested locks for the same image header at the same time and one of
the processes was validating the image.
--------------------------------------------------------------------------------
Etrack Incident = ET1081410
Associated Primary Etrack = ET1064989
Titan cases: 290-661-307

Description:
The bpdbm -consistency command was core dumping after processing
corrupted catalog files.
--------------------------------------------------------------------------------
Etrack Incident = ET936893
Associated Primary Etrack = ET936885
Titan cases: 280-590-785

Description:
When using a Terminal Service Session to connect to the Master server,
the following scenario explains an issue that was found and fixed.
- Administrator "A" opens an Administration console in the normal
course of duty to monitor, and so forth.
- Administrator "B" opens an Administration console and performs an
add for a new policy or modify an existing policy.
- Administrator "B" then closes their console when the work is finished.
- Administrator "A" closes their Administration console at the end of
their shift. (Note, other users may have logged in and out during
the course of their day as well)
- It was discovered that a "random" policy was missing or corrupted on
the NetBackup server.
--------------------------------------------------------------------------------
Etrack Incident = ET856463

Description:
Added support for -drfile -drfile_dest options to the bpimport command.
This allows for importing a Disaster Recovery (DR) file from a hot
catalog backup, and is documented in the NetBackup Troubleshooting
Guide.
--------------------------------------------------------------------------------
Etrack Incident = ET1112364

Description:
A change has been made that prevents a segmentation fault from occurring
during Sybase Catalog backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1115046
Associated Primary Etrack = ET1112383
Titan cases: 230-406-221

Description:
The NetBackup Sybase agent would incorrectly parse isql load commands
that contained certain keywords.
--------------------------------------------------------------------------------
Etrack Incident = ET1119141
Associated Primary Etrack = ET1110077
Titan cases: 1110077 220-107-339 220-107-436 220-107-445 220-107-522
220-107-687 220-109-637 220-114-833 220-118-922 220-121-897 220-123-950
220-125-736 220-128-088 220-133-998 220-137-410 220-141-606 220-156-184
220-223-834 230-422-980 230-434-222 230419912 240-624-298 240-639-570
240-639-994 240-641-226 240-693-867 281-185-246 281-186-665 281-187-293
281-208-063 281-210-344 281-213-877 281-221-450 281-222-551 281-224-311
281-226-390 281-229-734 281-245-454 281-247-498 281-248-070 281-251-406
281-257-608 281-260-719 281-268-264 281-268-820 281-274-995 281-282-661
281-301-382 281218316 290-842-404 290-843-173 290-843-290 290-843-902
290-845-748 290-846-298 290-853-590 290-855-426 290-857-281 290-860-508
290-880-192 290-898-136 290-903-709 290-906-022 290-914-220 290-969-212
290-980-285 311-772-601 320-067-544 320-072-400 320-075-312 320-076-565

Description:
Compression and decompression of .f files was failing with
NetBackup 6.0 MP5.
--------------------------------------------------------------------------------
Etrack Incident = ET609282 ET788886
Associated Primary Etrack = ET773552
Titan cases: 240-168-192 290-242-220

Description:
Synthetic backup run on policies in which some of the catalog images
were compressed would uncompress the catalog images to new files. This
left the original compressed file untouched and caused an increase in
the amount of disk space required for the catalog.

With this patch, the compressed images are uncompressed for the
duration of the synthetic backup catalog query, then compressed again.

Workaround:
To avoid this issue, set the catalog image compression to not occur
until after synthetic policies are run.
--------------------------------------------------------------------------------
Etrack Incident = ET1044598 ET1126542 ET1126545
Associated Primary Etrack = ET1044598 ET1044598

Description:
A change has been added to make nbsu version 1.2.5 available on all
platforms. The fix is for the DNS nslookup < IP Address> acquisition of
associated alias hostnames.
--------------------------------------------------------------------------------
Etrack Incident = ET1125132
Associated Primary Etrack = ET1110081
Titan cases: 220-104-676

Description:
bpdbm could core dump when reading corrupted .f files.
--------------------------------------------------------------------------------
Etrack Incident = ET1074817
Associated Primary Etrack = ET1046768
Titan cases: 220-141-713 240-571-701

Description:
Many nbpem child processes will not run if the backup_exit_notify
script cannot execute.

Workaround:
To resolve this issue, make sure that a backup_exit_notify script exists
and it has execute permissions.
--------------------------------------------------------------------------------
Etrack Incident = ET701767
Associated Primary Etrack = ET701066
Titan cases: 220-060-766

Description:
bplist would fail when it was used with directories that contained the
'{' character in the name.
--------------------------------------------------------------------------------
Etrack Incident = ET1058587

Description:
Catalog backups could end with a conditional success.
--------------------------------------------------------------------------------
Etrack Incident = ET619266
Titan cases: 230-117-184

Description:
Vault appeared to run one batch short of the total number of
duplication batches. This was a cosmetic issue with empty disk
batches and occurred only when the number of images to duplicate was
less then number of write drives.

A change was made that ensures the empty disk batches are processed
correctly to reflect the correct total number of batches.
--------------------------------------------------------------------------------
Etrack Incident = ET930868

Description:
You can use mmcrawl to detect device configuration conflicts, or errors
and inconsistencies from the NetBackup 5.x upgrade process.

--------------------------------------------------------------------------------
Etrack Incident = ET1124179
Titan cases: 290-842-791

Description:
Manually-submitted, immediate backups would queue very slowly.

Workaround:
To avoid this issue, create a policy that schedules a job to run in
the future.
--------------------------------------------------------------------------------
Etrack Incident = ET1128964

Description:
A change was added to address a potential core dump issue for the nbemm
process.
--------------------------------------------------------------------------------
Etrack Incident = ET1119149
Associated Primary Etrack = ET1095265
Titan cases: 281-146-400

Description:
In some cases, memory allocations larger than what Windows would accept
were being attempted and caused incremental Flashbackups to fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1115039
Associated Primary Etrack = ET1112554
Titan cases: 281-179-170

Description:
The log message format changed between NetBackup 5.x and NetBackup 6.x
in the following manner:
- The NetBackup 5.x message was, "the requested operation was
successfully completed."
- The NetBackup 6.0MP5 (and previous) message was, "the requested
operation was successfully completed"

Workaround:
Customers may have to modify their scripts that parsed logs to determine
results on jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1115151
Associated Primary Etrack = ET410360
Titan cases: 290-837-362

Description:
Encrypted backups would be reported as successfully completed even if no
valid encryption keys existed on the system. This would create a backup
image that was encrypted with a pseudo random key. The restore of the image
would fail.

Workaround:
If you encounter this issue, add an encryption key for encrypted backups to
use.
--------------------------------------------------------------------------------
Etrack Incident = ET1032486

Description:
A problem existed where a process would crash if nbemm shutdown while
it was fetching drive information. In addition, nbemmcmd would crash
if the EMMSERVERNAME parameter was not defined in either the bp.conf
file or the registry.
--------------------------------------------------------------------------------
Etrack Incident = ET993132
Associated Primary Etrack = ET993129

Description:
A change was added that allows a rename in nbemmcmd for a cluster
machine type.
--------------------------------------------------------------------------------
Etrack Incident = ET1077799

Description:
A memory leak existed in the EMM access library when the Machine
Configuration was queried.
--------------------------------------------------------------------------------
Etrack Incident = ET1095195
Associated Primary Etrack = ET1087426
Titan cases: 230-396-756

Description:
Lotus backups and restores would fail if the user did not have the
read and execute permissions set in the root user's home directory
or in root of file system (/).
--------------------------------------------------------------------------------
Etrack Incident = ET1125794
Associated Primary Etrack = ET1124254
Titan cases: 220-106-791 311-838-646

Description:
A change has been added to resolve an nbpem crash issue that would
occur repeatedly after NetBackup 6.0 MP5 was installed.

Additional Notes:
This problem was not introduced with NetBackup 6.0 MP5.
--------------------------------------------------------------------------------
Etrack Incident = ET1051239
Associated Primary Etrack = ET1040750
Titan cases: 240-576-334

Description:
NetBackup Vault Administrator console (both Windows and UNIX) and
vltadm have a problem showing the vault configuration, after a catalog
restore is done. This happens because a vault service does not get
started.

Workaround:
To resolve this issue, restart the vault service (nbvault) a second time.
--------------------------------------------------------------------------------
Etrack Incident = ET1039190
Associated Primary Etrack = ET1006955
Titan cases: 281-016-998

Description:
A change has been added to allow more than 64 volumes to be protected.
--------------------------------------------------------------------------------
Etrack Incident = ET1041113

Description:
The user interface would crash when discovering the operating system of the
client that is being added to a policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1130594
Associated Primary Etrack = ET1124350
Titan cases: 240-626-530

Description:
The restoration of a client with a DMP-attached fibre device that
utilizes VxVM would fail during VxVM disk initialization operations.
--------------------------------------------------------------------------------
Etrack Incident = ET1075535

Description:
Lotus backups and restores will fail if the absolute path for the
NOTES.INI file contains a space in it.


Workaround:
To avoid this issue, install the Lotus Domino server at a location
where the path does not contain a space.

--------------------------------------------------------------------------------
Etrack Incident = ET1034245

Description:
Messages from listAllocationStatus were not logging the full function
name.
--------------------------------------------------------------------------------
Etrack Incident = ET991063

Description:
The nbemmcmd -forcemerge command would fail for optical media.
--------------------------------------------------------------------------------
Etrack Incident = ET1067776

Description:
EMM library calls would leak memory after receiving the interface
reference from EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET1062667
Associated Primary Etrack = ET1032373
Titan cases: 240-540-817

Description:
bpstuadd creates a SERVER entry in the master bp.conf file even though
the MEDIA_SERVER entry already exists.

Workaround:
After running bpstuadd, manually modify the server list to remove the
SERVER entry.
--------------------------------------------------------------------------------
Etrack Incident = ET1129777
Associated Primary Etrack = ET1062665
Titan cases: 220-099-185

Description:
A change was added that offers a less aggressive unloading of drives using
a touchfile on the EMM server.

Additional Notes:
The following is the touchfile on the EMM server that triggers the
unloading of files:
"/usr/openv/netbackup/db/config/RB_DISABLE_REAL_UNLOADS_ON_DEMAND"

The following items describe the behavior of this touchfile:
1) The media unload delay will remain at the default of three minutes
for user backup jobs.

2) If there is another job in the queue that can use the media where it is
mounted, then that job can still get the media ahead of the next user
backup job.

3) If there is another job in the queue that can use the drive on a
different media server or with different media, the drive will NOT be
unloaded until the media unload delay expires.

The primary behavior changed in this touchfile is described in item
number 3. Without the touchfile, the drive could be unloaded if there
is a job in the queue that could use the drive on a different media
server or with different media
--------------------------------------------------------------------------------
Etrack Incident = ET1130930
Associated Primary Etrack = ET1079305
Titan cases: 240598535

Description:
Inline Tape Copy (ITC) backups with multiplexing (MPX) enabled could
result in Status Code 63 when spanning media.
--------------------------------------------------------------------------------
Etrack Incident = ET1131165
Associated Primary Etrack = ET1091665
Titan cases: 290-823-681

Description:
The NetBackup Service Layer (nbsl) failed to terminate using the
"netbackup" script or the "nbsl -terminate" command after starting
with the "at" command.
--------------------------------------------------------------------------------
Etrack Incident = ET1131156
Associated Primary Etrack = ET1131135
Titan cases: 230-431-828

Description:
Unable to connect to the NetBackup Service Layer Service on the host
after selecting, Media and Device Manager > Media.
--------------------------------------------------------------------------------
Etrack Incident = ET1101047
Associated Primary Etrack = ET1101043

Description:
Multi-threading issues existed in the EMM library where the reference
to the EMM server could be reset while it was in use. This resulted in
a core dump from the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1100900
Associated Primary Etrack = ET1094524
Titan cases: 240-610-300

Description:
A change was made to BPTM to detect empty MDS strings. If a message was
received with no strings, bptm would erroneously treat it as a valid
message and use the existing strings which could lead to possible data loss.
--------------------------------------------------------------------------------
Etrack Incident = ET999338

Description:
After a movedb operation was performed, the media server version could
not be obtained from EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET1106653

Description:
This pack contains Exchange 2007 Proliferation changes that were included in
the NetBackup 6.0 MP5S01 special pack.

Additional Notes:
This Exchange 2007 support is for non-Advanced Client backup schedules only.
--------------------------------------------------------------------------------
Etrack Incident = ET1098395
Associated Primary Etrack = ET1075821
Titan cases: 281-124-171

Description:
The alternate restore of International folder and file names failed when
restoring from a Windows source client to a Windows destination client.
--------------------------------------------------------------------------------
Etrack Incident = ET862454
Associated Primary Etrack = ET862405
Titan cases: 220-037-863

Description:
For a NetBackup 4.5 FlashBackup image, a restore could miss files if
the file records in the catalog are out of order. For example:
/dir/dir1/file1
/dir/dir1/file2
/dir/dir1/
/dir/dir1/file3

If a restore was attempted, and just /dir/dir1/ was specified, then
only /dir/dir1/ and /dir/dir1/file3 was restored.
--------------------------------------------------------------------------------
Etrack Incident = ET1111365
Associated Primary Etrack = ET1059484
Titan cases: 290-659-726

Description:
The Remote Administration user interface became unresponsive when changing
client attributes in the master server Host Properties window.
--------------------------------------------------------------------------------
Etrack Incident = ET1054735
Associated Primary Etrack = ET1054732
Titan cases: 220-096-800 290-755-811

Description:
vltopmenu needlessly consumed CPU cycles when waiting for an eject
operation. This happened when a robot did not have an empty MAP/CAP for
an eject operation, and at that time, vltopmenu would go into an
endless loop. This issue caused high CPU utilization.

Additional Notes:
You could observe this problem for robots ACS or TLM or TLH, on which
you have MAP/CAP to eject or inject the media(tape).
--------------------------------------------------------------------------------
Etrack Incident = ET1073969

**Description:
System state restores would randomly crash on Windows Vista systems.
--------------------------------------------------------------------------------
Etrack Incident = ET1059861
Associated Primary Etrack = ET1056231
Titan cases: 240-512-525

Description:
The bprecover script would fail if the NetBackup-Java Administration
Console was never launched by the executing user. It failed because the
user_ops/<username>/jobs did not exist unless the console was started.
bprecover now checks that this directory exists for the user and creates
it if necessary.

Workaround:
To resolve this issue, start the NetBackup-Java Administration Console
and then run bprecover.
--------------------------------------------------------------------------------
Etrack Incident = ET1132293
Associated Primary Etrack = ET1114024
Titan cases: 230-416-089

Description:
If the primary copy for a backup was higher than 2, and a copy with
a lower copy number was expired, the primary copy would be reset
incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET1082843
Associated Primary Etrack = ET1075693
Titan cases: 320-055-552

Description:
Added additional status information to the SAP BRTOOLS log.
--------------------------------------------------------------------------------
Etrack Incident = ET1072957
Associated Primary Etrack = ET1051977
Titan cases: 290-795-451

Description:
During multiplexing (MPX) and Inline Tape Copy (ITC) backups or
duplications, an error could occur during an end of media (EOM) event
that would result in a status code 229.
--------------------------------------------------------------------------------
Etrack Incident = ET969293

Description:
When encryption is selected for a Lotus policy, the backup would
look like it hung. However, after waiting about 15 minutes the
backup would exit.
--------------------------------------------------------------------------------
Etrack Incident = ET1075540

Description:
After recovery, if the renaming a file from the temporary path to
its original name failed, it indicated that the paths were not logged
in the tar logs.
--------------------------------------------------------------------------------
Etrack Incident = ET1060843

Description:
Added support of the 32-bit Lotus/Domino on Windows 64-bit platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET1075552

Description:
Backing up and restoring Lotus transaction logs fail if the Lotus
transaction logging is enabled to the Internationalization (I18N)
path.

Workaround:
To avoid this issue, enable the Lotus transaction logging to a
normal (Non-I18N) path.
--------------------------------------------------------------------------------
Etrack Incident = ET834749

Description:
After catalog recovery, the NetBackup scheduler is suspended.
NetBackup will not run scheduled backup jobs until NetBackup is stopped
and restarted. A warning message will now be displayed at the end of
the catalog recovery to indicate this.
--------------------------------------------------------------------------------
Etrack Incident = ET936891
Associated Primary Etrack = ET936885

Description:
If multiple administrators used Windows consoles to update policies, some
policies would get deleted, leaving clients within them un-protected.
--------------------------------------------------------------------------------
Etrack Incident = ET1133604
Associated Primary Etrack = ET936099
Titan cases: 220-084-917 220-097-471

Description:
The NetBackup resource Broker (nbrb) would hang in some scenarios,
and the backup jobs would remain queued.
--------------------------------------------------------------------------------
Etrack Incident = ET1129723

Description:
Changes were made to address possible buffer overflows in the
Lotus Notes agent.
--------------------------------------------------------------------------------
Etrack Incident = ET1131174

Description:
A change was made to remove an exception that would occur from the
collection-module if an error occurred within EMM, causing nbsl to
crash.
--------------------------------------------------------------------------------
Etrack Incident = ET1131176

Description:
A change was made to remove an exception that would occur from the
collection-module if an error occurred within EMM, causing nbsl to
crash.
--------------------------------------------------------------------------------
Etrack Incident = ET1131169

Description:
Corruption was found during a parsing operation that was not anticipated.
This issue caused a null-pointer access that caused core dump issues.
--------------------------------------------------------------------------------
Etrack Incident = ET1075550
Titan cases: 280-514-582

Description:
Issues related to FULL Lotus Notes backups that display behaviors like a
Transaction log backup will not be recycled. Refer to the following example.

tar_base::V_vTarMsgW: WRN - Abnormal backup status, Lotus Transaction
Logs will not be recycled

nbex_DebugLog: INF - NBLN_ArchiveLogEnd()Transaction log archiving has
not previously been started.
--------------------------------------------------------------------------------
Etrack Incident = ET1064771
Titan cases: 320023286

Description:
A change was added that enables you to unload and reload the ASA
database from the nbdb_unload command line.
--------------------------------------------------------------------------------
Etrack Incident = ET1096991
Titan cases: 220-099-064

Description:
Characters that do not meet the naming guidelines for media ID were
being allowed. Media with these IDs would not behave properly.
--------------------------------------------------------------------------------
Etrack Incident = ET1118074

Description:
The potential for a crash existed if variable length corba parameters
were not initialized before a function returned.
--------------------------------------------------------------------------------
Etrack Incident = ET1127677
Associated Primary Etrack = ET1122811
Titan cases: 230-430-097 281-211-845 290-845-354

Description:
The bpdbjobs output was truncated for the STARTED and ENDED fields.
A change has been added to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1124931
Associated Primary Etrack = ET1120656
Titan cases: 290-821-914 311-887-438

Description:
The PureDisk export policy failed with a status 227 as the wrong image
path used to try to write a file.
--------------------------------------------------------------------------------
Etrack Incident = ET1098793
Associated Primary Etrack = ET1096808
Titan cases: 281-156-083

Description:
The bpdbjobs -report output had truncated fields for the Elapsed and
Active Elapsed fields.
--------------------------------------------------------------------------------
Etrack Incident = ET1096660

Description:
Wrong values were being shown for the Job ID and Job Type fields.
--------------------------------------------------------------------------------
Etrack Incident = ET1131177

Description:
NetBackup policies and clients were not updated in NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET1131183

Description:
If there were many media servers connected to a master server, NOM
would timeout while collecting the service information if some the
media servers were down or not responding.
--------------------------------------------------------------------------------
Etrack Incident = ET1094037 ET1131285

Description:
Changes were added to this pack to address the following issues:
- An nbsl core dump issue that occurred on a Solaris-managed server
- The inability to read the job and log manager's IOR by proxy
--------------------------------------------------------------------------------
Etrack Incident = ET1131098

Description:
A deadlock would occur when the JobMonitor was restarted when its separator
was being processed by the JobUpdaterThread.
--------------------------------------------------------------------------------
Etrack Incident = ET1094304
Associated Primary Etrack = ET843448
Titan cases: 280-792-796

Description:
An issue existed that caused an encrypted Windows backup to fail to
restore. An error status 92 was received and the error message read,
"Not in Tar format".
--------------------------------------------------------------------------------
Etrack Incident = ET1135508

Description:
Restoring from a multi-path NDMP backup may hang on a file from second
or later paths.

This type of backup fails with a restore from an NDMP backup that
included two or more paths, where the first path backed up completely
on one tape, then tape spanning occurred on a subsequent path. The
restore fails if a file from the first path is selected, then a file
that is completely on the second tape is selected.

Workaround:
To avoid this issue, restore files that are all within the same backup
path. If additional files are needed, restore them in a separate job.
--------------------------------------------------------------------------------
Etrack Incident = ET1128915
Associated Primary Etrack = ET1114286
Titan cases: 290-836-488

Description:
bpverify would core dump if it were run against a successful Windows
FlashBackup image.
--------------------------------------------------------------------------------
Etrack Incident = ET1136368
Associated Primary Etrack = ET1136314
Titan cases: 230-418-729 281-255-630

Description:
File names were truncated with an "=" sign which should have been a
valid character. And change was made to remove the code that overwrote
the "=" sign was removed.
--------------------------------------------------------------------------------
Etrack Incident = ET1054432
Associated Primary Etrack = ET1036349
Titan cases: 290-742-408

Description:
The parent bptm would core dump during a multiplex restore.

Workaround:
To resolve this issue, implement the NON_MPX_RESTORE touch file:
- UNIX: /usr/openv/netbackup/NON_MPX_RESTORE
- Windows: <install path>\VERITAS\NetBackup\NON_MPX_RESTORE

--------------------------------------------------------------------------------
Etrack Incident = ET1129714

Description:
The nbjm process would exit if an error occurred when establishing a
connection to a media server.
--------------------------------------------------------------------------------
Etrack Incident = ET404574
Titan cases: 220-057-865 290056071

Description:
Logging out of Windows would cause manually initiated verify, duplication,
import, and expdate operations to end prematurely.
--------------------------------------------------------------------------------
Etrack Incident = ET1054522 ET1122310 ET1016365
Associated Primary Etrack = ET1030108 ET1115368 ET997695
Titan cases: 290-765-337 281-181-444 240-432-799

Description:
The vmoprcmd -comment 0 command would not update comments if it
were blank. A drive status of stuck in "AVR" will now go to "TLD"
control.
--------------------------------------------------------------------------------
Etrack Incident = ET1030320
Associated Primary Etrack = ET1000662
Titan cases: 281-016-419

Description:
The status message socket between bptm and bpduplicate was being
dropped because a "keep alive" was not being set. A change was made
to send a keep alive on the socket during duplication jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1119235 ET1137969
Associated Primary Etrack = ET1275377 ET1129823
Titan cases: 240-628-676 281-176-389 220-125-326 281-239-168 290-868-053
290-838-243

Description:
A media write error was causing status 1 and status 191 errors on
staging duplications operations after NetBackup 6.0 MP5 was applied.
--------------------------------------------------------------------------------
Etrack Incident = ET1137257
Associated Primary Etrack = ET1115007
Titan cases: 240610300

Description:
In some error situations, bptm would overwrite data on a tape that was
left in a drive.
--------------------------------------------------------------------------------
Etrack Incident = ET1138853
Associated Primary Etrack = ET1135473
Titan cases: 240-628-279

Description:
A CORBA communication error (195) would occur during a vault
V_QUERY_BYPOOL that caused vault to fail with an error 332.
--------------------------------------------------------------------------------
Etrack Incident = ET1139766
Associated Primary Etrack = ET1116213
Titan cases: 220-105-172

Description:
A change was made to correct a case where bpmedialist would exit
without properly releasing its result set. In an environment with a
large number of media, this "result set leak" produced noticeable
growth in nbemm memory consumption over time.
--------------------------------------------------------------------------------
Etrack Incident = ET1107694
Associated Primary Etrack = ET1037368
Titan cases: 220-096-910 220-123-945 220-124-001 220-135-401 220-141-599
281-218-316 290-883-680

Description:
A change was made to nbpem to ensure all jobs that are due to start,
run as scheduled.
--------------------------------------------------------------------------------
Etrack Incident = ET1138823

Description:
The cold catalog backup would fail after the Sybase ASA database was
rebuilt. The failure produced the following error.

NB database backup failed, a path was not found or is inaccessible
--------------------------------------------------------------------------------
Etrack Incident = ET1141194
Associated Primary Etrack = ET1117970
Titan cases: 220-102-189

Description:
Vault was unable to suspend media using the name of an application
cluster.
--------------------------------------------------------------------------------
Etrack Incident = ET1049452
Associated Primary Etrack = ET1021162
Titan cases: 290-747-009

Description:
Resource allocation was not allocating or de-allocating resources.
This issue caused jobs to not run and the system to go down following
a reboot.
--------------------------------------------------------------------------------
Etrack Incident = ET1143290
Associated Primary Etrack = ET1143028
Titan cases: 290851148

Description:
Prepare to Restore would fail if the client has an upper case
specification in the policy configuration and bp.conf.
--------------------------------------------------------------------------------
Etrack Incident = ET602147

Description:
The restoration of an AIX client fails if a configuration mapping
occurs that does not include a JFS log for a volume group.

Workaround:
To resolve this issue, perform the mapping again, however include the
JFS log in the mapping operation.
--------------------------------------------------------------------------------
Etrack Incident = ET1141860

Description:
A logic error in bpduplicate prevented it from sending an exit status
acknowledgment to bpdm. bpdm waited a few minutes, stopped waiting,
and printed an error in the logs when there was no error.

Additional Notes:
There is no actual error and this scenario happens only after the job
is already successful.
--------------------------------------------------------------------------------
Etrack Incident = ET1131162
Associated Primary Etrack = ET1122821
Titan cases: 320-063-880

Description:
The NOM user interface would show the master as partially offline and
would no longer collect the job information.
--------------------------------------------------------------------------------
Etrack Incident = ET1078652

Description:
Able to import media from a scratch pool.
--------------------------------------------------------------------------------
Etrack Incident = ET1141801
Associated Primary Etrack = ET936099
Titan cases: 220-084-917 220-097-471

Description:
An issue existed where NetBackup would stop processing new jobs. This
was a sporadic issue that produced no errors and rarely occurred. The
jobs that were already active continued to run to completion, however
other jobs that were in the queue to run stay in the queue until
NetBackup was restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET1146112

Description:
The ServiceManager would be evicted even if the service data collection
was not started. This caused the client count in NOM to not match the
client count in NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET1145873
Associated Primary Etrack = ET1137937
Titan cases: 220-108-064

Description:
Duplication would fail on the second backup ID when duplicating from
an application cluster storage unit.
--------------------------------------------------------------------------------
Etrack Incident = ET1141129

Description:
NBSL could deadlock when making a connection to nbemm.
--------------------------------------------------------------------------------
Etrack Incident = ET1043447
Associated Primary Etrack = ET1041252
Titan cases: 281-035-231

Description:
When starting a backup a bpfis popup error occurred on the client. The
user should click OK in the pop-up error box and then the backup will
continue and run successfully. In addition, if the "Take checkpoint
every" box was unchecked for the policy then the issue was not seen.
--------------------------------------------------------------------------------
Etrack Incident = ET1150050

Description:
Database restores would receive core files from bptm if they were
canceled.
--------------------------------------------------------------------------------
Etrack Incident = ET1137310

Description:
Corrected an issue of adding multiple media in the media user
interface pane.
--------------------------------------------------------------------------------
Etrack Incident = ET1095133
Associated Primary Etrack = ET1075401
Titan cases: 220-099-852

Description:
When using the Oracle templates created with NetBackup, the
"NB_ORA_SCHED" parameter is not used when the actual RMAN commands
are executed.

This happens only for the first or initial subset of channel
allocations. Meaning, if the database is backed up, and then the
archive logs and the control file, the "NB_ORA_SCHED" parameter is
not used just for the database portion, it is also passed for the
archive logs and control file.

When the templates are converted to backup scripts, the "NB_ORA_SCHED"
parameter is present in all backup steps.

Workaround:
To resolve this issue, convert the Template to a script and use the
script in the policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1014122
Associated Primary Etrack = ET989114
Titan cases: 280-984-584

Description:
A change was added to allow multiple policies and schedules to be used for a
DB2 database backup.

Additional Notes:
This change only works on DB2 V8.1 FixPak 7 or later.

The syntax for specifying the policy and schedule using the command line is:
'db2 BACKUP DATABASE SAMPLE LOAD
/usr/openv/netbackup/bin/nbdb2.* OPTIONS
"DB2_POLICY=policy_name:DB2_SCHED=sched_name"'

The schedule passed using the command line must be of type "Application
Backup".

If the policy or schedule are passed using the command line then they
override whatever is defined in the db2.conf file.
--------------------------------------------------------------------------------
Etrack Incident = ET1154517
Associated Primary Etrack = ET1141889
Titan cases: 240-624-463

Description:
Storage unit group would not maintain the storage unit priority.
--------------------------------------------------------------------------------
Etrack Incident = ET1154458

Description:
The hot catalog backup would fail with a status 190. This issue would
occur when using a remote EMM server and incremental hot catalog backups.
--------------------------------------------------------------------------------
Etrack Incident = ET829241

Description:
The DB2 Proxy Restore of a raw data file would fail with a file count
mismatch.
--------------------------------------------------------------------------------
Etrack Incident = ET997692
Associated Primary Etrack = ET994917
Titan cases: 240-478-391

Description:
An improper status 0 was received on an Exchange Server Information Store
differential backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1152641
Associated Primary Etrack = ET1144027
Titan cases: 220-109-428

Description:
The catalog compression interval could not be set on master servers
running HP-UX IA64, Windows IA64, or Windows AMD64.
--------------------------------------------------------------------------------
Etrack Incident = ET1154418

Description:
Differential and cumulative incremental backups did not work as
expected in Lotus Domino server 8.0 GA.
--------------------------------------------------------------------------------
Etrack Incident = ET1142057
Associated Primary Etrack = ET1136380
Titan cases: 290-853-846

Description:
The ffilelogs for the restore job would show only the first directory that
was restored. A change was made to restore this functionality that existed
in earlier versions of NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET1157508
Associated Primary Etrack = ET1149031
Titan cases: 240649594

Description:
On SLES 9 IA64 Linux, nbpem executes the backup_exit_notify script
with a bad argument list - reports EFAULT.
--------------------------------------------------------------------------------
Etrack Incident = ET1152840

Description:
Restores from DB2 Snapshot only backups would fail if the DB2 database
contained DMS containers that were created using default paths.
--------------------------------------------------------------------------------
Etrack Incident = ET1077555
Associated Primary Etrack = ET1045839
Titan cases: 240-570-502

Description:
Changes were added to this pack to address the following two issues:
- An SQL Restore failure caused repeated mm_check_child_read:
Received StopDbRestore Event messages that caused a Disk full state.

- The bptm processes would not stop even though the restore completed
successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET1155362

Description:
The mmcrawl utility would consume more than 1.4GB of memory, making it
unable to allocate memory and therefore not run. A change was made to
address this memory consumption issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1120022

Description:
Changes were added to support Exchange 2007 database and mailbox backups and
restores.
--------------------------------------------------------------------------------
Etrack Incident = ET1147543
Associated Primary Etrack = ET1145806
Titan cases: 281213560

Description:
A NetBackup restore of Enterprise Vault migration data would truncate the
last character of a file name because of an improper rename file syntax.
--------------------------------------------------------------------------------
Etrack Incident = ET1157003

Description:
Exchange 2007 databases would fail to mount and dismount.
--------------------------------------------------------------------------------
Etrack Incident = ET1161349
Associated Primary Etrack = ET1079721
Titan cases: 290-652-172

Description:
A change was made to fix an nbpem crash dump under ReadHostConfigExA.
--------------------------------------------------------------------------------
Etrack Incident = ET1149042
Associated Primary Etrack = ET1102562
Titan cases: 220-102-040

Description:
NOM would not show accurate job data for inline tape copy jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1163510
Titan cases: 281-245-969

Description:
If a user "lost" a drive path (that is to say, the operating system
deleted it for some reason) and the user tried to start ltid, ltid
would fail to initiate because the drive path was invalid. This has been
changed to DOWN the drive and to allow ltid to continue initializing.
--------------------------------------------------------------------------------
Etrack Incident = ET1161887
Titan cases: 240-647-369 281-178-937

Description:
Unable to restore the BackupExec Exchange 2003 images from NetBackup.
The following error was received.

Error: unable to create object for restore: Microsoft Information
Store:\First Storage Group\Mailbox Store (BEDS 0xE000FEA9: The Backup Exec
data store encountered a problem during the operation.
--------------------------------------------------------------------------------
Etrack Incident = ET1107481

Description:
A VSS transportable backup would fail because the
Libfi_VSS_Transportable.dll would not build properly.
--------------------------------------------------------------------------------
Etrack Incident = ET1144105
Associated Primary Etrack = ET1165695
Titan cases: 240-623-383

Description:
SQL backups would fail when the batch file contained more than 255 backup
operations. This occurred under the following conditions:
1. A batch file was used with at least 255 backups.
2. It was launched as a scheduled backup.
3. The client's server list had at least two servers and the default
(the server listed first in the registry) is NOT the same as the one
specified in the batch file.)
--------------------------------------------------------------------------------
Etrack Incident = ET1145054

Description:
NetBackup MSSQL would fail with a program exception while browsing for
images under an IA64 processor type.
--------------------------------------------------------------------------------
Etrack Incident = ET1162159
Associated Primary Etrack = ET1129884
Titan cases: 281-199-021 281-218-316

Description:
Remote NDMP backups fail with the following error:

"Error ndmpagent(pid=4100) Received continue when not PAUSED, state =
ACTIVE"


Workaround:
To resolve this issue, lower logging levels and make sure the fragment
size is not too small.
--------------------------------------------------------------------------------
Etrack Incident = ET1163683
Associated Primary Etrack = ET1157412
Titan cases: 230-445-620

Description:
An SQL password would become inaccessible if the end user's Windows
user ID was changed by the Windows administrator. This issue caused
backups to fail. In addition, the user would have to re-enter the
password in the SQL user interface.

The change that was added provides an informative message that tells
the user to re-enter the SQL password. However, it is still necessary for
the user to re-enter the SQL password as this cannot be retrieved if a
Windows administrator changes the end-user's Windows password.

Additional Notes:
This change fixes the problem addressed in the following TechNote,
http://eng.support.veritas.com/docs/258735 .
--------------------------------------------------------------------------------
Etrack Incident = ET1127680

Description:
Added support with FlashBackup-Windows Instant Recovery file restores
making it possible to backup file lists that contain mount points.
Also fixed a 6.0MP5 max_snapshots>1 FlashSnap snapshot IR rotation
regression.
--------------------------------------------------------------------------------
Etrack Incident = ET1160469
Associated Primary Etrack = ET1159867
Titan cases: 320-069-438

Description:
After attempting to do an SQL cloaked backup by adding CLOAKEDBACKUP TRUE
to the batch file, the backup progress viewer reported the following:

WARN - COPYONLY and CLOAKEDBACKUP were both specified in the batch file.
--------------------------------------------------------------------------------
Etrack Incident = ET1166456
Associated Primary Etrack = ET1164146
Titan cases: 281-212-676

Description:
A Redirected Exchange VSS backup to an alternate server may fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1167648

Description:
After restoring the lotus database link, the database would be
deleted.
--------------------------------------------------------------------------------
Etrack Incident = ET584649
Titan cases: 280-093-438

Description:
A change was added to change the Exchange directive to MS_EXCHANGE_200x
instead of MS_EXCHANGE_2000.
--------------------------------------------------------------------------------
Etrack Incident = ET1083195

Description:
An Exchange VSS Transportable backup would fail if the Exchange writer was
in a Retryable state.
--------------------------------------------------------------------------------
Etrack Incident = ET1167061

Description:
A change was made to address an nbsl core dump issue on HP-UX 11.11.
--------------------------------------------------------------------------------
Etrack Incident = ET1090978

Description:
SQL VCS cluster backups fail. This occurs because the virtual instance
is not recognized as being virtual when the SQL user interface is
browsing for databases. Since the instance is not recognized as virtual,
the SQL script generator does not add the 'BROWSECLIENT <virtual-server>'
tuple to the batch file. This results in the SQL backup agent not
identifying the SQL instance as virtual when the backup operation is
performed and causes the backup to fail.

Workaround:
To resolve this issue, add the following tuple to the batch file.

BROWSECLIENT <virtual-server>
--------------------------------------------------------------------------------
Etrack Incident = ET1148909

Description:
The restoration of an AIX client that originally utilized JFS2 file
systems with inline logging would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1172182

Description:
HP-UX clients that utilize a VxVM boot disk may not boot after a
dissimilar disk restoration to an alternate disk because the primary
boot disk path is not set.

Workaround:
To avoid this issue, run "setboot -p <boot disk path>" in a maintenance
shell.
--------------------------------------------------------------------------------
Etrack Incident = ET1171778

Description:
An HP-UX client utilizing a VxVM boot disk will fail to boot after
restoration if a dissimilar disk mapping has been performed on the boot
disk group and the "standvol" volume has not been mapped first.

Workaround:
To resolve this issue, map configuration again and choose to map
"Disk Group Only" and then map the volumes within the disk group one at
a time making sure to map "standvol" first, then rootvol, and swapvol
onto the same disk.
--------------------------------------------------------------------------------
Etrack Incident = ET1166792
Associated Primary Etrack = ET1164173
Titan cases: 220-135-395

Description:
Drives could not be deleted from a media server due to
case-sensitive server name matching in the EMM stored procedures.
--------------------------------------------------------------------------------
Etrack Incident = ET1171236

Description:
A change was made to address Shadow copy restores that would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1152595
Associated Primary Etrack = ET1079261
Titan cases: 290-814-962

Description:
When using scripts with DB_BEGIN_BACKUP_CMD and the SnapVault option,
the scripts would not run prior to the snapshot on the SnapVault Primary
being taken.


--------------------------------------------------------------------------------
Etrack Incident = ET1150787

Description:
An issue exists in NBRB that causes a core file to be generated.

Workaround:
To avoid this issue, make sure nbemm is running and then restart nbrb.
--------------------------------------------------------------------------------
Etrack Incident = ET1166347

Description:
HP-UX volume groups had invalid size values after performing DDR
mapping operations.
--------------------------------------------------------------------------------
Etrack Incident = ET1159518

Description:
VxVM disk enclosure-based names can be incorrectly numbered in the
"vxdisk list" output after a BMR restoration.

Workaround:
To avoid this issue, remove the file, /etc/vx/disk.info, and then
reboot the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1151846
Associated Primary Etrack = ET1170498
Titan cases: 220-105-273

Description:
Performance improvements for nbrb resource evaluation were added to
this pack.
--------------------------------------------------------------------------------
Etrack Incident = ET1168017
Associated Primary Etrack = ET1160557
Titan cases: 220-126-112

Description:
A change was made to address an issue in the NetBackup Job Manager (nbjm)
that caused bpjobd to deadlock.
--------------------------------------------------------------------------------
Etrack Incident = ET1170911
Associated Primary Etrack = ET1156903
Titan cases: 290-837-137 290-957-709

Description:
SAP data backups threads were failing with socket read failed error
messages that were reported in backint. When bpbrm exited, the SAP client
would immediately fail with a "socket read failed" error message.
--------------------------------------------------------------------------------
Etrack Incident = ET1172646

Description:
A Windows Oracle stream-based backup would fail after the Storage
Foundation 5.0 was installed.
--------------------------------------------------------------------------------
Etrack Incident = ET1169688

Description:
A change has been added that prevents a potential segmentation violation
that could occur during encrypted DataStore backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1175399

Description:
This pack is part of the Microsoft Exchange 2007 mailbox support for
NetBackup 6.0 MP6.
--------------------------------------------------------------------------------
Etrack Incident = ET1170164

Description:
Oracle restore would fail with a table space larger than 2G from a
Flashsnap snap-only backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1174720
Associated Primary Etrack = ET1163418
Titan cases: 240-659-059

Description:
With checkpoints and BMR enabled, "bad image header" error appears
because of a "no entity was found (227)" error in bpdbm after the
"move backup job from incomplete state to done state" time has expired.

Workaround:
The workaround for this scenario is to ignore the error message because
it is benign.
--------------------------------------------------------------------------------
Etrack Incident = ET1176222
Associated Primary Etrack = ET1157114
Titan cases: 290-652-172

Description:
A change was made to address an issue in the NetBackup Job Manager (nbjm)
that would potentially cause a core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET1162317
Associated Primary Etrack = ET1153592
Titan cases: 220-097-876 281-213-614

Description:
The bpbrm parent for a multiplexed group worked correctly until
123 encrypted backup jobs were processed. At that point, all new
bpbrm.child processes failed with a status 159 before contacting the
client.
--------------------------------------------------------------------------------
Etrack Incident = ET1168696
Associated Primary Etrack = ET1148310
Titan cases: 220-118-788

Description:
The Vault eject operation showed an incorrect count for TLH media
(always zero). A fix was added to ensure that the correct ejected count
is reported for TLH media.

Additional Notes:
This issue was observed only with the TLH media.
--------------------------------------------------------------------------------
Etrack Incident = ET1159724
Associated Primary Etrack = ET1086130
Titan cases: 290-821-682

Description:
Bpdbjobs would produce an incorrect output if the job-database messages
included carriage returns.
--------------------------------------------------------------------------------
Etrack Incident = ET1177687

Description:
Added ACS support for Sun/STK SL3000 robot.
--------------------------------------------------------------------------------
Etrack Incident = ET1173328

Description:
If the nbpem process was started or stopped from the NetBackup-Java
Administration Console, the process state should have been reflected
in NOM. NOM did not show this state change.
--------------------------------------------------------------------------------
Etrack Incident = ET791283

Description:
SAP raw partition restores using the ROLLBACK method were failing
with a STATUS = 249.
--------------------------------------------------------------------------------
Etrack Incident = ET1176655

Description:
A change was made to fix a condition that caused the connectToObject()
function to fail. The above function now correctly returns an exception.
--------------------------------------------------------------------------------
Etrack Incident = ET1169329
Associated Primary Etrack = ET1149036
Titan cases: 290-854-384

Description:
The media going offsite (MGO) reports (Pick list and Detailed
distribution) showed incorrect total kbytes for images on all media, and
for the current vault session.

A fix was added to ensure all kbytes numbers are reported correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET1176304

Description:
ACS now supports a change in responses from the ACSLS version 7.2 and
higher.
--------------------------------------------------------------------------------
Etrack Incident = ET1177982

Description:
A change has been made so that fetching device information is done in
one call to avoid communication overhead.
--------------------------------------------------------------------------------
Etrack Incident = ET1178736

Description:
Max_snapshot in a NAS_snapshot backup was not deleting the image or the
snapshot when it was hit.

--------------------------------------------------------------------------------
Etrack Incident = ET1177072

Description:
The Q_IMAGE_READ_FILES_FILE query would retries after a failed
flist_complete (Q_IMAGE_FLIST_COMPLETE) query.
--------------------------------------------------------------------------------
Etrack Incident = ET1178397

Description:
Junk values for job type, job status, and Undefined jobid 0 were seen
in NOM for an HP-UX IA64 managed server.
--------------------------------------------------------------------------------
Etrack Incident = ET1160350
Associated Primary Etrack = ET1155014
Titan cases: 281-224-323

Description:
Vault would fail to consider valid images for duplication because of a
case change in host names. A change was made to treat all host names
with varying cases alike.

Workaround:
Aliases can be added to the "Alternative media server names" tab of the
Vault Management Global Properties.
--------------------------------------------------------------------------------
Etrack Incident = ET1177593

Description:
Mapping a VxVM volume and choosing to not restore the file system does
not allow for a reduction in volume size that is smaller than the
original used space of the volume.
--------------------------------------------------------------------------------
Etrack Incident = ET1179931
Associated Primary Etrack = ET1131280
Titan cases: 220-107-289

Description:
When the user selects the Activity Monitor node, the CPU usage goes up to
more than 90%. Processes such as nbemm, dbsrv, etc. display high CPU usage.

Workaround:
The work around is to increase the refresh interval for the Activity
Monitor. Increase the value of the RefreshSeconds key under
HKEY_CURRENT_USER\Software\VERITAS\NetBackup\NBPMon\General in the registry.
--------------------------------------------------------------------------------
Etrack Incident = ET1140137
Titan cases: 280-882-431

Description:
During a Nearstore FSE backup, a query was made to the catalog that
could consume 100% of the master server CPU resource. This fix
optimizes the catalog query. The catalog query was not locking catalog
images for read, so if the previous backup was expired while the backup
was in process the backup could fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1175452

Description:
Adding an Exchange mailbox to a new exclude list would cause NBWin.exe to
close.
--------------------------------------------------------------------------------
Etrack Incident = ET1176372

Description:
The Exchange public folder restore view was not consistent with the mailbox
view.
--------------------------------------------------------------------------------
Etrack Incident = ET1146967

Description:
A BMR restore of Windows clients that have BroadCom NetXtreme-II NIC(s)
fail because of missing drivers in the FastBoot ISO that was shipped with
the NetBackup 6.0 MPs.
--------------------------------------------------------------------------------
Etrack Incident = ET1183648
Associated Primary Etrack = ET1037368
Titan cases: 220-096-910 220-123-945 220-124-001 220-135-401 220-141-599
281-218-316 290-883-680

Description:
NOM provides a report for to show the jobs that did not run, but were
scheduled and due to run. NBSL provides the required job data to NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET1182143

Description:
Mapping Solaris Volume Manager (SVM) disk sets would fail, stating that
the number of disks did not match the original number of disks in the
disk set.
--------------------------------------------------------------------------------
Etrack Incident = ET1181897

Description:
Unmapping Solaris Volume Manager (SVM) disk sets would fail with a
status code 252.
--------------------------------------------------------------------------------
Etrack Incident = ET1176200
Associated Primary Etrack = ET1117350
Titan cases: 220-099-084 281-168-660

Description:
A correction was made to address a problem with ACS libraries and LTO
drives having mount times that were too long.
--------------------------------------------------------------------------------
Etrack Incident = ET1182020

Description:
A Checkpoint backup job that was targeted to a storage unit group
(or ANY) could go to a different media server after start up. This would
make the image non-restorable.
--------------------------------------------------------------------------------
Etrack Incident = ET1177985

Description:
Changes were added to enhance performance in a large environment during
DNS lookup.
--------------------------------------------------------------------------------
Etrack Incident = ET1182062

Description:
NBJM hung during a test that canceled a large number of jobs and also
killed the BPBRM processes manually.
--------------------------------------------------------------------------------
Etrack Incident = ET1173920

Description:
The file count was not getting updated during a backup job. The "Files
written" value was always 0.
--------------------------------------------------------------------------------
Etrack Incident = ET1186192
Associated Primary Etrack = ET1144200
Titan cases: 290-859-975 220-146-936

Description:
nbpem terminates after failing five times to get policy information.

Additional Notes:
If the policy list gets too large that it takes more than 10 minutes to
read it, nbpem would timeout while trying to get the list.
--------------------------------------------------------------------------------
Etrack Incident = ET1187051

Description:
An NBSL core dump on Solaris would occur when the creation of proxy
failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1165566

Description:
Running a media list report failed to fetch media for clusters. All media
servers that were queried after a cluster or a back-level media server were
treated as a back-level media server and could cause a degradation in
performance.
--------------------------------------------------------------------------------
Etrack Incident = ET1190469

Description:
A change was made to ensure database statements are freed during a machine
configuration fetch operation.
--------------------------------------------------------------------------------
Etrack Incident = ET1188846

Description:
A change was made to address a user interface crash that would occur while
performing a refresh on the Policy node > Summary of all policies node.
--------------------------------------------------------------------------------
Etrack Incident = ET1143454
Associated Primary Etrack = ET1136246
Titan cases: 240-637-777

Description:
The Policy Execution Manager may fail with a status 200 if the file list
starts with two or more consecutive NEW_STREAM directives or may run the
job without starting all the streams because of gaps in the STREAMS file
from having two or more consecutive NEW_STREAM directives in the file
list. The Policy Execution Manager was changed to filter consecutive
NEW_STREAM directives in the file list to prevent gaps in the STREAMS file
which caused only some of the streams to be started.

Workaround:
To resolve this issue, remove two or more consecutive NEW_STREAM directives
from the file list. Also remove the NEW_STREAM directive if no entries
follow it in the file list.
--------------------------------------------------------------------------------
Etrack Incident = ET1055679
Associated Primary Etrack = ET1052792
Titan cases: 240-470-646

Description:
The Policy Execution Manager exits because it times out while jobs are
waiting for a query to nbproxy to get the last backup time. (The default
is 10 minutes.) The timeout is due to jobs being queued behind a hot
catalog backup job which is query to nbproxy that may exceed the timeout
period. The Policy Execution Manager was changed to start another nbproxy
to run hot catalog backup jobs to avoid this the timeout problem.
--------------------------------------------------------------------------------
Etrack Incident = ET1186480

Description:
A Snapshot backup on Windows bpbrm would fail with the snapshot error:
FTL - process_fs_list() failed, status 20.
--------------------------------------------------------------------------------
Etrack Incident = ET1188445

Description:
nbrb would sometimes crash while connecting to nbemm. A change was made
to address the CORBA exception.
--------------------------------------------------------------------------------
Etrack Incident = ET1181925

Description:
The VSS_Transportable FIM would back up the wrong device when the policy
filelist item was longer than three characters in length (for example, when
the doing a raw backup).
--------------------------------------------------------------------------------
Etrack Incident = ET1190635

Description:
Error conditions that occurred during a device monitor query could have
caused nbemm to crash while shutting down.
--------------------------------------------------------------------------------
Etrack Incident = ET1188189
Associated Primary Etrack = ET1166801
Titan cases: 311701404

Description:
If the active directory (NTDS/SYSVOL) database files were on another disk,
then that disk would not be restored during a "System-only" Restore.

Workaround:
The problem occurs only in case of System-only Restore. So if it is
possible, attempt a Full System Restore instead of a System-only Restore.
A Full Restore will correctly restore all data.
--------------------------------------------------------------------------------
Etrack Incident = ET1187805

Description:
Truncated messages without a trailing new-line character were being
emitted by bpfis.
--------------------------------------------------------------------------------
Etrack Incident = ET1186137
Titan cases: 220-117-958

Description:
Changes of Host Name, IP, and Gateway were not committed in "Hosts" page.
--------------------------------------------------------------------------------
Etrack Incident = ET1194223
Associated Primary Etrack = ET1192681
Titan cases: 311-793-147

Description:
SAP backups would fail because of a truncation issue with client names of
31 characters.

Workaround:
To resolve this issue, increase the size of the buffer so it can
accommodate the entire client name.
--------------------------------------------------------------------------------
Etrack Incident = ET1190602

Description:
NBRB would hang or crash when shutting down during a failover in a
clustered environment.
--------------------------------------------------------------------------------
Etrack Incident = ET1188080 ET1211841 ET1214400

Description:
Caching DeviceConfig information would create issues with the ltid
start up and proper displaying after the configuration changes
(tpautoconf -a).
--------------------------------------------------------------------------------
Etrack Incident = ET1198270

**Description:
The Policy Execution Manager was not honoring a pre-process interval. A
change was made that ensures the stream discovery honors the pre-process
interval on a per policy basis by creating a STREAMS file for each policy
instead of having one file for all of the policies.

Additional Notes:
NOTE: Creating a new STREAMS file will cause incremental (INCR) backups
to run as FULL backups; thus, the previous STREAMS data will not be
contained or copied. Users who do not have enough disk space to hold a
second full backup should consider implementing a workaround. For more
information about this issue as well as a possible work-around, refer to
the following TechNote on the Support Web site.

http://entsupport.symantec.com/docs/301465
--------------------------------------------------------------------------------
Etrack Incident = ET1112364

Description:
A change has been made that prevents a segmentation fault from occurring
during Sybase Catalog backups.
--------------------------------------------------------------------------------





=========
NB_60_5_M
=========
Etrack Incident = ET644656

Description:
Backups to FSE-enabled Nearstore storage units require TIR to be enabled on
the policy. A change was made to enforce this requirement at run time.
--------------------------------------------------------------------------------
Etrack Incident = ET570561
Associated Primary Etrack = ET808113

Description:
This fix improves the performance of advanced method Oracle database
backups.
--------------------------------------------------------------------------------
Etrack Incident = ET809090

Description:
If you were using vxlogview along with options �d and �t, vxlogview should
have accepted these options in any order, but it did not. The �d option
displays debug messages, and the �t option displays the most recent
messages. These are not related options, however, vxlogview did not honor
the �t option if it was listed after the �d option. A change was made to
correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET828552

Description:
Changes were made to this maintenance pack to update the PBX and ICSCO pbx
merge modules.
--------------------------------------------------------------------------------
Etrack Incident = ET861550

Description:
If the NBDB database is not created properly during installation, the
install continues, however the user may not understand that there was
an issue creating the database. As a result, the user may encounter
errors in the command line and the user interfaces.

In addition, if during a patch installation that nbnd_upgrade fails,
the database winds up with the incorrect version. Again, nbemm will
not start because of the version mismatch.

Changes have been made so that the install will fail if the database
cannot be created or upgraded and installation warnings will be logged
in a new logging directory for nbnd commands. The new directories are:

UNIX: /usr/openv/netbackup/logs/nbdb
Windows: InstallPath\NetBackup\logs\nbdb
--------------------------------------------------------------------------------
Etrack Incident = ET861567

Description:
Corrected the Vault version files for the HP-UX IA-64 and Linux IA-64
platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET862411

Description:
Made a change to unload tapes in a more timely manner on back-level media
Servers (for example, NetBackup 5.x).
--------------------------------------------------------------------------------
Etrack Incident = ET862518

Description:
Changes were made to fix potential memory leaks, while fetching pending
requests from the NetBackup Resource Broker.
--------------------------------------------------------------------------------
Etrack Incident = ET862534

Description:
Calls to emmlib_GetStorageUnitHosts no longer result in segmentation
violations.
--------------------------------------------------------------------------------
Etrack Incident = ET862464
Associated Primary Etrack = ET791864

Description:
Changes were added that prevent bpsynth from hanging on patched, Solaris 10
systems.
--------------------------------------------------------------------------------
Etrack Incident = ET862606

Description:
Changes have been made to ensure that all Chinese messages that are suppose
to appear in the Bare Metal Restore (BMR) command line interface (CLI)
output appear, no matter what locale is used.
--------------------------------------------------------------------------------
Etrack Incident = ET863123
Associated Primary Etrack = ET863120

Description:
A condition existed when the bprd service on the master server connected to
the hosts in its SERVER list and started a process on those servers to
remove old debug log files. If a host was in the MEDIA_SERVER list but not
in the SERVER list on the master server, bprd would not contact that host.
A change was made to ensure that bprd connects to hosts in both the SERVER
list and the MEDIA_SERVER list on the master server to remove old debug
log files.
--------------------------------------------------------------------------------
Etrack Incident = ET863150

Description:
NetBackup�s Release Broker's logging has been improved in the following
manner:

- The total amount of logging content has been reduced.
- The messages that are displayed have been enhanced to be more meaningful.
- Different debug levels are used for different purposes.
--------------------------------------------------------------------------------
Etrack Incident = ET863199

Description:
The SRCMEDIAID & DSTMEDIAID fields of the jobs database were not being
written to.
--------------------------------------------------------------------------------
Etrack Incident = ET861965

Description:
In some cases, when a request for a volume pended, the NetBackup-Java user
interface and vmoprcmd -xdpa would display an error when asked to show the
pending action.
--------------------------------------------------------------------------------
Etrack Incident = ET863314

Description:
The patch level of the (remote) client was wrong when Windows was configured
in the environment.
--------------------------------------------------------------------------------
Etrack Incident = ET861709
Associated Primary Etrack = ET701050

Description:
Network issues would cause tldd connect timeout issues that would result in
downed drives.
--------------------------------------------------------------------------------
Etrack Incident = ET861712 ET861714

Description:
Changes were made to ltid that corrected the following issues:
- ltid would stop and report the following message if it received a message
that were larger than 208 bytes.
Arg list too long
- Occasionally, ltid would not continue to run at startup.
--------------------------------------------------------------------------------
Etrack Incident = ET803746

Description:
Using the -i option for vmchange command resulted in an incorrect error
message that would indicate to users that this function is not implemented
in NetBackup Enterprise Media Manager (EMM).
--------------------------------------------------------------------------------
Etrack Incident = ET862501

Description:
If the registry hive needs to be replaced after a restore operation, the
registry may not get fully replaced.

Workaround:
To avoid this issue, manually shutdown NetBackup, using the bpdown command,
before you reboot the system.
--------------------------------------------------------------------------------
Etrack Incident = ET863393
Associated Primary Etrack = ET863378

Description:
Backup duplication errors would occur because of a timeout issue that caused
bptm to exit with 54 and 25 errors.
--------------------------------------------------------------------------------
Etrack Incident = ET862641
Associated Primary Etrack = ET702146

Description:
DSSU relocation (duplication) jobs no longer leave a bid_file_* on master
server.
--------------------------------------------------------------------------------
Etrack Incident = ET862648

Description:
Changes were added to correct a DSSU staging process issue that caused the
parent job to hang.
--------------------------------------------------------------------------------
Etrack Incident = ET862609

Description:
The fragment size set for a disk storage unit (DSU) was ignored when doing a
Synthetic backup.
--------------------------------------------------------------------------------
Etrack Incident = ET861978

Description:
Changes were made to eliminate potential race conditions between ltid and
vmd when adding a host entry to EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET863428
Associated Primary Etrack = ET806075

Description:
The Oracle agent no longer ignores BPBACKUP_SCHED in the bp.conf file on
the client system.
--------------------------------------------------------------------------------
Etrack Incident = ET862543

Description:
The bpplinclude command could not handle file paths that contain the %
character.
--------------------------------------------------------------------------------
Etrack Incident = ET574945

Description:
Snapshot client SAP backups would fail because no valid license key be
found on the server.
--------------------------------------------------------------------------------
Etrack Incident = ET862603

Description:
A change was made to ensure that bpbrmds no longer exits prior to
bpduplicate finishing (on Tru64 systems only).
--------------------------------------------------------------------------------
Etrack Incident = ET862491

Description:
The nbpushdata log files are now written to the following locations:

/usr/openv/var/nbpushdata (UNIX)
VERITAS\NetBackup\var\nbpushdata (Windows)

Log files are not pruned from these directories, so the files are available
for later review.
--------------------------------------------------------------------------------
Etrack Incident = ET596559

Description:
If an SAP backup is initiated without a definition for "policy" in the
init<SID>.utl file, then the backup fails with the following error messages
in the backint log:

9:52:22.021 [3632.3884] <4> do_file_backup: VxBSACreateObject - SUCCESS
09:52:22.021 [3632.3884] <16> VxBSAGetPolicyInfo: ERR - policy_name is null
09:52:22.021 [3632.3884] <4> do_file_backup: A NULL pointer was encountered
in a required argument.
09:52:22.021 [3632.3884] <4> do_backup: Exit with status: <2>.

Workaround:
To resolve this issue, add a definition for Policy in the parameters
file(init<SID>.utl).
--------------------------------------------------------------------------------
Etrack Incident = ET863106

Description:
The MEDIA_UNMOUNT_DELAY is not honored consistently for standalone drives.

Workaround:
To avoid this issue, ensure an eligible tape is loaded in the drive before
You start a job.
--------------------------------------------------------------------------------
Etrack Incident = ET864928

Description:
A backup job would hang in the bpbrm process after the client read timeout
expired. The job would not finish and a 41 status (network connection
timed out) error would occur.
--------------------------------------------------------------------------------
Etrack Incident = ET862498

Description:
It was possible for a restore to fail when using Windows Active Directory
on a Windows 2003 system and setting the restore mode to Windows 2000 with
the following command:
w2koption -restore -system_state 1 -sysvol 2

Then restore using a listfile with bprestore such as:
bprestore -w -T -f "Z:\listfile.txt" -L "Z:\adr.log"
Where listfile is:
31 System_State:\Active_Directory\ xxx xxx

The failure was caused by the double back slashes "\\" in the name. A
change was made to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET862496

Description:
Errors no longer exist in the protocol between bpbkar32.exe (client)
and bpbrm (media server) because of embedded carriage returns and line
feeds in the error message text. This problem was recognizable by a
pattern found in the job try files, similar to the following example:

KBW 1154008933 40192 2551.240
KBW 1154008950 40192 2550.072
LOG 1154008966 8 bpbrm 2276 from client h-crowvalley: WRN - can't open
object: Shadow Copy Components:\System Service\Removable Storage
Manager\Removable
Storage Manager (BEDS 0xE000FED1: A failure occurred querying
the Writer status.
LOG 1154008966 16 bpbrm 2276 from client h-crowvalley: )
KBW 1154008960 40192 2555.205
KBW 1154008966 40192 2563.794

Refer to the second LOG message of status. It should have been part of
the first log message.
--------------------------------------------------------------------------------
Etrack Incident = ET865189 ET842864
Associated Primary Etrack = ET833467

Description:
Changes were made to enhance the performance and speed in which the list of
media servers would appear after a user selects Host Properties > Media
Servers from the NetBackup-Java Administration Console. The slow response
was caused by the following command, which would return the external
attribute settings for each media server.

vmoprcmd -h <server_name> -extall
--------------------------------------------------------------------------------
Etrack Incident = ET852905 ET850830
Associated Primary Etrack = ET832181

Description:
Changes were added to solve various issues in the Device Configuration
Wizard with respect to back-level media servers. In addition, a change
was made that solves a device configuration wizard defect that prevented
users from reconfiguring standalone drives as robotic.
--------------------------------------------------------------------------------
Etrack Incident = ET861980

Description:
Corrected a tape drive cleaning issue where the end user running the
NetBackup Administration Console on a UNIX server could not successfully
clean a tape drive using a path on a Windows server.
--------------------------------------------------------------------------------
Etrack Incident = ET865211 ET645838
Associated Primary Etrack = ET645838

Description:
A status 50 error would be shown in the Activity Monitor if a user tried to
perform a large duplication that was greater than 20 minutes. Similar
issues were reported in earlier versions of NetBackup. Smaller duplications
were not a problem.
--------------------------------------------------------------------------------
Etrack Incident = ET865184

Description:
Some languages use a comma, instead of a period, to delimit the fractional
portion of a floating point number. If the default language is set to one
of these language, some operations might fail. Specifically, any time a
floating point parameter is passed to the EMM server database it will
reject a floating point number delimited by a comma, instead of a period.

One example of this is attempting to change or set the cleaning frequency
of a drive.

Workaround:
To resolve this issue, change the decimal point character from a comma
to a period ('.'). This can be done by modifying the locale or switching
to a different locale, such as US English.
--------------------------------------------------------------------------------
Etrack Incident = ET865706

Description:
This maintenance pack contains multiple NB_SECURITY infrastructure changes.
--------------------------------------------------------------------------------
Etrack Incident = ET862283

Description:
Changes were made to correct the following issues with the nbemmcmd command.
- The nbemmcmd -getemmserver command would not always get the NetBackup
version.
- The nbemmcmd -setemmserver command would try to set the EMM server on
machines that were not in its domain.
- The nbemmcmd -setemmserver command would not set the EMM server of a master
server.
--------------------------------------------------------------------------------
Etrack Incident = ET865792

Description:
nbVersionNumber() would not return a zero (0) when there was an error
attempting to get the version number from the client. However, in certain
cases this does not happen.
--------------------------------------------------------------------------------
Etrack Incident = ET783403

Description:
The status collector daemon that NetBackup uses to monitor device and host
status for back-level media servers has been logging /vm/debug/reqlib.
This has made debugging for traditional media manager command lines
difficult. This change introduces a new media manager debug directory
/vm/debug/vmscd. This makes it much easier to obtain debugging information
for both vmscd and the media manager command lines.
--------------------------------------------------------------------------------
Etrack Incident = ET863402

Description:
A change was made to ensure the nbemmcmd -listmedia command prints out the
number of mounts, as well as the maximum mounts.
--------------------------------------------------------------------------------
Etrack Incident = ET863433

Description:
The message a user would receive when adding a host that already existed in
database was invalid hostname. A change has been made to correct this
message.
--------------------------------------------------------------------------------
Etrack Incident = ET847915
Associated Primary Etrack = ET820303

Description:
A change was made so that a READY standalone drive was not marked as
NOT-READY during a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET865996

Description:
Restoration of a Linux LVM-based root file system client could fail to boot
in dissimilar disk restore situations where the Linux LVM partition had been
remapped to another disk, and another partition resided in the same location
as the original Linux LVM partition. This was caused by the vgscan command
running and discovering the original LVM volume group descriptor area.
--------------------------------------------------------------------------------
Etrack Incident = ET863427

Description:
bpmedialist now uses EMM to build the host list instead of using the storage
unit list.
--------------------------------------------------------------------------------
Etrack Incident = ET866829

Description:
Queuing jobs could not be canceled from bpdbjobs command.

--------------------------------------------------------------------------------
Etrack Incident = ET863413

Description:
A change was made to the nbemmcmd -help command. It now
returns an exit status of 0 instead of an error status.
--------------------------------------------------------------------------------
Etrack Incident = ET866997

Description:
If the NetBackup Request Daemon (bprd) terminated a backup before the
NetBackup Policy Execution Manager (nbpem) was invoked, the terminated
backup job may be reported with a "queued" status forever. This could
occur if a backup was initiated by the bpbackup command line and it
referenced an unwritable progress log file.
--------------------------------------------------------------------------------
Etrack Incident = ET569130

Description:
If the NetBackup Request Daemon (bprd) terminates a backup before the
NetBackup Policy Execution Manager (nbpem) is invoked, the terminated
backup job may be reported with a "queued" status forever. This can
occur if a backup is initiated by the bpbackup command line and it
references an unwritable progress log file.
--------------------------------------------------------------------------------
Etrack Incident = ET534732

Description:
A fix was added that resolves a UTF8 to GB18030 conversion problem in the
Oracle XML Archiver agent in which GB18030 strings were being truncated.
--------------------------------------------------------------------------------
Etrack Incident = ET865243

Description:
If the NBDB database is not created properly during installation, the
install continues, however the user may not understand that there was an
issue creating the database. As a result, the user may encounter errors
in the command line and the user interfaces.

In addition, if during a patch installation that nbnd_upgrade fails, the
database ends up with the incorrect version. Again, nbemm will not start
because of the version mismatch.

Changes have been made so that the install will fail if the database
cannot be created or upgraded and installation warnings will be logged in
a new logging directory for nbnd commands. The new directories are:

UNIX: /usr/openv/netbackup/logs/nbdb
Windows: InstallPath\NetBackup\logs\nbdb
--------------------------------------------------------------------------------
Etrack Incident = ET865850

Description:
Erase job failures would occur because NDMP drives were being selected for
erase jobs.

Workaround:
To resolve this issue, down NDMP drives to prevent NetBackup from selecting
them for erase jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET865186

Description:
If you use the "Configure Multiple Copies" option before any storage units
are defined the following error message appears.

"Not all storage units are on the same media server"

A change was made to the message to correctly indicate that no storage units
exist.
--------------------------------------------------------------------------------
Etrack Incident = ET894254

Description:
Each time a file access time was successfully changed the error, "Invalid
error severity <16>" would appear as shown in the following example.

Windows Client log entry: <16> file_system_access::V_Cleanup: TRV - set
times for file: C:\test
--------------------------------------------------------------------------------
Etrack Incident = ET863282
Associated Primary Etrack = ET837020

Description:
The Active Directory Server recovery, with the BMR process, would not
recover the SYSVOL contents.

The Recovery Active Directory Server, using FastBoot, ran the BMR process
with no errors. After a final reboot, the Active Directory contents under
SYSVOL was not present.

Additional Notes:
The tar debug log contained the following Warning messages:

15:49:49 (97.001) MNR - The object was re-directed to:
15:49:49 (97.001) UTF - C:\BMR\SCC\
15:49:50 (97.001) WRN - error writing object: Shadow Copy Components:\System
State\SYSVOL\SYSVOL\ceedd98b-aeb2-4f9d-9fefb6872c13446b
15:49:50 (97.001) WRN - error writing byte: 3763200
15:49:50 (97.001) WRN - desired byte count: 65536
15:49:50 (97.001) WRN - actual byte count: 65077
--------------------------------------------------------------------------------
Etrack Incident = ET865136

Description:
A change was made that removes the ability of bpdown to kill any nbproxy
processes that remain after the normal shutdown sequence.
--------------------------------------------------------------------------------
Etrack Incident = ET846230

Description:
A change was made to resolve an issue that caused NetBackup Release Broker
(NBRB) to crash randomly while performing a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET895177

Description:
A change was made to resolve an issue that caused NetBackup Policy
Execution Manager (NBPEM) to crash because of a shutdown during
clean_media_db operation.
--------------------------------------------------------------------------------
Etrack Incident = ET895170 ET895172

Description:
Changes were made to address scalability issues with NBPEM because
unnecessary computations were being performed of the "jobs due" time.
In addition, the internal queue management was a single thread to
handle multiple queues. This caused long waits to process requests on
some queues.
--------------------------------------------------------------------------------
Etrack Incident = ET834075

Description:
Improvements were added to the CPU utilization by bprd during restore
operations of a large numbers of files.
--------------------------------------------------------------------------------
Etrack Incident = ET862350

Description:
Jobs may queue instead of fail when all drives are down or not available
because of an onDemandOnly setting.

Workaround:
To avoid this issue, cancel the queued jobs if there is no possibility of
them getting drives.
--------------------------------------------------------------------------------
Etrack Incident = ET858772

Description:
Installer will verify that PBX service is running before attempting a server
patch install, and it will start the service if necessary.
--------------------------------------------------------------------------------
Etrack Incident = ET862424

Description:
Messages were added to the NetBackup log whenever media is
frozen/unfrozen/suspended/unsuspended.
--------------------------------------------------------------------------------
Etrack Incident = ET862425

Description:
A message has been added to the client log when the operator is about to
request a media that may be standalone. This message warns the operator
that they may need to manually load the requested media.
--------------------------------------------------------------------------------
Etrack Incident = ET862427

Description:
If a multiplexed job stopped during a tape span (on a standalone drive) the
Media Database for the next tape used would be incorrect, enabling this
tape to be used again and cause data to be overwritten.
--------------------------------------------------------------------------------
Etrack Incident = ET862428

Description:
Added a change to address the latest SCSI standard that changed a device
response to a Test Unit Ready command when the device is SCSI Reserved to
another initiator.
--------------------------------------------------------------------------------
Etrack Incident = ET862430

Description:
Added support for Quantum/Certance Ultrium 3 drive with WORM media.
--------------------------------------------------------------------------------
Etrack Incident = ET862441

Description:
Canceled jobs no longer cause a future job to hang during a media mount.
--------------------------------------------------------------------------------
Etrack Incident = ET841107

Description:
During a synthetic backup job, one of the source images for the synthetic
may expire. If this happens, when the bptm or bpdm reader attempts to
read the image, it will experience a "no entity found" error from the
catalog. The bptm reader fails. For this particular case, the reader will
enter a code that causes it to hang up indefinitely.
--------------------------------------------------------------------------------
Etrack Incident = ET847324

Description:
Duplicate forms of the .ds file may be created as part of the NetBackup 5.x
to NetBackup 6.x upgrade process that cause bptm or bpbrmds to crash.
For example,

beany_1162489194_C1_F1.ds.info
beany_1162489194_C1_F1.ds.1162489194.img
beany_1162489194_C1_F1.ds.1162489194.info
beany_1162489194_C1_F1.ds

Workaround:
Normally, NetBackup perceives a .img and .info file as one "file" to its
I/O layer. There is a special compatibility mode that enables it to see
the extra .ds and its .info file as the same file in the previous pair.

To avoid this issue, remove one of the pairs, preferably the .img file and
its .info file.
--------------------------------------------------------------------------------
Etrack Incident = ET896802
Associated Primary Etrack = ET798913

Description:
An issue would occur when children jobs were retired due to exceeding the
time allowed in an incomplete state. The parent job, being resumed either
manually or automatically, resulted in an Frequent status code 805 error
because the invalid jobid was -1.

A change was added that prevents the child from starting since it is not
resumable. The new result will correctly be a 200 error if no children
can be started. An indication of this will be written to the policy
execution manager (pem) log.
--------------------------------------------------------------------------------
Etrack Incident = ET864394
Associated Primary Etrack = ET789899

Description:
If bpcd.exe faulted on Windows, a backup completion message would still be
recorded in the log.
--------------------------------------------------------------------------------
Etrack Incident = ET862590
Associated Primary Etrack = ET862589

Description:
Added the capability to open UNIX progress logs that are non-blocking.
--------------------------------------------------------------------------------
Etrack Incident = ET860837
Associated Primary Etrack = ET834130

Description:
Jobs would not be retried until all jobs associated with the parent job were
complete.
--------------------------------------------------------------------------------
Etrack Incident = ET860882
Associated Primary Etrack = ET845081

Description:
Restarting a job that was originally an immediate backup, may cause streams
of a different schedule type to be run.
--------------------------------------------------------------------------------
Etrack Incident = ET575030

Description:
A change was made so that a restore of a multi-striped snapshot is no longer
inhibited.
--------------------------------------------------------------------------------
Etrack Incident = ET894249

Description:
NBJM was not forwarding the connect options to bpbrm. On a NetBackup 6.0
media server, bpbrm is able to obtain the connect options. Whereas on a
NetBackup 5.x media server, the connect options must be specified using the
command line.
--------------------------------------------------------------------------------
Etrack Incident = ET847976

Description:
If a synthetic backup job failed to get the requested resources, no
messages were displayed in the job details to explain the cause of a
job that appeared to be hung.
--------------------------------------------------------------------------------
Etrack Incident = ET850210

Description:
SQL server snapshot backups that use the GROUPSIZE parameter sometimes skip
one or more databases.

Workaround:
To avoid this issue, back up databases without using the GROUPSIZE
parameter.
--------------------------------------------------------------------------------
Etrack Incident = ET862277

Description:
A fix was added that resolves a load library failure that would occur with
DB2 advanced method backups on HP-UX platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET855555

Description:
A change was made that enables SQL 2005 mixed security to initialize the SQL
user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET860844
Associated Primary Etrack = ET860273

Description:
Changes were made to resolve status 200 errors that occurred when a parent
job started when children were left active because PEM terminated or a
crash of a generic job occurred.
--------------------------------------------------------------------------------
Etrack Incident = ET867730

Description:
An enhancement was included in this maintenance pack that implements an
automatic retry for SQL backups.

To carry out a retry, NetBackup MSSQL (NB-MSSQL) keeps track of the failed
operations in the batch. Failed operations are written to a newly
generated batch file with the number of retries, decremented by 1. For a
manual retry, the retry batch is placed in dbext\mssql\retry\. For an
automatic retry, the retry batch is placed in dbext\mssql\temp\ and is
initiated automatically by NB-MSSQL when the previous batch file completes.

Note: There are no NetBackup server changes in this feature for providing
advanced job grouping, server console retry, and-so-on.

Retry functionality is driven by new keyword-value pairs as follows:

RETRYTYPE MANUAL|AUTOMATIC
NUMRETRIES n --- n must be 1-9
RETRYWAITSECONDS n �--- number of seconds until next retry

Usage:
1. Keywords are available only if all of the operations in the batch
file are backups.
2. They are only allowed in the first operation of the batch file.
3. They are also compatible with GROUPSIZE, BATCHSIZE, as well as $ALL
options.
4. If NUMRETRIES is specified but not RETRYTYPE, then AUTOMATIC is assumed.
5. If RETRYTYPE is specified, but not NUMRETRIES, then 1 retry is assumed.

Note: Backup $ALL uses an expansion macro to generate a new batch file that
Specifies operations for each object. If retry is specified with $ALL,
then the retry logic is applied to the expanded batch file.

In addition to restart capability, new information is added to the
progress viewer to enumerate the objects on which failed to get
backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET860853
Associated Primary Etrack = ET858810

Description:
A change was made so that jobs no longer wait for resources after the window
is closed .
--------------------------------------------------------------------------------
Etrack Incident = ET860856
Associated Primary Etrack = ET860266

Description:
A change was made to address an issue that caused backups to fail with an
800 status.
--------------------------------------------------------------------------------
Etrack Incident = ET854621

Description:
Resolved an issue that caused scheduled, cold-catalog backups to not start.
--------------------------------------------------------------------------------
Etrack Incident = ET860879

Description:
Resolved an issue that caused PEM to run an incremental schedule instead of
a full schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET427447

Description:
In the NetBackup Oracle client restore user interface, an incorrect restore
may occur if you select the "Point In Time rollback" restore type, go
through the restore wizard and supply a tag to the "backup set identifier"
field, and then run the restore. The result is it restores from the latest
backup instead of restoring from the backup with the supplied backup set.

In addition, if you choose to save it as template, the key words
"from tag ..." are missing from RMAN RUN statement in the template. And
if you choose to run the restore from a normal backup, the tag field works
as expected.
--------------------------------------------------------------------------------
Etrack Incident = ET899176

Description:
Near the completion of a Synthetic backup, the following error message would
intermittently be issued to the Activity Monitor:

Error ACEMsgTran::handleOutput_u (pid=28968) write failed
from OUTPUT socket, errno=9(Bad file descriptor)

This error did not affect the successful completion of the backup, but it
did indicate a problem.
--------------------------------------------------------------------------------
Etrack Incident = ET855601

Description:
A change was added that resolves a segmentation fault that could occur while
performing a roll-forward recovery.
--------------------------------------------------------------------------------
Etrack Incident = ET592677
Associated Primary Etrack = ET808108

Description:
A change was added that resolves a segmentation fault that could occur while
performing Teradata backups on Linux platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET431952

Description:
This maintenance pack contains an enhancement that enables encryption for
Teradata backups.
--------------------------------------------------------------------------------
Etrack Incident = ET865054

Description:
If an Exchange Storage Group has a database with the same name as the
storage group (SG), the VSS backup ends with a status 1, and the data is
still backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET865059

Description:
An Exchange VSS backup that used a wildcard such as an asterisk (*) could
result in a status 0 when the database is not accessible.
--------------------------------------------------------------------------------
Etrack Incident = ET866750

Description:
The nbpushdata -modify_5x_hosts command now sets the standalone volume
database host to the EMM server on NetBackup 5.x hosts without standalone
drives.
--------------------------------------------------------------------------------
Etrack Incident = ET899837
Associated Primary Etrack = ET865853

Description:
There was a memory leak in the NetBackup Release Broker (nbrb) that caused
the memory utilization of nbrb to go very high after duplication/synthetic
jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET860860
Associated Primary Etrack = ET856242

Description:
The message queue between bprd and pem would fill up if the request to pem
was invalid.
--------------------------------------------------------------------------------
Etrack Incident = ET849248
Associated Primary Etrack = ET846190

Description:
Changes were made to resolve memory issues on immediate and user-backup
requests.
--------------------------------------------------------------------------------
Etrack Incident = ET832247

Description:
Deleting a cluster node no longer leaves invalid references.
--------------------------------------------------------------------------------
Etrack Incident = ET856478

Description:
The bptm -updatedb command would swap the number of images and the number of
valid images when inserting the data into the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET855644

Description:
A change was made to resolve a possible stack overflow issue that would
cause a system crash.
--------------------------------------------------------------------------------
Etrack Incident = ET850303

Description:
There is a timing issue with bringing the cluster online and running
runtpext. Bringing the cluster online (which can be slow), has an
adverse affect on the runtpext custom action that requests ltid.exe and
vmd.exe to be bounced. On some clustered NetBackup systems that have a
large number of devices (tape drives and robots) this can hang the
cluster install.

Workaround:
To resolve this issue, go into the Windows Task Manager and kill both the
"ltid.exe" and "vmd.exe" processes. The install will then continue and
complete successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET895259

Description:
Added support for PureDisk export to NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET850034

Description:
Changes were made to ensure that the device configuration analyzer utility,
mmcrawl, is working.
--------------------------------------------------------------------------------
Etrack Incident = ET863440

Description:
A change was made to ensure the nbemmcmd -errorsdb command no longer causes
a core dump on 64-bit machines.
--------------------------------------------------------------------------------
Etrack Incident = ET861373
Associated Primary Etrack = ET901494

Description:
Switches have been added to nbemmcmd to allow the use of a different
emmserver than those listed in the configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET860244

Description:
Initialization of a configuration for dissimilar disk restore (DDR) on a
Solaris 10 configuration that contains a Solaris Volume Manager database
replica and is using Solaris Zones fails with a return code 114.
--------------------------------------------------------------------------------
Etrack Incident = ET863437

Description:
Formatting is now correct for strings on Windows x64 systems.
--------------------------------------------------------------------------------
Etrack Incident = ET863277

Description:
Disk Access Record (DAR) information is not saved if type=TAR is set using
all capital letters.

Workaround:
To avoid this issue, use lower case letters when setting the type by using
the following command: set type=tar.
--------------------------------------------------------------------------------
Etrack Incident = ET863424

Description:
Because IBM markets NetApp filers, new checks have been added to search for
either "NetApp" or "IBM" as a filer vendor.
--------------------------------------------------------------------------------
Etrack Incident = ET863343

Description:
The restore would fail to recover the requested backed up files for Hitachi
filers.
--------------------------------------------------------------------------------
Etrack Incident = ET863306

Description:
Restoring a spanned backup would display the wrong number of restored KB's.
--------------------------------------------------------------------------------
Etrack Incident = ET894033

Description:
Unable to restore from images created with 5.x SAP Agent, after upgrading to
6.MP2 or later on Windows Platform. backint core dumps when the
restore/inquire is initiated.
--------------------------------------------------------------------------------
Etrack Incident = ET276146

Description:
Changes were made to enhance the performance of an NDMP DAR restore to
optimize catalog calls. These changes also improved performance on the
restore of a large number of files.
--------------------------------------------------------------------------------
Etrack Incident = ET794493
Associated Primary Etrack = ET777908

Description:
A restore would fail following a tape span due to attempting to position
to file number "0". The bptm logs show that a "STOP RESTORE" was received
for a restore that was already complete during the tape mount.
--------------------------------------------------------------------------------
Etrack Incident = ET863338

Description:
An issue exists where you are unable to verify a spanned non-NDMP image
using an NDMP drive.

Workaround:
To avoid this issue, do not use an NDMP drive to verify a spanned
non-NDMP image.
--------------------------------------------------------------------------------
Etrack Incident = ET863353
Associated Primary Etrack = ET863346

Description:
A restore failure would occur that caused bptm to send the wrong image
length to ndmpagent.
--------------------------------------------------------------------------------
Etrack Incident = ET799779
Associated Primary Etrack = ET799774

Description:
The recovery manager (RMAN) catalog maintenance functions were taking too
long and using excessive resources on the master server.

Additional Notes:
To ensure a faster search for catalog entries, use a %t on the format
parameter during an Oracle backup.
--------------------------------------------------------------------------------
Etrack Incident = ET792615
Associated Primary Etrack = ET781425

Description:
bpjobd script would hang sporadically causing the user to manually restart
to view the job monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET864935
Associated Primary Etrack = ET821288

Description:
If the client for a multiplexed backup could not be contacted, the job would
take nearly twice as long as to timeout.
--------------------------------------------------------------------------------
Etrack Incident = ET406353

Description:
Multi-streaming with wild-cards and NEW_STREAM directives would not
process correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET864177

Description:
The deletion of an application cluster would fail if there were storage
units (STU's) associated with it.

Workaround:
To avoid this issue, delete storage unit first.
--------------------------------------------------------------------------------
Etrack Incident = ET917548
Associated Primary Etrack = ET901564

Description:
If a window closes while a multiple data streams backup has children queued,
the resume of the parent may produce a 200 error.
--------------------------------------------------------------------------------
Etrack Incident = ET918511
Associated Primary Etrack = ET860790

Description:
Changed Policy Execution Manager to log failure history message as an
informational message to avoid adding it to the error log report. Also log
failure history message based on failure history threshold (default
12 hours) instead of using the policy update interval (default 10 minutes)
thus reducing the number of entries logged.

Workaround:
To avoid this issue, increase the policy update interval threshold from
the default of 10 minutes.
--------------------------------------------------------------------------------
Etrack Incident = ET860802
Associated Primary Etrack = ET850162

** Description:
The disk storage unit (DSU) staging did not maintain a retention level on
secondary copies when using inline tape copy (ITC).
--------------------------------------------------------------------------------
Etrack Incident = ET860288
Associated Primary Etrack = ET857531

Description:
Policy Execution Manager would stop processing manual backup jobs when
house keeping was performed (bptm delete_expired). The worst case
scenario was when the media server could not be reached. The Policy
Execution Manager would then wait for the time out
(CLIENT_CONNECT_TIMEOUT)to be exceeded before moving on.

Changed the Policy Execution Manager to start a third nbproxy which
processes only clean media database (db) commands to avoid a delay of
manual backups.
--------------------------------------------------------------------------------
Etrack Incident = ET914057

Description:
A problem existed that caused an error status on user backups to sometimes
return a 236 error when a 199 error was expected.
--------------------------------------------------------------------------------
Etrack Incident = ET867927

Description:
When using the bpsetconfig command to implement bp.conf entries for a
client, if stdin was used, the list could not exceed 1023 bytes. If
the list did exceed 1023 bytes, the entire list was ignored and the
update failed.

Workaround:
To avoid this issue, use the command with the filename as a parameter
and everything will work properly.

--------------------------------------------------------------------------------
Etrack Incident = ET919129
Associated Primary Etrack = ET848190

Description:
When Multiple Data Streams, DHCP and Windows Open File Backups (WOFB�s) are
enabled, jobs end with 48 status. To resolve this issue, the generic job
(nbgenjob) was changed to only pass a -hostname option if DHCP is enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET853612

Description:
The parent job would exit with a status 50 before starting any children. To
Resolve this issue, the parent job (nbgenjob) was changed to ping the job
manager as soon as possible after startup instead of waiting three minutes.
--------------------------------------------------------------------------------
Etrack Incident = ET832007

Description:
Logs were unclear on what the problem was when database operations were
performed on un-assigned media.
--------------------------------------------------------------------------------
Etrack Incident = ET505726

Description:
The "bpdbjobs -resume" command no longer reports an incorrect number of
restores that were resumed.
--------------------------------------------------------------------------------
Etrack Incident = ET845150

Description:
The machine update code has been updated so it no longer allows machines to
have invalid parent keys.
--------------------------------------------------------------------------------
Etrack Incident = ET856486
Associated Primary Etrack = ET997038

Description:
Added support for failing over NearStore storage units to a different NetApp
filer that had been mirrored using NetApp's Volume Snap Mirror technology.
--------------------------------------------------------------------------------
Etrack Incident = ET919043

Description:
A job that was configured to use a storage unit group, failed with a
status 129. The job details for a retry gives the appearance that it
retried the job with the STU from the previous try. In reality, all of
the STUs in the group were queried for the best possible candidate.
--------------------------------------------------------------------------------
Etrack Incident = ET838968

Description:
This maintenance pack contains new versions of ACE and TAO libraries. These
libraries contain fixes for race conditions and other problems.
--------------------------------------------------------------------------------
Etrack Incident = ET864163

Description:
A change was made so that nbrb no longer sends "bptm -rptdrv" to an
inactive node in a cluster. In addition, the output of the
nbemmcmd -listhost command has been changed. The description of
machine type for emmserver has been changed from "server" to
"emmserver".
--------------------------------------------------------------------------------
Etrack Incident = ET896185

Description:
When you log in on a node of master in cluster environment, the "Add STU"
operation did not show all of the available media servers.

Workaround:
To avoid this issue, log in using a virtual (cluster) name.
--------------------------------------------------------------------------------
Etrack Incident = ET901549
Associated Primary Etrack = ET857094

Description:
During testing, an active duplicate job was noticed in the Activity
Monitor. The job had a status 150 message in detailed status and it was
still at attempt 1. Its children appeared dead. (No activity in since
12:47 and they were being displayed as active).

The parent seemed active. It was not only displayed active but it was
doing a tape mount around 18:30. It had received a status 150 around
12:47 pm.

Workaround:
To avoid this situation, you can wait until the job state is active and
then cancel it. This will cause it to die correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET862912

Description:
Support for -fillup/-f option of BRBACKUP & BRRESTORE tools was added to
the NetBackup SAP Agent with this feature. If the backup/restore job
terminates and you do not want to repeat the complete backup/restore
again, the -f/-fillup option of BRBACKUP/BRRESTORE can be used now to
backup/restore only those files that were not saved and/or restored
earlier.

To use this feature for backups, configure 'Take checkpoints every _'
option for the SAP policy to a time period (range: 5-180 minutes).
Checkpoints are taken periodically after this time period. If the
backup job fails after taking a checkpoint, the partial image is
created until that checkpoint is retained. The SAP Agent gives
BackupIDs for files that are saved in this partial image.
Brbackup -f/-fillup option can be used to backup the remaining files.

The commands for backup are:
brbackup -d util_file -m all -c -f <brbackup_failed_job_log_name>
or
brbackup -d util_file -m all -c -f last

For restores, this feature is enabled automatically. If the restore job
fails after successfully restoring a few files, the SAP Agent reports
success for those files and reports an error for the remaining files.
BRRESTORE with -f/fillup option can be used to start a restore of the
remaining files.

The commands for restore are:
brrestore -d util_file -b <brbackup_log_name or last> -m all -c -f
<brbackup_failed_job_log_name>
or
brrestore -d util_file -b <brbackup_log_name or last> -m all -c -f last
--------------------------------------------------------------------------------
Etrack Incident = ET849073

Description:
Canceled mount/unmount requests would cause future unmount requests to hang
in BPTM.
--------------------------------------------------------------------------------
Etrack Incident = ET901476

Description:
Changes were made to keyword handling of user backups from
NetBackup 5.0 to 6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET863363

Description:
Job details for backup shows NDMP_XDR_DECODE_ERR error message, even though
the job completes successfully. This occurred only when the backup job
spans tapes.

Workaround:
If the job completed successfully, this error can be ignored.
--------------------------------------------------------------------------------
Etrack Incident = ET918447

Description:
BMR no longer creates multiple boot server records for the same boot server.
--------------------------------------------------------------------------------
Etrack Incident = ET814657

Description:
A backup job would potentially hang if bpbrm received a 174 error (media
manager - system error occurred) prior to receiving a "media ready"
indication from bptm.
--------------------------------------------------------------------------------
Etrack Incident = ET519708

Description:
The Perform Snapshot Backup option in Policy dialog should be disabled if
the Block level increment (BLI) is selected.
--------------------------------------------------------------------------------
Etrack Incident = ET922508
Associated Primary Etrack = ET854626

Description:
During multiplexed backups, multiple retention levels could be added to a
media, even if it was not configured to be allowed.
--------------------------------------------------------------------------------
Etrack Incident = ET515830

Description:
The SSO_SCAN_ABILITY option was not being used and has been removed to avoid
confusion.
--------------------------------------------------------------------------------
Etrack Incident = ET819221
Associated Primary Etrack = ET797322

Description:
Pegasus Software Drives on Windows did not work in NetBackup 6.0 as Disk
Storage Units.
--------------------------------------------------------------------------------
Etrack Incident = ET855357

Description:
NetBackup Enterprise Media Manager (EMM) was using the wrong directory when
checking for a disk full condition that affected the NetBackup Relational
Database (NBDB). If a mirrored transaction log was created, EMM was
checking the location of the main transaction log only.
--------------------------------------------------------------------------------
Etrack Incident = ET922513
Associated Primary Etrack = ET896030

Description:
FlashBackup restores would sometimes produce 252 errors when done with a
short file list.
--------------------------------------------------------------------------------
Etrack Incident = ET865177
Associated Primary Etrack = ET864919

Description:
Freeze scratch media that was found to have a Recorded Volume Serial Number
(RVSN) was not expected. Users must use bplabel to correct this problem
and make the media useable again.
--------------------------------------------------------------------------------
Etrack Incident = ET850088

Description:
Policy Execution Manager no longer passes unlocalized status descriptions
in the error database.
--------------------------------------------------------------------------------
Etrack Incident = ET852626
Associated Primary Etrack = ET841470

Description:
For TLH robots, NetBackup Vault was not recalling the media from the
offsite.

To resolve this issue for TLH robots, eject the media and recall them
back from the offsite location. And those media are now shown in the
"Picking list for Vault" report.

Additional Notes:
For TLH robots, NetBackup Vault was not adding media in the "Picking
list for Vault" report, which were supposed to be recalled from the
off-site location. Therefore, those media would not recalled back
rom the off-site location.
--------------------------------------------------------------------------------
Etrack Incident = ET848632
Associated Primary Etrack = ET841558

Description:
A fix was added so that nbgenjob no longer fails with status 25
and nbpem no longer receives a status 50 after a multi-streaming
job.
--------------------------------------------------------------------------------
Etrack Incident = ET858227

Description:
NetBackup-Java Administration Console Device Configuration wizard now
correctly updates the Robot Type of drives that are detected as stand
alone but drag-dropped by user to a robot.
--------------------------------------------------------------------------------
Etrack Incident = ET865805

Description:
On Windows systems, the Vault reports were not being localized.
--------------------------------------------------------------------------------
Etrack Incident = ET896510

Description:
A change was made to correct an issue that was causing code to appear in a
progress log.
--------------------------------------------------------------------------------
Etrack Incident = ET896531

Description:
A change was made to correct a core dump issue that occurred from vmdareq
when it was run from a command line with no switches.
--------------------------------------------------------------------------------
Etrack Incident = ET896568

Description:
The words "handling path" were not being recorded in the \db\error\ logs
file. The All Logs Entry and the bperror command both mine their results
from the \db\error\ logs and the words "handling path" could be used to
determine if the correct data is being backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET916389
Associated Primary Etrack = ET863109

Description:
Changes were added to resolve an nbpem core dump that would occur after a
successful backup.
--------------------------------------------------------------------------------
Etrack Incident = ET863403

Description:
The selected host does not have the service BPRD operating. (Error 25)

This problem occurred on Windows. The handle count for the process
"tldcd.exe" was very high (several thousand). This resulted in a lack
of resources that caused other processes, such as bprd, to fail.

Workaround:
Stopping and starting the Device Manager Services will cause a new tldcd
process. The old tldcd process will shutdown and release all its unclosed
handles.
--------------------------------------------------------------------------------
Etrack Incident = ET863396

Description:
NDMP backup fails when TIR data spans tapes. This failure occurs only for
NDMP local or NDMP 3-way (backup to an NDMP drive).

Workaround:
Rerunning the backup to a different media will likely work since it is
unlikely that tape spanning will occur during TIR data. (This is because
the TIR data is usually a fraction of the size of the backup image itself.)

Another approach is add the following line to the file
<installdir>/netbackup/db/config/ndmp.cfg

NDMP_MOVER_CLIENT_DISABLE

Adding this line will have a minimal impact on backups. However it will
cause a significant performance impact to dup/verify/import when using
NDMP drives.
--------------------------------------------------------------------------------
Etrack Incident = ET777981

Description:
nbpemreq would fail if a large time value was passed to the nbpemreq
predict option. If you specified a number that exceeded a long value
for the command, nbpemreq -predict -dateu <timevalue>, the results
would be undefined.
--------------------------------------------------------------------------------
Etrack Incident = ET821317

Description:
A misleading error status 48 (client hostname could not be found) may be
applied to a job if a communication problem occurred between the media and
the master server. A typical cause of the problem was an expired license
on the media server. In this case, the error status should have been 161
(Evaluation software has expired.)
--------------------------------------------------------------------------------
Etrack Incident = ET828730

Description:
In a rare situation, a FlashBackup job could not be cancelled.
--------------------------------------------------------------------------------
Etrack Incident = ET863430

Description:
An NDMP backup this is greater than 4 terabytes (TB) fails on duplication.
The following error appears in the progress log:

ERR - Unable to create data socket to receive TIR data.

Workaround:
To avoid this issue, break up the backups so that they are smaller than 4TB.
--------------------------------------------------------------------------------
Etrack Incident = ET924742

Description:
When using VSP as the Windows Open File Backup (WOFB) snapshot provider on a
Windows NT4 client, the file system backups of Windows NT4 clients may end
with partial success. VSP snapshot creation failed on Windows NT4 clients
because the VSP driver did not initialized correctly after a clean install.
--------------------------------------------------------------------------------
Etrack Incident = ET852018

Description:
Changes have been made to reduce the performance overhead when sending mail
to a client after a backup job completes.
--------------------------------------------------------------------------------
Etrack Incident = ET896769
Associated Primary Etrack = ET923399

Description:
The pem logs report a scheduled backup (SB) job type as an immediate (IB)
backup job type after a failed immediate backup.
--------------------------------------------------------------------------------
Etrack Incident = ET773744

Description:
Exchange MBX backups configured incorrectly would fail with status 1 instead
of a status 71.
--------------------------------------------------------------------------------
Etrack Incident = ET864933

Description:
On Windows media servers, restores from disk in some cases would potentially
read unneeded data instead of skipping it, which could affect performance.
--------------------------------------------------------------------------------
Etrack Incident = ET805992

Description:
In some cases, hot catalog backup would report success even though the
ASA backup was either not successful or conditionally successful.
--------------------------------------------------------------------------------
Etrack Incident = ET924798
Associated Primary Etrack = ET860296

Description:
Callers to bpdbm make unnecessary licensing checks that could lead to
misleading error messages.
--------------------------------------------------------------------------------
Etrack Incident = ET923799

Description:
With NetBackup running under NetBackup Access Control (NBAC), authorization
checks were skipped for some operation of corba daemons. This could have
enabled an unauthorized user to perform some privileged operations.
--------------------------------------------------------------------------------
Etrack Incident = ET924345
Associated Primary Etrack = ET856266

Description:
Jobs that were due to start, would not start if JobDefinition::checkDueness
took more than one second.
--------------------------------------------------------------------------------
Etrack Incident = ET863251
Associated Primary Etrack = ET863137

Description:
An option was added for a user-directed Exchange backup to act as a full
and not a copy backup. A registry key enables the functionality.
--------------------------------------------------------------------------------
Etrack Incident = ET901028

Description:
Changes were made that enable you to now use "./bpnbat -login -info" on
Linux systems.


Workaround:
You can also use bpnbat in interactive mode by using just the -login option.
--------------------------------------------------------------------------------
Etrack Incident = ET778927

Description:
A master could be renamed to a pre-existing media server. However, the
logs were recording the wrong name if a machine was renamed to a
pre-existing machine.
--------------------------------------------------------------------------------
Etrack Incident = ET417907

Description:
When vmquery was used with a prefix containing '_', the char '_' was used
as a wild card character and an out of order media id could be given.
--------------------------------------------------------------------------------
Etrack Incident = ET831182

Description:
The message, "database backup is currently disabled," appeared in the
Problems report even when a scheduled hot catalog backup was configured.
--------------------------------------------------------------------------------
Etrack Incident = ET863447

Description:
NDMP restore from an Overland tape device failed because the same
fragment was loaded twice.
--------------------------------------------------------------------------------
Etrack Incident = ET865094

Description:
Exchange restores will now allow multiplexed restores if the restore job is
requesting one image to restore from or if all images requested are on the
same media.
--------------------------------------------------------------------------------
Etrack Incident = ET924482

Description:
The parent key could be incorrectly set when adding a node of a cluster.
The parent key of a media server could be incorrectly set if node of master
cluster was given instead of cluster name.
--------------------------------------------------------------------------------
Etrack Incident = ET534073 ET534196 ET569931 ET592599

Description:
The following Windows updates have been added to this maintenance pack:
- Updated the support utility nbsupport to version 2.1.2
- Updated the Windows support utility nbsupport.exe to version 2.1.2
- Updated the Windows support utility nbsu_win_cmds.exe to version 2.0
- Added the Windows support script fs
--------------------------------------------------------------------------------
Etrack Incident = ET864934

Description:
A duplication may have been reported as successful if a defective tape
drive incorrectly reported a tape mark on the read operation, followed
by an I/O error. This maintenance pack detects this error condition.
--------------------------------------------------------------------------------
Etrack Incident = ET803724

Description:
Catalog recovery from a hot catalog backup failed if Bare Metal Restore
(BMR) was installed but not configured and/or running at the time of the
hot catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET923486
Associated Primary Etrack = ET922740

Description:
jbpSA/bpubsbora would produce a segmentation fault when the oratab file had
more than 50 valid entries.
--------------------------------------------------------------------------------
Etrack Incident = ET648727

Description:
Added a new Automated Cartridge System (ACS) vendor for media and drive
types.
--------------------------------------------------------------------------------
Etrack Incident = ET857214

Description:
Changes were added so that the date printed at the top of Vault reports is
now localized.
--------------------------------------------------------------------------------
Etrack Incident = ET616381

Description:
In NetBackup-Java Administration Console, inventory of a robot attached to
a cluster node resulted in volumes being added with the cluster node as the
robot control host and not the virtual host name. This behavior has been
changed to make the virtual host name as the control host. Doing this
avoids potential problems in inventory if a cluster fails over to a
different cluster node.
--------------------------------------------------------------------------------
Etrack Incident = ET895576

Description:
Corrected an issue where the restore of Lotus databases were partially
successful for UNC path.

--------------------------------------------------------------------------------
Etrack Incident = ET916378
Associated Primary Etrack = ET915043

Description:
The bpdbjobs timestamp output is no longer truncated for STARTED and ENDED
fields.
--------------------------------------------------------------------------------
Etrack Incident = ET863435

Description:
It was possible that tape drives for SSO could cause a DEVICE_BUSY_ERR
error on the backup host. Retry logic was added in this maintenance
pack so that if an NDMP_DEVICE_BUSY_ERR error is received when opening
an NDMP drive, a retry will occur.
--------------------------------------------------------------------------------
Etrack Incident = ET863432

Description:
ndmpagent dumps core if the last line in the path list is not a path.

This happens if the user incorrectly adds a "SET" line to the end of the
path list. For example:
/vol/dir_to_backup
SET HIST=n

The "SET" line must come before the path to backup. A fix was added so
that it no longer causes a core dump and instead runs the job and reports
partial success.

Workaround:
To resolve this issue, correct the path list so that it ends with a path.
--------------------------------------------------------------------------------
Etrack Incident = ET616141

Description:
An incorrect nomenclature existed for the dialogue box of
"Authorization Domain". The correct box should be "Authentication Domain".
--------------------------------------------------------------------------------
Etrack Incident = ET895580

Description:
In Windows, restoring a Lotus database with a non-English name would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET895551

Description:
Attempting to backup a Lotus database with names that contain characters
like "%s", "%5.nsf" would make the Lotus Notes agent crash the Domino
server.
--------------------------------------------------------------------------------
Etrack Incident = ET842011

Description:
bpmedialist could not be killed from the Activity Monitor successfully.
A change was made to ensure the correct program name is being passed from
bpmedialist to the job manager (JM).
--------------------------------------------------------------------------------
Etrack Incident = ET857564

Description:
Changes were made to enable Instant Recovery for Windows FlashBackup
policies.
--------------------------------------------------------------------------------
Etrack Incident = ET926712

Description:
A small memory leak in Policy Execution Manager when processing change
events has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET926721

Description:
Changed the Policy Execution Manager to pass the locale attributes correctly
to the job manager instead of setting them all to lctype.
--------------------------------------------------------------------------------
Etrack Incident = ET852018

Description:
Changes were made to address some small performance issue due to unnecessary
string duplications in the Policy Execution Manager when mailing client
status upon job completion.
--------------------------------------------------------------------------------
Etrack Incident = ET767211

Description:
Added Oracle support for Windows 2003 x64.
--------------------------------------------------------------------------------
Etrack Incident = ET863453

Description:
An error message "write to socket returned -1" occurs on NDMP restore.

The restore is reported as successful. In fact, the restore is successful.
The error message is misleading and has been removed from the user
interface.

Workaround:
Since the restore was successful, the error message can be ignored.
--------------------------------------------------------------------------------
Etrack Incident = ET863454

Description:
The Veritas Unified Logging (VxUL) logging level for NDMP (ORGID=151) does
not change while an NDMP backup or restore is in process. A change has
been made that enables you to change to DebugLevel for NDMP so that it
takes affect while an NDMP backup or restore is in process.
--------------------------------------------------------------------------------
Etrack Incident = ET856250

Description:
Mapping an extended partition no longer fails with the following error
message:

Error 1003, unable to create subdisk of size X bytes',
where X is the size of the partition in bytes.
--------------------------------------------------------------------------------
Etrack Incident = ET611965

Description:
The eject notification email in a Vault configuration cannot be more than
127 characters long.

Workaround:
To resolve this issue, create an email alias, rather than entering the full
list of addresses in the Vault configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET896570

Description:
Vault does not abort a session if any of the Notify scripts return a
non-zero exit status.
--------------------------------------------------------------------------------
Etrack Incident = ET844889
Associated Primary Etrack = ET839903

Description:
The "Summary Distribution List for Vault" in Vault reports generates data
that is not readable in the Windows Console.
--------------------------------------------------------------------------------
Etrack Incident = ET498723

Description:
In the event that a shared standalone drive is updated to be robotic, other
hosts that share this drive will also be updated to robotic. If the robot
is not configured on any of those hosts, however, this results in an
illegal configuration.

Workaround:
To avoid this issue, manually create robotic entries or only use the Device
Configuration wizard.
--------------------------------------------------------------------------------
Etrack Incident = ET926699
Associated Primary Etrack = ET925811

Description:
When drives are selected for NDMP restores, NetBackup media servers are
preferred over NDMP tape servers that are not local to the NDMP host being
restored to.

Workaround:
If a media server has drives with paths to both NetBackup and NDMP servers,
you should down the NetBackup paths before initiating the restore.
--------------------------------------------------------------------------------
Etrack Incident = ET863458

Description:
NDMP backup no longer fails a block position check when two directories are
backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET863457

Description:
NDMP restores using SpectraLogic Gator fails

The NetBackup NDMP log showed an NDMP_MOVER_STOP message failing with
NDMP_ILLEGAL_STATE_ERR.

Additional Notes:
The SpectraLogic Gator did not detect that the data connection from the
data side of the 3-way backup had closed. It also did not process the
NDMP_MOVER_CLOSE message properly, as that should have brought it to a
HALTED state where the NDMP_MOVER_STOP would have been okay. And
NetBackup should have ignored all of this because the data side
reported a SUCCESSFUL status for the restore.

This fix detects the problem in the mover side and issues
NDMP_MOVER_ABORT to bring it to HALTED state.
--------------------------------------------------------------------------------
Etrack Incident = ET865066

Description:
If an Exchange VSS backup included a file list item that does not exist,
the backup would still end with status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET852171

Description:
The EMM server does not reject a client-provided media_id such as, '------'.
This is not a regression. The NetBackup 5.x behavior was exactly the same.

Workaround:
This issue is a client application error when such a name comes is used.
--------------------------------------------------------------------------------
Etrack Incident = ET851125
Associated Primary Etrack = ET793484

Description:
In some instances a job would receive an incorrect 24 status (socket write
failed) instead of the correct 84 status (media write error).
--------------------------------------------------------------------------------
Etrack Incident = ET865106

Description:
Using the eseutil throttling option for Exchange VSS backups would sometimes
cause a status 13 error.
--------------------------------------------------------------------------------
Etrack Incident = ET417904

Description:
NetBackup clients using Windows Open File Backup and VSP as its snapshot
provider may intermittently have some VSP cache files leftover when running
multi-streamed jobs. This was because the snapshot cleanup functionality in
the client was done at the end of a backup instead of the beginning of a
backup. Multi-streamed backups that last a long time (first stream takes
about an hour and the rest of the streams take longer than an hour) with
multiple groups of streams running at the same time may have problems
deleting VSP snapshots because of this.
--------------------------------------------------------------------------------
Etrack Incident = ET846076

Description:
An incremental hot catalog backup would fail with a 190 error if the master
server name configured in the hot catalog backup policy differed from the
currently active master server name where each name is a valid name for the
host. This would occur if the long name was used in the policy, but the
short name was being used in the bp.conf file.
--------------------------------------------------------------------------------
Etrack Incident = ET863389

Description:
Duplication of NDMP image fails when using non-NDMP drives.

This problem only occurs when the duplication is using the shared memory
method (SHM) method. In NetBackup 6.0, this happens for any NDMP backup
that used MM (non-NDMP) drives (also known as, "Remote NDMP"). In addition,
this happens if an NDMP image is duplicated to a non-NDMP drive and then
the duplicated image is duplicated.

The progress log shows the following error:
ERR - Unable to create data socket to receive TIR data.

Workaround:
To avoid this issue, disable the shared memory method by adding the
following touch file:
<installdir>/netbackup/NOSHMDUP

Additional Notes:
This problem has been fixed in this maintenance pack, such that all
duplications of NDMP backup images using non-NDMP drives will now use
the shared memory method.

(This problem was solved by disabling shared memory method for all
NDMP images in the NetBackup 5.1 maintenance packs.)
--------------------------------------------------------------------------------
Etrack Incident = ET805980

Description:
On Windows platforms, a hot catalog backup would fail when backing up the
Sybase ASA database files if NetBackup is installed in a directory beginning
with '\n', for example, G:\nbu.
--------------------------------------------------------------------------------
Etrack Incident = ET828441

Description:
NetBackup relational databases would not be restarted when a cold catalog
backup was canceled.
--------------------------------------------------------------------------------
Etrack Incident = ET930028

Description:
A hot catalog backup parent job no longer fails with a status 818 error
(retention level mismatch).
--------------------------------------------------------------------------------
Etrack Incident = ET862324

Description:
A change was added to remove hard coded English Error Messages in bmrsrtadm.
--------------------------------------------------------------------------------
Etrack Incident = ET893639 ET417284

Description:
When NetBackup is clustered, NOM would show the wrong information about
services and media.
--------------------------------------------------------------------------------
Etrack Incident = ET895543

Description:
NetBackup for Lotus Notes transaction log restores no longer fail with a
Status 5 when the "Transaction Log" node is selected for restore.
--------------------------------------------------------------------------------
Etrack Incident = ET895545

Description:
A change was added to ensure the NetBackup for Lotus transaction logs
restore with the proper modified and creation dates.
--------------------------------------------------------------------------------
Etrack Incident = ET583036

Description:
Restoring a Lotus database link no longer results in a loss of data.
--------------------------------------------------------------------------------
Etrack Incident = ET922076

Description:
When a database link is restored on UNIX platform, it is restored with the
size of the original database it was pointing to when the backup was taken.
--------------------------------------------------------------------------------
Etrack Incident = ET865713

Description:
Under NBAC, 'bpnbaz -setupsecurity' could fail silently, potentially
compromising the desired access control hierarchy.
--------------------------------------------------------------------------------
Etrack Incident = ET863443

Description:
An NDMP backup a file that is greater than 2GB no longer causes the reported
size of that file to be incorrect in the catalog file.
--------------------------------------------------------------------------------
Etrack Incident = ET925839

Description:
The shell script, versioninfo, was originally a UNIX-only shell script.
This maintenance pack contains, versioninfo.exe, a Windows version of
this script.
--------------------------------------------------------------------------------
Etrack Incident = ET854649

Description:
The shutdown and startup of the NetBackup relational databases, NBDB and
BMRDB, will be logged to the NetBackup error log.
--------------------------------------------------------------------------------
Etrack Incident = ET922097

Description:
A change has been made so that if a database is partially restored, it is
renamed back to the original name.
--------------------------------------------------------------------------------
Etrack Incident = ET796330

Description:
Added support for NetAPP VSS provider for Filesystem and Exchange VSS
offhost Backup.
--------------------------------------------------------------------------------
Etrack Incident = ET863377
Associated Primary Etrack = ET863373

Description:
After an NDMP backup spans media, the second tape is mounted in a drive in
the same robot, however the drive is attached to a different NAS filer. The
tape mount caused the backup to fail because it should not have used a
drive that is attached to a different NAS filer.
--------------------------------------------------------------------------------
Etrack Incident = ET863289

Description:
NDMP_LOG_ERROR messages are now sent to the progress log.

When doing an NDMP backup or restore, if the NAS device detects an error
and sends NetBackup a message of type NDMP_LOG_ERROR, this message will
be displayed in the progress log. This is consistent with functionality
in pre-6.0 NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET863382

Description:
bpduplicate would fail when using the ndmp_mover_connect method.

In NetBackup 6.0, the ndmp_mover_connect method is not used by default, so
this would only fail if this feature had been explicitly enabled. The
failure occurred when the duplicate fragments because of a maximum fragment
size or tape spanning.
--------------------------------------------------------------------------------
Etrack Incident = ET536723

Description:
Added NetBackup for DB2 support on 64-bit x86 Windows operating systems.
--------------------------------------------------------------------------------
Etrack Incident = ET927755
Associated Primary Etrack = ET926665

Description:
On some Windows machines, any Firewall_in bpconf configuration would report
as "Malformed Firewall_in line" in the VxUL log files, and rendered the
NAT translation feature as not operational.
--------------------------------------------------------------------------------
Etrack Incident = ET926704
Associated Primary Etrack = ET926503

Description:
If a user backup submits a very large number of files, PEM may cause a
memory fragmentation and possibly a crash.

Workaround:
To resolve this issue, reduce the file list size by specifying directories
instead of individual files.
--------------------------------------------------------------------------------
Etrack Incident = ET928972
Associated Primary Etrack = ET785731

Description:
Windows Disk Image/Raw Partition back up fails when the Checkpoint Restart
option is enabled.

Workaround:
To avoid this issue, do not enable the Checkpoint Restart option for Disk
Image backups.
--------------------------------------------------------------------------------
Etrack Incident = ET917579

Description:
A change was made to ensure that the NetBackup client version is listed
correctly after the NetBackup client package from the NetBackup 6.0MP4 CD
build is added.
--------------------------------------------------------------------------------
Etrack Incident = ET515549 ET933307

Description:
The CIsActive function that is loaded from the NBClusterConfig.dll failed on
64-bit systems.

Additional Notes:
The use of VCS API calls, which did not support 64-bit platforms in the
past, have been removed. IsActive simply tests if the shared disk resource
is on the current system to determine if it is the active node.
--------------------------------------------------------------------------------
Etrack Incident = ET932016 ET988979 ET1002606

Description:
Buffer overflow areas have been identified and corrected in daemons that
run on Veritas NetBackup master, media, and client servers. Successful
access to a vulnerable Veritas NetBackup server and the ability to
successfully execute arbitrary code could potentially result in
unauthorized access with elevated privilege on a system.
--------------------------------------------------------------------------------
Etrack Incident = ET932003

Description:
A change was added to resolve a possible memory corruption issue in the
legacy DA process (vmd on EMM server).
--------------------------------------------------------------------------------
Etrack Incident = ET927553
Associated Primary Etrack = ET924626

Description:
Fixed an issue that caused bpbkar to hang on Linux systems if it encounters
an NFS mount point when the NFS server is down.

Workaround:
To resolve this issue, add the NFS mount point to the exclude list for the
client.
--------------------------------------------------------------------------------
Etrack Incident = ET854810

Description:
By using the bprestore command (/usr/openv/netbackup/bin/bprestore) it is
now possible to restore an image using a non-primary copy.

Workaround:
In addition, you can use the bpchangeprimary command
(/usr/openv/netbackup/bin/admincmd/bpchangeprimary) to change the primary
copy of the image.
--------------------------------------------------------------------------------
Etrack Incident = ET533389

Description:
For a True Image Restore (TIR) that is larger than 2GB, the following error
would occur when reading the TIR information.

Error occurred reading TIR information, expected -2103963310 bytes, read
2191003986

The bpdm log would show the following:

11:03:32.958 [20388] <16> read_data_tir: ERR - Error occurred reading TIR
information, expected -2103963310 bytes, read 2191003986

2191003986 is the size of the TIR file -
-rw------- 1 root root 2191003986 Dec 30 10:50
devnfs2-bkup_1135889406_C1_TIR.1135889406.img

The problem only occurred, when the TIR file was larger than 2GB.
--------------------------------------------------------------------------------
Etrack Incident = ET863133

Description:
A fix was added so that a hot catalog recovery from a hot catalog backup to
a new master server name no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET925227
Associated Primary Etrack = ET922389

Description:
When the client name is in upper case, a Windows backup uses WOFB even
though the clientDB entry disables the WOFB.

Workaround:
To resolve this issue, use the same case for client name in client
database and policy database.
--------------------------------------------------------------------------------
Etrack Incident = ET895746

Description:
The renewal of a machine credential issued by a non-root authentication
broker no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET932264
Associated Primary Etrack = ET893298

Description:
An issue existed that would sometimes cause a job to run on the exclude day
even if a frequency scheduling of 24 hours was used.
--------------------------------------------------------------------------------
Etrack Incident = ET510678

Description:
The NetBackup-Java Administration Console would fail to display Vault
Reports in a localized NetBackup installation.
--------------------------------------------------------------------------------
Etrack Incident = ET848040
Associated Primary Etrack = ET841853

Description:
Incremental NDMP backups would fail with status code 99 when no data has
changed. The problem occurred because of an incremental backup that had no
changed data, and thus, was a 0-byte backup.

A change was made to add support for backup, restore, duplicate, verify, and
import of 0-byte backups.
--------------------------------------------------------------------------------
Etrack Incident = ET855922

Description:
Catalog archiving would fail intermittently with the following message:

bpcatarc: failure running catalog archiving backup policy: the specified
policy is not active (247)

Workaround:
This problem was observed with a mis-configured /etc/hosts file, which
caused excessively long DSN lookups. To avoid this situation, configure
the /etc/hosts file to avoid long DSN lookups.
--------------------------------------------------------------------------------
Etrack Incident = ET591098
Associated Primary Etrack = ET896233

Description:
If the hot catalog backup encountered an image catalog that was corrupted,
it would continue the hot catalog backup, and then finish with success
status of 0.

Changes have been made so that the hot catalog backup continues past the
corrupted image catalog, and backs up the rest of the catalog, but it
finishes with a partial success status of 1.

Workaround:
To avoid this issue, fix the corruption in the image catalog, or take a
cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET930124

Description:
A change has been made to ensure that NBPEM finds all user-initiated jobs,
all of the time.
--------------------------------------------------------------------------------
Etrack Incident = ET850566
Associated Primary Etrack = ET844922

Description:
Vault would fail to sync recalled media with the EMM database, resulting
with vmchange producing the error message, "invalid command usage".
--------------------------------------------------------------------------------
Etrack Incident = ET855860
Associated Primary Etrack = ET819709

Description:
Policy names are truncated in the Summary Distribution list and the Detailed
Distribution list for Vault. The client and policy names are split in the
above reports to overcome a possible policy name truncation.
--------------------------------------------------------------------------------
Etrack Incident = ET933326
Associated Primary Etrack = ET917312

Description:
nbnos would core dump on an HP-UX master server with max_thread_proc set at
the default value of 64. Every nbpem restart would cause nbnos to create
more threads. Corrections were made to nbpem that prevent nbnos from
creating new threads every time nbpem is restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET933586
Associated Primary Etrack = ET932325

Description:
During a multi-streamed database backup (MS-SQL backup in this case), the
media gets unmounted/mounted again intermittently. Ideally, the NetBackup
resource broker (nbrb) should try to use the loaded media (preferably same
media) for all streams.
--------------------------------------------------------------------------------
Etrack Incident = ET915850
Associated Primary Etrack = ET915879

Description:
Changes were made to ensure that multi-threaded processes no longer crash.
--------------------------------------------------------------------------------
Etrack Incident = ET918766

Description:
Sorting would not work on some columns if the report contained one or more
hidden columns.
--------------------------------------------------------------------------------
Etrack Incident = ET933398
Associated Primary Etrack = ET933394

Description:
Backups may not run as expected if full and incremental had the same
frequency.
--------------------------------------------------------------------------------
Etrack Incident = ET931959
Associated Primary Etrack = ET931900

Description:
Corrected errors that caused canceled backups to leave the tape media
without a valid empty header on it.
--------------------------------------------------------------------------------
Etrack Incident = ET847597

Description:
In NetBackup Vault product, the purging functionality of profile/session
record from vlteject.mstr file was missing.

Additional Notes:
The vlteject.mstr file will now be purged automatically, whenever you
run a Vault session. It will remove the profile > session entry from
vlteject.mstr file, when corresponding session directory is missing
(or removed).
--------------------------------------------------------------------------------
Etrack Incident = ET819697

Description:
This maintenance pack contains enhancements and fixes to some minor errors
that were occurring in NOM (specifically in the Display Point version of
NetBackup in NOM).
--------------------------------------------------------------------------------
Etrack Incident = ET797596

Description:
On the NOM user interface, (Managing > Media > Details) the "Time Assigned"
filter was not functioning properly.
--------------------------------------------------------------------------------
Etrack Incident = ET896513

Description:
NBPEM e-mail function would send a secondary "additional information" e-mail
for some failed backups.
--------------------------------------------------------------------------------
Etrack Incident = ET892407

Description:
Corrected an issue that caused bplabel to fail if VxSS (NBAC) is enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET807751

Description:
The "import" feature would not work on a NOM Windows server after an
"export" database (DB) function was performed.
--------------------------------------------------------------------------------
Etrack Incident = ET852129

Description:
Under NBAC, a NetBackup 5.1 media server or client could not be configured
with NetBackup 6.0 master.

The bpnbat -loginmachine command would cause a hang or failure on a
NetBackup 5.1 media server or client. The following logs were produced.

14:52:27.578 [2035] <2> get_string: (7) inadequate buffer space for data
14:52:27.578 [2035] <2> get_string: read until the buffer was full; got:
14:52:27.578 [2035] <2> get_string: EXIT STATUS 13
14:52:27.578 [2035] <2> bprd_get_nbac_pdr_info: get_string() failed,
Error 0 (0), success
--------------------------------------------------------------------------------
Etrack Incident = ET929910
Associated Primary Etrack = ET915900

Description:
After applying 6.0 MP4 on Windows 2003 machines with DFS (Distributed File
System) configured, the bpbkar32.exe process would fault when backing up
Shadow_Copy_Components.
--------------------------------------------------------------------------------
Etrack Incident = ET794712
Associated Primary Etrack = ET785847

Description:
Changes were added to increase the efficiency of an image cleanup when the
disk-stage storage unit (DSSU) fills.
--------------------------------------------------------------------------------
Etrack Incident = ET845125

Description:
An exception occurs sometimes when opening the NetBackup-MSSQL user
interface if the host machine is disconnected from the network.

Workaround:
To avoid this issue, update the default SQL host and default SQL registry
entries manually, in case your host machine is disconnected from the
network.
--------------------------------------------------------------------------------
Etrack Incident = ET934452

Description:
The machine state could be reported inaccurately from the
nbemmcmd -listhosts -verbose command if the machine state was inactive
for disk jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET853808 ET898992

Description:
A multi-streamed parent job may have been retried more than the configured
number of times if the parent job failed before the streams were created for
the first time.
--------------------------------------------------------------------------------
Etrack Incident = ET764762

Description:
Vault was erroneously killing duplication jobs that copied data to a tape
storage unit because of a change to a log message.
--------------------------------------------------------------------------------
Etrack Incident = ET797314

Description:
Add VxUL Logging support for Activity Monitor module and as a result
a new log file with ID 263 will be generated in the logs folder.
--------------------------------------------------------------------------------
Etrack Incident = ET935814

Description:
Corrected the check used to determine if the local device_mappings.txt
is current.
--------------------------------------------------------------------------------
Etrack Incident = ET792287
Associated Primary Etrack = ET792281

Description:
The NetBackup SharePoint 2003 agent would receive an "access denied" status
when attempting to backup a Portal Index database.
--------------------------------------------------------------------------------
Etrack Incident = ET913578

Description:
NBSL is crashing due to the read only directory or invalid path of nbsl.xml.
--------------------------------------------------------------------------------
Etrack Incident = ET640573
Associated Primary Etrack = ET777779

Description:
The SharePoint 2003 agent redirection of the portal databases were not
redirecting the SharePoint databases to the correct destination portal path.
Instead, the redirect put the databases back to the master database
location.
--------------------------------------------------------------------------------
Etrack Incident = ET614826
Associated Primary Etrack = ET777799

Description:
Added support for SQL 2005 with NetBackup SharePoint 2003 agent.
--------------------------------------------------------------------------------
Etrack Incident = ET933518 ET933543 ET544382 ET933547 ET933544 ET933528 ET933537
ET830317 ET830319 ET916879
Associated Primary Etrack = ET814702 ET799749 ET647499 ET899240 ET851802
ET858011

Description:
The following changes were added to this maintenance pack in response to
customer escalations:
- Issues with pop-ups that occurred when FlashBackup terminated
- Restores from multiple images
- Multi-volume image and 32-bit overflow
- Incorrect handling of multi-byte characters
- Incomplete data being sent to catalog
- Ensure that directories are restored in descending order
- Hard-link restore problems
- Linux master and FlashBackup windows
--------------------------------------------------------------------------------
Etrack Incident = ET861506

Description:
The Job Manager must forward a snap ID from a non-streamed Windows open
file backup (WOFB) to the Policy Execution Manager for VSP cache files
to be cleaned. In addition, changed the Policy Execution Manager to add
SNAP_ID directives to include the file list.
--------------------------------------------------------------------------------
Etrack Incident = ET918477
Associated Primary Etrack = ET917028

Description:
This is limited to the Nearstore storage unit.
If an incremental backup was done after a synthetic full backup, and no
other full backups existed on that volume, then the incremental would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET899124
Associated Primary Etrack = ET899121

Description:
This issue only affected restores from Nearstore storage units.
Non-full backups (a subset of the entire backup ) where files were pulled
from fragments other than fragment 1 would fail. The issue was that the
image relative offset was not being tracked and NetBackup was seeking to
the incorrect offset within the image.

Workaround:
To resolve this issue, use the Nearstore File System Export functionality
or duplicate the entire backup to basic disk or some other media.
--------------------------------------------------------------------------------
Etrack Incident = ET921795

Description:
Changes were made in this maintenance pack to ensure the Log Management
feature is working.
--------------------------------------------------------------------------------
Etrack Incident = ET937144

Description:
A new, unsupported Windows application for viewing log files has
been added in the goodies directory, at:

VERITAS\NetBackup\bin\goodies\lv.exe

You can use this application to build a VxLogView command and
run it. For more information and instructions on using the tool,
click the help button within the application, or double click
the lv.chm file within Explorer.
--------------------------------------------------------------------------------
Etrack Incident = ET932217

Description:
NBJM was failing jobs with a status 818 (retention level mismatch) because
of an incorrect check.
--------------------------------------------------------------------------------
Etrack Incident = ET937680

Description:
Some TLD libraries with barcode readers were unable to import or inventory
media with an unbarcoded media in the library.
--------------------------------------------------------------------------------
Etrack Incident = ET828518 ET959929 ET959931
Associated Primary Etrack = ET828513

Description:
Added NDMP support for multiple NICs with multiple disjoint networks.

For example, consider the following configuration:
- Media Server with two NICs (Network Interface Cards)
- Each NIC is connected to a network that is independent of the other.
- NDMP servers on each of the networks.
- Tape drives attached to the Media Server (used for Remote NDMP backups)

Previous to this patch update, the Media Server would not be able to
perform Remote NDMP backups for all of the NDMP servers in the
configuration. It would have been able to support the NDMP servers on
one network or the other, but not on both.

With this update, a single Media Server can support multiple NICs and
multiple networks.

Another smaller part of this update is that, when writing the catalog file
to tape (which is done after every NDMP backup) and when doing duplicate,
verify, and import using NDMP drives, NetBackup now creates a listen socket
and sends it to the NDMP server to connect to. Previous to this patch, the
NDMP server would create the listen socket and NetBackup would connect to
it. This change is intended to help control firewall situations by
enabling NetBackup users to specify the port ranges used. The port ranges
that are used are specified in the "Host Properties" for NetBackup.

Additional Notes:
For most network topologies this should work without any additional
configuration of NetBackup. Where an additional configuration might be
needed is in situations where there are more than one network path to a
particular NDMP server, and one network path is preferred over another.
An example might be where there are both 100 Mbps and 1000 Mbps networks.
In such cases, the preferred network can be specified.

NOTE: These parameters effect only the NDMP data connections, they do not
effect the NDMP control connections. The NDMP control connection is used
to send/receive NDMP control messages, while the NDMP data connection is
used to transfer the backup data stream.

To specify the network path to use for NDMP data connections, create the
following file:

<installdir>/netbackup/db/config/ndmp.cfg

To specify the Media Server host name to use for all NDMP data
connections between the media Server and any NDMP host, add the following
line:

NDMP_DATA_CONNECTION_HOST_NAME=host_name

Where host_name is either xx.xx.xx.xx or the host_name as a string.


To specify the Media Server host name to use for NDMP data connections
between the Media Server and a specific NDMP host, add the following
line:

NDMP_DATA_CONNECTION_HOST_NAME_FOR_nnnn=host_name

Where nnn is the NDMP host name, and
Where host_name is either xx.xx.xx.xx or the host_name as a string.
--------------------------------------------------------------------------------
Etrack Incident = ET937829

Description:
Accessing the Oracle wizard though the BAR Java user interface causes an
error box to appear with the following messages after clicking on the
"Oracle" node.

- /usr/lib/dld.sl invalid version for shared library
- /usr/openv/java/jre/lib/PA_RISC2.0/libjava.sl (status 134)
--------------------------------------------------------------------------------
Etrack Incident = ET831697

Description:
Added some exception handling code to this maintenance pack.
--------------------------------------------------------------------------------
Etrack Incident = ET569949

Description:
This change enables the localization team to localize the XML files for VxUL
logs.
--------------------------------------------------------------------------------
Etrack Incident = ET831189

Description:
NetBackup shutdown would not terminate parent jobs (nbgenjob). A change
was made to the Policy Execution Manager to terminate all parent jobs
with a 50 status (EC_client_aborted).

Workaround:
To resolve this issue, manually terminate all nbgenjob processes.
--------------------------------------------------------------------------------
Etrack Incident = ET857404

Description:
Changes were added to correct possible null pointer issues.
--------------------------------------------------------------------------------
Etrack Incident = ET851163
Associated Primary Etrack = ET849091

Description:
Changes have been added to ensure that send_mail() validates
all parameters it receives.
--------------------------------------------------------------------------------
Etrack Incident = ET515960

Description:
When a NDMP backup is initiated on Windows using a local NDMP drive, and if
a write-protected tape is grabbed, the backup will hang and continuously
mount and unmount the same write-protected tape.

Workaround:
To avoid this issue, do not put a write-protected tape in the media pool.
--------------------------------------------------------------------------------
Etrack Incident = ET866302 ET893368

Description:
The catalog cleanup process will not run to completion because it yields to
a catalog backup. If the cleanup process is long or if catalog backups are
frequent, the cleanup will not be able to delete expired images.

This maintenance pack contains a fix that enables catalog cleanup and
catalog backup to run in parallel. If a cleanup operation runs when a hot
catalog backup is in progress, it might delete images that were sent to
bpbkar earlier (in its image directive list), and cause the hot catalog
backup to finish with a partial success. This fix detects this situation
and returns the right error code to bpbkar.

The cleanup and catalog backup running in parallel is now the default
behavior. However, this can be disabled by creating a file called
"CLEANUP_WAIT_FOR_CATBKUP" in netbackup/db/config (for UNIX) and
\NetBackup\db\config (for Windows).

This fix also enables images to be expired and deleted using bpexpdate
even when a hot catalog backup is in progress.

Workaround:
To resolve this issue, disable hot catalog backups to allow cleanup to
run to completion.
--------------------------------------------------------------------------------
Etrack Incident = ET808281

Description:
bpdbm incorrectly sets the PFI_TYPE to 0. It must check if the copy being
deleted is a Persistent Frozen Image (PFI) or not and set the PFI_TYPE to 0
(only when the copy being deleted is a PFI).
--------------------------------------------------------------------------------
Etrack Incident = ET802974
Associated Primary Etrack = ET802966

Description:
The read_files_file queries would fail with a status of 249 because bpdbm
had not received the flist_complete yet.
--------------------------------------------------------------------------------
Etrack Incident = ET862545
Associated Primary Etrack = ET862538

Description:
Importing NetBackup 5.0 NDMP images would fail with an error code 42
from db_end().
--------------------------------------------------------------------------------
Etrack Incident = ET863352
Associated Primary Etrack = ET863351

Description:
The command "bperror -d <start date/time> -e <end date/time>" would not
give the correct result when daylight time saving was involved.
--------------------------------------------------------------------------------
Etrack Incident = ET542191

Description:
The success_fail_msg function in nb/media/bpbackupdb.c is for an offline
catalog backup on online catalog backups.
--------------------------------------------------------------------------------
Etrack Incident = ET863358
Associated Primary Etrack = ET848205

Description:
Internationalization (I18N): An NDMP restore with a Japanese directory
name no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET578391

Description:
Incremental, TIR backups with move detection back up subdirectories as Full
backups.

Workaround:
To avoid this issue, do not use TIR with move detection for Incremental
backups.
--------------------------------------------------------------------------------
Etrack Incident = ET546825

Description:
An error <16> message was logged by bpbkar when no error occurred. Changes
have been made to correct any incorrect error severity codes.
--------------------------------------------------------------------------------
Etrack Incident = ET894354
Associated Primary Etrack = ET859042

Description:
A Differential, Incremental backup would back up more data than expected
when initiating a Checkpoint Restart and TIR with move detection enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET926476

Description:
bporaexp no longer fails with a segmentation fault on X64 Windows systems.
--------------------------------------------------------------------------------
Etrack Incident = ET965811
Associated Primary Etrack = ET964501

Description:
Duplication (with multiplexing preserved) hangs for multiplexed TIR
images when using NetBackup 6.0 MP4.

Workaround:
To resolve this issue, do not preserve multiplexing when duplicating,
or do not use multiplexing. In addition, this may slow down performance.
--------------------------------------------------------------------------------
Etrack Incident = ET894201
Associated Primary Etrack = ET840906

** Description:
There are some rare instances when directory names do not get backed up.
For example, having C:\Data\Lindstrasse and C:\Data\LindstraÃ?e in the
file list will result in backing up only the first entry in the list.

Workaround:
To resolve this issue, back up C:\Data so that both directories will be
backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET894211
Associated Primary Etrack = ET840780

Description:
For backups that contain files or directory pairs such as 'Strasse' and
'StraÃ?e', only 'Strasse' would be displayed in the BAR user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET962923

Description:
NetBackup Service Layer (nbsl) no longer core dumps during install,
sched_bkup, and uninstall tests.
--------------------------------------------------------------------------------
Etrack Incident = ET965512

Description:
The VSS authorization tables were updated to include the new EMM interfaces.
--------------------------------------------------------------------------------
Etrack Incident = ET973073
Associated Primary Etrack = ET971052

Description:
The vlt_end_notify script always reports an exit status of 0, no matter
what the actual exit status is. A fix has been made that passes the
correct exit status value to vlt_end_notify script.
--------------------------------------------------------------------------------
Etrack Incident = ET973985
Associated Primary Etrack = ET931484

Description:
Multiplexed SAP backups that were using (Standard) AES-128 Encryption
would fail with the following error: "ERR - backup failed 49 <client
did not start>".
--------------------------------------------------------------------------------
Etrack Incident = ET974342
Associated Primary Etrack = ET972826

Description:
A change has been made to ensure that a non-streamed, Windows open file
backup, runs the right schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET973638

Description:
Added support for compressed backups to Oracle & MSSQL.
--------------------------------------------------------------------------------
Etrack Incident = ET967050
Associated Primary Etrack = ET965273

Description:
Running deferred ejects for all vaults fail if vlteject.mstr and
SID (session ID) directories are out of sync. Vault cross checks all the
SID entries of the vlteject.mstr file. If it fails to find any SID, it
exits with a status 12. This fix, identifies SIDs that are out of sync
(or missing) with respect to vlteject.mstr, and it ignores such SIDs
during the vault eject operation.

Workaround:
To resolve this issue, manually remove entries of missing SIDs in the
vlteject.mstr file.
--------------------------------------------------------------------------------
Etrack Incident = ET915448
Associated Primary Etrack = ET915442

Description:
Adding an operating system (OS) group to a Role in NBAC does not give the
Appropriate permissions to members of that OS group.
--------------------------------------------------------------------------------
Etrack Incident = ET602621

Description:
Provided X64 (AMD64/EM64T) support for SAP on the X-64 Windows client.
--------------------------------------------------------------------------------
Etrack Incident = ET964515
Associated Primary Etrack = ET964514

Description:
This maintenance pack contains an upgrade to Sun LibAttach version 1.4.2 for
ACS robotics. This enables ACS robotics support for Windows X64 server
support.
--------------------------------------------------------------------------------
Etrack Incident = ET964515
Associated Primary Etrack = ET964514

Description:
Upgraded to Sun LibAttach version 1.4.2 for ACS robotics. This
enables ACS robotics support for Windows X64 server support.
--------------------------------------------------------------------------------
Etrack Incident = ET928695 ET492823
Associated Primary Etrack = ET928687

Description:
In certain cases, PBX logs were not being pruned according to settings in
/etc/vx/VxICS/icsul.conf.

Additional Notes:
UNIX PBX runtime components are being updated in this maintenance pack along
with the NetBackup Server.
--------------------------------------------------------------------------------
Etrack Incident = ET831965

Description:
NetBackup 6.0 disk staging storage unit�s high water mark (HWM) and low
water mark (LMW) are not changeable for an application cluster
(AppCluster) configuration. Currently, the AppCluster Configuration does
not have a NetBackup version so it is treated as a pre-NetBackup 6.0
storage unit, where the HWM is set to the previous behavior of 100 percent
and a LWM did not exist, therefore it is set to a default value of
80 percent. Both of these settings were new in NetBackup 6.0 and are not
configurable in pre-NetBackup 6.0 versions.

Workaround:
The AppCluster version number must be at the same version level as
the servers that make up the AppCluster. To resolve this issue, the
user should manually enter the NetBackup version number for the
AppCluster using the nbbemmcmd command. In addition, all of the
NetBackup servers in the AppCluster should be at the same, specified
version.

As an example, you would use the following command on the master
server to update the NetBackup version number for an AppCluster.

nbemmcmd -updatehost -machinename virtual_name -machinetype app_cluster
-netbackupversion 6.0

where virtual_name is the virtual name of the application (AppCluster).
--------------------------------------------------------------------------------
Etrack Incident = ET991906

Description:
Changes were made to ensure that a Vault operator could operate properly in
an NBAC environment.
--------------------------------------------------------------------------------
Etrack Incident = ET991647
Associated Primary Etrack = ET990896

Description:
After installing the BMR boot server to a Windows system with a
NetBackup 6.0 MP maintenance pack installed, and then performing a repair
on the pack to apply the BMR boot server binaries, the user should copy
the binaries to the correct directory location. If a NetBackup
installation was installed to a alternate location, the repair will not
correctly apply the patch binaries to the alternate location.

Workaround:
Again, to resolve this issue, copy the binaries, after performing the
"repair" option to the correct directory.
--------------------------------------------------------------------------------
Etrack Incident = ET992147

Description:
NetBackup, while running under NBAC, experienced authorization checks that
were skipped for some operation of corba daemons. This could have enabled
an unauthorized user to perform some privileged operations in NBRB.
--------------------------------------------------------------------------------
Etrack Incident = ET992949

Description:
V_snprintf uses vsnprintf to implement a fix for uncommon strcat usage. On
the Windows platforms, vsnprintf did not guarantee a null terminated buffer.
Specifically, this was true if the data in the buffer exactly filled the
destination without leaving room for the null termination. In this case,
the buffer would not be null terminated and the function would crash when
V_strlcpy is called.
--------------------------------------------------------------------------------
Etrack Incident = ET990034

Description:
When an inline tape copy job with multiplexed protocol was resumed after a
checkpoint, the job was restarted instead of resumed.
--------------------------------------------------------------------------------
Etrack Incident = ET995110
Associated Primary Etrack = ET983973

Description:
Because of changes in Oracle10gR2, multi-streamed backups will restore using
one stream.

Workaround:
To avoid this issue, use the RMAN syntax: "SET PARALLELMEDIARESTORE OFF;".
--------------------------------------------------------------------------------
Etrack Incident = ET995846

Description:
A change was made to disable alternate buffer backups when compression is
in use.
--------------------------------------------------------------------------------
Etrack Incident = ET994229
Associated Primary Etrack = ET993986

Description:
A condition existed that caused failed jobs to exceed a configured number of
tries.
--------------------------------------------------------------------------------
Etrack Incident = ET992223

Description:
When checkpoint restart was enabled, and the "continue" flag was set in
the schedule, bptm terminated the copy when an error on that copy
occurred. When the copy terminates, for multiplexing, no more jobs were
scheduled for the multiplexed group. However, in rare cases there is a
timing window where jobs may have already been started but not yet
processed by bptm. In this case, incomplete fragment cleanup occurred
for the failed copy.
--------------------------------------------------------------------------------
Etrack Incident = ET997861

Description:
Removed a line in flash_bridge.cpp that was inadvertently added to the file.
--------------------------------------------------------------------------------
Etrack Incident = ET997950
Associated Primary Etrack = ET984069

Description:
Oracle proxy copy incremental (CINC) backups are no longer running as full
Backups.
--------------------------------------------------------------------------------
Etrack Incident = ET992959
Associated Primary Etrack = ET993079

Description:
In some scenarios, the resource broker (RB) was orphaning resources that
were already marked to be released. This caused extra processing overhead
and communication overhead between nbrb and nbjm.
--------------------------------------------------------------------------------
Etrack Incident = ET999559

Description:
The pack installer will now log server system information such as EMMSERVER
(remote or local), media versus master server, and inactive cluster node.
--------------------------------------------------------------------------------
Etrack Incident = ET998728

Description:
The NetBackup version is now displayed in the nbemmcmd -listhosts -verbose
output.
--------------------------------------------------------------------------------
Etrack Incident = ET1000607

Description:
Symantec Code Repository Revision Tags was added to some files, to enable
better tracking.
--------------------------------------------------------------------------------
Etrack Incident = ET999754

Description:
If there were multiple copies of a backup, and a duplication was requested
for disk source copy 1 (or any disk copy other than the last), the
duplication might be started as a non-shared memory duplication. A shared
memory duplication is preferable for performance reasons.
--------------------------------------------------------------------------------
Etrack Incident = ET1002385
Associated Primary Etrack = ET982979

Description:
Vault processing has been noted to have slowed down resulting in a
significant number of vault jobs remaining queued and then being
canceled due to preventing normal NetBackup operation.

EMM calls in Vault were observed to be taking longer time than
anticipated. As a fix, EMM calls were optimized as to fetch 1000
records/request. This should resolve the vault performance issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1001117

Description:
For Windows, added Sybase ASA service dependency to the NetBackup Resource
Broker.
--------------------------------------------------------------------------------
Etrack Incident = ET970398

Description:
In an NBAC setup, a volume configuration that uses the user interface wizard
would fail with an error 39.
--------------------------------------------------------------------------------
Etrack Incident = ET1008736
Associated Primary Etrack = ET966429

Description:
bpstart_notify would not get executed if the dos 8.3 pathname option was
turned off on NTFS partitions. After disabling dos 8.3 pathnames,
bpstart_notify would not run. bpbkar32.exe reports the bpstart_notify script
has started and ended, but the contents would not be executed.
--------------------------------------------------------------------------------
Etrack Incident = ET1005425

Description:
NetBackup pem would consistently terminate when an orphan job existed.
--------------------------------------------------------------------------------
Etrack Incident = ET1003200
Associated Primary Etrack = ET1003184

Description:
bprecover would crash during a recovery of a BMR database file that exceeded
2GB in size.
--------------------------------------------------------------------------------
Etrack Incident = ET990295

Description:
During multi-eject operations the vmchange program would return a
status code 0 (success) if another eject operation was in progress.
vmchange now returns a status code 223 (STATUS_ROBOT_BUSY) when another
eject operation is in progress. This problem primarily affected vault
eject operations.
--------------------------------------------------------------------------------
Etrack Incident = ET997925

Description:
Stream discovery would ignore the preprocess interval and use the default of
four hours. A change was made so that the preprocess interval is now passed
from Policy Execution Manager to the Job Manager and then to the parent job
(nbgenjob) on the command line using the -preprocessInterval option.
--------------------------------------------------------------------------------
Etrack Incident = ET1012795 ET1003554

Description:
Multiplexed SAP backups that use (Standard) AES-128 Encryption would fail
with the error, "ERR - backup failed:49 <client did not start>".
--------------------------------------------------------------------------------
Etrack Incident = ET1013849

Description:
The host list would be empty if a cluster node name was given instead of
virtual cluster name.
--------------------------------------------------------------------------------
Etrack Incident = ET1003608

Description:
Duplication to an FSE Nearstore storage unit failed if the
�stsdeletefiles process returned a status 1 (which is valid). A change
has been made that allows a duplicate to complete successfully if a
status 1 is encountered from -stsdeletefiles.
--------------------------------------------------------------------------------
Etrack Incident = ET1002794
Associated Primary Etrack = ET1004537

Description:
A change has been made to provide support for overriding the schedule that
is specified in the utl file for an SAP standard backup.


Additional Notes:
This change includes two environment variables, SAP_SCHED and
SAP_SNC_SCHED.

SAPSCHED: Use this variable for standard backups. If a user wants to
override the schedule that is specified in the utl file, he/she must
to specify SAP_SCHED. This will be the Application backup schedule.
In addition, it will also be used for future enhancements of an
advanced backup. [Currently, the behavior of SAP_SCHED is same as
NetBackup 6.0GA and earlier].

SAP_SNC_SCHED: For advanced backups you must specify the SAP_SNC_SCHED.
This will be the Automatic schedule [Automatic Full, Automatic
Differential Incremental, or Automatic Cumulative Incremental backup
type].

For detailed information on how to use the SAP_SNC_SCHED variable,
refer to the following Tech-Note on the Symantec Support web site.
http://entsupport.symantec.com/docs/282337
--------------------------------------------------------------------------------
Etrack Incident = ET1013509

Description:
A change was made to disable sorting on the Elapsed time and Active elapsed
time columns.
--------------------------------------------------------------------------------
Etrack Incident = ET1013882

Description:
Manual configuration of ACS libraries does not always record the library
serial number.
--------------------------------------------------------------------------------
Etrack Incident = ET1014147

Description:
In certain conditions a robotic daemon would become "UP" even though the
device monitor showed drives under AVR control.
--------------------------------------------------------------------------------
Etrack Incident = ET1010767
Associated Primary Etrack = ET990884

Description:
Immediate backups jobs would not initiate properly causing nbpem to return
the following statuses: msgsndd status = 0; send status 0; and bprd exit
status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET1016131

Description:
A change was made to implement support for Instant Recovery with Windows
FlashBackup policies.
--------------------------------------------------------------------------------
Etrack Incident = ET1014974
Associated Primary Etrack = ET892850

Description:
Backups written by 64-bit Linux servers were unreadable by non-64-bit Linux
servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1012144 ET1016961

Description:
Added support for a new Automated Cartridge System (ACS) vendor media and
drive type.
--------------------------------------------------------------------------------
Etrack Incident = ET1011704
Associated Primary Etrack = ET1015054

Description:
The robotic control daemon would not handle robots with more than
128 drives.
--------------------------------------------------------------------------------
Etrack Incident = ET1016602

Description:
During a backup, the path of the database link was not printed
in the bpbkar logs. The following message was written in the
bpbkar log.

13:02:41.761 [270564] <4> NBLN_DbBackupOpen(): INF �
/opt/lotus7/notesdata/mail/linkdb.nsf is a database link. Updated
size with the actual size of database link.
was wrongly printed as
12:43:47.569 [282760] <4> NBLN_DbBackupOpen(): INF -
NBLN_DbBackupOpen() is a database link. Updated size with the
actual size of database link.
--------------------------------------------------------------------------------
Etrack Incident = ET1015612

Description:
Corrected an issue that would not allow you to write to disk and resulted
in an error code 84 (media write error).
--------------------------------------------------------------------------------
Etrack Incident = ET1018156 ET1016311
Associated Primary Etrack = ET1008244 ET1011211

Description:
The window checking routine would sometimes schedule jobs to run
multiple times in one window, or even skip a window.
--------------------------------------------------------------------------------
Etrack Incident = ET925285
Associated Primary Etrack = ET834682

Description:
Internationalization (I18N) issue: An issue existed that caused the content
of a notification e-mail to illegible.
--------------------------------------------------------------------------------
Etrack Incident = ET1017152
Associated Primary Etrack = ET1013059

Description:
If there are transient environmental hostname lookup issues, nbrb may
core dump near \"__nscd_get_map_ref\".
--------------------------------------------------------------------------------
Etrack Incident = ET1019073
Associated Primary Etrack = ET988955

Description:
TIR files that were than 2GB were not able to be read because the size was
stored in a 32-bit integer and the math used to turn that into a 64-bit
integer caused a large negative value to be stored on some platforms. This
maintenance pack contains a fix that contains explicit casts at appropriate
junctures. This issue was found on a Nearstore storage unit but would have
affected any disk storage unit if TIR was being used.
--------------------------------------------------------------------------------
Etrack Incident = ET1009036
Associated Primary Etrack = ET936732

Description:
A change was made to correct an nbpem core dump issue that occurred because
a null pointer was being passed to libc::strcmpstack.
--------------------------------------------------------------------------------
Etrack Incident = ET839666
Associated Primary Etrack = ET833118

Description:
VxSS is not compatible with wide characters for usernames or machine names.
This causes bpnbaz -setupsecurity and user interface logins to fail on
non-English installations on Windows platforms.

Workaround:
To avoid this issue, create a user with standard ASCII characters for
the username.
--------------------------------------------------------------------------------
Etrack Incident = ET1020129
Associated Primary Etrack = ET1003895

Description:
It is possible for an NDMP restore to be successful and still produce a
status code 83 when media is write protected and spans media. The bptm
log will contain a messagesimilar to the following:

15:51:14.479 [6272.8404] <16> open_ndmp_device: cannot open ndmp device
nrst07a, error code 11 (NDMP_WRITE_PROTECT_ERR)

Workaround:
The restore completes successfully, so you can ignore the error status.
Or you can unmark the tape to make it write protected.
--------------------------------------------------------------------------------
Etrack Incident = ET1020196
Associated Primary Etrack = ET1003986

Description:
A change has been made to correct an unexpected termination of the NetBackup
Job Manager service.
--------------------------------------------------------------------------------
Etrack Incident = ET1016884

Description:
Corrected the use of ejecting to the "any" cap (a function used by Vault)
when ejecting to ACS robotics. Also corrected use of -w option when
ejecting to ACS robotics from the command line.
--------------------------------------------------------------------------------
Etrack Incident = ET1015650

Description:
Lotus Notes user-directed backups were failing if the notes.ini path
specified through the user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1006573

Description:
A change was made so that the Managing -> Job Policies -> Details, user
backup & user archive policies are no longer shown twice.
--------------------------------------------------------------------------------
Etrack Incident = ET1024918

Description:
Changes were added to resolve an intermittent pem core dump issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1021373

Description:
Corrected an issue that caused FlashBackup Windows single-file restores to
fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1020081

Description:
A change was added so that when printDueJobs accesses the work list it will
lock the list to avoid potential issues with other threads trying to access
the work list.
--------------------------------------------------------------------------------
Etrack Incident = ET995592

Description:
Conversion of the policy include file-list entries failed resulting in
blank entries. A change was made to the nbproxy conversion code to use
language codeset setting of "utf8" for HP platforms, otherwise "UTF-8" for
all other platforms to prevent the conversion from returning an error saying
the input was invalid.
--------------------------------------------------------------------------------
Etrack Incident = ET1024066

Description:
Corrected a bpdm core dump that occurred with V_strverify on a Linux IA-64
System.
--------------------------------------------------------------------------------
Etrack Incident = ET1023729
Associated Primary Etrack = ET1027068

Description:
A storage unit update operation (from the NetBackup-Jave Administration
Console) will fail if the user is logged into the system using the node name
(not the virtual name).

Workaround:
To resolve this issue, use the virtual name.
--------------------------------------------------------------------------------
Etrack Incident = ET1026332
Associated Primary Etrack = ET1018020

Description:
A restore attempt, using a duplicated copy of a standard backup image
that was duplicated using NDMP attached tape drive, would fail with exit
status 25 (cannot connect on socket). The failure occurred because bpdm
was started instead of bptm.
--------------------------------------------------------------------------------
Etrack Incident = ET1028083

Description:
The ltid reports that the user had configured more drives than they were
licensed for, when they were using multiple drive paths.
--------------------------------------------------------------------------------
Etrack Incident = ET1028405

Description:
A change was made to ensure that the Windows FlashBackup Policy Type is
disabled when the Advanced Client license key is not installed.
--------------------------------------------------------------------------------
Etrack Incident = ET1030436

Description:
DB2 V9 can only be enumerated if it was installed in the default
location. A change was included that adds support to enumerate all
installations of DB2.
--------------------------------------------------------------------------------
Etrack Incident = ET1029379
Associated Primary Etrack = ET971543

Description:
For FlashBackup Windows incremental backups, the extents for named streams
associated with directories were not being examined and put in the bitmap.
--------------------------------------------------------------------------------
Etrack Incident = ET858201
Associated Primary Etrack = ET850921

Description:
A hot catalog backup with a large number of image catalog entries
can run out of memory.

Workaround:
For a temporary fix to the memory issue, contact Symantec Support and inquire
about Emergency Engineering Binaries (EEBs) that are available for this issue,
or perform an offline backup, or a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1028058

Description:
An incorrect group and ownership on a libdbjodbc9.so symbolic link file has
been corrected.

Additional Notes:
This change only affects HP-UX on RISC hardware.
--------------------------------------------------------------------------------
Etrack Incident = ET1026006

Description:
Under nb/idl/NBPolicyTypes.idl, many new fields were added for
NetBackup 6.5. This created problems for NOM 6.5 to support 6.0 MP5
masters. To avoid this issue, Symantec added the new fields in 6.0 MP5
as reserved fields which will resolve this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1029007
Associated Primary Etrack = ET1026162

Description:
Oracle stream-based backups would intermittently fail with an error 25.
--------------------------------------------------------------------------------
Etrack Incident = ET1028169

Description:
NetBackup will now be shutdown in runlevel 1 on Solaris systems.
--------------------------------------------------------------------------------
Etrack Incident = ET1032876
Associated Primary Etrack = ET963719

Description:
Changes were made to correct a Dr Watson error caused by bpbkar.

Bpbkar would cause a Dr Watson error on the client while backing up
encrypted files. The job consistently failed with an exit status 13
while backing up the following directory: E:\QuickBase\server\dbs\.

Files that were backed up were continuously changing. A third party
application would capture changes made from the end user (web user)
to a .delta file, the delta file was then written to the files in the
directory, "E:\QuickBase\server\dbs\", only after the user had closed
the web application. The .delta files were continuously changing, and
the changes made to the directory were approximately 10 gigabytes
an hour.
--------------------------------------------------------------------------------
Etrack Incident = ET1028004
Associated Primary Etrack = ET1021953

Description:
A change was added to remove BLI clones that would sometimes remain on a
system after a failed Oracle BLI backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1035215

Description:
DB2 V9.1 backups failed when a template was used in a policy's backup
selection.
--------------------------------------------------------------------------------
Etrack Incident = ET1026986
Associated Primary Etrack = ET1005324

Description:
Cleaning jobs that were initiated because of a TapeAlert or frequency would
fail if they did not complete in six minutes.
--------------------------------------------------------------------------------
Etrack Incident = ET1035288

Description:
NetBackup 6.0 does not provide a way to perform device monitor queries for a
single media server. Users must sift through all servers' output for the
data needed. This maintenance pack adds the option -hostdevmon to the
vmoprcmd command line to provide a single server's device state.
--------------------------------------------------------------------------------
Etrack Incident = ET1040339
Associated Primary Etrack = ET1027138

Description:
Increased the drive ready timeout for TLD drives to 14 minutes to
incorporate a worst case scenario of 14 minutes for LTO drives in
an effort to remove bad media.
--------------------------------------------------------------------------------
Etrack Incident = ET1039797

Description:
When a full data directory is restored, the recovery was failing due to a
truncation of the database name.
--------------------------------------------------------------------------------
Etrack Incident = ET1041415

Description:
DB2 stream-based log restores would fail if the policy used to perform the
backup did not exist.
--------------------------------------------------------------------------------
Etrack Incident = ET1038347
Associated Primary Etrack = ET996144

Description:
After a WOFB backup, bpbkar32 would clean up an active
FlashBackup- Windows snapshot - because PEM did not send the
SET SNAP_ID for snapshots that should be retained on the client.

Workaround:
To resolve this issue, reschedule the backups of the C: and D: drives so
that they start -and- complete at non-overlapping time periods
However, for some customers this is not practical because they may have
volumes that are in the range of 800GB ~ 1TB. In addition, some of their
servers may have more than one volume that needs to be protected using
Flashbackup

In this circumstance, Symantec suggests the customer sets the priority
of the C: drive backup to a higher value than the Flashbackup policy;
and then for the affected clients that are part of their Flashbackup
policies, using the Master Server Host Properties > Client Attributes >
Set Max jobs/client option and setting it to 1.
--------------------------------------------------------------------------------
Etrack Incident = ET1041220
Associated Primary Etrack = ET1039034

Description:
After BPCD passes the following locale:
<2> set_all_locale_rqst: setting value: LC_ALL=English_United States.1252

The following error occurs with BPDM:

bpdm: ignoring unrecognized media manager option States.1252

Corrected bpcd to quote the locale that is being passed.
--------------------------------------------------------------------------------
Etrack Incident = ET1039117
Associated Primary Etrack = ET1038317

Description:
"bpmedia -movedb" starts bptm on the old server to move the media
database. If the old server and the new server are at NetBackup 6.0
(or post 6.0), then there is no need to start bptm. All the
operations can be done in bpmedia. This also helps the scenario
where one of the media server is offline or de-commissioned (and
all the steps for de-commissioning the media server are not followed).
--------------------------------------------------------------------------------
Etrack Incident = ET1044853
Associated Primary Etrack = ET1028211

Description:
Windows servers no longer ignore the media mount timeout on standalone
drives.
--------------------------------------------------------------------------------
Etrack Incident = ET1042448

Description:
Snapvault backups are running has snapshot backups on the filer,
under the volume's .snapshot directory and no "sv" is present in
the snapshot name, for example:

NAS+NBU+PFI+steeljacket.min.veritas.com+snapvault+sr+vol1+
2007.05.04.14h37m35s
--------------------------------------------------------------------------------
Etrack Incident = ET992572
Associated Primary Etrack = ET892420

Description:
The bppllist -allpolicies -U command would not return all policies.
In addition, when recreating the issue, an application fault
against bppllist was also found.
--------------------------------------------------------------------------------
Etrack Incident = ET1050190

Description:
Changes were made to correct the NetBackup 6.0 MP5 NetWare
build.
--------------------------------------------------------------------------------
Etrack Incident = ET1050372
Associated Primary Etrack = ET1047809

Description:
Sybase 11.9.x backups no longer fail on HP-UX 11.00 after upgrading to
NetBackup 6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET1043639

Description:
Restoring files on a second tape of an NDMP backup would cause a failure.
--------------------------------------------------------------------------------
Etrack Incident = ET1046813

Description:
Online catalog backup was failing with a status 50 when writing to a
password-protected DR path in an environment with NBAC installed.

Workaround:
To avoid this issue, store the DR file in a path which the running NetBackup
bpbdm process has write access to without changing credentials.
--------------------------------------------------------------------------------
Etrack Incident = ET1047911

Description:
A description of the new '-copy' option is missing from the bprestore
command line usage.
--------------------------------------------------------------------------------
Etrack Incident = ET1050488

Description:
Corrected an issue that caused ltid to fault after it was started.
--------------------------------------------------------------------------------
Etrack Incident = ET1050393
Associated Primary Etrack = ET1036542

Description:
ACS robot pre-eject operations sometimes show volumes that are
NOT_IN_LIBRARY when they actually are. This is due to a buffer
length problem in the acsd robotic daemon. This primarily affects
Vault ejects to ACS robots.
--------------------------------------------------------------------------------
Etrack Incident = ET1041952
Associated Primary Etrack = ET992544

Description:
Changes were made to address a backint/bprm/bpkar/brbackup handshake
failure that would occur at end of a backup. An explanation of the
problem follows.

A backup may sit in the scheduler queue for more than 25 hours. Then
over the next two hours it performs a successful backup of the data
files. The backup of each file involves a quiesce, backup, and
unquiesce. This sequence is successful for the datafiles. The quiesce
and backup of the control file is also successful.

- bpbkar shows a successful data transfer and request to take the
control file out of backup mode.
- bpbkar shows the completion of the job including client and
server status 0.
- bptm shows successful completion.
- bpbrm shows successful completion.

However, backint appears to have not yet received the #END or
UNQUIESCE for the control file. Hence when bpbrm.child exits, the
sockets to backint are removed and backint reports the loss.
--------------------------------------------------------------------------------
Etrack Incident = ET1052551

Description:
Intermittent issues were found when ejecting multiple CAP-fulls of
media with the latest ACSLS patch, PUT0701S.
--------------------------------------------------------------------------------
Etrack Incident = ET1051474

Description:
Some ACS_SDLT* media will not be mapped correctly to NetBackup media types
when specifying the mapping in vm.conf.
--------------------------------------------------------------------------------
Etrack Incident = ET1054463
Associated Primary Etrack = ET1039776

Description:
After changing the bp.conf SERVER entry from short name to FQDN
(or vice versa) and when performing a hot catalog backup with Vault,
the Vault job will fail with a status 294, even though the catalog
backup was successful.

Now, instead of using gethostname() results when vault performs a
validation, the client name (as configured in the policy) will be
used.

Workaround:
UNIX ONLY: In the imageDB directory, create a symbolic link between
FQDN and short names.
--------------------------------------------------------------------------------
Etrack Incident = ET1053444

Description:
A change was made that corrects a crash using bpplschedrep.
--------------------------------------------------------------------------------
Etrack Incident = ET1052430
Associated Primary Etrack = ET1032378

Description:
Added a fix to correct an nbjm crash in TAO_Transport::handle_input.
--------------------------------------------------------------------------------
Etrack Incident = ET1018993

Description:
On some SuSE 10 servers, when NetBackup asks the system if
it is the name listed as the EMM Server in the bp.conf file
at boot time, it incorrectly answers no. This correction asks
several times and usually the second attempt gives the correct
answer.

This causes a 55 second delay, with starting NetBackup daemons,
on SuSE 10 servers that are not MM Servers.

Workaround:
To resolve this issue, run the following start command after a
system has rebooted.

/usr/openv/netbackup/bin/goodies/netbackup
--------------------------------------------------------------------------------
Etrack Incident = ET1060972
Associated Primary Etrack = ET1038232

Description:
When Enterprise Vault performs backups to NetBackup using the
VxBSA file APIs, the backups can fail. Enterprise Vault posts
an event error entry saying Failed to send file (error 00000003:
System detected error, operation aborted.). Check the NetBackup
Activity Monitor.

Examination of the exten_client debug log shows that following
type of error being logged.
07:13:13.973 [9820.5196] <16> bsa_WriteFileList: ERR - filelist
file <C:\Program
Files\VERITAS\NetBackup\Logs\user_ops\dbext\logs\
vxbsa.1177038793.9820.5196.files.1> open() failed: Errno=24:
<Too many open files>
--------------------------------------------------------------------------------
Etrack Incident = ET1056147

Description:
An SQL Server move would fail for a snapshot backup when the
database included a full text catalog. This problem occurred
with SQL2005. The dbclient log contained the following data.

USER - Failed to find move object <sysft_catalog1> in the object
descriptor
--------------------------------------------------------------------------------
Etrack Incident = ET1018093

Description:
An error occurred on a Windows setup that caused a failure to
occur when copying files.
--------------------------------------------------------------------------------
Etrack Incident = ET1047888
Associated Primary Etrack = ET1041180

Description:
The NDMP jobs' drives were sometimes pre-empted with a local
or incorrect drive path.
--------------------------------------------------------------------------------
Etrack Incident = ET1063773
Associated Primary Etrack = ET1063750

Description:
A crash in nbemm would occur if an inventory was attempted
while the database server was down. This would easily happen
if a site was performing a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1064798

Description:
A DB2 restore now has the ability to redirect a DB2 database
to a different owner from the original owner (both owners
being from the same group). A new backup of the source DB2
database is required so the correct group permission is on the
image to allow the alternate user to perform a restore to the
new instance, or database.
--------------------------------------------------------------------------------
Etrack Incident = ET1065639
Associated Primary Etrack = ET1064866

Description:
The bmrd process on the master server would sometimes core dump or hang
indefinitely while importing a Solaris client configuration that had
Solaris Volume Manager database replicas configured.
--------------------------------------------------------------------------------
Etrack Incident = ET1042568

Description:
An SQL server database clustered with VCS may fail during a
backup if there are more than one clustered SQL Server instances
that map to the same physical host.

Workaround:
In the above case, if the backup fails, check the batch file that is
generated by the NB-MSSQL user interface. If it does not specify
BROWSECLIENT <virtual-server>, then insert it into the batch file.
Then rerun the batch file manually.

Additional Notes:
This was a latent problem that existed in 5.0/5.1/6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET1066935
Associated Primary Etrack = ET1062088

Description:
bpdbm crash can occur, during a recovery, if a damaged image
file exists prior to the recovery.

Workaround:
To avoid this issue, manually remove all damaged image files
before attempting a recovery.
--------------------------------------------------------------------------------
Etrack Incident = ET1066885

Description:
Listing storage unit groups were leaking memory. Changes were
added to resolve the memory leaks.
--------------------------------------------------------------------------------
Etrack Incident = ET1067176
Associated Primary Etrack = ET1001827

Description:
Jobs are not being cleaned from job database even after the
KEEP_JOBS_HOURS was run.
--------------------------------------------------------------------------------
Etrack Incident = ET1067996
Associated Primary Etrack = ET1058482

Description:
Changes were made to resolve memory leak issues in NBJM
and NBPEM.
--------------------------------------------------------------------------------
Etrack Incident = ET1070595

Description:
NOM no longer creates multiple NBProxy processes when there
is no job activity.
--------------------------------------------------------------------------------
Etrack Incident = ET1072094

Description:
If you enter "bpdown" (without the -f argument) on a Windows server,
it would prompt you with the following question:

"Do you wish to proceed?". If you press "n" services will not
be terminated."

If you pressed "n", the nbproxy processes were terminated even though
the the other services are not. This left NetBackup in an
unpredictable state.

A change was made that ensures the nproxy processes are not terminated
if "n" is pressed during bpdown.
--------------------------------------------------------------------------------
Etrack Incident = ET1072865

Description:
The NetBackup service layer (NBSL) would take a long time to initiate
proxies when the initial data load is on from NOM. A change has been
made that prevents NBSL from starting the proxies when NOM's initial
data load is on.
--------------------------------------------------------------------------------
Etrack Incident = ET1073038

Description:
An NetBackup EMM memory leak was detected in the xxxFetch()
implementation causing EMM to consume more memory over time.

Workaround:
To resolve this issue, restart the EMM process.
--------------------------------------------------------------------------------
Etrack Incident = ET1062791

Description:
Corrected an issue where the NetBackup Job Manager (NBJM) could
not be terminated and it had to be killed.
--------------------------------------------------------------------------------
Etrack Incident = ET1061742
Associated Primary Etrack = ET1058482

Description:
Added changes to correct a memory leak found in the NetBackup
policy execution manager (PEM).
--------------------------------------------------------------------------------
Etrack Incident = ET1066381
Associated Primary Etrack = ET1066374

Description:
The INCR frequency schedule would run multiple times within a
window with an incorrect snapid.


--------------------------------------------------------------------------------
Etrack Incident = ET1068635

Description:
The NetBackup service layer (NBSL) crashes on an HP-UX system.

Workaround:
To avoid this issue, default catch blocks were added to handle
all other exceptions in the Proxy client.
--------------------------------------------------------------------------------
Etrack Incident = ET1075834

Description:
An issue exited that caused jobs to remain queued when a
196 error should have occured.
--------------------------------------------------------------------------------
Etrack Incident = ET1076967
Associated Primary Etrack = ET1033590

Description:
A crash would sometimes occur in bpdbm when the cleanup process
was cleaning one of the images of a duplication, where the
duplication had failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1076060

Description:
The NetBackup PEM would terminate because of a timeout to the
nbproxy for getLastBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET1078998
Associated Primary Etrack = ET993531

Description:
The NetBackup Service Layer (NBSL) will not stay running and the
following error is produced.

Windows error 1063 - Windows SCM unable to start it as a service.

Workaround:
To avoid this issue, increase the service-registration timeout
from the Windows-registry.
--------------------------------------------------------------------------------
Etrack Incident = ET1078584

Description:
Running backups that have streaming enabled (and perform
incremental backups whose file list changes) may encountered
the following problem.

When stream discovery is done and some existing streams are shuffled
because new files are being added or existing streams being deleted,
the streams files are shuffled but the "lastbackup" time is saved for
the streams that remain. Therefore, when a new stream maps to a
preexisting stream with a date of zero (since there was no prior
backup) you want to avoid doing a query for "lastbackup" with that
stream number because it will return the "lastbackup" time for the
stream that was shuffled or deleted. If you avoid doing a query
for "lastbackup" when the date is zero you also keep the streams
from shuffling and the query returning a "lastbackup" time from a
different stream.
--------------------------------------------------------------------------------
Etrack Incident = ET1079265
Associated Primary Etrack = ET1075693

Description:
There were situations where the SAP data files to be backed up
were skipped during the backup. The backup status was still
reported as being successful (status 0) in NetBackup and as being
saved in the brbackup detail log. This backup set would not be
usable in an SAP/Oracle DR situation.

A message similar to the following may appear in the bpbrm log:
<4> bpbrm main: from client xyz: TRV - object not found for
file system backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1079359
Associated Primary Etrack = ET899380

Description:
A change was added that corrects a Status 805 error condition on
resubmitted, failed, multiple-data stream child jobs using snapshots.
--------------------------------------------------------------------------------
Etrack Incident = ET1079420

Description:
BasicDisk backups to filesystems with block sizes greater than 8K may fail.

Workaround:
Lower the block size of the filesystem to a value of 8K or less.
--------------------------------------------------------------------------------
Etrack Incident = ET1079272
Associated Primary Etrack = ET1049382

Description:
AIX master servers were unable to restore Windows Flashbackup
images. This was because of a problem linking the VxMS libraries
in the AIX compile. A change has been added to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1081508
Associated Primary Etrack = ET1075693

Description:
A fix was added that resolves an issue where SAP backups may
report success even though some of the data files being backed
up were skipped.
--------------------------------------------------------------------------------
Etrack Incident = ET1083381

Description:
Policy Execution Manager would core dump when reading a policy because
of a configuration change event.
--------------------------------------------------------------------------------
Etrack Incident = ET1092076

Description:
NOM receives data from NBSL regarding changes in policy, storage units,
processes and services information, and so forth through events. When
the nbnos process is terminated, NBSL cannot deliver these events to NOM.

After restarting the nbnos process, the event delivery mechanism should
resume and NOM should continue to get data from NBSL, but it fails.
--------------------------------------------------------------------------------
Etrack Incident = ET1092060

Description:
When invoking the Device Configuration Wizard from the NetBackup-Java
Administration Console, a dialog box named "Device Configuration
Wizard - Initialization" shows the error "unknown error".
--------------------------------------------------------------------------------
Etrack Incident = ET1095578
Associated Primary Etrack = ET1094524

**Description:
If bpbrm/bptm terminates abnormally while executing multiple jobs and
another job is added to this multiplexed group by the Resource Broker, it is
possible that a data loss could occur.
--------------------------------------------------------------------------------
Etrack Incident = ET860960 ET862556

Description:
Corrected a potential performance issue in VxUL when deleting a large
number of log files in the VxUL log directory. bprd would
automatically remove the old VxUL log files at Midnight. If there
were a large number of log files it would take many hours for bprd to
remove them.




=========
NB_60_4_M
=========

Etrack Incident = ET633295 ET617152 ET801824

Description:
Upgraded the version of Veritas Unified Logging (VxUL) to 1.3.7.2 to
enable users to recycle VxUL logs.
--------------------------------------------------------------------------------
Etrack Incident = ET538815

DescriptionThe following two issues have been resolved:

- Systems that are up more than three days, no longer become unresponsive
on MSCS systems running NetBackup 6.0.
- Changes have been made to nbemm and nbrb processes to eliminate core
dumps when running with NBAC.
--------------------------------------------------------------------------------
Etrack Incident = ET831404

Description
The BAR user interface failed to connect to Oracle 10.1.0.5.0
instances on UNIX platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET796423

Description:
Remote NDMP performance for NetBackup 6.0 was less than half that of
NetBackup 5.x. This issue appeared to affect UNIX more than Windows, as
Windows performance was much closer to NetBackup 5.x rates. Also, this was only
a problem with GigE and high performance tape drives.

This fix brings the Remote NDMP performance rates closer to that of previous
NetBackup versions for both UNIX and Windows.

Additional Notes:

You may also need to increase the number of buffers to 16 or 32. Use the
following to add the number of buffers desired to the file:
/user/openv/netbackup/db/config/NUMBER_DATA_BUFFERS

If you have multiple NICs and want to choose which is to be used for
the data connection to the filer, (for example, if one of them is not
1000Mbps) create the following file:
/user/openv/netbackup/db/config/ndmp.cfg
With the following line:
NDMP_DATA_CONNECTION_HOST_NAME=<host_name>

<host_name> can be either xx.xx.xx.xx or the host_name as a string.

Also, performance can be impacted by VxUL tracing. DebugLevel=4 should be
used for ndmp and ndmpagent (to avoid tracing file history which can also
cause a 2x to 3x reduction in performance).

To set DebugLevel, use the following commands:

/usr/openv/netbackup/bin/vxlogcfg -a -p nb -o ndmpagent -s
"DiagnosticLevel=5"
/usr/openv/netbackup/bin/vxlogcfg -a -p nb -o ndmpagent -s "DebugLevel=4"
/usr/openv/netbackup/bin/vxlogcfg -a -p nb -o ndmp -s "DebugLevel=4"
--------------------------------------------------------------------------------
Etrack Incident = ET633395

Description:
A change has been added that prevents bpduplicate from overwriting the
heap accounting information and causing the bpduplicate to crash by
copying a string into destination string that is too small.
--------------------------------------------------------------------------------
Etrack Incident = ET638325

Description:
NetBackup log messages no longer show up in the /etc/security/password
file on AIX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET639142

Description:
Under some circumstances (such as network issues), Vault could start a
new bpduplicate job before the previous bpduplicate job (for a given
storage unit pair) completed. This caused drive contention between the
old and new bpduplicate jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET617600
Associated Primary Etracks = ET702111

Description:
Vault's Media Going Offsite Reports did not count images that span media
correctly. Instead of being counted just once, such images and their sizes
were being added for the number of media spanned.
--------------------------------------------------------------------------------
Etrack Incident = ET638699

Description:
The Policy Execution Manager (PEM) would crash while PEM was shutting down,
if it was shutting down at the same time a progress log was being updated.
--------------------------------------------------------------------------------
Etrack Incident = ET617254 ET617889 ET640121

Description:
Hot Catalog Backup would not backup images when IDIRSTRUCT equaled 1
because the code expected the master server had a second or later version
of the catalog image directory structure, for example, IDIRSTRUCT = 2.

In a UNIX cluster environment, the VAR_GLOBAL_PATH is linked to the shared
drive. The backup client (such as, bpbkar) does not follow symbolic links
currently and therefore the files inside the linked directory would not be
backed up in an online catalog backup.

Excessive bpdbm debug log entries were produced from a Hot Catalog Backup.
This fix ties the logging of libcatbackup debug messages to the following
setting.

BPDBM_VERBOSE setting.
Example of affected log message:
00:00:02.032 [8398] < 2> db_ImgUnlock: db_ImgUnlock(833d698) error(0)
--------------------------------------------------------------------------------
Etrack Incident = ET636334 ET636411 ET636414

Description:
The hot catalog backups would fail if the CRYPT_OPTION was set to REQUIRED
in bp.conf, where it could also be set through the GUI->Host Properties->
Clients->Encryption tab.

Workaround:
To avoid this issue, set CRYPT_OPTION to ALLOWED, which is the default.
--------------------------------------------------------------------------------
Etrack Incident = ET617892

Description:
For an imported catalog backup image, the command line instruction
"bprecover -r -nbdb" would not work because the parent image ID was
missing in imported ASA image header.

Workaround:
To avoid this issue, open the imported catalog image header file and
remove the PARENT_IMAGE_ID line so that the ASA and the catalog backup
image header files do not contain the field.
--------------------------------------------------------------------------------
Etrack Incident = ET631474

Description:
Certain network timings and delays during increment backups can later
cause a synthetic backup to fail with a status 671. The client process
now attempts to recover from those network timings and delays. If the
client process is unable to recover, the error is no longer ignored and
the increment backup fails.

Additional Notes:
The executable, bpbkar32.exe, now issues the following new message if it
is unable to send information to the server:

"catalog write error (error_code)"
--------------------------------------------------------------------------------
Etrack Incident = ET642003
Associated Primary Etracks = ET841985

Description:
Changes were made to JobIMOMObject::CheckAndUpdateJobInfoData() in the
NetBackup Service Layer (NBSL) to correct a core dump situation.
--------------------------------------------------------------------------------
Etrack Incident = ET638313

Description:
The NetBackup Job Manager (NBJM) would crash when it received a message
from BPTM with a bad copy number.
--------------------------------------------------------------------------------
Etrack Incident = ET638320

Description:
The NetBackup Job Manager (NBJM) writes un-initialized data to the
JobParams file. When it reads the file again on a subsequent submission of
the job, it sometimes crashed because of un-initialized fields in the
JobParams file.
--------------------------------------------------------------------------------
Etrack Incident = ET638318

Description:
The NetBackup Policy Execution Manager (NBPEM) submitted a child job with
the option to inherit resources from the parent job after it released
resources from the parent job. The NBJM then crashed while trying to get
the resource from the parent job.
--------------------------------------------------------------------------------
Etrack Incident = ET633983 ET640407

Description:
Status 25 or 45 backup failures occurred under the following conditions:

- The master server is running NetBackup 6.0MP3.
- The media server is running NetBackup 5.x.
- The client is added to the NetBackup client database with the default
connect options.

Workaround:
To avoid this issue, explicitly set the connect_options value in the
client database to a value that is acceptable for a NetBackup 5.x version.
Do not use the default values:

admincmd/bpclient -update -client <client_name> -connect_options 0 0 2
--------------------------------------------------------------------------------
Etrack Incident = ET621772
Associated Primary Etracks = ET642018

Description:
Made changes to correct an NBSL core dump issue.
--------------------------------------------------------------------------------
Etrack Incident = ET642010

Description:
Changes were made to replace TreadSafeWrappers calls and to correct an
exception handling logic error in ServiceManagerCollector(). These issues
were causing a core dump issue in the NetBackup Service Layer (NBSL).
--------------------------------------------------------------------------------
Etrack Incident = ET628333

Description:
Mixing Dynamic Host Configuration Protocol (DHCP) clients and Dynamic Domain
Name Service (DNS) would cause potential data loss and security issues.
--------------------------------------------------------------------------------
Etrack Incident = ET627398

Description:
Hot catalog backup failed if the EMM server was installed on a remote
media server instead of on the master server, and BMR was installed on the
master server.
--------------------------------------------------------------------------------
Etrack Incident = ET579341

Description:
Added Encryption support to x64 NetBackup hosts.
--------------------------------------------------------------------------------
Etrack Incident = ET641058
Associated Primary Etracks = ET641055

Description:
A condition existed that caused NetBackup Service Layer (NBSL) to core
dump in HostSessionImpl::ping().
--------------------------------------------------------------------------------
Etrack Incident = ET638703
Associated Primary Etracks = ET638702

Description:
The NetBackup Policy Execution Manager (nbpem) process deadlocked while
doing bpexpdate -deassignempty -force >/dev/null.
--------------------------------------------------------------------------------
Etrack Incident = ET617887

Description:
An attempt to restore from a True Image Recovery (TIR) backup to tape after
the TIR data had been pruned from the catalog would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET630777
Associated Primary Etracks = ET630772

Description:
A change was made to the Policy Execution Manager to auto retry Vault jobs
on Status codes EC_vc_EjectFailed (287), EC_vc_EjectPartialSuccess (288),
and EC_vc_PartialSuccess (306). If one image failed to duplicate, Vault
would return a status 306. Also changed the parent job (nbgenjob) to
validate the image for a Vault job that returned an error status 306, 287,
or 288.
--------------------------------------------------------------------------------
Etrack Incident = ET618696

Description:
The following error would occur when trying to apply a patch when running
nbdb_upgrade:

Verifying the running version of NBDB ...
***** SQL error: Database server not found
Failed system call, '/usr/openv/db/bin//nbdb_unload -dbn NBDB -s /tmp'
Verification Failed.

When connecting to Sybase ASA using Open Database Connectivity (ODBC),
shared memory connections used space in /tmp by default. If there were
issues creating files in /tmp, the connection would fail. To resolve this
issue, the environment variable, ASTMP, is now set to /usr/openv/tmp.
--------------------------------------------------------------------------------
Etrack Incident = ET638071

Description:
Vltrun would dump core when trying to eject media (less/more than the
MAP full). A core dump would also occur after ejecting the first set of
media into the MAP.

This was observed only on HP-UX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET636795

Description:
Added the capability to do a step-wise downgrade of the NetBackup
Relational Database schema. This enables you to uninstall one or more
maintenance patches in the order in which they were applied.
--------------------------------------------------------------------------------
Etrack Incident = ET621857

Description:
Unable to create or modify disk staging storage units using the
NetBackup-Java Administration Console if a NetBackup 5.x system was
upgraded to NetBackup 6.0 or if a NetBackup 5.x license key was used
during a NetBackup 6.0 server installation.

This pack corrects this issue and enables you to create or modify disk
staging storage units using the NetBackup-Java Administration Console
if a NetBackup 5.x system is upgraded to NetBackup 6.0 using the 5.x
license or you could update to a NetBackup 6.0 license key.
--------------------------------------------------------------------------------
Etrack Incident = ET644627

Description:
On the active node, if the user has installed this pack on a secure
VCS Windows cluster environment that has a NetBackup server with EMM,
and are observing that NetBackup does not come online, the Enterprise
Media Manager (EMM) database schema did not update properly.

Workaround:
To avoid this issue, perform the following steps:
1. Take the NetBackup Server resource offline.
2. Freeze the NetBackup Service group.
3. Make sure that the Adaptive Server Anywhere � VERITAS_NB service is
started.
4. Execute the following command.
<install dir>/NetBackup/bin/nbdb_upgrade.exe �dbn NBDB
5. Execute the following command.
<install dir>/NetBackup/bin/admincmd/bpsyncinfo.exe
-add_paths NETBACKUP_RELATIONAL_DATABASE_FILES
6. Unfreeze the NetBackup Service group.
7. Bring NetBackup Server resource back online.

If you have experienced this issue on the install then you will also
experience it on the uninstall from the active node.
--------------------------------------------------------------------------------
Etrack Incident = ET636799

Description:
An error would occur when mixing FULL, Differential Incremental, and Vault
schedules in the "Hot_Catalog" backup policy. For example, if a Vault
schedule ran, followed by a Differential schedule (without any other jobs
running in between the two), the result would be the following:

JobID X = Catalog "Control" Job - Ends with Status 2
JobID X+1 = Differential Incremental Catalog Job - Ends with Status 227
--------------------------------------------------------------------------------
Etrack Incident = ET644077

Description:
In NetBackup 4.5, netbackup.dll was installed in the
C:\Program files\CommonFiles\VERITAS\Shared Directory. The NetBackup 6.0 GA
installer did not remove the old version of the file.
--------------------------------------------------------------------------------
Etrack Incident = ET618372

Description:
A change was made so that bpstsinfo correctly passes the
-filteronimagemodetype flag when used with the -remote flag.
--------------------------------------------------------------------------------
Etrack Incident = ET645645
Associated Primary Etracks = ET645697

Description:
A condition existed that caused the NetBackup resource Broker (nbrb) to
core dump under heavily loaded conditions. This problem had occurred
on AIX and HP-UX. There was lot of locking and unlocking involved in the
area where the resource broker (RB) sends the resources to the job manager.
RB was using reverse lock provided by ACE. Either RB was not using the
lock correctly or there was some issue in the ACE's implementation of
reverse lock which caused this core dump. To address the issue, the
lock/unlock logic was simplified.
--------------------------------------------------------------------------------
Etrack Incident = ET617893

Description:
TIR-enabled backups (including FlashBackup and NDMP) could fail in the
validation phase of the backup because of a miscalculated file size. This
patch provides earlier detection of the error and improved reporting on the
cause of the error.
--------------------------------------------------------------------------------
Etrack Incident = ET641172

Description:
Online catalog backups in configurations with cluster 5.x media servers
were creating a bpbackupdb process that looped infinitely.
--------------------------------------------------------------------------------
Etrack Incident = ET646623
Associated Primary Etracks = ET849324

Description:
The default method for NetBackup ODBC connections to the NetBackup database
(NBDB)/EMM database is to use shared memory followed by tcpip if shared
memory fails. This is controlled by the LINKS=shmem,tcpip{PORT=13785}
parameter in the database connection string.

On some platforms, there have been intermittent issues with shared memory
connections to the Sybase ASA database.

To work-around this issue, a new parameter has been aded to the vxdbms.conf
dfile to set the LINKS parameter in the connection string. To change this
parameter to only use tcpip connections, the following line
was added to vxdbms.conf:

VXDBMS_LINKS = tcpip{PORT=13785}

The vxdbms.conf file is located in /usr/openv/db/data (UNIX) and
InstallPath\VERITAS\NetBackupDB\data (Windows).
--------------------------------------------------------------------------------
Etrack Incident = ET637921

Description:
A change was added to ensure restores from legacy images do not fail
on Windows clients.
--------------------------------------------------------------------------------
Etrack Incident = ET641145

Description:
A problem existed that caused, in a few rare cases, f-list files in the
catstore subdirectories to have a mixed set of UNIX-style and Windows-style
path separators or even incorrect path entries. The code currently assumes
only one style of path separator was being used which caused problems for
hot catalog backup.

On Windows master servers this results in a partially successful
(status 1) hot catalog backup job.

On UNIX or Linux master servers this results in a failed (status 67)
hot catalog backup job on patch levels prior to MP4 and in a partially
successful (status 1) hot catalog backup job on patch levels MP4 and
later. (UNIX or Linux master servers are now consistent with Windows
master servers in the status for this condition.)

A message similar to the following should be seen in the bpbkar debug log
if this bug is encountered:

ERR - Unable to expand hot catalog backup directive: CATALOG_BACKUP

Workaround:
It is reasonably straightforward to manually identify, edit, and correct
the offending f-list files to avoid this problem.
--------------------------------------------------------------------------------
Etrack Incident = ET593700

Description:
Added a check so that any backups going to a file system export-enabled
Nearstore storage unit must have TIR enabled. This is because the
sts_delete_files process, which is part of the file system export backup,
requires the TIR data.
--------------------------------------------------------------------------------
Etrack Incident = ET632204

Description:
Media locations in ACS robotics were not updated properly after dismount
or during inventory when moving from standalone to robotic.
--------------------------------------------------------------------------------
Etrack Incident = ET644756 ET702144

Description:
In cases where a user authenticated against a non-root broker a failure to
load a credential from disk could occur. This would result in false
negative access checks for users leading to a Backup, Archive, and Restore
user interface rather than the NetBackup Administration console.

Workaround:
To avoid this issue, authenticate against the root broker on the master
server rather than another broker.
--------------------------------------------------------------------------------
Etrack Incident = ET630539

Description:
Corrected the vm.conf mapping of the ACS T10000 media types to HCART2.
--------------------------------------------------------------------------------
Etrack Incident = ET500024
Associated Primary Etracks = ET838966

Description:
Oracle backups no longer fail with a NetBackup status 227.
--------------------------------------------------------------------------------
Etrack Incident = ET646981

Description:
The NDMP agent caused a Dr. Watson error and a DUMP file when backing up
one volume.

This happens only on Windows and only when NDMP logging is enabled.
The problem is caused by "invalid" mtime/atime/ctime values sent by the
filer in the file history. This is not a normal situation.

Workaround:
To avoid this issue, turn NDMP logging off. This problem only occurs if
NDMP logging is enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET635017
Associated Primary Etracks = ET635016

Description:
Due to a memory management issue, the Volume Manager Daemon could
crash during certain media management operations.
--------------------------------------------------------------------------------
Etrack Incident = ET646977

Description:
A backup would fail if there was a space in the user and group name
in bpdbm.
--------------------------------------------------------------------------------
Etrack Incident = ET646985

Description:
NDMP backups failed with a status 84 when writing a TIR fragment.

The bptm log showed an error where the expected block position is one off.
This error occurred in the function write_data_tir().

Workaround:
To avoid this issue, add the following line to the file
<installdir>/netbackup/db/config/ndmp.cfg

NDMP_MOVER_CLIENT_DISABLE

This will have a minimal impact on backups. However it will cause a
significant performance impact to dup/verify/import when using
NDMP drives.
--------------------------------------------------------------------------------
Etrack Incident = ET640207

Description:
Allow the end user to specify pool numbers when creating a new volume pool.
A new option (-pnum) was added to the vmpool command to facilitate this.

The new usage is:

vmpool [-pnum <pool number>] -add <pool_name> "<description>" <host> <uid>
<gid>

The -pnum option must be specified before the -add option. The -pnum has
no effect when the -change option is specified.
--------------------------------------------------------------------------------
Etrack Incident = ET627870

Description:
The image will not be closed correctly and a data loss will occur during
duplication or staging where the following is true:

- The destination storage unit (STU) is a volume on a Nearstore with
version 7.2 of ONTAP.
- The disk storage unit option for 'enable block sharing' is set.

The first duplication or DSSU_POLICY backup to the Nearstore will complete
successfully, but subsequent operations using that image (such as, restore
and incremental backups) will not succeed.
--------------------------------------------------------------------------------
Etrack Incident = ET636626
Associated Primary Etracks = ET794331

Description:
Vault batching logic for image duplication may be sub-optimal if source
tape images span media.
--------------------------------------------------------------------------------
Etrack Incident = ET612141

Description:
The "File System Export" button on the Storage Unit dialog will be
available when NetBackup media server 6.0MP3 or higher version is
connected to a 7.2 ONTAP Nearstore or higher version as a
7.1 ONTAP Nearstore cannot export a file system.
--------------------------------------------------------------------------------
Etrack Incident = ET640456 ET632241 ET630393 ET632790
Associated Primary Etracks = ET640453

Description:
The nbpem showed scalability problems because of a recomputation of a
job�s due-time when not necessary. In addition, the internal queue
management was a single thread trying to handle multiple queues, which
caused long waits to process requests on some of the queues.
--------------------------------------------------------------------------------
Etrack Incident = ET641156

Description:
Hot catalog backup jobs fail with status 29 on Linux platforms.

In reality the backup did succeed, but the status is not being recorded
correctly resulting in the failed backup job.

Messages similar to the following will be seen in the admin debug log,
which show that the internal CLI used for the hot catalog backup job
did complete successfully:

<2> bpbackupdb: INITIATING: NetBackup 6.0
<2> logparams: -vxss -pjobid 672 -nodbpaths ...
<2> bpbackupdb: EXIT status = 0

But as message similar to these in the bpdbm debug log will indicate,
bpdbm thinks that the CLI operation failed:

<16> exec_vxss_backup: OVsystem(bpbackupdb -vxss -pjobid 672 -nodbpaths ...)
<16> exec_catalog_backup: exec_vxss_backup() failed (29)

--------------------------------------------------------------------------------
Etrack Incident = ET648677
Associated Primary Etracks = ET639374

Description:
The nbpem showed jobs were due but not queued.
--------------------------------------------------------------------------------
Etrack Incident = ET638693 ET649607
Associated Primary Etracks = ET615118

Description:
Changes were added to resolve an nbpem crash.
--------------------------------------------------------------------------------
Etrack Incident = ET638703
Associated Primary Etracks = ET638702

Description:
Changes were made to keep nbpem from hanging or suspending on a
start_bpexpdate.
--------------------------------------------------------------------------------
Etrack Incident = ET649692 ET636127

Description:
Changes were incorporated to address slow start times on user backups.
--------------------------------------------------------------------------------
Etrack Incident = ET596091

Description:
When running full/incremental hot catalog backup jobs on Windows with a
relatively large NetBackup catalog (containing at least 150,000 backup
images), the hot catalog backup ended with a status 41. Bpbkar32 took too
long to process these 150,000 backup images during it's pre-backup
operations; thus, causing the server to timeout before the client engine
starts sending data.
--------------------------------------------------------------------------------
Etrack Incident = ET646015
Associated Primary Etracks = ET644582

Description:
Changes were made to fix an NBSL core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET641162 ET649541

Description:
Some new image data fields added in NetBackup 6.0 were missing in the
image index file and therefore an online catalog backup job could fail
if the image index feature was enabled for the master server. (The image
index feature was enabled by the "bpimage -create_image_list -client
<master-server-name>" command line utility.)

Running bpexpdate to change the expiration of a phase I imported image
could cause it to be deleted if the backup spans tapes AND the first
tape has not yet completed phase II of the import process.

Workaround:
To avoid this issue, do not enable the image index feature for the master
server (for example, do not run bpimage -create_image_list -client
<master-server-name>"). If the image index feature has already been
enabled for the master server, apply this patch or contact technical
support for assistance in disabling the image index feature for the
master server by removing the IMAGE_* files from the
/usr/openv/netbackup/db/images/<master-server-name> directory to disable
the image index feature for the master server.
--------------------------------------------------------------------------------
Etrack Incident = ET645336
Associated Primary Etracks = ET644082

Description:
The NBJM returns a normal status to NBPEM after the request to resubmit a
job failed.
--------------------------------------------------------------------------------
Etrack Incident = ET699915

Description:
When a backup failed and went from an incomplete to a failed state,
the child job would not run again. The Policy Execution Manager
would not run child jobs after a failure due to the Job Manager changing
the job type from a resume to a restart.
--------------------------------------------------------------------------------
Etrack Incident = ET699915

Description:
When a backup failed and went from incomplete to a failed state,
the child job would not run again.
--------------------------------------------------------------------------------
Etrack Incident = ET700003

Description:
A disk staging storage unit (DSSU) relocation job failed with a status 96,
in spite of available media.
--------------------------------------------------------------------------------
Etrack Incident = ET649559
Associated Primary Etracks = ET646615

Description:
NDMP backups no longer fail with a status 84 - Cannot write TIR data to
media.
--------------------------------------------------------------------------------
Etrack Incident = ET700745

Description:
Multiplexed restore jobs would possibly fail when the number of active
jobs reached the maximum of 32. When this error occurred, the bptm log
would have an entry similar to the following:

12:21:15.296 [3471] <16> bct_find_nonactive: FATAL - cannot find
non-active Backup Control Table entry
--------------------------------------------------------------------------------
Etrack Incident = ET626205

Description:
Added a call to Sybase's dbvalid command when NBDB or BMRDB databases
were started after a cold catalog backup, catalog recovery, or by
nbdb_admin -start. In addition, added an nbdb_admin -validate
option to call dbvalid at any time.
--------------------------------------------------------------------------------
Etrack Incident = ET527990
Associated Primary Etracks = ET798116

Description:
Added error detection for Oracle restores that would fail because of
corruption.
--------------------------------------------------------------------------------
Etrack Incident = ET700848

Description:
I18N: Unable to restore \"Information Store\" / using Traditional Chinese
(Big5) character set.
--------------------------------------------------------------------------------
Etrack Incident = ET700802

Description:
Prepare to restore failed on an AIX client if a volume group contained a
disk or disks that were multi-pathed.
--------------------------------------------------------------------------------
Etrack Incident = ET617061

Description:
Changes were made to ensure that NBSL no longer core dumps in
JobIMOMObject::CheckAndUpdateJobInfoData().
--------------------------------------------------------------------------------
Etrack Incident = ET700039

Description:
NetBackup was not retaining the volume pool override information in
schedules.
--------------------------------------------------------------------------------
Etrack Incident = ET700039

Description:
NetBackup was not retaining the volume pool override information in
schedules.
--------------------------------------------------------------------------------
Etrack Incident = ET621934

Description:
When two or more DSSUs fill up, they are unable to independently reclaim
disk space. This could cause additional backup jobs to fail (error 129) to
these two unrelated DSSUs if space reclamation took too long.
--------------------------------------------------------------------------------
Etrack Incident = ET632300

Description:
The tpconfig manual user interface would not successfully add shared
robot/drives.
--------------------------------------------------------------------------------
Etrack Incident = ET627293 ET617051

Description:
The NetBackup Service Layer (NBSL) no longer core dumps when failing
over the cluster or if NBSL creates zombie threads.
--------------------------------------------------------------------------------
Etrack Incident = ET703004
Associated Primary Etracks = ET647573

Description:
If NetBackup Access Control (NBAC) was enabled prior to an upgrade
from 6.0GA (or 6.0MP1) to 6.0MP2, any non-Administrator, non-root
users in the NBU_Security Admin Group would lose their Access Control
privileges after the upgrade.

Workaround:
There are three workaround options available to you, that you can use
to avoid this issue:

First workaround option:
------------------------
Add the Non-admin user to the �Security Administrators� group in
VxAZ. To do this, perform the following steps:

1. Open the VxSS user interface (/opt/VRTSat/bin/runvssatgui.sh
2. Open the appropriate Authorization Server (top right button).
Connect to it using root.
3. Select the �Authorization Groups� button on the left panel.
4. Select the �Security Administrators� group in the tree.
5. Select the menu option Authorization > Authorization Groups >
Add Member.
6. Add the non-Admin user using the dialog that appears.
7. The non-Admin user should now have the necessary permission.
This should not circumvent any other security because this
user now has security privileges on VxAZ. If this is not
appropriate, contact Symantec Support for help in taking other
other measures, such as read-only access to Security
information.

Note: The non-Admin user SHOULD have permission without
taking this step.

Second workaround option:
------------------------
Uninstall the VxAZ installation and reinstall. Re-configure NBAC by
Running �bpnbaz �SetupSecurity <server>� and the appropriate
�bpnbaz �AllowAuthorization� commands.

Note: This option will cause any customization to be lost.

Third workaround option:
------------------------
Only use Admin users for Security Operations.
--------------------------------------------------------------------------------
Etrack Incident = ET621194

Description:
Hot Catalog Backups were not cleaning old logs in the
/usr/openv/netbackup/logs/user_ops/dbext/jobs and
/usr/openv/netbackup/logs/user_ops/dbext/logs folders.

--------------------------------------------------------------------------------
Etrack Incident = ET643841
Associated Primary Etracks = ET799808

Description:
A Recovery Manager (RMAN) restore could not be redirected to an Oracle
instance owned by a different Oracle user.

Additional Notes:
After you have installed this pack, a new backup of the source Oracle
database is required so the correct group permission is on the image to
allow the alternate user to performed a restore to the new
instance/database.
--------------------------------------------------------------------------------
Etrack Incident = ET649659

Description:
A change has been made that makes it possible to correct old EMM database
entries in the device mappings file.

--------------------------------------------------------------------------------
Etrack Incident = ET703078
Associated Primary Etracks = ET648013

Description:
The Device auto-discovery wizard and acstest displayed only some of the
tape drives.

Additional Notes:
The problem only happened to a robot with a large number of drives.
--------------------------------------------------------------------------------
Etrack Incident = ET704572
Associated Primary Etracks = ET771586

** Description:
BPTM would overwrite a valid image if a backup was canceled during a
fragment break. This issue effected HP-UX and AIX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET703493

Description:
Changes were made to correct an error string collision that prevented the
L10N tools from working.
--------------------------------------------------------------------------------
Etrack Incident = ET704578

Description:
A change was added to correct an incorrect log message in the NetBackup
Tape Manager during a media expiration operation.
--------------------------------------------------------------------------------
Etrack Incident = ET648724 ET631626
Associated Primary Etracks = ET699996

Description:
Changes have been made for various problems that include named streams
associated with directories, and performance issues. In addition, these
changes fix a problem with an HP master that was not able to load the
restricted version of libxm.
--------------------------------------------------------------------------------
Etrack Incident = ET703215 ET771306

Description:
A change has been implemented that allows a local client install of a
Macintosh platform as well as other non-server platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET648714

Description:
The most current version of VxMS, 4.3 build 15, is included in this pack.
This version addresses an X64 installation issue and a vfm_open_id issue.
--------------------------------------------------------------------------------
Etrack Incident = ET704832
Associated Primary Etracks = ET704822

Description:
When using virtual storage units and after a cluster application failover,
the active node was not being set correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET702128
Associated Primary Etracks = ET702125

Description:
A user was unable to enumerate any Sharepoint Portal Server 2003 objects
using the NetBackup Backup, Archive, and Restore (BAR)user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET640484
Associated Primary Etracks = ET640481

Description:
When Endpoint_Selector tries to connect to profile_in_use () it is possible
that another thread closes the connection and resets profile_in_use.
--------------------------------------------------------------------------------
Etrack Incident = ET704957 ET704961 ET704980 ET704977

Description:
Changes have been made to correct issues relating to duplicate log message
numbers as well as a Linux loader problem.
--------------------------------------------------------------------------------
Etrack Incident = ET648557

Description:
Excessive resource usage no longer occurs during synthetic backups.
--------------------------------------------------------------------------------
Etrack Incident = ET704640 ET632758 ET763828
Associated Primary Etracks = ET610208 ET703589

Description:
If failure history was exceeded, it would recalculate jobs and continue to
retry; thus, not starting the children jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET609542

Description:
Certain VSP binaries were being laid down, even though VSP was not
installed on the machines. A check has been added to see if the VSP key
exists before laying down the binaries.
--------------------------------------------------------------------------------
Etrack Incident = ET766069

Description:
The NetBackup Job Manager (NBJM) had deallocated the resources of a
parent job because they were not consumed in time because the NetBackup
Policy Execution Manager (NBPEM) took longer to submit the first child.
This resulted in status 50 and status 801 errors. (Status 50 is a parent
job end error and status 801 is a children end error.)
--------------------------------------------------------------------------------
Etrack Incident = ET647920
Associated Primary Etracks = ET646600

Description:
A problem with the bpstsinfo -UPDATE command has been corrected and it
no longer causes a core dump when creating threads.
--------------------------------------------------------------------------------
Etrack Incident = ET764906 ET783411
Associated Primary Etracks = ET795340

Description:
Using the catalog archive process, files were not being removed from the
catstore directory. In addition, running the catalog archive process while
an online catalog backup was in process could have caused the catalog
backup to fail.

Additional Notes:
A new option, "-remove_dotf", has been added to the bpcatarc command. This
option eliminates the need to pipe the output from bpcatarc to bpcatrm to
remove .f files. If the new option is not used, you must continue to pipe
the output from bpcatarc to bpcatrm to remove .f files.
--------------------------------------------------------------------------------
Etrack Incident = ET764867

Description:
Solaris Zone restoration with Bare Metal Restore (BMR)

BMR relies on entries in /etc/vfstab to document the file systems that are
subject to restoration. Dynamically created and mounted file systems not
appearing in /etc/vfstab, even if backed up by NetBackup, do not
automatically restore. The easiest way to make such BMR file systems is to
add an entry to /etc/vfstab documenting the devices and mount points used,
with the "Mount at boot" field set to "no".

Then, the dynamic file systems can continue to be used as before, only BMR
is now aware of them, and recreates them unless unmapped in DDR, and
restores their contents if backed up by NetBackup.

Two types of zone features cause dynamically mounted file systems to appear:
1) fs entries involving devices in the global zone
2) Device entries imported from the global zone but mounted either by the
/etc/vfstab of the non-global zone, or dynamically by the zone itself.

To automate BMR restoration of zones using such features, you should add
entries to the global zone /etc/vfstab that causes BMR to restore them.
1) For fs entries, the global zone's devices are used as raw, special
values with a mount point that appears under the root of the non-global
zone.

The entry to add to the global zone's /etc/vfstab should use the global
zone's device paths with the full path to the non-global zone mount point,
including the zone path. For example, if the zone looks like:
zonepath=/export/zone1
fs:
dir=/export
special=/dev/dsk/c0t9d0s6
raw=/dev/rdsk/c0t9d0s6
type=ufs
then the global zone entry in /etc/vfstab should look like:
/dev/dsk/c0t9d0s6 /dev/rdsk/c0t9d0s6 /export/zone1/root/export ufs - no-

2) For device entries mounted by the non-global zone, there are two issues
to be dealt with when configuring for BMR restoration:
a) The dynamic mount used involves the imported device path under the
zone path.
b) The device match should not use wildcards to allow BMR to edit if DDR
is used.

Concerning point a) - For a device that is mounted by an /etc/vfstab inside
a non-global zone, there will be one or more device entries in the zone
such as:
zonepath=/export/zone2
device:
match=/dev/*dsk/c0t0d0s4
and in the non-global zone's /etc/vfstab:
/dev/dsk/c0t0d0s4 /dev/rdsk/c0t0d0s4 /local ufs 3 yes -
This causes the global zone to dynamically mount
/export/zone2/dev/dsk/c0t0d0s4 on mount point /export/zone2/root/local.
However, to make BMR automatically recreate the file system, you should
add the documenting entry to the global zone /etc/vfstab instead as:
/dev/dsk/c0t0d0s4 /dev/rdsk/c0t0d0s4 /export/zone2/root/local ufs - no -
(If you use the device paths relative to the zone path, BMR will only
recreate the mount point instead of restoring the whole file system.)

Concerning point b) - when the device specification involves a wildcard,
BMR will not be able to edit the entry if DDR mapping is done that affects
the zone, such as unmapping or moving a file system from one disk to
another.

The affected zone's /etc/vfstab ware edited, but the device match entries
will only be edited if the match does not include a wildcard. So, instead
of
match=/dev/*dsk/c0t0d0s4
use two device entries:
match=/dev/dsk/c0t0d0s4
and
match=/dev/rdsk/c0t0d0s4
to ensure BMR DDR correctly updates the zone definitions and the vfstab
file.
--------------------------------------------------------------------------------
Etrack Incident = ET633295 ET620589 ET767219 ET771458

Description:
Log Recycling enables NetBackup users to control the amount of disk space
that is used for logs. Prior to this change, the disk could fill with
log files.

Previous options available for controlling disk use was available via
either 1) user intervention with the vxlogmgr �d command, 2) a cron job
that called vxlogmgr -d, or 3) the �Keep Logs� setting in the
NetBackup-Java Administration Console. These options were often inadequate
because they are time-based pruning, while VxUL log recycling is
continuous. Often, time-based pruning has been inadequate because the log
files filled the disk before the time-based pruning has chance to execute.

For more detailed information about Log Recycling, refer to the following
TechNote on the Symantec Support Web site.

http://entsupport.symantec.com/docs/279590
--------------------------------------------------------------------------------
Etrack Incident = ET766166

Description:
Block-level incremental (BLIB) backups were not working with the SAP
database agent.
--------------------------------------------------------------------------------
Etrack Incident = ET768521

Description:
Changes have been made to correct status 31 (setuid failed) errors that
occurred when running multiple concurrent backups on Windows clients.
--------------------------------------------------------------------------------
Etrack Incident = ET768448

Description:
Could not manually create NDMP or Media Manager storage units using the
NetBackup-Java Administration console. Using the bpstuadd �nodevhost
command would return the message, �Remote Media Servers not allowed for
NetBackup Server�.
--------------------------------------------------------------------------------
Etrack Incident = ET768441

Description:
vmphyinv no longer fails while changing media residence.
--------------------------------------------------------------------------------
Etrack Incident = ET769421

Description:
When selecting the preferred machine name for a cluster node, which will
be stored in the EMM database, ignore any REQUIRED_INTERFACE entries in
vm.conf or bp.conf (Registry on Windows).

Workaround:
To avoid this issue, remove the REQUIRED_INTERFACE entries from vm.conf and
bp.conf (Registry on Windows) before installing NetBackup 6.0. This only
pertains to cluster environments.
--------------------------------------------------------------------------------
Etrack Incident = ET768457

Description:
The nbemmcmd �deletehost command no longer fails if a storage unit is set
to, "Any Available Host".
--------------------------------------------------------------------------------
Etrack Incident = ET767144
Associated Primary Etracks = ET767131

Description:
No longer receive �Allocation Failed� errors when trying to connect to the
Activity Monitor. This occurred for all users using the Java Activity
Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET769437

Description:
A previous change was made to bpduplicate which could in some instances
result in creating a command string which bpdm could not parse. This
caused duplication to fail. This problem only existed for NearStore
storage units.
--------------------------------------------------------------------------------
Etrack Incident = ET649747
Associated Primary Etracks = ET648871

Description:
User-directed archives no longer delete files if warnings are generated
during the backup portion of the operation.
--------------------------------------------------------------------------------
Etrack Incident = ET770672

Description:
Storage unit changes could cause policy execution manager (PEM) to receive
unnecessary event notifications which would impact PEM performance.
--------------------------------------------------------------------------------
Etrack Incident = ET413513

Description:
For a policy that used wildcards (such as, *) in the file list and enabled
multiple data streams, NetBackup would not include any dot files (such as,
.rhosts) at that directory level in the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET772376
Associated Primary Etracks = ET846168

Description:
A restore no longer fails when restoring an Exchange DB store that contains
a special character (for example, "#") to a Recovery Storage Group.
--------------------------------------------------------------------------------
Etrack Incident = ET769378

Description:
If the Hot Catalog Backup encountered an image catalog that was corrupted,
it would stop the hot catalog backup at that point and finish immediately
with an error code of 67 (file list read failed).

Now it continues past the corrupted image catalog, and backs up the rest of
the catalog, and finishes with a partial success status of 1.

Workaround:
To avoid this issue, fix the corruption in the image catalog, or take a
cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET767294
Associated Primary Etracks = ET763625

Description:
A new entry "MediaBlockSize" is provided in the nbsl.xml file to configure
fetch size. This option is useful for congested TCP/IP networks, where the
default fetch size of 1000 could fail.
--------------------------------------------------------------------------------
Etrack Incident = ET764251

Description:
On vaults where the eject list is greater than map size, the vaults are
successful, however they are slow, sometimes taking between 20 and 50
minutes to complete.
--------------------------------------------------------------------------------
Etrack Incident = ET593547

Description:
The media_deassign_notify notification script, added to the
<install_path>/netbackup/bin/goodies directory, will execute if it is
moved into the <install_path>/netbackup/bin directory. This script is
executed every time a media is deassigned.
--------------------------------------------------------------------------------
Etrack Incident = ET613852
Associated Primary Etracks = ET778164

Description:
Exchange CINC, or user-directed backup, fails with media that is
multiplexed.
--------------------------------------------------------------------------------
Etrack Incident = ET774846 ET805115 ET818780 ET831242
Associated Primary Etracks = ET621934

Description:
On large file systems with a large number of images, disk staging would not
free space fast enough to prevent concurrent backups from failing with 129
errors.

Additional Notes:
When a backup to a disk storage unit with staging completes, the percent
used is compared with the high water mark. If the percent used is equal to
or greater than the high water mark, a bpdm process will be invoked which
will remove staged images until the low water mark is reached.

To disable this behavior, create the "IGNORE_HIGH_WATER_MARK" touch file in
the netbackup/bin directory.
--------------------------------------------------------------------------------
Etrack Incident = ET770159

Description:
To determine the NetBackup server version, bpexpdate, bpdbm, and some other
components were using bpcd protocol. If one of the servers is down, it may
take a long time. In addition, the error handling of the failure was not
appropriate.

A change has been made to fetch the NetBackup server version from the EMM
database. This is a fast and more reliable way to determine NetBackup
server versions.
--------------------------------------------------------------------------------
Etrack Incident = ET770650

Description:
Changes have been made to correct various compile warnings.
--------------------------------------------------------------------------------
Etrack Incident = ET776562

Description:
The Problem�s Report shows, "SO_REUSEADDR failed, errno = 0, No error".
--------------------------------------------------------------------------------
Etrack Incident = ET772419

Description:
During normal termination using the bpdown command (on Windows), PEM's
JobScheduler::terminate was not called. This casued PEM to hang while
waiting for the Connection Factory to be closed and eventually lead to a
crash.
--------------------------------------------------------------------------------
Etrack Incident = ET699903

Description:
Tapes that were not full were sometimes mistakenly ejected from standalone
drives after jobs completed.
--------------------------------------------------------------------------------
Etrack Incident = ET773419

Description:
Changes were added to fix warning errors when compiling jobmgr on
HP-UX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET772287

Description:
Changes were made to fix issues where synth backups were failing when going
to a File system, export-enabled, NearStore storage unit because they did
not "admit" to being TIR enabled even if the policy they are run out of is
TIR enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET768443

Description:
The user was able to change the pool type of the default none, NetBackup,
DataStore, and Catalog backup pools. This fixes the problem from the
server side.
--------------------------------------------------------------------------------
Etrack Incident = ET776697

Description:
Duplication failed if VERBOSE=5 was set and the destination storage unit
was a tape.

This problem was introduced by a previous fix in this pack and does not
exist in any released software.

Workaround:
To avoid this issue, do not set VERBOSE equal to 5.
--------------------------------------------------------------------------------
Etrack Incident = ET770273

Description:
Wildcard matching in image keywords does not work.
--------------------------------------------------------------------------------
Etrack Incident = ET777616

Description:
Failing synthetic backups would unintentionally perform a catalog cleanup
instead of deleting the single failed backup image.

--------------------------------------------------------------------------------
Etrack Incident = ET771311

Description:
Changes were made to resolve several small memory leaks that were possible
in infrequently encountered scenarios.
--------------------------------------------------------------------------------
Etrack Incident = ET773473

Description:
Added support for Linux, Red Hat 4, and SuSE 9, on Power PC from IBM.
Normal UNIX client support for these client types is also covered with
this maintenance pack.

File system support is limited to EXT2, EXT3, ReiserFS on SuSE SLES 9, and
NFS. Files that are greater than 2 Gigabytes are supported. Local user
interfaces are available through the command line or the menu interface
(using the bp command). Remote access is the same as all other UNIX
clients.

For the client binaries to be installed from the UNIX patch you must first
create the following directories:

/usr/openv/netbackup/client/Linux/IBMpSeriesRedHat2.6
/usr/openv/netbackup/client/Linux/IBMpSeriesSuSE2.6

The binaries for the Encryption licensed feature are available through
the Encryption patch. For the Encryption binaries to be installed from
the UNIX Encryption patch you must first create the following directories:

/usr/openv/netbackup/crypt/Linux/IBMpSeriesRedHat2.6
/usr/openv/netbackup/crypt/Linux/IBMpSeriesSuSE2.6

For additional information about Encryption, refer to the NetBackup
Encryption readme.
--------------------------------------------------------------------------------
Etrack Incident = ET579398 ET775062
Associated Primary Etracks = ET701785 ET701785

Description:
Synthetic Backup no longer fails when a component image spans tape volumes.
--------------------------------------------------------------------------------
Etrack Incident = ET774704
Associated Primary Etracks = ET774649

Description:
Restores of backups for clients that had FlashBackup policies (either alone
or in combination with other policy types) were slow to become active and
mount tapes.
--------------------------------------------------------------------------------
Etrack Incident = ET770151

Description:
The �bpexpdate �recalculate �backupid �ret� command correctly changed the
expiry date of an image, but not the image retention level.
--------------------------------------------------------------------------------
Etrack Incident = ET772390

Description:
In some scenarios, the NetBackup Resource Broker (NBRB) was orphaning
resources while waiting for tape span and then deallocating those
resources. This caused an erroneous job termination.
--------------------------------------------------------------------------------
Etrack Incident = ET775684

Description:
Vaulting (bpduplicate) failed with the second image in a batch job with a
�resource request failed� message.

Workaround:
This problem may occur if images are on media with an ID of less than six
characters. To avoid this issue, use six-character media ID�s.
--------------------------------------------------------------------------------
Etrack Incident = ET776253
Associated Primary Etracks = ET700121

Description:
Clicking into the Device Monitor generated the following error message, "An
invalid argument was encountered".
--------------------------------------------------------------------------------
Etrack Incident = ET777442
Associated Primary Etracks = ET694851

Description:
The physical size/length of the "Cache device path" attribute field has
been enlarged to accommodate more characters for those users who have long
path lengths.
--------------------------------------------------------------------------------
Etrack Incident = ET778055

Description:
The "Default gateway" can be changed and saved from NetBackup
Administration Console for Windows in Change Config wizard.
--------------------------------------------------------------------------------
Etrack Incident = ET775681

Description:
Increased the mount timeout for TLH drives to accommodate drive cleaning by
the library between mounts.
--------------------------------------------------------------------------------
Etrack Incident = ET775677

Description:
Changes have been made to enable NetBackup to control TLH robotics with up
to 512 drives.
--------------------------------------------------------------------------------
Etrack Incident = ET775429

Description:
Changes were made to correct error message for invalid media type mapping.
--------------------------------------------------------------------------------
Etrack Incident = ET775427

Description:
Changes were added to correct syslog messages to print appropriate
information.
--------------------------------------------------------------------------------
Etrack Incident = ET775428

Description:
Resolved an issue with the TLD inventory with the empty_map option set by
correcting the algorithm so that if only the last slot is open, it can
still be used without failing.
--------------------------------------------------------------------------------
Etrack Incident = ET768449

Description:
Resolved an issue that would not allow you to delete a machine of
APP_CLUSTER type.
--------------------------------------------------------------------------------
Etrack Incident = ET776667

Description:
Changes were made to correct various compiler warnings.
--------------------------------------------------------------------------------
Etrack Incident = ET778780

Description:
A bad configuration could lead to thousands of monitor-provider allocations
in the database. The resource broker (RB), on startup, may consume a lot of
memory reading these database entries and may even dump core. Now the RB
removes all of the monitor-provider allocations at startup.
--------------------------------------------------------------------------------
Etrack Incident = ET779594
Associated Primary Etracks = ET779463

Description:
Earlier Windows consoles were not displaying all network interfaces, more
specifically, Virtual interfaces were not shown in main console.
--------------------------------------------------------------------------------
Etrack Incident = ET775425

Description:
When downing a drive using the vmoprcmd -downbyname or vmoprcmd �down
comands, the drive's designated scan path was sometimes set back to "UP".
--------------------------------------------------------------------------------
Etrack Incident = ET775423

Description:
The results displayed by the command vmdareq show a scan host, but
the results displayed by the command vmoprcmd indicate any scan paths.
--------------------------------------------------------------------------------
Etrack Incident = ET775435

Description:
When a pre-NetBackup 6.0 media server was unassigned a drive that was
Scanned by a NetBackup 6.0 media server, it was not clearing the
RVSN/EVSN and Ready fields.
--------------------------------------------------------------------------------
Etrack Incident = ET780083
Associated Primary Etracks = ET780079

Description:
When changing a drive from not shared to shared using the wizard, and
the new host (the host that will now make it shared) was running
NetBackup 5.x, the wizard would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET777630

Description:
Back-level media servers are not able to DA-release the drives because
re-registration timers block the request.
--------------------------------------------------------------------------------
Etrack Incident = ET775426

Description:
The robotic test utility (robtest) would core dump and could not perform
an unload if multiple paths exist.
--------------------------------------------------------------------------------
Etrack Incident = ET770182

Description:
Long delays occurred when starting immediate backups because the Policy
Execution Manager calls getNextJob() when processing immediate requests.
Removed call to getNextJob() for immediate requests when searching for the
backup. It makes the time to find the job n squared instead of n, where n
is the number of entries in the worklist.
--------------------------------------------------------------------------------
Etrack Incident = ET770337

Description:
The Policy Execution Manager was using the wrong lock to extract entries
from the job queue when processing user, archive, or manual backup
requests. This issue has been resolved and will no longer result in
data corruption, a crash, or lost data.
--------------------------------------------------------------------------------
Etrack Incident = ET772631

Description:
The Job Manager CPU utilization was high while most of the user backup jobs
were queued. The Job Manager was busy sending WAITING messages to the
progress logs for the queued, user backup jobs. The WAITING message is sent
every 30 seconds.

To resolve this issue, Job Manager was changed to increase the interval
between these WAITING messages sent to the progress logs.
--------------------------------------------------------------------------------
Etrack Incident = ET770167

Description:
Because of changes in the startup process with NetBackup 6.0 MP4, the
Policy Execution Manager can not start jobs until the build worklist is
complete. This process can take a long time.

To compensate for this, the build worklist has been changed to not query
the last backup or compute the due times so that the list can be built very
quickly. After the list has been built it will then synchronize with the
NetBackup Job Manager so the jobs can be started, followed by the
calculation of all of the jobs due times.

By dividing the process of how the worklist is built into two steps, jobs
can be started much sooner.
--------------------------------------------------------------------------------
Etrack Incident = ET770655

Description:
User backup requests to the Policy Execution Manager appeared to be waiting
a long time for the worklist lock. A change was made to the Policy
Execution Manager to skip the due-time calculation for user, archive, or
immediate requests.
--------------------------------------------------------------------------------
Etrack Incident = ET781527
Associated Primary Etracks = ET703273

Description:
Changed the Policy Execution Manager to call the Job Manager restartJob
Interface which looks at restartSelection setting instead of
resourceSelection. When a parent job is resumed, it frees the resource.
Job Manager failed the job if it looked at the resourceSelection (that is
set to inherit parent resource) but would work if it used restartSelection
(that is, set to use standard resource).
--------------------------------------------------------------------------------
Etrack Incident = ET782623

Description:
A change was made to correct an uninitialized local variable as well as
remove an unused local variable within the code.
--------------------------------------------------------------------------------
Etrack Incident = ET778981

Description:
Changes were made to resolve NBPEM memory leaks.
--------------------------------------------------------------------------------
Etrack Incident = ET779116

Description:
NetBackup services NBPEM and NBJM would core dump if an attempt was made to
Start them on a media server.
--------------------------------------------------------------------------------
Etrack Incident = ET781175
Associated Primary Etracks = ET781185

Description:
The user-configurable, MEDIA_UNMOUNT_DELAY timeout, was not being honored
for database agents.
--------------------------------------------------------------------------------
Etrack Incident = ET773564

Description:
A problem with the command -delete_server_from_app_cluster, made it
impossible to unconfigure an application cluster and reconfigure it with
the correct name.
--------------------------------------------------------------------------------
Etrack Incident = ET778908

Description:
Made multiple Coverity fixes for PEM.
--------------------------------------------------------------------------------
Etrack Incident = ET771373

Description:
Fixed the potential access of pointers that were not initialized.
--------------------------------------------------------------------------------
Etrack Incident = ET784803 ET784808 ET784805 ET784804 ET784810 ET792742 ET784809
ET802855

Description:
Buffer overflow areas have been identified and corrected in daemons running
on Veritas NetBackup master, media, and client servers. Successful access
to a vulnerable Veritas NetBackup server and the ability to successfully
execute arbitrary code could potentially result in unauthorized access with
elevated privilege on a system.
--------------------------------------------------------------------------------
Etrack Incident = ET775510

Description:
A restore of a large backup image would potentially fail if a large number
of data buffers (for example, 1024) was configured. The number of data
buffers is configured on UNIX systems in
/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS, and for Windows
systems in <install_path>\NetBackup\db\config\NUMBER_DATA_BUFFERS.

Workaround:
To avoid this problem, do one of the following:

- Set the number of data buffers to a smaller value (For example, 128).

- Create the following file:

UNIX: /usr/openv/netbackup/db/config/MIN_RESTORE_SKIP
Windows: <install_path>\NetBackup\db\config\MIN_RESTORE_SKIP

Then enter a number greater than the following:
(size_data_buffers) * (number_data_buffers) / 512
--------------------------------------------------------------------------------
Etrack Incident = ET775513

Description:
Individual file restores would potentially fail in the following
circumstance:

- The original backup was done using Inline Copy, and at least one of the
copies was disk, and the backup was multiplexed.
- The backup had multiple fragments for the disk copy.
- A duplicate from a disk copy to tape was performed, and the source and
destination storage units are on the same machine.
- The restore is from the duplicated disk copy.

Workaround:
To avoid this issue, create the following file on the master server:

For UNIX Systems:
/usr/openv/netbackup/NOSHMDUP

For Windows Systems:

<installed_path>\NetBackup\NOSHMDUP
--------------------------------------------------------------------------------
Etrack Incident = ET771240

Description:
The NBPEM no longer waits for a notification script to be complete before
continuing to process.
--------------------------------------------------------------------------------
Etrack Incident = ET771553

Description:
The NBPEM uses write locks instead of read/write locks to enhance
performance.
--------------------------------------------------------------------------------
Etrack Incident = ET770349

Description:
bprd and nbpem now exchange user backup startup parameters through the
use of a file named with a GUID instead of a process PID, eliminating the
possibility that the same filename will be used twice.
--------------------------------------------------------------------------------
Etrack Incident = ET774791

Description:
A missing log message was added for when FFREADtries are exceeded.
--------------------------------------------------------------------------------
Etrack Incident = ET775512

Description:
Verify, duplication, or import operations are not able to browse
images from the Windows NetBackup Remote Administration Client.

Workaround:
To avoid this issue, run the following command on the Remote Administration
Client:

<install_path>\volmgr\bin\vmglob -set_gdbhost <master server>
--------------------------------------------------------------------------------
Etrack Incident = ET781618
Associated Primary Etracks = ET771576

Description:
Destination media may incorrectly get unmounted and a new media chosen when
duplicating multiple images. This can occur when duplicating a mixture of
multiplexed and non-multiplexed backups.
--------------------------------------------------------------------------------
Etrack Incident = ET775591
Associated Primary Etracks = ET789993

Description:
The image file created for the parent job, while multi-streaming, was not
being validated. This would later cause status 200 failures.
--------------------------------------------------------------------------------
Etrack Incident = ET785921
Associated Primary Etracks = ET783614

Description:
Duplication was failing after successfully duplicating the first image.
This occurred because the server name in bp.conf file was different from
what was in the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET778008

Description:
When you run NBJM, built with a Windows debug build, it gets an assertion
failure because of variables that were not initialized.
--------------------------------------------------------------------------------
Etrack Incident = ET775486
Associated Primary Etracks = ET771394

Description:
LTID could not connect to the NBRB when VxSS was enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET786811

Description:
If a job is queued awaiting resources, the message displaying the reason
for queuing is not displayed in the job details in the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET775422

Description:
Linux servers, with SAN attached tape drives, can have trouble using drives
that are in use at the time of a service start.
--------------------------------------------------------------------------------
Etrack Incident = ET787735

Description:
Avoid closing an NDMP tape device, so that the filer does not unreserve
the drive.
--------------------------------------------------------------------------------
Etrack Incident = ET775430

Description:
Synthetic backups no longer cause bptm core dumps when all drives are down.
--------------------------------------------------------------------------------
Etrack Incident = ET775431

Description:
Occasionally, BPTM would not handle canceled jobs during NBJM waits.
--------------------------------------------------------------------------------
Etrack Incident = ET775433

Description:
TapeAlert data is no longer ignored after the media is unloaded.
--------------------------------------------------------------------------------
Etrack Incident = ET643875

Description:
Unloads would fail on NDMP drives if the raw open operation failed.
--------------------------------------------------------------------------------
Etrack Incident = ET770157
Associated Primary Etracks = ET794596

Description:
The cleanup process intermittently failed to remove image header files on
busy systems.

Workaround:
To avoid this issue, ignore the reported error and let a subsequent cleanup
process delete the file.
--------------------------------------------------------------------------------
Etrack Incident = ET783401

Description:
Restarting the device daemons on pre-NetBackup 6.0 media servers after a
device configuration change would inadvertently unregister the host with
the device allocator (DA).
--------------------------------------------------------------------------------
Etrack Incident = ET781676 ET781719

Description:
Made multiple Coverity fixes for the NetBackup Job Manager (NBJM).
--------------------------------------------------------------------------------
Etrack Incident = ET771614

Description:
Improved the nbpem performance when reading the failure history database.
--------------------------------------------------------------------------------
Etrack Incident = ET777662

Description:
Trying to change a configured device to partially configured on a
pre-6.0 media server in the device configuration wizard, may sometimes
cause devices to become "DISABLED" for a NetBackup 5.x media server.
For NetBackup 5.x media servers, there is no concept of "DISABLED".
--------------------------------------------------------------------------------
Etrack Incident = ET776871

Description:
Duplications would fail with status codes of 114 or 800. This occurred
when media with mixed multiplexed and non-multiplexed backups were
duplicated, and when using multiplexed duplication.
--------------------------------------------------------------------------------
Etrack Incident = ET778815

Description:
The nbpem restarts it�s timer for the next housekeeping activity only after
the previous housekeeping activity has completed
--------------------------------------------------------------------------------
Etrack Incident = ET772500

Description:
Changes were added to this pack to eliminate crashes and core dumps during
nbpem shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET781548

Description:
When moving a host to new hardware using nbemmcmd, not all of the database
entries were updated with the new hostname. A change was added that
verifies that all of the necessary database fields have been updated
correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET772510

Description:
Changes were made that improve performance when writing error history by
caching the Veritas Unified Logging (VxUL) configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET771618

Description:
Changes were added that improve performance for bpdbm and other processes
by improved caching of configuration information.
--------------------------------------------------------------------------------
Etrack Incident = ET783370

Description:
The NetBackup Resource Broker (NBRB) no longer crashes while running
bplabel.
--------------------------------------------------------------------------------
Etrack Incident = ET787072

Description:
An object was being deleted incorrectly for an obscure end case that is
normally not encountered.
--------------------------------------------------------------------------------
Etrack Incident = ET784575
Associated Primary Etracks = ET624633

Description:
The bpbackup command, when used with the -L and -i options, did not
provide useful information in the progress log.
--------------------------------------------------------------------------------
Etrack Incident = ET790023
Associated Primary Etracks = ET782774

Description:
You can now backup NetBackup media servers using Storage Area Network (SAN)
media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET777633
Associated Primary Etracks = ET777631

Description:
In the Java user interface, the Activity Monitor�s Detailed Status did not
increment the percent complete. It jumped from 0% to 100% at the end of
the job.
--------------------------------------------------------------------------------
Etrack Incident = ET772618

Description:
Generic jobs would not start when a large number of them were initiated in
quick succession on Windows.

NetBackup Job Manager (NBJM) was changed to start an extra nbproxy on
startup that is used by all nbgenjob's. The only exception is that a
catalog backup job will start its own nbproxy because a cancel is
implemented by shutting down the nbproxy.
--------------------------------------------------------------------------------
Etrack Incident = ET790041
Associated Primary Etracks = ET790038

Description:
Generic job exited after a few retries when the Policy Execution Manager
did not respond to pings. The parent job would exit with a status 50 and
the children exits with a status 801.

To resolve this issue, a change was made to genericjob that forces it to
ping forever until the Policy Execution Manager responds or is restarted,
or an OBJECT_NOT_EXIST exception is returned.
--------------------------------------------------------------------------------
Etrack Incident = ET786951
Associated Primary Etracks = ET781181

Description:
The Policy Execution Manager would core dump on a resume due to not copying
last schedule used when the job was being deleted.
--------------------------------------------------------------------------------
Etrack Incident = ET786406
Associated Primary Etracks = ET784164

Description:
A problem existed in the "Media and Device Management > Media" section of
the Windows Administration Console and the Java user Interface. Whenever a
tape holds more than 2 Terabytes of data on it, the Kbytes number in the
"Kilobytes" column displays as a -ve number.
--------------------------------------------------------------------------------
Etrack Incident = ET789535

Description:
When the default robotic volume group is selected in "Change Vault" dialog,
it is not selecting the correct volume group.
--------------------------------------------------------------------------------
Etrack Incident = ET785497

Description:
Removed the new ORB created during a ServiceManager collection process.
--------------------------------------------------------------------------------
Etrack Incident = ET791064

Description:
Using long hostnames for NDMP hosts no longer results in the credentials
being added incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET791401
Associated Primary Etracks = ET647711

Description:
If the Media Mount Timeout was set in the Master Server properties >
Timeouts section, the backup for NDMP would fail with the following
error message.

"timed out waiting for media manager to mount volume"

Workaround:
To avoid this issue, disable the media mount timeout in the Master Server
properties > Timeouts section. For NDMP backup, the backup should execute
if this is disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET787049

Description:
The install was starting the ASA database service on non-EMM media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET787586 ET786594 ET790483

Description:
The NetBackup service layer (NBSL) would crash when connected from a
user interface or NetBackup Operations Manager (NOM).
--------------------------------------------------------------------------------
Etrack Incident = ET789695

Description:
Adding a cleaning tape from the user interface would result in a �bad
Cleanings� remaining number.
--------------------------------------------------------------------------------
Etrack Incident = ET772403

Description:
Formatting of jobid in log files has been normalized to "jobid=" in all
reasonable cases. This format agrees with the use of context as well.
In some places where stringstreams were used to format jobid, an
.imbue(std::locale("C")) was added to prevent localized formatting of large
integers. For more information about this change, refer to the following
TechNote on the Symantec Support Web site.

http://entsupport.symantec.com/docs/284795
--------------------------------------------------------------------------------
Etrack Incident = ET787963

Description:
The nbpem no longer leaks memory with each CORBA connection.
--------------------------------------------------------------------------------
Etrack Incident = ET776946

Description:
The nbpem no longer uses memory that is not initialized that could result
in a random error message.
--------------------------------------------------------------------------------
Etrack Incident = ET777867

Description:
Changed the Policy Execution Manager objects to initialize all fields in
constructor.
--------------------------------------------------------------------------------
Etrack Incident = ET784609
Associated Primary Etracks = ET782395

Description:
When time falls back because daylight savings time ends, jobs may run
1 hour late.
--------------------------------------------------------------------------------
Etrack Incident = ET790574

Description:
When attempting to create a Vault profile on the Java user interface, the
Make Primary Checkbox was not functioning properly. If this was used on a
storage unit in the Duplication Rule Dialog, it would not be written
correctly in vault.xml file.
--------------------------------------------------------------------------------
Etrack Incident = ET791514

Description:
Changes were added to correct the AUTO_UPDATE_ROBOT feature for Windows.
--------------------------------------------------------------------------------
Etrack Incident = ET789971
Associated Primary Etracks = ET785700

Description:
Robot inventory reports a confusing error when it is run on a robot that
contains media that is marked "conflicted" in the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET788825
Associated Primary Etracks = ET647204

Description:
The tpautoconf -replace_drive command no longer corrupts the drive's
inquiry string in the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET787033

Description:
The nbpem no longer fails or crashes when processing Share Point backups.
--------------------------------------------------------------------------------
Etrack Incident = ET792594
Associated Primary Etracks = ET646858

Description:
The NetBackup Resource Broker (NBRB), under heavily loaded conditions with
many media servers, would take about 30 seconds to give resources to the
job.

To fix the problem the following improvements have been made:

- Improved drive cache in RB (RB no longer links with emmlib).
- If the maxmpx in the request is 1, do not try to join it to any group.
- Delete all MonitorProvider allocations using a single SQL statement.
- Prioritize the requests based on the birth time too.
- Some miscellaneous improvements.
--------------------------------------------------------------------------------
Etrack Incident = ET777893

Description:
Changed the Policy Execution Manager to not exit the application
if the restart request could not be satisfied because of a malloc failure.
--------------------------------------------------------------------------------
Etrack Incident = ET792609
Associated Primary Etracks = ET764790

Description:
The tpconfig command would fail with the following error when the range
of the CLIENT_PORT_WINDOW parameter was set between 1025 to 5000, for
example.

"EMM interface initialization failed, status = 77"
--------------------------------------------------------------------------------
Etrack Incident = ET786617 ET631392

Description:
bpsturep and bpstuadd did not have Nearstore version checking that was
present in the user interfaces. This brings them to the same level.
It is not permissible to configure an SOI storage unit on a ONTAP 7.1.x
Nearstore. (Refer to TechNote 282929 on the Symantec Support Web site for a
more detailed explanation.) It is also not permissible to have a Nearstore
staging storage unit that has any type of SIS (SOI or FSE) enabled for
ONTAP 7.2 and higher Nearstores.
--------------------------------------------------------------------------------
Etrack Incident = ET765029
Associated Primary Etracks = ET763562

Description:
The hot catalog backup feature did not work with images that had been
archived using the catalog archiving feature. Prior to this fix, if the
catalog archiving feature had been used to archive images, the backup job
generated from a hot catalog backup policy would fail with a status 67
on a UNIX or Linux master server and with a status 1 (partially
successful) on a Windows master server.
--------------------------------------------------------------------------------
Etrack Incident = ET770171

Description:
Changes were made to improve performance on multiple data streams by not
generating streams again if stream discovery did not change the stream
content.
--------------------------------------------------------------------------------
Etrack Incident = ET789170
Associated Primary Etracks = ET702600

Description:
Vault duplication jobs were forcing a dismount/re-mount of media in drives
while processing a batch of images on a tape. This was happening because
more than one duplication job was active at the same time in the system
and the media and device selection (MDS) was asking the resource broker
(RB) to unload drives so that the other job could use it. Now the
duplicate writer is not unloaded if told by MDS to do so.

If you want pre 6.0MP4 behavior, you can create the following touch file:
<install_path>/netbackup/db/config/RB_UNLOAD_DUP_WRITER_ON_DEMAND.
--------------------------------------------------------------------------------
Etrack Incident = ET792327 ET792328 ET803918 ET808971 ET843451 ET847076

Description:
A logic error has been identified and corrected in daemons that run on
Veritas NetBackup master, media, and client servers. Successful access to
and manipulation of this logic error could potentially lead to arbitrary
command execution with elevated privileges on a vulnerable system.

For customers who need to back out this patch and want to automate the
down-rev process on their clients using the Update_clients script can
contact Support to obtain a revised bpinst file for their respective
version.

The following scenarios do NOT require a new bpinst from Support:

- If you are downgrading to 50MP7 or higher, 51MP6 or higher,
or 6.0MP4 or higher.

- If you are running Windows on your server.

- If you are only downgrading any of the following addons:
- DB agents (DB2, Lotus Notes, Oracle, SAP, Sybase, or Informix)
- Encryption (all key lengths)
- Java
- Advanced Client
- BMR master or BMR boot server
- NDMP
- Vault
- GDM (5.x only)
- Advanced Reporter (5.x only)
- NetBackup Operations Manager (6.0 only)
- Storage Migrator
- Japanese or Chinese Language Packs
--------------------------------------------------------------------------------
Etrack Incident = ET795443
Associated Primary Etracks = ET794631

Description:
If a hot catalog backup policy (policy type NBU_Catalog) was set up for
a UNIX clustered NetBackup master server that included the Vault option
and the /usr/openv/netbackup/vault/sessions directory was a link pointing
to the shared drive in the cluster configuration, then the data in the
sessions directory was not properly included in the catalog backup image.
--------------------------------------------------------------------------------
Etrack Incident = ET795533 ET795523
Associated Primary Etracks = ET618799 ET791036

Description:
bptm would erroneously log an error, (either an error code 95 or an error
code 97), during image expiration.
--------------------------------------------------------------------------------
Etrack Incident = ET792470

Description:
nbproxy and nbgenjob had unnecessary CPU utilization because additional
logging operations were enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET784640

Description:
Changes were added to fix a memory leak in the PEM logging.
--------------------------------------------------------------------------------
Etrack Incident = ET792282

Description:
In some cases, if the resource broker (RB) was not shut down cleanly,
backups would not run until nbrbutil -resetAll was run.
--------------------------------------------------------------------------------
Etrack Incident = ET794270

Description:
Script-based BLI backups were not cleaning up checkpoint files properly.

Workaround:
To avoid this issue, you can manually delete the checkpoints using the
fsckptadm command. For example, fsckptadm remove <ckpt-name> <mountpoint>
--------------------------------------------------------------------------------
Etrack Incident = ET795345

Description:
Memory was being read after being freed in the job scheduler's work list.
--------------------------------------------------------------------------------
Etrack Incident = ET796051

Description:
Changes were made to correct a minor logic error.
--------------------------------------------------------------------------------
Etrack Incident = ET610398

Description:
When a suspended job is resumed, the bytes count and the file count in the
activity monitor job display is no longer incorrect.
--------------------------------------------------------------------------------
Etrack Incident = ET778923

Description:
When a job was retried immediately, the job status of the previous try
was lost.
--------------------------------------------------------------------------------
Etrack Incident = ET631436

Description:
A problem existed that caused NOM to not show bprd and bpdbm.
--------------------------------------------------------------------------------
Etrack Incident = ET777860

Description:
Changes were made to clean up the following Policy Execution Manager tasks:
- Switched data types from int to bool if used as a boolean.
- Added error checking to the job submission queue to fix a memory leak.
- Changed the Policy Execution Manager to return the status
EC_backup_error or EC_malloc_failed if an error is encountered
starting child jobs for a parent job.
--------------------------------------------------------------------------------
Etrack Incident = ET796104

Description:
A race condition occurred when two add_files queries were received
simultaneously and both attempted to create the catstore folder.
--------------------------------------------------------------------------------
Etrack Incident = ET784650
Associated Primary Etracks = ET829340

Description:
NetBackup communication between components that were separated by a
firewall did not work. For instance, when a master server was behind the
firewall and a media server was outside the firewall, all communication
from the master server had an internal host address that was not accessible
from outside systems.

This is the same when clients and other services are in question.

Additional Notes:
To activate NAT address replacement, systems outside of the firewall should
have the FIREWALL_IN parameter specified in their bp.conf/registry.

Format: FIREWALL_IN=hostname1,nat_address1|hostname2,nat_address2|...

Where: <hostname> is the name of the host system that needs to be accessed
and <nat_address> is the actual NAT address for the firewall to do
forwarding.
--------------------------------------------------------------------------------
Etrack Incident = ET795448

Description:
Changes were made to not send Storage Unit Events when only updating
capacity information. Too many of these events were being generated and
impacting performance.
--------------------------------------------------------------------------------
Etrack Incident = ET795436 ET796505 ET801859
Associated Primary Etracks = ET794344

Description:
VSP files would sometimes get deleted when they were needed to resume an
incomplete or suspended stream.
--------------------------------------------------------------------------------
Etrack Incident = ET795374 ET814653

Description:
BPTM failed a job with a 174 error when it should retry the
resource allocation.
--------------------------------------------------------------------------------
Etrack Incident = ET797992

Description:
NetBackup 5.x media servers fail when running tpautoconf -sync, if the
global database host is a 6.0 server.

Workaround:
To avoid this issue, delete the device configuration on the 5.x media
server and reconfigure.
--------------------------------------------------------------------------------
Etrack Incident = ET781386

Description:
There may be cases where configuring either shared libraries or shared
drives does not perform the necessary device configuration updates on all
hosts. For example, if host A has drive D1 configured, and then the wizard
is used to configure host B, host B will have the drive added as shared,
but host A's configuration will not be updated. This results in two hosts
scanning the drive.

Workaround:
To avoid this issue, do the following:
- Always use the wizard to configured devices.
- Always scan all media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET797150
Associated Primary Etracks = ET797162

Description:
The bptm process no longer crashes while duplicating data that has True
Image Restore (TIR) information associated with it.
--------------------------------------------------------------------------------
Etrack Incident = ET797080

Description:
When the parent job does stream discovery the
getRealAndVirtualPolicyByName() gives an error and sometimes fails
because the sig library was not initialized. Currently the sig library
is only initialized for catalog backups instead of for all backup types.
--------------------------------------------------------------------------------
Etrack Incident = ET802582
Associated Primary Etracks = ET793913

Description:
The NetBackup Java user interface no longer displays �square box�
characters in the Media �Side� column for the second AcsLsm.
--------------------------------------------------------------------------------
Etrack Incident = ET796480

Description:
Backup jobs would occasionally fail with error status 26 (client/server
handshaking failed). The bpbrm log would show the following:

08:34:12.336 [2764.3504] <2> bpbrm multiplexed_backup: calling
read_media_msg for media manager PID.
08:34:42.618 [2764.3504] <2> bpbrm read_media_msg: media manager pid 0 is
not alive
08:34:42.618 [2764.3504] <16> bpbrm multiplexed_backup: cannot get PID of
media manager
08:34:42.915 [2764.3504] <2> bpbrm Exit: ERROR 26 sent to parent process
--------------------------------------------------------------------------------
Etrack Incident = ET796392

Description:
The NBJM threads block while calling the proxy for BPDBM requests.
--------------------------------------------------------------------------------
Etrack Incident = ET796475

Description:
If a Windows FlashBackup aborts early in its processing, then a user pop-up
occurred since a throw was taking place without the catch being set up.
--------------------------------------------------------------------------------
Etrack Incident = ET794326

Description:
Changed a strncpy to a V_strlcpy to prevent the string not being null
terminated.
--------------------------------------------------------------------------------
Etrack Incident = ET797363

Description:
Increased the connection cache size for nbjm to reduce number of
Communication retries by bptm.
--------------------------------------------------------------------------------
Etrack Incident = ET784514

Description:
Synthetic backups no longer fail with the error message, "termination
requested by bpcoord(665)".
--------------------------------------------------------------------------------
Etrack Incident = ET797083

Description:
The parent job no longer core dumps upon exiting an application when trying
to log a VxUL message after an orb shutdown. The parent job was modified
to remove all VxUL messages that are being logged after an orb shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET797388 ET798930

Description:
Multiple backups for the same client and policy that were started at the
same time created a situation where an image was being validated at
the same time the previous backup for the client and policy was being
validated.

One of the final steps in image validation is to go back through previous
backups for the client and policy and update the TIR meta data to allow TIR
data to be pruned. However, since the previous backup for the client and
policy was still being validated, it could not be updated and the following
log message (and error report entry) were generated:

17:27:33.723 [11812] <16> get_last_backup_lock: Bad image header:
many-non-multi-stream_1158100028_FULL, error: file read failed (13)

bpdbm was exiting with a normal status, so the backup was successful.

Workaround:
To avoid this issue, wait before starting backups for the same client and
policy.

Additional Notes:
With this change, any failures in updating tir meta data in image
validation will result in a conditional success for the backup job.
--------------------------------------------------------------------------------
Etrack Incident = ET797999 ET797370

Description:
Changes were made to clarify error message that may have been unclear.
This involved no functional change.
--------------------------------------------------------------------------------
Etrack Incident = ET796292

Description:
Pending messages were not displayed in the Activity Monitor for spanned
backups.
--------------------------------------------------------------------------------
Etrack Incident = ET798366

Description:
EMM now logs a more accurate disk space message when space is below
the threshold.
--------------------------------------------------------------------------------
Etrack Incident = ET796332

Description:
Changes were made to bpbrmds to eliminate core dumps when performing a
manual or scheduled relocation of a DSSU on media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET800221

Description:
Parent images have no associated .f file, and as a result have a file count
of zero. When images with a zero file count are validated, a function to
tally the number of files is called. This function should not be called
when there is no associated .f file. The logic to determine whether there
is an associated .f file has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET800184
Associated Primary Etracks = ET798913

Description:
Resolved an issue that caused, "Frequent status code 805 - invalid jobid,"
errors to occur.

Additional Notes:
This condition occurred when children jobs were retired due to exceeding
the time allowed in incomplete state. The parent job being resumed either
manually or automatically resulted in an 805 error due to the job having
a jobid of -1. This fix prevents the child from starting since it is not
resumable. The new result will correctly be a 200 error if no children
can be started. An indication of this will be written to the pem log.
--------------------------------------------------------------------------------
Etrack Incident = ET801046

Description:
The job monitor would cancel the catalog backup job after 20 minutes.
The nbgenjob ping interval to the job manager was changed to three minutes
to keep the job from being cancelled.
--------------------------------------------------------------------------------
Etrack Incident = ET799129

Description:
The synthetic backups were not scheduling correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET800016

Description:
The nbpem would core dump because getECmsgl was not thread safe.
--------------------------------------------------------------------------------
Etrack Incident = ET803630

Description:
Changes were added to correct an issue that casued the resource broker (RB)
to hang at startup.
--------------------------------------------------------------------------------
Etrack Incident = ET799867

Description:
The Policy Execution Manager inefficiently processes policy change
notifications when performing housekeeping tasks which may slow job
submission. This inefficiency can occur from the user interface if the
user selects all policies and then activates or deactivates the list of
policies.

Workaround:
To avoid this issue, do not generate a large number of policy changes all
at once before a window opens. Instead, amortize them over time to limit
the impact on the Policy Execution Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET800184
Associated Primary Etracks = ET798913

Description:
The jobid of a child checkpoint restart job would be set to -1 when
a 196 status occurred. The result was an 805 error if the parent was
resumed because the jobid -1 gets resumed.
--------------------------------------------------------------------------------
Etrack Incident = ET804921

Description:
The calendar schedule would not run when the available window spanned
across the specified day.
--------------------------------------------------------------------------------
Etrack Incident = ET805146

Description:
The NetBackup Job Manager (NBJM) was checking the connection to the proxy
before reading the global configuration to obtain attributes such as,
max vault jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET805407

Description:
The policy monitor would show as being down in Initial Data Load status
page.
--------------------------------------------------------------------------------
Etrack Incident = ET800841

Description:
Sometimes manual jobs would not start through either the user interface
or the command line. This would happen if PEM lost connection with NBJM.
--------------------------------------------------------------------------------
Etrack Incident = ET804850

Description:
An issue that caused catalog backups to hang on a retry have been fixed.
--------------------------------------------------------------------------------
Etrack Incident = ET805807

Description:
Cancelling an incomplete job that failed with a 196 error, then restarting
nbpem would cause the job to show as done in the Activity Monitor.
However, if the job is set to done in the Activity Monitor, a retry or
resume of the active job will not show up in the Activity Monitor.

Workaround:
If there are checkpoint restart jobs that show as complete but have a
status of 196 and pem needs to be restarted, remove the pempersist file
before pem is started again.
--------------------------------------------------------------------------------
Etrack Incident = ET806779

Description:
A timer was scheduled for a backup job even when throttling was not
configured.
--------------------------------------------------------------------------------
Etrack Incident = ET806990

Description:
Service credentials had expired and because of that, the NOM client was
unable to log into the NOM server.

Workaround:
To avoid this issue, you can renew the credential using the command line
interface provided by vssat.
--------------------------------------------------------------------------------
Etrack Incident = ET803889

Description:
A fix was made that enables a Nearstore storage unit on an ONTAP 7.1
nearstore to have both "enable block sharing" on and be a staging storage
unit.
--------------------------------------------------------------------------------
Etrack Incident = ET803649

Description:
Jobs would queue indefinitely, following a media server reset while
pending resource requests were outstanding.

Workaround:
To avoid this issue, restart the resource broker, or run nbrbutil -resetall.
--------------------------------------------------------------------------------
Etrack Incident = ET798064

Description:
A problem existed when using the vxlogview command that caused the
�t option to be ignored if it followed a �d option.
--------------------------------------------------------------------------------
Etrack Incident = ET808318
Associated Primary Etracks = ET796499

Description:
The service called NetBackup Volume Manager (vmd) would stop unexpectedly
because of a network problem.
--------------------------------------------------------------------------------
Etrack Incident = ET808314
Associated Primary Etracks = ET804963

Description:
The Tape Library DLT Control Deamon (tldcd) service would unexpectedly
terminate because of network problems.
--------------------------------------------------------------------------------
Etrack Incident = ET808037 ET807124

Description:
The SharePoint Portal, when configured with a network name in a network,
load-balanced, medium farm configuration, would not relink the portal
databases after a restore.

Additional Notes:
Please refrain from using a local IP address when configuring portals and
team sites. SharePoint communicates to all the load-balanced, front-end
servers to get information about the Portal/Team Site when they are backed
up or restored. If there is a Portal/Team Site that is tied locally to one
of the load-balanced servers, then other front-end servers will not be
cognizant of the local names. It will result in backup and restore failures
for the local portals and team sites.

Please use fully qualified domain names or IP addresses (such as,
http://10.80.138.80 instead of http://vitualportal ) when configuring
portals and team sites with a network name in a network, load-balanced
environment. A SharePoint application generates exceptions when virtual
servers that are specified that cannot be resolved by the application while
committing and reconnecting the restored databases. These errors can be
tracked with the help of tar logs in NetBackup\logs\tar on the database
client and spswrapper log files in NetBackup\logs\spps folder in the
sharepoint front end servers.

The workaround for this scenario is to use the IP address while
configuring the portal/team sites or restoring/reconnecting the databases
to the portal/team site using the SharePoint 2003 administration console
after the NetBackup restore has completed.
--------------------------------------------------------------------------------
Etrack Incident = ET814706

Description:
PEM no longer crashes when starting a bpduplicate job (or any job where
the client was not set).
--------------------------------------------------------------------------------
Etrack Incident = ET814644
Associated Primary Etracks = ET797945

Description:
The inventory operation, using vmphyinv, was failing with a network
protocol error (39). This was because oprd was crashing. After fixing the
core dump, other issues were encountered (and fixed) because of which tape
header was not being read correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET814692
Associated Primary Etracks = ET801982

Description:
A change was made to ensure that the volume expiration was not getting
reset after expiring all images on a tape.
--------------------------------------------------------------------------------
Etrack Incident = ET814762
Associated Primary Etracks = ET783819

Description:
An Oracle restore would fail if no drives were available within 900
seconds.
--------------------------------------------------------------------------------
Etrack Incident = ET814884

Description:
ExportedResourceMgr.cpp and ExportedResource.cpp do not show up in the
"what" output, making it impossible to verify the version of these files
in the nbjm binary.
--------------------------------------------------------------------------------
Etrack Incident = ET818259
Associated Primary Etracks = ET809337

Description:
Changes were made to correct an issue with adding an NDMP robot.
--------------------------------------------------------------------------------
Etrack Incident = ET818227

Description:
The text for status code 125 has been changed to reflect the use of this
status code in preventing some operations when an online catalog backup is
in progress.
--------------------------------------------------------------------------------
Etrack Incident = ET818136
Associated Primary Etracks = ET807602

Description:
NOM no longer shows the start and end times being off by 30 minutes for the
Singapore timezone (SGT).
--------------------------------------------------------------------------------
Etrack Incident = ET774674

Description:
When a bad drive or bad tape is mounted and the mount fails, the Media and
Device Selection (MDS) will down the drive and retry using other
drives/media. If this happened to be the scan host for this drive, MDS
would not clear the scanning assignment. Subsequently the device allocator
(DA) would bring the drive back up.
--------------------------------------------------------------------------------
Etrack Incident = ET771156 ET806039

Description:
When drive or library paths are swapped, and devices are re-discovered
using the wizard, users may see drives or libraries with an "empty" path.
This makes the device unusable and it must be deleted and reconfigured.
--------------------------------------------------------------------------------
Etrack Incident = ET772110

Description:
NetBackup would show the incorrect version number when it was installed as
Media Server. For example, bpgetconfig -s >host< (or the appropriate
bpjava* protocol) would not return the patch level if initiated across
UNIX <-> Windows boundaries, for instance,

On UNIX host A, execute bpgetconfig -s B -A

where B is Windows...

or vice-versa
--------------------------------------------------------------------------------
Etrack Incident = ET818369
Associated Primary Etracks = ET808850

Description:
A job could be canceled out of a window when the window was still open.
--------------------------------------------------------------------------------
Etrack Incident = ET818434
Associated Primary Etracks = ET802264

Description:
Scheduled backups did not always run in a window that was open for only
one day, and the freqency was set for less than one day.
--------------------------------------------------------------------------------
Etrack Incident = ET819178

Description:
The nbnos process no longer leaks memory with policy changes.
--------------------------------------------------------------------------------
Etrack Incident = ET818041

Description:
NetBackup would leave rogue/zombie processes running during the course of
the patch install/uninstall. The installer will now actively search for
these processes and terminate them before it continues with the install.
--------------------------------------------------------------------------------
Etrack Incident = ET821063

Description:
Java user interface would use the wrong authentication broker if it was
different from root broker.
--------------------------------------------------------------------------------
Etrack Incident = ET820406

Description:
In some cases, bptm was not exiting after job completion, making jobs
unavailable for other jobs.

Workaround:
Manually kill hung bptm processes.
--------------------------------------------------------------------------------
Etrack Incident = ET819158

Description:
A backup job would get retried even though it completed with a status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET818859

Description:
A change was made so that NBSL no longer core dumps when NetBackup is
accessed using NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET803700

Description:
Changes were made to ensure that parent jobs no longer exit with a
status 200.
--------------------------------------------------------------------------------
Etrack Incident = ET788999

Description:
In the Activity Monitor, the elapsed time for a job would sometimes appear
formatted incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET821035
Associated Primary Etracks = ET795266

Description:
Database backups or restores may fail (because of a timeout).

An examination of the debug logs showed that the EXIT STATUS was sent from
the client to bpbrm, however bpbrm did not receive the EXIT STATUS message.
--------------------------------------------------------------------------------
Etrack Incident = ET821355
Associated Primary Etracks = ET808950

Description:
nbemm will now allow alias functions with machinetypes cluster, app_cluster
and api.
--------------------------------------------------------------------------------
Etrack Incident = ET828665

Description:
A problem that occurred when the following conditions existed has been
fixed:

1) The schedule associated with the DSSU initiates relocation operations.
2) All completed images on the DSSU have already been relocated.
3) New, uncompleted images are in the process of being written to the
DSSU because of new backup operations.

There were no images that could be relocated and the job terminated with
an error status of 190. No errors had actually occurred but the resultant
messages gave the user the impression that something was wrong.
--------------------------------------------------------------------------------
Etrack Incident = ET828100

Description:
The cluster package and monitoring configuration was incorrect when
installing with a fully qualified virtual name on HP serviceGuard
and SunCluster clusters.
--------------------------------------------------------------------------------
Etrack Incident = ET827854

Description:
On the HP-UX IA64 platform, the "bpcatlist -id <backup id>" command could
core dump if the -id option is used.

Workaround:
To avoid this issue, do not use the "-id" option.
--------------------------------------------------------------------------------
Etrack Incident = ET819570

Description:
After you have attempted to stop a NetBackup Service, you may receive a
service stop failure.

Approximately 3 seconds after you have attempted to stop a NetBackup
Service you will notice that progress bar zooms across the screen and
disappears before the service has had a chance to do an orderly shutdown,
causing the stop failure to be reported.
--------------------------------------------------------------------------------
Etrack Incident = ET819159

Description:
An expire from the user interface of a snapshot-based backup image copy
failed with the following message in the bpfis log.

"fis_rebuild_from_db: cannot open"
--------------------------------------------------------------------------------
Etrack Incident = ET821071

Description:
A problem existed in Exchange VSS jobs that caused incremental backups to
act like FULL backups.
--------------------------------------------------------------------------------
Etrack Incident = ET820388

Description:
Added support to display filesystem capacities that are larger than
several Terabytes (TB).
--------------------------------------------------------------------------------
Etrack Incident = ET828735
Associated Primary Etracks = ET821288

Description:
When using vnetd only for client connect, all backups in the multiplexing
group would fail with a 41 status ("network connection timed out") if one
client cannot be contacted.

Workaround:
To avoid this issue, run the backups as non-multiplexed.
--------------------------------------------------------------------------------
Etrack Incident = ET802903

Description:
A problem existed where a catalog backup would run however it did not
appear in the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET828685

Description:
Changes have been made that ensures a Synthetic schedule will run at the
proper time.
--------------------------------------------------------------------------------
Etrack Incident = ET829045

Description:
Pem no longer crashes if there is an attempt to restart a done job from
the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET829683
Associated Primary Etracks = ET814470

Description:
Empty paths on file entries were causing backups to fail with a status 1
and an entry in the bpdbm log similar to the following:

11:29:18.781 [5216.3708] <32> add_files: File:
v:\src\common\libcatalog\nbe_string.h Line: 434: null pointerFunction:
utf8_strlen

With this patch, the backup will still fail if a null or empty path is
detected, but an entry similar to the following will appear in the
NetBackup error report:

A null or empty path was provided for policy1_1160000001_FULL at entry 2501

Additional Notes:
A null or empty path string is usually caused by a failure in the client
device. Check for patches from the device manufacturer to address the
root cause.

There is a known issue with NetApp filers configured for Chinese locales
that produces this problem. NetApp has a file history patch that addresses
the issue:

NetApp Bug ID: 195779
Title: NDMP DMA shows no file names after a backup with 7.0.x

Description:

Empty NFS pathnames will be returned in the file history for non-ASCII
filenames if the root volume's language is not set to C/POSIX or
the language setting of the volume being backed up differs from the
root volume's language setting.

Workaround:

Make sure the language setting of the root volume matches that of
the volume being backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET830269

Description:
A change has been made that ensures that after you have downed a drive on
the scan host, it will not come back up.
--------------------------------------------------------------------------------
Etrack Incident = ET805843

Description:
bpdbm uses the notification service to notify the PEM and JM components
when policies are updated. When the call to the notification service
failed, the bpdbm child process would terminate with little information on
the cause of the failure. With this patch, the cause of the failed call to
the notification service will be logged, and an entry will be made in the
NetBackup error report for the termination of the child bpdbm process.
--------------------------------------------------------------------------------
Etrack Incident = ET797083

Description:
A Parent job (nbgenjob) would core dump when an exception, thrown by
ORB, was not handled. This problem has been fixed in this pack.
--------------------------------------------------------------------------------
Etrack Incident = ET831186
Associated Primary Etracks = ET830464

Description:
Changes were made to resolve an intermittent crash in findByJobId.
--------------------------------------------------------------------------------
Etrack Incident = ET831242

Description:
On large file systems with a large number of images, disk staging would not
free space fast enough to prevent concurrent backups from failing with 129
errors. (Refer also to ET774846.)

Additional Notes:
When a backup to a disk storage unit with staging completes, the percent
used is compared with the high water mark. If the percent used is equal to
or greater than the high water mark, a bpdm process will be invoked which
will remove staged images until the low water mark is reached.

To disable this behavior, create the "IGNORE_HIGH_WATER_MARK" touch file in
the netbackup/bin directory.
--------------------------------------------------------------------------------
Etrack Incident = ET831331
Associated Primary Etracks = ET829395

Description:
The bpduplicate command would fail, resulting in a core dump. This would
occur if bpduplicate, while running on a media server, tried to invoke
bpduplicate on the master using a bidfile. This would happen most
frequently as part of disk staging.
--------------------------------------------------------------------------------
Etrack Incident = ET831415

Description:
When a request to the EMM server to change an expiration date for a media
failed, an unreadable message would appear in the NetBackup error report.
--------------------------------------------------------------------------------
Etrack Incident = ET819040

Description:
A job that was added to a multiplexed group would show an incorrect
operation in the Activity Monitor. For example, the Job operation would
remain as CONNECTING during a successful backup. However, if the backup
job spans tape, the operation would remain as POSITIONING until the job
completes.
--------------------------------------------------------------------------------
Etrack Incident = ET831231
Associated Primary Etracks = ET613789

Description:
Oracle and Informix restores may hang or fail (via a timeout). In one
situation bptm log would contain the following message:

08:40:54.944 [20370] <2> mpx_read_backup: waiting for children to
terminate so exit status can be sent to bpbrm

In another situation the bpbrm log would contain the following message:

16:13:00.835 [173273] <8> bpbrm process_media_msg: unknown media message:
RCD_STOP_DB_RESTORE_STR
--------------------------------------------------------------------------------
Etrack Incident = ET831977

Description:
When an inline tape copy job failed due to un-availability of resources,
the reason string was not displayed in jobd for all copies.
--------------------------------------------------------------------------------
Etrack Incident = ET832116
Associated Primary Etracks = ET829088

Description:
Calendar schedules would not run if another backup ran the same calender
day, even if the backup was in a window that opened on the previous day.

Workaround:
To avoid this issue, use a frequency scheduling of 24 hours.
--------------------------------------------------------------------------------
Etrack Incident = ET833015

Description:
A timeout of a clean or an unload when ltid was not running in verbose
mode would not be cleaned up.
--------------------------------------------------------------------------------
Etrack Incident = ET831472

Description:
NBPEM and NBJM code did not handle exceptions from all ORB calls.
--------------------------------------------------------------------------------
Etrack Incident = ET833885
Associated Primary Etracks = ET833782

Description:
After a pem crash with multistreamed jobs active, the job may not get
scheduled to run again.
--------------------------------------------------------------------------------
Etrack Incident = ET834141

Description:
NBJM would crash on shutdown if there was an active connection in the
connection factory and the timing was such that one thread was destroying
the connection factory while another was working with the connection object.
--------------------------------------------------------------------------------
Etrack Incident = ET834475

Description:
NetBackup Job Manager no longer hangs while running backups for clients
with throttling configured.
--------------------------------------------------------------------------------
Etrack Incident = ET834802

Description:
Catalog recovery from a hot catalog backup would fail with the following
error when the entry for EMMSERVER in bp.conf was different than the
SERVER name for the master server, but, they were actually the same
machine. This would occur when there were two NICs in the master server.

"Failed to find last NBDB backup image record for client serverName
with policy policyName (227)"
--------------------------------------------------------------------------------
Etrack Incident = ET834080
Associated Primary Etracks = ET646858

Description:
A change has been that keeps a bogus STU (such as, a STU pointing to
non-existing device) from causing the NetBackup Resource Broker's cache
to become invalid.
--------------------------------------------------------------------------------
Etrack Incident = ET831475

Description:
Changes were made that enable Vault VCCS Portal libraries to handle
exceptions such as, CORBA::Exception.
--------------------------------------------------------------------------------
Etrack Incident = ET832946

Description:
Changes were added that eliminate the possibility of a user not being
able to login to NOM. This intermittent problem would cause the NOM user
interface to become unusable until it was restarted.

Workaround:
NOM can run as many as five reports simultaneously. If you try to run a
sixth report, the report request will go into a queue. The report will
start running only after one of the previous reports completes running.
This delay may cause you to beleive that the run report page in the NOM
user interface has hung.

The pie charts you see on the overview pages are a type of graphical
report. So, if five reports are already running, instead of seeing
pie-charts, you will see the message, �pie charts unavailable,� message on
the overview screens.
--------------------------------------------------------------------------------
Etrack Incident = ET836865

Description:
A change was made to resolve and issue that caused database backups to fail
with a status 13 (file read failed) error. The Job Details would show the
following types of messages:

Error bpbrm (pid=xxxx) socket read failed: errno = 131 - Connection reset
by peer
end writing; write time: 2:04:24
file read failed (13)
--------------------------------------------------------------------------------
Etrack Incident = ET837124

Description:
A change was made that resolves an issue that caused scheduled jobs to not
run.
--------------------------------------------------------------------------------
Etrack Incident = ET837779

Description:
Performing an "Unmap All" operation on a Solaris 10 client configuration
which contains a zones configuration will fail with exit status 252.
--------------------------------------------------------------------------------
Etrack Incident = ET829247

Description:
The vmoprcmd -devmon command may incorrectly display multiple drive paths
under a drive name.
--------------------------------------------------------------------------------
Etrack Incident = ET834952

Description:
When a longer frequency backup (such as a full backup) for a client failed
and could not be retried due to an exceeded failure history, nbpem would
initiate a shorter frequency backup, if one was configured and due at the
same time (such as an incremental). This job would also be retried if it
failed.

A change was made to the failure history to resolve this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET831460

Description:
Changed the location of the pempersist file so it is shared in a
clustered setup.
--------------------------------------------------------------------------------
Etrack Incident = ET837657

Description:
Some of the connections between the media server and client were not
affected by the CLIENT_CONNECT_TIMEOUT configuration value for database
agent backups. A hard-coded value of one minute was used instead.

This patch fixes the media server to use the CLIENT_CONNECT_TIMEOUT for
database agent backups as well as file system backups.
--------------------------------------------------------------------------------
Etrack Incident = ET840396

Description:
The Cluster Server Agent for Storage Migrator now installs on Solaris 10.
--------------------------------------------------------------------------------
Etrack Incident = ET840432
Associated Primary Etracks = ET838346

Description:
After a status 129 failure occurred, the retry was not picking a different
DSU in the stunit group.
--------------------------------------------------------------------------------
Etrack Incident = ET837609

Description:
A problem existed that caused jobs to be stuck in a waiting-for-retry state
for multiple days.
--------------------------------------------------------------------------------
Etrack Incident = ET841713

Description:
A change was made to correct the NetWare Loadable Module (NLM) Version
numbers from 5.0 to 6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET840460
Associated Primary Etracks = ET837021

Description:
The pending requests output of the vmoprcmd command no longer prints the
volume group for pending mount requests.
--------------------------------------------------------------------------------
Etrack Incident = ET841261

Description:
Vault sessions and ejects failed under NetBackup Access Control (NBAC).


--------------------------------------------------------------------------------
Etrack Incident = ET841643

Description:
bpmedialist -mcontents command terminated abnormally without notifying NBJM.
The job was declared abandoned after a while. As a result, NBJM failed on
an assertion check while cancelling the job.

After NBJM was restarted, NBPEM could not communicate with NBJM because all
of its threads were hung on a corba call to ping NBJM.
--------------------------------------------------------------------------------
Etrack Incident = ET841711

Description:
In certain conditions where bpmedialist does not get updates from bptm for
more than an hour, NBJM could terminate bpmedialist.
--------------------------------------------------------------------------------
Etrack Incident = ET837077

Description:
A problem existed that caused a catalog backup child job to fail and
remain in "Waiting for Retry" state indefinitely.

Workaround:
To avoid this issue, cancel the job.
--------------------------------------------------------------------------------
Etrack Incident = ET839365
Associated Primary Etracks = ET829855

Description:
The status backup report would report no data or it would report data only
with the wrong hostname.
--------------------------------------------------------------------------------
Etrack Incident = ET844039

Description:
In some instances, it is possible for a media server to have a robotic
drive configured but no corresponding robot entry in the database. In this
case, the device monitor request to the database is "short-circuiting". In
other words, whatever has been retrieved up until the offending record is
displayed, subsequent data is lost.

The fix for this problem is to mark the drive as "AVR" control and continue
normally. Therefore, if such a configuration occurs, these drives will
always have a status of robot DOWN. If you see this, you need to make sure
that the host for the "AVR" drive path has a robotic entry which matches
the drive's residence.
--------------------------------------------------------------------------------
Etrack Incident = ET844043

Description:
When device configuration changes are made, occasionally this will require
that all hosts sharing a drive, be restarted. Previous to this patch, the
device monitor is showing "RESTART" for all the paths - even those paths on
hosts that have had their Device Management Service or Daemon restarted.
This patch changes the device monitor so that the RESTART status is
displayed only for the paths on hosts whose Device Manager have not yet
been restarted.

NOTE: NetBackup may still not use this drive until all hosts' Device
Manager have been restarted.

In addition, the unsupported option for vmoprcmd "-reset_ltid_restarted_bit"
has been changed so that it works on back-rev media servers. Also, a new
option "-get_host_restart_list" has been added to provide a list of all
the hosts for which NetBackup is waiting to have the Device Manager
restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET842109

Description:
After executing bpdown or NetBackup stop, the bpdbm cleanup process was
continuing to run. It was attempting to notify other processes that were
terminated. With this fix, the bpdbm cleanup process checks the status of
the parent bpdbm process and terminates the cleanup if the parent bpdbm
process has been terminated.

Workaround:
To resolve this issue, make sure cleanup is not running before you shut
down NetBackup. You can so this by running bpps and looking for a child
bpdbm process, or by inspecting the bpdbm log for Q_IMAGE_DELETE queries
that have not finished.
--------------------------------------------------------------------------------
Etrack Incident = ET843993
Associated Primary Etracks = ET795418

Description:
It was possible to create a media server and cluster with the same name.
However, depending on which one was used first could create problems at
run time.

Workaround:
To avoid this issue, clean the database with the nbemmcmd command or
direct SQL.
--------------------------------------------------------------------------------
Etrack Incident = ET846970

Description:
NBRB would crash in some situations while running duplicate, synth or
Inline Tape Copy jobs.



*****************************************
*****************************************

The following items are BBS/BMR specific:

*****************************************
*****************************************
--------------------------------------------------------------------------------
Etrack Incident = ET589226
Description:
Restore logs on the master server did not contain the time value. Only the
date was shown.
--------------------------------------------------------------------------------
Etrack Incident = ET573412
Description:
You can now save changes to a Bare Metal Restore configuration that contains
Chinese characters.
--------------------------------------------------------------------------------
Etrack Incident = ET594173
Description:
Unfriendly warnings are no longer displayed during restores.
--------------------------------------------------------------------------------
Etrack Incident = ET598114
Description:
bmrsavecfg failed to collect system information on servers that were
running some versions of the MSSQL server.
--------------------------------------------------------------------------------
Etrack Incident = ET575186
Description:
BMR Windows DSR would fail if the restoring server had installed some
of the Microsoft security patches.
--------------------------------------------------------------------------------
Etrack Incident = ET409317
Description:
Customers should not use "BmrCreatePkg" utility to add service packs
to the server. This fix displays this information on the BmrCreatePkg
user interface to remind them.
--------------------------------------------------------------------------------
Etrack Incident = ET567501
Description:
External Procedures failed to execute on a Windows 2003 SP1 RC2 client with
all security updates installed.
--------------------------------------------------------------------------------
Etrack Incident = ET611820 ET641223
Description:
A new wizard has been added to the Windows Boot Server Assistant. This new
wizard enables users to create ISO CD/DVD images for the Fast Windows
Restore Boot CD.
--------------------------------------------------------------------------------
Etrack Incident = ET512915
Description:
All Windows restores will finish after the first login that requires
Administrator privileges; therefore, a special first-login screen appears
for the Administrator to login.
--------------------------------------------------------------------------------
Etrack Incident = ET564236
Description:
There was no way to change the boot server's IP address in the database.
This problem occurred when the boot server had multiple interfaces, and the
default address chosen by BMR was not usable.
--------------------------------------------------------------------------------
Etrack Incident = ET622214
Description:
After a dissimilar system restore on Windows 2000 systems, an excessive
number of "New Hardware Found" dialogs appeared. This was because the
"DevicePath" value in the registry was incorrectly set.

Workaround:
To avoid this issue, customers should click on "Cancel" for those dialogs.
--------------------------------------------------------------------------------
Etrack Incident = ET573733
Description:
When modifying a configuration, and when mapping a NIC from another NIC,
only IP-related information should change, not the description or the
PNP IDs.
--------------------------------------------------------------------------------
Etrack Incident = ET622074
Description:
The Media Boot Shared Resource Tree (SRT) creation failed if the SRT was
too large fit on a CD media.

Additional Notes:
Media Boot support is enhanced in this patch to include support for
DVD media.
--------------------------------------------------------------------------------
Etrack Incident = ET622102
Description:
Added support for the following:
- Bare Metal Restore Support for Solaris 10
- Bare Metal Restore Support for Veritas Volume Manager 4.1 in Solaris
--------------------------------------------------------------------------------
Etrack Incident = ET765357
Description:
Restoring from a NetBackup MP4 master server will initiate autoDDR on an
AIX 5.3 client that is running NetBackup 6.0MP2 or MP3.

Additional Notes:
AIX 5.3 clients running NetBackup 6.0 MP2 and MP3 should be upgraded to
NetBackup 6.0 MP4 and backed up immediately after installing MP4 on the
master server.

Workaround:
To restore a client that is still at NetBackup 6.0 MP2 or MP3, you must
use a NetBackup 6.0 MP4 Shared Resource Tree (SRT) to discover a
configuration from the hardware (or use the configuration generated by
autoDDR with a NetBackup MP4 SRT), and then use DDR with this
configuration to restore the client.
--------------------------------------------------------------------------------
Etrack Incident = ET768305
Description:
For Windows clients, after initializing disk information in a
configuration, discovered disks were blank and unrestricted. Even if the
user did not map any volumes to those disks, any discovered volumes on
those disks were erased unless the user restricted those disks.

With this change, discovered disks are automatically restricted when a
configuration is initialized. The user must manually unrestrict those
disks before mapping volumes to them.

Workaround:
If the user wants to prevent the restore process from altering unused
disks, the user should edit the configuration and mark those disks as
restricted.
--------------------------------------------------------------------------------
Etrack Incident = ET769511
Description:
An AIX client that was utilizing VxVM 4.x disk groups could not perform
dissimilar disk mapping operations on its configuration using a
discovered configuration because of incomplete physical volume information
stored in the discovered configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET774743
Description:
Solaris client configurations that contained a �rootdg� on a slice Veritas
Volume Manager (VxVM) configuration on a full disk, fail to self-restore
and are forced into auto-DDR mode at restore time.
--------------------------------------------------------------------------------
Etrack Incident = ET779084, ET771267, ET772825, ET772735, ET773720
Description:
A new version of the BMR Windows Fast Recovery Disk is provided
in this MP. Users should re-run the Boot Server Assistant from the
Start Menu, and follow the menus to create a new CD/DVD ISO image.
--------------------------------------------------------------------------------
Etrack Incident = ET786931
Description:
A Solaris client self-restore can fail under conditions where the original
live client had file systems that were not mounted when the backup was
taken.
--------------------------------------------------------------------------------
Etrack Incident = ET783882
Description:
If a Solaris 10 boot server is hosting a Solaris 8 or Solaris 9 SRT, and if
the first "Prepare to Restore" operation using this boot server does not
use a Solaris 10 SRT, the "Prepare to Restore" operation will fail.

Workaround:
To avoid this issue, start the tftp service by hand.
--------------------------------------------------------------------------------
Etrack Incident = ET788817
Description:
BMR did not collect the configuration information correctly on machines
running in a non-English locale.
--------------------------------------------------------------------------------
Etrack Incident = ET792676
Description:
Large file, file systems were not being created properly on HP-UX 11.i
systems.
--------------------------------------------------------------------------------
Etrack Incident = ET796403
Description:
A Linux client self-restore could fail because of invalid file system
configuration data. This would occur when the running client had file
systems mounted on device names that were long enough to cause the output
of the "df" command to span two lines.
--------------------------------------------------------------------------------
Etrack Incident = ET801098
Description:
Linux client configuration editing allows DDR mapping to disks that have
been restricted. In addition, there are no checks in place so that restores
are not allowed on disks that are restricted.
--------------------------------------------------------------------------------
Etrack Incident = ET820368
Description:
External procedures no longer fail to run on Windows 2003 SP1, (with
security updates installed).
--------------------------------------------------------------------------------
Etrack Incident = ET801694
Description:
Under extremely rare conditions, the bmrprep command fails when invoked
from the user interface but succeeds when invoked from the command line.
--------------------------------------------------------------------------------




=========
NB_60_3_M
=========

Etrack Incident = ET421741

Description:
A user-directed backup for Exchange Volume Shadow Copy Service (VSS)
Transportable failed with a status 200. To resolve this issue, the Policy
Execution Manager (PEM) was changed to start a child Exchange VSS
Transportable job instead of another parent job.

Additional Notes:
Refer also to ET612121.
--------------------------------------------------------------------------------
Etrack Incident = ET630389

Description
The job params file had un-initialized fields that caused nbjm to crash
when it read the file.
--------------------------------------------------------------------------------
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://entsupport.symantec.com/docs/283726
================================================================================




=========
NB_60_2_M
=========

Etrack Incident = ET425118

Description:
An issue in bpdbm caused the cleanup process to halt on Windows platforms
and prevented jobs from running.
--------------------------------------------------------------------------------
Etrack Incident = ET426750

Description:
A downed or disabled media server will no longer block the entire DA
thread pool.
--------------------------------------------------------------------------------
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 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 = ET411505

Description:
On an Exchange 2000/2003 server with Circular logging enabled on a storage
group, a differential backup would fail to backup any log files. The debug
log for bkar would log the following error:

3:09:43.796 PM: [4556.3884] <2> ov_log::V_GlobalLog: ERR -
BEDS_AttachToDLE():FS_AttachToDLE() DeviceName:'\Microsoft
Information Store\Test' Failed! (0xFFFFFE4C: The operation cannot be
performed since circular logging was enabled.

However, the backup will succeed with a status 0.
--------------------------------------------------------------------------------
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 = ET421491

Description:
Fixed a memory corruption issue with a char buffer that crashed bpbkar32.
--------------------------------------------------------------------------------
Etrack Incident = ET412790

Description:
When performing an incremental backup of Exchange mailboxes, a status 0
may be reported for the backup even though no data was actually backed up.
This occurred when the Exchange mailbox logon failed.
--------------------------------------------------------------------------------
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 = ET296533

Description:
Enhancements have been added that provide the following:
- The option to change the replica ID of unlogged databases
- The option to skip the recovery of logged databases

Additional Notes:
Users can use the touch file at <NetBackup Install Path>\LOTUS_NO_RECOVERY
to control the recovery of logged Lotus Notes databases. During restore,
the presence of the file bypasses the recovery of logged Lotus Notes
databases.
--------------------------------------------------------------------------------
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 = ET422723

Description:
If the Exchange VSS writer is in an error state with
VSS_E_WRITEERROR_RETRYABLE as the last error during an Exchange VSS
transportable backup, the error is ignored and the backup continues.
However, NetBackup will not return status to Exchange during
BackupComplete processing, which leaves Exchange in a backup-in-progress
state. Exchange never truncates log files. The next incremental backup
attempt fails and Exchange produces a message that a Full backup is
required rather than a incremental.
--------------------------------------------------------------------------------
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 = ET415504

Description:
Ensure primary and non-primary source images on disk are sorted correctly
for duplication; to avoid creation of extra duplication jobs.
--------------------------------------------------------------------------------
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 = ET411631

Description:
Running bmrconfig on an AIX client no longer causes an error when mapping
a striped volume that needs more disks than available columns.
--------------------------------------------------------------------------------
Etrack Incident = ET409373

Description:
Could not restore an AIX client if the boot logical volume was not hd5.
--------------------------------------------------------------------------------
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 = ET414241

Description:
Mapping a Solaris disk or Solaris Volume Manager managed disk failed if
the source disk was not using slice 2 as a backup slice and the disk was
filled to capacity.

Workaround:
To avoid this issue, unmap slice 2 from the target disk after configuration
initialization and before you attempt to map to the source disk.
--------------------------------------------------------------------------------
Etrack Incident = ET412755

Description:
Mapping Windows spanned volumes onto more than one disk no longer results
in an error message that complained about inadequate free space even
though adequate free space existed. The error message has the following
format: "A subdisk of length X does not fit on disk Y", where X is some
number and Y is a disk name.
--------------------------------------------------------------------------------
Etrack Incident = ET414965

Description:
A �prepare to restore� operation fails on a Solaris client that has a
configuration containing a Solaris Volume Manager disk set that has no
metadevices in it.

Workaround:
To avoid this issue, remove the empty Solaris Volume Manager disk set from
the configuration and rerun the �prepare to restore� operation.
--------------------------------------------------------------------------------
Etrack Incident = ET424767

Description:
During Solaris client restoration, disks allocated for Solaris Volume
Manager disk sets were not being formatted after being added to the disk
set causing failures to create metadevices.
--------------------------------------------------------------------------------
Etrack Incident = ET416705

Description:
Restoration or Dissimilar Disk Restore (DDR) mapping of a Solaris Volume
Manager one-way mirror metadevice no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET415984

Description:
Resizing a VxVM volume on an encapsulated disk that contained a B0 subdisk
in the source disk no longer fails.
--------------------------------------------------------------------------------
Etrack Incident = ET366934

Description:
Disks with only swap volumes/partitions on them were not being considered
as system-critical disks during restoration.
--------------------------------------------------------------------------------
Etrack Incident = ET408810

Description:
When performing a Dissimilar Disk Restore (DDR) mapping, the user could
not remove Linux partitions, multi-devices, or physical volumes whose
components (usually partitions) were not the last component on the disk.

For example, if the disk had partitions A, B, and C, then neither
partition A or B could be removed. The user had to start removing
partition C followed by partition B, and then partition A.

Additional Notes:
An extra message was added in case a failure occurred. The message reads:
"The partition <PART NUMBER> could not be removed."
--------------------------------------------------------------------------------
Etrack Incident = ET426030

Description:
The bmrsavecfg UNIX command removes the directory,
/usr/openv/netbackup/baremetal/client/data upon each invocation which
then causes the ClientCustomFiles feature to break because it is contained
in this same directory.
--------------------------------------------------------------------------------
Etrack Incident = ET425710

Description:
A Solaris machine fails to boot after restoration because of device major
number entries are not being synchronized between /dev and /devices device
special files and their specifications in the file /etc/name_to_major.

Workaround:
To avoid this issue, boot the machine into single-user modeand synchronize
the device major number entries with the device special files in /dev and
/devices.
--------------------------------------------------------------------------------
Etrack Incident = ET401379

Description:
If the Linux root file system (/) is mirrored using a Multi Device and
this mirror is broken (converted to a RAID 0 device) using Dissimilar
Disk Restore, the kernel will panic on boot after a restore.


--------------------------------------------------------------------------------
Etrack Incident = ET413615

Description:
When mapping a volume, that is not a vendor or system volume, in a
Dissimilar System Restore configuration the �Map� option is now always
enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET273610

Description:
The instructions on how to perform Dissimilar Disk Restore (DDR) have been
enhanced when a difference in the saved disks and the existing ones is
detected.

Additional Notes:
The instructions for performing DDR while the client is restoring were
reworded to:

The discovered disks in this client are different than the ones specified
in the configuration that is being restored. For this reason, the volume
layout needs to be changed to fit in the existing hardware. To change the
volume layout you have two options: map locally or map on the main server.
If you map locally a dialog will be started to perform the changes but the
screen resolution may not be adequate for more than three disks. If you
decide to map on the master server, the Change Configuration dialog has to
be used to modify the configuration with this new hardware. Please note
that in the master server, the configuration will be ready for editing and
once you accept the changes, by clicking the OK button, this restore
procedure will continue.

--------------------------------------------------------------------------------
Etrack Incident = ET409857

Description:
Changing the size of a Windows mirrored system volume no longer causes
the mirrored slices to be different sizes.
--------------------------------------------------------------------------------
Etrack Incident = ET409679

Description:
When removing a Windows disk that contains the secondary mirror of a
mirrored system volume, the system volume is correctly changed to a
concatenated volume instead of a primary partition.
--------------------------------------------------------------------------------
Etrack Incident = ET416985

Description:
The NetBackup Oracle agent would not recognize the RMAN PARMS option.
--------------------------------------------------------------------------------
Etrack Incident = ET338590

Description:
Mapping a Windows-striped volume will now correctly show the amount of
space used in the target volume.
--------------------------------------------------------------------------------
Etrack Incident = ET410054

Description:
Mapping a Windows vendor partition to the target layout is now disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET416745

Description:
The Solaris Volume Manager mirror read/write and raid5 interlace options
are now correctly preserved.
--------------------------------------------------------------------------------
Etrack Incident = ET416585

Description:
During a Dissimilar System Restore (DSR) of a Windows client, an
administrator is required to login on the final system boot to complete
DSR tasks and cleanup. The final system boot login prompt does not display
the background message:

"BMR Restore underway...Please login as administrator to complete the
restore."

Additional Notes:
The binary bmmrst.exe, is only used by clients in the BMR restore
environment. After this maintenance pack is applied to a BMR Boot
Server, previously existing Shared Resource Trees managed by the Boot
Server are updated with the �Add NBU MP� option (from the Shared Resource
Tree Administration Wizard). Shared Resource Trees created after the
BMR Boot Server has applied this maintenance pack do not need to be
updated.
--------------------------------------------------------------------------------
Etrack Incident = ET424686

Description:
After a client has been restored and BMR is performing final clean-up
tasks, the C:\Program Files directory may be removed if no network
connectivity is available.
--------------------------------------------------------------------------------
Etrack Incident = ET408806

Description:
On Windows platforms, the restoring client VxUL logging level was too
low , resulting in not enough diagnostic messages being generate if a
problem arises.
--------------------------------------------------------------------------------
Etrack Incident = ET400222

Description:
The Recovery Report IM file for container-based Vaults no longer prints
a "(null)" string in second field.
--------------------------------------------------------------------------------
Etrack Incident = ET410163

Description:
Windows BMR Media boot attempts to copy NetBackup files from the boot
server. In addition, the BMR client restoration would fail if the
network or the SRT was not available to use.
--------------------------------------------------------------------------------
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 = ET421068

Description:
Some databases with special characters ((for example, '[', '\', ']', '^', '_', and '`')
are not shown in the MSSQL Server Restore user interface.

Workaround:
Databases with the above characters can be restored using a batch file
instead of the GUI.
--------------------------------------------------------------------------------
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 = ET429575

Description:
Certain types of backups such as partial database or grouped advanced
client backups caused the SQL Server agent user interface to crash when
browsing for restore images. This problem was confined to SQL Server 2005.
--------------------------------------------------------------------------------
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 = ET497273

Description:
An error message was received when performing a DB2 roll-forward after a
restore. The following is an example of the error message that was
received:

$ db2 rollforward db sample to end of logs and stop
SQL1268N Roll-forward recovery stopped due to error "28" while
retrieving log file "S0000001.LOG" for database "SAMPLE" on node "0"
--------------------------------------------------------------------------------
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 = ET395667

Description:
The return date in the Container Inventory Report no longer displays as
�DATE ERROR� on HP-UX IA64 (Itanium) master servers.
--------------------------------------------------------------------------------
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 = ET496509

Description:
A change was made to resolve an issue that caused the Exchange Restore
operation to fail.
--------------------------------------------------------------------------------
Etrack Incident = ET418052

Description:
vlteject does not show messages on console during Eject
--------------------------------------------------------------------------------
Etrack Incident = ET420766

Description:
The vmoprcmd -devmon ds command is failing with a Corba exception.
--------------------------------------------------------------------------------
Etrack Incident = ET430826

Description:
Binding to a socket already in use would cause the error,
�10061 � WSAECONNREFUSED� to appear in the bpcd log.

Workaround:
To avoid this issue, use vnetd.
--------------------------------------------------------------------------------
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 = ET495831

Description:
After the file copy portion of Windows XP setup has been completed, an
error message indicating an internal set-up error occurs. The error is
similar to the following:

�Setup cannot set the required Windows XP configuration information.�
--------------------------------------------------------------------------------
Etrack Incident = ET492674

Description:
The SQL server inhibits a transaction log backup if the database is
currently in the process of being backed up. In this situation, the log
backup should timeout during the VDI connection and the NetBackup SQL
agent process should continue on and process the next backup (assuming
there is more than one operation in the batch file). Instead,
NetBackup SQL agent process would hang indefinitely and not process any
subsequent operations in the batch file.

With this fix, the agent waits for SQL Server to time out (VDI timeout),
typically, after five minutes. Then the agent proceeds to process any
subsequent commands in the batch file.
--------------------------------------------------------------------------------
Etrack Incident = ET500408

Description:
Oracle backups would fail because bphdb.exe quit with an application
error. This problem was encountered when using the following agents :

- ORACLE
- SAP
- SYBASE
- DB2
--------------------------------------------------------------------------------
Etrack Incident = ET402265

Description:
After a Bare Metal Restore (BMR) restore finished, the MSSQL Server Image
path might be incorrect. To address this issue, the following message has
been added in bmrsavecfg.xml.

bmrsavecfg.xml:BMRSAVECFG_ERROR_SAVING_SQL_IMAGE_PATH
--------------------------------------------------------------------------------
Etrack Incident = ET495250

Description:
Eject for ALL vaults (consolidated) no longer fails with the error 293
when there are mixed media types.
--------------------------------------------------------------------------------
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 = ET499028

Description:
An Exchange VSS Transportable snapshot backup using an Exchange cluster
no longer fails with a status 156.
--------------------------------------------------------------------------------
Etrack Incident = ET506650

Description:
In the repair environment, the Windows Bare Metal Restore user interface
displays the hot-fix executable names as they are installing.
--------------------------------------------------------------------------------
Etrack Incident = ET404604

Description:
You can now remove newly added Hosts from non-current configurations.


--------------------------------------------------------------------------------
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 = ET299908

Description:
The IMReport file is no longer empty if the profile has the
media-going-offsite report function disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET496560

Description:
The NetBackup Service Layer (NBSL) no longer causes a core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET425114

Description:
A potential looping bpbar client process no longer occurs if an
Microsoft Exchange Mailbox SIS attachment cannot be accessed.
--------------------------------------------------------------------------------
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 = ET506663

Description:
A Point in Time (PIT) retrieval of a UNIX client configuration being
managed by a Windows Master BMR server failed and produced the following
error message:

"The requested operation could not be completed. The server returned
code 1."
--------------------------------------------------------------------------------
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 = ET492456

Description:
An incorrect message was added in the log file when the External Procedures
option was chosen at "Prepare to Restore" time:

"External Procedures Notify: You have chosen to run External Procedures,
but no external procedures are defined for client"
--------------------------------------------------------------------------------
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 = ET494397

Description:
The Vault user interface did not display the robot number and robotic
volume group when trying to add a new robot or vault for vault.
--------------------------------------------------------------------------------
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 = ET429580

Description:
The MS SQL user interface no longer aborts when retrieving properties of
database names that contained special characters or were SQL keywords, for
example, databases with names similar:

- TABLE
- USER
- MAX'S
--------------------------------------------------------------------------------
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 = ET506568

Description:
Restoring a partial database image (or a partial differential image) would
fail with the error message:

�Filegroup� cannot be restored because it does not exist in the backup set.

Also, the property sheet for a partial backup image did not display the
list of file groups contained in the partial backup.

Additional Notes:
Create a partial backup of a db full text indexing and try to restore.
--------------------------------------------------------------------------------
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 = ET506727

Description:
After applying the MS05-051 security patch, clients that were restored
using BMR would encounter problems with the Active Directory.

Workaround:
To avoid this issue, fix the permissions for the WINDOWS\Registration
directory and its files.
--------------------------------------------------------------------------------
Etrack Incident = ET412241

Description:
Vault would mark DSSU and DSU images for expiration after a successful
duplication. However, the DSSU images should not have been marked, because
they would expire according to DSSU schedule/configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET493839

Description:
Vault would not put tapes to the wrong volume group if the volume
database host (or EMM server) was different from the robotic control host
while running a vault session.
--------------------------------------------------------------------------------
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 = ET414682

Description:
This fix guarantees the capability to restore a multiplexed SQL Server
backup by loading each stream from the same tape sequentially. That is,
the next stream will be started after the previous one has completed.

To use this function, modify the generated restore batch file by modifying
the keyword/value 'STRIPES N' (where N is the number of streams) to
'STRIPES 1'.

In addition to providing guaranteed demultiplexing for SQL Server
restores, you can also use this functionality to restore a multi-streamed
(non-multiplexed) backup with fewer tape devices than it was backed up
with. For example, if a database is backed up with five tape devices, then
it can be restored with two devices by modifying the STRIPES parameter in
the batch file to 'STRIPES 2'.

CAUTION: If you use multiplexing, then always set the STRIPES parameter
to 1.

NOTE: This fix requires SQL Server 2000 or greater.
--------------------------------------------------------------------------------
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 = ET507678

Description:
Installation of NetBackup Maintenance Packs into a BMR Shared Resource
Tree(SRT) no longer fail with an error indicating that gunzip is missing
from the SRT.

Additional Notes:
Solaris Shared Resource Trees need SUNWgzip to be installed into the SRT
as an additional package before NetBackup 6.0 MP2 can be installed into
the SRT.
--------------------------------------------------------------------------------
Etrack Incident = ET509515

Description:
A change was made to enable version compatibility checking between
bmrsavecfg and the import configuration procedure in bmrd.

Additional Notes:
Clients that are running later versions of NetBackup than the version on
the master server with which they are associated will have failed
bmrsavecfg jobs. Subsequently, no configuration for a backup will be
saved. There will be a message produced in the "Detailed Status" for the
bmrsavecfg job that states the incompatibility.
--------------------------------------------------------------------------------
Etrack Incident = ET499203

Description:
bpdbjobs -all_columns takes a segmentation fault in either the FreeJobs()
or PrintJobs() function with a stack overflow.
--------------------------------------------------------------------------------
Etrack Incident = ET424966

Description:
A problem exists if you have "Stage a full recovery" selected and try to
restore a database and the latest transaction log from the user interface,
and a transaction log backup occurs between a full and incremental backup.
For example, if backups occurred in the following order, the result would
be a failed restore:
1st - A FULL backup
2nd - A transaction log backup
3rd - An incremental backup
4th - Another transaction log backup

The user interface automatically includes the transaction log backup taken
between the Full backup and the INCREMANTAL backup in its list of objects
to restore and would attempt to restore all four backups in the order
presented above and result in a failed restore. The proper sequence of
restore operations should be to restore the full back up first, followed
by the incremental backup, and lastly, all transaction log backups.
Changes contained in this pack resolves this issue.

Workaround:
To avoid this issue, restore the database by running,
�restore database <name> with recovery,� after the restore.
--------------------------------------------------------------------------------
Etrack Incident = ET511981

Description:
It is now possible for SAN media servers to be used as write hosts for
duplicate jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET420394

Description:
The SQL user interface would abort when attempting to open the restore
browser. The following conditions applied:

1. The image set included an SQL snapshot backup.
2. The platform was AMD64 or IA64.
--------------------------------------------------------------------------------
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 = ET403446

Description:
Users can now backup/restore SAP files with names that contain multi-byte
characters on Windows platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET494572

Description:
Users can now back up and restore DB2 table spaces that are created for
Database Managed Space (DMS) containers. DB2 DMS support includes
stream-based and Advanced Client methods.
--------------------------------------------------------------------------------
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 = ET416679

Description:
This pack contains fixes for multiple driver-related problems in
NetBackup 6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET513419

Description:
NBNos no longer runs in single-threaded mode only.
--------------------------------------------------------------------------------
Etrack Incident = ET512920

Description:
If the customer's Windows system is using a configuration other than the
default configuration (ControlSet001), after a BMR restore, unexpected
behavior may occur, such as unexpected drive letter assignments or even a
blue screen of death.
--------------------------------------------------------------------------------
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 = ET514399

Description:
When running backups with VSP enabled for open file backups, the client
machine would intermittently lock and become unresponsive during a backup.
The only workaround for this issue is a reboot of the machine.
--------------------------------------------------------------------------------
Etrack Incident = ET499144

Description:
When running multi-streamed Windows Open File Backup backups, jobs would
fail with a status 200 error.
--------------------------------------------------------------------------------
Etrack Incident = ET426647

Description:
The SAP Agent now supports Split-Mirror Backups through the NetBackup
Advanced Client and is available in this NetBackup 6.0 MP2 release.

The following list identifies the key Advanced Client features that are
now supported as well as the benefits that SAP customers will recieve:

- Off-host Backup - Backup overhead moves critical systems to an
Alternate Data mover

- Block-Level Incremental Backup and Recovery - Less data leads to
high-performance data protection.

This feature is supported in: Solaris, HP-UX PA Risc, AIX5 and
Windows 2000/2003 platforms. Refer to the compatibility support matrix
for applicable methods in the above platforms.

For more detailed information about this new feature, refer to the
following TechNote on the Symantec Support Web site.

http://entsupport.symantec.com/docs/282337
--------------------------------------------------------------------------------
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 = ET423712

Description:
Performing an SQL 2005 transaction log backup that does not truncate
failed with verification enabled. In addition, the OBDC reported
conflicting options.

Workaround:
To avoid this issue, perform transaction backups that do not truncate
the log without verification enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET512479

Description:
Eseutil no longer fails a consistency check for the Exchange DB or the
log files that exist on a volume mount point.
--------------------------------------------------------------------------------
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 = ET494850

Description:
Recovery Storage Groups (RSG) could get backed up improperly and cause a
direct restore to a defined Recovery Storage Groups to fail.

Workaround:
To avoid this issue, restore to the original storage group and let the
Microsoft Extensible Storage Engine (ESE) handle the restore redirection.
In addition, exclude RSG from backup list.
--------------------------------------------------------------------------------
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 = ET518105

Description:
If an Exchange restore takes place with the Databases still mounted, no
good indication was reported to the tar log or progress monitor.
--------------------------------------------------------------------------------
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 = ET517992

Description:
Vault no longer reports an error exit status (351) for a successfully
completed preview session.
--------------------------------------------------------------------------------
Etrack Incident = ET516880

Description:
Vault can fail while logging very long strings.

Workaround:
To avoid this issue, disable the Vault logging.
--------------------------------------------------------------------------------
Etrack Incident = ET494433

Description:
When attempting to perform an Exchange VSS restore, the following error
would be written in the tar32 log:

Tar log:
8:05:02.461 AM: [9320.4644] <2> ov_log::V_GlobalLog: INF - Info: Creating
Writer User?Data\Exchange Server
8:05:02.555 AM: [9320.4644] <2> ov_log::V_GlobalLog: INF - Info: Opening
Writer
User?Data\Exchange Server
8:05:02.555 AM: [9320.4644] <2> ov_log::V_GlobalLog: INF - StreamInfo
Id:SCWD
FSAttrib:0x0 FSAttrib:0x0 CAlgor:0x0 Flags:0x0 Size:24380
8:05:02.555 AM: [9320.4644] <2> ov_log::V_GlobalLog: INF-Shadow Copy Writer

Metadata
8:05:02.555 AM: [9320.4644] <2> ov_log::V_GlobalLogEx: ERR -
exchange_shadowcopy_access::V_Write:Shadow Copy Stream ID is unknown!
--------------------------------------------------------------------------------
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 = ET520844

Description:
Vault might incorrectly flag valid images that have zero copies, as
inconsistent. Vault should ignore these types of images.
--------------------------------------------------------------------------------
Etrack Incident = ET520188

Description:
Vault could fail to suspend the current session's media immediately
after duplication even if it was configured to do so.
--------------------------------------------------------------------------------
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 = 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 = ET327111

Description:
Prepare-to-Restore failures no longer display specific error messages on
the NetBackup Administration Console, rather than indicate that the user
should get the error details from the server logs.
--------------------------------------------------------------------------------
Etrack Incident = ET492907

Description:
You can now add Maintenance Packs and Language Packs to Shared Resource
Trees.
--------------------------------------------------------------------------------
Etrack Incident = ET517030

Description:
Some Ethernet DOS drivers failed when the slot number was specified in the
protocol.ini file. Such drivers required DevNum and BusNum to be
specified in the protocol.ini
--------------------------------------------------------------------------------
Etrack Incident = ET511350

Description:
You can now see the correct embedded package type in the Shared Resource
Tree properties dialog in the NetBackup Administration Console.

--------------------------------------------------------------------------------
Etrack Incident = ET508741

Description:
Robot Name is now displayed correctly in NOM user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET524600

Description:
Exchange Database restore can possibly write a transaction log file to the
wrong temp location with the wrong filename.

Workaround:
To correct this issue, use the following temp location:
c:\ instead of c:\temp.
--------------------------------------------------------------------------------
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 = 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 = ET521071

Description:
NDMP backups do not complete after an upgrade to NetBackup 5.1 or later.

This problem can occur when doing NDMP backups to a NAS device that is on
the other side of a firewall from NetBackup. An error occurs when
NetBackup attempts to connect to the NAS device to write the catalog
information (after the backup has completed), but the error is not
reported and the job never terminates. This pack contains a fix for the
error reporting.

Workaround:
To avoid the error caused by the inability to connect across the firewall,
add the following line to the netbackup/db/config/ndmp.cfg file.

NDMP_MOVER_CLIENT_DISABLE

This workaround will impact the performance of backups that have a large
number of files.
--------------------------------------------------------------------------------
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 = ET426054 ET526890 ET497175 ET527259 ET526743 ET536724 ET528536 ET536727 ET540200 ET535947
ET535943 ET536885 ET530704 ET543353 ET543793 ET544785 ET528150 ET537641 ET544785 ET528150 ET537641 ET563753
ET567293 ET

Description:
Port of Windows Server to 6.0MP2 on AMD64 architecture
--------------------------------------------------------------------------------
Etrack Incident = ET514701

Description:
Following an upgrade from NetBackup 4.5 to NetBackup 5.0/5.1, the
NetBackup MSSQL user interface would sometimes issue the following
error message when trying to browse NetBackup 4.5 images:

�Error encountered while trying to read database images�
--------------------------------------------------------------------------------
Etrack Incident = ET525104

Description:
Oracle users can now perform XML exports/imports on tables that contain
timestamps and interval data types.
--------------------------------------------------------------------------------
Etrack Incident = ET320480

Description:
This fix prevents a segmentation fault on Windows that can occur when
using the Backup, Archive, and Restore (BAR) user interface to access
multiple Oracle instances.
--------------------------------------------------------------------------------
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 = ET514064

Description:
Changes have been made to eliminate a code vulnerability that would lead
to a potential core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET525101

Description:
A change has been made to prevent any potential segmentation faults that
can occur on Windows when performing multi stream Oracle backups.
--------------------------------------------------------------------------------
Etrack Incident = ET412591

Description:
Oracle proxy backups, using multiple RMAN channels, fail with a
status 156, �snapshot error encountered.�
--------------------------------------------------------------------------------
Etrack Incident = ET527481

Description:
NBJM no longer leaks small amounts of memory while running multi-streamed
jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET494976

Description:
The backup no longer fails when backing up a directory that contains
special files such as named pipe, blockdevice, and chardevice. Another
type of special file is, TYPE=tar (path based FH).

Additional Notes:
Additional Notes:
The bpbrm log would show something similar to the following:

15:53:13.321 [14506] <16> bpbrm main: db_FLIST send failed:
file read failed (13)
--------------------------------------------------------------------------------
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 = ET513932

Description:
After upgrading to AIX 5.2 ML5, if the locale was set to non "C", vault
would not function properly as volume_full.list consists of a thousand
separator entries for date entries. Changes to this pack put the correct
date values in the volume_full.list file enabling vault to function
properly.

Workaround:
To avoid this issue, change the system locale to "C".
--------------------------------------------------------------------------------
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 = 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 = 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 = ET529095

Description:
Updating the NetBackup Client Image in a Windows Shared Resource Tree with
an install image that is not a NetBackup Client image will corrupt the
database and prevent a 'Prepare To Restore'.

Workaround:
Adding a NetBackup Client Image to the Shared Resource Tree again will fix
the database and allow a 'Prepare To Restore'.
--------------------------------------------------------------------------------
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 = ET499394

Description:
On the "Drivers" tab in the "Change configuration" dialog, the "Bootable"
and "Use BMR Discovered" options were added in the configured packages
list for MSD drives where the "Use BMR Discovered" option was added for
configured NIC drivers. The "Change" button was added to change these
attributes for every configured ( NIC/ MSD) driver. The "Bootable"
property was associated only to MSD and not to NIC drivers.
--------------------------------------------------------------------------------
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 = 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 = ET193029

Description:
When performing a restore, the user has the ability to select commit and
mount options for an Exchange 2000 Database. However, no entries are
made in the progress log to reflect the success or failure of the
processing.
--------------------------------------------------------------------------------
Etrack Incident = ET529739

Description:
Windows bmrsavecfg would fail on systems that were running some versions
of the MSSQL Server.
--------------------------------------------------------------------------------
Etrack Incident = ET493894

Description:
A backup attempt for Exchange VSS (either local or transportable) would
fail if a Recovery Storage Group existed on the Exchange server. The
following error will show up in the bkar32 log:

2:16:48.133 PM: [8840.8788] <2> ov_log::V_GlobalLog: INF - ESE_EnumSpecFiles:
Entered
2:16:48.352 PM: [8840.8788] <2> ov_log::V_GlobalLog: INF - ESE_EnumSpecFiles:
pStorageDS->Open() failed - 0xc1032221

For local Exchange VSS, the backup job failed with a status 71,
�none of the files in the file list exist.� For transportable
Exchange VSS, the job failed with status 156, �snapshot error encountered.�
--------------------------------------------------------------------------------
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 = ET413184

Description:
Special files (such as ntuser.dat and ntuser.dat.log) could not be backed
up when the backup job was started and the user logged off the system.
Now those files are backed up even if the user logs off after the backup
job is started.

Additional Notes:
This fix was tested on all supported Windows platforms for this release.
--------------------------------------------------------------------------------
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 = ET507141

Description:
Added Engenio, IBM DM4000, and HP EVA to test VSS transportable providers
and enhance the diagnostics.
--------------------------------------------------------------------------------
Etrack Incident = ET523060

Description:
Resolved issues with msvcrt.dll errors that would appear in the event
viewer, and caused errors in Windows x64 Clients.
--------------------------------------------------------------------------------
Etrack Incident = ET530155

Description:
If the password for the NBDB database was changed using the nbdb_admin
command, the installation of a NetBackup 6.0 maintenance pack would fail
when calling the nbdb_upgrade command. The admin log showed the following
error:

"verifyDB(): NBDB Schema modified outside of System! Call support."

The nbdb_admin command has been fixed to prevent this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET532731

Description:
A problem existed where two different message IDs were associated to the
same error message.
--------------------------------------------------------------------------------
Etrack Incident = ET517406

Description:
Multiple leak issues in TAO have been fixed in this maintenance pack.
--------------------------------------------------------------------------------
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 = ET494801

Description:
The Bare Metal Restore Volume Mapping wizard now enables users to specify
the "Stripe Size" for Linux multi-device volumes.
--------------------------------------------------------------------------------
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 = 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 = ET425127

Description:
When restoring/importing backup images of large files (at least 1 Gb) that
were made from a NetBackup 3.4.1 OpenVMS client, the restores and imports
would fail.
--------------------------------------------------------------------------------
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 = ET519437 ET430443

Description:
In an Internationalization (I18N) environment the NetBackup Client user
interface would hang if SharePoint Portal Server 2003 backwards compatible
document library option was installed.
--------------------------------------------------------------------------------
Etrack Incident = ET494904

Description:
Buffer overflow in the I18N/L10N environments has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET533706

Description:
Base AIX 5.3 client support was added for BMR in this pack.

Refer to the following TechNote for more specific support limitations.
Note: Advanced features of AIX 5.3 are not yet supported.

http://entsupport.symantec.com/docs/282054
--------------------------------------------------------------------------------
Etrack Incident = ET422446

Description:
Corrected the drive unload function in acstest.
--------------------------------------------------------------------------------
Etrack Incident = ET424715

Description:
When doing a Dissimilar System Restore (DSR), if the source and target
machines had the exact same mass storage drivers, but the machines had
some other critical devices that were different, then a blue screen
would occur after the restore.
--------------------------------------------------------------------------------
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 = ET361792

Description:
The NetBackup MS SharePoint Portal Server 2003 agent DBCC check option
(FULL check - exclude index) performs a physical check. A change has
been made to ensure this check does not occur.
--------------------------------------------------------------------------------
Etrack Incident = ET533070

Description:
The NetBackup SharePoint Portal Server 2003 agent failed to enumerate
backup objects for I18N/L10N.
--------------------------------------------------------------------------------
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 = ET527310

Description:
Added the capability of performing eseutil throttling when validating
Exchange databases during Local or Offhost VSS backups. This is a new
feature that Microsoft added for Exchange 2003 SP2.

Additional Notes:
The registry value (HKLM\Software\Veritas\netbackup\CurrentVersion\
Config\Exchange_ESEUTIL_Throttle) can create a value between 1 and 10000
that can determine the number of I/O's between one-second pauses.

For more information, refer to the following:
http://www.microsoft.com/technet/prodtechnol/exchange/2003/vssbp.mspx .
--------------------------------------------------------------------------------
Etrack Incident = ET522228

Description:
FlashBackup on Windows did not handle named streams associated with
directories properly.
--------------------------------------------------------------------------------
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://entsupport.symantec.com/docs/281521 ).
--------------------------------------------------------------------------------
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 = ET543209

Description:
When performing a restore, the security permissions on the
%WINDIR%\Registration directory were not the same as they were at the
time of the backup.
--------------------------------------------------------------------------------
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 = 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 = ET566754

Description:
The bmrcreatepkg program shows some its messages in English only.
--------------------------------------------------------------------------------
Etrack Incident = ET565075

Description:
Changes have been made to resolve an NBSL core dump on an AIX 5.3 master
server.
--------------------------------------------------------------------------------
Etrack Incident = ET563634

Description:
The VxMS API call vfm_open_id was not recognizing certain frozen image
names. This issue is resolved in release 4.3 version 012.
--------------------------------------------------------------------------------
Etrack Incident = ET546882

Description:
Support for SFW 4.3 has been added for Windows clients.
================================================================================



=========
NB_60_1_M
=========

Etrack Incident = ET421953

Description:
An issue in bpdbm caused the cleanup process to halt on Windows platforms
and prevented jobs from running.
--------------------------------------------------------------------------------
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 = 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 = ET497262

Description:
An error message was received when performing a DB2 roll-forward after
restore.

For example:
$ db2 rollforward db sample to end of logs and stop
SQL1268N Roll-forward recovery stopped due to error "28" while
retrieving log file "S0000001.LOG" for database "SAMPLE" on node "0".
--------------------------------------------------------------------------------
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 = 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 = ET419262

Description:
The ability to browse for backup objects failed in Localized environments.
--------------------------------------------------------------------------------
Etrack Incident = ET423206

Description:
The back-level media server V_QUERY_CLEAN_BYROBNUM request caused an SQL
error.
--------------------------------------------------------------------------------
Etrack Incident = ET492763

Description:
Users can now backup SAP files on Windows that contain multi-byte
characters in the file path and file name.
--------------------------------------------------------------------------------
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 = ET495088

Description:
After the file copy portion of Windows XP setup was completed, an error
message similar to the following would occur:

�Setup cannot set the required Windows XP configuration information.
This indicates an internal setup error. Contact...�
--------------------------------------------------------------------------------
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 = ET414648

Description:
Oracle backups would fail because bphdb.exe quit with an Application Error.
This problem was encountered when using the following agents :

- ORACLE
- SAP
- SYBASE
- DB2
--------------------------------------------------------------------------------
Etrack Incident = ET497784

Description:
After a BareMetalRestore restore, the MSSQL Server Image path could be
incorrect.

Additional Notes:
Added message #70 in the following file:

bmrsavecfg.xml:BMRSAVECFG_ERROR_SAVING_SQL_IMAGE_PATH
--------------------------------------------------------------------------------
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 = ET424615

Description:
Thread handles were not being destroyed even after the threads have exited.
- To correct this issue, and array of threads is created and maintained.
Then before adding any new thread details to this list a check is made
of the existing threads that have completely processing. If the check
competes it cleans up the resources used for the same threads and then
adds the details for the newly created thread into the list of threads.

- At the time of exit, it cleans up all the thread handles irrespective of
whether they are currently executing or not.
--------------------------------------------------------------------------------
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 = ET500433

Description:
Restoring a partial database image (or a partial differential image) fails
with the following error message:

''Filegroup '' cannot be restored because it does not exist in the backup
set.''

In addition, the property sheet for a partial backup image did not display
the list of file groups contained in the partial backup.
--------------------------------------------------------------------------------
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 = ET509427

Description:
A function that CPtrArray::GetCount() was used with was incompatible with
the Windows 64-bit Environment. Code changes have been made to use the
alternate function CPtrArray::GetSize().
--------------------------------------------------------------------------------
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 = ET506726

Description:
After applying the MS05-051 security patch, clients restored using BMR
would experience a problem with Active Directory.

Workaround:
To avoid this issue, fix the permissions for the WINDOWS\Registration
directory and its files.
--------------------------------------------------------------------------------
Etrack Incident = ET508191

Description:
vmd now retries the connection to EMM forever, instead of shutting down
if it cannot connect to EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET507275

Description:
When performing a restore, the security permissions on the
%WINDIR%\Registration directory were not the same as they were at the
time of the backup.
--------------------------------------------------------------------------------
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 = ET514039

Description:
When running backups with VSP enabled for open file backups, the client
machine would intermittently lock up and become unresponsive during a
backup. To avoid this issue, the user must reboot of the machine.
--------------------------------------------------------------------------------
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.
================================================================================




Attachments

NB_60_7_M.winnt.x64_308513.exe (143.8 MBytes)


Legacy ID



308513


Article URL http://www.symantec.com/docs/TECH63285


Terms of use for this information are found in Legal Notices