CLT 6.0GA Pack NB_CLT_60_7_M README                           September 15, 2008
Corequirement: NB_60_7_M NB_BBS_60_7_M NB_BMR_60_7_M NB_JAV_60_7_M

================================================================================
This Maintenance Pack provides fixes for the Veritas NetBackup (tm) UNIX
clients.  NetBackup UNIX Add-on products, Database Agents and the Java user
interface have separate Maintenance Packs.  

This Maintenance Pack may require as much as 400MB in free space in the /usr
partition to install. This Maintenance Pack contains a full replacement of all
client binaries for all platforms.  If applying this Maintenance pack locally,
up to 50MB of free space is required in /usr partition, depending on platform.
If applying this pack to a server that has had other client platform types
loaded (for example, push install of client binaries) more space is required,
up to 400MB. For more information, please refer to the following TechNote:

  http://seer.support.veritas.com/docs/280824.htm
================================================================================


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

   -- On a server, NB_CLT_60_7_M (this Maintenance Pack) can be installed on a
      client using a remote installation procedure or a local installation
      procedure.
   
   -- Only on a NetBackup server, NB_60_7_M_<6 digit number>.<server>.tar
      must be installed after this Maintenance Pack is installed.

   -- Only if Bare Metal Restore Boot Server is installed,
      NB_BBS_60_7_M_<6 digit number>.<platform>.tar must be installed after this
      Maintenance Pack is installed.

   -- Installation of this Maintenance Pack requires version 1.33.10.18
      of Vrts_pack.install script.

   -- Deliverables for the agents or options such as DB2, Oracle, Veritas
      Storage Migrator (tm) (VSM) do not always change between patches and could
      result in a patch not being delivered.  When upgrading or patching client
      software, any agent software must be upgraded or patched to the latest or
      matching level at the same time as the client software.

    -- Added support for multiple ACSLS servers to Windows.  This requires
       all Windows ACS customers upgrade to SUN/STK Libattach version 1.4.1.

 

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
VII.  MAINTENANCE PACK CONTENT
        Conventions
        Current Maintenance Pack
          NB_CLT_60_7_M
        Maintenance Pack History
          NB_CLT_60_6_M
          NB_CLT_60_5_M
          NB_CLT_60_4_M
          NB_CLT_60_3_M
          NB_CLT_60_2_M
          NB_CLT_60_1_M


============================================
I.  NEW FEATURES AND PLATFORM PROLIFERATIONS
============================================
Many new features, enhancements, and platform proliferations have been made
to NetBackup 6.0 MP7  in general.  For a complete list of these additions, refer
to the New Features and Platform Proliferations section in the NB_CLT_60_7_M
online Readme that you installed prior to installing this package.

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

+  (ET1185725) When running on an AIX 5.3 system, Symantec recommends that you
  install the patch APAR IY92889 if you are installing NetBackup on a system
  using the xlC.aix50.rte C++ runtime version 8.0.0.0 or later.  You can find
  this patch on the www.ibm.com Web site by entering, IY92889 in the search
  field.

+  (ET1182594) You may encounter a core dump of dbeng9 after performing a Full
  Catalog Backup Recovery. This is not a Symantec NetBackup issue; thus, you can
  delete or ignore the core dump. Testing showed that the catalog recovery
  completed successfully and that bprecover handled the core dump issue
  appropriately.

+  (ET1208336) When using NBAC on a Linux system running a kernel at or
   above 2.6.9-*, it is possible that backups may fail after 1000 jobs have
   completed. To avoid this issue, you will need to update your VxAT version
   to 4.2.2.40 or greater.

+  (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

+  (ET1189468) At the next major release of NetBackup, the NetBackup
  Administrator's Guide for UNIX will be updated to clarify how to set and
  use the Busy File Settings host properties.  The NetBackup 6.0
  Administrator's Guide instructs the user to copy bpend_notify_busy script
  to the /usr/openv/netbackup/bin/bpend_notify location.  However the guide
  does not specify that the bpend_notify_busy script resides on the master
  server and needs to be copied to the client machine.  Thus, the each
  client system will have a goodies directory, but it will not contain the
  bpend_notify_busy file.

+  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


+  On all platforms, if the server pack install fails for any reason after the
  Client pack has completed, be sure not to restart the daemons before you
  attempt to install the pack again.

+  Reminder: Synthetics is not supported on Tru64 platforms.

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

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

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

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

+  The NetBackup 6.0 Commands document contains incorrect information for
  the vxlogcfg -r command.  The following is the revised description for this
  command.  

  -r, --remove

  Unregisters and removes the log configuration settings for the specified
  OID and product from the product logging configuration file. Individual
  settings can be removed with the “–s, --setting keyname=value“ option.

  Caution: Always use the -r option with the –o option. Otherwise, all of the
           existing NetBackup log settings are removed and no further logging
           is performed for all of NetBackup.




==========================
III. DOWNLOAD INSTRUCTIONS
==========================
1) Download the NB_CLT_60_7_M_<6 digit number>.tar into the
  /tmp directory,

  where <6 digit number> is an internal tracking identifier

    NOTE: NB_CLT_60_7_M_<6 digit number>.tar contains all client binaries.
 
    NOTE: Only if Bare Metal Boot Server is installed, download
          and extract NB_BBS_60_7_M_<6 digit number>.<platform>.tar
          into the /tmp directory.


2) Extract the NB_CLT_60_7_M_<6 digit number>.tar file
       tar xvf NB_CLT_60_7_M_<6 digit number>.tar

       This will create the files:
       VrtsNB_CLT_60_7_M.README
       VrtsNB_CLT_60_7_M.tar.Z
       VrtsNB_CLT_60_7_M.preinstall        
       VrtsNB_CLT_60_7_M.postinstall
       VrtsNB_CLT_60_7_M.postuninstall
       Vrts_pack.install




=============================
IV. INSTALLATION INSTRUCTIONS
=============================

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

Before installing this maintenance pack, please review the following items:
 - Symantec recommends that you perform catalog backups before and after you
   apply this maintenance pack.

 - If you are planning to install this Maintenance Pack as a part of an
   upgrade from a 5.x release then it is important that you understand that the
   existing NetBackup databases must be in a consistent state prior to beginning
   the upgrade. Information and tools to assist you in determining the current
   state of your database, as well as instructions to help you address any
   inconsistencies that you might discover can be viewed on the NetBackup Upgrade
   Portal, a part of the Symantec NetBackup Support Web site.

     http://www.symantec.com/business/support/overview.jsp?pid=15143

 - If you are upgrading from 5.x to 6.0, you must install this Maintenance Pack
   before you run nbpushdata.  Failure to install this Maintenance Pack first
   will result in a failed upgrade.

 - If upgrading a NetBackup client on which this Maintenance Pack has been
   installed to a NetBackup server, you must first uninstall this Maintenance
   Pack, perform the upgrade from client to server,then re-apply this
   Maintenance Pack to the new server.


For Maintenance Pack installation on a UNIX Cluster Environment:
--------------------------------------------------------------------------------
1) Before you install this Maintenance Pack, make sure that NetBackup is at
  release level 6.0 and configured to run in a cluster.

2) Freeze the NetBackup group. (By freezing the group, you will prevent a
  'failover' from occurring during a patch installation).

3) Install this Maintenance Pack on the inactive node(s) of the cluster
  (perform steps 1 through 3 below).

  IMPORTANT: If you are using HP Service Guard and upgrading from a
  pre-NetBackup 6.0 MP4 version, you must complete the installation of
  this pack to the inactive node(s), and then copy the following file from
  an inactive node to the active node before beginning the pack install on
  the active node:

  /usr/openv/netbackup/bin/cluster/util/monitor

4) Install this Maintenance Pack on the active node of the cluster (perform
  steps listed below).

5) If the cluster is in a faulted state, clear the fault.

6) Unfreeze the NetBackup group.
--------------------------------------------------------------------------------

There are two ways to install the client maintenance pack software.

1. Remote Installation:  Loads the software on a master server with
   the intent of pushing client software out to affected clients.

2. Local Installation:   Loads and installs the software only to this
   local machine.

Remote client install:

NOTE:  This pack contains NetBackup Client binaries for Linux, Red Hat 4,
and SuSE 9, on Power PC from IBM.  To install these binaries on a NetBackup
Server (for pushing to clients), you must first create the following
directories:
      mkdir /usr/openv/netbackup/client/Linux/IBMpSeriesRedHat2.6
      mkdir /usr/openv/netbackup/client/Linux/IBMpSeriesSuSE2.6


As root on the NetBackup Master/Media Server:

1) Close the NetBackup user interfaces.
  - Make sure the NetBackup server has no active jobs running (for example,
    backups, restores, or duplications).

  - If a database agent is being used, such as Oracle, ensure that the database
    services are stopped.

2) Install NB_60_7_M and NB_CLT_60_7_M Maintenance Pack binaries.

       cd /tmp
       /bin/sh Vrts_pack.install

  NOTE: Selecting the client Maintenance Pack on a Master/Media server will
  automatically install the server maintenance pack if the server (NB) .Z file
  and README exist in the installation directory. The client install will fail
  if the (NB) .Z file and README are not present and the server pack has not
  been previously installed. The server maintenance pack will NOT be installed
  automatically during a reinstall of the client maintenance pack.  

  NOTE: The installation of the client pack on a server copies the appropriate
  client binaries into place on the server.  Additionally, any other client
  binaries on the server will be updated so that they can then be pushed out
  using update_clients.  Therefore, Symantec recommends that you also apply
  the NB JAV Maintenance Pack before running update_clients.

  NOTE: It is important that Server and Client binaries are kept at the same
  pack level on all NetBackup Servers.  This is enforced by the Pack install
  process.


3) On a server ONLY: The Vrts_pack.install script will prompt you to restart
  daemons.  Otherwise, after the pack installation has completed, run:

       /usr/openv/netbackup/bin/goodies/netbackup start

4) The pack install logs can be found in /usr/openv/pack/pack.history once the
  installation is complete.

5) On a server ONLY, update the remote NetBackup clients with the
  update_clients script.

       /usr/openv/netbackup/bin/update_clients <hardware> <os>

       where <hardware> <os> is one of the following:

       ALPHA/OSF1_V5
   HP-UX-IA64/HP-UX11.23
   HP9000-700/HP-UX11.00
   HP9000-700/HP-UX11.11
   HP9000-700/HP-UX11.23
   HP9000-800/HP-UX11.00
   HP9000-800/HP-UX11.11
   HP9000-800/HP-UX11.23
   INTEL/FreeBSD5.3
   Linux-IA64/RedHat2.4
   Linux-IA64/SuSE2.4
   Linux/IBMzSeriesLinux2.4.21
   Linux/IBMpSeriesRedHat2.6
   Linux/IBMpSeriesSuSE2.6
   Linux/RedHat2.4
   MACINTOSH/MacOSX10.3
   RS6000/AIX5
   SGI/IRIX65
   Solaris/Solaris8
   Solaris/Solaris9
   Solaris/Solaris10
   Solaris/Solaris_x86_8
   Solaris/Solaris_x86_9
   Solaris/Solaris_x86_10

           
      Note: The /usr/openv/netbackup/bin/update_clients command without
            any parameters will update all the UNIX clients.
           
      Note: When updating an RS6000 client, there may be circumstances
            where update_clients will fail with an error similar to
            this:

            Couldn't open /usr/openv/lib/libVmangle.so on client
            Client open errno = 26

            If this happens, execute /usr/sbin/slibclean on the client
            to be updated and re-run update_clients.

If the client (CLT) .Z file and README exist in the installation
directory during the installation of the server maintenance pack,
the Vrts_pack.install script will install the client
maintenance pack automatically.  The client maintenance pack will NOT
be installed automatically during a reinstall of the server
maintenance pack.  

Local client install:

The install script will determine if a local client install is appropriate
and choose the appropriate client type to install.

As root on the NetBackup client:

1) Close the NetBackup user interfaces.
  - Make sure the NetBackup server has no active jobs running (for example,
    backups, restores, or duplications).

  - If a database agent is being used, such as Oracle, ensure that the database
    services are stopped.


2) Install NB_CLT_60_7_M Maintenance Pack binaries.

      cd /tmp
      /bin/sh Vrts_pack.install

NOTE:  Again, Symantec recommends that you perform catalog backups after you
have applied this maintenance pack.




=========================
V. UNINSTALL INSTRUCTIONS
=========================
Note:  This will ONLY uninstall the maintenance pack from your machine
      if the client maintenance pack software was installed directly on the
      machine.  This uninstall procedure will NOT work on clients that were
      installed by pushing the software from a server.
   
As root on the NetBackup Master/Media Server in which the maintenance pack was
installed:

   1) Close the NetBackup user interfaces.

       - Make sure the NetBackup server has no active jobs running (for
         example, backups, restores, or duplications).

       - If a database agent is being used, such as Oracle, ensure that the
         database services are stopped.

   2) Change directory to the patch save directory.  
       Substitute the pack name for ${PACK} in the following command:

          cd /usr/openv/pack/${PACK}/save

   3) Run the un-install script:

         ./Vrts_pack.uninstall

   4) Verify that the pack uninstalled successfully by checking:

       /usr/openv/pack/pack.history.

   5) If update_clients was run after the pack was originally INSTALLED,
       run it again after that pack is successfully UNINSTALLED.

   6) If necessary, restart the NetBackup and Media Manager daemons:

       /usr/openv/netbackup/bin/goodies/netbackup start




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

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


NB_60_7_M
---------
1128726 1145685 1146635 1150657 1172971 1178481 1194284 1175361 1196200 1160439
1191148 1193696 1197056 1201124 1186553 1201289 1200945 1193183 1186256 1202780
1181024 1046203 1188094 1193241 1200911 1196151 1204133 1194711 1203203 1203315
1204149 1203341 1196108 1206982 1149072 1203743 1206988 1209668 1141942 1210324
1181990 1205097 1157872 1028523 1193739 1202703 1139683 1213186 1210997 1213398
1194467 1198779 1163522 1194630 1186713 1159797 1215592 1215486 1213931 1146675
1213936 1217081 1019035 1003076 1199328 1173094 1211957 1209824 1210121 1219899
1206849 1204494 852979 1168028 1190482 1223027 1223019 1229928 1159536 1200897
1224637 1214052 1201393 1152608 1042411 1211653 1137917 1135737 1227823 814704
1175373 1236186 1237077 1237818 918372 1200166 1216170 1039111 1238630 1229969
1238098 1239178 1236032 1242512 1245566 1244766 1245997 1244622 1221477 1036931
1200190 1089296 1251778 1252326 1219002 1252345 1268942 1184332 1223173 1212526
1259059 1195231 1260503 1259252 1262091 1150199 1240367 1261507 1261430 1269061
1273387 1275369 1269918 1228938 1261282 1097416 1275549 1281153 1270235 1253532
1283873 1283865 1277786 1077528 1189875 1190428 1291060 1260324 1287242 1292773
1294647 1291761 1295792 1302098 1251842 1316727 1316894 1321914 1178607

NB_ADC_60_7_M
-------------
1179426 1220903 1227575 1239595 1235529 1231895 1219116 1134888 1211678 1275147
1227541 1210195 1361434

NB_BBS_60_7_M
-------------
1194900 1198426 1201794 1240183

NB_BMR_60_7_M
-------------
1201741 1212630 1213219 1219751 1222733 1231109 1228989 1212202 1175891 1195956


NB_CLT_60_7_M
-------------
1128726 1145685 1146635 1150657 1172971 1178481 1194284 1175361 1196200 1160439
1191148 1193696 1197056 1201124 1186553 1201289 1200945 1193183 1186256 1202780
1181024 1046203 1188094 1193241 1200911 1196151 1204133 1194711 1203203 1203315
1204149 1203341 1196108 1206982 1149072 1203743 1206988 1209668 1141942 1210324
1181990 1205097 1157872 1028523 1193739 1202703 1139683 1213186 1210997 1213398
1194467 1198779 1163522 1194630 1186713 1159797 1215592 1215486 1213931 1146675
1213936 1217081 1019035 1003076 1199328 1173094 1211957 1209824 1210121 1219899
1206849 1204494 852979 1168028 1190482 1223027 1223019 1229928 1159536 1200897
1224637 1214052 1201393 1152608 1042411 1211653 1137917 1135737 1227823 814704
1175373 1236186 1237077 1237818 918372 1204203 1200166 1216170 1039111 1238630
1229969 1238098 1239178 1236032 1242512 1245566 1244766 1245997 1244622 1221477
1036931 1200190 1089296 1251778 1252326 1219002 1252345 1268942 1184332 1223173
1212526 1259059 1195231 1260503 1259252 1262091 1150199 1240367 1261507 1261430
1269061 1273387 1250877 1275369 1269918 1228938 1261282 1097416 1275549 1281153
1271278 1270235 1253532 1283873 1283865 1277786 1077528 1189875 1190428 1291060
1260324 1287242 1292773 1294647 1291761 1296282 1295792 1302098 1251842 1316727
1316894 1321914 1178607

NB_DB2_60_7_M
-------------
1294774

NB_DMP_60_7_M
-------------
1152587 1213695 1222258 1214070 1235538 1233401 1249754 1257297

NB_ENC_60_7_M
-------------
1238098

NB_INX_60_7_M
-------------
1145850

NB_JAV_60_7_M
-------------
1188650 1194367 1135270 1187772 1205636 384091 1278056 1255609 1301700

NB_LOT_60_7_M
-------------
1314264

NB_NOM_60_7_M
-------------
1226692 1233746 1195149 1238422 1204000 1122893 1036931 1283800 1291729

NB_ORA_60_7_M
-------------
1226883 1224664 1294774

NB_SAP_60_7_M
-------------
1209710 1142467 1210594

NB_SMU_60_7_M
-------------
1280906

NB_VLT_60_7_M
-------------
1238369 1166277 1283692 1297162 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 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 = ET1145685

Description:
   A change was made to address an issue that would cause a core file to be
   generated after a login failure occurred on the NetBackup-Java
   administration console only.
--------------------------------------------------------------------------------
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 = 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 = 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 = ET1193241
Associated Primary Etrack = ET1189083
Titan cases:  281-238-515

Description:
   The cluster monitor would falsely detect the NB_dbsrv process as being
   offline.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = ET1157872
Associated Primary Etrack = ET1154612
Titan cases:  311-639-750

Description:
   Small sparse files, less than 64KB, were not being restored properly on
   HP-UX clients.
--------------------------------------------------------------------------------
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 = 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 = ET1139683
Associated Primary Etrack = ET1129815
Titan cases:  311-694-272

Description:
   Restoring from a raw partition backup with encryption fails on HP-UX and
   Linux systems.

Workaround:
   If you encounter this issue, disable encryption before performing a
   restore, or create an unencrypted duplicate of the image.
--------------------------------------------------------------------------------
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 = 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 = ET1163522
Associated Primary Etrack = ET1161321

Description:
   When the touch file /usr/openv/netbackup/HARD_LINK_AS_FILE is present,
   bpbkar treats all hard-links as a normal file.  

Additional Notes:
   This increases the size of an overall backup and restore operation.
--------------------------------------------------------------------------------
Etrack Incident = ET1194630
Associated Primary Etrack = ET1194611
Titan cases:  311-789-088

Description:
   Raw device restores would fail on Linux systems.
--------------------------------------------------------------------------------
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 = ET1215486
Titan cases:  320-087-606

Description:
   A change was made to address "allocation failed" errors being received in
   the Activity Monitor.  The cause was a failure to read the psinfo file in
   bpcd_get_process_status_rqst.

Additional Notes:
   This issue affected Solaris and UnixWare only.
--------------------------------------------------------------------------------
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 = 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 = ET1209824

Description:
   NetBackup clustered on a system running SunCluster v3.0 (or 3.1/ 3.2)
   fails to perform a patch install or upgrade, or installing (or upgrading)
   database agents, or options using the documented Sun Cluster commands
   provided in the NetBackup High Availability (HA) Guide.

Workaround:
   If you want to install or upgrade your clustered environment, follow the
   documented steps provided in the NetBackup High Availability (HA) Guide,
   but replace the documented SunCluster commands with the following
   commands.
   
   1. Freeze the NetBackup group by executing the following command before
      patch install of upgrade.
         /usr/cluster/bin/scswitch -n -j scnb-hars
   
   2. Unfreeze the NetBackup group by executing the following command after
      patch install or upgrade.
         /usr/cluster/bin/scswitch -e -j scnb-hars
--------------------------------------------------------------------------------
Etrack Incident = ET1210121

Description:
   The nbdbms_start_server -stat command would parse and use an incorrect
   value for the port. This issue only occurred if the shared memory
   connection failed.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = ET1214052

Description:
   Changes were made to ensure the timeouts are being calculated properly for
   Linux SCSI calls to an sg driver.
--------------------------------------------------------------------------------
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 = 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 = 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 = ET1204203
Associated Primary Etrack = ET1200103
Titan cases:  281-262-301

Description:
   The User Archive did not work with Encryption.  After the backup portion
   of the archive completes, the entire job would hang and bpfilter would use
   100% of the CPU resources on the client machine.
--------------------------------------------------------------------------------
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 = ET1238098
Titan cases:  290-934-270

Description:
   An issue existed that caused NBNos to core dump on AIX master servers.
   To work around the core dump issues, a change was made to the set the
   linker option to increase maximum memory size for all AIX executables
   except for those linked with ld and those compiled in 64 bit.  This
   linker option was also not used for shared libraries.  
--------------------------------------------------------------------------------
Etrack Incident = ET1239178

Description:
   Make messages would fail because of the duplicated ID, CerRba0065N, in the
   commands.c file.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = ET1268942 ET1184332 ET1223173 ET1212526
Associated Primary Etrack = ET1241252 ET1162079
Titan cases:  290-958-463 311-775-022 281-242-905

Description:
   A new Runtime PBX has been added for Solaris, HP-UX, AIX, and Tru64
   platforms only.  This fixes the following issues:

    - EMM would fail to start due to an "unable to open acceptor for
        <1556:EMM>:Invalid argument".
    - VxPBX resource failed to be offline with the cluster configuration.
    - The ICS patch installer modified the owner/group of the system /tmp
        directory to 123/107.
    - PBX would fail with the error: [Error] Could not open pipe stream.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = ET1250877
Associated Primary Etrack = ET1234214
Titan cases:  320-095-399

Description:
   A change was made to the behavior of AFS file system backups that are no
   longer online at the time of the backup.  The option of incrementing the
   error count was added rather than failing the backup.  This behavior is
   controlled using the following new client touch file:
   
      /usr/openv/netbackup/WAIT_FOR_VOS_DUMP.

Workaround:
   If you encounter this issue, re-run listvol and the backup.
--------------------------------------------------------------------------------
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 = 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 = ET1228938
Associated Primary Etrack = ET1225195
Titan cases:  290-061-961

Description:
   When forking a child process to call lstat/lstat64 to detect an unavailable
   NFS mount, the case where kill(child) returns errno ESRCH was not properly
   handled. When ESRCH is returned by kill(child) it is assumable that the
   child exited on its own accord.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = ET1296282

Description:
   The Legacy encryption backups and restores For AFS policy types are
   supported with this version of NetBackup. Standard encryption backups for
   AFS policy types are not supported and the following message will be logged:
       
   "Standard Encryption is not supported for AFS volume backups. Use Legacy
   Encryption"
--------------------------------------------------------------------------------
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 = 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 = 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 = 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.
--------------------------------------------------------------------------------



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

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

=============
NB_CLT_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 = 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 = ET971561
Titan cases:  230-281-035

Description:
   If bpadm was used to modify a catalog policy, policies that were set
   as a "Critical policy" in the NetBackup-Java Administration Console
   would have that setting removed.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = ET1102716
Associated Primary Etrack = ET1044565
Titan cases:  290-777-895

Description:
   When upgrading on a multiple NIC machine, the name of the emmserver
   may not have been properly set.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = ET1061995
Associated Primary Etrack = ET1052610
Titan cases:  311-480-661

Description:
   On HP-UX IA64 restores of large sparse files (4 gigabytes and greater)
   would fail to correctly restore the file holes present.

Additional Notes:
   Running ls -ls would show that the restored files occupy less blocks
   than the original.  In addition, the checksum of the file would be
   different, simply because the file holes would be absent.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = ET1087582
Associated Primary Etrack = ET1086608
Titan cases:  240-597-110

Description:
   On AIX, a CIFS file system is backed up under the local drives
   directive when it is actually a remote drive.

Workaround:
   To resolve this issue, create an exclude entry for drives that are
   CIFS if they are not wanted in the backup.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = ET1120743
Associated Primary Etrack = ET1077895

Description:
   Added new client touch-file, /usr/openv/netbackup/TREAT_LOFS_LOCAL.  When
   present on a client, NetBackup will treat any LOFS file system mounts as
   local file systems rather than NFS.  This allows them to be backed up
   the ALL_LOCAL_DRIVES touch-file.
--------------------------------------------------------------------------------
Etrack Incident = ET786841
Associated Primary Etrack = ET701942
Titan cases:  230-118-717

Description:
   LIMIT_BANDWIDTH does not work properly on a Linux client.  The client
   doubles the actual value of LIMIT_BANDWIDTH.

Workaround:
   To avoid this issue, use a value for LIMIT_BANDWIDTH equal to half of the
   desired amount.
--------------------------------------------------------------------------------
Etrack Incident = ET1052440
Associated Primary Etrack = ET1018017
Titan cases:  290-704-908 290-730-131

Description:
   Performance testing with bpdm_dev_null caused a bpdm Status 84 error, with a
   bp_sts_write_image: Invalid input argument.

Workaround:
   Build a legacy STU using the bpstuadd command, then use an old dev_null
   touch file.
   a. Create a touch file to enable a legacy disk:
         /usr/openv/netbackup/bin/ENABLE_LEGACY_DISK.
   b. Add the STU:
         bpstuadd –label test_old_stu –dt 0 –path /disk_stu
   c. Create a “dev_null” touch file:
         /usr/openv/netbackup/bpdm_dev_null
--------------------------------------------------------------------------------
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 = 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 = 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 = ET1051726
Associated Primary Etrack = ET1033225
Titan cases:  290-754-496

Description:
   If a child bprd process associated with a user backup was terminated
   using a "kill <PID>" command, then scheduling was suspended.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = ET1161182
Associated Primary Etrack = ET1137130
Titan cases:  290-857-049

Description:
   The cluster_upgrade from NetBackup 5.x could fail silently if a
   pre-existing globdb host is local and has a fully qualified name.
--------------------------------------------------------------------------------
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 = ET1161334

Description:
   The bpnbat_helper binary would occasionally dump core and cause manual
   backups to stall.
--------------------------------------------------------------------------------
Etrack Incident = ET1167061

Description:
   A change was made to address an nbsl core dump issue on HP-UX 11.11.
--------------------------------------------------------------------------------
Etrack Incident = ET1168990
Associated Primary Etrack = ET1166780
Titan cases:  230444045

Description:
   Some HP-UX systems running in the zh_CH.hp15CN locale would fail
   bmrsavecfg when doing a backup.
--------------------------------------------------------------------------------
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 = 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 = 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 = ET1172601

Description:
   When running SELinux on a zSeries platform, the operating system would not
   load some of the shared libraries.  A changed was added to build with -fPIC.
--------------------------------------------------------------------------------
Etrack Incident = ET1002113
Associated Primary Etrack = ET996018
Titan cases:  290-632-354

Description:
   Some files cannot be seen in the BAR user interface and therefore cannot
   be selected for restore because a directory in the path to the files is
   not backed up.  This occurs because of the configuration of the
   exclude_list and include_list on the client.

Workaround:
   To avoid this issue, use bprestore to restore the files.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = ET1188445

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

Description:
   Error conditions that occurred during a device monitor query could have
   caused nbemm to crash while shutting down.
--------------------------------------------------------------------------------
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 = ET1210874
Associated Primary Etrack = ET1130841
Titan cases:  290-846-872 290-847-642

Description:
   The server pack install no longer modifies the attributes of the
   system /opt directory.
--------------------------------------------------------------------------------
Etrack Incident = ET1137171
Associated Primary Etrack = ET1119164
Titan cases:  220-105-447

Description:
   Stripping (-s) HP-UX binaries caused supportability problems.
--------------------------------------------------------------------------------





=============
NB_CLT_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 = ET809090

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

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

Description:
   UNIX domain socket files with path names of the form /tmp/vnet*
   were periodically created on UNIX/Linux NetBackup systems.  Most
   of these files were only needed for a few minutes and were quickly
   deleted.  If NetBackup processes terminate abnormally before the
   /tmp/vnet* file can be deleted, then these files could accumulate
   on the user's system.
   
   This patch periodically deletes old (more than one hour) /tmp/vnet* UNIX
   domain socket files.
   
   Previously the Java server (bpjava) would also use UNIX domain socket file
   paths of the form /tmp/vnet*.  Since these files often need to exist for
   several hours, the automated cleanup could cause problems.  In this patch,
   the form of the bpjava UNIX domain socket file path names has changed to
   /tmp/jbp*.
--------------------------------------------------------------------------------
Etrack Incident = ET861571

Description:
   Under certain circumstances, bpcd and vnetd services would be
   put into maintenance mode on solaris10 systems.  Changes were
   made to disable/enable these services to make sure they respond.
--------------------------------------------------------------------------------
Etrack Incident = ET861550

Description:
   If the NBDB database is not created properly during installation, the
   install continues, however the user may not understand that there was
   an issue creating the database.  As a result, the user may encounter
   errors in the command line and the user interfaces.  
   
   In addition, if during a patch installation that nbnd_upgrade fails,
   the database winds up with the incorrect version.  Again, nbemm will
   not start because of the version mismatch.
   
   Changes have been made so that the install will fail if the database
   cannot be created or upgraded and installation warnings will be logged
   in a new logging directory for nbnd commands.  The new directories are:
   
   UNIX:  /usr/openv/netbackup/logs/nbdb
   Windows:  InstallPath\NetBackup\logs\nbdb
--------------------------------------------------------------------------------
Etrack Incident = ET862411

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

Description:
   Added support for 64-bit Linux on Power client.
--------------------------------------------------------------------------------
Etrack Incident = ET862518

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

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

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

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

Description:
   On a busy UNIX NetBackup server, you may encounter defunct
   bpcompatd processes that may appear at any time.  These defunct
   processes will eventually be cleaned up, but it might some time.

Workaround:
   To avoid this issue, periodically, stop and restart bpcompatd:
   
   /usr/openv/netbackup/bin/bpcompatd -terminate
   /usr/openv/netbackup/bin/bpcompatd
--------------------------------------------------------------------------------
Etrack Incident = ET863123
Associated Primary Etrack = ET863120

Description:
   A condition existed when the bprd service on the master server connected to
   the hosts in its SERVER list and started a process on those servers to
   remove old debug log files.  If a host was in the MEDIA_SERVER list but not
   in the SERVER list on the master server, bprd would not contact that host.
   A change was made to ensure that bprd connects to hosts in both the SERVER
   list and the MEDIA_SERVER list on the master server to remove old debug
   log files.  
--------------------------------------------------------------------------------
Etrack Incident = ET863150

Description:
   NetBackup’s Release Broker's logging has been improved in the following
   manner:
   
   - The total amount of logging content has been reduced.
   - The messages that are displayed have been enhanced to be more meaningful.
   - Different debug levels are used for different purposes.  
--------------------------------------------------------------------------------
Etrack Incident = ET863199

Description:
   The SRCMEDIAID & DSTMEDIAID fields of the jobs database were not being
   written to.
--------------------------------------------------------------------------------
Etrack Incident = ET861965

Description:
   In some cases, when a request for a volume pended, the NetBackup-Java user
   interface and vmoprcmd -xdpa would display an error when asked to show the
   pending action.
--------------------------------------------------------------------------------
Etrack Incident = ET863314

Description:
   The patch level of the (remote) client was wrong when Windows was configured
   in the environment.
--------------------------------------------------------------------------------
Etrack Incident = ET861709
Associated Primary Etrack = ET701050

Description:
   Network issues would cause tldd connect timeout issues that would result in
   downed drives.
--------------------------------------------------------------------------------
Etrack Incident = ET861712 ET861714

Description:
   Changes were made to ltid that corrected the following issues:
   -  ltid would stop and report the following message if it received a message
      that were larger than 208 bytes.
         Arg list too long
   -  Occasionally, ltid would not continue to run at startup.  
--------------------------------------------------------------------------------
Etrack Incident = ET803746

Description:
   Using the -i option for vmchange command resulted in an incorrect error
   message that would indicate to users that this function is not implemented
   in NetBackup Enterprise Media Manager (EMM).  
--------------------------------------------------------------------------------
Etrack Incident = ET863393
Associated Primary Etrack = ET863378

Description:
   Backup duplication errors would occur because of a timeout issue that caused
   bptm to exit with 54 and 25 errors.
--------------------------------------------------------------------------------
Etrack Incident = ET862641
Associated Primary Etrack = ET702146

Description:
   DSSU relocation (duplication) jobs no longer leave a bid_file_* on master
   server.  
--------------------------------------------------------------------------------
Etrack Incident = ET862648

Description:
   Changes were added to correct a DSSU staging process issue that caused the
   parent job to hang.
--------------------------------------------------------------------------------
Etrack Incident = ET862609

Description:
   The fragment size set for a disk storage unit (DSU) was ignored when doing a
   Synthetic backup.  
--------------------------------------------------------------------------------
Etrack Incident = ET861978

Description:
   Changes were made to eliminate potential race conditions between ltid and
   vmd when adding a host entry to EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET862543

Description:
   The bpplinclude command could not handle file paths that contain the %
   character.  
--------------------------------------------------------------------------------
Etrack Incident = ET574945

Description:
   Snapshot client SAP backups would fail because no valid license key be
   found on the server.  
--------------------------------------------------------------------------------
Etrack Incident = ET862603

Description:
   A change was made to ensure that bpbrmds no longer exits prior to
   bpduplicate finishing (on Tru64 systems only).
--------------------------------------------------------------------------------
Etrack Incident = ET862491

Description:
   The nbpushdata log files are now written to the following locations:
   
   /usr/openv/var/nbpushdata (UNIX)
   VERITAS\NetBackup\var\nbpushdata (Windows)
   
   Log files are not pruned from these directories, so the files are available
   for later review.
--------------------------------------------------------------------------------
Etrack Incident = ET863106

Description:
   The MEDIA_UNMOUNT_DELAY is not honored consistently for standalone drives.

Workaround:
   To avoid this issue, ensure an eligible tape is loaded in the drive before
   You start a job.
--------------------------------------------------------------------------------
Etrack Incident = ET864928

Description:
   A backup job would hang in the bpbrm process after the client read timeout
   expired.  The job would not finish and a 41 status (network connection
   timed out) error would occur.
--------------------------------------------------------------------------------
Etrack Incident = ET865189 ET842864
Associated Primary Etrack = ET833467

Description:
   Changes were made to enhance the performance and speed in which the list of
   media servers would appear after a user selects Host Properties > Media
   Servers from the NetBackup-Java Administration Console.  The slow response
   was caused by the following command, which would return the external
   attribute settings for each media server.
   
   vmoprcmd -h <server_name> -extall
--------------------------------------------------------------------------------
Etrack Incident = ET852905 ET850830
Associated Primary Etrack = ET832181

Description:
   Changes were added to solve various issues in the Device Configuration
   Wizard with respect to back-level media servers.  In addition, a change
   was made that solves a device configuration wizard defect that prevented
   users from reconfiguring standalone drives as robotic.  
--------------------------------------------------------------------------------
Etrack Incident = ET861980

Description:
   Corrected a tape drive cleaning issue where the end user running the
   NetBackup Administration Console on a UNIX server could not successfully
   clean a tape drive using a path on a Windows server.
--------------------------------------------------------------------------------
Etrack Incident = ET865211 ET645838
Associated Primary Etrack = ET645838

Description:
   A status 50 error would be shown in the Activity Monitor if a user tried to
   perform a large duplication that was greater than 20 minutes.  Similar
   issues were reported in earlier versions of NetBackup.  Smaller duplications
   were not a problem.
--------------------------------------------------------------------------------
Etrack Incident = ET865184

Description:
   Some languages use a comma, instead of a period, to delimit the fractional
   portion of a floating point number.  If the default language is set to one
   of these language, some operations might fail.  Specifically, any time a
   floating point parameter is passed to the EMM server database it will
   reject a floating point number delimited by a comma, instead of a period.
   
   One example of this is attempting to change or set the cleaning frequency
   of a drive.  

Workaround:
   To resolve this issue, change the decimal point character from a comma
   to a period ('.').  This can be done by modifying the locale or switching
   to a different locale, such as US English.  
--------------------------------------------------------------------------------
Etrack Incident = ET865706

Description:
   This maintenance pack contains multiple NB_SECURITY infrastructure changes.
--------------------------------------------------------------------------------
Etrack Incident = ET862283

Description:
   Changes were made to correct the following issues with the nbemmcmd command.
   - The nbemmcmd -getemmserver command would not always get the NetBackup
         version.
   - The nbemmcmd -setemmserver command would try to set the EMM server on
         machines that were not in its domain.
   - The nbemmcmd -setemmserver command would not set the EMM server of a master
         server.
--------------------------------------------------------------------------------
Etrack Incident = ET865792

Description:
   nbVersionNumber() would not return a zero (0) when there was an error
   attempting to get the version number from the client.  However, in certain
   cases this does not happen.  
--------------------------------------------------------------------------------
Etrack Incident = ET783403

Description:
   The status collector daemon that NetBackup uses to monitor device and host
   status for back-level media servers has been logging /vm/debug/reqlib.
   This has made debugging for traditional media manager command lines
   difficult.  This change introduces a new media manager debug directory
   /vm/debug/vmscd.  This makes it much easier to obtain debugging information
   for both vmscd and the media manager command lines.  
--------------------------------------------------------------------------------
Etrack Incident = ET863402

Description:
   A change was made to ensure the nbemmcmd -listmedia command prints out the
   number of mounts, as well as the maximum mounts.  
--------------------------------------------------------------------------------
Etrack Incident = ET863433

Description:
   The message a user would receive when adding a host that already existed in
   database was invalid hostname. A change has been made to correct this
   message.
--------------------------------------------------------------------------------
Etrack Incident = ET847915
Associated Primary Etrack = ET820303

Description:
   A change was made so that a READY standalone drive was not marked as
   NOT-READY during a cold catalog backup.  
--------------------------------------------------------------------------------
Etrack Incident = ET863427

Description:
   bpmedialist now uses EMM to build the host list instead of using the storage
   unit list.  
--------------------------------------------------------------------------------
Etrack Incident = ET866829

Description:
   Queuing jobs could not be canceled from bpdbjobs command.
   
--------------------------------------------------------------------------------
Etrack Incident = ET863413

Description:
   A change was made to the nbemmcmd -help command.  It now
   returns an exit status of 0 instead of an error status.  
--------------------------------------------------------------------------------
Etrack Incident = ET866997

Description:
   If the NetBackup Request Daemon (bprd) terminated a backup before the
   NetBackup Policy Execution Manager (nbpem) was invoked, the terminated
   backup job may be reported with a "queued" status forever.  This could
   occur if a backup was initiated by the bpbackup command line and it
   referenced an unwritable progress log file.
--------------------------------------------------------------------------------
Etrack Incident = ET569130

Description:
   If the NetBackup Request Daemon (bprd) terminates a backup before the
   NetBackup Policy Execution Manager (nbpem) is invoked, the terminated
   backup job may be reported with a "queued" status forever.  This can
   occur if a backup is initiated by the bpbackup command line and it
   references an unwritable progress log file.
--------------------------------------------------------------------------------
Etrack Incident = ET865243

Description:
   If the NBDB database is not created properly during installation, the
   install continues, however the user may not understand that there was an
   issue creating the database.  As a result, the user may encounter errors
   in the command line and the user interfaces.  
   
   In addition, if during a patch installation that nbnd_upgrade fails, the
   database ends up with the incorrect version.  Again, nbemm will not start
   because of the version mismatch.
   
   Changes have been made so that the install will fail if the database
   cannot be created or upgraded and installation warnings will be logged in
   a new logging directory for nbnd commands.  The new directories are:
   
   UNIX:  /usr/openv/netbackup/logs/nbdb
   Windows:  InstallPath\NetBackup\logs\nbdb
--------------------------------------------------------------------------------
Etrack Incident = ET865850

Description:
   Erase job failures would occur because NDMP drives were being selected for
   erase jobs.

Workaround:
   To resolve this issue, down NDMP drives to prevent NetBackup from selecting
   them for erase jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET865186

Description:
   If you use the "Configure Multiple Copies" option before any storage units
   are defined the following error message appears.
   
        "Not all storage units are on the same media server"
   
   A change was made to the message to correctly indicate that no storage units
   exist.  
--------------------------------------------------------------------------------
Etrack Incident = ET893223

Description:
   When a server is configured to e-mail from the client after
   a successful backup, the bpbrm process would hang and would
   not exit because of an e-mail problem on the client.
--------------------------------------------------------------------------------
Etrack Incident = ET846230

Description:
   A change was made to resolve an issue that caused NetBackup Release Broker
   (NBRB) to crash randomly while performing a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET895177

Description:
   A change was made to resolve an issue that caused NetBackup Policy
   Execution Manager (NBPEM) to crash because of a shutdown during
   clean_media_db operation.
--------------------------------------------------------------------------------
Etrack Incident = ET895170 ET895172

Description:
   Changes were made to address scalability issues with NBPEM because
   unnecessary computations were being performed of the "jobs due" time.
   In addition, the internal queue management was a single thread to
   handle multiple queues.  This caused long waits to process requests on
   some queues.  
--------------------------------------------------------------------------------
Etrack Incident = ET834075

Description:
   Improvements were added to the CPU utilization by bprd during restore
   operations of a large numbers of files.  
--------------------------------------------------------------------------------
Etrack Incident = ET862350

Description:
   Jobs may queue instead of fail when all drives are down or not available
   because of an onDemandOnly setting.

Workaround:
   To avoid this issue, cancel the queued jobs if there is no possibility of
   them getting drives.
--------------------------------------------------------------------------------
Etrack Incident = ET858772

Description:
   Installer will verify that PBX service is running before attempting a server
   patch install, and it will start the service if necessary.  
--------------------------------------------------------------------------------
Etrack Incident = ET862424

Description:
   Messages were added to the NetBackup log whenever media is
   frozen/unfrozen/suspended/unsuspended.  
--------------------------------------------------------------------------------
Etrack Incident = ET862425

Description:
   A message has been added to the client log when the operator is about to
   request a media that may be standalone.  This message warns the operator
   that they may need to manually load the requested media.  
--------------------------------------------------------------------------------
Etrack Incident = ET862427

Description:
   If a multiplexed job stopped during a tape span (on a standalone drive) the
   Media Database for the next tape used would be incorrect, enabling this
   tape to be used again and cause data to be overwritten.  
--------------------------------------------------------------------------------
Etrack Incident = ET862428

Description:
   Added a change to address the latest SCSI standard that changed a device
   response to a Test Unit Ready command when the device is SCSI Reserved to
   another initiator.  
--------------------------------------------------------------------------------
Etrack Incident = ET862430

Description:
   Added support for Quantum/Certance Ultrium 3 drive with WORM media.  
--------------------------------------------------------------------------------
Etrack Incident = ET862431

Description:
   Some tape drives on HP_UX would not perform an erase operation
   from NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET862441

Description:
   Canceled jobs no longer cause a future job to hang during a media mount.  
--------------------------------------------------------------------------------
Etrack Incident = ET413285

Description:
   A change was made to endure that timestamps were included in
   the cluster agent debug.
--------------------------------------------------------------------------------
Etrack Incident = ET841107

Description:
   During a synthetic backup job, one of the source images for the synthetic
   may expire.  If this happens, when the bptm or bpdm reader attempts to
   read the image, it will experience a "no entity found" error from the
   catalog.  The bptm reader fails.  For this particular case, the reader will
   enter a code that causes it to hang up indefinitely.  
--------------------------------------------------------------------------------
Etrack Incident = ET847324

Description:
   Duplicate forms of the .ds file may be created as part of the NetBackup 5.x
   to NetBackup 6.x upgrade process that cause bptm or bpbrmds to crash.
   For example,
   
   beany_1162489194_C1_F1.ds.info
   beany_1162489194_C1_F1.ds.1162489194.img
   beany_1162489194_C1_F1.ds.1162489194.info
   beany_1162489194_C1_F1.ds

Workaround:
   Normally, NetBackup perceives a .img and .info file as one "file" to its
   I/O layer.  There is a special compatibility mode that enables it to see
   the extra .ds and its .info file as the same file in the previous pair.
   
   To avoid this issue, remove one of the pairs, preferably the .img file and
   its .info file.  
--------------------------------------------------------------------------------
Etrack Incident = ET896802
Associated Primary Etrack = ET798913

Description:
   An issue would occur when children jobs were retired due to exceeding the
   time allowed in an incomplete state.  The parent job, being resumed either
   manually or automatically, resulted in an Frequent status code 805 error
   because the invalid jobid was -1.
   
   A change was added that prevents the child from starting since it is not
   resumable.  The new result will correctly be a 200 error if no children
   can be started.  An indication of this will be written to the policy
   execution manager (pem) log.  
--------------------------------------------------------------------------------
Etrack Incident = ET862590
Associated Primary Etrack = ET862589

Description:
   Added the capability to open UNIX progress logs that are non-blocking.  
--------------------------------------------------------------------------------
Etrack Incident = ET860837
Associated Primary Etrack = ET834130

Description:
   Jobs would not be retried until all jobs associated with the parent job were
   complete.  
--------------------------------------------------------------------------------
Etrack Incident = ET860882
Associated Primary Etrack = ET845081

Description:
   Restarting a job that was originally an immediate backup, may cause streams
   of a different schedule type to be run.  
--------------------------------------------------------------------------------
Etrack Incident = ET894249

Description:
   NBJM was not forwarding the connect options to bpbrm.  On a NetBackup 6.0
   media server, bpbrm is able to obtain the connect options.  Whereas on a
   NetBackup 5.x media server, the connect options must be specified using the
   command line.
--------------------------------------------------------------------------------
Etrack Incident = ET847976

Description:
   If a synthetic backup job failed to get the requested resources, no
   messages were displayed in the job details to explain the cause of a
   job that appeared to be hung.  
--------------------------------------------------------------------------------
Etrack Incident = ET860264
Associated Primary Etrack = ET860276

Description:
   There was insufficient logging information provided when a
   catastrophic failure occurred while accessing the UNIX
   configuration (bp.conf).  In addition, no re-try would be
   attempted for such a failure.  
--------------------------------------------------------------------------------
Etrack Incident = ET860844
Associated Primary Etrack = ET860273

Description:
   Changes were made to resolve status 200 errors that occurred when a parent
   job started when children were left active because PEM terminated or a
   crash of a generic job occurred.
--------------------------------------------------------------------------------
Etrack Incident = ET860853
Associated Primary Etrack = ET858810

Description:
   A change was made so that jobs no longer wait for resources after the window
   is closed .
--------------------------------------------------------------------------------
Etrack Incident = ET860856
Associated Primary Etrack = ET860266

Description:
   A change was made to address an issue that caused backups to fail with an
   800 status.  
--------------------------------------------------------------------------------
Etrack Incident = ET854621

Description:
   Resolved an issue that caused scheduled, cold-catalog backups to not start.
--------------------------------------------------------------------------------
Etrack Incident = ET860879

Description:
   Resolved an issue that caused PEM to run an incremental schedule instead of
   a full schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET899176

Description:
   Near the completion of a Synthetic backup, the following error message would
   intermittently be issued to the Activity Monitor:
   
   Error ACEMsgTran::handleOutput_u (pid=28968) write failed
   from OUTPUT socket, errno=9(Bad file descriptor)
   
   This error did not affect the successful completion of the backup, but it
   did indicate a problem.  
--------------------------------------------------------------------------------
Etrack Incident = ET592677
Associated Primary Etrack = ET808108

Description:
   A change was added that resolves a segmentation fault that could occur while
   performing Teradata backups on Linux platforms.  
--------------------------------------------------------------------------------
Etrack Incident = ET431952

Description:
   This maintenance pack contains an enhancement that enables encryption for
   Teradata backups.  
--------------------------------------------------------------------------------
Etrack Incident = ET866750

Description:
   The nbpushdata -modify_5x_hosts command now sets the standalone volume
   database host to the EMM server on NetBackup 5.x hosts without standalone
   drives.
--------------------------------------------------------------------------------
Etrack Incident = ET899837
Associated Primary Etrack = ET865853

Description:
   There was a memory leak in the NetBackup Release Broker (nbrb) that caused
   the memory utilization of nbrb to go very high after duplication/synthetic
   jobs.  
--------------------------------------------------------------------------------
Etrack Incident = ET860860
Associated Primary Etrack = ET856242

Description:
   The message queue between bprd and pem would fill up if the request to pem
   was invalid.  
--------------------------------------------------------------------------------
Etrack Incident = ET849248
Associated Primary Etrack = ET846190

Description:
   Changes were made to resolve memory issues on immediate and user-backup
   requests.  
--------------------------------------------------------------------------------
Etrack Incident = ET832247

Description:
   Deleting a cluster node no longer leaves invalid references.  
--------------------------------------------------------------------------------
Etrack Incident = ET856478

Description:
   The bptm -updatedb command would swap the number of images and the number of
   valid images when inserting the data into the EMM database.  
--------------------------------------------------------------------------------
Etrack Incident = ET855644

Description:
   A change was made to resolve a possible stack overflow issue that would
   cause a system crash.
--------------------------------------------------------------------------------
Etrack Incident = ET850303

Description:
   There is a timing issue with bringing the cluster online and running
   runtpext. Bringing the cluster online (which can be slow), has an
   adverse affect on the runtpext custom action that requests ltid.exe and
   vmd.exe to be bounced.  On some clustered NetBackup systems that have a
   large number of devices (tape drives and robots) this can hang the
   cluster install.  

Workaround:
   To resolve this issue, go into the Windows Task Manager and kill both the
   "ltid.exe" and "vmd.exe" processes.  The install will then continue and
   complete successfully.  
--------------------------------------------------------------------------------
Etrack Incident = ET895259

Description:
   Added support for PureDisk export to NetBackup.  
--------------------------------------------------------------------------------
Etrack Incident = ET850034

Description:
   Changes were made to ensure that the device configuration analyzer utility,
   mmcrawl, is working.
--------------------------------------------------------------------------------
Etrack Incident = ET863440

Description:
   A change was made to ensure the nbemmcmd -errorsdb command no longer causes
   a core dump on 64-bit machines.  
--------------------------------------------------------------------------------
Etrack Incident = ET861373
Associated Primary Etrack = ET901494

Description:
   Switches have been added to nbemmcmd to allow the use of a different
   emmserver than those listed in the configuration.  
--------------------------------------------------------------------------------
Etrack Incident = ET863437

Description:
   Formatting is now correct for strings on Windows x64 systems.  
--------------------------------------------------------------------------------
Etrack Incident = ET794493
Associated Primary Etrack = ET777908

Description:
   A restore would fail following a tape span due to attempting to position
   to file number "0".  The bptm logs show that a "STOP RESTORE" was received
   for a restore that was already complete during the tape mount.
--------------------------------------------------------------------------------
Etrack Incident = ET792615
Associated Primary Etrack = ET781425

Description:
   bpjobd script would hang sporadically causing the user to manually restart
   to view the job monitor.  
--------------------------------------------------------------------------------
Etrack Incident = ET864935
Associated Primary Etrack = ET821288

Description:
   If the client for a multiplexed backup could not be contacted, the job would
   take nearly twice as long as to timeout.
--------------------------------------------------------------------------------
Etrack Incident = ET419594

Description:
   Added a new touch-file (/usr/openv/netbackup/IGNORE_ACL) on UNIX client
   machines to not back up ACLs.
--------------------------------------------------------------------------------
Etrack Incident = ET594838

Description:
   On HP-UX clients, NetBackup now treats cifs file system mount points
   as NFS rather than local.  Therefore, policies with ALL_LOCAL_DRIVES
   specified will no longer back them up.
--------------------------------------------------------------------------------
Etrack Incident = ET614569

Description:
   True Image Restore Plus (TIR+) backups currently delete any
   TIR information files that are 10 days old or more.  Symantec
   added a new touch file for UNIX clients to set the number of
   days to keep the TIR information files.  The default will
   remain 10 days, but that can now be set to a value higher
   than 10 if desired.  In addition, setting this value to 0 (zero)
   makes NetBackup never delete old TIR information files.
   
   The touch file is called /usr/openv/netbackup/TIR_INFO_KEEP_DAYS.
   Simply put an integer value in this file that represents the
   number of days to keep the TIR information files.  Numbers that
   are less than 10 will set the value to 10 (other than 0).
--------------------------------------------------------------------------------
Etrack Incident = ET406353

Description:
   Multi-streaming with wild-cards and NEW_STREAM directives would not
   process correctly.    
--------------------------------------------------------------------------------
Etrack Incident = ET864177

Description:
   The deletion of an application cluster would fail if there were storage
   units (STU's) associated with it.

Workaround:
   To avoid this issue, delete storage unit first.
--------------------------------------------------------------------------------
Etrack Incident = ET853592

Description:
   An archive job may complete with the following error:
   
      "EXIT STATUS 3: valid archive image produced, but no files
       deleted due to non-fatal problems"
   
   This is an issue in the underlying operating system and not
   NetBackup. This patch detects the condition and takes the
   additional steps necessary to handle it.

Workaround:
   To resolve this issue, the user may manually remove the backed up
   files after the archive completes. Note that care must be taken
   not to remove files that are created or modified after the start
   of the archive job.
--------------------------------------------------------------------------------
Etrack Incident = ET917548
Associated Primary Etrack = ET901564

Description:
   If a window closes while a multiple data streams backup has children queued,
   the resume of the parent may produce a 200 error.
--------------------------------------------------------------------------------
Etrack Incident = ET803831

Description:
   Executing a bpps -a command on a RedHat 5.0 system would produce
   the following NetBackup processes:
   
     tail: cannot open `+2' for reading: No such file or directory
     tail: cannot open `+2' for reading: No such file or directory
--------------------------------------------------------------------------------
Etrack Incident = ET918511
Associated Primary Etrack = ET860790

Description:
   Changed Policy Execution Manager to log failure history message as an
   informational message to avoid adding it to the error log report.  Also log
   failure history message based on failure history threshold (default
   12 hours) instead of using the policy update interval (default 10 minutes)
   thus reducing the number of entries logged.  

Workaround:
   To avoid this issue, increase the policy update interval threshold from
   the default of 10 minutes.
--------------------------------------------------------------------------------
Etrack Incident = ET860802
Associated Primary Etrack = ET850162

** Description:
   The disk storage unit (DSU) staging did not maintain a retention level on
   secondary copies when using inline tape copy (ITC).  
--------------------------------------------------------------------------------
Etrack Incident = ET849012

Description:
   If nbemm is down and NOM connects to NBSL, then NBSL would
   crash.
--------------------------------------------------------------------------------
Etrack Incident = ET764809
Associated Primary Etrack = ET764804

Description:
   On Linux clients, raw partition backups of raw devices would
   fail with a status 6 error when compression was enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET860288
Associated Primary Etrack = ET857531

Description:
   Policy Execution Manager would stop processing manual backup jobs when
   house keeping was performed (bptm delete_expired). The worst case
   scenario was when the media server could not be reached.  The Policy
   Execution Manager would then wait for the time out
   (CLIENT_CONNECT_TIMEOUT)to be exceeded before moving on.
   
   Changed the Policy Execution Manager to start a third nbproxy which
   processes only clean media database (db) commands to avoid a delay of
   manual backups.
--------------------------------------------------------------------------------
Etrack Incident = ET914057

Description:
   A problem existed that caused an error status on user backups to sometimes
   return a 236 error when a 199 error was expected.  
--------------------------------------------------------------------------------
Etrack Incident = ET867927

Description:
   When using the bpsetconfig command to implement bp.conf entries for a
   client, if stdin was used, the list could not exceed 1023 bytes.  If
   the list did exceed 1023 bytes, the entire list was ignored and the
   update failed.

Workaround:
   To avoid this issue, use the command with the filename as a parameter
   and everything will work properly.
--------------------------------------------------------------------------------
Etrack Incident = ET919129
Associated Primary Etrack = ET848190

Description:
   When Multiple Data Streams, DHCP and Windows Open File Backups (WOFB’s) are
   enabled, jobs end with 48 status.  To resolve this issue, the generic job
   (nbgenjob) was changed to only pass a -hostname option if DHCP is enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET853612

Description:
   The parent job would exit with a status 50 before starting any children.  To
   Resolve this issue, the parent job (nbgenjob) was changed to ping the job
   manager as soon as possible after startup instead of waiting three minutes.  
--------------------------------------------------------------------------------
Etrack Incident = ET832007

Description:
   Logs were unclear on what the problem was when database operations were
   performed on un-assigned media.  
--------------------------------------------------------------------------------
Etrack Incident = ET505726

Description:
   The "bpdbjobs -resume" command no longer reports an incorrect number of
   restores that were resumed.  
--------------------------------------------------------------------------------
Etrack Incident = ET845150

Description:
   The machine update code has been updated so it no longer allows machines to
   have invalid parent keys.  
--------------------------------------------------------------------------------
Etrack Incident = ET591318

Description:
   NetBackup now checks the file list to validate that UNIX
   file paths begin with a "/" character.  This will also
   catch cases where extra characters are added to directives
   (for example, "ALL_LOCAL_DRIVES;").
--------------------------------------------------------------------------------
Etrack Incident = ET856486
Associated Primary Etrack = ET997038

Description:
   Added support for failing over NearStore storage units to a different NetApp
   filer that had been mirrored using NetApp's Volume Snap Mirror technology.  
--------------------------------------------------------------------------------
Etrack Incident = ET919043

Description:
   A job that was configured to use a storage unit group, failed with a
   status 129. The job details for a retry gives the appearance that it
   retried the job with the STU from the previous try. In reality, all of
   the STUs in the group were queried for the best possible candidate.
--------------------------------------------------------------------------------
Etrack Incident = ET838968

Description:
   This maintenance pack contains new versions of ACE and TAO libraries. These
   libraries contain fixes for race conditions and other problems.
--------------------------------------------------------------------------------
Etrack Incident = ET864163

Description:
   A change was made so that nbrb no longer sends "bptm -rptdrv" to an
   inactive node in a cluster.  In addition, the output of the
   nbemmcmd -listhost command has been changed.  The description of
   machine type for emmserver has been changed from "server" to
   "emmserver".
--------------------------------------------------------------------------------
Etrack Incident = ET896185

Description:
   When you log in on a node of master in cluster environment, the "Add STU"
   operation did not show all of the available media servers.

Workaround:
   To avoid this issue, log in using a virtual (cluster) name.
--------------------------------------------------------------------------------
Etrack Incident = ET901549
Associated Primary Etrack = ET857094

Description:
   During testing, an active duplicate job was noticed in the Activity
   Monitor. The job had a status 150 message in detailed status and it was
   still at attempt 1. Its children appeared dead. (No activity in since
   12:47 and they were being displayed as active).  
   
   The parent seemed active. It was not only displayed active but it was
   doing a tape mount around 18:30. It had received a status 150 around
   12:47 pm.

Workaround:
   To avoid this situation, you can wait until the job state is active and
   then cancel it.  This will cause it to die correctly.  
--------------------------------------------------------------------------------
Etrack Incident = ET849073

Description:
   Canceled mount/unmount requests would cause future unmount requests to hang
   in BPTM.  
--------------------------------------------------------------------------------
Etrack Incident = ET901476

Description:
   Changes were made to keyword handling of user backups from
   NetBackup 5.0 to 6.0.  
--------------------------------------------------------------------------------
Etrack Incident = ET814657

Description:
   A backup job would potentially hang if bpbrm received a 174 error (media
   manager - system error occurred) prior to receiving a "media ready"
   indication from bptm.  
--------------------------------------------------------------------------------
Etrack Incident = ET519708

Description:
   The Perform Snapshot Backup option in Policy dialog should be disabled if
   the Block level increment (BLI) is selected.  
--------------------------------------------------------------------------------
Etrack Incident = ET922508
Associated Primary Etrack = ET854626

Description:
   During multiplexed backups, multiple retention levels could be added to a
   media, even if it was not configured to be allowed.  
--------------------------------------------------------------------------------
Etrack Incident = ET515830

Description:
   The SSO_SCAN_ABILITY option was not being used and has been removed to avoid
   confusion.  
--------------------------------------------------------------------------------
Etrack Incident = ET819221
Associated Primary Etrack = ET797322

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

Description:
   NetBackup Enterprise Media Manager (EMM) was using the wrong directory when
   checking for a disk full condition that affected the NetBackup Relational
   Database (NBDB).  If a mirrored transaction log was created, EMM was
   checking the location of the main transaction log only.  
--------------------------------------------------------------------------------
Etrack Incident = ET922513
Associated Primary Etrack = ET896030

Description:
   FlashBackup restores would sometimes produce 252 errors when done with a
   short file list.  
--------------------------------------------------------------------------------
Etrack Incident = ET865177
Associated Primary Etrack = ET864919

Description:
   Freeze scratch media that was found to have a Recorded Volume Serial Number
   (RVSN) was not expected.  Users must use bplabel to correct this problem
   and make the media useable again.  
--------------------------------------------------------------------------------
Etrack Incident = ET850088

Description:
   Policy Execution Manager no longer passes unlocalized status descriptions
   in the error database.
--------------------------------------------------------------------------------
Etrack Incident = ET848632
Associated Primary Etrack = ET841558

Description:
   A fix was added so that nbgenjob no longer fails with status 25
   and nbpem no longer receives a status 50 after a multi-streaming
   job.
--------------------------------------------------------------------------------
Etrack Incident = ET858227

Description:
   NetBackup-Java Administration Console Device Configuration wizard now
   correctly updates the Robot Type of drives that are detected as stand
   alone but drag-dropped by user to a robot.  
--------------------------------------------------------------------------------
Etrack Incident = ET865805

Description:
   On Windows systems, the Vault reports were not being localized.
--------------------------------------------------------------------------------
Etrack Incident = ET896510

Description:
   A change was made to correct an issue that was causing code to appear in a
   progress log.  
--------------------------------------------------------------------------------
Etrack Incident = ET896531

Description:
   A change was made to correct a core dump issue that occurred from vmdareq
   when it was run from a command line with no switches.
--------------------------------------------------------------------------------
Etrack Incident = ET896568

Description:
   The words "handling path" were not being recorded in the \db\error\ logs
   file.  The All Logs Entry and the bperror command both mine their results
   from the \db\error\ logs and the words "handling path" could be used to
   determine if the correct data is being backed up.  
--------------------------------------------------------------------------------
Etrack Incident = ET916389
Associated Primary Etrack = ET863109

Description:
   Changes were added to resolve an nbpem core dump that would occur after a
   successful backup.
--------------------------------------------------------------------------------
Etrack Incident = ET863396

Description:
   NDMP backup fails when TIR data spans tapes.  This failure occurs only for
   NDMP local or NDMP 3-way (backup to an NDMP drive).  

Workaround:
   Rerunning the backup to a different media will likely work since it is
   unlikely that tape spanning will occur during TIR data. (This is because
   the TIR data is usually a fraction of the size of the backup image itself.)
   
   Another approach is add the following line to the file
   <installdir>/netbackup/db/config/ndmp.cfg
   
      NDMP_MOVER_CLIENT_DISABLE
   
   Adding this line will have a minimal impact on backups. However it will
   cause a significant performance impact to dup/verify/import when using
   NDMP drives.
--------------------------------------------------------------------------------
Etrack Incident = ET777981

Description:
   nbpemreq would fail if a large time value was passed to the nbpemreq
   predict option.  If you specified a number that exceeded a long value
   for the command, nbpemreq -predict -dateu <timevalue>, the results
   would be undefined.  
--------------------------------------------------------------------------------
Etrack Incident = ET821317

Description:
   A misleading error status 48 (client hostname could not be found) may be
   applied to a job if a communication problem occurred between the media and
   the master server.  A typical cause of the problem was an expired license
   on the media server.  In this case, the error status should have been 161
   (Evaluation software has expired.)  
--------------------------------------------------------------------------------
Etrack Incident = ET828730

Description:
   In a rare situation, a FlashBackup job could not be cancelled.
--------------------------------------------------------------------------------
Etrack Incident = ET852018

Description:
   Changes have been made to reduce the performance overhead when sending mail
   to a client after a backup job completes.  
--------------------------------------------------------------------------------
Etrack Incident = ET896769
Associated Primary Etrack = ET923399

Description:
   The pem logs report a scheduled backup (SB) job type as an immediate (IB)
   backup job type after a failed immediate backup.  
--------------------------------------------------------------------------------
Etrack Incident = ET864933

Description:
   On Windows media servers, restores from disk in some cases would potentially
   read unneeded data instead of skipping it, which could affect performance.
--------------------------------------------------------------------------------
Etrack Incident = ET805992

Description:
   In some cases, hot catalog backup would report success even though the
   ASA backup was either not successful or conditionally successful.  
--------------------------------------------------------------------------------
Etrack Incident = ET924798
Associated Primary Etrack = ET860296

Description:
   Callers to bpdbm make unnecessary licensing checks that could lead to
   misleading error messages.  
--------------------------------------------------------------------------------
Etrack Incident = ET923799

Description:
   With NetBackup running under NetBackup Access Control (NBAC), authorization
   checks were skipped for some operation of corba daemons.  This could have
   enabled an unauthorized user to perform some privileged operations.  
--------------------------------------------------------------------------------
Etrack Incident = ET924345
Associated Primary Etrack = ET856266

Description:
   Jobs that were due to start, would not start if JobDefinition::checkDueness
   took more than one second.
--------------------------------------------------------------------------------
Etrack Incident = ET901028

Description:
   Changes were made that enable you to now use "./bpnbat -login -info" on
   Linux systems.

Workaround:
   You can also use bpnbat in interactive mode by using just the -login option.  
--------------------------------------------------------------------------------
Etrack Incident = ET778927

Description:
   A master could be renamed to a pre-existing media server.  However, the
   logs were recording the wrong name if a machine was renamed to a
   pre-existing machine.  
--------------------------------------------------------------------------------
Etrack Incident = ET417907

Description:
   When vmquery was used with a prefix containing '_', the char '_' was used
   as a wild card character and an out of order media id could be given.  
--------------------------------------------------------------------------------
Etrack Incident = ET831182

Description:
   The message, "database backup is currently disabled," appeared in the
   Problems report even when a scheduled hot catalog backup was configured.  
--------------------------------------------------------------------------------
Etrack Incident = ET924482

Description:
   The parent key could be incorrectly set when adding a node of a cluster.
   The parent key of a media server could be incorrectly set if node of master
   cluster was given instead of cluster name.  
--------------------------------------------------------------------------------
Etrack Incident = ET534073 ET534196 ET569931 ET592599

Description:
   The following Windows updates have been added to this maintenance pack:
   -  Updated the support utility nbsupport to version 2.1.2
   -  Updated the Windows support utility nbsupport.exe to version 2.1.2
   -  Updated the Windows support utility nbsu_win_cmds.exe to version 2.0
   -  Added the Windows support script fs
--------------------------------------------------------------------------------
Etrack Incident = ET864934

Description:
   A duplication may have been reported as successful if a defective tape
   drive incorrectly reported a tape mark on the read operation, followed
   by an I/O error.  This maintenance pack detects this error condition.  
--------------------------------------------------------------------------------
Etrack Incident = ET803724

Description:
   Catalog recovery from a hot catalog backup failed if Bare Metal Restore
   (BMR) was installed but not configured and/or running at the time of the
   hot catalog backup.  
--------------------------------------------------------------------------------
Etrack Incident = ET648727

Description:
   Added a new Automated Cartridge System (ACS) vendor for media and drive
   types.  
--------------------------------------------------------------------------------
Etrack Incident = ET616381

Description:
   In NetBackup-Java Administration Console, inventory of a robot attached to
   a cluster node resulted in volumes being added with the cluster node as the
   robot control host and not the virtual host name.  This behavior has been
   changed to make the virtual host name as the control host. Doing this
   avoids potential problems in inventory if a cluster fails over to a
   different cluster node.  
--------------------------------------------------------------------------------
Etrack Incident = ET916378
Associated Primary Etrack = ET915043

Description:
   The bpdbjobs timestamp output is no longer truncated for STARTED and ENDED
   fields.
--------------------------------------------------------------------------------
Etrack Incident = ET830327

Description:
   Access failures to the Activity Monitor were occurring for the
   Domino-partitioned, server backup reports file (exec.nbf).
   However, the bpbrm log would exit with a Status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET895584
Associated Primary Etrack = ET786448

Description:
   NetBackup for Lotus Notes parses all the paths in the
   LOTUS_NOTES_PATH variable to determine the Lotus program
   directory.  The first path in the LOTUS_NOTES_PATH variable
   in which "bin/server" is present is treated as a Lotus Program
   directory.  If any other path (for example, the Lotus data
   directory) which is present in the beginning and "bin/server",
   exists in that path then it is misinterpreted as Lotus program
   directory. This causes the backup to fail with a status 9 error.

Workaround:
   To resolve this issue, enter the path of the Lotus program
   directory in the beginning of LOTUS_NOTES_PATH variable.
--------------------------------------------------------------------------------
Etrack Incident = ET842011

Description:
   bpmedialist could not be killed from the Activity Monitor successfully.
   A change was made to ensure the correct program name is being passed from
   bpmedialist to the job manager (JM).  
--------------------------------------------------------------------------------
Etrack Incident = ET639038

Description:
   A correction was made to ensure the vulnerability test for
   bprd (Vuln_bprd.tst) no longer generates a core dump issue.
--------------------------------------------------------------------------------
Etrack Incident = ET925564

Description:
   The "bpdbm –consistency 2" command was removed from the
   list of commands that nbsupport runs.
--------------------------------------------------------------------------------
Etrack Incident = ET926712

Description:
   A small memory leak in Policy Execution Manager when processing change
   events has been corrected.  
--------------------------------------------------------------------------------
Etrack Incident = ET926721

Description:
   Changed the Policy Execution Manager to pass the locale attributes correctly
   to the job manager instead of setting them all to lctype.  
--------------------------------------------------------------------------------
Etrack Incident = ET852018

Description:
   Changes were made to address some small performance issue due to unnecessary
   string duplications in the Policy Execution Manager when mailing client
   status upon job completion.
--------------------------------------------------------------------------------
Etrack Incident = ET498723

Description:
   In the event that a shared standalone drive is updated to be robotic, other
   hosts that share this drive will also be updated to robotic.  If the robot
   is not configured on any of those hosts, however, this results in an
   illegal configuration.  

Workaround:
   To avoid this issue, manually create robotic entries or only use the Device
   Configuration wizard.
--------------------------------------------------------------------------------
Etrack Incident = ET926699
Associated Primary Etrack = ET925811

Description:
   When drives are selected for NDMP restores, NetBackup media servers are
   preferred over NDMP tape servers that are not local to the NDMP host being
   restored to.  

Workaround:
   If a media server has drives with paths to both NetBackup and NDMP servers,
   you should down the NetBackup paths before initiating the restore.  
--------------------------------------------------------------------------------
Etrack Incident = ET852171

Description:
   The EMM server does not reject a client-provided media_id such as, '------'.
   This is not a regression. The NetBackup 5.x behavior was exactly the same.

Workaround:
   This issue is a client application error when such a name comes is used.
--------------------------------------------------------------------------------
Etrack Incident = ET851125
Associated Primary Etrack = ET793484

Description:
   In some instances a job would receive an incorrect 24 status (socket write
   failed) instead of the correct 84 status (media write error).
--------------------------------------------------------------------------------
Etrack Incident = ET846076

Description:
   An incremental hot catalog backup would fail with a 190 error if the master
   server name configured in the hot catalog backup policy differed from the
   currently active master server name where each name is a valid name for the
   host.  This would occur if the long name was used in the policy, but the
   short name was being used in the bp.conf file.  
--------------------------------------------------------------------------------
Etrack Incident = ET863389

Description:
   Duplication of NDMP image fails when using non-NDMP drives.
   
   This problem only occurs when the duplication is using the shared memory
   method (SHM) method.  In NetBackup 6.0, this happens for any NDMP backup
   that used MM (non-NDMP) drives (also known as, "Remote NDMP"). In addition,
   this happens if an NDMP image is duplicated to a non-NDMP drive and then
   the duplicated image is duplicated.
   
   The progress log shows the following error:
       ERR - Unable to create data socket to receive TIR data.  

Workaround:
   To avoid this issue, disable the shared memory method by adding the
   following touch file:
       <installdir>/netbackup/NOSHMDUP  

Additional Notes:
   This problem has been fixed in this maintenance pack, such that all
   duplications of NDMP backup images using non-NDMP drives will now use
   the shared memory method.
   
   (This problem was solved by disabling shared memory method for all
   NDMP images in the NetBackup 5.1 maintenance packs.)
--------------------------------------------------------------------------------
Etrack Incident = ET828441

Description:
   NetBackup relational databases would not be restarted when a cold catalog
   backup was canceled.  
--------------------------------------------------------------------------------
Etrack Incident = ET930028

Description:
   A hot catalog backup parent job no longer fails with a status 818 error
   (retention level mismatch).  
--------------------------------------------------------------------------------
Etrack Incident = ET893639 ET417284

Description:
   When NetBackup is clustered, NOM would show the wrong information about
   services and media.  
--------------------------------------------------------------------------------
Etrack Incident = ET583036

Description:
   Restoring a Lotus database link no longer results in a loss of data.
--------------------------------------------------------------------------------
Etrack Incident = ET922076

Description:
   When a database link is restored on UNIX platform, it is restored with the
   size of the original database it was pointing to when the backup was taken.
--------------------------------------------------------------------------------
Etrack Incident = ET865713

Description:
   Under NBAC, 'bpnbaz -setupsecurity' could fail silently, potentially
   compromising the desired access control hierarchy.  
--------------------------------------------------------------------------------
Etrack Incident = ET854649

Description:
   The shutdown and startup of the NetBackup relational databases, NBDB and
   BMRDB, will be logged to the NetBackup error log.  
--------------------------------------------------------------------------------
Etrack Incident = ET928712
Associated Primary Etrack = ET897092

Description:
   NetBackup Job Manager (NBJM) could take a long time to unload drives,
   or fail to unload drives because the media servers all had multiple
   endpoints, many that were on unreachable networks.
   
   For example, an unreachable network would take about 225 seconds to
   fail on Solaris, and some callbacks would take about 10 to 15 minutes
   to iterate all failed endpoints.
   
   A change was added to the endpoint selection algorithm so that if
   there is at least one endpoint that matches the server list, it will
   only attempt those endpoints that match the server list.
--------------------------------------------------------------------------------
Etrack Incident = ET927755
Associated Primary Etrack = ET926665

Description:
   On some Windows machines, any Firewall_in bpconf configuration would report
   as "Malformed Firewall_in line" in the VxUL log files, and rendered the
   NAT translation feature as not operational.
--------------------------------------------------------------------------------
Etrack Incident = ET926704
Associated Primary Etrack = ET926503

Description:
   If a user backup submits a very large number of files, PEM may cause a
   memory fragmentation and possibly a crash.  

Workaround:
   To resolve this issue, reduce the file list size by specifying directories
   instead of individual files.  
--------------------------------------------------------------------------------
Etrack Incident = ET857478
Associated Primary Etrack = ET838788

Description:
   NetBackup currently treats all read-only HFS file systems
   on Mac OS X as CD-ROMs and disallows the backup.  This
   change allows the backup of mounted read-only file systems
   that are not CD-ROMs.
--------------------------------------------------------------------------------
Etrack Incident = ET515549 ET933307

Description:
   The CIsActive function that is loaded from the NBClusterConfig.dll failed on
   64-bit systems.

Additional Notes:
   The use of VCS API calls, which did not support 64-bit platforms in the
   past, have been removed.  IsActive simply tests if the shared disk resource
   is on the current system to determine if it is the active node.  
--------------------------------------------------------------------------------
Etrack Incident = ET932016 ET988979 ET1002606

Description:
   Buffer overflow areas have been identified and corrected in daemons that
   run on Veritas NetBackup master, media, and client servers. Successful
   access to a vulnerable Veritas NetBackup server and the ability to
   successfully execute arbitrary code could potentially result in
   unauthorized access with elevated privilege on a system.  
--------------------------------------------------------------------------------
Etrack Incident = ET932003

Description:
   A change was added to resolve a possible memory corruption issue in the
   legacy DA process (vmd on EMM server).  
--------------------------------------------------------------------------------
Etrack Incident = ET927553
Associated Primary Etrack = ET924626

Description:
   Fixed an issue that caused bpbkar to hang on Linux systems if it encounters
   an NFS mount point when the NFS server is down.  

Workaround:
   To resolve this issue, add the NFS mount point to the exclude list for the
   client.  
--------------------------------------------------------------------------------
Etrack Incident = ET854810

Description:
   By using the bprestore command (/usr/openv/netbackup/bin/bprestore) it is
   now possible to restore an image using a non-primary copy.  

Workaround:
   In addition, you can use the bpchangeprimary command
   (/usr/openv/netbackup/bin/admincmd/bpchangeprimary) to change the primary
   copy of the image.  
--------------------------------------------------------------------------------
Etrack Incident = ET533389

Description:
   For a True Image Restore (TIR) that is larger than 2GB, the following error
   would occur when reading the TIR information.
   
      Error occurred reading TIR information, expected -2103963310 bytes, read
      2191003986
   
   The bpdm log would show the following:
   
      11:03:32.958 [20388] <16> read_data_tir: ERR - Error occurred reading TIR
      information, expected -2103963310 bytes, read 2191003986
   
      2191003986 is the size of the TIR file -
      -rw-------  1 root root  2191003986 Dec 30 10:50
      devnfs2-bkup_1135889406_C1_TIR.1135889406.img
   
   The problem only occurred, when the TIR file was larger than 2GB.
--------------------------------------------------------------------------------
Etrack Incident = ET863133

Description:
   A fix was added so that a hot catalog recovery from a hot catalog backup to
   a new master server name no longer fails.  
--------------------------------------------------------------------------------
Etrack Incident = ET925227
Associated Primary Etrack = ET922389

Description:
   When the client name is in upper case, a Windows backup uses WOFB even
   though the clientDB entry disables the WOFB.

Workaround:
   To resolve this issue, use the same case for client name in client
   database and policy database.
--------------------------------------------------------------------------------
Etrack Incident = ET895746

Description:
   The renewal of a machine credential issued by a non-root authentication
   broker no longer fails.  
--------------------------------------------------------------------------------
Etrack Incident = ET932264
Associated Primary Etrack = ET893298

Description:
   An issue existed that would sometimes cause a job to run on the exclude day
   even if a frequency scheduling of 24 hours was used.  
--------------------------------------------------------------------------------
Etrack Incident = ET829853

Description:
   FlashSnap Instant Recovery rotation would fail on Linux
   because of a bprd request popen failure.
--------------------------------------------------------------------------------
Etrack Incident = ET855922

Description:
   Catalog archiving would fail intermittently with the following message:
   
   bpcatarc: failure running catalog archiving backup policy: the specified
   policy is not active (247)

Workaround:
   This problem was observed with a mis-configured /etc/hosts file, which
   caused excessively long DSN lookups.  To avoid this situation, configure
   the /etc/hosts file to avoid long DSN lookups.  
--------------------------------------------------------------------------------
Etrack Incident = ET796521
Associated Primary Etrack = ET704676

Description:
   A backup job would fail with a status 130 when a client path
   exceeded 1023 characters.

Workaround:
   To avoid this issue, add the long directory path to an exclude
   list.
--------------------------------------------------------------------------------
Etrack Incident = ET893368 ET893377 ET893379

Description:
   If a Catalog Cleanup operation is kicked off in the middle
   of a Hot Catalog Backup, the operation may clean up expired
   image catalog entries that were given to the Hot Catalog Backup
   in its file list, causing the Hot Catalog Backup to finish
   with a partial success.
   
   Changes have been made so that a Hot Catalog Backup now completes with
   success status of 0. In addition, it internally detects the cleaned up
   image catalog entries, and quietly ignores them.
--------------------------------------------------------------------------------
Etrack Incident = ET930124

Description:
   A change has been made to ensure that NBPEM finds all user-initiated jobs,
   all of the time.
--------------------------------------------------------------------------------
Etrack Incident = ET933326
Associated Primary Etrack = ET917312

Description:
   nbnos would core dump on an HP-UX master server with max_thread_proc set at
   the default value of 64.  Every nbpem restart would cause nbnos to create
   more threads.  Corrections were made to nbpem that prevent nbnos from
   creating new threads every time nbpem is restarted.  
--------------------------------------------------------------------------------
Etrack Incident = ET649458

Description:
   The VRTS VxFS file system does not support named data streams
   that contain directory structures.  A check was added to warn
   users if a named data stream that contains a directory structure
   is found during file processing.  Such structures will not be
   backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET933586
Associated Primary Etrack = ET932325

Description:
   During a multi-streamed database backup (MS-SQL backup in this case), the
   media gets unmounted/mounted again intermittently. Ideally, the NetBackup
   resource broker (nbrb) should try to use the loaded media (preferably same
   media) for all streams.  
--------------------------------------------------------------------------------
Etrack Incident = ET915850
Associated Primary Etrack = ET915879

Description:
   Changes were made to ensure that multi-threaded processes no longer crash.  
--------------------------------------------------------------------------------
Etrack Incident = ET918766

Description:
   Sorting would not work on some columns if the report contained one or more
   hidden columns.  
--------------------------------------------------------------------------------
Etrack Incident = ET933398
Associated Primary Etrack = ET933394

Description:
   Backups may not run as expected if full and incremental had the same
   frequency.  
--------------------------------------------------------------------------------
Etrack Incident = ET926835
Associated Primary Etrack = ET794461

Description:
   Corrected a possible truncation of a file's user or group name.
   This change allows for a full 32 character user and group name.
--------------------------------------------------------------------------------
Etrack Incident = ET931959
Associated Primary Etrack = ET931900

Description:
   Corrected errors that caused canceled backups to leave the tape media
   without a valid empty header on it.  
--------------------------------------------------------------------------------
Etrack Incident = ET850961
Associated Primary Etrack = ET809378

Description:
   The restore of database and compressed files could fail with
   a status 5 when "overwrite existing files" was not selected
   and the files to be restored exist.
--------------------------------------------------------------------------------
Etrack Incident = ET819697

Description:
   This maintenance pack contains enhancements and fixes to some minor errors
   that were occurring in NOM (specifically in the Display Point version of
   NetBackup in NOM).  
--------------------------------------------------------------------------------
Etrack Incident = ET797596

Description:
   On the NOM user interface, (Managing > Media > Details) the "Time Assigned"
   filter was not functioning properly.
--------------------------------------------------------------------------------
Etrack Incident = ET896513

Description:
   NBPEM e-mail function would send a secondary "additional information" e-mail
   for some failed backups.
--------------------------------------------------------------------------------
Etrack Incident = ET892407

Description:
   Corrected an issue that caused bplabel to fail if VxSS (NBAC) is enabled.  
--------------------------------------------------------------------------------
Etrack Incident = ET807751

Description:
   The "import" feature would not work on a NOM Windows server after an
   "export" database (DB) function was performed.  
--------------------------------------------------------------------------------
Etrack Incident = ET852129

Description:
   Under NBAC, a NetBackup 5.1 media server or client could not be configured
   with NetBackup 6.0 master.
   
   The bpnbat -loginmachine command would cause a hang or failure on a
   NetBackup 5.1 media server or client.  The following logs were produced.
   
   14:52:27.578 [2035] <2> get_string: (7) inadequate buffer space for data
   14:52:27.578 [2035] <2> get_string: read until the buffer was full; got:
   14:52:27.578 [2035] <2> get_string: EXIT STATUS 13
   14:52:27.578 [2035] <2> bprd_get_nbac_pdr_info: get_string() failed,
     Error 0 (0), success  
--------------------------------------------------------------------------------
Etrack Incident = ET794712
Associated Primary Etrack = ET785847

Description:
   Changes were added to increase the efficiency of an image cleanup when the
   disk-stage storage unit (DSSU) fills.  
--------------------------------------------------------------------------------
Etrack Incident = ET934452

Description:
   The machine state could be reported inaccurately from the
   nbemmcmd -listhosts -verbose command if the machine state was inactive
   for disk jobs.  
--------------------------------------------------------------------------------
Etrack Incident = ET853808 ET898992

Description:
   A multi-streamed parent job may have been retried more than the configured
   number of times if the parent job failed before the streams were created for
   the first time.  
--------------------------------------------------------------------------------
Etrack Incident = ET797314

Description:
   Add VxUL Logging support for Activity Monitor module and as a result
   a new log file with ID 263 will be generated in the logs folder.
--------------------------------------------------------------------------------
Etrack Incident = ET935814

Description:
   Corrected the check used to determine if the local device_mappings.txt
   is current.
--------------------------------------------------------------------------------
Etrack Incident = ET806878
Associated Primary Etrack = ET814738

Description:
   A multi-threading issue would occasionally cause bpstsinfo
   to core dump on some platform and operating system combinations.
--------------------------------------------------------------------------------
Etrack Incident = ET913578

Description:
   NBSL is crashing due to the read only directory or invalid path of nbsl.xml.  
--------------------------------------------------------------------------------
Etrack Incident = ET936802
Associated Primary Etrack = ET924495

Description:
   The backup of a directory that contains a large number of
   files using wild cards would fail with a STATUS 70.

Workaround:
   To resolve this issue, specify the directory in question in
   the file list rather than using wild cards.
--------------------------------------------------------------------------------
Etrack Incident = ET933518 ET933543 ET544382 ET933547 ET933544 ET933528 ET933537
ET830317 ET830319 ET916879
Associated Primary Etrack = ET814702 ET799749 ET647499 ET899240 ET851802
ET858011

Description:
   The following changes were added to this maintenance pack in response to
   customer escalations:
   - Issues with pop-ups that occurred when FlashBackup terminated
   - Restores from multiple images
   - Multi-volume image and 32-bit overflow
   - Incorrect handling of multi-byte characters
   - Incomplete data being sent to catalog
   - Ensure that directories are restored in descending order
   - Hard-link restore problems
   - Linux master and FlashBackup windows  
--------------------------------------------------------------------------------
Etrack Incident = ET861506

Description:
   The Job Manager must forward a snap ID from a non-streamed Windows open
   file backup (WOFB) to the Policy Execution Manager for VSP cache files
   to be cleaned. In addition, changed the Policy Execution Manager to add
   SNAP_ID directives to include the file list.  
--------------------------------------------------------------------------------
Etrack Incident = ET918477
Associated Primary Etrack = ET917028

Description:
   This is limited to the Nearstore storage unit.
   If an incremental backup was done after a synthetic full backup, and no
   other full backups existed on that volume, then the incremental would fail.  
--------------------------------------------------------------------------------
Etrack Incident = ET899124
Associated Primary Etrack = ET899121

Description:
   This issue only affected restores from Nearstore storage units.
   Non-full backups (a subset of the entire backup ) where files were pulled
   from fragments other than fragment 1 would fail.  The issue was that the
   image relative offset was not being tracked and NetBackup was seeking to
   the incorrect offset within the image.  

Workaround:
   To resolve this issue, use the Nearstore File System Export functionality
   or duplicate the entire backup to basic disk or some other media.
--------------------------------------------------------------------------------
Etrack Incident = ET924417
Associated Primary Etrack = ET917312

Description:
   Please see etrack
--------------------------------------------------------------------------------
Etrack Incident = ET921795

Description:
   Changes were made in this maintenance pack to ensure the Log Management
   feature is working.  
--------------------------------------------------------------------------------
Etrack Incident = ET932217

Description:
   NBJM was failing jobs with a status 818 (retention level mismatch) because
   of an incorrect check.
--------------------------------------------------------------------------------
Etrack Incident = ET937680

Description:
   Some TLD libraries with barcode readers were unable to import or inventory
   media with an unbarcoded media in the library.  
--------------------------------------------------------------------------------
Etrack Incident = ET831697

Description:
   Added some exception handling code to this maintenance pack.
--------------------------------------------------------------------------------
Etrack Incident = ET569949

Description:
   This change enables the localization team to localize the XML files for VxUL
   logs.  
--------------------------------------------------------------------------------
Etrack Incident = ET831189

Description:
   NetBackup shutdown would not terminate parent jobs (nbgenjob).  A change
   was made to the Policy Execution Manager to terminate all parent jobs
   with a 50 status (EC_client_aborted).  

Workaround:
   To resolve this issue, manually terminate all nbgenjob processes.
--------------------------------------------------------------------------------
Etrack Incident = ET857404

Description:
   Changes were added to correct possible null pointer issues.  
--------------------------------------------------------------------------------
Etrack Incident = ET933508

Description:
   Added the latest version of VxMS 4.3.018 in this maintenance
   pack.
--------------------------------------------------------------------------------
Etrack Incident = ET851163
Associated Primary Etrack = ET849091

Description:
   Changes have been added to ensure that send_mail() validates
   all parameters it receives.
--------------------------------------------------------------------------------
Etrack Incident = ET866302 ET893368

Description:
   The catalog cleanup process will not run to completion because it yields to
   a catalog backup. If the cleanup process is long or if catalog backups are
   frequent, the cleanup will not be able to delete expired images.
   
   This maintenance pack contains a fix that enables catalog cleanup and
   catalog backup to run in parallel. If a cleanup operation runs when a hot
   catalog backup is in progress, it might delete images that were sent to
   bpbkar earlier (in its image directive list), and cause the hot catalog
   backup to finish with a partial success. This fix detects this situation
   and returns the right error code to bpbkar.
   
   The cleanup and catalog backup running in parallel is now the default
   behavior.  However, this can be disabled by creating a file called
   "CLEANUP_WAIT_FOR_CATBKUP" in netbackup/db/config (for UNIX) and
   \NetBackup\db\config (for Windows).
   
   This fix also enables images to be expired and deleted using bpexpdate
   even when a hot catalog backup is in progress.

Workaround:
   To resolve this issue, disable hot catalog backups to allow cleanup to
   run to completion.  
--------------------------------------------------------------------------------
Etrack Incident = ET808281

Description:
   bpdbm incorrectly sets the PFI_TYPE to 0. It must check if the copy being
   deleted is a Persistent Frozen Image (PFI) or not and set the PFI_TYPE to 0
   (only when the copy being deleted is a PFI).  
--------------------------------------------------------------------------------
Etrack Incident = ET802974
Associated Primary Etrack = ET802966

Description:
   The read_files_file queries would fail with a status of 249 because bpdbm
   had not received the flist_complete yet.
--------------------------------------------------------------------------------
Etrack Incident = ET862545
Associated Primary Etrack = ET862538

Description:
   Importing NetBackup 5.0 NDMP images would fail with an error code 42
   from db_end().  
--------------------------------------------------------------------------------
Etrack Incident = ET863352
Associated Primary Etrack = ET863351

Description:
   The command "bperror -d <start date/time> -e <end date/time>" would not
   give the correct result when daylight time saving was involved.  
--------------------------------------------------------------------------------
Etrack Incident = ET542191

Description:
   The success_fail_msg function in nb/media/bpbackupdb.c is for an offline
   catalog backup on online catalog backups.  
--------------------------------------------------------------------------------
Etrack Incident = ET863358
Associated Primary Etrack = ET848205

Description:
   Internationalization (I18N): An NDMP restore with a Japanese directory
   name no longer fails.  
--------------------------------------------------------------------------------
Etrack Incident = ET972452

Description:
   Block Level Incremental (BLI) backups of DB2 databases
   would fail on Linux.
--------------------------------------------------------------------------------
Etrack Incident = ET965811
Associated Primary Etrack = ET964501

Description:
   Duplication (with multiplexing preserved) hangs for multiplexed TIR
   images when using NetBackup 6.0 MP4.  

Workaround:
   To resolve this issue, do not preserve multiplexing when duplicating,
   or do not use multiplexing. In addition, this may slow down performance.  
--------------------------------------------------------------------------------
Etrack Incident = ET962923

Description:
   NetBackup Service Layer (nbsl) no longer core dumps during install,
   sched_bkup, and uninstall tests.
--------------------------------------------------------------------------------
Etrack Incident = ET965512

Description:
   The VSS authorization tables were updated to include the new EMM interfaces.  
--------------------------------------------------------------------------------
Etrack Incident = ET983962

Description:
   An earlier change was made to keep track of open file
   descriptors.  Descriptors are pushed onto a stack as files
   are opened and popped from the stack when they are closed.
   For file pointers the fileno of the pointer is used.  On
   Linux, when a file pointer is closed, the pointer value is
   reset by the operating system.  This caused problems with
   fileno and it is possible to cause segmentation violations.
   
   The fix is to replace existing "close then pop" sequences
   with a macro that does a "pop then close" sequence on Linux
   and a "close then pop" on other platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET973985
Associated Primary Etrack = ET931484

Description:
   Multiplexed SAP backups that were using (Standard) AES-128 Encryption
   would fail with the following error: "ERR - backup failed 49 <client
   did not start>".
--------------------------------------------------------------------------------
Etrack Incident = ET974342
Associated Primary Etrack = ET972826

Description:
   A change has been made to ensure that a non-streamed, Windows open file
   backup, runs the right schedule.  
--------------------------------------------------------------------------------
Etrack Incident = ET915448
Associated Primary Etrack = ET915442

Description:
   Adding an operating system (OS) group to a Role in NBAC does not give the
   Appropriate permissions to members of that OS group.
--------------------------------------------------------------------------------
Etrack Incident = ET928695 ET492823
Associated Primary Etrack = ET928687

Description:
   In certain cases, PBX logs were not being pruned according to settings in
   /etc/vx/VxICS/icsul.conf.  

Additional Notes:
   UNIX PBX runtime components are being updated in this maintenance pack along
   with the NetBackup Server.  
--------------------------------------------------------------------------------
Etrack Incident = ET990874
Associated Primary Etrack = ET974535

Description:
   A timing problem was introduced in the last patch that could
   cause multiplexed TIR backups to fail.  This was due to a
   backup ending as another was recording the TIR information.
--------------------------------------------------------------------------------
Etrack Incident = ET831965

Description:
   NetBackup 6.0 disk staging storage unit’s high water mark (HWM) and low
   water mark (LMW) are not changeable for an application cluster
   (AppCluster) configuration.  Currently, the AppCluster Configuration does
   not have a NetBackup version so it is treated as a pre-NetBackup 6.0
   storage unit, where the HWM is set to the previous behavior of 100 percent
   and a LWM did not exist, therefore it is set to a default value of
   80 percent.  Both of these settings were new in NetBackup 6.0 and are not
   configurable in pre-NetBackup 6.0 versions.

Workaround:
   The AppCluster version number must be at the same version level as
   the servers that make up the AppCluster.  To resolve this issue, the
   user should manually enter the NetBackup version number for the
   AppCluster using the nbbemmcmd command. In addition, all of the
   NetBackup servers in the AppCluster should be at the same, specified
   version.
   
   As an example, you would use the following command on the master
   server to update the NetBackup version number for an AppCluster.
   
   nbemmcmd -updatehost -machinename virtual_name -machinetype app_cluster
   -netbackupversion 6.0
   
   where virtual_name is the virtual name of the application (AppCluster).
--------------------------------------------------------------------------------
Etrack Incident = ET991906

Description:
   Changes were made to ensure that a Vault operator could operate properly in
   an NBAC environment.
--------------------------------------------------------------------------------
Etrack Incident = ET991647
Associated Primary Etrack = ET990896

Description:
   After installing the BMR boot server to a Windows system with a
   NetBackup 6.0 MP maintenance pack installed, and then performing a repair
   on the pack to apply the BMR boot server binaries, the user should copy
   the binaries to the correct directory location.  If a NetBackup
   installation was installed to a alternate location, the repair will not
   correctly apply the patch binaries to the alternate location.  

Workaround:
   Again, to resolve this issue, copy the binaries, after performing the
   "repair" option to the correct directory.
--------------------------------------------------------------------------------
Etrack Incident = ET992949

Description:
   V_snprintf uses vsnprintf to implement a fix for uncommon strcat usage.  On
   the Windows platforms, vsnprintf did not guarantee a null terminated buffer.  
   Specifically, this was true if the data in the buffer exactly filled the
   destination without leaving room for the null termination.  In this case,
   the buffer would not be null terminated and the function would crash when
   V_strlcpy is called.  
--------------------------------------------------------------------------------
Etrack Incident = ET990034

Description:
   When an inline tape copy job with multiplexed protocol was resumed after a
   checkpoint, the job was restarted instead of resumed.  
--------------------------------------------------------------------------------
Etrack Incident = ET996117
Associated Primary Etrack = ET990855

Description:
   Changes were made so that direct calls to the signal (),SBT implementation
   no longer occurs.
   
--------------------------------------------------------------------------------
Etrack Incident = ET994229
Associated Primary Etrack = ET993986

Description:
   A condition existed that caused failed jobs to exceed a configured number of
   tries.  
--------------------------------------------------------------------------------
Etrack Incident = ET992223

Description:
   When checkpoint restart was enabled, and the "continue" flag was set in
   the schedule, bptm terminated the copy when an error on that copy
   occurred.  When the copy terminates, for multiplexing, no more jobs were
   scheduled for the multiplexed group. However, in rare cases there is a
   timing window where jobs may have already been started but not yet
   processed by bptm.  In this case, incomplete fragment cleanup occurred
   for the failed copy.
--------------------------------------------------------------------------------
Etrack Incident = ET997950
Associated Primary Etrack = ET984069

Description:
   Oracle proxy copy incremental (CINC) backups are no longer running as full
   Backups.
--------------------------------------------------------------------------------
Etrack Incident = ET992959
Associated Primary Etrack = ET993079

Description:
   In some scenarios, the resource broker (RB) was orphaning resources that
   were already marked to be released. This caused extra processing overhead
   and communication overhead between nbrb and nbjm.  
--------------------------------------------------------------------------------
Etrack Incident = ET999559

Description:
   The pack installer will now log server system information such as EMMSERVER
   (remote or local), media versus master server, and inactive cluster node.  
--------------------------------------------------------------------------------
Etrack Incident = ET998728

Description:
   The NetBackup version is now displayed in the nbemmcmd -listhosts -verbose
   output.  
--------------------------------------------------------------------------------
Etrack Incident = ET1000607

Description:
   Symantec Code Repository Revision Tags was added to some files, to enable
   better tracking.  
--------------------------------------------------------------------------------
Etrack Incident = ET999754

Description:
   If there were multiple copies of a backup, and a duplication was requested
   for disk source copy 1 (or any disk copy other than the last), the
   duplication might be started as a non-shared memory duplication.  A shared
   memory duplication is preferable for performance reasons.  
--------------------------------------------------------------------------------
Etrack Incident = ET1001117

Description:
   For Windows, added Sybase ASA service dependency to the NetBackup Resource
   Broker.  
--------------------------------------------------------------------------------
Etrack Incident = ET970398

Description:
   In an NBAC setup, a volume configuration that uses the user interface wizard
   would fail with an error 39.
--------------------------------------------------------------------------------
Etrack Incident = ET1008736
Associated Primary Etrack = ET966429

Description:
   bpstart_notify would not get executed if the dos 8.3 pathname option was
   turned off on NTFS partitions.  After disabling dos 8.3 pathnames,
   bpstart_notify would not run. bpbkar32.exe reports the bpstart_notify script
   has started and ended, but the contents would not be executed.  
--------------------------------------------------------------------------------
Etrack Incident = ET1005425

Description:
   NetBackup pem would consistently terminate when an orphan job existed.  
--------------------------------------------------------------------------------
Etrack Incident = ET1003200
Associated Primary Etrack = ET1003184

Description:
   bprecover would crash during a recovery of a BMR database file that exceeded
   2GB in size.  
--------------------------------------------------------------------------------
Etrack Incident = ET990295

Description:
   During multi-eject operations the vmchange program would return a
   status code 0 (success) if another eject operation was in progress.
   vmchange now returns a status code 223 (STATUS_ROBOT_BUSY) when another
   eject operation is in progress.  This problem primarily affected vault
   eject operations.  
--------------------------------------------------------------------------------
Etrack Incident = ET997925

Description:
   Stream discovery would ignore the preprocess interval and use the default of
   four hours.  A change was made so that the preprocess interval is now passed
   from Policy Execution Manager to the Job Manager and then to the parent job
   (nbgenjob) on the command line using the -preprocessInterval option.  
--------------------------------------------------------------------------------
Etrack Incident = ET1013849

Description:
   The host list would be empty if a cluster node name was given instead of
   virtual cluster name.  
--------------------------------------------------------------------------------
Etrack Incident = ET1003608

Description:
   Duplication to an FSE Nearstore storage unit failed if the
   –stsdeletefiles process returned a status 1 (which is valid). A change
   has been made that allows a duplicate to complete successfully if a
   status 1 is encountered from -stsdeletefiles.
--------------------------------------------------------------------------------
Etrack Incident = ET1013509

Description:
   A change was made to disable sorting on the Elapsed time and Active elapsed
   time columns.  
--------------------------------------------------------------------------------
Etrack Incident = ET1013882

Description:
   Manual configuration of ACS libraries does not always record the library
   serial number.
--------------------------------------------------------------------------------
Etrack Incident = ET1014147

Description:
   In certain conditions a robotic daemon would become "UP" even though the
   device monitor showed drives under AVR control.  
--------------------------------------------------------------------------------
Etrack Incident = ET1010767
Associated Primary Etrack = ET990884

Description:
   Immediate backups jobs would not initiate properly causing nbpem to return
   the following statuses: msgsndd status = 0; send status 0; and bprd exit
   status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET1016131

Description:
   A change was made to implement support for Instant Recovery with Windows
   FlashBackup policies.  
--------------------------------------------------------------------------------
Etrack Incident = ET1014974
Associated Primary Etrack = ET892850

Description:
   Backups written by 64-bit Linux servers were unreadable by non-64-bit Linux
   servers.  
--------------------------------------------------------------------------------
Etrack Incident = ET1012144 ET1016961

Description:
   Added support for a new Automated Cartridge System (ACS) vendor media and
   drive type.  
--------------------------------------------------------------------------------
Etrack Incident = ET1011704
Associated Primary Etrack = ET1015054

Description:
   The robotic control daemon would not handle robots with more than
   128 drives.  
--------------------------------------------------------------------------------
Etrack Incident = ET1015612

Description:
   Corrected an issue that would not allow you to write to disk and resulted
   in an error code 84 (media write error).
--------------------------------------------------------------------------------
Etrack Incident = ET1018156 ET1016311
Associated Primary Etrack = ET1008244 ET1011211

Description:
   The window checking routine would sometimes schedule jobs to run
   multiple times in one window, or even skip a window.  
--------------------------------------------------------------------------------
Etrack Incident = ET925285
Associated Primary Etrack = ET834682

Description:
   Internationalization (I18N) issue: An issue existed that caused the content
   of a notification e-mail to illegible.
--------------------------------------------------------------------------------
Etrack Incident = ET1017152
Associated Primary Etrack = ET1013059

Description:
   If there are transient environmental hostname lookup issues, nbrb may
   core dump near \"__nscd_get_map_ref\".
--------------------------------------------------------------------------------
Etrack Incident = ET1019073
Associated Primary Etrack = ET988955

Description:
   TIR files that were than 2GB were not able to be read because the size was
   stored in a 32-bit integer and the math used to turn that into a 64-bit
   integer caused a large negative value to be stored on some platforms. This
   maintenance pack contains a fix that contains explicit casts at appropriate
   junctures.  This issue was found on a Nearstore storage unit but would have
   affected any disk storage unit if TIR was being used.  
--------------------------------------------------------------------------------
Etrack Incident = ET1009036
Associated Primary Etrack = ET936732

Description:
   A change was made to correct an nbpem core dump issue that occurred because
   a null pointer was being passed to libc::strcmpstack.
--------------------------------------------------------------------------------
Etrack Incident = ET1020129
Associated Primary Etrack = ET1003895

Description:
   It is possible for an NDMP restore to be successful and still produce a
   status code 83 when media is write protected and spans media.  The bptm
   log will contain a messagesimilar to the following:
   
   15:51:14.479 [6272.8404] <16> open_ndmp_device: cannot open ndmp device
   nrst07a, error code 11 (NDMP_WRITE_PROTECT_ERR)  

Workaround:
   The restore completes successfully, so you can ignore the error status.
   Or you can unmark the tape to make it write protected.  
--------------------------------------------------------------------------------
Etrack Incident = ET1016884

Description:
   Corrected the use of ejecting to the "any" cap (a function used by Vault)
   when ejecting to ACS robotics. Also corrected use of -w option when
   ejecting to ACS robotics from the command line.  
--------------------------------------------------------------------------------
Etrack Incident = ET1015650

Description:
   Lotus Notes user-directed backups were failing if the notes.ini path
   specified through the user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1006573

Description:
   A change was made so that the Managing -> Job Policies -> Details, user
   backup & user archive policies are no longer shown twice.
--------------------------------------------------------------------------------
Etrack Incident = ET1012757

Description:
   The server connection would fail while upgrading the Master
   Server from NetBackup 60MP4 to NetBackup 60MP5 on a TRU64
   system.
--------------------------------------------------------------------------------
Etrack Incident = ET1024918

Description:
   Changes were added to resolve an intermittent pem core dump issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1021373

Description:
   Corrected an issue that caused FlashBackup Windows single-file restores to
   fail.  
--------------------------------------------------------------------------------
Etrack Incident = ET1022947 ET1062137
Associated Primary Etrack = ET984055

Description:
   Status was being sent to the client after the stsdeletefiles
   process was run. If that process took too long, the client
   timed out. The backup was successful however the archive bits
   on the client were not cleared, so the same files were backed
   up in the next incremental, even though that was not necessary.
   
   The result was that incremental backups were essentially running
   as full backups.
--------------------------------------------------------------------------------
Etrack Incident = ET518074
Associated Primary Etrack = ET1009431

Description:
   Upgraded the Sig Scheduler to 2.60.030 in this maintenance pack.
--------------------------------------------------------------------------------
Etrack Incident = ET1020081

Description:
   A change was added so that when printDueJobs accesses the work list it will
   lock the list to avoid potential issues with other threads trying to access
   the work list.  
--------------------------------------------------------------------------------
Etrack Incident = ET995592

Description:
   Conversion of the policy include file-list entries failed resulting in
   blank entries.  A change was made to the nbproxy conversion code to use
   language codeset setting of "utf8" for HP platforms, otherwise "UTF-8" for
   all other platforms to prevent the conversion from returning an error saying
   the input was invalid.  
--------------------------------------------------------------------------------
Etrack Incident = ET1024066

Description:
   Corrected a bpdm core dump that occurred with V_strverify on a Linux IA-64
   System.
--------------------------------------------------------------------------------
Etrack Incident = ET1023729
Associated Primary Etrack = ET1027068

Description:
   A storage unit update operation (from the NetBackup-Jave Administration
   Console) will fail if the user is logged into the system using the node name
   (not the virtual name).  

Workaround:
   To resolve this issue, use the virtual name.
--------------------------------------------------------------------------------
Etrack Incident = ET1027605
Associated Primary Etrack = ET1024835

Description:
   ShadowImage snapshots failed on an AMS500 because the product
   ID was set to DF6 and yet it was interpreted as a 9500.

Workaround:
   To resolve this issue, set the Product ID to DF7 as the code
   currently expects.
--------------------------------------------------------------------------------
Etrack Incident = ET1026332
Associated Primary Etrack = ET1018020

Description:
   A restore attempt, using a duplicated copy of a standard backup image
   that was duplicated using NDMP attached tape drive, would fail with exit
   status 25 (cannot connect on socket). The failure occurred because bpdm
   was started instead of bptm.  
--------------------------------------------------------------------------------
Etrack Incident = ET1028083

Description:
   The ltid reports that the user had configured more drives than they were
   licensed for, when they were using multiple drive paths.  
--------------------------------------------------------------------------------
Etrack Incident = ET1028405

Description:
   A change was made to ensure that the Windows FlashBackup Policy Type is
   disabled when the Advanced Client license key is not installed.  
--------------------------------------------------------------------------------
Etrack Incident = ET1029379
Associated Primary Etrack = ET971543

Description:
   For FlashBackup Windows incremental backups, the extents for named streams
   associated with directories were not being examined and put in the bitmap.  
--------------------------------------------------------------------------------
Etrack Incident = ET858201
Associated Primary Etrack = ET850921

Description:
   A hot catalog backup with a large number of image catalog entries
   can run out of memory.  

Workaround:
   For a temporary fix to the memory issue, contact Symantec Support and inquire
   about Emergency Engineering Binaries (EEBs) that are available for this issue,
   or perform an offline backup, or a cold catalog backup.  
--------------------------------------------------------------------------------
Etrack Incident = ET1028058

Description:
   An incorrect group and ownership on a libdbjodbc9.so symbolic link file has
   been corrected.  

Additional Notes:
   This change only affects HP-UX on RISC hardware.  
--------------------------------------------------------------------------------
Etrack Incident = ET1026006

Description:
   Under nb/idl/NBPolicyTypes.idl, many new fields were added for
   NetBackup 6.5.  This created problems for NOM 6.5 to support 6.0 MP5
   masters. To avoid this issue, Symantec added the new fields in 6.0 MP5
   as reserved fields which will resolve this issue.  
--------------------------------------------------------------------------------
Etrack Incident = ET1028169

Description:
   NetBackup will now be shutdown in runlevel 1 on Solaris systems.  
--------------------------------------------------------------------------------
Etrack Incident = ET1032876
Associated Primary Etrack = ET963719

Description:
   Changes were made to correct a Dr Watson error caused by bpbkar.
   
   Bpbkar would cause a Dr Watson error on the client while backing up
   encrypted files.  The job consistently failed with an exit status 13
   while backing up the following directory: E:\QuickBase\server\dbs\.
   
   Files that were backed up were continuously changing. A third party
   application would capture changes made from the end user (web user)
   to a .delta file, the delta file was then written to the files in the
   directory, "E:\QuickBase\server\dbs\", only after the user had closed
   the web application. The .delta files were continuously changing, and
   the changes made to the directory were approximately 10 gigabytes
   an hour.  
--------------------------------------------------------------------------------
Etrack Incident = ET1026986
Associated Primary Etrack = ET1005324

Description:
   Cleaning jobs that were initiated because of a TapeAlert or frequency would
   fail if they did not complete in six minutes.  
--------------------------------------------------------------------------------
Etrack Incident = ET1036385
Associated Primary Etrack = ET1006915

Description:
   A disk staging job that runs from one media server to another,
   where the media server that is performing the write operation
   is a UNIX system, will fail some of the jobs and/or hang.

Workaround:
   To resolve this issue, create the following touch file on the
   master server:
   
   For UNIX:
      /usr/openv/netbackup/NODTTSDUP
   
   For Windows:
      VERITAS\NetBackup\NODTTSDUP  
--------------------------------------------------------------------------------
Etrack Incident = ET1035288

Description:
   NetBackup 6.0 does not provide a way to perform device monitor queries for a
   single media server.  Users must sift through all servers' output for the
   data needed.  This maintenance pack adds the option -hostdevmon to the
   vmoprcmd command line to provide a single server's device state.  
--------------------------------------------------------------------------------
Etrack Incident = ET1040339
Associated Primary Etrack = ET1027138

Description:
   Increased the drive ready timeout for TLD drives to 14 minutes to
   incorporate a worst case scenario of 14 minutes for LTO drives in
   an effort to remove bad media.  
--------------------------------------------------------------------------------
Etrack Incident = ET1039797

Description:
   When a full data directory is restored, the recovery was failing due to a
   truncation of the database name.  
--------------------------------------------------------------------------------
Etrack Incident = ET1038347
Associated Primary Etrack = ET996144

Description:
   After a WOFB backup, bpbkar32 would clean up an active
   FlashBackup- Windows snapshot - because PEM did not send the
   SET SNAP_ID for snapshots that should be retained on the client.

Workaround:
   To resolve this issue, reschedule the backups of the C: and D: drives so
   that they start -and- complete at non-overlapping time periods
   However, for some customers this is not practical because they may have
   volumes that are in the range of 800GB ~ 1TB. In addition, some of their
   servers may have more than one volume that needs to be protected using
   Flashbackup
   
   In this circumstance, Symantec suggests the customer sets the priority
   of the C: drive backup to a higher value than the Flashbackup policy;
   and then for the affected clients that are part of their Flashbackup
   policies, using the Master Server Host Properties > Client Attributes >
   Set Max jobs/client option and setting it to 1.
--------------------------------------------------------------------------------
Etrack Incident = ET1039117
Associated Primary Etrack = ET1038317

Description:
   "bpmedia -movedb" starts bptm on the old server to move the media
   database. If the old server and the new server are at NetBackup 6.0
   (or post 6.0), then there is no need to start bptm. All the
   operations can be done in bpmedia.  This also helps the scenario
   where one of the media server is offline or de-commissioned (and
   all the steps for de-commissioning the media server are not followed).  
--------------------------------------------------------------------------------
Etrack Incident = ET992572
Associated Primary Etrack = ET892420

Description:
   The bppllist -allpolicies -U command would not return all policies.
   In addition, when recreating the issue, an application fault
   against bppllist was also found.
--------------------------------------------------------------------------------
Etrack Incident = ET1050190

Description:
   Changes were made to correct the NetBackup 6.0 MP5 NetWare
   build.
--------------------------------------------------------------------------------
Etrack Incident = ET1047982
Associated Primary Etrack = ET914734

Description:
   The V_* functions would sometimes cause binaries with incorrect
   signal handlers to core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET1050372
Associated Primary Etrack = ET1047809

Description:
   Sybase 11.9.x backups no longer fail on HP-UX 11.00 after upgrading to
   NetBackup 6.0.  
--------------------------------------------------------------------------------
Etrack Incident = ET1046813

Description:
   Online catalog backup was failing with a status 50 when writing to a
   password-protected DR path in an environment with NBAC installed.  

Workaround:
   To avoid this issue, store the DR file in a path which the running NetBackup
   bpbdm process has write access to without changing credentials.  
--------------------------------------------------------------------------------
Etrack Incident = ET1047911

Description:
   A description of the new '-copy' option is missing from the bprestore
   command line usage.  
--------------------------------------------------------------------------------
Etrack Incident = ET1051657
Associated Primary Etrack = ET1045602

Description:
   The NetBackup service layer (nbsl) would not start on a
   master server using PA_RISC 1.1 architecture if nbsl was
   compiled with PA_RISC 2.0.
--------------------------------------------------------------------------------
Etrack Incident = ET1050488

Description:
   Corrected an issue that caused ltid to fault after it was started.
--------------------------------------------------------------------------------
Etrack Incident = ET1050393
Associated Primary Etrack = ET1036542

Description:
   ACS robot pre-eject operations sometimes show volumes that are
   NOT_IN_LIBRARY when they actually are.  This is due to a buffer
   length problem in the acsd robotic daemon.  This primarily affects
   Vault ejects to ACS robots.  
--------------------------------------------------------------------------------
Etrack Incident = ET1052551

Description:
   Intermittent issues were found when ejecting multiple CAP-fulls of
   media with the latest ACSLS patch, PUT0701S.  
--------------------------------------------------------------------------------
Etrack Incident = ET1051474

Description:
   Some ACS_SDLT* media will not be mapped correctly to NetBackup media types
   when specifying the mapping in vm.conf.  
--------------------------------------------------------------------------------
Etrack Incident = ET1054463
Associated Primary Etrack = ET1039776

Description:
   After changing the bp.conf SERVER entry from short name to FQDN
   (or vice versa) and when performing a hot catalog backup with Vault,
   the Vault job will fail with a status 294, even though the catalog
   backup was successful.
   
   Now, instead of using gethostname() results when vault performs a
   validation, the client name (as configured in the policy) will be
   used.  

Workaround:
   UNIX ONLY: In the imageDB directory, create a symbolic link between
   FQDN and short names.  
--------------------------------------------------------------------------------
Etrack Incident = ET1053444

Description:
   A change was made that corrects a crash using bpplschedrep.  
--------------------------------------------------------------------------------
Etrack Incident = ET1052430
Associated Primary Etrack = ET1032378

Description:
   Added a fix to correct an nbjm crash in TAO_Transport::handle_input.
--------------------------------------------------------------------------------
Etrack Incident = ET1018993

Description:
   On some SuSE 10 servers, when NetBackup asks the system if
   it is the name listed as the EMM Server in the bp.conf file
   at boot time, it incorrectly answers no.  This correction asks
   several times and usually the second attempt gives the correct
   answer.
   
   This causes a 55 second delay, with starting NetBackup daemons,
   on SuSE 10 servers that are not MM Servers.

Workaround:
   To resolve this issue, run the following start command after a
   system has rebooted.
   
      /usr/openv/netbackup/bin/goodies/netbackup
--------------------------------------------------------------------------------
Etrack Incident = ET1060972
Associated Primary Etrack = ET1038232

Description:
   When Enterprise Vault performs backups to NetBackup using the
   VxBSA file APIs, the backups can fail.  Enterprise Vault posts
   an event error entry saying Failed to send file (error 00000003:
   System detected error, operation aborted.).  Check the NetBackup
   Activity Monitor.
   
   Examination of the exten_client debug log shows that following
   type of error being logged.
   07:13:13.973 [9820.5196] <16> bsa_WriteFileList: ERR - filelist
   file <C:\Program
   Files\VERITAS\NetBackup\Logs\user_ops\dbext\logs\
   vxbsa.1177038793.9820.5196.files.1> open() failed: Errno=24:
   <Too many open files>
--------------------------------------------------------------------------------
Etrack Incident = ET1018093

Description:
   An error occurred on a Windows setup that caused a failure to
   occur when copying files.
--------------------------------------------------------------------------------
Etrack Incident = ET1047888
Associated Primary Etrack = ET1041180

Description:
   The NDMP jobs' drives were sometimes pre-empted with a local
   or incorrect drive path.
--------------------------------------------------------------------------------
Etrack Incident = ET1063773
Associated Primary Etrack = ET1063750

Description:
   A crash in nbemm would occur if an inventory was attempted
   while the database server was down.  This would easily happen
   if a site was performing a cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1064798

Description:
   A DB2 restore now has the ability to redirect a DB2 database
   to a different owner from the original owner (both owners
   being from the same group). A new backup of the source DB2
   database is required so the correct group permission is on the
   image to allow the alternate user to perform a restore to the
   new instance, or database.  
--------------------------------------------------------------------------------
Etrack Incident = ET1066935
Associated Primary Etrack = ET1062088

Description:
   bpdbm crash can occur, during a recovery, if a damaged image
   file exists prior to the recovery.  

Workaround:
   To avoid this issue, manually remove all damaged image files
   before attempting a recovery.
--------------------------------------------------------------------------------
Etrack Incident = ET1066885

Description:
   Listing storage unit groups were leaking memory.  Changes were
   added to resolve the memory leaks.
--------------------------------------------------------------------------------
Etrack Incident = ET1067176
Associated Primary Etrack = ET1001827

Description:
   Jobs are not being cleaned from job database even after the
   KEEP_JOBS_HOURS was run.
--------------------------------------------------------------------------------
Etrack Incident = ET1067996
Associated Primary Etrack = ET1058482

Description:
   Changes were made to resolve memory leak issues in NBJM
   and NBPEM.
--------------------------------------------------------------------------------
Etrack Incident = ET1070595

Description:
   NOM no longer creates multiple NBProxy processes when there
   is no job activity.
--------------------------------------------------------------------------------
Etrack Incident = ET1073038

Description:
   An NetBackup EMM memory leak was detected in the xxxFetch()
   implementation causing EMM to consume more memory over time.

Workaround:
   To resolve this issue, restart the EMM process.
--------------------------------------------------------------------------------
Etrack Incident = ET1062791

Description:
   Corrected an issue where the NetBackup Job Manager (NBJM) could
   not be terminated and it had to be killed.
--------------------------------------------------------------------------------
Etrack Incident = ET1061742
Associated Primary Etrack = ET1058482

Description:
   Added changes to correct a memory leak found in the NetBackup
   policy execution manager (PEM).
--------------------------------------------------------------------------------
Etrack Incident = ET1066381
Associated Primary Etrack = ET1066374

Description:
   The INCR frequency schedule would run multiple times within a
   window with an incorrect snapid.
--------------------------------------------------------------------------------
Etrack Incident = ET1068635

Description:
   The NetBackup service layer (NBSL) crashes on an HP-UX system.

Workaround:
   To avoid this issue, default catch blocks were added to handle
   all other exceptions in the Proxy client.
--------------------------------------------------------------------------------
Etrack Incident = ET1075834

Description:
   An issue exited that caused jobs to remain queued when a
   196 error should have occured.
--------------------------------------------------------------------------------
Etrack Incident = ET1076967
Associated Primary Etrack = ET1033590

Description:
   A crash would sometimes occur in bpdbm when the cleanup process
   was cleaning one of the images of a duplication, where the
   duplication had failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1076060

Description:
   The NetBackup PEM would terminate because of a timeout to the
   nbproxy for getLastBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET1078998
Associated Primary Etrack = ET993531

Description:
   The NetBackup Service Layer (NBSL) will not stay running and the
   following error is produced.
   
   Windows error 1063 - Windows SCM unable to start it as a service.

Workaround:
   To avoid this issue, increase the service-registration timeout
   from the Windows-registry.
--------------------------------------------------------------------------------
Etrack Incident = ET1078584

Description:
   Running backups that have streaming enabled (and perform
   incremental backups whose file list changes) may encountered
   the following problem.
   
   When stream discovery is done and some existing streams are shuffled
   because new files are being added or existing streams being deleted,
   the streams files are shuffled but the "lastbackup" time is saved for
   the streams that remain.  Therefore, when a new stream maps to a
   preexisting stream with a date of zero (since there was no prior
   backup) you want to avoid doing a query for "lastbackup" with that
   stream number because it will return the "lastbackup" time for the
   stream that was shuffled or deleted.  If you avoid doing a query
   for "lastbackup" when the date is zero you also keep the streams
   from shuffling and the query returning a "lastbackup" time from a
   different stream.
--------------------------------------------------------------------------------
Etrack Incident = ET1079359
Associated Primary Etrack = ET899380

Description:
   A change was added that corrects a Status 805 error condition on
   resubmitted, failed, multiple-data stream child jobs using snapshots.
--------------------------------------------------------------------------------
Etrack Incident = ET1079272
Associated Primary Etrack = ET1049382

Description:
   AIX master servers were unable to restore Windows Flashbackup
   images. This was because of a problem linking the VxMS libraries
   in the AIX compile. A change has been added to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1083381

Description:
   Policy Execution Manager would core dump when reading a policy because
   of a configuration change event.
-------------------------------------------------------------------------------
Etrack Incident = ET1092076

Description:
   NOM receives data from NBSL regarding changes in policy, storage units,
   processes and services information, and so forth through events. When
   the nbnos process is terminated, NBSL cannot deliver these events to NOM.
   
   After restarting the nbnos process, the event delivery mechanism should
   resume and NOM should continue to get data from NBSL, but it fails.
--------------------------------------------------------------------------------
Etrack Incident = ET1092060

Description:
   When invoking the Device Configuration Wizard from the NetBackup-Java
   Administration Console, a dialog box named "Device Configuration
   Wizard - Initialization" shows the error "unknown error".  
--------------------------------------------------------------------------------
Etrack Incident = ET1095578
Associated Primary Etrack = ET1094524

**Description:
   If bpbrm/bptm terminates abnormally while executing multiple jobs and
   another job is added to this multiplexed group by the Resource Broker, it is
   possible that a data loss could occur.
--------------------------------------------------------------------------------
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_CLT_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 = ET831404

Description
   The BAR user interface failed to connect to Oracle 10.1.0.5.0
   instances on UNIX platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET633395

Description:
   A change has been added that prevents bpduplicate from overwriting the
   heap accounting information and causing the bpduplicate to crash by
   copying a string into destination string that is too small.
--------------------------------------------------------------------------------
Etrack Incident = ET634272

Description:
   Backup of multiple VxFS file systems using NetBackup's Advanced Clients
   Frozen Image Backup method failed in close_vxfs_filesystem() of the
   previous open VxFS checkpoint.

Workaround:
   Backup one filesystem at a time for frozen image backups.
--------------------------------------------------------------------------------
Etrack Incident = ET638325

Description:
   NetBackup log messages no longer show up in the /etc/security/password
   file on AIX systems.  
--------------------------------------------------------------------------------
Etrack Incident = ET638699

Description:
   The Policy Execution Manager (PEM) would crash while PEM was shutting down,
   if it was shutting down at the same time a progress log was being updated.
--------------------------------------------------------------------------------
Etrack Incident = ET617254 ET617889 ET640121

Description:
   Hot Catalog Backup would not backup images when IDIRSTRUCT equaled 1
   because the code expected the master server had a second or later version
   of the catalog image directory structure, for example, IDIRSTRUCT = 2.
   
   In a UNIX cluster environment, the VAR_GLOBAL_PATH is linked to the shared
   drive. The backup client (such as, bpbkar) does not follow symbolic links
   currently and therefore the files inside the linked directory would not be
   backed up in an online catalog backup.
   
   Excessive bpdbm debug log entries were produced from a Hot Catalog Backup.
   This fix ties the logging of libcatbackup debug messages to the following
   setting.
   
   BPDBM_VERBOSE setting.
   Example of affected log message:
   00:00:02.032 [8398] < 2> db_ImgUnlock: db_ImgUnlock(833d698) error(0)
--------------------------------------------------------------------------------
Etrack Incident = ET636334 ET636411 ET636414

Description:
   The hot catalog backups would fail if the CRYPT_OPTION was set to REQUIRED
   in bp.conf, where it could also be set through the GUI->Host Properties->
   Clients->Encryption tab.  

Workaround:
   To avoid this issue, set CRYPT_OPTION to ALLOWED, which is the default.
--------------------------------------------------------------------------------
Etrack Incident = ET617892

Description:
   For an imported catalog backup image, the command line instruction
   "bprecover -r -nbdb" would not work because the parent image ID was
   missing in imported ASA image header.  

Workaround:
   To avoid this issue, open the imported catalog image header file and
   remove the PARENT_IMAGE_ID line so that the ASA and the catalog backup
   image header files do not contain the field.
--------------------------------------------------------------------------------
Etrack Incident = ET642003

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

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 DHCP clients and Dynamic 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

Description:
   A condition existed that caused NetBackup Service Layer (NBSL) to core
   dump in HostSessionImpl::ping().
--------------------------------------------------------------------------------
Etrack Incident = ET638703

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 TIR backup to tape after the TIR data had
   been pruned from the catalog would fail.  
--------------------------------------------------------------------------------
Etrack Incident = ET630777

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 ODBC, shared memory connections used
   space in /tmp by default.  If there were issues creating files in /tmp,
   the connection would fail.  To resolve this issue, the environment
   variable, ASTMP, is now set to /usr/openv/tmp.
--------------------------------------------------------------------------------
Etrack Incident = ET636795

Description:
   Added the capability to do a step-wise downgrade of the NetBackup
   Relational Database schema. This enables you to uninstall one or more
   maintenance patches in the order in which they were applied.  
--------------------------------------------------------------------------------
Etrack Incident = ET621857

Description:
   Unable to create or modify disk staging storage units using the
   NetBackup-Java Administration Console if a NetBackup 5.x system was
   upgraded to NetBackup 6.0 or if a NetBackup 5.x license key was used
   during a NetBackup 6.0 server installation.  
   
   This pack corrects this issue and enables you to create or modify disk
   staging storage units using the NetBackup-Java Administration Console
   if a NetBackup 5.x system is upgraded to NetBackup 6.0 using the 5.x
   license or you could update to a NetBackup 6.0 license key.  
--------------------------------------------------------------------------------
Etrack Incident = ET644627

Description:
   On the active node, if the user has installed this pack on a secure
   VCS Windows cluster environment that has a NetBackup server with EMM,
   and are observing that NetBackup does not come online, the Enterprise
   Media Manager (EMM) database schema did not update properly.  

Workaround:
   To avoid this issue, performing 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

Description:
   A condition existed that caused the NetBackup resource Broker (nbrb) to
   core dump under heavily loaded conditions. This problem had occurred
   on AIX and HP-UX. There was lot of locking and unlocking involved in the
   area where the resource broker (RB) sends the resources to the job manager.
   RB was using reverse lock provided by ACE. Either RB was not using the
   lock correctly or there was some issue in the ACE's implementation of
   reverse lock which caused this core dump. To address the issue, the
   lock/unlock logic was simplified.  
--------------------------------------------------------------------------------
Etrack Incident = ET617893

Description:
   TIR-enabled backups (including FlashBackup and NDMP) could fail in the
   validation phase of the backup because of a miscalculated file size.  This
   patch provides earlier detection of the error and improved reporting on the
   cause of the error.  
--------------------------------------------------------------------------------
Etrack Incident = ET641172

Description:
   Online catalog backups in configurations with cluster 5.x media servers
   were creating a bpbackupdb process that looped infinitely.  
--------------------------------------------------------------------------------
Etrack Incident = ET628709

Description:
   A change was made so that EMM now verifies that all nodes in a cluster are
   configured either as masters or media servers.  EMM should not allow
   media-master configurations among the cluster nodes.
--------------------------------------------------------------------------------
Etrack Incident = ET646623

Description:
   The default method for NetBackup ODBC connections to the NetBackup database
   (NBDB)/EMM database is to use shared memory followed by tcpip if shared
   memory fails.  This is controlled by the LINKS=shmem,tcpip{PORT=13785}
   parameter in the database connection string.
   
   On some platforms, there have been intermittent issues with shared memory
   connections to the Sybase ASA database.
   
   To work-around this issue, a new parameter has been aded to the vxdbms.conf
   dfile to set the LINKS parameter in the connection string.  To change this
   parameter to only use tcpip connections, the following line
   was added to vxdbms.conf:
   
       VXDBMS_LINKS = tcpip{PORT=13785}
   
   The vxdbms.conf file is located in /usr/openv/db/data (UNIX) and
   InstallPath\VERITAS\NetBackupDB\data (Windows).
--------------------------------------------------------------------------------
Etrack Incident = ET641145

Description:
   A problem existed that caused, in a few rare cases, f-list files in the
   catstore subdirectories to have a mixed set of UNIX-style and Windows-style
   path separators or even incorrect path entries.  The code currently assumes
   only one style of path separator was being used which caused problems for
   hot catalog backup.
   
   On Windows master servers this results in a partially successful
   (status 1) hot catalog backup job.
   
   On UNIX or Linux master servers this results in a failed (status 67)
   hot catalog backup job on patch levels prior to MP4 and in a partially
   successful (status 1) hot catalog backup job on patch levels MP4 and
   later.  (UNIX or Linux master servers are now consistent with Windows
   master servers in the status for this condition.)
   
   A message similar to the following should be seen in the bpbkar debug log
   if this bug is encountered:
   
   ERR - Unable to expand hot catalog backup directive: CATALOG_BACKUP  

Workaround:
   It is reasonably straightforward to manually identify, edit, and correct
   the offending f-list files to avoid this problem.
--------------------------------------------------------------------------------
Etrack Incident = ET593700

Description:
   Added a check so that any backups going to a file system export-enabled
   Nearstore storage unit must have TIR enabled. This is because the
   sts_delete_files process, which is part of the file system export backup,
   requires the TIR data.  
--------------------------------------------------------------------------------
Etrack Incident = ET632204

Description:
   Media locations in ACS robotics were not updated properly after dismount
   or during inventory when moving from standalone to robotic.  
--------------------------------------------------------------------------------
Etrack Incident = ET644756 ET702144

Description:
   In cases where a user authenticated against a non-root broker a failure to
   load a credential from disk could occur. This would result in false
   negative access checks for users leading to a Backup, Archive, and Restore
   user interface rather than the NetBackup Administration console.  

Workaround:
   To avoid this issue, authenticate against the root broker on the master
   server rather than another broker.  
--------------------------------------------------------------------------------
Etrack Incident = ET630539

Description:
   Corrected the vm.conf mapping of the ACS T10000 media types to HCART2.  
--------------------------------------------------------------------------------
Etrack Incident = ET500024

Description:
   Oracle backups no longer fail with a NetBackup status 227.
--------------------------------------------------------------------------------
Etrack Incident = ET646981

Description:
   The NDMPagent 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

Description:
   Due to a memory management issue, the Volume Manager Daemon could
   crash during certain media management operations.  
--------------------------------------------------------------------------------
Etrack Incident = ET646985

Description:
   NDMP backups failed with a status 84 when writing a TIR fragment.
   
   The bptm log showed an error where the expected block position is one off.
   This error occurred in the function write_data_tir().

Workaround:
   To avoid this issue, add the following line to the file
   <installdir>/netbackup/db/config/ndmp.cfg
   
       NDMP_MOVER_CLIENT_DISABLE
   
   This will have a minimal impact on backups. However it will cause a
   significant performance impact to dup/verify/import when using
   NDMP drives.
--------------------------------------------------------------------------------
Etrack Incident = ET640207

Description:
   Allow the end user to specify pool numbers when creating a new volume pool.
   A new option (-pnum) was added to the vmpool command to facilitate this.  
   
   The new usage is:
   
   vmpool [-pnum <pool number>] -add <pool_name> "<description>" <host> <uid>
   <gid>
   
   The -pnum option must be specified before the -add option.  The -pnum has
   no effect when the -change option is specified.  
--------------------------------------------------------------------------------
Etrack Incident = ET627870

Description:
   The image will not be closed correctly and a data loss will occur during
   duplication or staging where the following is true:
   
   - The destination storage unit (STU) is a volume on a Nearstore with
     version 7.2 of ONTAP.
   - The disk storage unit option for 'enable block sharing' is set.
   
   The first duplication or DSSU_POLICY backup to the Nearstore will complete
   successfully, but subsequent operations using that image (such as, restore
   and incremental backups) will not succeed.
--------------------------------------------------------------------------------
Etrack Incident = ET630303

Description:
   If there was an error in a scheduled report, the report that caused the
   error would not appear in the corresponding email.
--------------------------------------------------------------------------------
Etrack Incident = ET612141

Description:
   The "File System Export" button on the Storage Unit dialog will be
   available when NetBackup media server 6.0MP3 or higher version is
   connected to a 7.2 ONTAP Nearstore or higher version as a
   7.1 ONTAP Nearstore cannot export a file system.  
--------------------------------------------------------------------------------
Etrack Incident = ET640456 ET632241 ET630393 ET632790

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

Description:
   The nbpem showed jobs were due but not queued.  
--------------------------------------------------------------------------------
Etrack Incident = ET638693 ET649607

Description:
   Changes were added to resolve an nbpem crash.  
--------------------------------------------------------------------------------
Etrack Incident = ET419599

Description:
   NetBackup could get an error 130 when backing up VxFS file systems on AIX
   platforms that were mounted under non-VxFS file systems that had ACLs on
   them.  
--------------------------------------------------------------------------------
Etrack Incident = ET638703

Description:
   Changes were made to keep nbpem from hanging or suspending on a
   start_bpexpdate.
--------------------------------------------------------------------------------
Etrack Incident = ET649692 ET636127

Description:
   Changes were incorporated to address slow start times on user backups.  
--------------------------------------------------------------------------------
Etrack Incident = ET646015

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

Description:
   The NBJM returns a normal status to NBPEM after the request to resubmit a
   job failed.  
--------------------------------------------------------------------------------
Etrack Incident = ET699915

Description:
   When a backup failed and went from an incomplete to a failed state,
   the child job would not run again.  The Policy Execution Manager
   would not run child jobs after a failure due to the Job Manager changing
   the job type from a resume to a restart.
--------------------------------------------------------------------------------
Etrack Incident = ET699915

Description:
   When a backup failed and went from incomplete to a failed state,
   the child job would not run again.  
--------------------------------------------------------------------------------
Etrack Incident = ET700003

Description:
   A disk staging storage unit (DSSU) relocation job failed with a status 96,
   in spite of available media.
--------------------------------------------------------------------------------
Etrack Incident = ET700745

Description:
   Multiplexed restore jobs would possibly fail when the number of active
   jobs reached the maximum of 32.  When this error occurred, the bptm log
   would have an entry similar to the following:
   
   12:21:15.296 [3471] <16> bct_find_nonactive: FATAL - cannot find
   non-active Backup Control Table entry
--------------------------------------------------------------------------------
Etrack Incident = ET626205

Description:
   Added a call to Sybase's dbvalid command when NBDB or BMRDB databases
   were started after a cold catalog backup, catalog recovery, or by
   nbdb_admin -start.  In addition, added an nbdb_admin -validate
   option to call dbvalid at any time.  
--------------------------------------------------------------------------------
Etrack Incident = ET700802

Description:
   Prepare to restore failed on an AIX client if a volume group contained a
   disk or disks that were multi-pathed.  
--------------------------------------------------------------------------------
Etrack Incident = ET617061

Description:
   Changes were made to ensure that NBSL no longer core dumps in
   JobIMOMObject::CheckAndUpdateJobInfoData().
--------------------------------------------------------------------------------
Etrack Incident = ET644612

Description:
   The VCS agent and configuration scripts were added for the following
   platforms:
      -  HPIA64
      -  Linux64

Additional Notes:
   To configure and run NetBackup as a VCS clustered application on
   HPIA64 and Linux64 platforms, the base NetBackup must be installed along
   with this patch.  Without this patch, cluster configuration cannot be
   performed on these platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET621934

Description:
   When two or more DSSUs fill up, they are unable to independently reclaim
   disk space. This could cause additional backup jobs to fail (error 129) to
   these two unrelated DSSUs if space reclamation took too long.  
--------------------------------------------------------------------------------
Etrack Incident = ET632300

Description:
   The tpconfig manual user interface would not successfully add shared
   robot/drives.
--------------------------------------------------------------------------------
Etrack Incident = ET627293 ET617051

Description:
   The NetBackup Service Layer (NBSL) no longer core dumps when failing
   over the cluster or if NBSL creates zombie threads.
--------------------------------------------------------------------------------
Etrack Incident = ET703004

Description:
   If NetBackup Access Control (NBAC) was enabled prior to an upgrade
   from 6.0GA (or 6.0MP1) to 6.0MP2, any non-Administrator, non-root
   users in the NBU_Security Admin Group would lose their Access Control
   privileges after the upgrade.

Workaround:
   There are three workaround options available to you, that you can use
   to avoid this issue:
   
   First workaround option:
   ------------------------
   Add the Non-admin user to the “Security Administrators” group in
   VxAZ.  To do this, perform the following steps:
   
   1.  Open the VxSS user interface (/opt/VRTSat/bin/runvssatgui.sh
   2.  Open the appropriate Authorization Server (top right button).
          Connect to it using root.
   3.  Select the “Authorization Groups” button on the left panel.
   4.  Select the “Security Administrators” group in the tree.
   5.  Select the menu option Authorization > Authorization Groups >
          Add Member.
   6.  Add the non-Admin user using the dialog that appears.
   7.  The non-Admin user should now have the necessary permission.  
          This should not circumvent any other security because this
          user now has security privileges on VxAZ.  If this is not
          appropriate, contact Symantec Support for help in taking other
          other measures, such as read-only access to Security
          information.  
   
          Note:  The non-Admin user SHOULD have permission without
          taking this step.
   
   Second workaround option:
   ------------------------
   Uninstall the VxAZ installation and reinstall.  Re-configure NBAC by
   Running “bpnbaz –SetupSecurity <server>” and the appropriate
   “bpnbaz –AllowAuthorization” commands.
   
   Note:  This option will cause any customization to be lost.
   
   Third workaround option:
   ------------------------
   Only use Admin users for Security Operations.
--------------------------------------------------------------------------------
Etrack Incident = ET621194

Description:
   Hot Catalog Backups were not cleaning old logs in the
   /usr/openv/netbackup/logs/user_ops/dbext/jobs and
   /usr/openv/netbackup/logs/user_ops/dbext/logs folders.
   
--------------------------------------------------------------------------------
Etrack Incident = ET649659

Description:
   A change has been made that makes it possible to correct old EMM database
   entries in the device mappings file.
   
--------------------------------------------------------------------------------
Etrack Incident = ET703078

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

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

Description:
   Changes have been made for various problems that include named streams
   associated with directories, and performance issues.  In addition, these
   changes fix a problem with an HP master that was not able to load the
   restricted version of libxm.
--------------------------------------------------------------------------------
Etrack Incident = ET703215 ET771306

Description:
   A change has been implemented that allows a local client install of a
   Macintosh platform as well as other non-server platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET704832

Description:
   When using virtual storage units and after a cluster application failover,
   the active node was not being set correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET640484

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

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

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

Description:
   Using the catalog archive process, files were not being removed from the
   catstore directory.  In addition, running the catalog archive process while
   an online catalog backup was in process could have caused the catalog
   backup to fail.

Additional Notes:
   A new option, "-remove_dotf", has been added to the bpcatarc command.  This
   option eliminates the need to pipe the output from bpcatarc to bpcatrm to
   remove .f files.  If the new option is not used, you must continue to pipe
   the output from bpcatarc to bpcatrm to remove .f files.
--------------------------------------------------------------------------------
Etrack Incident = ET768361

Description:
   update_clients -Install_ADC no longer fails if the client HOME is something
   other than /.
--------------------------------------------------------------------------------
Etrack Incident = ET633295 ET620589 ET767219 ET771458

Description:
   Log Recycling enables NetBackup users to control the amount of disk space
   that is used for logs.  Prior to this change, the disk could fill with
   log files.  
   
   Previous options available for controlling disk use was available via
   either 1) user intervention with the vxlogmgr –d command, 2) a cron job
   that called vxlogmgr -d, or 3) the ‘Keep Logs’ setting in the
   NetBackup-Java Administration Console.  These options were often inadequate
   because they are time-based pruning, while VxUL log recycling is
   continuous.  Often, time-based pruning has been inadequate because the log
   files filled the disk before the time-based pruning has chance to execute.
   
   For more detailed information about Log Recycling, refer to the following
   TechNote on the Symantec Support Web site.
   
     http://entsupport.symantec.com/docs/279590
--------------------------------------------------------------------------------
Etrack Incident = ET766166

Description:
   Block-level incremental (BLIB) backups were not working with the SAP
   database agent.
--------------------------------------------------------------------------------
Etrack Incident = ET768448

Description:
   Could not manually create NDMP or Media Manager storage units using the
   NetBackup-Java Administration console.  Using the bpstuadd –nodevhost
   command would return the message, “Remote Media Servers not allowed for
   NetBackup Server”.
--------------------------------------------------------------------------------
Etrack Incident = ET768441

Description:
   vmphyinv no longer fails while changing media residence.
--------------------------------------------------------------------------------
Etrack Incident = ET769421

Description:
   When selecting the preferred machine name for a cluster node, which will
   be stored in the EMM database, ignore any REQUIRED_INTERFACE entries in
   vm.conf or bp.conf (Registry on Windows).

Workaround:
   To avoid this issue, remove the REQUIRED_INTERFACE entries from vm.conf and
   bp.conf (Registry on Windows) before installing NetBackup 6.0.  This only
   pertains to cluster environments.
--------------------------------------------------------------------------------
Etrack Incident = ET768457

Description:
   The nbemmcmd –deletehost command no longer fails if a storage unit is set
   to, "Any Available Host".
--------------------------------------------------------------------------------
Etrack Incident = ET767144

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

Description:
   User-directed archives no longer delete files if warnings are generated
   During the backup portion of the operation.
--------------------------------------------------------------------------------
Etrack Incident = ET770672

Description:
   Storage unit changes could cause policy execution manager (PEM) to receive
   unnecessary event notifications which would impact PEM performance.
--------------------------------------------------------------------------------
Etrack Incident = ET413513

Description:
   For a policy that used wildcards (such as, *) in the file list and enabled
   multiple data streams, NetBackup would not include any dot files (such as,
   .rhosts) at that directory level in the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET769378

Description:
   If the Hot Catalog Backup encountered an image catalog that was corrupted,
   it would stop the hot catalog backup at that point and finish immediately
   with an error code of 67 (file list read failed).
   
   Now it continues past the corrupted image catalog, and backs up the rest of
   the catalog, and finishes with a partial success status of 1.

Workaround:
   To avoid this issue, fix the corruption in the image catalog, or take a
   cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET767294

Description:
   A new entry "MediaBlockSize" is provided in the nbsl.xml file to configure
   fetch size.  This option is useful for congested TCP/IP networks, where the
   default fetch size of 1000 could fail.
--------------------------------------------------------------------------------
Etrack Incident = ET593547

Description:
   The media_deassign_notify notification script, added to the
   <install_path>/netbackup/bin/goodies directory, will execute if it is
   moved into the <install_path>/netbackup/bin directory.  This script is
   executed every time a media is deassigned.
--------------------------------------------------------------------------------
Etrack Incident = ET774846 ET805115 ET818780 ET831242

Description:
   On large file systems with a large number of images, disk staging would not
   free space fast enough to prevent concurrent backups from failing with 129
   errors.

Additional Notes:
   When a backup to a disk storage unit with staging completes, the percent
   used is compared with the high water mark. If the percent used is equal to
   or greater than the high water mark, a bpdm process will be invoked which
   will remove staged images until the low water mark is reached.
   
   To disable this behavior, create the "IGNORE_HIGH_WATER_MARK" touch file in
   the netbackup/bin directory.
--------------------------------------------------------------------------------
Etrack Incident = ET768910

Description:
   update_clients did not recognize the invalid parameter Install_java.  A
   change to the parameter check has been made to catch this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET645067

Description:
   Sun Cluster agent was reporting the following error when failing over the
   resource group.
      “Failed to retrieve the resource type handle: invalid resource type”
--------------------------------------------------------------------------------
Etrack Incident = ET770159

Description:
   To determine the NetBackup server version, bpexpdate, bpdbm, and some other
   components were using bpcd protocol. If one of the servers is down, it may
   take a long time. In addition, the error handling of the failure was not
   appropriate.
   
   A change has been made to fetch the NetBackup server version from the EMM
   database. This is a fast and more reliable way to determine NetBackup
   server versions.
--------------------------------------------------------------------------------
Etrack Incident = ET770650

Description:
   Changes have been made to correct various compile warnings.
--------------------------------------------------------------------------------
Etrack Incident = ET776562

Description:
   The Problem’s Report shows, "SO_REUSEADDR failed, errno = 0, No error".
--------------------------------------------------------------------------------
Etrack Incident = ET772419

Description:
   During normal termination using the bpdown command (on Windows), PEM's
   JobScheduler::terminate was not called.  This casued PEM to hang while
   waiting for the Connection Factory to be closed and eventually lead to a
   crash.  
--------------------------------------------------------------------------------
Etrack Incident = ET777370

Description:
   "bpstsinfo -UPDATE" no longer hangs on an exit.
--------------------------------------------------------------------------------
Etrack Incident = ET699903

Description:
   Tapes that were not full were sometimes mistakenly ejected from standalone
   drives after jobs completed.  
--------------------------------------------------------------------------------
Etrack Incident = ET773419

Description:
   Changes were added to fix warning errors when compiling jobmgr on
   HP-UX systems.
--------------------------------------------------------------------------------
Etrack Incident = ET772287

Description:
   Changes were made to fix issues where synth backups were failing when going
   to a File system, export-enabled, NearStore storage unit because they did
   not "admit" to being TIR enabled even if the policy they are run out of is
   TIR enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET768443

Description:
   The user was able to change the pool type of the default none, NetBackup,
   DataStore, and Catalog backup pools.  This fixes the problem from the
   server side.
--------------------------------------------------------------------------------
Etrack Incident = ET776697

Description:
   Duplication failed if VERBOSE=5 was set and the destination storage unit
   was a tape.
   
   This problem was introduced by a previous fix in this pack and does not
   exist in any released software.

Workaround:
   To avoid this issue, do not set VERBOSE equal to 5.
--------------------------------------------------------------------------------
Etrack Incident = ET770273

Description:
   Wildcard matching in image keywords does not work.
--------------------------------------------------------------------------------
Etrack Incident = ET777616

Description:
   Failing synthetic backups would unintentionally perform a catalog cleanup
   instead of deleting the single failed backup image.
   
--------------------------------------------------------------------------------
Etrack Incident = ET771311

Description:
   Changes were made to resolve several small memory leaks that were possible
   in infrequently encountered scenarios.
--------------------------------------------------------------------------------
Etrack Incident = ET773473

Description:
   Added support for Linux, Red Hat 4, and SuSE 9, on Power PC from IBM.
   Normal UNIX client support for these client types is also covered with
   this maintenance pack.
   
   File system support is limited to EXT2, EXT3, ReiserFS on SuSE SLES 9, and
   NFS.  Files that are greater than 2 Gigabytes are supported.  Local user
   interfaces are available through the command line or the menu interface
   (using the bp command). Remote access is the same as all other UNIX
   clients.
   
   For the client binaries to be installed from the UNIX patch you must first
   create the following directories:
   
   /usr/openv/netbackup/client/Linux/IBMpSeriesRedHat2.6
   /usr/openv/netbackup/client/Linux/IBMpSeriesSuSE2.6
   
   The binaries for the encryption licensed feature are available through
   the encryption patch.  For the Encryption binaries to be installed from
   the UNIX encryption patch you must first create the following directories:
   
   /usr/openv/netbackup/crypt/Linux/IBMpSeriesRedHat2.6
   /usr/openv/netbackup/crypt/Linux/IBMpSeriesSuSE2.6
   
   For additional information about encryption, refer to the NetBackup
   Encryption readme.
--------------------------------------------------------------------------------
Etrack Incident = ET579398 ET775062

Description:
   Synthetic Backup no longer fails when a component image spans tape volumes.
--------------------------------------------------------------------------------
Etrack Incident = ET774704

Description:
   Restores of backups for clients that had Flashbackup policies (either alone
   or in combination with other policy types) were slow to become active and
   mount tapes.
--------------------------------------------------------------------------------
Etrack Incident = ET770151

Description:
   The “bpexpdate –recalculate –backupid –ret” command correctly changed the
   expiry date of an image, but not the image retention level.
--------------------------------------------------------------------------------
Etrack Incident = ET772390

Description:
   In some scenarios, the NetBackup Resource Broker (NBRB) was orphaning
   resources while waiting for tape span and then deallocating those
   resources. This caused an erroneous job termination.
--------------------------------------------------------------------------------
Etrack Incident = ET775684

Description:
   Vaulting (bpduplicate) failed with the second image in a batch job with a
   “resource request failed” message.

Workaround:
   This problem may occur if images are on media with an ID of less than six
   characters.  To avoid this issue, use six-character media ID’s.
--------------------------------------------------------------------------------
Etrack Incident = ET775681

Description:
   Increased the mount timeout for TLH drives to accommodate drive cleaning by
   the library between mounts.
--------------------------------------------------------------------------------
Etrack Incident = ET775677

Description:
   Changes have been made to enable NetBackup to control TLH robotics with up
   to 512 drives.
--------------------------------------------------------------------------------
Etrack Incident = ET775429

Description:
   Changes were made to correct error message for invalid media type mapping.
--------------------------------------------------------------------------------
Etrack Incident = ET775427

Description:
   Changes were added to correct syslog messages to print appropriate
   information.
--------------------------------------------------------------------------------
Etrack Incident = ET775428

Description:
   Resolved an issue with the TLD inventory with the empty_map option set by
   correcting the algorithm so that if only the last slot is open, it can
   still be used without failing.
--------------------------------------------------------------------------------
Etrack Incident = ET768449

Description:
   Resolved an issue that would not allow you to delete a machine of
   APP_CLUSTER type.
--------------------------------------------------------------------------------
Etrack Incident = ET776667

Description:
   Changes were made to correct various compiler warnings.
--------------------------------------------------------------------------------
Etrack Incident = ET778780

Description:
   A bad configuration could lead to thousands of monitor-provider allocations
   in the database. The resource broker (RB), on startup, may consume a lot of
   memory reading these database entries and may even dump core. Now the RB
   removes all of the monitor-provider allocations at startup.
--------------------------------------------------------------------------------
Etrack Incident = ET775425

Description:
   When downing a drive using the vmoprcmd -downbyname or vmoprcmd –down
   comands, the drive's designated scan path was sometimes set back to "UP".
--------------------------------------------------------------------------------
Etrack Incident = ET775435

Description:
   When a pre-NetBackup 6.0 media server was unassigned a drive that was
   Scanned by a NetBackup 6.0 media server, it was not clearing the
   RVSN/EVSN and Ready fields.
--------------------------------------------------------------------------------
Etrack Incident = ET780083

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

Description:
   Changed the Policy Execution Manager to call the Job Manager restartJob
   Interface which looks at restartSelection setting instead of
   resourceSelection.  When a parent job is resumed, it frees the resource.
   Job Manager failed the job if it looked at the resourceSelection (that is
   set to inherit parent resource) but would work if it used restartSelection
   (that is, set to use standard resource).
--------------------------------------------------------------------------------
Etrack Incident = ET777064

Description:
   The naming convention used by the Sun Solaris Leadville HBA driver has
   changed.
--------------------------------------------------------------------------------
Etrack Incident = ET782623

Description:
   Added changes to correctan uninitialized local variable and remove an
   unused local variable.
--------------------------------------------------------------------------------
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

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 tat were not initialized.
--------------------------------------------------------------------------------
Etrack Incident = ET784803 ET784808 ET784805 ET784804 ET784810 ET792742 ET784809 ET802855

Description:
   Buffer overflow areas have been identified and corrected in daemons running
   on Veritas NetBackup master, media, and client servers.   Successful access
   to a vulnerable Veritas NetBackup server and the ability to successfully
   execute arbitrary code could potentially result in unauthorized access with
   elevated privilege on a system.
--------------------------------------------------------------------------------
Etrack Incident = ET775510

Description:
   A restore of a large backup image would potentially fail if a large number
   of data buffers (for example, 1024) was configured.  The number of data
   buffers is configured on UNIX systems in
   /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS, and for Windows
   systems in <install_path>\NetBackup\db\config\NUMBER_DATA_BUFFERS.  

Workaround:
   To avoid this problem, do one of the following:
   
   - Set the number of data buffers to a smaller value (For example, 128).
   
   - Create the following file:
   
       UNIX: /usr/openv/netbackup/db/config/MIN_RESTORE_SKIP
       Windows: <install_path>\NetBackup\db\config\MIN_RESTORE_SKIP
   
       Then enter a number greater than the following:
       (size_data_buffers) * (number_data_buffers) / 512
--------------------------------------------------------------------------------
Etrack Incident = ET775517

Description:
   Bpbrm would occasionally terminate abnormally without core on a very busy
   media server, which would cause the backup job to hang.  This could only
   happen on UNIX media servers, and not on Windows media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET775513

Description:
   Individual file restores would potentially fail in the following
   circumstance:
   
   - The original backup was done using Inline Copy, and at least one of the
        copies was disk, and the backup was multiplexed.
   - The backup had multiple fragments for the disk copy.
   - A duplicate from a disk copy to tape was performed, and the source and
        destination storage units are on the same machine.
   - The restore is from the duplicated disk copy.

Workaround:
   To avoid this issue, create the following file on the master server:
   
   For UNIX Systems:
   /usr/openv/netbackup/NOSHMDUP
   
   For Windows Systems:
   
   <installed_path>\NetBackup\NOSHMDUP
--------------------------------------------------------------------------------
Etrack Incident = ET771553

Description:
   The NBPEM uses write locks instead of read/write locks to enhance
   performance.
--------------------------------------------------------------------------------
Etrack Incident = ET770349

Description:
   bprd and nbpem now exchange user backup startup parameters through the
   use of a file named with a GUID instead of a process PID, eliminating the
   possibility that the same filename will be used twice.
--------------------------------------------------------------------------------
Etrack Incident = ET774791

Description:
   A missing log message was added for when FFREADtries are exceeded.
--------------------------------------------------------------------------------
Etrack Incident = ET775512

Description:
   Verify, duplication, or import operations are not be 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

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

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

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

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

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

Description:
   The bpbackup command, when used with the -L and -i options, did not
   provide useful information in the progress log.
--------------------------------------------------------------------------------
Etrack Incident = ET790023

Description:
   You can now backup NetBackup media servers using Storage Area Network (SAN)
   media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET777633

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

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

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

Description:
   A problem existed in the "Media and Device Management > Media" section of
   the Windows Administration Console and the Java user Interface.  Whenever a
   tape holds more than 2 Terabytes of data on it, the Kbytes number in the
   "Kilobytes" column displays as a -ve number.
--------------------------------------------------------------------------------
Etrack Incident = ET789535

Description:
   When the default robotic volume group is selected in "Change Vault" dialog,
   it is not selecting the correct volume group.
--------------------------------------------------------------------------------
Etrack Incident = ET785497

Description:
   Removed the new ORB created during a ServiceManager collection process.
--------------------------------------------------------------------------------
Etrack Incident = ET791064

Description:
   Using long hostnames for NDMP hosts no longer results in the credentials
   being added incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET787049

Description:
   The install was starting the ASA database service on non-EMM media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET787586 ET786594 ET790483

Description:
   The NetBackup service layer (NBSL) would crash when connected from a
   user interface or 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://library.veritas.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

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

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

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

Description:
   The NetBackup Resource Broker (NBRB), under heavily loaded conditions with
   many media servers, would take about 30 seconds to give resources to the
   job.
   
   To fix the problem the following improvements have been made:
   
   -  Improved drive cache in RB (RB no longer links with emmlib).
   -  If the maxmpx in the request is 1, do not try to join it to any group.
   -  Delete all MonitorProvider allocations using a single SQL statement.
   -  Prioritize the requests based on the birth time too.
   -  Some miscellaneous improvements.
--------------------------------------------------------------------------------
Etrack Incident = ET644674 ET427279

Description:
   The cluster_config script was failing when a fully qualified domain name
   was used as the virtual name.  In addition, deleting and then re-adding
   robot daemons using cluster_config -r caused the cluster monitoring to
   fail.
--------------------------------------------------------------------------------
Etrack Incident = ET777893

Description:
   Changed the Policy Execution Manager to not exit the application
   if the restart request could not be satisfied because of a malloc failure.
--------------------------------------------------------------------------------
Etrack Incident = ET792609

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

Description:
   The hot catalog backup feature did not work with images that had been
   archived using the catalog archiving feature.  Prior to this fix, if the
   catalog archiving feature had been used to archive images, the backup job
   generated from a hot catalog backup policy would fail with a status 67
   on a UNIX or Linux master server and with a status 1 (partially
   successful) on a Windows master server.
--------------------------------------------------------------------------------
Etrack Incident = ET791570

Description:
   Added a call to nbproxyreq in a NetBackup script in case the nbproxy
   commands are not shutting down gracefully.
--------------------------------------------------------------------------------
Etrack Incident = ET770171

Description:
   Changes were made to improve performance on multiple data streams by not
   generating streams again if stream discovery did not change the stream
   content.
--------------------------------------------------------------------------------
Etrack Incident = ET597353

Description:
   Changes have been made to limit support of VxFS File Change Log to FCLv3
   during incremental backups.
--------------------------------------------------------------------------------
Etrack Incident = ET785820

Description:
   bpclntcmd no longer fails on HP-UX systems with the following error.
   
   "_main() not called"  
--------------------------------------------------------------------------------
Etrack Incident = ET789170

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.  
--------------------------------------------------------------------------------
Etrack Incident = ET795443

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

Description:
   bptm would erroneously log an error, error code 95, during image
   expiration.
--------------------------------------------------------------------------------
Etrack Incident = ET795523

Description:
   bptm would erroneously log an error, 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

Description:
   NetBackup communication between components that were separated by a
   firewall did not work.  For instance, when a master server was behind the
   firewall and a media server was outside the firewall, all communication
   from the master server had an internal host address that was not accessible
   from outside systems.
   
   This is the same when clients and other services are in question.  

Additional Notes:
   To activate NAT address replacement, systems outside of the firewall should
   have the FIREWALL_IN parameter specified in their bp.conf/registry.
   
   Format:  FIREWALL_IN=hostname1,nat_address1|hostname2,nat_address2|...
   
   Where: <hostname> is the name of the host system that needs to be accessed
   and <nat_address> is the actual NAT address for the firewall to do
   forwarding.
--------------------------------------------------------------------------------
Etrack Incident = ET795448

Description:
   Changes were made to not send Storage Unit Events when only updating
   capacity information.  Too many of these events were being generated and
   impacting performance.
--------------------------------------------------------------------------------
Etrack Incident = ET793447

Description:
   Changes have been made to reduce the bpdbm CPU consumption by doing fewer
   things on exit of child bpdbm processes.
--------------------------------------------------------------------------------
Etrack Incident = ET795436 ET796505 ET801859

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

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

Description:
   The NetBackup Java user interface no longer displays “square box”
   characters in the Media “Side” column for the second AcsLsm.
--------------------------------------------------------------------------------
Etrack Incident = ET796480

Description:
   Backup jobs would occasionally fail with error status 26 (client/server
   handshaking failed).  The bpbrm log would show the following:
   
   08:34:12.336 [2764.3504] <2> bpbrm multiplexed_backup: calling
   read_media_msg for media manager PID.
   08:34:42.618 [2764.3504] <2> bpbrm read_media_msg: media manager pid 0 is
   not alive
   08:34:42.618 [2764.3504] <16> bpbrm multiplexed_backup: cannot get PID of
   media manager
   08:34:42.915 [2764.3504] <2> bpbrm Exit: ERROR 26 sent to parent process
--------------------------------------------------------------------------------
Etrack Incident = ET796392

Description:
   The NBJM threads block while calling the proxy for BPDBM requests.
--------------------------------------------------------------------------------
Etrack Incident = ET794326

Description:
   Changed a strncpy to a V_strlcpy to prevent the string not being null
   terminated.
--------------------------------------------------------------------------------
Etrack Incident = ET797363

Description:
   Increased the connection cache size for nbjm to reduce number of
   Communication retries by bptm.
--------------------------------------------------------------------------------
Etrack Incident = ET784514

Description:
   Synthetic backups no longer fail with the error message, "termination
   requested by bpcoord(665)".
--------------------------------------------------------------------------------
Etrack Incident = ET797083

Description:
   The parent job no longer core dumps upon exiting an application when trying
   to log a VxUL message after an orb shutdown.  The parent job was modified
   to remove all VxUL messages that are being logged after an orb shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET797388 ET798930

Description:
   Multiple backups for the same client and policy that were started at the
   same time created a situation where an image was being validated at
   the same time the previous backup for the client and policy was being
   validated.
   
   One of the final steps in image validation is to go back through previous
   backups for the client and policy and update the TIR meta data to allow TIR
   data to be pruned.  However, since the previous backup for the client and
   policy was still being validated, it could not be updated and the following
   log message (and error report entry) were generated:
   
   17:27:33.723 [11812] <16> get_last_backup_lock: Bad image header:
   many-non-multi-stream_1158100028_FULL, error: file read failed (13)
   
   bpdbm was exiting with a normal status, so the backup was successful.

Workaround:
   To avoid this issue, wait before starting backups for the same client and
   policy.

Additional Notes:
   With this change, any failures in updating tir meta data in image
   Validation will result in a conditional success for the backup job.
--------------------------------------------------------------------------------
Etrack Incident = ET797999 ET797370

Description:
   Changes were made to clarify error message that may have been unclear.
   This involved no functional change.
--------------------------------------------------------------------------------
Etrack Incident = ET796292

Description:
   Pending messages were not displayed in the Activity Monitor for spanned
   backups.
--------------------------------------------------------------------------------
Etrack Incident = ET798366

Description:
   EMM now logs a more accurate disk space message when space is below
   the threshold.
--------------------------------------------------------------------------------
Etrack Incident = ET796332

Description:
   Changes were made to bpbrmds to eliminate core dumps when performing a
   manual or scheduled relocation of a DSSU on media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET800221

Description:
   Parent images have no associated .f file, and as a result have a file count
   of zero.  When images with a zero file count are validated, a function to
   tally the number of files is called.  This function should not be called
   when there is no associated .f file.  The logic to determine whether there
   is an associated .f file has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET800184

Description:
   Resolved an issue that caused, "Frequent status code 805 - invalid jobid,"
   errors to occur.

Additional Notes:
   This condition occurred when children jobs were retired due to exceeding
   the time allowed in incomplete state.  The parent job being resumed either
   manually or automatically resulted in an 805 error due to the job having
   a jobid of -1.  This fix prevents the child from starting since it is not
   resumable.  The new result will correctly be a 200 error if no children
   can be started.  An indication of this will be written to the pem log.
--------------------------------------------------------------------------------
Etrack Incident = ET801046

Description:
   The job monitor would cancel the catalog backup job after 20 minutes.
   The nbgenjob ping interval to the job manager was changed to three minutes
   to keep the job from being cancelled.
--------------------------------------------------------------------------------
Etrack Incident = ET799129

Description:
   The synthetic backups were not scheduling correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET800016

Description:
   The nbpem would core dump because getECmsgl was not thread safe.
--------------------------------------------------------------------------------
Etrack Incident = ET802987

Description:
   A Hot Catalog Backup of a large catalog with a large number of files can
   sometimes end up in a deadlock between the NetBackup UNIX agent bpbkar and
   the NetBackup media server process bpbrm.
--------------------------------------------------------------------------------
Etrack Incident = ET803630

Description:
   Changes were added to correct an issue that casued the resource broker (RB)
   to hang at startup.
--------------------------------------------------------------------------------
Etrack Incident = ET799867

Description:
   The Policy Execution Manager inefficiently processes policy change
   notifications when performing housekeeping tasks which may slow job
   submission.  This inefficiency can occur from the user interface if the
   user selects all policies and then activates or deactivates the list of
   policies.  

Workaround:
   To avoid this issue, do not generate a large number of policy changes all
   at once before a window opens. Instead, amortize them over time to limit
   the impact on the Policy Execution Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET800184

Description:
   The jobid of a child checkpoint restart job would be set to -1 when
   a 196 status occurred.  The result was an 805 error if the parent was
   resumed because the jobid -1 gets resumed.
--------------------------------------------------------------------------------
Etrack Incident = ET804921

Description:
   The calendar schedule would not run when the available window spanned
   across the specified day.
--------------------------------------------------------------------------------
Etrack Incident = ET805146

Description:
   The NetBackup Job Manager (NBJM) was checking the connection to the proxy
   before reading the global configuration to obtain attributes such as,
   max vault jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET805407

Description:
   The policy monitor would show as being down in Initial Data Load status
   page.
--------------------------------------------------------------------------------
Etrack Incident = ET800841

Description:
   Sometimes manual jobs would not start through either the user interface
   or the command line. This would happen if PEM lost connection with NBJM.
--------------------------------------------------------------------------------
Etrack Incident = ET804850

Description:
   An issue that caused catalog backups to hang on a retry have been fixed.
--------------------------------------------------------------------------------
Etrack Incident = ET805807

Description:
   Cancelling an incomplete job that failed with a 196 error, then restarting
   nbpem would cause the job to show as done in the Activity Monitor.
   However, if the job is set to done in the Activity Monitor, a retry or
   resume of the active job will not show up in the Activity Monitor.

Workaround:
   If there are checkpoint restart jobs that show as complete but have a
   status of 196 and pem needs to be restarted, remove the pempersist file
   before pem is started again.
--------------------------------------------------------------------------------
Etrack Incident = ET806779

Description:
   A timer was scheduled for a backup job even when throttling was not
   configured.
--------------------------------------------------------------------------------
Etrack Incident = ET806051

Description:
   NetBackup Maintenance Pack upgrades were failing on the active node of an
   HP ServiceGuard cluster, due to the package monitor offlining the package
   even with switching disabled.  The capability to freeze the cluster agent
   monitoring by touching a file (/usr/openv/netbackup/bin/cluster/frozen)
   was added.
--------------------------------------------------------------------------------
Etrack Incident = ET806888

Description:
   The bpinet services on media servers were being reported as an
   "unknown" status in NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET806990

Description:
   Service credentials had expired and because of that, the NOM client was
   unable to log into the NOM server.

Workaround:
   To avoid this issue, you can renew the credential using the command line
   interface provided by vssat.
--------------------------------------------------------------------------------
Etrack Incident = ET803649

Description:
   Jobs would queue indefinitely, following a media server reset while
   pending resource requests were outtanding.

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

Description:
   The service called NetBackup Volume Manager (vmd) would stop unexpectedly
   because of a network problem.
--------------------------------------------------------------------------------
Etrack Incident = ET808314

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

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

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

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

Description:
   Changes were made to correct an issue with adding an NDMP robot.
--------------------------------------------------------------------------------
Etrack Incident = ET818227

Description:
   The text for status code 125 has been changed to reflect the use of this
   status code in preventing some operations when an online catalog backup is
   in progress.
--------------------------------------------------------------------------------
Etrack Incident = ET774674

Description:
   When a bad drive or bad tape is mounted and the mount fails, MDS (EMM) 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

Description:
   A job could be canceled out of a window when the window was still open.
--------------------------------------------------------------------------------
Etrack Incident = ET818434

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

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

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

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

Description:
   Empty paths on file entries were causing backups to fail with a status 1
   and an entry in the bpdbm log similar to the following:
   
   11:29:18.781 [5216.3708] <32> add_files: File:
   v:\src\common\libcatalog\nbe_string.h Line: 434: null pointerFunction:
   utf8_strlen
   
   With this patch, the backup will still fail if a null or empty path is
   detected, but an entry similar to the following will appear in the
   NetBackup error report:
   
   A null or empty path was provided for policy1_1160000001_FULL at entry 2501

Additional Notes:
   A null or empty path string is usually caused by a failure in the client
   device.  Check for patches from the device manufacturer to address the
   root cause.
   
   There is a known issue with NetApp filers configured for Chinese locales
   that produces this problem.  NetApp has a file history patch that addresses
   the issue:
   
   NetApp Bug ID: 195779    
   Title: NDMP DMA shows no file names after a backup with 7.0.x    
   
   Description:
   
   Empty NFS pathnames will be returned in the file history for non-ASCII  
   filenames if the root volume's language is not set to C/POSIX or    
   the language setting of the volume being backed up differs from the  
   root volume's language setting.  
   
   Workaround:
   
   Make sure the language setting of the root volume matches that of  
   the volume being backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET830269

Description:
   A change has been made that ensures that after you have downed a drive on
   the scan host, it will not come back up.
--------------------------------------------------------------------------------
Etrack Incident = ET805843

Description:
   bpdbm uses the notification service to notify the PEM and JM components
   when policies are updated.  When the call to the notification service
   failed, the bpdbm child process would terminate with little information on
   the cause of the failure.  With this patch, the cause of the failed call to
   the notification service will be logged, and an entry will be made in the
   NetBackup error report for the termination of the child bpdbm process.
--------------------------------------------------------------------------------
Etrack Incident = ET797083

Description:
   A Parent job (nbgenjob) would core dump when an exception, thrown by
   ORB, was not handled.  This problem has been fixed in this pack.
--------------------------------------------------------------------------------
Etrack Incident = ET776675

Description:
   The pem was referencing a function that was using strtok(), which was not
   thread-safe on UNIX platforms. This change only effected UNIX platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET831186

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

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

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

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

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

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 = 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 pem persist 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

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

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

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

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

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