NetBackup LiveUpdate 6.5.4 README                                   May 11, 2009
NBLU_6.5.4 UNIX
================================================================================
This README describes the fixes and updates contained within the Veritas
NetBackup 6.5.4 Release Update LiveUpdate Packages.
================================================================================


====================
RELEASE DEPENDENCIES
====================    

     --  You can use a single LiveUpdate server for NetBackup to deploy updates
         for UNIX and Windows.  To create a LiveUpdate server for NetBackup
         UNIX 6.5.4, you MUST download and extract *ALL* of the following
         three (3) segments of the LiveUpdate server for NetBackup UNIX
         bundle.  
       
          NBLU_6.5.4.UNIX_1of3.zip
          NBLU_6.5.4.UNIX_2of3.zip
          NBLU_6.5.4.UNIX_3of3.zip

    --   You can use the same LiveUpdate server to deploy NetBackup updates for
         Windows.  To accomplish this, download and extract the following
         bundles into the same location as the three (3) segments of the
         NetBackup UNIX bundle.
 
          NBLU_6.5.4.WINia64.zip
          NBLU_6.5.4.WINx64.zip
          NBLU_6.5.4.WINx86.zip

   --    In order to update NetBackup UNIX hosts, be sure that /tmp on the
         hosts to be updated meet the minimum available space requirements of
         2.0GB for NetBackup Servers and 1.0GB for NetBackup clients.  See the
         Known Issues section below for more information.



I.    LIVEUPDATE FOR NETBACKUP
        Creating a LiveUpdate Server for NetBackup
        NetBackup LiveUpdate Known Issues
        Using LiveUpdate to deploy NetBackup Release Update 6.5.4
        Uninstalling NetBackup Release Update 6.5.4
II.   NEW NETBACKUP FEATURES AND PLATFORM PROLIFERATIONS
        Platform Proliferations
        New Features and Enhancements
        End-of-Life Notifications
III.  NETBACKUP KNOWN ISSUES
IV.   CURRENT RELEASE UPDATE INDEX  
V.    RELEASE UPDATE CONTENT
        Conventions
        Current Release Update
           NBLU_6.5.4.UNIX
        Release Update History
           NBLU_6.5.3.UNIX
           NBLU_6.5.2.UNIX
           NBLU_6.5.1.UNIX


===========================
I. LIVEUPDATE FOR NETBACKUP
===========================
Creating a LiveUpdate Server for NetBackup:
-------------------------------------------
A LiveUpdate Server for NetBackup does not require any additional software, but
is simply an HTTP server or disk share that has been populated with the contents
of this LiveUpdate Server for NetBackup bundle.  

1. Create a LiveUpdate Server for NetBackup.
  a.  Configure either an HTTP server or a shared disk that can be accessed by
      all NetBackup hosts that you plan to update.  Refer to the "NetBackup
      LiveUpdate" chapter of the NetBackup 6.5 Installation Guide for UNIX and
      Linux.
 
      The LiveUpdate Server for NetBackup can be a Windows or UNIX host.  
      NetBackup LiveUpdate policies can be used to update NetBackup on either
      Windows or UNIX machines.

  b.  Download the following files into the root directory of the NetBackup
      LiveUpdate server, which is either the HTTP root directory or the shared
      disk directory.
      -  NBLU_6.5.4.UNIX_1of3_<6 digit number>.zip
      -  NBLU_6.5.4.UNIX_2of3_<6 digit number>.zip
      -  NBLU_6.5.4.UNIX_3of3_<6 digit number>.zip
      where <6 digit number> is an internal tracking identifier

      **NOTE: Without both segments, LiveUpdate for NetBackup UNIX will not
      be functional.


2. Extract the following files into the root directory of the NetBackup
  LiveUpdate server, which is either the HTTP root directory or the shared
  disk directory.
      -  NBLU_6.5.4.UNIX_1of3_<6 digit number>.zip
      -  NBLU_6.5.4.UNIX_2of3_<6 digit number>.zip
      -  NBLU_6.5.4.UNIX_3of3_<6 digit number>.zip
 
  a. To extract the bundles on a UNIX system use the following command.

     unzip NBLU_6.5.4.UNIX_1of3_<6 digit number>.zip
     unzip NBLU_6.5.4.UNIX_2of3_<6 digit number>.zip
     unzip NBLU_6.5.4.UNIX_3of3_<6 digit number>.zip

  b. To extract the bundles on a Windows system use an appropriate unzip
  utility.

  This creates a large number of files that comprise a LiveUpdate Server for
  NetBackup. Do not rename, move, or delete any files that were extracted.



NetBackup LiveUpdate Known Issues:
----------------------------------
The following issues pertain specifically to the LiveUpdate server for NetBackup
product.

+  (ET1544083) When creating a Live Update policy, make sure that the policy
  name is unique and that it is not the same as any other internal or external
  policy name.  The Live Update policy fails if its name is the same as any
  other policy name.


+  In order to free up disk space for downloading updates, the JavaLiveUpdate
  agent on UNIX caches downloaded patches, by default, in the /tmp directory.
 
  To reconfigure the directory the JavaLiveUpdate uses for temporary space,
  modify the "workdir" setting in the /usr/openv/netbackup/nblu.conf file.


+  In order to successfully use LiveUpdate to apply NetBackup 6.5.4 on UNIX
  hosts, ensure the total available space in the /tmp directory of the
  NetBackup host to be updated meets the following minimum space requirement:
 
    NetBackup Server - /tmp must have at least 2.0GB of total available space
    NetBackup Client - /tmp must have at least 1.0GB of total available space

 If the /tmp directory of the NetBackup host to be updated cannot meet the
 minimum requirement, you can reconfigure the JavaLiveUpdate agent to use an
 alternate directory.  Edit the "workdir" setting in the  
 /usr/openv/netbackup/nblu.conf file.  For example, to reconfigure a machine
 to use /space/downloads as the working directory, edit nblu.conf to replace
 the line:

     workdir=/tmp

With the following line:

     workdir=/space/downloads

 Failure to meet the minimal space requirement can result in your NetBackup
 Liveupdate policy failing with an exit status of 77.  The
 /opt/Symantec/LiveUpdate/liveupdt.log will indicate exit status "246", with
 a message similar to the following:

 "Disk space check for <pkgname> failed. Requested free space was XXX (in MB)
 The Java LiveUpdate session did not complete successfully.
 Return code = 246"


 Additionally, the /usr/openv/netbackup/logs/nbliveup/ logs will indicate
 status "118", with a message similar to the following:

 "Error executing /usr/openv/java/jre/bin/java -cp
 /opt/Symantec/LiveUpdate/jlu.jar com.symantec.liveupdate.LiveUpdate -c
 /usr/openv/netbackup/nblu.conf, status = 118"


+  Page 118 and 119 of the NetBackup 6.5 Installation Guide for Windows
  indicates the use of a universal naming convention path (UNC) as one of the
  acceptable methods of using a Windows machine as a LiveUpdate server for
  NetBackup. An example of a UNC path on Windows is "\\server\shared_dir\".

  Currently, when a client is configured to use a UNC for the LiveUpdate
  server, and the update is launched using the policy execution on the
  LiveUpdate server, the nbliveup process on the client starts and then halts
  shortly after starting.  

  This is the result of system permissions and the local SYSTEM account's
  inability to resolve network drives. Refer to the following TechNote on the
  Symantec Support Web Site for more information.

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


Using LiveUpdate to deploy NetBackup Release Update 6.5.4:
---------------------------------------------------------
To use the LiveUpdate Server for NetBackup, you must first ensure that all
NetBackup hosts that you intend to update have the NetBackup LiveUpdate Agent
installed, and that they are configured with the location and protocol that
points to your LiveUpdate Server for NetBackup.

To install NetBackup LiveUpdate Agent on Windows
1.  The agent is automatically installed on Windows.
2.  The agent needs to be configured for protocol and location of the
   LiveUpdate Server for NetBackup.

To install NetBackup LiveUpdate Agent on UNIX
1.  From the NetBackup 6.5 Options CD, select "LiveUpdate Agent".
2.  When prompted for protocol and location, enter the protocol and location
   used by the LiveUpdate Server for NetBackup that has been populated with
   the contents of these bundles.

Refer the NetBackup 6.5 Installation Guide for UNIX and Linux for instructions
on installing the NetBackup LiveUpdate agent, and creating and executing a
NetBackup LiveUpdate policy.  

On UNIX, ensure that each host to be updated meets the minimum space
requirements in /tmp, as specified in the Known Issues section of this README.

NOTE: The updates contained in the following files are not meant to be
installed manually, and must only be used by a NetBackup LiveUpdate policy.

   -  NBLU_6.5.4.UNIX_1of3_<6 digit number>.zip
   -  NBLU_6.5.4.UNIX_2of3_<6 digit number>.zip
   -  NBLU_6.5.4.UNIX_2of3_<6 digit number>.zip
   -  NBLU_6.5.4.WINia64_<6 digit number>.zip
   -  NBLU_6.5.4.WINx64_<6 digit number>.zip
   -  NBLU_6.5.4.WINx86_<6 digit number>.zip


Uninstalling NetBackup Release Update 6.5.4:
--------------------------------------------
LiveUpdate for NetBackup does not provide a NetBackup policy method for
uninstalling Release Updates.  You must follow this procedure locally on each
NetBackup host that you want to uninstall.

   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 Release Update name for ${PACK} in the following
       command:

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

   3)Run the un-install script:

         ./NB_update.uninstall

   4)Verify that the Release Update uninstalled successfully by checking
       /usr/openv/pack/pack.history.

   5)If necessary, restart the NetBackup and Media Manager daemons:
       /usr/openv/netbackup/bin/bp.start_all




=======================================================
II.  NEW NETBACKUP FEATURES AND PLATFORM PROLIFERATIONS
=======================================================
This section contains subsections that describes the new UNIX and Windows
features and platform proliferations that are being released in NetBackup 6.5.4.
In addition, this section contains subsections that describe the features and
proliferations that were released in previous NetBackup Release Updates.  

--------------------------------
Current Platform Proliferations:
--------------------------------
The following is a comprehensive list of the platform proliferations that were
added in this Release Update of NetBackup. (This list contains both UNIX and
Windows proliferations.) For additional information about platform
proliferations, see the following TechNote on the Symantec Support Web site:

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

+  Bare Metal Restore (BMR)
  - BMR Server and Client support for Red Hat 5 x64
  - BMR Server support for HP-UX 11 v2 (11.23) IA64
  - Support for BMR was added for Windows 2003 x64 client
  - Solaris 10 x64 server support for BMR
  - BMR Master Server support for Windows 2008 x64
  - BMR Supports SAN-Boot for Windows 2003 32- and 64-bit clients
  - BMR Does not support BMR Client/Boot server on SPARC-Sun4V

+  Clients and agents
  - Database agent support for Informix 10.0, 11.1, and 11.5 on AIX 6.1
  - Database Agent support for SQL Server on Windows 2003 IA64
  - Database Agent support for Sybase ASE 15.0 on Windows 2008 x86
  - Database Agent support for XBSA on Windows 2008 IA64  
  - Sybase 12.5 and 15.0 agent support for Red Hat 4.0 and 5.0 x64
  - FT Media Server support on Red Hat 5.0 and 5.2 Update 2
  - SAN Client support on Windows 2003 IA64
  - Lotus Notes 8.5 on Windows Server 2008 (WS2008) x64
  - Oracle 10gR2 and  11g on Red Hat 5.0 IBM pSeries platform
  - SAP on MaxDB 7.7.04.30 databases on Windows 2008 x64
  - SAP on Oracle 10G R2, BRTools 7.10, on Windows 2008 x64
  - SharePoint 2007 with SQL 2008
  - SharePoint agent support for an SQL server cluster in a VCS environment
  - File System Snapshot Client (SNC) support on AIX 6.1
  - Enterprise Vault agent support for Enterprise Vault 7.5 on Windows 2003 x86
  - Enterprise Vault agent support for Enterprise Vault 7.5 on Windows 2003 x64
    Note: NetBackup 6.5.4 does not formally support Enterprise Vault 8.x.
          However, the following TechNote on the Symantec Support Web site
          contains additional information on how you can protect Enterprise
          Vault 8.x data using NetBackup 6.5.4.
             http://entsupport.symantec.com/docs/323945

+  NetBackup Operations Manager (NOM)
  - 64-bit NOM Support
    NOM server support of 64-bit platforms including Solaris SPARC,
    Solaris x64 and Windows 2003 x64

+  Windows 2008
  - MSEO 2008 Support
  - WS2008 core x64 SAN Client
  - WS2008 IA64 SAN Client
  - WS2008 SnapVault
  - WS2008 NDMP support
  - WS2008 database agent Cluster support for VCS x64
  - WS2008 database agent Cluster support for MSCS x64
  - WS2008 x64 Database Agents SNC
  - WS2008 x86 Database Agents SNC
  - Windows 2008 OST Device Qualification
  - Windows 2008 Vault Support (Master & Media) x64
  - Windows 2008 File System x64 SNC
  - Windows 2008 Cluster Support (Master & Media) x64
  - Windows 2008 NBAC/Encryption Support (Master & Media) x64
  - Windows Logo Certification (Certified for Windows 2008 Server 2008)
  - NOM and Java user interface support for Windows 2008

+  Other
  - Introduce AIX 6.1 master and media server support
  - Mid-range Disk arrays integration with Snapshot Client - IBM DS4000 array
  - File System & Oracle Agent SNC support on AIX 6.1 - local disk
  - HP-UX 11.31 path support
  - HP-UX 11iv3 persistent DSFs (Refer to the New Features and Enhancements
       section of this Readme for additional information about this feature.)



----------------------------------------
NetBackup 6.5.3 Platform Proliferations:
----------------------------------------
The following platform proliferations were announced in the NetBackup 6.5.3.

+  Added support for Informix on Red Hat 4, 32 and 64 bit platforms.  Also added
  support for Informix on Red Hat 5, 32 and 64 bit platforms.

+  Added support for SQL 2008 on Windows 2008, 64-bit platforms.

+  Added support VCB 1.5 support for VMWare.


----------------------------------------
NetBackup 6.5.2 Platform Proliferations:
----------------------------------------
The following platform proliferations were announced in the NetBackup 6.5.2.
 
+  The release adds support for the following Windows platforms.
    - NetBackup media server support for Windows 2008 X64
    - NetBackup client support for Windows 2008 X64
    - NetBackup client support for Windows 2008 X86

+  This release adds support for Mac OS X 10.5 Client on Apple and MacIntosh
  platforms.

+  This release adds support for AIX 6.1 Client on IBM platforms.

+  This release adds support for OpenAFS 1.4.4 Client on Solaris 8.

+  This release adds support for HP-UX 11.31 for NetBackup Access Control (NBAC).

+  Support has been added for the following Linux releases for SharedDisk media
  servers:
    - RedHat 4.0 Update 5 on Intel/AMD x86 and x64 (FID 2305)
    - SuSE 9 SP 3 on Intel/AMD x86 and x64 (FID 2306)
  This Linux support includes the following limitations:
    - Device mapper multipath is supported on Red Hat Enterprise Linux 4
      update 5 only.
    - If device mapper multipathing is configured for a LUN, LUN formatting
      using Veritas Storage Foundation is not supported.
    - EMC PowerPath with Veritas Storage Foundation is supported with Storage
      Foundation 5.0mp2rp1 and later.

+  For the new Exchange Instant Recovery feature, when using Veritas Storage
  Foundation for Windows (SFW), the minimum software level is SFW 5.0.

+  The BMR master server is now supported on following two new platforms:
  -  Windows 2003 X64 platform
  -  HP-UX 11.23 PARISC

+  This release provides support the following QLogic HBAs for Fibre Transport
  media servers:
    - QLA2460 and QLA2462 (PCI-X)
    - QLE2460 and QLE2462 (PCI-e)


----------------------------------------
NetBackup 6.5.1 Platform Proliferations:
----------------------------------------
The following platform proliferations were announced in the NetBackup 6.5.1.

+  Microsoft Office SharePoint Server (MOSS) 2007 and Windows SharePoint
  Services (WSS) 3.0 (For more information about this proliferation refer to
  the New Features subsection.)

+  Microsoft Exchange 2007 proliferations that adds mailbox, Snapshot client,
  and VCS support. (For more information about this proliferation refer to
  the New Features subsection.)

+  Added master and media server support for the Red Hat Enterprise
  Linux 5.0 Intel x64 operating system.

+  Added master and media server support for the HP-UX 11i v3 (11.31)
  operating system. (NBAC is not supported on this platform, in this release.)

+  Added NDMP support for HP-UX IA64, Solaris x64, and Windows 2003 x64
  operating systems.

+  Added support for 64-bit SLES 9 SP3 x86_64 as a Fibre Transport Media Server.

+  Added support for 64-bit Red Hat 4 update 5 x86_64 as a Fibre Transport Media
  Server (Note: Red Hat 4 update 3 x86_64 was supported in NetBackup 6.5 GA
  however, it did not support quad core machines).

+  Added Windows 2003 x64 Snapshot client and CLARiiON array support. This
  includes Instant Recovery (IR) for the SQL server on a Windows VSS platform.

+  Added SAN Client support for HP-UX 11.31 PA-RISC and IA-64 operating systems.


--------------------------------------
Current New Features and Enhancements:
--------------------------------------
This section contains a comprehensive list of the new UNIX and Windows features
and enhancements that are being added to NetBackup in this Release Update. For
more information about any new feature contained in this release, refer to the
NetBackup 6.5.4 Documentation Updates document contained in the following
TechNote on the Symantec Support Web site.

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

Some new features mentioned in the list below are documented in a stand-alone
TechNote. In those instances, the TechNote number is supplied in the list.

+  BMR no longer requires a separate license. The license is embedded in the
  NetBackup server license.

+  New Database Agent features and enhancements

  - NetBackup for Enterprise Vault agent
    The new NetBackup for Enterprise Vault agent greatly simplifies data
    protection for the Enterprise Vault servers. This new agent protects all
    of the Enterprise Vault partitions and their associated databases. Because
    the agent leverages snapshot technology, the vault is in a read-only
    backup-mode for the shortest time possible: just long enough to complete
    a snapshot. A backup like this is completely coordinated with Enterprise
    Vault using the agent; no scripts or manipulating registry settings.

    The agent supports disaster recovery of a partition and databases.
    Moreover, it also supports recovery of individual files within a
    partition. Lastly, the agent will automatically discover the various
    servers and components within your Enterprise Vault environment that
    needs protection.

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

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

    In addition to the NetBackup 6.5.4 Enterprise Vault agent, the following
    white papers are available:
    -  For information on how to protect Enterprise Vault 8.0 entities using
       Enterprise Vault Agent 6.5.4 and SQL Agent 6.5.4, you can refer to the
       following white paper on the Symantec Support Web site:
          http://entsupport.symantec.com/docs/323945

    -  For information on the NetBackup Enterprise Vault Migrator, you can
       refer to the following white paper on the Symantec Support Web site:
          http://entsupport.symantec.com/docs/324305

  - NetBackup for Hyper-V agent
    The new NetBackup for Hyper-V agent leverages the same granular
    recovery technology used in the NetBackup for VMware agent. The agent
    protects virtual machines (VM) by backing up the virtual hard drive
    (VHD) images. From the image backup, you can restore the entire VM or
    individual files within the VM. This is done without any VHD staging;
    only the files you select are recovered from tape. Policy setup is
    also simplified by the automatic detection of all VMs within the
    Hyper-V server. Supports Windows 2008 Hyper-V servers.

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

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

  - Granular Recovery for Active Directory
    The new NetBackup for Active Directory agent supports granular recovery
    of most AD objects, including:
    - User Accounts
    - Organizational Units
    - Printers
    - Individual attribute values, like names, addresses, IDs, etc.
    - And others

    This is available for Windows Server 2003 & 2008 AD servers by simply
    including Windows System State in the backup.

+  NetBackup for Microsoft Exchange Server
  The NetBackup for Microsoft Exchange Server Administrator's Guide was updated
  to include all new features that were added since NetBackup 6.5.

  See http://entsupport.symantec.com/docs/320793

  - Instant recovery log truncation option
  - Granular cataloging option

  To use this new feature in 6.5.4, both the media server and the Exchange
  clients need to be at the same NetBackup version. If you upgrade the media
  server to NetBackup 6.5.4, you must also upgrade your clients to version
  NetBackup 6.5.4.

  In addition, this release contains the following configuration changes for
  Exchange cluster environments:
  - To perform Continuous Cluster Replication (CCR) backups of the passive VSS
    writer, you no longer need to set the "Enable Remote Streaming Backup"
    registration key.
  - For Exchange 2007 SP1 or later, you no longer need to configure the
    NetBackup Client Service to run as domain admin.

+  NetBackup for Microsoft SharePoint Server
  - The NetBackup for Microsoft SharePoint Server Administrator's Guide has
    been updated to include all new features that were added since
    NetBackup 6.5 GA.

        See http://entsupport.symantec.com/docs/318354

      - To use the new SharePoint features in 6.5.4, both the media server
        and SharePoint clients need to be at the same NetBackup version. If you
        upgrade the media server to NetBackup 6.5.4, you must also upgrade your
        clients to version 6.5.4.
      - The agent now validates user credentials entered in the NetBackup
        Administration Console.
      - You can now browse for SharePoint objects when you create a backup
        policy.
      - The "AllWebs" directive in the file list selection backs up all Web
        Applications.  This directive is only supported for NetBackup 6.5.4
        and later.

  - Granular restores can be redirected to a file system.

  - Improved SharePoint Granular Recovery
    In NetBackup 6.5.4, the NetBackup for SharePoint agent offers
    additional, more comprehensive granular recovery capabilities, that
    includes the following:
    - Sites and sub-sites
    - Entire lists, like calendars, tasks, links, discussions, and others
    - Any item(s) from a list
    - Any version of a file
    - Recover files to a folder on disk

    Also, several simplifications have been made in configuring a granular
    recovery policy. This new feature is supported for SharePoint 2003 & 2007,
    and WSS 2.0 & 3.0.

+  Enhanced NetBackup clustering support for Snapshot Client
  This release contains enhancements that improve the support of NetBackup
  Snapshot Client Storage Foundation (SF) snapshot methods in a cluster
  environment. Some of the SF snapshot methods that have been improved are:
  VxVM, FlashSnap, VxFS Checkpoint, and VVR.

+  The following new features have been added in the NetBackup for VMware.
  For more information about these new features, refer to the following
  TechNote on the Symantec Support Web site:

     See http://entsupport.symantec.com/docs/318357
   
  - VMware "hotadd" transport mode
    A new VMware feature called the "hotadd" transport mode allows you to run
    the VMware backup proxy server in a virtual machine. The "hotadd" transport
    mode for a backup proxy server in a virtual machine allows the required
    virtual disks to be made dynamically visible to the backup proxy server.
    This feature requires ESX 3.5 Update 2 or later and VCB 1.5. For
    instructions on the hotadd transport mode and on installing the backup
    proxy server in a VMware virtual machine, refer to your VMware
    documentation.
   
    The only configuration requirement in NetBackup is to select "5-hotadd"
    as the transfer type in the Snapshot Client Options dialog in the
    NetBackup policy.

  - VMware physical Raw Device Mapping integration with Snapshot Client
    VMware offers a technology called raw device mapping (RDM). This technology
    allows a virtual machine (VM) to access physical disks directly. One of the
    benefits of RDM is that it enables a VM to use large storage devices such
    as disk arrays. This feature provides a NetBackup Snapshot Client Alternate
    Client backup solution that protects the data on VMware RDM storage.

  - The NetBackup server requires logon credentials to access your VMware
    ESX server or VMware VirtualCenter. This NetBackup 6.5.4 release adds the
    ability to verify that the credentials you have entered are valid for the
    server. The NetBackup Add Virtual Machine Server dialog now contains a
    Validate Credentials check box.

  - Added an option to disable virtual machine quiesce before the snapshot.
    By default, I/O on the virtual machine is quiesced before NetBackup creates
    the snapshot. In rare circumstances, if you have a database running on the
    virtual machine, it may be necessary to create the snapshot without
    performing the quiesce. This option must be used with care, and is not
    recommended for most VMware environments.

+  Backup Exec Tape Reader now supports BE 11/11d
  This feature enables customers to import and restore their BE 11 & BE 11d
  backup images into the NetBackup environment. Customers who want to
  migrate from BE to NetBackup will likely benefit from this feature.


+  NetBackup User Interfaces Features and Enhancements
  - NetBackup Administration Console: Configurable auto-logoff
    NetBackup now provides the option for administrators to configure the
    administration console to automatically log off users after a
    specified period of inactivity. They are required to enter their
    credentials again before further administering the product. This
    feature is off by default.

  - NetBackup Administration Console: Configurable Login Banner
    A login banner can be configured to appear for users while logging in.
    Customers who require an acceptance of a corporate security or legal
    statement for administrators to proceed with login would use this
    feature. Another common use is for company branding or informational
    messages, where users are presented with the message but not required
    to accept or act on the communication.


+  OST Enhancements
  - OpenStorage Direct Copy to Tape
    Many intelligent disk appliances attach tape libraries on the back-end
    and create tape copies unbeknownst to NetBackup. The OpenStorage API has
    been extended to enable data protection applications to direct data
    movement from disk to tape. The user, through NetBackup, chooses which
    backup images are copied to tape and also controls the tape format.

    The following list explains some of the benefits of this feature:
    - Eliminates I/O through the media server
    - NetBackup's catalog is aware of all backup copies
    - Enables you to apply different retention periods for copies
    - NetBackup aware tape format - the tapes can be transported to a
      different library and read by NetBackup.

   For more information about this feature, see the NetBackup Shared Storage
   Guide for release 6.5.4 at the following URL:

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

  - OpenStorage Optimized Synthetic backups
    The OpenStorage Optimized Synthetic backup method requires no data
    movement across the network from the storage server to the media
    server. The optimized, synthetic backup method constructs the synthetic
    image by using calls from the media server to the storage server. The
    media server tells the storage server which full and incremental images
    to use to create the synthetic backup. Then, the synthetic backup is
    constructed directly on the storage server.

    (In previous releases, the synthetic backup method was constructed on
    the media server. Backups were moved across the network from the
    storage server to the media server and constructed (or synthesized)
    into one image. The synthetic image was then moved back to the storage
    server. The process was lengthy and caused additional network traffic.)

    For more information, see the NetBackup Shared Storage Guide for
    release 6.5.4 at the following URL:

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

  - OpenStorage versioning solution
    It is possible for a number of potential version incompatibilities to
    arise, because different versions between the various components exist
    in the stack. This Release Update contains a versioning solution that
    permits interoperability across the OST core library and the OST plug-in.
    These changes enable the OST core library to work with different
    versioned libraries and plug-ins can determine which versions to support.

  - Support NetApp P3 conversion to OST and metadata support
    This feature provides enhanced functionality in the OpenStorage program.
    Vendors, such as NetApp, can leverage existing benefits of the OST
    program.  In addition, they can develop and deliver OST-specific feature
    sets like optimized duplication or virtual synthetics without regard to\
    the NetBackup release schedule.

    Vendors such as these currently parse an OST image name to identify the
    NetBackup-specific details such as copy and fragment numbers. This
    feature adds an additional (imageset) structure to an OST image's
    definition that enables NetBackup to give plug-in vendors a programmatic
    way to connect OST images into a logical hierarchy.

  - This feature also supports Hot Catalog backup and restore operations to
    OpenStorage Disk Pools.


+  Storage Lifecycle Policy Features and Enhancements

  - Network Optimized Duplication
    This feature optimizes duplication traffic by selecting the same Media
    server for both Source and Destination when possible. The result is that
    no data is sent over the network. This gives the user better control of
    image movement over the storage network and it eliminates LAN usage
    during a duplication operation.

  - Hierarchical duplication (Dup from Copy X)
    This feature provides the ability to specify, in a Storage Lifecycle
    Policy, a hierarchy the represents a cascaded duplication plan. Each
    duplication step specifies which storage device is used as the source.
    The typical use case is to drive off-host duplication. This enables a
    configuration that clearly separates the duplication overhead from the
    backup processes.

  - Storage Lifecycle Policy (SLP) performance improvements with media
    contention during duplication jobs

    New in 6.5.4:  SLP Media Set Batching for duplicating backup images
    from a tape device (or VTL) to some other device.

    A SLP collects batches of related backup images and includes the images
    in a series of duplication jobs.  How these images are selected to create
    each batch (each duplication job), can significantly improve or diminish
    the efficiency (performance) of the duplication jobs.  If multiple
    duplication jobs are created such that they need to read from the same
    set of tapes, the contention for media can seriously diminish product
    performance.

    In previous NetBackup versions, the SLP created a duplication job for a
    batch of backup images if the images all started on the same tape.  The
    parameters in the LIFECYCLE_PARAMETERS file determined how large the batch
    file could become.  If the parameters in the LIFECYCLE_PARAMETERS were set
    sufficiently large, then all of the images that started on a given tape
    were included in a single batch (duplication job).  If those parameters
    were not large enough to include all images that started on a given tape,
    then multiple duplication jobs were created to copy the images from the
    tape. These multiple duplication jobs were in contention for the same set
    of media. Symantec advised administrators to set the parameters in the
    LIFECYCLE_PARAMETERS file large enough to include all images that started on
    a given tape.

    However, even if administrators followed this advice, the last image on a
    tape (or the last images if the backups were multiplexed) would span to a
    second tape, causing contention for the second tape.  This occurred because
    a subsequent duplication job had tried to duplicate all images that started
    on the second tape.

    In NetBackup 6.5.4, the SLP looks beyond a single tape when forming each
    batch of images (each duplication job).  In 6.5.4, the SLP collects all
    images that start on the first tape, but will continue on to subsequent
    tapes, as images continue to span from tape to tape.  When an image spans
    to a second tape, the SLP adds the images that start on the second tape to
    the batch that will form the next duplication job.  This continues as
    images span tapes, until one of the parameters in the LIFECYCLE_PARAMETERS
    file causes the SLP to stop adding images. At that point, the duplication
    job is submitted (requested).

    The administrator should know the following information about configuring
    these parameters.

    Keep in mind that the goal is to allow the duplication jobs to become as
    large as possible for more efficient duplication.  Especially when the
    original backup images are multiplexed on tape, duplication performs best
    when one large duplication job can stream "all" images from a connected set
    of tapes to secondary storage.  Administrators are often inclined to split
    this set of tapes into multiple duplication jobs, so that they can keep
    multiple destination drives spinning.  Consider making the number of drives
    that write duplicate copies equal to the number of drives that write the
    original backup images.  This allows batches of connected images to stay
    together in complete and efficient duplication jobs.

    A. If duplication jobs are to run at the same time as backup jobs, or if
       you need enough concurrent duplication jobs to keep all of the

       destination tape drives spinning (see the previous paragraph), then one
       of the following parameters must be used to limit the size of the
       duplication jobs:
       - MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB
       - MIN_GB_SIZE_PER_DUPLICATION
       - MAX_GB_SIZE_PER_DUPLICATION

    B. Alternatively, the user can disable SLP duplication during the backup
       window.  This lets the duplication jobs run after the product has stopped
       writing backups to the source media, thereby further reducing contention
       for the source media.  This can improve the performance of duplication
       itself, though there may be idle time on the devices between the backup
       window and the time that duplications are allowed to begin.

       In either case, to further reduce media contention, assign each SLP to a
       different Volume Pool for any copy that will be used as the source copy
       for subsequent duplication jobs.  To separate the source tapes in this
       way avoids having multiple SLPs trying to read from the same source tape
       pool.

+  Support for HP-UX 11iv3 persistent DSFs:
  NetBackup 6.5.4 includes support for HPUX 11iv3 persistent device special
  files (DSF) for tape drives and robotic tape libraries.

  The installation of the NetBackup 6.5.4 patch makes no device path changes
  on existing NetBackup installation. The NetBackup administrator must change
  device paths on existing installations. See "How to upgrade to 11iv3 new
  persistent DSFs" below for more information on transitioning to the new DSFs.

  If your system is a new NetBackup installation and you have not previously
  configured the legacy HP device paths, you do not need to use the upgrade
  section below. NetBackup device discovery will correctly configure your
  devices using the new HP-UX persistent DSFs.

  You do not have to use persistent DSFs. However, beginning with this patch,
  NetBackup device discovery finds only persistent DSFs. To use legacy device
  files on new NetBackup installations, you must configure them manually.

  Also, you can use persistent DSFs on some HP-UX servers and legacy device
  files on others.

  For information about how to create the persistent DSFs, see "To configure
  HP 11iV3 devices after connecting devices to the system" below.

  About Persistent DSFs:
  Persistent DSFs for tape drives have a tape path form of
  /dev/rtape/tape#_BESTnb.  NetBackup only supports the Berkeley no-rewind
  device paths. NetBackup also requires pass-through paths for all tape drives.

  In HP 11iv3, these tape pass-through paths are of the following form:
      /dev/pt/pt_tape#
  The # represents the instance number that matches the number in the
  /dev/rtape/tape#_BESTnb device file or retrieved from the ioscan output.

  These pass-through paths are created automatically for all tape defined tape
  drives that have valid /dev/rtape paths. Any NetBackup auto discovery command
  or the /usr/openv/volmgr/bin/scan command automatically creates these
  pass-through paths. For robotics, NetBackup supports the HP-UX eschgr driver
  paths of the form /dev/rchgr/autoch#.

  NetBackup also supports the use of the IBM atdd tape driver on HP-UX 11iv3.
  There is a minimum atdd driver level required. Please see the NetBackup
  Hardware Compatibility List for more IBM attd driver levels supported and
  atdd configuration information:
     http://entsupport.symantec.com/docs/284599
  Also see the NetBackup OS compatibility list for the minimum OS patch level
  required to run on HP-UX:
     http://entsupport.symantec.com/docs/325328

  To create HP-UX 11iV3 device files after connecting devices to the system:
  Use one of the following procedures to create the DSF files. Create DSFs on
  every HP-UX 11iV3 server on which you want to use the new persistent DSFs. If
  you do not create persistent DSFs, you must create legacy device files and
  then configure devices manually in NetBackup.

  NetBackup device discovery discovers these files when you configure devices
  in NetBackup.

  To create the tape devices files automatically:
  - Enter one of the following commands as root:
        For estape (tape entries): insf - d estape
        For eschgr (autoch entries): insf - d eschgr
        For IBM atdd driver controlled tape drive: insf - d atdd

  - Adding the -e option to these command lines refreshes the device path for
    all devices using the given driver. For example, "insf - d estape - e"
    refreshes all estape controlled tape drives.
  For more information about using the HP-UX insf command, see the man page.

  To manually create passthru paths for tape drives:
  - Enter the following command (# is the instance number of the device from
    the ioscan output):
        mksf - P - C tape - I #
    For more information about using the HP-UX mksf command, see the man page.

  How to upgrade to 11iv3 new persistent DSFs
  -------------------------------------------
  To upgrade from the legacy DSFs to the new DSFs:

  1. Add the following entry to the /usr/openv/volmgr/vm.conf file (the syntax
     must be as specified in all capital letters):
        AUTO_PATH_CORRECTION=YES

  2. After adding the entry to the vm.conf file and with no current jobs running
     on the media server, run the following command:  
        /usr/openv/volmgr/bin/stopltid

  3. Wait a few minutes for the service to stop, then restart ltid by running
     the following command:
        /usr/openv/volmgr/bin/ltid
       
  You can also start and stop the device service by using the NetBackup
  Administration Console.

  After the services are all restarted, you should be able to see that the tape
  paths and robotic paths were updated to the new persistent device paths.

  After the services are started and device paths updated, you can (but do not
  have to) remove the AUTO_PATH_CORRECTION=YES entry from the vm.conf file can
  be removed. If you roll back to a previous NetBackup 6.5.x version, the
  AUTO_PATH_CORRECTION=YES entry in the vm.conf file will cause the device
  files to be automatically re-configured using the legacy DSF's when ltid
  restarts on the older patch version.

  If you ran device discovery before reading this information, the new DSF
  paths were added to the configuration but the old legacy path(s) will still
  be configured in the device database as alternate paths. Because you should
  only be running the legacy paths or the new paths but not both, on restart
  if ltid finds a mixed path configuration on the media server it automatically
  runs AUTO_PATH_CORRECTION, which uses all the new DSFs and purge the legacy
  DSF's from your NetBackup configuration for the media server.

  To save the old paths, you can use tpconfig to DISABLE to old paths but keep
  their data in the device configuration before restarting ltid.


+  NOM Features and Enhancements

  - Tree view roll-up for multi-part jobs
    For multi-part jobs - like those from storage lifecycle policies, Vault,
    application and multi-streamed backups - users can choose whether to show
    all jobs or only the top level, parent job in the NOM Job Monitor. When
    viewing only parent jobs, a tree structure is presented with the overall
    jobs status in the top node. Users are then able to expand the tree to
    drill into the individual child jobs and related details within.

  - NOM Integration with Symantec Threatcon
    Symantec Threatcon is a measurement of the global threat exposure. NOM
    now displays the Threatcon graphic and threat level so that NetBackup
    administrators can determine whether any action is required in the
    protection environment. If an administrator does not spend time actively
    monitoring the environment, NOM also offers a Threatcon alert for
    notification when a user-specified threat level is met.

  - Read-only NOM access
    A built-in role for read-only access to NOM. The read-only user can
    monitor all operations, but not take any action against the NetBackup
    environment (up and down drives or services, start or stop jobs, and so
    forth). Daily monitoring and troubleshooting activities can be assigned
    to the operations team without introducing the risk of configuration
    updates or NetBackup actions that impact backup or recovery activities.

  - NOM CSV report export
    NOM reports can now be emailed in CSV format. Some of the benefits
    users expect from this feature include the ability to analyze the data
    outside of the NOM tool, correlate with other data sets and preserve
    the data for historical reference and analysis.

  - NOM performance/scalability improvements
    NOM now provides visibility and a single-point-of-control across the
    entire NetBackup environment. With this release, a single NOM server
    can support up to 100 master servers and 150,000 jobs per day. Also,
    additional infrastructure optimizations provide faster and more
    predictable User Interface response times.

  - Virtual Client Summary report
    A new report called Virtual Client Summary report has been added in
    NOM 6.5.4. This report shows details of all virtual clients of a
    NetBackup Master Server. Using this report, you can determine whether
    these virtual clients were backed up by NetBackup or not.

  - Representation of Storage Unit Lifecycle Policy hierarchy
    In NetBackup 6.5.4, Storage Unit Lifecycle Policy feature has been
    enhanced so that you can add storage destinations in a hierarchical
    manner. For example, a backup storage destination can have a
    duplication storage destination, which can further have multiple
    duplication destinations. NOM 6.5.4 has been enhanced to represent
    this Storage Unit Lifecycle Policy hierarchy in a tree view, as it is
    managed in NetBackup.

  - Improvement in database upgrade process
    The upgrade process has now been improved, to avoid any hassles because
    of database upgrade taking long hours. In NOM 6.5.4, the database is
    upgraded in two stages. The first part of the database, which comprises
    data other than Jobs and Media and is smaller in size, is upgraded while
    NOM is being upgraded to 6.5.4. The bigger part of the database
    comprises Job and Media data, which is upgraded after the NOM 6.5.4
    upgrade is complete. You can work in the NOM console while this data is
    being upgraded in the background. In addition, you can view the database
    upgrade status using the NOM console.

  - Enhancements in Monitoring section
    The Monitoring section has been enhanced in terms of usability. The
    Master Server details page has been updated to clearly state the
    connection status of all monitors as Connected, Partially Connected,
    and Not Connected. In addition, you can view the root cause for a
    connection failure.

  - Few enhancements in alerting functionality
    For a hung job alert, you can now configure NOM to ignore the time for
    which a job is in a queued state. You can also configure the severity
    for an email/trap that is sent when an alert is cleared.

  - Support for new SNMP versions
    NOM now supports the following SNMP versions:
     - SNMPv1
     - SNMPv3


+  New Tools and Supportability

  - NBCC utility
    The NBCC utility uses the output from various OS and NetBackup commands
    to analyze the consistency state of the NetBackup configuration and
    database/catalogs as they relate to tape media. If inconsistencies are
    detected, NBCC consolidates and packages the resulting data into a bundle
    that can be sent to Symantec Tech Support for analysis.

 - NBCCR utility
    The NBCCR utility processes database/catalog repair actions as defined
    in a special file generated by and under the guidance of Symantec Tech
    Support. This file is created as part of the analysis of the data
    collected by NBCC and any site specific situations.


+  General Enhancements to NetBackup

  - This release contains enhancements to the bpclntcmd command that
    make it easier to update the REVERSE_NAME_LOOKUP configuration on a
    NetBackup client.

  - An enhancement has been made to the NetBackup Live Update feature that
    enables a user to select a clustered master virtual name when creating
    LiveUpdate policies.


----------------------------------------------
NetBackup 6.5.3 New Features and Enhancements:
----------------------------------------------
The following features and enhancements were introduced in NetBackup 6.5.3. For
more information about any of the features introduced in that release, refer to
the NetBackup 6.5.3 Documentation Updates document contained in the following
TechNote on the Symantec Support Web site.  

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

+  NetBackup Exchange Granular Recovery

  NetBackup 6.5.3 includes the ability to restore Exchange mailboxes, folders,
  and messages from a storage group or database backup. This type of backup
  can serve both kinds of recovery situations: from the same backup image you
  can choose either to restore whole storage groups and databases or you can
  select individual items within mailboxes.

+  The administrator can customize how the Storage Lifecycle Manager (nbstserv)
  runs duplication jobs by creating a LIFECYCLE_PARAMETERS file and adding
  specific parameters.  (See Chapter 5 in the 6.5 Administrator's Guide, Vol. I,
  for complete setup instructions.)

  The following parameters were added since 6.5.

  DUPLICATION_SESSION_INTERVAL_MINUTES
     Indicates how frequently nbstserv starts a duplication session. During a
     duplication session, NetBackup looks for completed backups on backup
     storage destinations and decides whether or not it is time to start a new
     duplication job.

     Default: 5 minutes. Minimum: 1 minute.
     Syntax: DUPLICATION_SESSION_INTERVAL_MINUTES 5

  IMAGE_EXTENDED_RETRY_PERIOD_IN_HOURS
     All copies must be completed in a lifecycle. If necessary, NetBackup
     initially tries three times to duplicate an image to a duplication
     destination. This prevents NetBackup from retrying too frequently. If,
     after three tries, the copy is still unsuccessful, this parameter indicates
     how long NetBackup waits before an image copy is added to the next
     duplication job. (The frequency is determined by the
     DUPLICATION_SESSION_INTERVAL_MINUTES parameter.)

     The NetBackup administrator may need more than two hours (the default) to
     solve the problem. Alternatively, the administrator can temporarily
     de-activate a lifecycle using nbstlutil.

     Default: 2 hours. Minimum: 1 hour.
     Syntax: IMAGE_EXTENDED_RETRY_PERIOD_IN_HOURS 2

  The following parameters have been added to help the lifecycle run duplication
  jobs as efficiently as possible.  They are similar to existing parameters but
  indicate the size in gigabytes instead of kilobytes:

  MIN_GB_SIZE_PER_DUPLICATION_JOB
     Use this parameter (similar to MIN_KB_SIZE_PER_DUPLICATION_JOB, introduced
     in 6.5) to indicate the size that the batch of images should reach before
     one duplication job is run for the entire batch.  The lifecycle does not
     request a duplication job until either:

     - The aggregate size of the images in a batch reaches the minimum size as
       indicated by this parameter, or
     - The MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB time has passed. This
       parameter determines the maximum time between batch requests.

     Default:  8 gigabytes.  Syntax:  MIN_GB_SIZE_PER_DUPLICATION_JOB 8

  MAX_GB_SIZE_PER_DUPLICATION_JOB
     Use this parameter (similar to MAX_KB_SIZE_PER_DUPLICATION_JOB,
     introduced in 6.5) to indicate how large the batch of images is allowed to
     grow. When the size reaches the size as indicated by this parameter, no
     more images are added to the batch.  Default:  25 gigabytes.  

       Syntax:  MAX_GB_SIZE_PER_DUPLICATION_JOB 25

  Notes about MIN_GB_SIZE_PER_DUPLICATION_JOB/MAX_GB_SIZE_PER_DUPLICATION_JOB:
     - Use either the KB or the GB version of these parameters, but not both.
     - If only one MAX or one MIN parameter is specified, the other uses the
       default value for that parameter.



----------------------------------------------
NetBackup 6.5.2 New Features and Enhancements:
----------------------------------------------
The following features and enhancements were introduced in NetBackup 6.5.2. For
more information about any of the features introduced in that release, refer to
the NetBackup 6.5.2 Documentation Updates document contained in the following
TechNote on the Symantec Support Web site.

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

+  An enhancement has been made within Enhanced Staging to compute the
  maximum number of concurrent jobs for storage groups more precisely.
  Previously, Enhanced Staging used a hard-coded number to determine the maximum
  number of concurrent jobs for a storage group.  

+  This feature implements fast object positioning for NBBSAGetMultipleObject
  API restores. Fast object positioning improves restore performance by
  enabling XBSA to position the media server to the exact location of an
  object in an image. This enables XBSA to restore the object without having
  to read through the entire image.

+  This release of NetBackup provides enhanced file-based checkpointing for the
  SQL Server. For example, changes to the NetBackup for SQL Server framework
  makes it possible to resume partially completed backups. In addition, you can
  use the SQL Server database to recover a database to a new location from a
  set that does not include a full database backup image. (In earlier versions,
  only those sets that included a full database backup image was supported.)

  And finally, improvements were made that reduce the work-loss impact to the
  SQL Server database recovery by making recoveries possible through a series
  of restores rather than a monolithic restore operation.

+  Activity Monitor displays job state details
  This Release contains changes to the column layout in the Jobs
  view of the Activity Monitor. The columns are not displayed as per the layout
  preferences that you may have specified for the earlier releases.  Two new
  columns named State Details and Priority have been added to the Jobs view.
  The State Details column is displayed by default and indicates specific
  reasons why a job is queued or is not progressing.  It also lists the backup
  resource or condition for which the job is waiting.  The Priority column is
  hidden by default and indicates the current relative priority of a job to
  obtain backup resources.

+  Reverse Host Name Lookup
  The domain name system (DNS) reverse host name lookup is used to determine
  what host and domain name are indicated by a given IP address. In previous
  releases, NetBackup required that reverse host name lookup was working to
  determine that a connection to a host came from a recognizable server.

  Some administrators cannot or do not want to configure their DNS server for
  reverse host name lookup. For these environments, NetBackup now allows the
  configuration of Reverse Host Name Lookup as a master server, media server,
  or client host property in order to allow, restrict, or prohibit reverse host
  name lookup.

+  New Job Priority defaults and overrides
  In previous releases, the job priority was set only in the policy
  configuration using the Job Priority setting. The administrator was not able
  to specify a job priority for job types other than backups. In this release,
  administrators have greater flexibility and control over the priority of a
  job. In addition, administrators can set the priority of a job from multiple
  locations in the NetBackup Administration Console, from the Backup, Archive,
  and Restore client interface, and from the command line. This capability
  improves the usability and consistency of NetBackup's job priority scheme.

  This release introduces the following additions for setting and changing the
  priority of a job:
  - The ability to configure default job priorities for different job
    types in the new Default Job Priorities master server host properties.
  - The ability to dynamically change the job priority of a queued or an
    active job that waits for resources in the Activity Monitor.
  - The ability to set the priority for a media content job in the Reports
    utility.
  - The ability to set the job priority for import, verify, and duplicate
    jobs in the Catalog utility. The ability to specify the job priority
    for restore jobs in the Backup, Archive, and Restore client interface.
  - The ability to change job priorities in the bpadm and the bp interfaces.
  - The ability to specify the job priority from the command line.

+  Data at Rest Key Management Service (KMS)
  The KMS feature is a master server-based symmetric key management service that
  manages symmetric cryptography keys for tape drives that conform to the
  T10 standard (i.e. LTO4).  

+  Multiple Copy Synthetic Backups
  The Multiple Copy Synthetic Backups feature introduces the capability to read
  remote, non-primary source images to produce a second synthetic copy in
  remote storage.

  This feature provides the following benefits:
  - This feature eliminates the bandwidth cost of copying synthetic full
    backups to another site. Instead of duplicating a local synthetic full
    backup to a remote site to produce a second copy, it is more efficient to
    produce the second copy by using data movements only at the remote site.

  - This feature provides an efficient method to establish a dual-copy disaster
    recovery scheme for NetBackup backup images.

+  AdvancedDisk storage option
  This release contains new features that enable the user to choose which
  machines can be used for restores and duplications. The following list
  describes the added capabilities that this feature offers.

  - AdvancedDisk supports storage access by more than one media server.
  - AdvancedDisk supports specification of preferred or required media
      servers for restore and duplication operations. This new capability
      replaces the FORCE_RESTORE_MEDIA_SERVER option.

+  SharedDisk storage option
  The SharedDisk documentation in the Veritas NetBackup 6.5.2 Documentation
  Updates document packaged with this release supersedes the SharedDisk
  documentation in the NetBackup 6.5 and 6.5.1 versions of the NetBackup
  Shared Storage Guide. The Veritas NetBackup 6.5.2 Documentation Updates
  document contained in the following TechNote on the Symantec Support Web
  site. (http://entsupport.symantec.com/docs/302438)

  With this release, the SharedDisk feature enables you do the following:

  - Specify preferred or required media servers for restore and duplication
    operations. This new capability replaces the FORCE_RESTORE_MEDIA_SERVER
    option.  This capability provides the following benefits:
     - Offloads the workload of restores from the servers that perform the
       backups.
     - Directs the duplication traffic to specific storage servers.

  - Use either LUN masking or SCSI persistent reserve for exclusive volume
    access on the storage arrays.

+  Added SCSI persistent reservation support for SharedDisk on RedHat 4.0
  Update 5.

+  Added SCSI persistent reservation support for SharedDisk on SuSE 9 SP 3.

+  SAN Client and Fibre Transport
  The following list introduces the new features and capabilities for SAN
  client and Fibre Transport in this release.

  - You can use tape as a storage destination for the SAN Client and Fibre
    Transport feature.
  - On Solaris systems, NetBackup 6.5.2 detects the PCI bus and only allows
    ports on one bus to be used for target mode, as follows:
    - The first choice is the bus with the most 2312 target mode ports.
    - If there are no 2312 target mode ports, the bus with the most 24xx
      target mode ports is used.
    - Target mode ports on other buses are not used.
  - This release will now support the following QLogic HBAs for Fibre
    Transport media servers:
    - QLA2460 and QLA2462 (PCI-X)
    - QLE2460 and QLE2462 (PCI-e)

+  NetBackup for Microsoft Exchange
  - Backups of the Exchange 2007 passive VSS writer. With Exchange 2007,
    Microsoft introduced a new concept for Exchange that included the mirroring
    (replicating) of Exchange databases and logs to either a local server with
    replication enabled (LCR) or to a passive node of a Microsoft cluster with
    replication enabled (CCR).  The only supported backup interface to this
    replicated data is the "new" VSS passive writer that is automatically
    installed in either of these replication models. This NetBackup feature
    allows the user to select what VSS writer is backed up from the Host
    Properties for the Client. The client seamlessly backs up and catalogs as
    if it were a local VSS backup.

  - Exchange 2007 enhancements to consistency checks. Beginning with 6.5.2,
    NetBackup uses the Microsoft API to check the consistency of databases and
    transaction logs and to provide additional details.

    To take advantage of the Exchange 2007 consistency checks with the Microsoft
    API with a VSS off-host backup, the Exchange Management Console must be
    installed on the off-host client.

  - Ability to automatically redirect a VSS restore to the Exchange 2007
    recovery storage group (RSG).

  - Instant recovery for Exchange 2003 and later. This feature enables the
    recovery of storage groups and databases from a snapshot. These snapshots
    can also be staged to tape.

  - Additional information on the 6.5.2 version of the NetBackup for Exchange
    agent is available.

+  NetBackup for Microsoft SharePoint Portal Server
  - Document-level restores of MOSS 2007 & WSS 3.0.
  - Support for SharePoint 2007 document restore from a database backup.
  - Support for Microsoft SQL 2008.
  - Support for 64-bit versions of SQL Server.
  - Additional information on the 6.5.2 version of the NetBackup for SharePoint
    Portal Server agent is available.

+  NetBackup for Microsoft SQL Server
  - Support for Microsoft SQL Server 2008.
  - Support for the backup and restore data contained in the SQL Server
    filestream data type. The filestream data type allows the user to manage
    file system data using SQL Server.
  - SQL Server file-based checkpoint/restart.

+  NetBackup for Oracle (Support for Oracle 11g)
  NetBackup 6.5.2 supports backups and restores of Oracle 11g. This includes
  support for Oracle advanced data compression and Oracle data pump.

  For instructions on linking the Oracle Recovery Manager (RMAN) with NetBackup,
  refer to the appropriate procedure for your platform and Oracle 9i or later
  or for Oracle 10g and later.

  The information in the Appendix "Oracle 9i and 10g Real Application Clusters"
  also applies to Oracle 11g.

+  Storage Lifecycle Policy destination configuration changes
  This release introduces several configuration changes for storage lifecycle
  policy storage destinations. The changes appear in the Storage Destination
  dialog box and are as follows:

  - The new Snapshot destination type is available when the Snapshot Client
    option is installed.
  - The Alternate read server selection is available only for duplication
    destinations.
  - The Preserve multiplexing option is available for multiplexed source
    images.

+  Database Administration Tool for NetBackup Relational Databases
  The NetBackup relational database and Bare Metal Restore database in
  NetBackup 6.0 and 6.5 used Sybase Adaptive Server Anywhere (ASA). (Also
  known as SQL Anywhere.) NetBackup 6.0 and 6.5 included command line utilities
  to administer the databases. NetBackup 6.5.2 contains a tool that makes it
  easier for administrators to perform database administration tasks.

  The Database Administration tool for NetBackup databases is a stand-alone,
  interactive, menu-driven tool available on both UNIX and Windows:
  -  On UNIX, the tool has a menu-user interface, similar to the bpadm tool.
  -  On Windows, the tool has a graphical user interface. The tool is based on
     existing command lines.

  The tool, on both UNIX and Windows, provides a way for the administrator to
  perform many actions.  For a list of these actions and more information about
  this new feature, refer again to the NetBackup 6.5.2 Documentation Updates
  document.

+  How to configure and use NetBackup for VMware
  NetBackup for VMware provides backup and restore of the VMware virtual
  machines that run on VMware ESX servers. NetBackup for VMware takes advantage
  of VMware Consolidated Backup (VCB) technology. The backup process is
  off-loaded from the ESX server to a separate host that is called the VMware
  backup proxy server.

  The NetBackup 6.5.2 Documentation Updates document contains a chapter that
  describes this feature in detail as well as how to configure NetBackup for
  VMware.

+  Snapshot client features
  Snapshot features contained in this release of NetBackup are:
  - Storage lifecycle policies with Instant Recovery snapshots
    Instant Recovery snapshot-based backups to the types of images that
    NetBackup can manage with lifecycle policies. The Instant Recovery feature
    makes snapshots available for quick data recovery from disk. Lifecycle
    policies support a lifecycle storage plan for the storage unit copies made
    during an Instant Recovery backup.

  - NetBackup and Continuous Data Protection (CDP)
    CDP dramatically changes the data protection focus by continuously
    safeguarding all changes to important data. CDP increases the available
    recovery point granularity.

  - New disk array snapshot methods in 6.5.2
    The array snapshot methods contained in this release take advantage of
    high-speed mirroring and other snapshot capabilities that are provided by
    the arrays. The following list shows the new snapshot methods introduced in
    this release.  
      - Hitachi_CopyOnWrite
      - Hitachi_ShadowImage
      - IBM_DiskStorage_FlashCopy
      - IBM_StorageManager_FlashCopy

  - VMware raw device mode (RDM)
    VMware's raw device mapping mode (RDM) allows a VMware virtual machine to
    directly access raw physical disks. With raw device mapping, a VMware
    virtual machine can use large storage devices such as disk arrays. The
    arrays can be locally attached to the ESX server or configured on a Fibre
    Channel SAN.

+  This release adds coexistence support for clients that utilize EMC Powerpath
  devices.  Bare Metal Restore will not re-create or restore volumes or
  filesystems that reside on EMC Powerpath devices. The following is a summary
  of expected behavior when backing up and restoring EMC Powerpath clients
  with Bare Metal Restore:

  -  During backup, the configuration that is imported will have all
     references to EMC Powerpath pseudo-device names removed and replaced
     with the first active physical disk in the EMC Powerpath configuration.
     This is applicable for all UNIX and Linux platforms. For Windows
     platforms, pseudo device naming convention matches to native device naming
     convention and only pseudo device entry is maintained in the
     configuration.

  -  The physical disk(s) chosen to represent the EMC Powerpath configuration
     will be "Restricted" from restoration.

  -  The physical disk(s) chosen to represent the EMC Powerpath configuration
     will not be allowed to be unrestricted during Dissimilar Disk Restore
    (DDR) and Dissimilar System Restore (DSR) mapping operations.

  -  The filesystems, volumes and volume groups (if applicable) originally
     resident on EMC Powerpath devices can be mapped to non-EMC Powerpath
     devices for restoration.

  -  Resources (disk groups and volume groups) originally configured on
     EMC Powerpath devices will not automatically be imported and may not be
     available in the post-restore environment. Depending on the operating
     system, volume manager and Host Bus Adapter (HBA) in use will determine
     whether the resource is automatically available after restoration has
     completed.  If the resource is not available, it will need to be either
     imported by hand or made available via the external procedure feature of
     BMR if automation is desired.

  - For Windows platforms, Symantec's volume manager shipped with Storage
    Foundation for Windows (SFW) is not supported with the EMC Powerpath
    configured disks in this release and is planned for a future release.

+  The NBSU utility has been upgraded to include the following new features
  and capabilities.  In addition, this release contains the latest version
  which is 1.2.6.
  - NBSU now detects DNS alias hostnames.
  - Hostname checks for the etc/hosts, etc/lmhosts, NIS and NISplus will now
    detect and use the associated IP addresses.
  - Enhancements were made to the nbsu.exe Windows file-property values with
    additional Symantec-specific information.

+  The release contains the following changes and enhancements to the High
  Availability Guide.
  - Configuring the Key Management Service (KMS) for monitoring
  - Clustered media servers on Windows 2008
  - Changes to the bpclusterutil command for UNIX and Windows platforms

+  Many of the preceding features contained additional commands as well as
  new options to existing commands.  These new options and commands have been
  documented in the Commands chapter of the NetBackup 6.5.2 Documentation
  Updates document.

+  The following procedure should have been included in the Veritas NetBackup
  Shared Storage Guide that was released with the NetBackup 6.5 GA.

  BasicDisk storage units and Windows UNC

  Beginning with the NetBackup 6.5 release, if you use Windows Universal Naming
  Convention (UNC) pathnames to specify BasicDisk storage, you must configure
  the following NetBackup services on the NetBackup media server to use the
  same credentials:
  - The NetBackup Remote Manager and Monitor Service
  - The NetBackup Client Service

  If the services do not use the same credentials, NetBackup marks BasicDisk
  storage units that have UNC pathnames as DOWN.

  To configure NetBackup services credentials
  1. In Windows, open Services in the Microsoft Management Console.
  2. Select one of the following NetBackup services and open its Properties:
     - The NetBackup Remote Manager and Monitor Service
     - The NetBackup Client Service
  3. On the General tab, select Stop to stop the service.
  4. On the Log On tab, select This Account and then enter valid credentials.
     The credentials must allow read and write access to the storage.
  5. On the General tab, select Start to start the service.
  6. Repeat for the other service.

+  (ET1267896) When performing backups using the new Pure Deduplication
  Option (PDDO) feature, Symantec suggests that users monitor their shared
  memory usage as the number of jobs increases.  The job-size throttling has
  been turned off in NetBackup 6.5.2 to allow more PDDO backups to run
  concurrently.  Please consult your NetBackup Performance Tuning Guide for
  additional information on NetBackup tuning parameters affecting shared memory
  usage.

+  Enabling Multiple Robotic Paths for Highly Available Tape Libraries
 
  This release contains a new feature that allows a user to enable multiple
  robotic paths to achieve high availability for NetBackup TLD type tape
  libraries. This feature enables the use of multiple paths from a single media
  server to the tape robot. For more information about this feature, refer to
  the following TechNote on the Symantec Support Web site.
     http://entsupport.symantec.com/docs/303942

+  A new option has been added to the Disk Group Mapping Utility dialog of the
  BMR mapping wizard.

  For AIX and HP-UX, the option is called Simplify volume group.
  For VxVM, the option is called Simplify disk group.
  For Solaris Volume Manager, the option is called Simplify disk set.

  This option is being added to the table of selection items for the dialog.
  The description of this option is as follows:

  Select this option to force the creation of the volume group (AIX and HP-UX),
  disk group (VxVM), or disk set (Solaris Volume Manager) and set the number of
  copies and stripes in all the mapped volumes to 1. Use this option to map all
  volumes as concatenated volumes onto a disk.

  This option is only available if you select the Automatically map volumes in
  this volume group option on this page.


----------------------------------------------
NetBackup 6.5.1 New Features and Enhancements:
----------------------------------------------
The following features and enhancements were introduced in NetBackup 6.5.1.

+  For Solaris systems, you can now use SCSI persistent reservations for
  exclusive LUN access control for disk arrays used with the SharedDisk
  feature.  For more information, see the following Symantec TechNote:
     http://entsupport.symantec.com/docs/293321

+  Added support for Microsoft Office SharePoint Server (MOSS) 2007 and Windows
  SharePoint Services (WSS) 3.0

  -  NetBackup 6.5.1 supports Microsoft Office SharePoint Server (MOSS) 2007
     and Windows SharePoint Services (WSS) 3.0.
     -  MOSS 2007 standalone, federated, 32-bit and 64-bit with SQL 2005 or
        SQL Express. Shared Services configuration protection is supported
        within the same farm.
     -  WSS 3.0 standalone, federated, 32-bit and 64-bit with SQL 2005 or
        SQL Express.

  -  There are additional requirements if you want to perform document-level
     restores with SharePoint Portal Server 2003 and a 64-bit OS. You need to
     upgrade to Windows 2003 R2 and install the Software Development Kit (SDK)
     for SUA available from Microsoft. SUA is the Subsystem for UNIX-based
     Applications.

  -  Document-level restores of MOSS 2007 & WSS 3.0 are not supported in
     NetBackup 6.5.1. This functionality will be available in a future release.

  For further information on how to use NetBackup with MOSS 2007 and WSS 3.0,
  refer to the following TechNote on the Symantec Support Web site.
     http://entsupport.symantec.com/docs/292586

+  The following enhancements made to the NetBackup for Microsoft Exchange:

  -  Exchange 2007 mailbox-level backups and restores

     This release supports mailbox-level backups of Exchange 2007.  This
     includes the same functionality as in previous versions of NetBackup for
     Exchange, except an additional Microsoft package is required.

     Download and install the Microsoft Exchange Server MAPI Client and
     Collaboration Data Objects package. Version 6.05.7888 or higher is
     required.  You can find this package at the following Web site:
        http://www.microsoft.com/downloads/

     To run mailbox backups and restores, you must create a user account for
     the NetBackup Client Service. The process is different for Exchange 2007
     than for earlier versions of Exchange. Refer to the TechNote, Continued
     support for Microsoft Exchange 2007 on the Symantec Support Web site.
        http://entsupport.symantec.com/docs/292587
 
  -  Exchange 2007 VSS support
     This release update supports Snapshot Client backups of Exchange 2007.
     This includes off-host backups and the selection of the VSS provider, as
     with Exchange 2003 in previous versions of NetBackup. To successfully
     perform backups using the VSS method, you must apply two hotfixes.

     -  For Exchange 2003 and Exchange 2007 You must apply the following
        SFW 5.0 hotfix on all systems where a Snapshot Client backup occurs.
        The hotfix can be obtained by calling Symantec Support. This hotfix
        is also included in the SFW/SFW-HA 5.0 MP1 release. See the following
        TechNote for more information.
           http://entsupport.symantec.com/docs/287298

     -  If you have Exchange 2007 and VxVM 5.0 and use the VSS off-host method,
        you must also apply the following hotfix.
           http://entsupport.symantec.com/docs/292544

  -  With Exchange 2007, NetBackup 6.5.1 supports the redirection of a VSS
     backup image to a recovery storage group (RSG) or another alternate
     storage group.  As of NetBackup 6.5.1, you can only redirect the restore
     of an entire storage group (including the RSG) if it contains only one
     database.

     For more information on this type of restore, see the TechNote Continued
     support for Microsoft Exchange 2007.
        http://entsupport.symantec.com/docs/292587

  -  This release allows for off-host snapshot backups of uncommitted logs only.

  -  Support for Exchange 2007 in Veritas Cluster Server (VCS) environments.
     A patch is required. See the following TechNote for more information:
        http://entsupport.symantec.com/docs/288625

  -  In a future release the Exchange agent will support instant recovery for
     Exchange 2003 and later. This feature enables the recovery of storage
     groups and databases from a snapshot. These snapshots can also be staged
     to tape.

+  The release includes a new NetBackup for VMware that provides backup and
  restore of VMware virtual machines that run on VMware ESX servers. NetBackup
  for VMware uses the VMware Consolidated Backup (VCB) framework.

  NetBackup for VMware can back up and restore individual files or the full
  virtual machine. Also supports individual file restore from full Windows
  virtual machine backups, by means of FlashBackup-Windows.

  For additional information about this feature, see the following TechNote
  on the Symantec Support Web site.
     http://entsupport.symantec.com/docs/293350

+  The following enhancement was made to NetBackup Windows FlashBackup.

  NetBackup Windows FlashBackup uses VxMS for backup (mapping) and restore of
  NTFS files.  A change was made to provide a new VxMS build that supports the
  direct retrieval of security descriptors from the NTFS Security Descriptor
  database in VxMS.

+  This release adds coexistence support for clients that are utilize
  EMC Powerpath devices.  Bare Metal Restore will not re-create or restore
  volumes or file systems that reside on EMC Powerpath devices. The following
  is a summary of expected behavior when backing up and restoring
  EMC Powerpath clients with Bare Metal Restore:

  -  During backup, the configuration that is imported will have all
     references to EMC Powerpath pseudo-device names removed and replaced
     with the first active physical disk in the EMC Powerpath configuration.

  -  The physical disk(s) chosen to represent the EMC Powerpath configuration
     will be "Restricted" from restoration.

  -  The physical disk(s) chosen to represent the EMC Powerpath configuration
     will not be allowed to be unrestricted during Dissimilar System
     Restore (DSR) mapping operations.

  -  The filesystems, volumes and volume groups (if applicable) originally
     resident on EMC Powerpath devices can be mapped to non-EMC Powerpath
     devices for restoration.

  -  Resources (disk groups and volume groups) originally configured on
     EMC Powerpath devices will not automatically be imported and may not be
     available in the post-restore environment. Depending on the operating
     system and volume manager in use will determine whether the resource is
     automatically available after restoration has completed.  If the resource
     is not available, it will need to be either imported by hand or made
     available via the external procedure feature of BMR if automation is
     desired.

  This enhancement has been provided on all UNIX and Linux platforms which
  NetBackup currently supports.  Support for EMC Powerpath on Windows platforms
  is planned for a future release.

+  Additional error codes have been created for a NetBackup SharedDisk. For
  detailed information about these errors codes, refer to the following
  TechNote on the Symantec Support Web site.
     http://entsupport.symantec.com/docs/288177

+  Symantec will no longer support TSH robots in the next major release of
  NetBackup.



-------------------------
End-of-Life Notifications
-------------------------
+  The following is a list of platforms that will no longer be supported at
  the next major release of NetBackup.
  - Solaris 9 master and media server
  - HP-UX PA-RISC master server (Support will continue for an HP-UX PA-RISC
    client and the media server.)
  - Windows 2000 client
    - Exchange 5.x and Exchange 2000
    - SharePoint 2001

+  SharedDisk EOL - A decision has been made to EOL SharedDisk.

  SharedDisk was proven to be exceptionally sensitive to disk firmware and
  Operating S changes. These dependencies prevented it from being widely
  adopted and too difficult to proliferate.

  NetBackup 6.5.4 will be the last version of NetBackup that includes the
  SharedDisk product. SharedDisk will be unavailable in NetBackup 7.0.

  The End-of-Support Life (EOSL) for NetBackup 6.x is October 3, 2012. This date
  represents the end of partial support. The End-of-Standard Support (EOSS) is
  30 months after the GA date of the next major release of NetBackup.

  Customers who had planned to use SharedDisk should consider the following
  alternatives:

     * PureDisk Deduplication Option
     * OpenStorage
     * AdvancedDisk with standalone disk or NFS
     * AdvancedDisk with Veritas Storage Foundation CFS

  If you have any questions about SharedDisk EOL, please contact Paul Sustman
  or Alex Davies directly.


+  NetApp SnapVault for NetBackup EOL - NetApp recently announced EOL of
  SnapVault for NetBackup.

  This announcement, affects NetBackup customers using this joint solution.
  NetBackup 6.5.4 is the last version of NetBackup that includes the support
  for NetApp SnapVault for NetBackup product (internally referenced as "P3").
  NetApp SnapVault for NetBackup will not be available in NetBackup 7.0.

  The NetBackup EOSL for NetBackup 6.x is October 3, 2012. This date represents
  the end of partial support. The EOSS is 30 months after the GA date of the
  next major release of NetBackup.

  Because NetApp is not offering a migration path, NetBackup customers who use
  NetApp storage and who use NetApp SnapVault for NetBackup should consider the
  following alternatives:

     * VTL
     * OpenStorage
     * AdvancedDisk with standalone disk or NFS

  The EOSL notice from NetApp to a mutual NetApp SnapVault for NetBackup
  customer is included below:

  For your information and planning, this notice is meant to inform you about
  changes that affect the availability and support of the NetApp SnapVault for
  NetBackup solution jointly developed with Symantec Corporation.

  SnapVault for NetBackup is a storage-optimized solution that was developed by
  NetApp and Symantec in a joint effort to protect NetBackup clients using
  SnapVault.

  The NetApp SnapVault for NetBackup solution will not be offered or supported
  for use with the next major release of Data ONTAP. All existing customers
  that use SnapVault for NetBackup with either Data ONTAP 7.2.x or 7.3.x will
  continue to be supported by NetApp.

  Symantec will continue to support the solution as long as NetBackup 6.5.x is
  supported. The contents of SnapVault destination volumes that contain
  NetBackup client backups will not be available for backup, restore, or image
  management tasks if used with the next major release of Data ONTAP.

  Field sales and channel partners should inform and prepare all SnapVault for
  NetBackup customers who might be affected by the end of availability outlined
  in this bulletin. In particular, the field and partners need to understand
  and communicate the NetApp support policy for support.

  There is no migration path for SnapVault for NetBackup. Please contact your
  NetApp sales or channel partner representative for assistance in
  transitioning to an alternative solution.

  Service and Support

  Please note that although we are announcing the end of availability of this
  product, NetApp will continue to support it for a limited time. NetApp will
  continue to provide software support for SnapVault for NetBackup per standard
  support policies as described in this bulletin.

  SnapVault for NetBackup will continue to be supported for five years from end
  of availability or until December 1, 2013. NetApp will continue to develop
  and provide bug fixes per NetApp support policies. NetApp will continue to
  support the software in this limited manner until the expiration of the
  five-year end-of-support period.

  If you would like to receive technical assistance for this release or any
  other NetApp product, download software, manage your service contracts, view
  your open cases, open an RMA and more, go to the NOW site at NOW End of
  Availability Site.




============================
III.  NETBACKUP KNOWN ISSUES
============================
This section contains a list of known issues with this Release Update. These
issues will likely be fixed in future Release Updates for this version of
NetBackup. The issues below have been separated in to general groups to make
it easier for you to find the area that interests you most.

- Platform-specific issues
- Installation, upgrade, and cluster issues
- NetBackup Access Control issues
- NetBackup Database Agent issues
- Storage-related issues
- NetBackup user interface issues
- General NetBackup issues
- General Documentation issues


Platform-specific issues:
-------------------------
+  NetBackup could fail on systems running AIX and an older versions of the
  C++ run-time libraries. IBM has released xlC rte 9.0.0.3 C++ Runtime
  Environment Components for AIX. Symantec recommends that you download and
  install the latest C++ run-time library and then reboot your server. For
  more information about this issue and fix, refer to the following TechNote
  on the Symantec Support Web site.

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

+  NetBackup 6.5.4 contains three files (NBCC.exe, NBCCR.exe, nbsu.exe) that
  have invalid digital signatures. These signatures will be corrected in the
  next release of NetBackup.

+  (ET1258372) For Solaris 10 clients using the NAS_Snapshot snapshot method,
  if backup target filesystems are not mounted explicitly as NFS version 3, the
  snapshot directory on the filer volume will not be accessible through NFS as
  required to support snapshot restore. This may result in failed backups, or
  backups that appear to succeed, but are immediately expired during routine
  snapshot image validation. For Solaris 10 clients, filesystem mount commands
  should contain the following option:
       -o vers=3
  For example:
       mount -F nfs -o vers=3 file1:/vol/vol2 /mnt

+  Cannot install NetBackup 6.5.2 to a Macintosh computer running
  Mac OS X 10.5 (Leopard).  This issue affects PowerPC- and Intel-based
  machines with Mac OS X 10.5.

  NetBackup 6.5.2 is a patch release that is meant to upgrade an existing
  6.5.x installation. Attempting to locally install NetBackup 6.5 on a client
  running Mac OS X 10.5 will fail.  For more information about this issue and
  how to work-around it, refer to the following TechNote on the Symantec
  Support Web site.
      http://entsupport.symantec.com/docs/302495

+  (ET1150283) The HP-UX 11.11 patch PHSS_33037 introduced a defect that can
  cause applications to fail at start time. (Please see the HP patch
  description for PHSS_33037). This defect can cause the Oracle and DB2
  NetBackup agents to fail while executing calls to dlopen.

  Users who are affected by this defect should back out of the patch, or
  install the later patch PHSS_35379.



Installation, upgrade, and cluster issues:
------------------------------------------
+  (ET1595854) When you uninstall NetBackup from a VCS cluster, the VCS Type is
  not deleted. If you reinstall NetBackup to the same location, you are not
  able to run NetBackup.

  To avoid this problem, use the following procedure to uninstall NetBackup
  from a VCS cluster.

    Note: Step 1 applies only to UNIX systems. Steps 2-9 apply to UNIX and
          Windows systems.

  To uninstall NetBackup from a VCS cluster:
  1) If it exists, on UNIX systems, remove the following file from the active
       node: /usr/openv/netbackup/bin/cluster/frozen
  2) Enter the following command to take the NetBackup resource offline:
       hares -offline <resource name> -sys <active node>
  3) After ensuring that all NetBackup processes and services are down, delete
       all NetBackup data from the shared disk.
  4) Enter the following command to take the NetBackup group offline:
       hagrp -offline <group name> -sys <active node>
  5) Enter the following command to change the VCS configuration to R/W mode:
       haconf -makerw
  6) Enter the following command to delete the NetBackup group:
       hagrp -delete <group name>
  7) Enter the following command to delete the NetBackup resource type:
       hatype -delete NetBackup
  8) Enter the following command to change the VCS configuration back to R/O
     mode:
       haconf -dump -makero
  9) Uninstall NetBackup from all other nodes in the cluster.

+  The Veritas Private Branch Exchange (PBX) software is installed along with
  Veritas NetBackup 6.5.x  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

+  (ET1602744/ET1602745) Unable to configure AT after an upgrade to 4.3.42.0.

  After upgrading VRTSat to a newer version, an attempt to reconfigure VxAT
  using the /opt/VRTS/install/installat -configure command failed.

  Workaround:
  To resolve this issue, remove "/opt/VRTS/bin/installat" and try to reconfigure
  VxAT again using <Location of ICSInstaller>/authentication/installat.

+  (ET1633604) VRTSpbx is not patched with the newer version included in
  NetBackup 6.5.4 package

  After installing SF 5.0MP3 and NetBackup 6.5 on a NetBackup master and mdeia
  server, and then upgrading to NetBackup 6.5.4, the VRTSpbx version may not
  update to the version packaged with 6.5.4.

+  (ET1597077) Receive a different VRTSpbx version by using different commands.

  It is possible for the the NetBackup patch installation to fail if the
  Storage Foundation (SF) 5.0MP3 is installed before NetBackup 6.5 followed by
  6.5.4 if the SF 5.0MP3 VRTSpbx version is newer than the VRTSpbx version that
  is packaged with NetBackup 6.5.4.

+  (ET1257102) Before you attempt to install a NetBackup Master Server on a
  Tru64 system the following things must be present on the Tru64 system:
     1. Install the latest Internationalization (I18N) patch
     2. Shared Memory Size greater than 60MB.

  If these two criteria are not met then basic Backups fail with a status 230
  and status 89 error, respectively.

+  (ET1269244) When attempting an upgrade, if Fibre Transport clients or servers
  are discovered in the database, make sure that the appropriate services are
  running to avoid potential issues that could cause the upgrade to fail.  Use
  nbftconfig -ls and nbftconfig -lc to determine if Fibre Transport clients or
  servers are present.

+  On a media server (stand-alone or clustered), if the media server system
  is shutdown or a failover occurs while the media server is involved in a
  restore operation, further restore operations involving this media server
  will not function. For more information about this issue, refer to the
  following TechNote on the Symantec Support Web site.
      http://entsupport.symantec.com/docs/303970

+  (ET1116304) To view log messages generated by PBX exchange, use the vxlogview
  utility installed by the VRTSicsco package only. Typically, the VRTSicsco
  package is installed at "/opt/VRTSicsco" on UNIX systems and
  "<CommonProgramFiles>\VERITAS\VRTSicsco" on Windows systems.  It is not
  recommended to use the vxlogview utility that is installed by any other
  package because it may give errors due to a version/architecture mismatch.

+  (ET1380306) The initial PBX install or version upgrade,
  "NetBackup 6.5 ICS 1.4.37.9 for HP", failed to install or upgrade during a
  NetBackup install.  It would fail with the following error.

     The platform type of installics (ICS-HPUX-11.00 CS-HPUX-11.23) does not
     match the platform type of this machine (ICS-HPUX-11.00).

  To resolve this issue, a fix was made to a new PBX install or version upgrade,
  titled, "NetBackup 6.5 ICS 1.4.37.9a for HP".  Note the 'a' in the image name.
  The new image is easily denoted by the existence of the ./platform.txt.old
  file.

+  (ET1600692) While installing NetBackup in a cluster and making it Highly
  Available (HA), if you provide a fully qualified host name (FQHN) when
  asked for Virtual name, problems may occur and HA is not successful. You
  should not provide a fully qualified name during the configuration.  The
  NetBackup High Availability Administrator's Guide for UNIX, Windows, and
  Linux will be changed at the next major release of NetBackup to reflect
  this known issue.

+  (ET1651766) If you have upgraded NetBackup 6.5 to NetBackup 6.5.4 on an
  x86 system running Red Hat Enterprise Linux ES release 4, please shut down
  all of the running NetBackup processes before you attempt to uninstall.
  Otherwise it can cause an unclean uninstallation which can result in
  uncertain NetBackup behavior.  

+  (ET1299390) When the IP resource for a VCS cluster (or any other cluster
  technology) fails (or goes down unexpectedly), the NetBackup agent is
  incapable of determining the state of the master server. This leads the VCS
  server to believe that all NetBackup services are down when in reality they
  are up.

  To avoid this issue, perform the following workaround.
  1) Use the cluster technology specific command to offline the NetBackup
     resource group.
  2) Ensure that the NetBackup services are down on all of the nodes in the
     cluster. You can use the bp.kill_all command to shutdown NetBackup on all
     of the inactive nodes.
  3) Bring the NetBackup cluster resource group back online.



NetBackup Access Control issues:
--------------------------------
+  (ET1249781) Recovering NetBackup access management components

   If you have configured NetBackup Access Control (NBAC), your authentication
   and authorization configuration information is automatically backed up by
   the online, hot catalog backup.

   Both the Operate and Configure permission sets are required on the catalog
   object in order to successfully backup and recover NBAC authentication and
   authorization data.

   Perform the following procedure to recover the NetBackup catalog from an
   online catalog backup when NetBackup Access Control is configured:
   1. Ensure that NetBackup Access Management Control is installed, but
      disabled prior to running the actual catalog recovery wizard or bprecover
      command. You must have root privileges to execute the recovery.
   2. Shut down the authentication and authorization services/daemons.
   3. Recover the NetBackup catalog from the online catalog backup using the
      recovery wizard or bprecover command. Authentication and authorization
      data will not be copied back to the hosts from which it was backed up;
      instead, it will be copied to a staging area for use in step 4.
   4. Run "bprecover -r -vxss -p <policy name>, supplying the name of the
      online catalog backup policy. This will recover authentication and
      authorization data from the staging area to the hosts from which it was
      backed up.
   5. Start up the authentication and authorization services/daemons.
   6. Configure NetBackup to use NetBackup Access Management Control, by
      setting up the proper Access Control host properties for master
      server(s), media server(s), and client(s).
   7. Restart NetBackup.

+  (ET1137932) To do NetBackup restores as a non-administrative user under NBAC
  using the Windows Backup, Archive, and Restore client console or the Windows
  Administration Console, the permissions on the following directories need to
  be set to "Full Control" for each user of the user interfaces.  
     C:\ProgramFiles\Veritas\NetBackup\logs\nbwin
     C:\ProgramFiles\Veritas\NetBackup\logs\nbconsole

+  (ET1030850 ET1145680)  An issue exists for AIX platforms running a mixed
  NetBackup Access Control (NBAC) environment where NBAC is installed and
  enabled on some but not all hosts.  In this type of environment, USE_VXSS is
  set to AUTOMATIC.  There is an AIX compiler issue that causes a core dump to
  occur in a library routine.  You may observe core dumps in NetBackup daemon
  processes due to this issue.  A side effect to this issue may be that you are
  not able to log into the NetBackup-Java Administration Console after enabling
  NBAC.

+  (ET1274335) Applicability: Cluster NetBackup with NBAC (Clustered VxAT)

  A Hot Catalog backup of clustered NetBackup with NBAC (Clustered VxAT) does
  not protect VxAT data stores correctly. Attempting to recovery VxSS data
  using the command, bprecover -r -vxss -p <PolicyName> fails to recover the
  VxSS environment.

+  Configuring NOM and VxAT on the same cluster is not supported on VCS Windows.



NetBackup Database Agent issues:
--------------------------------

+  The following items pertain to the new Exchange Granular Recovery feature
  for this release.

  - A Microsoft hot fix is required for "Client for NFS" for windows 2003. You
    can locate and request this hot fix for either x86 or x64 platforms at:
    http://support.microsoft.com/kb/947186

  - A status 1 error may occur for an Exchange Granular-enabled backup job if
    the granular processing operations failed to complete successfully. The
    job details under the Activity Monitor or error log should indicate if this
    failure is what caused the status 1.
      - Look at the bpbkar debug log for more information
      - A legacy (non VSS) backup will still truncate transaction logs if the
        job ended with a status 1 because of a granular processing operation
        failure. In this situation, the backup image is suitable for database
        recovery.

  - The Qlogic San Surfer software may need to be disabled or un-installed
    because it may conflict with the port mapped for Windows "client for NFS".

  - Windows 2008 is also supported for Exchange 2007 granular backups.

      - The installation of the client for NFS is different than what is listed
        in the NetBackup 6.5.3 documentation update.  To enable Service for NFS
        on Windows 2008, add the "Services for Network File System" role under
        File Services within the Windows Server Manager.  Confirm the
        "Client for NFS" has started successfully.

      - The 8022.0 or higher version of "Microsoft Exchange Server MAPI Client
        and Collaboration Data Object 1.2.1" is required on the Exchange server
        for granular recoveries or mailbox level backups to function properly.
        This can be downloaded from the following web site.

        http://www.microsoft.com/downloads/details.aspx?familyid=E17E7F31-079A-
           43A9-BFF2-0A110307611E&displaylang=en

+  If pre-NetBackup 6.5.3 version is being used to backup granular backups for
  SharePoint and its media servers are upgraded to 6.5.3, then the SharePoint
  clients will also need to be upgraded to 6.5.3.

+  The following list of issues applies to Microsoft Exchange.
  -  Launching an off-host snapshot backup from the NetBackup Client or with
     bpbackup

     If you attempt to initiate an Exchange off-host alternate client backup
     from the NetBackup Client GUI or with the bpbackup command, the backup
     fails. Instead, use the NetBackup Administration Console to initiate a
     manual backup for that Exchange policy. See the "Testing configuration
     settings" section in the NetBackup for Microsoft Exchange Administrator's
     Guide for instructions on how to perform a manual backup.

  -  When an Exchange backup is launched from the NetBackup Client interface
     and uses the Snapshot Client offhost backup capability, the progress log
     window does not display the usual progress messages evident when a
     scheduled backup is executed. The backup operation is not impacted by this
     lack of progress logging. If detailed progress is desired, use the
     NetBackup Administration Console to launch a manual backup operation on an
     Exchange policy. See the "Testing configuration settings" section in the
     NetBackup for Microsoft Exchange Administrator's Guide for instructions on
     how to perform a manual backup operation.

+  (ET1527929) Backups of SharePoint Web applications or portals that use
  Granular Recovery Technology (GRT) and that contain a larger number of
  content databases (100+) may timeout. In this situation, increase the default
  "Client read timeout" setting to 900 seconds.

+  For NetBackup 6.5.4, the following configuration changes apply for Exchange
  cluster environments:
  -  To perform Continuous Cluster Replication (CCR) backups of the passive VSS
     writer, you no longer need to set the "Enable Remote Streaming Backup"
     registration key.
  -  For Exchange 2007 SP1 or later, you no longer need to configure the
     NetBackup Client Service to run as domain admin.

+  NetBackup for SQL Server
  If you peform a backup using multiple streams (stripes) and multiplexing, you
  cannot restore this backup image using more than one stripe.



Storage-related issues:
-----------------------
+  (ET1653458) When attempting multi-copy duplications in a clustered
  environment, duplications can fail with a status 254 if you have any
  storage units configured to use any available media server.

+  **(ET1652704) A potential for data loss was discovered in NetBackup
  Server / Enterprise Server when using Storage LifeCycle Policies (SLP).
  Duplication jobs that start writing data, but continue to fail past the
  expiration time of the source copy may never get retried, leading to skipped
  duplications or missing backup copies.  If this occurs, the activity monitor
  will display the failed duplication jobs, but there is no other indication
  that these duplications were missed.

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

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

+  (ET1634241) Network optimized duplication may not perform as expected.
  Under the following circumstances, NetBackup may not always use a common
  media server if one is available:

  - The list of source images specified for a duplication job reside on more
    than one disk or tape volume, other than cases where images from the first
    volume used for the image list span to subsequent volumes.
 
  - A required common server for duplication is configured (the
    "nbemmcmd -common_server_for_dup required" option).

  After NetBackup duplicates all of the images from the first media ID,
  NetBackup performs as expected if the remaining images span from the first
  media ID to the other volumes.  However, if the images do not span from the
  first media ID, NetBackup may use a different media server to read the
  remaining images.

  This situation may occur with image lists created by Storage Lifecycles.

+  (ET1538745) Destinations within a storage lifecycle policy may be backup
  destinations or duplication destinations.

  Duplication destinations can be configured to indicate an alternate read
  server. The alternate read server can read a backup image that was originally
  written by a different media server.

  Each destination belongs to a particular disk pool. The alternate read server
  indicated for a duplication destination in the same storage lifecycle policy
  must be a server for the disk pool of the source backup destination.  Disk
  pools are listed under Media and Device Management > Devices > Disk Pools.

+  (ET1518794) Editing an SLP that has images in process can have adverse
  affects.  Two workarounds exist:
  a. Disable backup policies that use the SLP.  Wait until all images that are
     being managed by the SLP are "Lifecycle complete". Edit the SLP. Enable
     the backup policies that use the SLP.

  b. If you can not afford to disable the backup polices as described in a.
     above, then leave them active, but edit the policies to use a different
     SLP: Rather than changing the existing SLP, create a new SLP with the
     changes you want.  Then edit the backup policies that are configured to
     use the active SLP to replace the reference to the "old" SLP with the new
     SLP.  Do not delete the old SLP until all of the images it is processing
     are "Lifecycle complete".  Please refer to Tech Alert 323746 on the
     Symantec Support Web site.

     A fix is currently underway for this issue.  Symantec expects to make
     the fixes available in a post-6.5.4 package as soon as possible.

+  (ET1543025) Both types of backup staging methods make use of capacity
  management on disk storage units. This means that NetBackup automatically
  removes expired images from the storage unit to create space for new images.

  In either situation, NetBackup cannot manage the capacity of a storage unit
  that is NFS-mounted:
  - For basic disk staging:
    The disk staging storage unit is capacity-managed by default. Do not make a
    DSSU out of a storage unit that is NFS-mounted. (That is, do not select the
    Enable Temporary Staging Area option for that storage unit.)
  - For storage lifecycle policies:
    A destination can be configured to be capacity-managed.  Do not enable the
    Staged Capacity Managed option for any destination that is NFS-mounted.

+  (ET1485775) OpenStorage direct to tape lets you copy NetBackup backup images
  from a disk appliance to tape drives that are attached to an NDMP host.

  For more information, see the 6.5.4 version of the NetBackup Shared Storage
  Guide contained in the following TechNote on the Symantec Support Web site.

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

  Note: The license key that activates OpenStorage must be installed on each
        NetBackup media server that you use for direct to tape.

+  (ET1543384) Backups to disk my fail with status code 800

  During heavy NetBackup media server activity, backups to disk may fail with
  a NetBackup status code of 800.  The code appears in the Administration
  Console Activity Monitor Job Details display.

  See the NetBackup Troubleshooting Guide description of NetBackup status
  code 880 for remedial action.

  Jobs may fail because the heavy load causes processes to wait longer than
  the default timeout period (60 seconds).  You can try to increase the
  timeout by creating the following file on the media server:

  UNIX: /usr/openv/netbackup/db/config/DPS_PROXYDEFAULTRECVTMO
  Windows: C:\Program Files\VERITAS\NetBackup\db\config\DPS_PROXYDEFAULTRECVTMO

  If the config directory does not exist, create it.

  The file should contain the new timeout value, greater than or equal to 10 or
  less than or equal to 3600 seconds.

+  The SAN Client does not support inline tape copy over Fibre Transport. Inline
  tape copy jobs occur over the LAN.  SAN Client is designed for very high
  speed backup and restore.  Therefore, SAN Client excludes backup options
  (such as inline tape copy) that require more resources to process and manage.

+  A button labeled New has been added to the Add Disk Array Host dialog box,
  as well as a new dialog box titled, New Array Type. When you click the
  New button the New Array Type dialog box appears. Included on this dialog
  box is a Help button. The online help for this dialog and button will be
  available at the next major release.

+  The NetBackup SharedDisk option does not support Windows 2008 for media
  servers.

+  (ET1516498) Images with a very large number of fragments (greater than
  12,000) can have adverse effects.
  (Note:  This issue pertains to the total number of fragments across all
          copies of a backup image.)

  The following configuration settings can be used to reduce the number of
  fragments:
  a. Make sure that the Maximum Fragment Size is not too small.
     -  A 1TB image with a Maximum Fragment Size of 20mb (with only one copy)
        would generate 50,000 fragments.  If a second copy was created, the
        image would have 100,000 fragments.
     -  Note:  Many users are configured with 20mb fragments, based on outdated
        TechNotes describing restore performance.  The limitation of restore
        performance has been resolved and these users should change this setting
        to allow larger fragments.
** b. The combination of checkpointing and multiplexing exacerbates this problem.
     Do not set checkpointing to a frequency less than 20 minutes.  Consider
     reducing the MPX factor.
     -  For example, checkpointing at five minutes with MPX at 8 causes
        96 fragments each hour.  If the client is slow and the backup runs for
        three days (this has been observed in the field), 6,912 fragments are
        created.  If the image is copied once,  a total of 13,824 fragments will
        exist.  A third copy results in a total of 20,736 fragments.  Please
        refer to Tech Alert 323748 on the Symantec Support Web site.

        A fix is currently underway for this issue.  Symantec expects to make
        the fixes available in a post-6.5.4 package as soon as possible.

+  (ET1444319) An issue exists in this Release Update where storage lifecycle
  policy (SLP) images that are no longer in the catalog still appear in the
  EMM image table list. These images are empty placeholder images and are
  created when multi-streamed backups occur. The nbstserv process detects
  these images in the EMM table list, processes them, and reports that it has
  removed them, when in fact they still appear in the image table list as not
  being processed by SLP.

+  The following list of issues applies to AdvancedDisk.
  -  Windows Common Internet File System (CIFS) is not supported.
  -  For NFS, you must use manual mount points.
  -  Symantec recommends that you do not span backup images across volumes in
     an AdvancedDisk disk pool. File system full conditions cannot be detected
     adequately. Therefore, each disk pool should be comprised of only one
     volume.

+  (ET1240562) NetBackup SharedDisk and Windows media servers

  If you use both NetBackup 6.5.2 and NetBackup 6.5 or 6.5.1 media servers
  (Windows) for SharedDisk, you must format LUNs using a 6.5 or 6.5.1 media
  server.  To avoid any LUN formatting issues, Symantec recommends that you
  upgrade all of the Windows media servers you use for SharedDisk to
  NetBackup 6.5.2.

+  (ET1128929) Potential free space is the amount of space on a disk staging
  storage unit (DSSU) or on a lifecycle policy destination that NetBackup can
  free if extra space on the volume is needed. (Use the nbdevquery command to
  display the potential_free_space and the free_space value.) The potential
  free space value represents the total size of the image copies that are
  eligible for expiration.

  To create free space, an administrator can run the bpexpdate command to
  manually expire eligible image copies on the volume. This changes the
  potential free space into available free space.

  If nbdevquery is run after bpexpdate is used, the potential free space value
  should be reduced and the free space value should be increased. However, this
  is not the case. The nbdevquery command does not display the correct
  potential free space value until one of the following updating events occurs:

  -  In the case of DSSUs: When the high water mark or a disk-full condition is
     reached on the storage unit. The automatic expiration of eligible copies
     of staged images occurs and potential_free_space for that disk is
     recalculated.

  -  For disk destinations within lifecycle policies: When a duplication job
     that writes to the disk completes, the potential_free_space value for that
     disk is recalculated.

  Suppose a copy of an image is beyond its try-to-keep date, and
  is a candidate for removal from disk.  For instance, this copy of the image
  is counted as a part of the Potential Free Space value.  If a user uses the
  bpexpdate command to manually expire this copy of the image from disk, the
  Potential Free Space value will not be decremented to reflect the action
  taken until the whole Potential Free Space value is recalculated.  Until the
  value is recalculated, the user and NetBackup will think that there is more
  available space on the disk than there actually is.

  The Potential Free Space value is recalculated:  
     a) When the High Water Mark (HWM) condition forces a draining of the disk
        down to Low Water Mark (LWM).
     b) When an image is fully duplicated, thus being "Lifecycle complete".  

  The "Available space" is Free Space plus Potential Free Space. The file
  system increments the Free Space, but NetBackup does not decrement the
  Potential Free Space. Thus, the size of the image that was expired is
  counted twice as both Free Space and Potential Free Space.  This is the
  reason why it will look to the user and NetBackup like the disk has more
  space than there actually is.  In addition, this may cause NetBackup to
  assign jobs to the disk that have a larger total estimated size than is
  actually available.

+  Dissimilar Disk Restore of a Solaris client fails if the client uses SVM
  metadevices (volumes) created using slice 2 of Solaris Disks. For more
  information on this issue, refer to the following TechNote on the Symantec
  Support Web site.

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

+  (ET1230073) A storage lifecycle policy can contain backup and duplication
  storage destinations. A duplication destination can be configured to have one
  of two retention types: Fixed or Capacity managed.

  When Capacity managed is selected, a Desired cache period is also configured.
  NetBackup tries to retain the image on the destination for the Desired cache
  period. Only if space is needed for new images are the capacity-managed copies
  to be expired.  However, testing has shown that for duplication destinations
  using the Capacity managed retention type, the Desired cache period is being
  overlooked.

  The overlooked desired cache period may allow images to become eligible for
  expiration as soon as all copies of the image have been created. The next time
  the disk reaches the high water mark, these copies may be deleted, regardless
  of the Desired cache period setting.

+  (ET1317594) To add clarity, the "Load balance" label in the Storage Unit
  Group dialog, has been changed to read, Media server load balancing.

+  (ET1239766) Some devices that have single-instance store (SIS) capabilities
  can be used as storage destinations in a storage lifecycle policy. (For
  example, PureDisk.)

  In this release, the Fixed and Capacity Managed retention types are available
  for selection for SIS devices used as duplication destinations. However, the
  Capacity Managed retention type actually behaves as a Fixed retention period
  for these devices.

  The log reflects this change in retention type behavior. In future releases,
  the Capacity Managed retention type will be available for SIS devices.



NetBackup user interface issues
(NetBackup Administration Console, command line interface, bp or bpadm, etc.)
-------------------------------------------------------------------------------
+  There is a difference in the user experience, between the MFC user interface
  and the NetBackup-Java Administration Console, when browsing granular backups
  for restores. This happens with granular backups from Microsoft Exchange,
  Microsoft SharePoint, or Microsoft Active Directory. The difference occurs
  when clicking on a granular node to expand the node and view its contents.
  Since there is a noticeable delay and overhead in expanding a granular node,
  the MFC user interface expands more than was being requested to attempt to
  minimize this delay.  The NetBackup-Java Administration Console does not do
  this. This requires the NetBackup-Java Console user to make additional node
  expansion clicks and causes an additional delay.

+  (ET1668436) Closing the NetBackup-Java Administration console does not
  terminate the NBSL session. It can cause the NBPROXY processes to run for
  the next 24 hours and eventually time out.  In addition, if you frequently
  start and stop the NetBackup-Java Administration console, the number of
  running NBPROXY processes increases the load on the respective NetBackup
  Master Server and eventually affects the performance of the Master Server.

  For more information and a work-around for this issue, refer to the
  following TechNote on the Symantec Support Web site:

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

+ (ET1517333) To back up all local drives, Symantec recommends that you use a
 scheduled backup from the master server. This method is much faster than
 performing a user-directed backup of all local drives from the client in
 Backup, Archive, and Restore.

+ (ET1401927) The Catalog Recovery wizard does not work after performing a
 change server operation. The operator must log on to the machine locally to
 recover the catalog.

+  The NetBackup Administration Console for Windows is not supported on
  Windows 2008 for the AMD64 platform. If a user attempts to launch the
  NetBackup Administration Console, it will cause the following error message.

    The NetBackup Administration Console cannot be started. The Windows-based
    NetBackup Administration Console is not supported on this platform.

+  (ET1231347) As a result of a security fix to handle characters like "<",
  ">", and ";", a user could issue UNIX commands without being a root user.
  Because the NetBackup-Java Administration Console uses the command line
  interface (CLI) to create policies, these characters cannot be allowed as
  text entries in policies. The security fix cannot be removed. Therefore,
  to work around this issue, the user should use a Java Administration
  Console that is running on a Windows workstation to create policies for
  MSEO. This issue will be fixed in a future release of NetBackup 6.5.

+  (ET1268670) A user cannot change the NDMP hosts in the Device Configuration
  wizard using the NetBackup-Java Administration Console.

  If you are on the NetBackup-Java Administration Console, you can work around
  this issue by performing the following steps.
    1.  Expand the Credentials within the left pane of the NetBackup-Java
        Administration Console.
    2.  Select NDMP Hosts.
    3.  Select the NDMP host that you want to change.
    4.  Right click the NDMP host and select "Change" from the drop-down menu.
        The Change NDMP Host window appears.

  If you want to use the command-line, you can work around this issue by
  performing the following command.
     /volmgr/bin  tpconfig -update -default_user_id <user ID>

+  (ET1367769) When using the nbdevconfig command from the command line
  interface it is important to remember to separate the server names with white
  space and not any other character such as a comma.  The NetBackup Commands
  document will be updated to include an additional sentence and possibly an
  example that demonstrates how this command is designed to be used.  

+  (ET1395328)  When using the bp or bpadm interface on HP-UX 11.23 or 11.31
  systems on Integrity (IA-64) architecture, a DATE ERROR will be returned
  during attempts to change dates. For more information about this issue,
  refer to the following TechNote on the Symantec Support Web site.
       http://entsupport.symantec.com/docs/308809



General NetBackup issues:
-------------------------
+  (ET1136915) NetBackup recognizes wildcard character usage in some areas,
  such as in backup selection lists and exclude file lists.  Curly brackets
  or braces) can be used around multiple wildcard file name patterns, as
  described in the Administrator's Guide.

  However, since curly bracket characters are valid characters for Windows
  file names, they cannot be used to indicate wildcard usage for Windows
  platforms.  Also, backslashes cannot be used as escape characters for
  curly bracket characters.

+  (ET1636600) Backup problem with MS-Windows-NT policy type and VMware ESX
  version 3.0 and 3.0.1

  Symantec has identified a problem when backing up a NetBackup client that
  is installed in a Windows guest operating system on certain versions of
  VMware ESX servers. If you select the "MS-Windows-NT" policy type, and the
  ESX server is at version 3.0 or 3.0.1, the backup job hangs.

  This problem is apparently due to an issue in ESX server versions 3.0 or
  3.0.1, not in NetBackup.

  Potential workarounds are the following:

  - Update your ESX server to 3.0.2 or later.
  - Or, configure a VMware backup proxy server and use NetBackup for VMware
    to perform the backup. For assistance with NetBackup for VMware, see the
    "NetBackup for VMware Administrator's Guide."

+  (ET1586456) The NetBackup server requires logon credentials to access the
  VMware ESX servers or the VMware VirtualCenter. If the credentials you have
  entered are incorrect or do not work, the backup may fail with status
  code 156, "snapshot error encountered." In this case, you must verify
  whether the correct credentials were entered in NetBackup, and correct them
  as needed.

  1. In the NetBackup Administration Console, go to Media and Device
     Management > Credentials > Virtual Machine Servers.
  2. Double click on the credentials definition for the VMware server or
     VirtualCenter.
  3. When finished editing the credentials, select the "Validate Credentials"
     box in the dialog and click OK.

+  (ET1593098) Error message issued when trying to validate VMware credentials

  This NetBackup 6.5.4 release adds the ability to verify that the VMware
  credentials you have entered in the NetBackup policy are valid for the VMware
  server. The NetBackup Add Virtual Machine Server dialog now contains a
  "Validate Credentials" checkbox.

  Note: If your VMware proxy server is running a version of NetBackup that is
        earlier than 6.5.4, the credentials cannot be validated and an error
        message is displayed. You must verify that the credentials you entered
        are correct for the VMware server. If the credentials are correct, you
        can ignore the error message.

+  (ET1556112) As part of the catalog policy configuration, the administrator
  indicates a path to the directory where the disaster recovery information
  is saved.  This path is indicated on the Disaster Recovery tab.

  The path for the disaster recovery information cannot be to a directory
  that is on the same partition as /usr/openv/netbackup.  If the path for
  the disaster recovery information is to a location on the same partition as
  /usr/openv/netbackup, NetBackup displays a status 20 error message.  The
  message states that the disk path is invalid.  The administrator needs to
  change the path on the Disaster Recovery tab to a directory on a different
  partition.

+  In rare situations the first backup attempt after NetBackup is installed
  may fail.  This only happens if the backup is granular and if Microsoft
  Volume Shadow copy Services (VSS) is being used.  In addition, after this
  one failure all subsequent backups succeed

+  (ET1535587) The media server used for catalog backups must be at the same
  level as the master server.  This is true for hot or cold catalog backups.

+  (ET1504682) The bpbackup command is used to perform user backups from clients
  and manual backups from master servers. In addition to listing individual
  files or directories, bpbackup can also use directives to indicate the files
  to be backed up. For example: bpbackup "/Shadow Copy Components/"
  bpbackup "/System State/"

  Clients can enter the directive in the listfile by using the following option:
     bpbackup -f <listfile>

+  (ET1536915) Do not save logs to a remote file system such as NFS or CIFS.
  Logs that are stored remotely and then grow large can cause critical
  performance issues.

+  (ET1539585) In this release, an administrator can resume a suspended job
  until the retention period of the job is met.  The retention period begins
  when the job is suspended. If the administrator resumes the job after the
  retention period passes, the job fails because the image has expired. The
  job is then moved to the DONE state.

  Note that the Clean-up host property, "Move backup job from incomplete
  state to done state," does not apply to suspended jobs. Jobs are suspended
  manually and must be resumed manually.

+  (ET1512562) Individual restore of mails from BE images is not supported in
  NetBackup 6.5.x as mentioned in the NetBackup online help. This issue will
  be addressed in the next major release of NetBackup.

+  (ET1260712) NetBackup considers the failure history of a policy when
  determining whether or not to run a scheduled backup job. The timeframe for
  NetBackup to examine is one of the settings configured using the Schedule
  Backup Attempts setting in the Global Attributes host properties.

  This property determines the following characteristics for each policy:
  - How many preceding hours NetBackup examine before determining whether to
    allow another backup attempt (retry). By default, NetBackup examines the
    past 12 hours.
  - How many times a backup can be retried within that timeframe.  By default,
    NetBackup allows two attempts.  Attempts include scheduled backups that
    start automatically or scheduled backups that are user-initiated.

  In NetBackup 6.0 and later, all backup attempts apply toward this
  configurable limit, regardless of the type of backup or the schedule. In
  releases prior to 6.0, NetBackup allowed each schedule to meet the Schedule
  Backup Attempts property limit.  In some cases this resulted in more backup
  attempts than expected based on the property setting.

  Consider the following 6.5 example scenario using the default setting:
  2 tries every 12 hours:

  1.  Policy_A runs at 6:00 p.m.; Schedule_1 fails.
  2.  Policy_A is user-initiated at 8:00 p.m.; Schedule_2 fails.
  3.  At 11:00 p.m., NetBackup looks at the previous 12 hours.  It sees one
      attempt at 6:00 p.m. and one attempt at 8:00 p.m.  The Schedule backup
      attempts setting of two has been met so NetBackup does not try again.
  4.  At 6:30 a.m. the next morning, NetBackup looks at the previous 12 hours.
      It sees only one attempt at 8:00 p.m.  The Schedule backup attempts
      setting of two has not been met so NetBackup tries again.  If a schedule
      window is not open at this time, NetBackup waits until a window is open.

+  (ET1260712) For master servers at NetBackup version 6.5 or later, the
  ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA setting in the bp.conf file has no
  effect.  To allow mixed retention levels on media, use the nbemmcmd command
  to update the nbemm database and change the
  ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA setting. The default configuration does
  not allow multiple versions (a setting of 0 or no).

  To allow multiple retention levels, use nbemmcmd -changesetting to change the
  ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA setting to 1 or yes.

+  (ET1364268) In 6.5.2 NetBackup introduced the ability to allow, restrict, or
  prohibit reverse host name lookup for master servers, media servers, and
  clients.

  Administrators can configure this using several methods:
  - By changing the Network Settings host properties in the Administration
    Console.
  - By editing the bp.conf file (UNIX) or the Windows Registry.
  - New in 6.5.4: By using the bpclntcmd command on UNIX or Windows systems.

  Using the bpclntcmd command:
  To display the current configuration setting, enter the command:
  bpclntcmd -reverse_name_lookup

  To change the entry, log on to the system as root or Administrator. Enter
  one of the following commands:

  - To allow reverse host name lookup (default), enter:
    bpclntcmd -reverse_name_lookup allowed

    This setting indicates that the host requires reverse host name lookup
    to be working in order to determine that the connection comes from a
    recognizable server.

  - To restrict reverse host name lookup, enter:
    bpclntcmd -reverse_name_lookup restricted

    This setting indicates that the NetBackup host first attempts to perform
    reverse host name lookup. If the NetBackup host successfully resolves the
    IP address of the connecting server to a host name (reverse lookup is
    successful), it compares the host name to the list of known server host
    names.

    If the resolution of the IP address to a host name fails (reverse lookup
    fails), based on the Restricted setting, the host converts the host names
    of the known server list to IP addresses (using a forward lookup). The
    host compares the IP address of the connecting server to the list of known
    server IP addresses.

    If the comparison fails, the host rejects the connection from server and
    the connection fails.

  - To prohibit reverse host name lookup enter
    bpclntcmd -reverse_name_lookup prohibited

    This setting indicates that the NetBackup host does not try reverse host
    name lookup at all. The host resolves the host names of the known server
    list to IP addresses using forward lookups.

    The NetBackup host then compares the IP address of the connecting server
    to the list of known server IP addresses.

    If the comparison fails, the NetBackup host rejects the connection from
    the server and the connection fails.

+  (ET1379837) An issue exists in this release update that can cause any
  supported version of HP-UX (PA-RISC) to encounter memory consumption issues
  with NetBackup processes. The degree of consumption will vary depending on a
  user's usage pattern. In addition, it is likely that the NBEMM process will
  be the first process to stop with a core dump. For more information about
  this issue, refer to the following TechNote on the Symantec Support Web site.

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

+  (ET1436810) Calendar incremental backups may not run on the same day as a
  calendar full backup as been scheduled.

+  (ET1199036 and ET1181074) Users may get a core dump of dbeng9 after
  performing a Full Catalog Backup Recovery. This is not a Symantec NetBackup
  issue. This core dump can be deleted and ignored. Testing showed that the
  catalog recovery completed successfully and that bprecover handled the core
  dump issue appropriately.

+  (ET1268670) In NetBackup 6.5.2, a user cannot change the NDMP hosts in Device
  Configuration wizard on the NetBackup-Java Administration console. You can use
  one of the following two workarounds to accomplish this task.

  Using the user interface:
  1.  Expand 'Credentials' within the left pane of the NetBackup-Java
         Administration console.
  2.  Select NDMP Hosts.
  3.  Select the NDMP host to change.
  4.  Right-click the NDMP host and select Change from the drop-down menu.
      The Change NDMP Host window appears.

  Using the command line:
  1.  Run /volmgr/bin  tpconfig -update -default_user_id <user ID>.

+  (ET1281808) Point-in-Time (PIT) is not supported in NetBackup 6.5.2 for
  IBM_DiskStorage_FlashCopy snapshot method.

  A Point-in-Time Rollback restore from an IBM_DiskStorage_FlashCopy snapshot
  backup fails on AIX platforms for backup resources built on AIX native stacks,
  for example, JFS2 file systems on AIX LVM volumes. The
  IBM_DiskStorage_FlashCopy snapshot method is supported on the IBM DS 6000
  series of Storage Arrays.

+  (ET1250126) To perform a Point-in-Time rollback restore for an IBM DS6000
  system, you must modify a VxFI configuration file for the Windows x64
  platform.  Perform the following steps to set up and change the
  configuration file:

  1.  Install IBM VSS 3.x
  2.  Install DSCLI 5.2.2.224 at a minimum.
  3.  Add the following lines to the end of %commonprogramfiles%\SymantecShared
      \VxFI\4\ConfigFiles\ibmtsfi.conf:
        [CLI_TOOL_INFO]
        "FILEPATH"="C:\Program Files (x86)\IBM\DSCLI\"
        (If DSCLI is installed to a different location, use that path in place
         of "C:\Program Files (x86)\IBM\DSCLI")

  You can find the following TechNote on this issue on the Symantec Support
  Web site.
      http://entsupport.symantec.com/docs/302962

+  (ET1245547) While running a report for tape reports > tape lists, if you
  have a volume name or media ID name that is less than six characters, then
  while using the command bpmedialist -ls -q -mlist -ev <volume/media name>
  -M <Master server>, the report operation will fail.  

  To resolve this issue and ensure that the report operations is successful,
  include the media ID in double quotes and add enough spaces within the quotes
  to make the media ID six characters long. For example, if you have the
  media ID "AB000" which is a five-character media ID, then you can use the
  command bpmedialist as follows:

     bpmedialist -ls -q -mlist -ev "AB000 " -M omwin1

  Since the length of the volume name is five characters, a space has been
  added, and the volume name is enclosed in double quotes. It is important that
  the media ID is in double quotes if spaces were added to make the ID six
  characters long.

+  VMware NetBackup Integration Module (VNIM) not required.

  The VMware NetBackup Integration Module (VNIM) is not required for NetBackup
  for VMware. In fact, NetBackup for VMware cannot function if VNIM is
  installed.

  NOTE: If VNIM is installed, you must uninstall it before running any backups.

+  (ET1250777) An alternate client off-host backup of a NetBackup RealTime
  application may fail with status code 156. This failure applies to a
  snapshot-based backup to a storage unit (with or without a retained snapshot
  for Instant Recovery). This error occurs if the RealTime server's host tables
  are not correctly updated for the alternate client. As a result, NetBackup
  cannot make a RealTime TimeImage accessible to the alternate client, and the
  backup fails.

  To resolve this problem, see the following NetBackup TechNote on the Symantec
  Support Web site:
     http://entsupport.symantec.com/docs/303966

+  The following items are corrections that will be made to the NetBackup 6.5
  Bare Metal Restore (BMR) Administrator's Guide at the next major release of
  NetBackup.

  In the Storage Area Network Support section of Chapter 6, Restoring Clients,
  the following text appears:

     Bare Metal Restore can restore a system that is attached to a Storage Area
     Network (SAN). On Windows, AIX, and Solaris systems, if the host bus
     adapter (HBA) drivers are available in the restore environment, BMR
     automatically restores the SAN-attached volumes. BMR does not support the
     restoration of systems with SAN attached volumes on HP-UX and Linux.

  The following text is the correct replacement text.

     Bare Metal Restore can restore a system that is attached to a Storage Area
     Network (SAN). If the host bus adapter (HBA) drivers are available in the
     restore environment then
     -  On Solaris 10, BMR automatically restores the SAN-attached boot and
        data volumes.
     -  On Solaris 8 and Solaris 9, BMR automatically restores the SAN-attached
        data volumes.
     -  On Windows, BMR automatically restores the SAN-attached data volumes.
     -  On AIX, BMR automatically restores the SAN-attached data volumes.
     -  On HP-UX and Linux, BMR does not support the restoration of systems
        with SAN attached volumes.

  In the Configuration Summary section of Chapter 10, Managing clients and
  configurations the following text should be added:

     Client configuration can be modified to add, change and remove a license
     key for software discovered for a protected system. The license key, which
     is added or changed, is also added to the protected system after restore
     using the configuration to which the key was added. This facility is
     available only for Veritas Storage Foundation products.

+  (ET1267896) When performing backups using the new Pure Deduplication
  Option (PDDO) feature, Symantec suggests that users monitor their shared
  memory usage as the number of jobs increases.  The job-size throttling has
  been turned off in NetBackup 6.5.2 to allow more PDDO backups to run
  concurrently.  Please consult your NetBackup Performance Tuning Guide for
  additional information on NetBackup tuning parameters affecting shared memory
  usage.

+  (ET1274002) The recovery of a catalog image taken in version 6.5.2 of
  NetBackup is NOT supported in an earlier version of NetBackup (such 6.5)
  or vice versa.

+  (ET1597920) Disaster recovery email and AdvancedDisk storage units
  If an online, hot catalog backup is directed to an AdvancedDisk storage unit
  and a catalog backup policy identifies a critical policy that has a backup
  image located on the same AdvancedDisk storage unit, the disaster recovery
  email does not list that critical policy.

  However, the policy is listed in the disaster recovery file.  You can open
  the DR file with a text editor to obtain that critical policy information
  (the media server and the media ID on which the policy's backup image
  resides).



General Documentation issues:
-----------------------------
+  (ET1197993) The 6.5 NetBackup Administrator's Guide, Volume I, incorrectly
  states that the Virtual Tape Option is necessary in order to create a NDMP
  storage unit.  This is incorrect.  The NetBackup for NDMP license must be
  installed on the media server in order to use a host as a NDMP storage unit.

+  The NetBackup Release Notes PDF that is available for download from the
  Symantec Support Web site has been updated with the following corrections.
  Users can download the latest version of this document at their convenience.

  -  SAN Client Platform Proliferations corrections

     -  Page 7: Original paragraph -
        The following client platforms support the SAN client: AIX, HP-UX,
        Linux, Solaris, and Windows, and the following media server platforms
        support the SAN client: Red Hat 4 update 3 Linux x86_64 and
        Solaris 9/10 SPARC. The SAN client will be supported in this release
        with disk storage. Support for tape storage may be added in a future
        release.

        Page 7:  Corrected paragraph for NetBackup 6.5.2 -
        The following client platforms support the SAN client: AIX, HP-UX,
        Linux, Solaris, and Windows, and the following media server platforms
        support the SAN client: RedHat 4 Update 3, RedHat 4 Update 5 and
        SLES 9 SP3 Linux x86_64 and Solaris 9/10 SPARC. The SAN client is
        supported in this release with disk storage. Support for tape storage
        may be added in a future release.

     -  Page 59, Table 2-19: Original paragraph -
        Media server     You can use the following systems for the NetBackup
                         media servers that host that are attached to the SAN:
                         -  Linux - RedHat 4.0 Update 3 X86_64 (EM64T or AMD64)
                         -  Solaris 9 and 10 (SPARC)

        Page 7:  59, Table 2-19: Corrected paragraph for NetBackup 6.5.2 -
        Media server     You can use the following systems for the NetBackup
                         media servers that host that are attached to the SAN:
                         -  Linux - RedHat 4 Update 3, RedHat 4 Update 5,
                            SLES 9 SP3 X86_64 (EM64T or AMD64)
                         -  Solaris 9 and 10 (SPARC)

  -  NetBackup PureDisk Deduplication Option Naming Correction
     The New Features chapter in the NetBackup 6.5 Release Notes document
     incorrectly refers to the PureDisk Deduplication Option as PureDisk Storage
     Option or PureDisk Optimization Option.  These names and the corresponding
     description have been corrected and a new updated version of the NetBackup
     Release Notes document that is available for download from the Symantec
     Support Web site.

+  The information about which policy types that support the client encryption
  option was not included in the NetBackup 6.5 Release Notes document.  The
  following list shows the policies types that support encryption in
  NetBackup 6.5.  This list will be updated and placed in the Release Notes
  document at the next major release of NetBackup.

  - AFS
  - DB2
  - DataStore
  - Informix-On-BAR
  - LOTUS_NOTES
  - Microsoft Exchange
  - Microsoft SharePoint
  - Microsoft SQL-Server
  - Microsoft Windows
  - Oracle
  - SAP
  - Standard
  - Sybase

  If you use one of the following policy types, you will not be able to select
  the encryption check box in the policy attributes interface.

  - DataTools-SQL-BackTrk
  - FlashBackup
  - FlashBackup-Windows
  - NDMP
  - NetWare
  - OS/2
  - Vault

+  (ET1268273) FlashBackup incremental backups do not operate as described in
  the NetBackup 6.5 Snapshot Client Administrator's Guide, page 82.

  The next revision of the Snapshot Client guide will contain information
  similar to the following:

  For FlashBackup and FlashBackup-Windows full policies, all blocks in the
  disk or raw partition (as selected in the Backup Selections tab) are backed
  up.

  For FlashBackup and FlashBackup-Windows incremental policies, complete files
  are backed up based on changes to the file Modified Time or Create Time
  since the last full or incremental backup.

  For FlashBackup-Windows Incremental policies, the Modified Time and Create
  Time changes are queried from the NTFS Master File Table (MFT) for File
  entries only (directories are skipped). Any newly created or modified files
  are backed up as complete files and corresponding directories up the tree are
  also backed up. Newly created but empty directories are not considered for
  FlashBackup-Windows incremental backups.

  Warning:
  During FlashBackup-Windows incremental backups, jobs will complete with
  status 0 but some skipped files may occur due to limitations with the NTFS
  file system.

  The NTFS Master File Table does not update the Create Time or Modified Time
  of a file or folder when the following changes are made:
  - File or directory rename operations
  - File or directory security changes
  - File or directory attribute changes (read only, hidden, system, archive bit)




================================
IV. CURRENT RELEASE UPDATE 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_6.5.4
--------
1285455 1247094 1266996 1274467 1271181 1266828 1267706 1240486 1275233 1291152
1260323 1251656 1254610 1248242 1290084 1281628 1264543 1277465 1267880 1065622
1298872 1286001 1278425 1298551 1266772 1295790 1321721 1151349 1276983 1274105
1286092 1302201 1253910 1246062 1316896 1234683 1282457 1315723 1141312 1235177
700722 1316030 1269701 1221450 1301941 1302903 1245767 1240580 1260009 1365476
1364370 1261359 1182949 1368000 1361179 1374137 1274771 1385956 1283409 1378098
1388949 1256040 1257567 1384505 1394294 1391201 1243760 1397770 1397803 1394464
1395191 1180431 1395095 1378871 1392357 1128777 1395388 1407095 1400851 1296897
1386091 1402016 1392368 1413113 1278561 1413313 1390861 1414077 1173100 1390505
1410798 1282150 1415947 1414211 1414312 1418051 1268084 1412901 1411499 1400002
1422476 1421893 1274472 1267027 1370671 1208654 1371578 1424207 1400376 1424291
1407021 1283922 1421724 1422599 1413001 1400717 1473485 1473486 1410178 1294340
1418524 1397773 1301030 1412924 1413063 1431018 1433273 1399857 1425305 1434146
1426057 1384805 1276634 1431894 1416846 1435119 1431758 1431826 1417844 1396173
1383748 1439607 1135673 1430950 1406219 1406213 1436844 1431015 1441498 1433052
1439252 1435489 1323857 1538553 1431527 1426014 1444551 1427600 1414674 1445493
1381806 1442063 1447058 1445648 1430034 1411788 1413618 1431088 1447265 1447160
1432407 1446408 1437425 1425084 1448195 1442239 1418373 1452416 1148446 1446653
1451465 1447260 1453529 1442301 1451023 1436594 1453605 1416785 1379510 1262599
1446468 1459294 1399839 1465331 1395101 1465033 1458226 1450234 1449178 1453422
1458420 1432148 1405180 1470340 1460964 1463890 1468581 1448206 1481250 1529072
1446401 1481284 1446147 1450564 1466528 1464016 1452281 1421534 1460587 1439971
1467900 1471621 1468877 1428325 1469444 1471613 1463937 1465258 1464015 1476600
1482673 1482676 1480286 1587338 1602790 1600654 1474403 1448396 1408851 1412268
1458872 1473860 1474475 1465728 1438645 1433497 1438822 1450268 1475313 1473499
1417504 1452344 1478495 1478915 1475161 1461116 1126065 1480041 1469706 1460837
1468318 1464701 1481159 1480280 1461993 1300129 1463877 1449955 1472234 1451817
1481404 1414922 1437385 1481373 1476107 1374989 1482914 1477935 1486988 1485005
1485946 1437453 1402322 1481348 1486168 1472633 1486686 1486807 1487580 1487510
1464678 1488267 1444236 1452950 1481714 1478999 1470973 1485977 1488734 1475372
1484302 1500272 1500484 1487577 1557578 1488525 1501040 1501855 1450415 1503555
1503554 1504217 1502059 1475402 1503097 1505138 1504987 1505661 1429723 1507290
1505203 1507663 1501647 1501118 1417539 1502104 1508567 1507033 1500451 1509112
1499426 1509107 1508224 1155347 1454759 1483007 1509370 1508901 1511217 1449853
1481224 1455436 1406992 1514843 1502251 1503674 1508943 1476060 1515064 1518716
1517830 1516611 1516658 1511966 1515378 1512269 1515674 1475595 1517091 1468310
1501973 1520790 1517775 1518415 1521609 1520660 1521319 1514161 1519049 1523991
1521072 1515697 1428897 1523771 1524262 1524495 1512307 1514813 1505895 1525307
1518751 1524391 1506156 1526402 1527601 1501039 1467372 1593966 1529861 1527862
1461913 1522273 1514334 1527768 1531249 1523443 1587409 1530121 1525375 1512052
1531929 1529030 1531907 1533986 1516985 1533817 1534963 1535794 1535780 1536441
1529377 1535663 1539736 1536918 1537820 1541722 1534880 1541682 1521076 1541521
1542981 1536999 1544193 1539274 1545900 1550511 1542746 1544010 1545883 1557845
1558318 1542974 1586474 1557304 1587307 1558193 1590423 1595019 1598449 1594679
1545939

NB_BBS_6.5.4
------------
1280130 1201793 1315488 1147236

NB_BMR_6.5.4
------------
1201738 1300796 1235891 1251401 1205755 1363119 1282624 1300702 1300520 1409123
1404510 1423547 1368029 1442012 1226065 1450240 1426891 1452256 1455096 1463875
1466044 1469841 1470826 1476962 1477173 1372973 1477142 1479559 1485370 1519805
1516293 1525928

NB_CLT_6.5.4
------------
1285455 1247094 1266996 1274467 1271181 1266828 1267706 1240486 1275233 1291152
1260323 1251656 1254610 1248242 1290084 1281628 1264543 1277465 1267880 1065622
1298872 1286001 1278425 1298551 1266772 1239520 1295790 1321721 1151349 1276983
1274105 1286092 1302201 1316849 1427469 1456039 1458931 1468485 1502155 1503870
1502078 1518331 1501805 1301041 1253910 1246062 1316896 1234683 1282457 1315723
1141312 1235177 700722 1316030 1269701 1221450 1301941 1302903 1245767 1240580
1260009 1363123 1365476 1226486 1244254 1249811 1255700 1370738 1384896 1377315
1382522 1383095 1126594 1403614 1431007 1432150 1421497 1509875 1558174 1590973
1595083 1598047 1597697 1603770 1603922 1364370 1261359 1182949 1368000 1361179
1374137 1250875 1274771 1385956 1283409 1378098 1388949 1256040 1257567 1227674
1384505 1394294 1391201 1243760 1397770 1397803 1394464 1395191 1180431 1395095
1378871 1392357 1128777 965836 1395388 1407095 1400851 1296897 1386091 1402016
1392368 1413113 1278561 1413313 1390861 1414077 1173100 1390505 1410798 1282150
1415947 1414211 1414312 1418051 1268084 1412901 1411499 1400002 1422476 1421893
1274472 1267027 1370671 1208654 1371578 1424207 1400376 1424291 1407021 1283922
1421724 1422599 1413001 1400717 1473485 1473486 1410178 1294340 1418524 1397773
1301030 1412924 1413063 1431018 1433273 1399857 1425305 1434146 1426057 1384805
1276634 1431894 1416846 1435119 1431758 1431826 1417844 1396173 1383748 1439607
1135673 1430950 1406219 1406213 1436844 1431015 1441498 1433052 1439252 1435489
1323857 1538553 1431527 1426014 1444551 1427600 1414674 1445493 1381806 1442063
1447058 1445648 1430034 1411788 1413618 1431088 1447265 1447160 1432407 1446408
1437425 1425084 1448195 1442239 1418373 1452416 1148446 1446653 1451465 1447260
1453529 1442301 1451023 1436594 1453605 1416785 1379510 1262599 1446468 1459294
1399839 1465331 1395101 1465033 1458226 1450234 1449178 1453422 1458420 1432148
1405180 1470340 1460964 1463890 1468581 1448206 1481250 1529072 1446401 1481284
1446147 1450564 1466528 1464016 1452281 1421534 1460587 1439971 1467900 1471621
1468877 1428325 1469444 1471613 1463937 1465258 1464015 1476600 1482673 1482676
1480286 1587338 1602790 1600654 1474403 1448396 1408851 1412268 1458872 1473860
1465634 1474475 1465728 1438645 1433497 1475916 1438822 1450268 1475313 1473499
1417504 1452344 1478495 1478915 1475161 1461116 1126065 1480041 1467989 1469706
1460837 1468318 1464701 1481159 1480280 1461993 1482660 1300129 1463877 1449955
1472234 1451817 1481404 1414922 1437385 1481373 1476107 1374989 1482914 1477935
1486988 1485005 1485946 1437453 1402322 1481348 1486168 1472633 1486686 1486807
1487580 1487510 1464678 1488267 1444236 1452950 1481714 1478999 1470973 1485977
1488734 1475372 1484302 1500272 1500484 1487577 1557578 1405038 1488525 1435092
1501040 1501855 1450415 1503555 1503554 1504217 1502059 1475402 1503097 1505138
1504987 1505661 1429723 1507290 1505203 1507663 1501647 1501118 1417539 1502104
1508567 1406063 1507033 1500451 1509112 1499426 1509107 1508224 1155347 1454759
1483007 1509370 1508901 1511217 1449853 1481224 1455436 1406992 1514843 1502251
1503674 1508943 1476060 1515064 1518716 1517830 1516611 1516658 1511966 1515378
1512269 1515674 1475595 1517091 1468310 1501973 1520790 1517775 1518415 1521609
1520660 1521319 1514161 1519049 1523991 1521072 1458798 1515697 1428897 1523771
1524262 1524495 1512307 1514813 1505895 1525307 1518751 1524391 1506156 1526402
1527601 1501039 1467372 1593966 1529861 1527862 1461913 1522273 1510981 1514334
1527768 1531249 1523443 1587409 1530121 1525375 1512052 1531929 1529030 1531907
1533986 1516985 1533817 1534963 1535794 1535780 1536441 1529377 1535663 1539736
1536918 1537820 1541722 1534880 1541682 1521076 1541521 1542981 1536999 1544193
1539274 1545900 1550511 1542746 1557316 1557318 1544010 1545883 1557845 1558318
1542974 1586474 1557304 1587307 1558193 1590423 1595019 1598449 1594679 1545939


NB_DB2_6.5.4
------------
1398665 1374366 1427035 1441557

NB_DMP_6.5.4
------------
1217098 1247981 1275573 1281911 1208508 1286172 1361300 1167140 1424308 1421594
1442316 1469272 1462054 1479387 1505107 1502073

NB_ENC_6.5.4
------------
1413512

NB_INX_6.5.4
------------
1302046

NB_JAV_6.5.4
------------
1269550 1385012 1015590 1373561 1231644 1398344 1398173 1385770 1300978 1402954
1412872 1411564 1412461 1425914 1035276 1421469 1388074 1416268 1439821 1436533
1426474 1439070 1398689 1447620 1155201 1453215 1456221 1451244 1454298 1465532
1252404 1461593 1471948 1433549 1475026 1475814 1452175 1479108 1466996 1478919
1483476 1483362 1483465 1391155 1486506 1478018 1500190 1483897 1399167 1505537
1399174 1517224 1519186 1518747 1524277 1531521 1544995

NB_LOT_6.5.4
------------
1487594

NB_LUA_6.5.4
------------
1363981 1513309 1158858

NB_NOM_6.5.4
------------
1167039 1255955 1240142 1245644 1275868 927989 1203966 855237 1427680 1315412
1446868 1422459 1461305 1259890 1432471 1414295 1448155 1484203 1529844 1528847


NB_ORA_6.5.4
------------
1374366 1402422 1452458

NB_SAP_6.5.4
------------
1063955 1430999 1458282 1509336 1501622

NB_SMU_6.5.4
------------
1442031 1463891 1484940 1510055

NB_SNC_6.5.4
------------
1275601 1244922 1249726 1287259 1272183 1258356 1272157 378649 1250928 1251765
1130616 1198363 1317951 1323300 1228384 1252585 1323643 1363449 1257455 1134680
1323758 1283920 1276398 1378894 1366314 1278645 1403955 1415117 1253140 1251337
1053635 1412947 1424138 1250759 382235 1444727 1448262 1447692 1446792 1457644
1456424 1428284 1466545 1466832 1428408 1437956 1461478 1428729 1460851 1477603
1474586 1231756 1481101 1483134 1481079 1462067 1513666 1526648 1529942 1474498
1532955 1529158 1537663 1533275 1535789 1542470 1599601

NB_SYB_6.5.4
------------
1321466

NB_VLT_6.5.4
------------
1321303 1399444 294799 1453874 1461863 1449157 1465117 1486202 1460712 1525087





=========================
V. RELEASE UPDATE CONTENT
=========================
This section contains the Release Update 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 Release Update
subsection describes a feature, enhancement, or issue fixed with this
Release Update.

Description
    Describes a particular problem contained in this Release Update.

** 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 Release Update
----------------------
Each item listed in this section describes a feature, enhancement, or change
that comprises this Release Update. Please read this section thoroughly to
understand the contents of this update.
--------------------------------------------------------------------------------
Etrack Incident = ET1285455

Description:
   A change was made to replace the raw-sockets Openstorage proxy plugin, RPC.
   This plug-in uses bpcd and pbx with a Corba-based scheme that is consistent
   with the established NetBackup practice.  
--------------------------------------------------------------------------------
Etrack Incident = ET1247094
Associated Primary Etrack = ET1247090
Titan cases:  240-749-518

Description:
   bpexpedate was missing from UNIX bpps output.
--------------------------------------------------------------------------------
Etrack Incident = ET1266996

Description:
   If the event manager (nbevtmgr) core dumped and was restarted by the
   service monitor (nbsvcmon) high water mark events might not get received by
   nbstserv.  As a result, disk clean up did not occur when the disk-staging
   storage unit (STU) reached the high-water mark. The backup policies
   reported the STU as full when there was still disk space available.
--------------------------------------------------------------------------------
Etrack Incident = ET1274467

Description:
   If a job queue was waiting for a counted resource such as max jobs per
   client or max jobs per policy, the retry reason was provided in the "state
   details" in Activity Monitor. However, there was no corresponding message
   in "job details".  
--------------------------------------------------------------------------------
Etrack Incident = ET1271181
Associated Primary Etrack = ET1270442
Titan cases:  240-929-831 291-179-422 311-919-195

Description:
   When upgrading from NetBackup 6.0 to 6.5 some old entries could remain in
   the database. These entries would cause the NetBackup Resource Broker
   (NBRB) to crash at start-up. A change was made to remove these entries
   from the database.

Workaround:
   If you encounter an issue similar to this, you should clean the database
   manually.
--------------------------------------------------------------------------------
Etrack Incident = ET1269550

Description:
   In the Change Configuration dialog for a Bare Metal Restore client, while
   mapping a HP-UX/AIX Volume Group or a VxVM Disk Group or SVM Disk Set,
   if a user chooses the "Simplify Volume Group"/"Simplify Disk
   Group"/"Simplify Disk Set" option respectively, the user interface was
   enforcing a size check which was not required.
   
   Because of this issue, the user could not proceed with the mapping
   operation from the user interface if the space available on the disks
   was less than that used by the original volume group.  
--------------------------------------------------------------------------------
Etrack Incident = ET1266828

Description:
   A change to the default value of some configuration options was added to
   this  release. The NetBackup resource broker (nbrb) will now use "shared
   reservations" as the default. In addition, the evaluation cycle will be
   interrupted every three minutes and unloads will be performed at each
   break.  
--------------------------------------------------------------------------------
Etrack Incident = ET1280130
Associated Primary Etrack = ET1256036
Titan cases:  230-523-609

Description:
   Unable to add packages or patches that require user interaction to Solaris
   Shared Resource Trees (SRT's).
--------------------------------------------------------------------------------
Etrack Incident = ET1201793

Description:
   The session cleanup would not complete if a Shared Resource Tree (SRT)
   copy session was interrupted.  
--------------------------------------------------------------------------------
Etrack Incident = ET1201738

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

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

Description:
   An enhancement has been made that enables a user to preserve multiplexing
   on duplicated tape images.  
--------------------------------------------------------------------------------
Etrack Incident = ET1240486

Description:
   Symbolic links were added between HP-UX11.11 and HP-UX11.31 for
   HP PA RISC systems.  In addition, symbolic links were added between
   HP-UX11.23 and HP-UX11.31 for HP Itanium.
--------------------------------------------------------------------------------
Etrack Incident = ET1275233

Description:
   Changes were made to the nbkmsutil client interface (CLI) to accept
   values for the arguments state and cipher to no longer be case sensitive.
   For example, Prelive, PRELIVE, prelive are now accepted as the same value.
--------------------------------------------------------------------------------
Etrack Incident = ET1291152

Description:
   This release of NetBackup contains a new NetBackup Enterprise Vault agent.
   For more information about this agent, refer to the following TechNote on
   the Symantec Support Web site.
   
       http://entsupport.symantec.com/docs/318349
--------------------------------------------------------------------------------
Etrack Incident = ET1260323
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 = ET1251656

Description:
   Changes were made to improve performance of tape (source) to tape
   (destination) duplications by using the same bptm write process across
   multiple backup images. This is similar to the current behavior when
   duplicating disk to tape images. The greatest benefit occurs when
   duplicating many small images, and when the source is a VTL. This change
   does not have any effect when using the "preserve multiplexing" option.  
--------------------------------------------------------------------------------
Etrack Incident = ET1275601

Description:
   FlashSnap Point-in-Time (PIT) restore on a Linux client was failing with
   a status 5 while using a Windows master.
   

Workaround:
   If you encounter this issue, use a UNIX master.  
--------------------------------------------------------------------------------
Etrack Incident = ET1244922

Description:
   You must use a capital letter when running a IR to STU backup of a raw
   partition or the restore would fail on a Windows system.

Workaround:
   To avoid this issue, make sure that you use a capital letter for the
   file list.
--------------------------------------------------------------------------------
Etrack Incident = ET1254610

Description:
   bpbackup would fail with a status code 174 error. A change was made to
   address a problem with how the Tru64 Advfs file system behaved when the
   file system became full. The change modifies the behavior of the disk
   write code to work around that problem.
--------------------------------------------------------------------------------
Etrack Incident = ET1249726
Associated Primary Etrack = ET1249433
Titan cases:  220-264-336

Description:
   NDMP backup would fail with an error 99 after 24 hours. A change was made
   that increases the maximum value of that timeout to 7 days.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1248242 ET1290084

Description:
   Bpdbm would exit if there was a serious mismatch between the content of
   the EMM Database and the image database. On startup, bpdbm would exit if
   the db/images/db_marker.txt file did not exist.  
--------------------------------------------------------------------------------
Etrack Incident = ET1281628

Description:
   Certain conditions could cause the number of images on a piece of media
   to become negative.  
--------------------------------------------------------------------------------
Etrack Incident = ET1264543

Description:
   Memory was leaked while fetching NDMP information.
--------------------------------------------------------------------------------
Etrack Incident = ET1287259
Associated Primary Etrack = ET1255281
Titan cases:  311-803-334

Description:
   FlashSnap snapshot disk group split operation would fail because of open
   handles to the snapshot volumes.  
--------------------------------------------------------------------------------
Etrack Incident = ET1277465
Titan cases:  320-181-589

Description:
   True Image Restore (TIR) was required for a backup to a NearStore storage
   unit with filesystem export enabled. The filesystem export feature
   provides a filesystem export of the data set as well as improved data
   de-duplication on the filer. This feature enables users who may not be
   interested in filesystem export to still receive the improved data
   de-duplication. In addition, a user also may not want to configure his
   or her policies with the overhead of TIR. This enhancement enables TIR
   to be optional for backups to a NearStore storage unit with filesystem
   export.  
--------------------------------------------------------------------------------
Etrack Incident = ET1267880

Description:
   For a multiple copy job, different copies could be waiting for different
   reason code. But only one reason could be displayed in the Activity
   Monitor. The reason code displayed in the Activity Monitor was the reason
   code for the last waiting copy and it was not getting updated in case the
   reason changes or if the copy was no longer waiting for anything.
   
   With the fix, the reason code for the last waiting copy is still
   displayed. However, the reason code is updated every five minutes. So if
   the reason code changes, it is reflected in the Activity Monitor.  
--------------------------------------------------------------------------------
Etrack Incident = ET1065622

Description:
   VxFI uses its own caching for assigning a LUN to array disks. If the disk
   was assigned to a host using another LUN, the nbshareddisk, after a
   failure, is  supposed to print the following error message if the LUN is
   already unmasked to the host.
      UDID already unmasked on the host on some other LUN
   
   Currently the nbshareddisk prints the following error.
      ERROR: import resource failed LUN unmasking (presenting) failed
--------------------------------------------------------------------------------
Etrack Incident = ET1167039

Description:
   The details of the Master Server Unreachable alert would show the NOM
   Server field twice.  
--------------------------------------------------------------------------------
Etrack Incident = ET1255955

Description:
   A change has been made to ensure that the "Duplicate Master Server Entry"
   error message is not displayed on a Window as well as a Solaris platform.  
--------------------------------------------------------------------------------
Etrack Incident = ET1240142

Description:
   The Low available media alert policy should not consider cleaning media as
   media available for backup.  
--------------------------------------------------------------------------------
Etrack Incident = ET1245644

Description:
   A change was made to remove the NOMAdmin -stop and -start commands from
   the NOMAdmin utility.  
--------------------------------------------------------------------------------
Etrack Incident = ET1298872

Description:
   Command lines that used emmlib would receive a segmentation fault if the
   orb initialization failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1286001
Titan cases:  320-113-968

Description:
   A progress log file created during bpbackup would not show the media ID
   used during that backup operation.
--------------------------------------------------------------------------------
Etrack Incident = ET1278425
Titan cases:  311-569-042

Description:
   Some Linux directories have incorrect ACL's assigned. A change has been
   added to rectify the issue by looking at each of the three values
   separately instead of en mass.
--------------------------------------------------------------------------------
Etrack Incident = ET1300796

Description:
   Solaris client restoration would fail if the client configuration
   contained a mapping of SVM metadevices originally on the backup tag slice.
   The mapping would result in the SVM metadevices on the wrong slice on the
   target disk, and caused the failure.  
--------------------------------------------------------------------------------
Etrack Incident = ET1235891

Description:
   An unmapped operation carried out on a slice of a Solaris client
   configuration would fail with the message, "Failed to pack slices
   together". This issue would occur if the slice being unmapped was
   created on an EMC-PP DMP disk.  
--------------------------------------------------------------------------------
Etrack Incident = ET1298551

Description:
   Failed SSOD start-up restore jobs would appear as completed (successful)
   in the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET1266772
Associated Primary Etrack = ET1241061
Titan cases:  220-246-593 220-263-137

Description:
   Changes have been made to correct misleading log messages.
--------------------------------------------------------------------------------
Etrack Incident = ET1239520
Associated Primary Etrack = ET1238164
Titan cases:  281-315-523

Description:
   If the CLIENT_PORT_WINDOW was specified in the configuration, vnetd
   connection code would give up too soon when seeing EADDRINUSE errors
   from connect(2).  

Workaround:
   If you encounter this issue, do not specify CLIENT_PORT_WINDOW. Use the
   default values.  
--------------------------------------------------------------------------------
Etrack Incident = ET1295790 ET1321721
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 full backup the first time an incremental was attempted after
   upgrading to 6.5.2.
   
   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 = ET1151349

Description:
   A status 26 error would appear in the restore status user interface during
   an SQL database Flashsnap Instant Recovery copy-back restore. The restore
   succeeds.
--------------------------------------------------------------------------------
Etrack Incident = ET1276983

Description:
   When using the NetBackup Administration Console on the inactive node of a
   cluster, a problem existed that prohibited a user from being able to view
   properties for disk storage units.  
--------------------------------------------------------------------------------
Etrack Incident = ET1272183
Associated Primary Etrack = ET1240427
Titan cases:  311-775-083

Description:
   When allowing a Media server to control the drives attached to an NDMP
   device smtape type backups will fail.  

Workaround:
   Allow only the Master Server to control the drives attached to an NDMP
   device.  
--------------------------------------------------------------------------------
Etrack Incident = ET1302046
Associated Primary Etrack = ET1301137
Titan cases:  240-779-991

Description:
   A fix has been added that provides support for Informix table-level
   restores using the Informix archecker utility.
--------------------------------------------------------------------------------
Etrack Incident = ET1298900
Associated Primary Etrack = ET1286267
Titan cases:  320-103-488

Description:
   SQL server snapshot client backups would fail on Windows x64 systems with
   a status 69 : "invalid filelist specification" error.  
--------------------------------------------------------------------------------
Etrack Incident = ET1274105

Description:
   The bpcompatd conversion to string was not handled in the start and the
   stop array for UNIX.  A change was made to add the proper string
   conversion for bpcompatd name.
--------------------------------------------------------------------------------
Etrack Incident = ET1258356

Description:
   A change was made to ensure that the user interface adds the option to
   validate VMware credentials when entered.
--------------------------------------------------------------------------------
Etrack Incident = ET1272157
Associated Primary Etrack = ET1227466
Titan cases:  311-818-404

Description:
   Backups of files larger than 2 gigabytes, using SnapVault would result in
   errors when restores were attempted. Additionally, bplist would display
   the incorrect size for the file, it appeared as a negative value.  
--------------------------------------------------------------------------------
Etrack Incident = ET378649

Description:
   A 3PC or MSC backup of an empty file system would cause bpbkar to core
   dump. However, after the files were put on the file system, bpbkar did
   not core dump and the backup completed successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET1250928

Description:
   Several snapshot methods were not properly listed as volume snapshot
   methods by the Snapshot Policy Configuration Wizard. This has been
   corrected.  
--------------------------------------------------------------------------------
Etrack Incident = ET1286092

Description:
   The output from the nbdb_backup command line was not localized on Japanese
   and Chinese systems.  This also affected the NbDbAdmin.exe on the Windows
   NetBackup Administration Console.  
--------------------------------------------------------------------------------
Etrack Incident = ET1253170
Associated Primary Etrack = ET1238757
Titan cases:  240-657-938 320-175-174

Description:
   Restores generated from Enterprise Vault Storage Migrator can be very slow
   when numerous images exist.  
--------------------------------------------------------------------------------
Etrack Incident = ET1315488

Description:
   The creation of media boot CD/DVD ISO images on AIX boot servers with
   bmrsrtadm would sometimes produce unmount error messages.  
--------------------------------------------------------------------------------
Etrack Incident = ET1302201

Description:
   A change has been added to address an issue that caused a bpdbm core dump
   while creating a new policy .
--------------------------------------------------------------------------------
Etrack Incident = ET1316849 ET1427469 ET1456039 ET1458931 ET1468485 ET1502155
ET1503870 ET1502078 ET1518331 ET1501805

Description:
   Active Directory Granular Restore is a feature being added to the 6.5.4
   release. This feature enables the restore of individual Active Directory
   objects from a standard System State backup.  
--------------------------------------------------------------------------------
Etrack Incident = ET1301041

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 is logged:
   
   "Standard Encryption is not supported for AFS volume backups. Use Legacy
   Encryption"
--------------------------------------------------------------------------------
Etrack Incident = ET1253910

Description:
   A change was made to ensure that the NetBackup Administration Console
   (for Java and Windows) validates VM user credentials when entered.
--------------------------------------------------------------------------------
Etrack Incident = ET1246062

Description:
   Changes have been made to the Snapshot Client Options dialog to improve
   the way VMware options are displayed.
--------------------------------------------------------------------------------
Etrack Incident = ET1275868

Description:
   Changes have been added to improve the performance of the login process
   into a NOM server.  
--------------------------------------------------------------------------------
Etrack Incident = ET1316896

Description:
   In certain failure cases the nbsvrgrp executable would crash.  
--------------------------------------------------------------------------------
Etrack Incident = ET1234683

Description:
   VxFI would close all the possible descriptors for a process. A change has
   been made to close only those that are open. This change also ensures that
   a lot of time is not consumed.
--------------------------------------------------------------------------------
Etrack Incident = ET1282457

Description:
   Changes have been made to PERFO Minimize BPGETCONFIG calls to improve
   performance.
--------------------------------------------------------------------------------
Etrack Incident = ET1251765

Description:
   The vmupdate command with the -inventory_file option would fail to add the
   correct (expected) media id when the specified media prefix contains digits.  
--------------------------------------------------------------------------------
Etrack Incident = ET1315723
Associated Primary Etrack = ET1136100
Titan cases:  281-183-906

Description:
   The NetBackup-Java Administration Console could not display certain
   French characters. This limited the restore capabilities in that a single
   file restore was not possible because the files could not be displayed.
   More specifically, there were no files that matched the specified criteria
   in restore properties.
--------------------------------------------------------------------------------
Etrack Incident = ET1141312
Associated Primary Etrack = ET1137054
Titan cases:  281-202-606

Description:
   The DISK_GROUP variable in a shell script was not being initialized. In
   some cases shell scripts would write an error message on the console,
   when the DISK_GROUP variable was used without initializing it.
--------------------------------------------------------------------------------
Etrack Incident = ET1235177

Description:
   Changes have been added in this release to fix for issues reported by
   Coverity such as a memory Leak in the setPolicyInfo() function. (This
   function was removed because it was no longer used.)
--------------------------------------------------------------------------------
Etrack Incident = ET1130616

Description:
   Snapshot backups, with either FlashBackup or Standard policy types, would
   fail when backing up / or the root partition. This has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET700722

Description:
   A change was made to improve the time it would take for NBSL to send the
   DriveThroughput information.
--------------------------------------------------------------------------------
Etrack Incident = ET1198363

Description:
   bpsnapconfig could hang when querying information from a client that was
   not responding to bpcd requests. This has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET1316030
Associated Primary Etrack = ET1243849
Titan cases:  311-867-637

Description:
   A change was added to address an issue that caused the KEEP_LOGS setting
   to not work on the Media server.
--------------------------------------------------------------------------------
Etrack Incident = ET1269701

Description:
   A change has been made to correct inconsistencies with the Attempt history
   in NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET1317951
Associated Primary Etrack = ET1215062
Titan cases:  220-204-387

Description:
   Flashbackup restores would fail with the following error message:
      find_imghdr: Unable to start VxMS XM-R'  
--------------------------------------------------------------------------------
Etrack Incident = ET1321466

Description:
   Added Linux x86 support for Sybase (32 and 64 bit).
--------------------------------------------------------------------------------
Etrack Incident = ET1217098
Titan cases:  290-870-194

Description:
   bpimagelist did not report the actual number of files backed up by NDMP.
   
   This patch fixes this problem so that bpimagelist will now report the same
   number of files as is recorded in the catalog.
   
   
   
--------------------------------------------------------------------------------
Etrack Incident = ET927989

Description:
   An issue with NOM caused the following error to occur.
      JobID:Backup job cannot be suspended or resumed
   
   A change has been made to ensure that the active or queued jobs suspend or
   Resumed properly.
--------------------------------------------------------------------------------
Etrack Incident = ET1323300

Description:
   If you select any active or queued job in the Monitoring > Jobs >
   Details page of the NOM user interface, and then attempt to suspend or
   resume job, the following error message would appear.
   
      JobID:Backup job cannot be suspended or resumed
   
   A change has been made to ensure that any active or queued jobs that are
   selected to be suspended or resumed actually are suspended ore resumed
   successfully.  
--------------------------------------------------------------------------------
Etrack Incident = ET1221450

Description:
   NOM requires NBSL interface for collecting media server information.  
--------------------------------------------------------------------------------
Etrack Incident = ET1228384

Description:
   The STS-I Core library would not validate the STS plug-in library names
   correctly and would load invalid libraries instead.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1301941

Description:
   This release contains added support for the following:
      RedHat 5 FT Media Server support
      RedHat 5.2 FT Media Server support
--------------------------------------------------------------------------------
Etrack Incident = ET1302903

Description:
   The NetBackup event manager (nbevtmgr) would crash when run on an HP-UX
   Machine with a hostname that is greater than eight characters long, due
   to the following error.
      ACE_OS::hostname() returning a truncated hostname.  
--------------------------------------------------------------------------------
Etrack Incident = ET1251401

Description:
   A restore  can fail if standvol and rootvol are mapped on separate disks.
   This can happen if standvol is unmapped and then mapped again on a
   different disk.  

Workaround:
   While editing the configuration, make sure that standvol and rootvol are
   mapped on the same disk.  
--------------------------------------------------------------------------------
Etrack Incident = ET1245767

Description:
   Some error descriptions could not be found for errors within nbemm.  
--------------------------------------------------------------------------------
Etrack Incident = ET1247981

Description:
   NDMP messages displayed in Job Details window were being truncated.
   The old limit was 256 characters. It has now been expanded to 2048
   characters.
--------------------------------------------------------------------------------
Etrack Incident = ET1240580

Description:
   A change has been made to address an issue that caused the Event Manager
   to core dump during startup if the Authentication Server was configured
   incorrectly and did not respond.  
--------------------------------------------------------------------------------
Etrack Incident = ET1205755

Description:
   A problem existed that caused Self Restore to go into Discovery mode.
   This issue occurred while carrying out a BMR restore of a RHEL4 operating
   system on machines that had USB, CD-ROMs, SAN Disks, and so on.  
--------------------------------------------------------------------------------
Etrack Incident = ET1252585

Description:
   Enhancements have been made to support OpenStorage direct copy to tape.
--------------------------------------------------------------------------------
Etrack Incident = ET1323643

Description:
   A change has been added to address a memory leak in Disk Service Manager
   (DSM) during a mount or unmount of a disk volume.  
--------------------------------------------------------------------------------
Etrack Incident = ET1260009

Description:
   If a backup was sent to a storage unit group that was comprised of one
   or more Disk Staging Storage Units (DSSU) and the first DSSU tried was
   full, the job would fail with a 129 status error. Subsequent retries
   would continue to use the original DSSU and would continue to fail with
   the same error.  A fix has been added to correct the retry behavior so
   the job is sent to another DSSU in the group on subsequent retries.  
--------------------------------------------------------------------------------
Etrack Incident = ET1275573

Description:
   An NdmpMoverClient error would repeat when the NDMP connection was dropped.
   The bptm log showed the following message repeated many times.
   
      13:37:07.235 [5472.4468] <16> NdmpMoverClient: ERROR InputHandler -
      ndmp_process_messages status = 19
--------------------------------------------------------------------------------
Etrack Incident = ET1281911
Associated Primary Etrack = ET1276601
Titan cases:  311-900-167 312-084-888

Description:
   While performing an NDMP restore to a different location from a Japanese
   directory name, NetBackup should support UTF-8 code in the temporary rename
   file on Windows server.  
--------------------------------------------------------------------------------
Etrack Incident = ET1208508

Description:
   NDMP_LOG_ERROR messages did not appear in the job monitor.
   
   A change has been added to ensure that all NDMP_LOG_ERROR messages sent
   from a NAS filer appear in the job monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET1147236
Titan cases:  230-623-321 291-190-483

Description:
   A change has been made to address an issue that would occur while
   recovering a BMR-Linux client. The BMR-Media Boot could not be completed
   if a USB keyboard is used for the host that was being recovered.
   This was because a USB keyboard could not respond when the user was
   required to enter the client configuration information.
--------------------------------------------------------------------------------
Etrack Incident = ET1363119
Associated Primary Etrack = ET1363124
Titan cases:  312-132-053

Description:
   A Solaris configuration with mounted Oracle Data Manager devices (/dev/odm)
would fail to import on the master server.
--------------------------------------------------------------------------------
Etrack Incident = ET1363123

Description:
   A change has been made to the bpclntcmd command to make it easier to update
   the REVERSE_NAME_LOOKUP configuration on a NetBackup client. For more
   information about this enhancement, refer to the NetBackup 6.5.4 Documentation
   Update contained in the following TechNote on the Symantec Support Web site.
   
      http://entsupport.symantec.com/docs/318350

Workaround:
   If you encounter an issue while attempting to update the
   REVERSE_NAME_LOOKUP, edit the bp.conf file on UNIX, or edit the
   Windows Registry.  
--------------------------------------------------------------------------------
Etrack Incident = ET1282624

Description:
   Restore of HP-UX client would fail if "/stand" was not on a separate volume.
   A change has been added to ensure that a restore is successful when "/" is
   configured as both "root" and "stand" with an HFS file system.
--------------------------------------------------------------------------------
Etrack Incident = ET1363449

Description:
   bpfis could unnecessarily read the vfm_master.conf file from the master
   server. This has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET1365476

Description:
   Virtual Synthetics code changes have been added to the release update.  
--------------------------------------------------------------------------------
Etrack Incident = ET1226486 ET1244254 ET1249811 ET1255700 ET1370738 ET1384896
ET1377315 ET1382522 ET1383095 ET1126594 ET1403614 ET1431007 ET1432150 ET1421497
ET1509875 ET1558174 ET1590973 ET1595083 ET1598047 ET1597697 ET1603770 ET1603922
Associated Primary Etrack = ET1384850 ET1316871 ET1421552 ET1488498 ET1545309
Titan cases:  220-375-654 281-377-492 291063101 240-882-181 281-537-375

Description:
   Problems would occur when trying to restore a SharePoint database from
   a full and differential backup.    
--------------------------------------------------------------------------------
Etrack Incident = ET1286172

Description:
   Unable to browse NDMP backups when the root node is something other
   than a 2.  

Workaround:
   To work around this issue, perform a full restore. (Single file restores
   would not work in this situation)  
--------------------------------------------------------------------------------
Etrack Incident = ET1364370

Description:
   Hot Catalog backups would fail with a 130 status when the db_marker.txt
   file existed in the images directory.  
--------------------------------------------------------------------------------
Etrack Incident = ET1261359

Description:
   A change has been made to bpmedialist to enable a user to display just
   the Media that is "owned" by the  "-owner UNRESTRICTED_SHARING_GROUP".
   
   When Unrestricted Media Sharing was enabled, and there were tapes that
   were being shared, the following was true:
   -  "nbemmcmd -listmedia" shows the Server Group for these tapes as
      "UNRESTRICTED_SHARING_GROUP".
   
   -  "bpmedialist -ls" shows the last field (media server name or Server
      Group) as "UNRESTRICTED_SHARING_GROUP".
   
   -  "bpmedialist -owner ALL" shows "UNRESTRICTED_SHARING_GROUP" as the
      Server Group that owns any shared tape.
   
   However....
   "bpmedialist -owner UNRESTRICTED_SHARING_GROUP" was not allowed.
   
   This meant that there was no way to get just the tapes that were "owned"
   by "UNRESTRICTED_SHARING_GROUP" unless a user performed a
   "bpmedialist -ls|grep UNRESTRICTED_SHARING_GROUP" or
   bpmedialist -owner all|grep UNRESTRICTED_SHARING_GROUP".
--------------------------------------------------------------------------------
Etrack Incident = ET1182949

Description:
   If the VXSS_CREDENTIAL_PATH environment variable is set to point to a file
   that contains valid credentials, executing bpnbat -login will overwrite the
   file with erroneous information.  

Workaround:
   If you encounter this issue, run bpnbat -login and then rename
   $HOME/.vxss/credential as desired and set the same into
   VXSS_CREDENTIAL_PATH.  
--------------------------------------------------------------------------------
Etrack Incident = ET1368000

Description:
   The first backup job (parent) for a differential schedule for a Windows
   Open File Backup (WOFB) job with multi-streaming enabled and a file list
   of ALL_LOCAL_DRIVES would fail with status 200. If you retry the job it
   runs successfully.  
--------------------------------------------------------------------------------
Etrack Incident = ET1257455

Description:
   mm/lib/comm.c get_emm_server_version_init() calls emmlib_initilize() with
   the application name "lib_comm". This call made it impossible to know which
   process made a request to EMM. In addition, it made it very difficult to
   troubleshoot the problem.  
--------------------------------------------------------------------------------
Etrack Incident = ET1361300

Description:
   NDMP drives were being downed because of a connection timeout.
   
   NDMP connection timeout now uses the client connect timeout value.
   Previously, this value was hard coded to 60 seconds. The default is now
   5 minutes and can be adjusted by changing the "client connect timeout"
   in the user interface.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1134680

Description:
   Convert was not installed but no error messages was displayed for VMWare
   Restores. The restore eventually failed after the files were restored to
   the proxy.  
--------------------------------------------------------------------------------
Etrack Incident = ET1323758

Description:
   bpbrm would send a signal to VM when bpfis failed instead of to the
   proxy server.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1361179
Associated Primary Etrack = ET1361178
Titan cases:  220-349-593 320-132-770

Description:
   If the MDS allocations were removed directly by using
   "nbrbutil -releaseMDS" or by deleting the record from the database,
   nbrb would not be able to remove the corresponding allocation records
   from its database. This would cause the resource broker's (RB's) drive
   cache to misbehave (for example, jobs would not receive resources even if
   the drives were available) and performed other redundant operations which
   simply consumed CPU cycles.  
--------------------------------------------------------------------------------
Etrack Incident = ET1283920

Description:
   The RTP FIM must manage the NetBackup policy client name's regardless
   of whether the client name is a hostname or an FQDN.
   
   The RTP server requires that all hostnames be FQDN's but, this is not a
   NetBackup requirement. As such, NetBackup must convert any hostnames in
   a policy to a (hostname, FQDN, IP address) 3-tuple and use that 3-tuple
   to compare to the host entries on the RTP server.
--------------------------------------------------------------------------------
Etrack Incident = ET1374137

Description:
   NetBackup Job Manager (NBJM) would crash when a vault job was canceled
   after vltrun started and while it was waiting for a logical resource from
   NBJM.  
--------------------------------------------------------------------------------
Etrack Incident = ET1250875
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 = ET1276398

Description:
   The NAS Snapshot P1 snapshot was taken before the DB_BEGIN_BACKUP_CMD
   script was run.  
--------------------------------------------------------------------------------
Etrack Incident = ET1063955

Description:
   Turning on NetBackup Access Control (NBAC) could cause backint to hang
   under certain conditions.  
--------------------------------------------------------------------------------
Etrack Incident = ET1274771

Description:
   Enhancements were made with API versioning that involved changes to the
   OST core library and header files, to enable interoperability between
   different versions of the core library and plug-ins.  
--------------------------------------------------------------------------------
Etrack Incident = ET1203966
Associated Primary Etrack = ET1192696
Titan cases:  290-912-740

Description:
   Unable to modify the shortcut value that links to the Veritas Backup
   Reporter (VBR) Web user interface.  
--------------------------------------------------------------------------------
Etrack Incident = ET1321303
Titan cases:  320-099-952

Description:
   To enhance Vault supportability, new log messages were added that provide
   justification for including media into the Non-Vaulted images report.
   
   The log message pinpoints a set of media that contains duplicated images
   and is not vaulted  
--------------------------------------------------------------------------------
Etrack Incident = ET1378894

Description:
   Enhancements were made in nbrbutil that enables it to list and reset
   orphaned FT pipes in an EMM database.
   
   FT pipes could be orphaned in an EMM database if the backend storage
   servers crashed or became unavailable. Because of this, it was necessary
   to have the ability to manually list and reset the state of FT pipes in
   the database.
   
   For example,  ./nbrbutil -listOrphanedPipes
                 ./nbrbutil -resetOrphanedPipes  
--------------------------------------------------------------------------------
Etrack Incident = ET1167140

Description:
   Restoring an NDMP backup path of approximately 500 characters or more to
   an alternate location would fail.  

Workaround:
   If you encounter this issue, restore to the original location.  
--------------------------------------------------------------------------------
Etrack Incident = ET1366314

Description:
   A servant eviction was being triggered by a call to getStatusEventChannel,
   which the user interface was not calling.
   
   A Manager health check in the NetBackup Service Layer (NBSL) was triggered
   by a call to getStatusEventChannel.  The user interface was not calling
   this method. Only NOM was using it. Therefore, even if a setFail call was
   made on the Managers in many places, servant objects were not being
   evicted. A change has been made to correct this issue.
   
   From the perspective of the client's user interface, the only change is
   that it will receive an OBJECT NOT EXIST exception instead of a
   TRANSIENT exception.  
--------------------------------------------------------------------------------
Etrack Incident = ET1385012

Description:
   The "Connect using Port number" checkbox should not be selectable by
   default for VMWare credentials.
--------------------------------------------------------------------------------
Etrack Incident = ET1015590

Description:
   In the Activity Monitor's Job Details dialog of the NetBackup-Java
   Administration Console, the new job progress detail messages have been
   added for a Vault job. This provides more clarity about the job progress.  
--------------------------------------------------------------------------------
Etrack Incident = ET1373561

Description:
   The Java Runtime Environment (JRE) that is packaged with the
   NetBackup-Java Administration console has been upgraded.
   
   The release update contains the following JRE versions:
      Windows X86 ... 1.5.0_16
      Windows IA64 .. 1.4.2_18
      Tru64 ......... 1.4.2-6
      Solaris ....... 1.5.0_16
      Linux x86 ..... 1.5.0_16
      Linux IA64 .... 1.4.2_18
      HP-UX ......... 1.5.0.13
      AIX ........... 1.4.2 SR 10
--------------------------------------------------------------------------------
Etrack Incident = ET1385956

Description:
   Enable Open Storage storage servers that support direct-attached devices
   to be configured as NDMP hosts in the Device Configuration wizard of the
   user interface.

Workaround:
   If you encounter this issue, use the -ndmp_host option for the tpautoconf
   command line utility.  
--------------------------------------------------------------------------------
Etrack Incident = ET1283409

Description:
   A change was made to address an issue that caused NBPEM to crash on
   shutdown when manual or user-initiated backup jobs were running.  
--------------------------------------------------------------------------------
Etrack Incident = ET1378098
Titan cases:  281-339-813

Description:
   Improve handling of disk full scenarios on NTFS compressed file systems.
   With NTFS compression, an image fragment cannot be closed if the file
   system was full. This change solves that problem. In addition, asynchronous
   compression can cause excessive and premature disk full processing. This
   change adds a delay loop in the image layer to allow NTFS compressed image
   files a 60 second opportunity to make space available for the current
   buffer.  
--------------------------------------------------------------------------------
Etrack Incident = ET1388949

Description:
   The pack install no longer shows "vxlogcfg: No such file or directory"
   messages during client installs on some platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET1278645

Description:
   VxVM backups would fail when policies configured for Oracle and VxVM
   had long names that contained the characters, "-" or "_".
   
   VxVM has a 30-character limit on the length of a diskgroup name. The CDP
   snapshot method uses the backup_id to create the clone diskgroup. Oracle
   policies can include the policy name in the backup_id. That causes the
   CDP snapshot method to create a DG name that is too long.  Then, the CDP
   snapshot method trims everything prior to the last "_" character,
   leaving just the backup_id's timestamp to use for the clone DG name.
--------------------------------------------------------------------------------
Etrack Incident = ET1256040

Description:
   The Disk Pool wizard does not show any SharedDisk arrays to import when
   the NetBackup host names are different from the actual host names of the
   machines.  
--------------------------------------------------------------------------------
Etrack Incident = ET1231644

Description:
   A change has been added to allow the Vault user interface to control image
   expiration for tape backup images.
--------------------------------------------------------------------------------
Etrack Incident = ET1257567

Description:
   The bpbrm process would hang for 15 minutes, which caused the backup job
   to error with a 50 status (client process aborted).  
--------------------------------------------------------------------------------
Etrack Incident = ET1300702
Titan cases:  291-153-753

Description:
   This release update adds RHEL5 Platform Support for BMR Client and Boot
   Server.
   
   With this feature, RHEL5 NetBackup Clients are recognized as valid BMR
   clients and BMR Backup and Restore will be possible for such clients.
   BMR Boot Server can now function on RHEL5 Clients and is capable of
   hosting Shared resource trees (SRTs) for restoring RHEL5 BMR Clients.  

Additional Notes:
   - This release does not claim support for the "Host OS" if the RHEL5 Host
        uses the virtualization feature available in RHEL5.
   - This release does not support the Native Clustering feature available
        in RHEL5.
   - Although the Support for RHEL5 Boot server is also provided in 6.5.4,
        while installing 6.5.4 BBS on RHEL5, one needs to install pre-6.5.4
        BBS package or patches before installing the 6.5.4 BBS patch. The
        installation of pre-6.5.4 BBS package/patch might display warnings
        indicating that BBS is unsupported on RHEL5, but these warnings can
        be safely ignored.  
--------------------------------------------------------------------------------
Etrack Incident = ET1300520

Description:
   Added BMR Master server support on the HPIA64 11.23 platform.
--------------------------------------------------------------------------------
Etrack Incident = ET1227674

Description:
   This Release Update adds support for Importing BE 10d Windows 2003 VSS
   Shadow-Copy tape images.
--------------------------------------------------------------------------------
Etrack Incident = ET1384505

Description:
   The ps output showed arguments out of order causing bpps to not detect a
   running nbemm on an AIX system.  
--------------------------------------------------------------------------------
Etrack Incident = ET1363981
Associated Primary Etrack = ET1257084
Titan cases:  320-176-637 320-183-343 320102760

Description:
   A change was made to correct an issue that caused bpps to core dump when
   running any NetBackup process such as jnbSA as a non-root user with a
   large UID.
--------------------------------------------------------------------------------
Etrack Incident = ET1394294

Description:
   An optimized duplication job must send a percent complete status to the
   job progress log.
   
   When an optimized duplication was performed, the progress status bar
   was not populated with the current job progress information. Normal
   duplication jobs display progress status. A change has been made so that
   optimized duplication updates the job progress monitor with the percent
   complete status. This fix enables customers to see the percent complete
   being updated as the job progresses.
--------------------------------------------------------------------------------
Etrack Incident = ET1391201

Description:
   If the KMS_DIR configuration variable was set to just the drive letter
   (for example, d:\) the creation of an empty KMS database failed. The
   error that was seen when running the command "nbkms -createemptydb" was:
     KMS db write failed - some changes may have been made EXIT STATUS = 1277
   
   The nbkms VxUL logs (OID 286) would contain the following line:
     CreateDirectory() failed: 5

Workaround:
   If you encounter this issue, include a directory name along with the drive
   letter in KMS_DIR to allow the KMS database to be created. For example,
   use d:\kms instead of d:\.
--------------------------------------------------------------------------------
Etrack Incident = ET1243760

Description:
   An image cleanup job would generate the following nbdelete error (status
   code 114: Unimplemented error code.
--------------------------------------------------------------------------------
Etrack Incident = ET1397770

Description:
   Adding an empty entry to the client database caused backups to fail with a
   status 48, (for example, bpclient -add -client client-name).

Workaround:
   If you encounter this issue, delete the empty client database entry.  
--------------------------------------------------------------------------------
Etrack Incident = ET1397803

Description:
   Events sent by NetBackup OST plug-ins are propagated to the NetBackup
   Event Manager so that other processes can consume these events. These
   events broadcast the general health, status changes and operational
   information related to storage servers.
   
   In addition to receiving events from the plug-in, single-threaded
   processes like bpdm/bpduplicate can also listen to such plug-in
   propagated events. Such infrastructure helps to initiate asynchronous
   operations in the storage server. Updates to the progress and completion
   of these operations are relayed via events.  
--------------------------------------------------------------------------------
Etrack Incident = ET1394464
Associated Primary Etrack = ET1385262
Titan cases:  230-576-424

Description:
   The Schedule name fields in the Activity Monitor for Vault jobs show "-".  
--------------------------------------------------------------------------------
Etrack Incident = ET1395191

Description:
   If NBAC was enabled and FIREWALL_IN was defined in bp.conf, NetBackup
   would stop working. This happens because all NetBackup CORBA
   communications failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1180431

Description:
   The localized Error Message for the Device Configuration wizard appeared
   as gibberish or unreadable characters.  
--------------------------------------------------------------------------------
Etrack Incident = ET1395095

Description:
   In AUTOMATIC NBAC mode, a change was added to attempt an insecure
   connection if the secure CORBA connection attempt fails.
--------------------------------------------------------------------------------
Etrack Incident = ET1399444
Associated Primary Etrack = ET1391227
Titan cases:  320-119-301

Description:
   The "Vault media going off-site" reports did not show the correct amount of
   data on tapes. These reports used a column width of six digits, it could not
   show more than 976GB. Therefore. if the data size of the media is more than
   976GB, the vault report would not show it correctly.  

Workaround:
   If you encounter this issue, view the reports in the NetBackup
   Administrator Console.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1378871

Description:
   In older versions of NBU, it was possible for xlatemsg() to return success
   without properly setting the message pointer.  The specific error in
   question is that nbpem crashes when its entries (116) are removed from
   /usr/openv/netbackup/nblog.conf.

Workaround:
   The workaround to this problem is to replace entries 116 in
   /usr/openv/netbackup/nblog.conf.  However, newer versions of NetBackup
   already have fixed the source of this problem, and no workaround is needed.
--------------------------------------------------------------------------------
Etrack Incident = ET1392357

Description:
   The NetBackup Service Layer (NBSL) Media manager would cache all pages.
--------------------------------------------------------------------------------
Etrack Incident = ET1398344
Associated Primary Etrack = ET1396979
Titan cases:  291-049-562

Description:
   The NetBackup-Java Administrator's Console would not maintain a
   customized column layout  
--------------------------------------------------------------------------------
Etrack Incident = ET1128777

Description:
   An enhancement was made to provide a more cautious warning message while
   expiring the tape. It will display the existing tape expiration on user
   prompt.  
--------------------------------------------------------------------------------
Etrack Incident = ET1398665
Titan cases:  290-940-742

Description:
   A NetBackup DB2 backup would fail when using the OPTIONS field on an
   HP-UX IA64 system.
--------------------------------------------------------------------------------
Etrack Incident = ET1398173

Description:
   While changing the storage unit (STU) in some policies, NetBackup would
   sometimes give an error 238.
--------------------------------------------------------------------------------
Etrack Incident = ET965836

Description:
   This Release Update provides support for NetBackup, Backup Exec tape
   reader (BETR) for BE 10d and 11d.
--------------------------------------------------------------------------------
Etrack Incident = ET1395388

Description:
   NetBackup Resource Broker (nbrb) has been enhanced to treat subsequent
   requests of a multiple image duplication job at a higher priority.  
--------------------------------------------------------------------------------
Etrack Incident = ET1374366
Associated Primary Etrack = ET1225228
Titan cases:  290-940-742

Description:
   Users from different groups cannot restore backups.
   
   A new keyword (BKUP_IMAGE_PERM) and values (USER, GROUP, ANY)have been
   defined to allow the user at backup time to set the permission on a
   backup image.
   
   A value of USER will set the permission to 600. This only allows the
   original user who backed up the data access to the backup images.
   
   A value of GROUP will set the permissions to 660. This allows anyone
   from the same group as the original user who backed up the data access
   to the backup images.
   
   A value of ANY will set the permissions to 664. This allows anyone
   access to the backup images.
   
   NOTE: If this keyword is not specified the permissions will default
         to 660.
   
   Specifying the keyword:
   Oracle - use the send command to set the variable
   For example:
   SEND 'BKUP_IMAGE_PERM=ANY';
   
   DB2 - specify the keyword in the db2.conf or in the "options" directive
   on the db2 backup command. An example of the db2.conf:
     DATABASE SAMPLE
     OBJECTTYPE DATABASE
     POLICY db2-bkup
     BKUP_IMAGE_PERM USER
     SCHEDULE Default-Application-Backup
     ENDOPER
   
   An example using the "options" directive:
     db2 backup db sample load /usr/openv/netbackup/bin/nbdb2.so OPTIONS
     BKUP_IMAGE_PERM=ANY
   
   NOTE on DB2 logs:  If use the userexit program, no configuration
   parameter is available and normal file system permission are used.
   If you use the stream method (LOGARCHMETH1 VENDOR:/usr/openv/netbackup
   /bin....) the new keyword can be used in the db2.conf or by specifying
   the keyword in the LOGARCHOPT1 parameter in the database configuration.
   
   An example of the db2.conf file:
     DATABASE SAMPLE
     OBJECTTYPE ARCHIVE
     SCHEDULE Default-Application-Backup
     BKUP_IMAGE_PERM USER
     POLICY db2_logs
     ARCFUNC SAVE
     #ARCFUNC COPY
     #ARCDIR /vxdb2/db2/v8/db2v832d/templogs
     #RETDIR /vxdb2/db2/v8/db2v832d/templogs
     ENDOPER
   
   An example of configuring the LOGARCHOPT1:
     db2 update db cfg for sample using LOGARCHOPT1 BKUP_IMAGE_PERM=USER
--------------------------------------------------------------------------------
Etrack Incident = ET1385770

Description:
   Exporting a list of clients that are connected and non-connected causes
   an error and an exception in the logs.
--------------------------------------------------------------------------------
Etrack Incident = ET1407095
Associated Primary Etrack = ET1402515
Titan cases:  220-384-133

Description:
   The nbevtmgr service runs only on the master server. On Windows, attempts to
   start on non-master servers caused errors to be recorded in the event logs.
   This issue could cause confusion for the system administrator.

Workaround:
   To resolve this issue, remove nbevtmgr from SCM on non-master servers.  
--------------------------------------------------------------------------------
Etrack Incident = ET1400851

Description:
   Network issues caused a job to stay active, resulting in no progress for
   37 hours after the job was started.
--------------------------------------------------------------------------------
Etrack Incident = ET1409123
Associated Primary Etrack = ET1408416
Titan cases:  240-951-505 251-045-129

Description:
   The SAN Volume Manager (SVM) metadevice submirror failed to attach to the
   parent metadevice due to a slice alignment mismatch between two mirrored
   disks. The error observed was:
   
      metattach: atrcus564-bup: d12: can't attach labeled submirror to
      an unlabeled mirror  

Additional Notes:
   Slices underlying submirrors on disks in use for SVM must both either
   start at cylinder 0 or both not start at cylinder 0.
--------------------------------------------------------------------------------
Etrack Incident = ET294799

Description:
   A change has been added to allow the Vault user interface to control
   image expiration for tape backup images.
   
   Today the Vault duplication tab can expire images from a disk storage
   unit after a configurable number of hours. Similar functionality is
   being offered for tape storage units such as VTLs.
   
   To expire the original tape (VTL) images, configure the following in the
   Duplication tab:
   
      "[] Expire original tape backup images after -- hour(s)"  
--------------------------------------------------------------------------------
Etrack Incident = ET1403955

Description:
   When performing a Timefinder backup on a single volume, bpdgclone would
   fail with a status 20. A change was made to correct a bad path.
--------------------------------------------------------------------------------
Etrack Incident = ET1296897

Description:
   Jobids were lost when an inline tape copy backup job was restarted.  
--------------------------------------------------------------------------------
Etrack Incident = ET1386091

Description:
   Improved the performance of Resource Broker's storage unit cache preparation.
--------------------------------------------------------------------------------
Etrack Incident = ET1402016
Associated Primary Etrack = ET1363688
Titan cases:  230-550-642

Description:
   A change was made to address an issue that caused a timeout error
   code 195 to occur when double-clicking a media device after upgrading
   NetBackup from 5.1 to 6.5.1, while running on a Solaris 8 system.  
--------------------------------------------------------------------------------
Etrack Incident = ET1392368

Description:
   A change was made in BH_ErrorServerInterceptor::send_reply (), to remove
   individual copy statements for TAO_OutputCDR copy.  
--------------------------------------------------------------------------------
Etrack Incident = ET855237

Description:
   The NOM monitoring page showed the "Total data backed up" which includes
   backup, archive, and duplicate. Starting with NetBackup 6.5.4 it will
   include backup and archive jobs only.  
--------------------------------------------------------------------------------
Etrack Incident = ET1413113

Description:
   The "make messages" failed because of a duplicated ID issue of the file
   bpfis.c.
--------------------------------------------------------------------------------
Etrack Incident = ET1374366
Associated Primary Etrack = ET1225228
Titan cases:  290-940-742

Description:
   Users from different groups could not restore backups.
   
   A new keyword (BKUP_IMAGE_PERM) and values (USER, GROUP, ANY)have been
   defined to allow the user at backup time to set the permission on a
   backup image.
   
   A value of USER will set the permission to 600. This allows only the
   original user who backed up the data access to the backup images.
   
   A value of GROUP will set the permissions to 660.  This allows anyone
   from the same group as the original user who backed up the data access
   to the backup images.
   
   A value of ANY will set the permissions to 664.  This allows anyone
   access to the backup images.
   
   NOTE: If this keyword is not specified the permissions default to 660.
   
   Specifying the keyword:
     Oracle - use the send command to set the variable
   For example:
     SEND 'BKUP_IMAGE_PERM=ANY';
   
   DB2 - specify the keyword in the db2.conf or in the "options" directive
   on the db2 backup command. An example of the db2.conf:
     DATABASE SAMPLE
     OBJECTTYPE DATABASE
     POLICY db2-bkup
     BKUP_IMAGE_PERM USER
     SCHEDULE Default-Application-Backup
     ENDOPER
   
   An example using the "options" directive:
     db2 backup db sample load /usr/openv/netbackup/bin/nbdb2.so OPTIONS
     BKUP_IMAGE_PERM=ANY
   
   NOTE on DB2 logs:  
   If you are using the userexit program, no configuration parameter is
   available and normal file system permission are used.  If using the
   stream method (LOGARCHMETH1 VENDOR:/usr/openv/netbackup/bin....)
   the new keyword can be used in the db2.conf or by specifying the
   keyword in the LOGARCHOPT1 parameter in the database configuration.
   
   An example of the db2.conf file:
     DATABASE SAMPLE
     OBJECTTYPE ARCHIVE
     SCHEDULE Default-Application-Backup
     BKUP_IMAGE_PERM USER
     POLICY db2_logs
     ARCFUNC SAVE
     #ARCFUNC COPY
     #ARCDIR /vxdb2/db2/v8/db2v832d/templogs
     #RETDIR /vxdb2/db2/v8/db2v832d/templogs
     ENDOPER
   
   An example of configuring the LOGARCHOPT1:
     db2 update db cfg for sample using LOGARCHOPT1 BKUP_IMAGE_PERM=USER
--------------------------------------------------------------------------------
Etrack Incident = ET1278561
Associated Primary Etrack = ET1384046
Titan cases:  281-399-626

Description:
   The bpstsinfo comparedbandstu functionality did not work for OpenStorage
   disk types.  
--------------------------------------------------------------------------------
Etrack Incident = ET1300978

Description:
   A Checkpoint-enabled backup job would not resume (or retry) after a
   failover.
--------------------------------------------------------------------------------
Etrack Incident = ET1413313
Associated Primary Etrack = ET1412612
Titan cases:  320-134-540

Description:
   nbpem would suspend the execution of immediate and user backups in
   NetBackup 6.5.2 when the nbpemreq -suspend_scheduling operation has been
   run.  This was different behavior than from earlier releases when only
   the scheduled jobs were suspended. A change has been made to restore the
   earlier behavior.
--------------------------------------------------------------------------------
Etrack Incident = ET1402954

Description:
   On NetBackup-Java Administration Console the nbstl command would not
   check the entered characters for Data Classification.
--------------------------------------------------------------------------------
Etrack Incident = ET1390861
Titan cases:  240-816-011

Description:
   A change was made to add additional log messages in the cluster_upgrade
   script to assist Support with troubleshooting issues that may arise
   while upgrading NetBackup on a cluster.
   
   The log messages were created in the /usr/openv/netbackup/bin/cluster
   /trace.cluster_upgrade.{pid} file.
--------------------------------------------------------------------------------
Etrack Incident = ET1414077

Description:
   A change was made to replace the BPSYNCINFO CLI call in NBSL with API.
--------------------------------------------------------------------------------
Etrack Incident = ET1173100

Description:
   bpdbjobs was not handling certain keywords and because of this, it would
   log parsing failure messages in the logs.  
--------------------------------------------------------------------------------
Etrack Incident = ET1390505
Associated Primary Etrack = ET1241252
Titan cases:  290-958-463

Description:
   A change was made to address an issue that caused EMM to fail to start
   because of the following invalid argument:
      "unable to open acceptor for <1556:EMM>: Invalid argument"

Additional Notes:
   NetBackup upgrades PBX in order to fix this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1415117

Description:
   A change was made that ensures bppficorr uses cached data instead of
   re-reading vfm.conf data.
--------------------------------------------------------------------------------
Etrack Incident = ET1412872

Description:
   A change was made to correct an ID length error in the LocalizedConstants
   java file.  
--------------------------------------------------------------------------------
Etrack Incident = ET1410798

Description:
   After NBJM was shutdown, the Windows Event Manager would sometimes
   report that job manager service stopped unexpectedly.  
--------------------------------------------------------------------------------
Etrack Incident = ET1404510
Associated Primary Etrack = ET1401282
Titan cases:  291-053-041

Description:
   A change was made to correct an issue that caused the bmrprep command to
   core dump on an AIX system when it was executed against a DOS Legacy SRT
   to restore the Windows Client.  
--------------------------------------------------------------------------------
Etrack Incident = ET1411564

Description:
   A change was made to allow a user to choose multiple hosts from the
   Devices > Hosts in the NetBackup Administration Console.  

Workaround:
   If you should encounter an issue such as this, a user can perform
   operations on the host by selecting each issue, one by one.  
--------------------------------------------------------------------------------
Etrack Incident = ET1282150

Description:
   NetApp VSM support would not work when images were expired during a
   failover.
   
   In a failover situation, the image expiration was not reading the
   NEARSTORE_FAILOVER_SERVER setting in the media servers bp.conf file
   (or registry) to determine that the filer names and volumes should be
   a swapped out.
--------------------------------------------------------------------------------
Etrack Incident = ET1415947

Description:
   During the NBJM process, the NBJM service "nbjm -terminate" would
   sometimes hang if the nbproxy was already been terminated.
--------------------------------------------------------------------------------
Etrack Incident = ET1414211
Associated Primary Etrack = ET1403880
Titan cases:  240-813-574

Description:
   If the xlatemsg call failed while writing to the progress log at the end
   of a job, the job end status notification was not sent to NBPEM. As a
   result, NBPEM thought the job was still running and no new jobs would be
   schedule for the policy/client.
   
   The xlatemsg call would fail because of erroneous entries in nblog.conf,
   because of an incorrect locale setting, or because the message catalog
   was not available for the system locale.  
--------------------------------------------------------------------------------
Etrack Incident = ET1414312

Description:
   A change was made to ensure the VMWare Credentials Screen opens when
   called.  
--------------------------------------------------------------------------------
Etrack Incident = ET1418051

Description:
   A problem displaying VMWARE machine credentials in the NetBackujp-Java
   Administration console has been fixed.  
--------------------------------------------------------------------------------
Etrack Incident = ET1268084

Description:
   The "nbshareddisk verify -udid_file ..." would fail in a clustered
   environment.  
--------------------------------------------------------------------------------
Etrack Incident = ET1413284
Associated Primary Etrack = ET1408068
Titan cases:  240-712-185

Description:
   This fix optimizes MS SQL Server Snapshot Client backups by minimizing the
   time database is kept suspended.
--------------------------------------------------------------------------------
Etrack Incident = ET1412901

Description:
   At present the NBSL - NOM protocol for volume information fetch does not
   guarantee a complete initial data load if an error occurs during initial
   data load.  

Workaround:
   If you encounter this issue, the NBSL sends error information through an
   interceptor and NOM can restart data loading under error conditions.  
--------------------------------------------------------------------------------
Etrack Incident = ET1411499

Description:
   The bpsturep command would give an error when trying to change a DSSU.
   After an upgrading, an attempt top modify a DSSU staging schedule to
   run more often resulted in receiving the following error from the user
   interface (and the command line) after each attempt:
     "invalid command parameter - Resources are busy(2050027)"
--------------------------------------------------------------------------------
Etrack Incident = ET1253140

Description:
   A continuous data protection (CDP) snapshot backup would fail when there
   are multiple cgroups in backup selection.
--------------------------------------------------------------------------------
Etrack Incident = ET1251337

Description:
   A change was made to address an issue that caused a RealTime snapshot
   method backup to fail for a VxVM volume at VxVM 5.0MP3.
--------------------------------------------------------------------------------
Etrack Incident = ET1400002

Description:
   A change was made to correct a vxlogview --showcorrupt issue that showed
   nbstserv logs as corrupt.

Additional Notes:
   This issued would not appear unless a LIFECYCLE_PARAMETERS file was not
   created.
--------------------------------------------------------------------------------
Etrack Incident = ET1053635

Description:
   FlashBackup policies on a Linux system using Flashsnap or the VxVM
   snapshot method were not completing.
   
   Policies of this type do not stop. The snapshot was taken and deported
   to the alternate client. It was then mounted and the read operation
   began but it never ended.

Workaround:
   To work around this issue, use the VxFS_snapshot method.
--------------------------------------------------------------------------------
Etrack Incident = ET1412947

Description:
   The "make messages" would fail because of a duplicated ID issue that
   was found in the file, restfiles.c.  
--------------------------------------------------------------------------------
Etrack Incident = ET1422476

Description:
   A change a made to address an issue that caused nbstlutil diskspaceinfo
   to core dumps every time it was run.
--------------------------------------------------------------------------------
Etrack Incident = ET1421893
Associated Primary Etrack = ET1395878
Titan cases:  240-804-685

Description:
   Unable to cancel duplications jobs at the same time when using the same
   bpduplicate process (ITC).

Workaround:
   If you encounter this issue, select only one of those jobs when
   canceling. Canceling one of the jobs causes the others to be canceled too.
--------------------------------------------------------------------------------
Etrack Incident = ET1412461

Description:
   On NetBackup Administration Console ,the "Browse for Virtual Machine"
   would show VM's name as blank while adding a client for a policy.  
--------------------------------------------------------------------------------

Etrack Incident = ET1274472

Description:
   The JAVA user interface for a Storage life cycle had a "Capacity
   Managed" retention type for disk destinations that did not enabled
   this capability.  A change was made to add a check to disable or enable
   the capacity option for the disk types, AdvancedDisk and SharedDisk.
--------------------------------------------------------------------------------
Etrack Incident = ET1423547

Description:
   The bmrc command on restoretask or discovertask would sometimes fail
   with the following error message.
      "[Error] V-122-3 Operation failed."  
--------------------------------------------------------------------------------
Etrack Incident = ET1267027
Associated Primary Etrack = ET1140671
Titan cases:  281-216-717

Description:
   Could not remove machines of type "virtual_machine" from nbemm.  
--------------------------------------------------------------------------------
Etrack Incident = ET1370671
Titan cases:  312-055-259

Description:
   A change was added to ensure the correct NetBackup version appears on
   all servers.  
--------------------------------------------------------------------------------
Etrack Incident = ET1208654
Titan cases:  311-820-657

Description:
   A parent ITC job would only show one tape/drive requested when
   multi-streaming is on.
--------------------------------------------------------------------------------
Etrack Incident = ET1371578
Associated Primary Etrack = ET964511
Titan cases:  220-128-684 220-136-126 240411626

Description:
   Added a -quick_print option to bpdbjobs command that can display the job
   report much quicker.  
--------------------------------------------------------------------------------
Etrack Incident = ET1424207

Description:
   When bpbrm or bpbrmds exits on media servers, there are times when the
   Job Manager (JM) does not receive a socket close notification for a
   long time. Because of this the job clean-up gets delayed and would
   cause problems.
   
   With this fix, JM is explicitly breaking the connection when it gets the
   final exit status from bpbrm or bpbrmds.  
--------------------------------------------------------------------------------
Etrack Incident = ET1400376

Description:
   Because of some timing issues, some fields of job record may get
   overwritten with stale information. In this particular case, an update
   from JM (which was issued first) reaches bpjobd after the update from
   bpduplicate (which was issued later).  
--------------------------------------------------------------------------------
Etrack Incident = ET1427035
Associated Primary Etrack = ET1423994
Titan cases:  320-131-925

Description:
   A DB2 alternate restore would fail on the db2 rollforward command and
   produce the error message: unable to find log files.
   
   DB2 has changed in the newer releases in the rollforward processing.
   The older releases would send our agent the DB2 instance.  The newer
   releases no longer do this - they send in an "*".  This breaks how the
   NetBackup DB2 agent handles the alternate restore for the archive logs.
   If the ALTERNATE object is present, the NetBackup agent would compare
   the database alias and database instance sent in by DB2 with the
   DESTALIAS and DESTINST in the ALTERNATE object of db2.conf. If these two
   tests were true, the NetBackup DB2 agent would process the restore of
   the archive logs as an alternate restore. The NetBackup DB2 agent now
   only compares the database alias with the DESTALIAS in the ALTERNATE
   object.  If they match, the restore of the archive logs will be treated
   as an alternate restore.  
--------------------------------------------------------------------------------
Etrack Incident = ET1424138

Description:
   The Snapshot Policy Wizard did not detect the presence of VxVM and VxFS
   on a Linux system for some newer releases of VxVM and VxFS. A change has
   been added to correct this issue.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1424291
Associated Primary Etrack = ET1364688
Titan cases:  281-384-196

Description:
   The user was not be able to see or deny pending requests if NBAC was
   enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET1424308

Description:
   An NDMP job on Windows x64 would fail with NDMP_XDR_DECODE_ERR.

Workaround:
   If you encounter this issue, change the VxUL logging to DebugLevel=5.

Additional Notes:
   This issue is timing related and it may be intermittent. Changing the
   logging level or rerunning the job might make the problem disappear.  
--------------------------------------------------------------------------------
Etrack Incident = ET1421594

Description:
   A change was made so the NUMBER_DATA_BUFFERS_DISK parameter can now be
   used for NDMP backups and restores to and from the disk storage units.  
--------------------------------------------------------------------------------
Etrack Incident = ET1407021
Associated Primary Etrack = ET1404301
Titan cases:  291-041-117

Description:
   A backup can fail with status 26 due to problems with mount points on
   the client that are not related to the job.  

Workaround:
   To work around this issue, change the permissions on the clients mount
   points so the bpbkar process can access them.  
--------------------------------------------------------------------------------
Etrack Incident = ET1283922

Description:
   Snapshot backups get progressively longer when more snapshot backups exist
   for a given policy.  This problem was detected when trying to support
   hundreds of snapshot backups using the RealTime Protection snapshot
   method.  The backup validation process consumed lots of extra time. This
   fix enhances how backups are validated so that validating hundreds of
   backups now takes seconds instead of minutes (or hours).
--------------------------------------------------------------------------------
Etrack Incident = ET1421724
Associated Primary Etrack = ET1363246
Titan cases:  320-119-563

Description:
   bprd would fail a user-directed list, restore, or backup with a
   status 133 even with the global and client list_restore enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET1422599

Description:
   In NetBackup-Java Administration console report "Disk Storage Unit
   Status", it was required to hit the refresh button before "run reports"
   to get new data.  
--------------------------------------------------------------------------------
Etrack Incident = ET1413001

Description:
   The "make messages" would fail because of duplicated message IDs.
--------------------------------------------------------------------------------
Etrack Incident = ET1400717

Description:
   A corrupted image file could cause media not to be unassigned when other
   images expired.  

Workaround:
   If you encounter this issue, manually remove the corrupt image file.  
--------------------------------------------------------------------------------
Etrack Incident = ET1473485 ET1473486

Description:
   This Release Update includes the NBCC and NBCCR support utilities.  

Additional Notes:
   You can download the latest released versions of NBCC and NBCCR from
   the NetBackup Support Download site.
--------------------------------------------------------------------------------
Etrack Incident = ET1410178
Associated Primary Etrack = ET1409088
Titan cases:  312-009-783

Description:
   The NetBackup-Java Administration console would report Kilobytes written
   as 2251459822883312 for DSSU de-staging.  
--------------------------------------------------------------------------------
Etrack Incident = ET1425914

Description:
   The password would disappear from the VMware Credential screen when the
   mouse was moved over the port option. A change was made to ensure that
   the letters in the remained visable.
--------------------------------------------------------------------------------
Etrack Incident = ET1035276

Description:
   Disk Pools would not display when the PureDisk Storage Unit was licensed.  
--------------------------------------------------------------------------------
Etrack Incident = ET1427680

Description:
   In NOM, alerts were not appearing at the group level in the client
   context. A change was made to show all alerts for the specified
   alert-policy and group.
--------------------------------------------------------------------------------
Etrack Incident = ET1294340
Associated Primary Etrack = ET1292139
Titan cases:  220-308-656

Description:
   After editing four default volume pools an error is received, however the
   changes occurred anyway.
--------------------------------------------------------------------------------
Etrack Incident = ET1418524
Associated Primary Etrack = ET1402607
Titan cases:  220-295-952

Description:
   A failure would occur when attempting to update the progress log on
   NDMP clients.  
--------------------------------------------------------------------------------
Etrack Incident = ET1397773
Associated Primary Etrack = ET1386783
Titan cases:  311-819-209

Description:
   Synthetic backup would fail with error code 42s or error code 671s,
   when the bptm exits with a status 175 because of a block-size
   miscalculation.  
--------------------------------------------------------------------------------
Etrack Incident = ET1301030

Description:
   A change was made to correct an issue that caused you to not be able to
   restore from an IR snapshot backup after a reboot on a Linux system.  
--------------------------------------------------------------------------------
Etrack Incident = ET1412924

Description:
   A change was made to resolve duplicated message IDs within bpdbm.c.
--------------------------------------------------------------------------------
Etrack Incident = ET1413063

Description:
   A change was made to resolve duplicated message IDs within bpexpdate.c.
--------------------------------------------------------------------------------
Etrack Incident = ET1431018

Description:
   A change was made to correct a mismatch between the number of format
   specifiers and the number of entities to be scanned.  
--------------------------------------------------------------------------------
Etrack Incident = ET1421469

Description:
   The Disk Storage Unit Status report would show a DiskPool name for a
   BasicDisk STU.
--------------------------------------------------------------------------------
Etrack Incident = ET1433273
Associated Primary Etrack = ET1426651
Titan cases:  230-600-780

Description:
   Jobs were being marked as DONE when the exit status was 134 (only for
   back-level media server.

Workaround:
   If you encounter this issue, upgrade the back-level media server.
--------------------------------------------------------------------------------
Etrack Incident = ET1399857 ET1425305

Description:
   Added NetBackup T10 drive encryption support modifications for the STK
   library encryption and IBM 3592E06 drives on HP-UX.  
--------------------------------------------------------------------------------
Etrack Incident = ET1434146

Description:
   NBKMS may core dump on HP-UX 11.00 and 11.11 systems during a
   nbkms -createemptydb function. You may encounter the following error:
      Bus error(coredump)  

Workaround:
   To resolve this issue, install a random number generator (such as,
   KRNG11i) that creates the /dev/random and /dev/urandom special files.
--------------------------------------------------------------------------------
Etrack Incident = ET1315412
Associated Primary Etrack = ET1241428
Titan cases:  220-165-605

Description:
   The NOM reports would show the robot number as -1.  
--------------------------------------------------------------------------------
Etrack Incident = ET1426057

Description:
   Job IDs could rollover to 1 if there was a power failure or bpjob was
   not shutdown properly.  
--------------------------------------------------------------------------------
Etrack Incident = ET1384805

Description:
   The check-pointed backup jobs were being suspended during a cluster
   failover. These jobs then required manual resumes to restart them after
   the failover to the new node.  
--------------------------------------------------------------------------------
Etrack Incident = ET1276634

Description:
   A change was made to address an issue that caused bpfis hang on
   remap_file_name.
--------------------------------------------------------------------------------
Etrack Incident = ET1431894

Description:
   When nbemm is forced to shutdown the database due to a disk full condition,
   log the message to the operating system log.

Additional Notes:
   The LogToOsLog option must be enabled for these logs to be sent to the
   operating system.  
--------------------------------------------------------------------------------
Etrack Incident = ET1250759

Description:
   The Detailed Status pane in the Activity Monitor indicated the wrong client
   name when running a VMware client backup. This issue has been corrected.  
--------------------------------------------------------------------------------
Etrack Incident = ET1416846
Titan cases:  290-929-142

Description:
   Calendar backups may never run if a date is set to 0.  

Workaround:
   To avoid this issue, eliminate run days that are before the first week
   of UNIX time.  
--------------------------------------------------------------------------------
Etrack Incident = ET1435119
Titan cases:  291-009-192 291-056-016

Description:
   After configuring FT server on the newly supported 2462 cards (as of
   6.5.2), the server would hang on boot. A fix has been added to address
   this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1388074
Associated Primary Etrack = ET1219358
Titan cases:  240-719-769 281-571-327

Description:
   The Search window in the NetBackup-Java Administration Console would not
   mark files for restore correctly.

Workaround:
   If you encounter this issue, manually re-select the files to restore.
--------------------------------------------------------------------------------
Etrack Incident = ET1416268
Associated Primary Etrack = ET1266115
Titan cases:  312-111-365 320-105-978

Description:
   Cannot log into the user interface during the peak production backup
   Intervals. (This issue would cause a 525 error to occur.)
--------------------------------------------------------------------------------
Etrack Incident = ET1431758

Description:
   Not all of the listed clients were being sent from NBSL to NOM through the
   client collector <65 Onwards>.  
--------------------------------------------------------------------------------
Etrack Incident = ET1431826

Description:
   A change was made to correct an issue that caused an error message to
   appear while Browsing for Virtual Machines.
--------------------------------------------------------------------------------
Etrack Incident = ET1417844

Description:
   A change was made to modify the bpsynth startup code to use bp_gethostname()
   to determine the master server host name.  
--------------------------------------------------------------------------------
Etrack Incident = ET1368029

Description:
   This Release Update contains an enhancement in BMR-Linux restore environment
that provides a prompt to the user for entering a SCSI
   Driver Load order. This change was added because it was determined that
   the kernel buffer length at the boot prompt,"BMR:", was too small to
   accommodate a long list of drivers.
   
   With this feature, the user will see the following message while
   carrying out network- or media-based restores in BMR-Linux:
   
      "Do you want to enter a Driver Load Order [ Auto Time-Out in 20
       seconds. Default value=no ]:"
   
   The user will have 20 seconds to answer this question.
   
   In case there is no answer in 20 seconds or if the answer is "no", the
   restore continues as before. If the answer is "yes", the user is
   provided the following prompt to enter a driver load order:
   
       "Enter a colon separated driver load order:"
   
   The driver load order provided at this prompt is then used in the
   course of the restore.
--------------------------------------------------------------------------------
Etrack Incident = ET1396173

Description:
   The PCRE compilation would fail as the version of PCRE was not compiled
   with PCRE_UTF8 support.
--------------------------------------------------------------------------------
Etrack Incident = ET1383748
Associated Primary Etrack = ET1298236
Titan cases:  240-925-155 311-943-165

Description:
   On some UNIX systems (for example, Solaris) emm would erroneously
   identify a disk full condition and shut down the ASA server.
--------------------------------------------------------------------------------
Etrack Incident = ET1439607
Associated Primary Etrack = ET1435447
Titan cases:  281-430-989

Description:
   The NDMP dmplevel was not being reset after a full backup was run.  
--------------------------------------------------------------------------------
Etrack Incident = ET1135673

Description:
   Spanning was not supported in OST because the SpanImages attribute was not
   being set or was not settable. The changes allow the SpanImages attribute
   to be set or cleared on OST storage servers.  
--------------------------------------------------------------------------------
Etrack Incident = ET1430950

Description:
   Error messages similar to the following appear in the bpcd log:
   
   13:49:19.970 [4872] <16> bpcd main: strlen(pProcList) = 7852
   13:49:19.970 [4872] <16> bpcd main: char_count = 7853, .line_count = 50
   
   These messages were not the result of an error, they were merely debug
   Messages and should not be printed as errors.  

Workaround:
   If you encounter any of these messages, understand that they are not
   errors, they are only debug messages.  
--------------------------------------------------------------------------------
Etrack Incident = ET1406219
Associated Primary Etrack = ET1406210
Titan cases:  311-969-479

Description:
   The Stream number would be skipped in streams file if file list contained
   NEW_STREAM but the first line was not a NEW_STREAM.  

Workaround:
   Make sure if there are any NEW_STREAM directives in a file list that the
   first line of the file list is a NEW_STREAM.  
--------------------------------------------------------------------------------
Etrack Incident = ET1406213

Description:
   A change was made to correct an LTID core dump in the case where it
   received an out-of-range mount ID.  
--------------------------------------------------------------------------------
Etrack Incident = ET1436844 ET1431015
Associated Primary Etrack = ET1361329
Titan cases:  320-116-153

Description:
   A change was added to prevent clearing the drive comment every time
   a tape is mounted.
--------------------------------------------------------------------------------
Etrack Incident = ET1442031
Associated Primary Etrack = ET1363349
Titan cases:  291-028-593

Description:
   migrd would sometimes dump core while processing and submitting scheduled
   jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1442316
Associated Primary Etrack = ET1430796
Titan cases:  320-140-055

Description:
   De-staging duplications of NDMP images fail on Windows media servers.
   
   Duplication of NDMP images from a DSU that is configured as a DSSU can
   fail if the touch file, SIZE_DATA_BUFFERS_DISK, is set to a value that
   is higher than the tape drive's block size.  This failure only occurs for
   NDMP images, other images duplicate correctly.

Workaround:
   The setup needs another touch file called SIZE_DATA_BUFFERS_NDMP that is
   set to 256K. This adjusts the buffer size to match the source block size
   (tape 256K).
   
   However, this workaround forces the NDMP backup jobs to use the
   SIZE_DATA_BUFFERS_NDMP block size too, which is not always ideal.
   So the fax that has been made uses the following logic to correct
   this issue:
   
     1. If the backup job includes an NDMP backup and DISK, then the
        SIZE_DATA_BUFFERS_DISK touch file is used, or else the
        SIZE_DATA_BUFFERS_NDMP touch is used.
   
     2. If the backup job is an NDMP duplication job and target is DISK,
        then the SIZE_DATA_BUFFERS_DISK is used, or else the
        SIZE_DATA_BUFFERS_NDMP touch file is used.
--------------------------------------------------------------------------------
Etrack Incident = ET1441498

Description:
   A change has been made to address an issue that would cause NBPEM to
   sometimes crash during a shutdown operation.
--------------------------------------------------------------------------------
Etrack Incident = ET382235

Description:
   The position of the string "11" is misaligned in the "bpclient" output.
   A change was made to remove this code to resolve the issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1433052
Associated Primary Etrack = ET1300134
Titan cases:  220-324-641

Description:
   A change was made that enables Application clusters to be deleted
   appropriately.
--------------------------------------------------------------------------------
Etrack Incident = ET1439252

Description:
   A change was made to fix an issue that caused a core dump to occur in
   nbstserv.
--------------------------------------------------------------------------------
Etrack Incident = ET1435489

Description:
   A change was made to fix a deadlock issue that occurred in nbstserv.
--------------------------------------------------------------------------------
Etrack Incident = ET1439821
Associated Primary Etrack = ET1424574
Titan cases:  220-384-044 281-387-212

Description:
   In the Activity Monitor, the ActiveElapsed/ElapsedTime/EndTime fields are
   blank for some jobs when the StartTime = EndTime.
--------------------------------------------------------------------------------
Etrack Incident = ET1323857 ET1538553
Titan cases:  281-476-301

Description:
   Added an option, -disk_media_server, to bprestore. A user can use this
   option to specify a media server for shared disk, OST, and PureDisk SPA.
   Users will find this option useful in cases where the NetBackup domain
   spans multiple sites (such as, PDDO, OST) and the resource allocation
   could choose a remote media server that causes the image to be dragged
   across the WAN either when retrieving the image from disk or sending it
   to the client. In this scenario, the user now has the option to specify
   a local media server.
--------------------------------------------------------------------------------
Etrack Incident = ET1436533
Associated Primary Etrack = ET1430317
Titan cases:  240-810-927

Description:
   The NetBackup-Java Administration Console hangs when the "Alternate Read
   Server" option is selected for Duplication in the Vault profile.

Workaround:
   If you encounter this issue, use the following procedure to work-around the
issue:
   
   When creating a new vault profile:
   1.  In the basic duplication tab, click on "Advanced configuration"
   2.  Inside the "Advanced configuration" screen, enable the "Alternate
       read server" option.
   3.  Add a new duplication rule and choose an alternate read server from
       the drop-down list.
   4.  Save the profile.
   5.  Edit the profile again. Uncheck the "Advanced configuration" option.
       The "Alternate read server" drop-down menu on the basic screen is
       populated with a list of servers and works fine.
   
   See, the following TechNote on the Symantec Support Web site:
      http://library.veritas.com/docs/305628
--------------------------------------------------------------------------------
Etrack Incident = ET1431527

Description:
   The Job Manger service (NBJM) would fail to shutdown during a patch upgrade.
--------------------------------------------------------------------------------
Etrack Incident = ET1426014
Associated Primary Etrack = ET1410971
Titan cases:  281-419-486

Description:
   Even though a relocation was successful, the expiration did not happen
   even when candidates existed in the DSSU. This would cause nbstserv to
   core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET1430999

Description:
   A change was made to correct an error found in the V_sscanf() function
   call. A comma "," was missing in the function parameter list.
--------------------------------------------------------------------------------
Etrack Incident = ET1444551
Associated Primary Etrack = ET1425282
Titan cases:  281-443-857 291-026-712

Description:
   Disk images were not being expired after the time that was defined in the
   vault profile.
--------------------------------------------------------------------------------
Etrack Incident = ET1427600
Associated Primary Etrack = ET1407472
Titan cases:  320-132-552

Description:
   The bpimmedia -disk_stu <STU> command would return all images that had the
   same absolute pathname and not just the images for the specified Storage
   Unit.
--------------------------------------------------------------------------------
Etrack Incident = ET1414674
Associated Primary Etrack = ET1391153
Titan cases:  311-959-074

Description:
   A change was made to ensure that bperror gives the expected output. It
   would missed reporting on the policy, sanbkupsrv-all-clients.
--------------------------------------------------------------------------------
Etrack Incident = ET1445493
Associated Primary Etrack = ET1446627

Description:
   A change has been added that allows the usage of the HP Command View 7.x
   and 8.x.
--------------------------------------------------------------------------------
Etrack Incident = ET1426474

Description:
   If an error occurs during the initial data load of volumes, the user
   interface should check for error information in the interceptor.  The
   NBSL should send an exception if a fetch fails during an initial
   dataload instead of sending a zero-length sequence.
--------------------------------------------------------------------------------
Etrack Incident = ET1439070
Titan cases:  312-013-527

Description:
   A fix was made to ensure the "Remove device host" is active on the
   NetBackup-Java Administration Console > Media and Device Management >
   Media Server menu.
--------------------------------------------------------------------------------
Etrack Incident = ET1442012

Description:
   Added support for a BMR Master on a Solaris 10 X64 server.
--------------------------------------------------------------------------------
Etrack Incident = ET1446868
Associated Primary Etrack = ET1444948
Titan cases:  240-849-829

Description:
   A change as made to correct an issue that caused NOM reports to not be
   visible in NetBackup 6.5.2 after upgrading from NetBackup 6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET1381806

Description:
   Changed bpdbm to exit on startup if the db_marker.txt file in the
   db/images directory does not exist.  
--------------------------------------------------------------------------------
Etrack Incident = ET1442063
Associated Primary Etrack = ET1439859
Titan cases:  230-605-520 291-158-778

Description:
   The Resource Broker was not be able to release allocation from the database
   or the memory when a job spanned multiple media. No drive leakage was
   observed. It was just the allocation record in database and memory.
--------------------------------------------------------------------------------
Etrack Incident = ET1444727
Associated Primary Etrack = ET1435379
Titan cases:  291-093-475

Description:
   The current command length limit of 1024 was not enough in legacy
   ShadowImage FIM. This command length would cause bpdgclone to fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1447058

Description:
   A nested duplication from an SLP to tape storage units could fail with a
   status 154 if the duplication was targeted to tape storage units that were
   configured with MPX=1.

Workaround:
   If you encounter this issue, confgiure tape storage unit with MPX enabled
   with a value that is greater than 1.
--------------------------------------------------------------------------------
Etrack Incident = ET1398689

Description:
   When a storage unit group that contains different robots is used,
   duplication would fail with a status error 167.
--------------------------------------------------------------------------------
Etrack Incident = ET1445648
Associated Primary Etrack = ET1413974
Titan cases:  240-796-482

Description:
   A fix was made to enable a user to delete critical policies from jnbSA/RAC
   for a catalog backup on a clustered Master server.
--------------------------------------------------------------------------------
Etrack Incident = ET1430034
Associated Primary Etrack = ET1430016
Titan cases:   220-437-078 220-649-926

Description:
   looking for a 6.5.1 binary for "bpbkar core dump causing hot catalog backup
   to fail with a 130"
--------------------------------------------------------------------------------
Etrack Incident = ET1411788
Associated Primary Etrack = ET1411762
Titan cases:  291-047-561

Description:
   The Hot Catalog Backup would intermittently fail with a status code 2
   (error validating NBDB backup in /usr/openv/db/staging).
--------------------------------------------------------------------------------
Etrack Incident = ET1447620
Associated Primary Etrack = ET1444852
Titan cases:  230-592-814

Description:
   The "Include all basic disks" that is specified in the Location of a VAULT
   profile did not include a Disk Staging Storage Unit.
--------------------------------------------------------------------------------
Etrack Incident = ET1413618

Description:
   Keywords that contained spaces were not being read correctly during the
   import from disk and were being displayed incorrectly in the BAR user
   interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1431088
Associated Primary Etrack = ET1367011
Titan cases:  220-477-292 311-928-363

Description:
   Verbosity should be set to 5 for additional logging to occur. This can be
   limited to bpdbm and bpbrm verbosity if desired.
   
   The sender always logs its buffer before sending it via the socket. The
   receiver logs its buffer only if it encounters an error. It will be
   accompanied by a message of the form "wanted x got y.
--------------------------------------------------------------------------------
Etrack Incident = ET1447265

Description:
   Could not add an NDMP host for OST storage servers' direct copy-to-tape
   reader.  The problem was that some vendors use multiple storage server
   names for various interfaces to the same physical machine - and same IP
   address.  If the storage server name was resolvable, for example due to
   an /etc/hosts entry, when the user attempted to add the NDMP host, the DNS
   lookup actually matched it to the storage server machine record. In this
   case, when the user attempted to add the NDMP credentials and errors with
   the message "Credentials already exist for NDMP host <hostname>".
   
   A setting for the EMM server has been added to override this.  In the
   /usr/openv/var/global/emm.conf file, add the following line:
      FORCE_ADD_NDMP_MACHINE=1
--------------------------------------------------------------------------------
Etrack Incident = ET1447160

Description:
   A change was made to the wording of the scheduling shutdown warning message.
--------------------------------------------------------------------------------
Etrack Incident = ET1432407

Description:
   A change was added to ensure the proper message is shown for a Redirected
   restore failure if the backup contains an .avhd file.
--------------------------------------------------------------------------------
Etrack Incident = ET1446408

Description:
   A fix was made to ensure that bpjobd terminates cleanly on Windows systems.
--------------------------------------------------------------------------------
Etrack Incident = ET1155201

Description:
   With NBAC configured, the Vault Reports for the Vault Operator were not
   being displayed in the NetBackup-Java Administration Console. A change was
   made to fix this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1437425

Description:
   The Hitachi_CopyOnWrite FIM was not supported for the USP/USP-V series
   of arrays.
--------------------------------------------------------------------------------
Etrack Incident = ET1226065

Description:
   Solaris clients with "no swap" configured would fail to register with the
   BMR Master server.
--------------------------------------------------------------------------------
Etrack Incident = ET1450240

Description:
   While doing a "Prepare To Restore" operation for a client, the user
   interface would display the following error message:
     "There are no valid SRTs matching client OS are available."

Workaround:
   After an NetBackup server (including BMR Master, BMR Boot servers and
   NetBackup-Java Administration Console) is upgraded to 6.5.4, if a user
   tries to run "Prepare to Restore" for an HP-UX client using the NetBackup
   Administration Console, the SRT list may not appear correctly. It will
   not include those SRT names that already existed before the 6.5.4 upgrade.
   Existing SRT names are not listed even though its hosted HP-UX NetBackup
   client is upgraded to 6.5.4.
   
   Use the following steps to resolve the problem:
   
   1. Logon to the BMR Boot server machine.
   
   2. Rename the SRT directory using the mv command in preparation for a
      delete, edit, and re-import of the SRT. For example, if the
      /srt/my_srt directory contains the SRT named my_srt then, type:
      mv /srt/my_srt /srt/tmp_srt
   
   3. Determine the BMR boot server architecture value. You can use the
      NetBackup Administration Console or the bmrs command.
      - To use the NetBackup Administration Console:
        Under Bare Metal Restore Management, click the Hosts > Boot Servers
        menu. This displays the available boot servers list and their
        information.
          - Check the boot server detail which hosts the required SRT.
          - Note architecture value of the boot server.      
   
      - To use the bmrs command line:
        Run the following command on the Master server:
        bmrs -o query -r database -t bootserver
          - This displays all of the available boot server records.
          - Note the architecture value of the boot server that hosts
            the required SRT.
   
   4. On the boot server,
      A. Edit the /srt/tmp_srt/srtData.xml file. Set the <Architecture> XML
         node value to the same value as the boot server architecture value.
         For example, if node vaulue is <Architecture>PA-RISC</Architecture>
         then set boot server architecture value to
         <Architecture>9000/800</Architecture>.
      B. Edit the /srt/tmp_srt/srtData.txt file. Set the Architecture =
         <boot server architecture value>
   
   5. Go to the NetBackup-Java Administration Console or use the bmrs CLI
      and delete the SRT record. In the current example, delete "my_srt".
   
   6. On the boot server, move the SRT directory name back to its original
      value. For example, mv /srt/tmp_srt /srt/my_srt
   
   7. Import the SRT again using option 4 of the bmrsrtadm CLI on the boot
      server.
   
   8. The SRT should now be listed in the BMR prepare to restore user
      interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1448262

Description:
   The VxVM snapshot device owner ID was changed to root after a Point-in-Time
   rollback.
--------------------------------------------------------------------------------
Etrack Incident = ET1425084

Description:
   When a large number of jobs have run and have not yet been recycled, a PEM
   request to resubmit a job (retry, resume, restart) to NBJM would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1448195
Associated Primary Etrack = ET1426108
Titan cases:  281-419-570

Description:
   The link lines for bptm and bpdm were changed to include the -N option
   for the HP PARISC platform only. This enables bptm to use 2.75 GB instead
   of 1 GB of shared memory on HP systems.
--------------------------------------------------------------------------------
Etrack Incident = ET1442239
Titan cases:  312-018-611

Description:
   If the maximum partially full media was set for a volume pool, and the
   volume pool contained media that was allocated once but for some reason no
   images were written to it, then the job would be queued indefinitely.
--------------------------------------------------------------------------------
Etrack Incident = ET1418373

Description:
   Update the Authorization entries to address an issue that would cause an
   error to occur while creating a new policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1452416

Description:
   Running the command, bpstudel -group, would cause a core dump if it were
   specified without any group name.
--------------------------------------------------------------------------------
Etrack Incident = ET1447692

Description:
   A change was made to address an issue that caused an IBM4000 IR
   snapshot-only backup to fail (no snapshot/flcp).
--------------------------------------------------------------------------------
Etrack Incident = ET1148446

Description:
   When a user backup job failed, the BAR user interface would sometimes
   show the status of the job as a success.
--------------------------------------------------------------------------------
Etrack Incident = ET1446653
Associated Primary Etrack = ET1443574
Titan cases:  220-457-153

Description:
   A change was added to address an issue that caused nbpem to asserts or
   core dump when failed, user-initiated backups were restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET1451465

Description:
   The nbrb -terminate command would sometimes core dump in certain
   situations. The process that was created to stop the nbrb service/daemon
   is the process that would stop.
--------------------------------------------------------------------------------
Etrack Incident = ET1447260
Associated Primary Etrack = ET1387022
Titan cases:  240-747-352

Description:
   A backup of a raw device could end with a status 0 but the files_file
   could contain no information.
--------------------------------------------------------------------------------
Etrack Incident = ET1453529

Description:
   The resource broker (RB) would time out while waiting for an MDS response.
--------------------------------------------------------------------------------
Etrack Incident = ET1446254
Associated Primary Etrack = ET1441875
Titan cases:  281-426-385

Description:
   PureDisk Exported images would fail to restore or verify because some of
   directories were cataloged incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET1442301

Description:
   Occasional jobs would fail with an invalid jobid returned from NBJM.
--------------------------------------------------------------------------------
Etrack Incident = ET1451023

Description:
   The NetBackup-Java Administration Console would show only the Client user
   interface when only the username is used to log into the NetBackup server.
--------------------------------------------------------------------------------
Etrack Incident = ET1453215
Titan cases:  240-850-063

Description:
   On the NetBackup-Java Administration Console, the Images On Media and the
   Images on Tape reports would display inaccurate information after all of the
   images on a client or a tape were expired.
--------------------------------------------------------------------------------
Etrack Incident = ET1426891
Associated Primary Etrack = ET1455343

Description:
   The QLogic HBA Driver ql2300.sys with a version greater than "9.1.4.10"
   are not compatible with the BMR-Windows Restore Environment (WindowsPE).
   The user receives a message similar to the following , when restoring a
   BMR-Windows Client that uses this driver.
      "ql2300.sys is corrupted"
   
   A BMR backup job will end with a status '1', (for example, "Partially
   Successful") if the client is using a QLogic qla2300 driver of version
   greater than "9.1.4.10".

Workaround:
   To resolve4 this issue, add a qla2300.sys driver of version 9.1.4.10 or
   earlier to the SRT.
--------------------------------------------------------------------------------
Etrack Incident = ET1436594

Description:
   The tape list report for a media ID with less than six characters returns
   an invalid command parameter error. This issue occurs while communicating
   with a back-level media server (invoking bptm) through the bpcd protocol.

Workaround:
   If you encounter this issue, manually run bptm -mlist -ev A1234 -raw on
   a media server.
--------------------------------------------------------------------------------
Etrack Incident = ET1453605

Description:
   The NetBackup Resource Broker, nbrb, would sometimes return an incomplete
   allocation to the Job Manager, nbjm, if the EMM was unresponsive. This
   would cause the job to fail with an nbjm internal error.
--------------------------------------------------------------------------------
Etrack Incident = ET1446792

Description:
   An issue existed that caused the following warning message to occur in the
   Activity M<onitor:
      "Warning bpdm(pid=5468) failure logging message"
--------------------------------------------------------------------------------
Etrack Incident = ET1441557
Associated Primary Etrack = ET1242536
Titan cases:  240-746-395

Description:
   DB agents timeout waiting for server status at the end of the backup or
   restore.  This change will allow development to send out an EEB faster when
   this is needed to work around the real issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1456221

Description:
   On the NetBackup-Java Administration Console, a VM name could not be added
   manually while creating a policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1416785
Associated Primary Etrack = ET1292708
Titan cases:  291-002-278

Description:
   The command, bpdbm -consistency 2 would result in a core dump.  A change
   has been made to address and fix this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1451244

Description:
   An issue existed that caused a large amount of data to be written into
   the Job's Detailed Status while taking backup.
   
   A change was made to the Activity Monitor code to make it more consistent
   with bpdbjobs and ensure that the Job Details displayed from the user
   interface are as verbose as bpdbjobs.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1379510
Titan cases:  290-843-085

Description:
   The "Exclude:" section has been removed from the output of the
   bppllist -L command.  This section is populated by deprecated database
   files that NetBackup does not use, therefore, the output has no
   relevance.
--------------------------------------------------------------------------------
Etrack Incident = ET1457644

Description:
   When starting a backup of any VM it could take a few attempts to start
   (typically 5 minutes). The Job Details page would show the following error
   message:
      "Error bpbrm[pid] cannot connect to [VM's name], status = 25"
--------------------------------------------------------------------------------
Etrack Incident = ET1402422
Associated Primary Etrack = ET1501206
Titan cases:  281-470-007 220-395-582

Description:
   A change was made to enable extended logging to help in debugging
   performance issues.  This logging was enabled by setting VERBOSE to 6 or
   higher.
--------------------------------------------------------------------------------
Etrack Incident = ET1456424

Description:
   A redirect restore works successfully even if the storage mentioned does
   not have enough space.
--------------------------------------------------------------------------------
Etrack Incident = ET1262599
Associated Primary Etrack = ET1244934
Titan cases:  240-748-094

Description:
   NetBackup silently truncates certain backup properties, such as keyword,
   when they are too long. Such values now trigger an error.
--------------------------------------------------------------------------------
Etrack Incident = ET1446468
Associated Primary Etrack = ET1395927
Titan cases:  230-571-131 320-171-378

Description:
   All NetBackup 6.5 disk types (AdvancedDisk, SharedDisk, PureDisk, and
   OpenStorage) would fail on FlashBackup restores.

Workaround:
   If you encounter an issue like this, duplicate the image to tape and
   restore it from the tape copy.
--------------------------------------------------------------------------------
Etrack Incident = ET1452256
Associated Primary Etrack = ET1452072
Titan cases:  240-834-385

Description:
   A change was made to address an issue that would cause bmrprep to core
   dump if the client had an unsupported SVM configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET1459294

Description:
   A change has been made to address an issue that caused bptm to generat
   a core dump on the media server.
--------------------------------------------------------------------------------
Etrack Incident = ET1399839

Description:
   A bpbackup user backup with a -ct specified that did not match the policy,
   would not fail with a 245 error, however it should have failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1455096
Associated Primary Etrack = ET1451420
Titan cases:  291-109-607 312-107-378

Description:
   BMR would fail to do Point in Time restores for the client if the intended
   backup image has NetBackup clients installed in some different directory
   than the latest NetBackup client setup.
   
   This failure would happen even if the directory or the sub-directory name
   case changed. In addition, it would happen while importing the Point in
   Time client BMR configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET1463891
Associated Primary Etrack = ET1460990
Titan cases:  220-487-296

Description:
   A nawk syntax error caused migcons to fail with migtrans failure 22.
   
   
--------------------------------------------------------------------------------
Etrack Incident = ET1463875
Associated Primary Etrack = ET1463817
Titan cases:  220-487-550

Description:
   Manipulation of a Solaris client configuration would take a very long time
   due to excessive disk entries in database tables. The large number of
   entries was caused by a client configuration that contained a large number
   of DMP disk paths.
--------------------------------------------------------------------------------
Etrack Incident = ET1454298

Description:
   A change was added to present the "Configuration Architecture" label as a
   read-only value on the Prepare to Restore dialog box. The change ensures
   that an error message appears if no SRT's found for a selected SRT.
--------------------------------------------------------------------------------
Etrack Incident = ET1465331

Description:
   A change was added to make the eviction time out configurable as well as
   fixing an issue with the FATManager eviction.
--------------------------------------------------------------------------------
Etrack Incident = ET1395101

Description:
   The nbdevquery -liststs command gives the error, "cannot open debug file:
   Permission denied (13)" by NBAC for non-admin user.
--------------------------------------------------------------------------------
Etrack Incident = ET1465033

Description:
   A change was added to ensure that this Release Update contains added
   support for solution enabler 6.5 for EMC Symmetrix.
--------------------------------------------------------------------------------
Etrack Incident = ET1453874
Associated Primary Etrack = ET1452185
Titan cases:  230-614-582

Description:
   The vltadm did not always save schedules changes correctly into the
   vault.xml.
   
   If you use vltadm to edit/configure the vault profiles, the
   edit/configure options of the profile selection list would not save the
   selected items correctly into the vault.xml.

Workaround:
   If you encounter an issue like this, use the NetBackup-Java (or Windows)
   Administration Console to configure the image selection of vault profile.
--------------------------------------------------------------------------------
Etrack Incident = ET1422459
Associated Primary Etrack = ET1401897
Titan cases:  320-127-406

Description:
   Drive down alerts reporting drive as clear although drive still down.
--------------------------------------------------------------------------------
Etrack Incident = ET1412607
Associated Primary Etrack = ET1405148
Titan cases:  291-049-971

Description:
   Exchange 2007 Instant Recovery backups would fail with a status 156 error.
   This issue occurred on Exchange 2007 Instant Recovery backups that used
   hardware-based VSS to an IBM DS8300 ARRAY.  The issue would manifest
   itself on all Exchange clients.
   
   Backups were successful if only one or two storage groups were configured
   in the policy. However, if the Microsoft Information Store directive was
   invoked (which can trigger backups for 10+ storage groups in some cases)
   the backups would fail with a status 156.

Workaround:
   To avoid this issue, skip vfi_analyze call to get the VSS HW snapshot
   UDID information.
--------------------------------------------------------------------------------
Etrack Incident = ET1461305
Associated Primary Etrack = ET1427870
Titan cases:  291-079-760

Description:
   In the Data View of the NOM user interface, the Media report would show
   the active media in volume pool number 0 even if a different volume pool
   should have been used.
--------------------------------------------------------------------------------
Etrack Incident = ET1458226

Description:
   The vnet_connect would retry infinitely for Address Not Available errors.
   This would result in very large log files.
--------------------------------------------------------------------------------
Etrack Incident = ET1465532

Description:
   The wrong information was being displayed in the Job's Detailed Status
   while taking backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1252404

Description:
   In the NetBackup-Java Administration Console, the Snapshot Policy
   Configuration Wizard did not contain enough details about the FlashCopy
   snapshot methods.  More detailed information is needed.
--------------------------------------------------------------------------------
Etrack Incident = ET1259890

Description:
   The Policy change alert policy has been enhanced to alert a user if a
   policy is deleted.
--------------------------------------------------------------------------------
Etrack Incident = ET1461863
Associated Primary Etrack = ET1461612
Titan cases:  281-439-624

Description:
   If Advanced Duplication rules were configured in a Vault Profile,
   duplication of images that did not match with any of the Backup servers
   was not performed.
--------------------------------------------------------------------------------
Etrack Incident = ET1450234

Description:
   bpstuadd would not add a storage unit (STU) if the -M options was
   specified without any value at the end of the command. A change was added
   to ensure that the command fails if the -M is specified without any value
   irrespective of where it is specified.
--------------------------------------------------------------------------------
Etrack Incident = ET1449178
Associated Primary Etrack = ET1442418
Titan cases:  230-600-278

Description:
   A change was made to add "handling path" messages in bperror for scripted
   monitoring of multistream backup success in NetBackup 5.1 and earlier
   releases.
--------------------------------------------------------------------------------
Etrack Incident = ET1453422
Associated Primary Etrack = ET1409915
Titan cases:  240-820-679

Description:
   MS SQL backups were running twice when an automatic backup was kicked off.
   This issue pertains to Windows master only.

Workaround:
   Be careful to spell policy names with the correct case when you perform
   immediate backups using the bpbackup command.
--------------------------------------------------------------------------------
Etrack Incident = ET1449157
Associated Primary Etrack = ET1446259
Titan cases:  281-488-492 312-027-940

Description:
   During the generation of Recovery report, Vault was attempting to query
   media records with media IDs that belonged to Advanced Disk (OST) based
   storage units (for example, @aaaab).
   A change was made to ensure that Vault does not query media records with
   media IDs that belong to Advanced Disk based STUs.
--------------------------------------------------------------------------------
Etrack Incident = ET1458420
Associated Primary Etrack = ET1455909
Titan cases:  291-113-436

Description:
   A fix was made to address an issue that caused the nbjm.exe application
   to fault under a heavy load.
--------------------------------------------------------------------------------
Etrack Incident = ET1432148
Associated Primary Etrack = ET1391305
Titan cases:  220-374-967 320-135-491

Description:
   Calendar incremental backups would not run on the same day as calendar
   full backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1405180

Description:
   The bpdm process was not terminated when the Optimized Duplication jobs
   were canceled from the Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET1469272

Description:
   "VERITAS" specific environment variables are no longer sent to the filer.
   
   Before this fix, the following environment variables were sent to the
   filer, causing some filers to return a warning message.
     VERITAS_XFL=2
     VERITAS_TAR_HDR_SIZE=512
   
   A change was made to ensure that these variables are no longer sent to
   the filer; thus, eliminating the warning messages that they caused.
--------------------------------------------------------------------------------
Etrack Incident = ET1470340

Description:
   When shutting NetBackup down, the shutdown script would sometimes display
   messages concerning the termination of the nbpemreq command. A change was
   made to ensure nbpemreq terminate quickly if nbpem is not up. In
   addition, a change was made to the request timeout value, ensuring that it
   is long enough so that data being transfered between nbpem and nbpemreq
   does not time out if nbpem is busy.
--------------------------------------------------------------------------------
Etrack Incident = ET1460964

Description:
   A multiple copy duplication would hang if a resource for the first copy
   could not be obtained.  This would only occur if the source and destination
   copies were on the same media server.

Workaround:
   To work around this issue, disable the shared memory duplications by
   creating the following file on the master server:
   
   UNIX: /usr/openv/netbackup/NOSHMDUP
   Windows: VERITAS\NetBackup\NOSHMDUP
--------------------------------------------------------------------------------
Etrack Incident = ET1463890

Description:
   An issue existed that caused bpinst to core dump when using the options:
   "-ENCRYPTION -policy_names xx". A change was made to bpinst to not free
   the client list which was allocated on the stack.
--------------------------------------------------------------------------------
Etrack Incident = ET1468581

Description:
   A fix was made to address an issue that caused bpbrm to produce a
   misleading, "cannot connect" error message.
--------------------------------------------------------------------------------
Etrack Incident = ET1462054
Titan cases:  220-549-599

Description:
   NDMP backup would fail with an error code 114.
   The ndmpagent log would show the following message:
     "Expected remainder to be 0. Remainder = 512"
   

Additional Notes:
   This problem occurs only for NDMP Local or NDMP 3-way.  
--------------------------------------------------------------------------------
Etrack Incident = ET1428284

Description:
   A Snapshot backup would take too long because of multiple "dtaputil
   discover" commands.
--------------------------------------------------------------------------------
Etrack Incident = ET1466044

Description:
   While editing a configuration, the Map/Unmap options might be disabled for
   SVM volumes.
--------------------------------------------------------------------------------
Etrack Incident = ET1448206 ET1481250 ET1529072
Associated Primary Etrack = ET1446176
Titan cases:  230-611-161 240-947-163

Description:
   NetBackup would take a long time to fail over if any processes took a
   long time to shutdown. A new enhancement has been added, bpclusterkill,
   that ensures a time-bound way of stopping all NetBackup processes.
--------------------------------------------------------------------------------
Etrack Incident = ET1446401 ET1481284

Description:
   On Windows hosts, an invalid handle was being passed to closesocket. The
   Appverifier was used to diagnose the problem. This issue has been resolved.
--------------------------------------------------------------------------------
Etrack Incident = ET1446147
Associated Primary Etrack = ET1421488
Titan cases:  312-021-840

Description:
   You can avoid a core dump by removing a reference to a pointer that is
   meaningless. You should allow -crawlreleasebyname to run on a non-SSO
   drive, however vmoprcmd must be run on the server with the drive
   configured.

Workaround:
   If you encounter an issue like this, do not run -crawlreleasebyname on
   non-SSO drives.
--------------------------------------------------------------------------------
Etrack Incident = ET1466545

Description:
   On Solaris, the following message would appear in the progress log for a
   snapshot backup:
      process_VMM_entry: WRN - Attempt to add_drv dlmfdrv failed; status=1
   
   This message is purely of a diagnostic nature and should not have
   appeared in the progress log. A fix has been made to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1450564
Associated Primary Etrack = ET1441619
Titan cases:  240-845-210

Description:
   Restore of individual files from spanned volumes would fail if the first
   file was not on the first volume.
--------------------------------------------------------------------------------
Etrack Incident = ET1466528

Description:
   If a job was suspended and canceled before it had completed the suspend
   processing, the job would terminate prematurely while the STU resource
   was still in use.
--------------------------------------------------------------------------------
Etrack Incident = ET1464016

Description:
   If a suspended shared disk job is resuming and the original media server
   is down, the job waits for down media server instead of using an available
   media server.

Workaround:
   If you encounter an issue like this, restore the connectivity between
   master and media server on which the job was started.
--------------------------------------------------------------------------------
Etrack Incident = ET1452281

Description:
   NOM reports services were down on Media servers, when the services were
   only expected to be running on the Master servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1469841

Description:
   bmrsrtadm would fail while preparing boot files after adding a VxVM package
   to the SRT if the bootserver was running on a host that had only VxVM DGs.
--------------------------------------------------------------------------------
Etrack Incident = ET1470826

Description:
   The command bmrprep (Prepare To Restore) would sometimes core dump when
   encountering a badly formatted client configuration that utilizes VxVM.  

Workaround:
   If you encounter this issue, edit the configuration and do not map the
   offending disk group so that it is not referenced when running "Prepare To
   Restore".
--------------------------------------------------------------------------------
Etrack Incident = ET1421534

Description:
   Multiple duplication jobs would hang with the following error message in
   job details:
   
      db_IMAGEreceive() failed: unexpected message received (43)
--------------------------------------------------------------------------------
Etrack Incident = ET1460587

Description:
   When a policy is created for Hot catalog backup with multiple copies,
   only one job should be created for the parent job.
--------------------------------------------------------------------------------
Etrack Incident = ET1439971

Description:
   A duplication job was not killed even though the job failed with status 50.
--------------------------------------------------------------------------------
Etrack Incident = ET1467900

Description:
   The bysyncinfo -add_paths command would not handle a localized directory
   correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET1466832

Description:
   The nbu_snap snapshot method would fail when supplied with a block device
   path in the Backup Selections list. This has been corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET1471621
Associated Primary Etrack = ET1471570

Description:
   The bpmedialist -mcontents command would sometimes dump core on Solaris x86
   systems.

Workaround:
   If you encounter this issue, specify a mediaserver in the bpmedialist
   -mcontents command, for example, bpmedilist -mcontents -h <hostname>.
   
   The command will only dump core if you do not specify a media server.
   Problem is specific to a Solaris x86.
--------------------------------------------------------------------------------
Etrack Incident = ET1468877

Description:
   When a suspended job was resumed the active start time was before the
   start time of the job.
--------------------------------------------------------------------------------
Etrack Incident = ET1461593

Description:
   In the NetBackup-Java Administration Console, the "Restore Job Details"
   would not show the "Current Kilobytes written" and other information.
   
   (In a Windows environment, the MFC user interface, did show the "Restore Job
   Details" information.)
--------------------------------------------------------------------------------
Etrack Incident = ET1428325

Description:
   The message, "database backup is currently disabled," appeared in the
   Problems report even when a scheduled hot catalog backup was configured.
   The message has been changed to, "NetBackup Catalog Backup is currently
   disabled" rather than the current reference to "database backup".  
--------------------------------------------------------------------------------
Etrack Incident = ET1469444
Titan cases:  312032203

Description:
   Duplication jobs could fail with a status 190 when validating a copy that
   contained a large number of fragments.

Workaround:
   To avoid this issue, increase the checkpoint time interval to create larger
   fragment sizes and fewer fragments per image. Also increase the fragment
   size configuration setting.
--------------------------------------------------------------------------------
Etrack Incident = ET1471613

Description:
   When a job submitted using the bpbackup command fails due to incorrect
   arguments (such as the policy, client, or schedule are bad), it appeared
   in the Activity Monitor with incorrect start and end times and no user or
   group was specified.
--------------------------------------------------------------------------------
Etrack Incident = ET1463937

Description:
   Running an NDMP policy with a filelist that specified one set directive
   for each entry in the file list would failed when the second directive was
   included in both streams.  The file list did not start with a NEW_STREAM
   directive, so each entry in the file list was treated as a separate stream.
--------------------------------------------------------------------------------
Etrack Incident = ET1465258
Associated Primary Etrack = ET1450724
Titan cases:  320-141-952

Description:
   NetBackup master servers were going partially online and offline daily
   making the user restart nbsl on master server to get back online.
--------------------------------------------------------------------------------
Etrack Incident = ET1432471

Description:
   A change was made to address an issue with policy and client group creation.
--------------------------------------------------------------------------------
Etrack Incident = ET1471948

Description:
   The BAR user interface would display files with a "Do Not" symbol while
   browsing the VMWare Mapped FullVM backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1464015 ET1476600 ET1482673 ET1482676 ET1480286 ET1587338
ET1602790 ET1600654
Associated Primary Etrack = ET1634433
Titan cases:  220-648-856

Description:
   Changes were made to the networking infrastructure inside of NetBackup to
   support the Strong Host Model, which is enabled by default in Windows
   Vista in those instances where REQUIRED_INTERFACE is set, or NetBackup is
   clustered. Please see rfc1122 for details on the weak and strong host
   models.
--------------------------------------------------------------------------------
Etrack Incident = ET1474403
Associated Primary Etrack = ET1427177
Titan cases:  320-136-423

Description:
   A fix was made to address an issue that caused a status 98 error to occur
   on an NDMP backup when spanning to the next media.  That would produce an
   "error code 7 (NDMP_IO_ERR)" message.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1448396
Associated Primary Etrack = ET1446406
Titan cases:  281-482-999 312-020-096

Description:
   A change was made to correct the available shared memory size for bptm.
--------------------------------------------------------------------------------
Etrack Incident = ET1414295

Description:
   When clearing an alert the trap goes with the same severity (Informational)
   as that of the raised alert. This enhancement ensures that user can
   configure the severity for a cleared alert.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1408851
Associated Primary Etrack = ET1398889
Titan cases:  320-127-406

Description:
   A change was made to address an issue with when the time is counted for
   a job that is hung.  
--------------------------------------------------------------------------------
Etrack Incident = ET1412268
Associated Primary Etrack = ET1411107
Titan cases:  230-590-313

Description:
   A change was made to eliminate a 15 second mount delay on TLD robotics
   on an AIX platform.
--------------------------------------------------------------------------------
Etrack Incident = ET1458872
Associated Primary Etrack = ET1318125
Titan cases:  220-340-938

Description:
   If a large file list was submitted using a user-backup request, NBPEM would
   crash.

Workaround:
   To resolve this issue, reduce the size of the file list.
--------------------------------------------------------------------------------
Etrack Incident = ET1473860

Description:
   A change has been made to add a command line option to nbpemreq to connect
   to nbpem on another master server. You could use this option with VBR for
   data collection.
--------------------------------------------------------------------------------
Etrack Incident = ET1428408

Description:
   When backing up multiple VxVM volumes with a Snapshot Client policy, the
   owner and group IDs was not being set on all cloned volumes. This has been
   corrected.
--------------------------------------------------------------------------------
Etrack Incident = ET1465634

Description:
   If an attempt was made to restore from a FlashBackup-Windows image to a
   UNIX client, the tar would crash.
--------------------------------------------------------------------------------
Etrack Incident = ET1474475

Description:
   NBJM would crash while starting a lifecycle job (bpduplicate) on a
   Windows IA64 platform.
--------------------------------------------------------------------------------
Etrack Incident = ET1437956

Description:
   A change was made to remove the restriction that a backup selection list
   comprise all the LUNs in any consistency group that is touched by the
   backup selection list.  
--------------------------------------------------------------------------------
Etrack Incident = ET1461478

Description:
   A fix was made to address an issue that caused a Snapvault restore to fail
   with an internal error 175.
--------------------------------------------------------------------------------
Etrack Incident = ET1465728
Associated Primary Etrack = ET1459357
Titan cases:  240-857-357

Description:
   The bpretlevel on a Linux system showed "week" instead of "1 week". A
   change was made to correct a missing Linux command that ensures a number
   appears before the number of weeks of retention. The following is an
   example of the actual output followed by the corrected output.
   
   Retention  Retention  Equivalent
     Level     Period       Days
   --------- ----------- ----------
       0      week          7
       1      weeks         14
       2      weeks         21
       3      month         31
       4      months        62
       5      months        93
       6      months        186
       7      months        279
   
   This fix ensures the following corrected output.
   
   Retention  Retention  Equivalent
     Level     Period       Days
   --------- ----------- ----------
       0     1 week         7
       1     2 weeks        14
       2     3 weeks        21
       3     1 month        31
       4     2 months       62
       5     3 months       93
       6     6 months       186
       7     9 months       279
--------------------------------------------------------------------------------
Etrack Incident = ET1438645

Description:
   Currently, the mount command and the fsck command use the same execPipe
   object. If either of the commands time out, then clean up of that process
   does not take place. In addition, the fsck command can run long so the
   timeout has been increased to ensure that the process gets cleaned up
   correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET1433549

Description:
   A change has been added to removed bprsh in Vault Java user interface.
   The use of bprsh has been replaced with bpcd for all vault functions. In
   addition, The Release Updates adds the use of vlteject over vltrun for
   vault reports.
--------------------------------------------------------------------------------
Etrack Incident = ET1475026

Description:
   A change has been made to ensure that the Vault Recovery report has a data
   range from 0 to 999.
--------------------------------------------------------------------------------
Etrack Incident = ET1475814

Description:
   The Create new vault profile dialog box would not come up when a NetBackup
   6.5.4 client was connected to a NetBackup 6.5.1 master.
--------------------------------------------------------------------------------
Etrack Incident = ET1433497

Description:
   When running under NBAC it was possible for a user to change some of the
   policy attributes when accessed in a particular way. A fix has been added
   to address this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1452458
Associated Primary Etrack = ET1449282
Titan cases:  320-139-917

Description:
   Oracle RMAN restores would fail when using the SAN FAT client.
--------------------------------------------------------------------------------
Etrack Incident = ET1475916

Description:
   A log message in the tar had a duplicate number.
--------------------------------------------------------------------------------
Etrack Incident = ET1428729
Associated Primary Etrack = ET1399901
Titan cases:  281-406-867

Description:
   Imports of VMWare Type 2 TAPE backups were being imported as VMWare Type 0.

Workaround:
   If you encounter this issue, manually change the VMware type in the
   header file.  
--------------------------------------------------------------------------------
Etrack Incident = ET1438822

Description:
   The Lifecycle CLI nbstl should not allow a "Capacity Managed" retention
   type for disk destinations that do not enabled this capability.
   
   For "Tape" destinations, "Capacity Managed" is not allowed.
   For "Disk" destinations, if the STU has the Capacity Management
   capability, this STU is allowed to be configured as "Capacity Managed".
   If it does not have the Capacity Management capability, it is refused.
--------------------------------------------------------------------------------
Etrack Incident = ET1450268

Description:
   Under certain error conditions one of the bptm processes for duplication
   would get an error, but the other bptm process would not be notified, and
   the duplication would hang while bpduplicate waited for the exit status.
--------------------------------------------------------------------------------
Etrack Incident = ET1076978

Description:
   A user-initiated backup would fail for Exchange VSS offhost or CCR passive
   backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1475313

Description:
   A change was made to address a communication problem between NBSL and NOM
   (Multi-NIC and Required_Interface). The NBSL was communicating on the
   Required_Interface NIC. NOM was connected to the "other" NIC. This meant
   callbacks, updates, and events were not reaching NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET1460851
Associated Primary Etrack = ET1234707
Titan cases:  230-505-333 230-621-131 291-089-942

Description:
   A fix was made to address an issue that caused an error 145 to occur
   during an unlock using the Advanced Client ShadowImage method. (It took
   more than 240 seconds to do VX_THAW which caused a timed out and failure.)  
--------------------------------------------------------------------------------
Etrack Incident = ET1476962

Description:
   Restoration of an SVM-named disk set would fail after mapping it from an
   EMC PowerPath disk to an internal disk.  

Workaround:
   Map the local database replica before the named disk set, or unrestrict
   the disk that the local database replica exists on.
--------------------------------------------------------------------------------
Etrack Incident = ET1473499

Description:
   The snapshot job for a SharePoint policy would show an invalid error
   number(-9999) in the Job details.
--------------------------------------------------------------------------------
Etrack Incident = ET1417504
Associated Primary Etrack = ET1417039
Titan cases:  281-417-280

Description:
   NetBackup 6.5.2 Java Console for Windows would incorrectly parse Portuguese
   characters with the system locale set to pt_BR.
--------------------------------------------------------------------------------
Etrack Incident = ET1477603
Associated Primary Etrack = ET1477338
Titan cases:   281-454-498 312-052-793

Description:
   A change has been added to ensure that HP-IA X64 FlashBackup restores are
   working in this Release Update.  
--------------------------------------------------------------------------------
Etrack Incident = ET1474586
Associated Primary Etrack = ET1474515
Titan cases:  320-154-014

Description:
   This Release Update contains a new disable_quiesce parameter that enables
   a user to disable Snapshot Quiesce on certain VMs.  This new parameter
   was added to the FIM.
--------------------------------------------------------------------------------
Etrack Incident = ET1452344
Associated Primary Etrack = ET1368270
Titan cases:  240-779-778

Description:
   Older versions of NetBackup could create a bad fragment on tape.  The
   fragment had some TIR data followed by normal backup data. These two
   types of data should have been written to separate fragments.
   
   This modification allows BPTM to recover the normal backup data from one
   of these malformed fragments.
--------------------------------------------------------------------------------
Etrack Incident = ET1478495
Associated Primary Etrack = ET1474907
Titan cases:  312-000-892

Description:
   NetBackup 6.5 introduced an error that may be logged in a servers syslog.
   This error reports a Reservation Conflict, which does not actually exist.
--------------------------------------------------------------------------------
Etrack Incident = ET1452175
Associated Primary Etrack = ET1449731
Titan cases:  220-463-516

Description:
   The NetBackup-Java Administration Console would display an invalid
   Storage unit and it could not be deleted. A change was made that enables
   a user to delete the Storage unit from the console.
--------------------------------------------------------------------------------
Etrack Incident = ET1477173

Description:
   A mirrored SVM disk set was still mirrored after a restore despite being
   auto-mapped with a "Simplify VG" option.
--------------------------------------------------------------------------------
Etrack Incident = ET1372973

Description:
   A BMR Prepare To Restore or Restore would fail because of anonymous disks
   (disks with no name) that were in the BMR Linux Client Configurations. This
   problem was seen when the host was connected to a console appliance that
   provided such virtual devices as Avocent or Raritan.

Workaround:
   In absence of the above fix, the following workaround could be used in some
   cases:
   1. Restricting the anonymous disks fails since the name field is blank.
   2. Create a copy of the configuration and use the "unmap all" option for
      disks.
   3. Map only the required system disks and use this configuration for
      restoring the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1478915

Description:
   The job details in the bpdbjobs output (with -all_columns) would show
   misleading text for the file path being written.
--------------------------------------------------------------------------------
Etrack Incident = ET1479387

Description:
   This Release Update adds support of NDMP on HP-UX IA64 and Solaris x86
   platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET1475161
Associated Primary Etrack = ET1249737
Titan cases:  311-876-817

Description:
   The volume cleanup within bpdm was exceeding fifty minutes and exited with
   a status 41 error.

Workaround:
   If bpdm exits after exceeding fifty minutes, execute the command,
   nbdelete -allvolumes again.
--------------------------------------------------------------------------------
Etrack Incident = ET1461116

Description:
   Added support for Catalog Backup and Restore operations to OpenStorage
   Disk Pools.
--------------------------------------------------------------------------------
Etrack Incident = ET1479108

Description:
   A change has been made to address an issue that caused a system error to
   occur (Status 130) while running reports.  
--------------------------------------------------------------------------------
Etrack Incident = ET1477142
Associated Primary Etrack = ET1469083
Titan cases:  240-862-746

Description:
   Unsupported disk devices on Linux would cause bmrd to core dump while the
   configuration was being imported.
--------------------------------------------------------------------------------
Etrack Incident = ET1231756

Description:
   A problem occurred when /usr/openv/netbackup/bin/bptpcinfo - x client_name
   failed to run on the Master/Media server. This command used bprsh which is
   no longer supported due to security concerns.

Workaround:
   To avoid this issue, make the disks visible to the media server, or
   manually enter the entries in the media server 3pc.conf file.
--------------------------------------------------------------------------------
Etrack Incident = ET1126065

Description:
   nbftsrv_config would fail on Linux machines with QLogic SCSI adapters.

Additional Notes:
   nbftsrv_config was always attempting to remove the qla2xxx driver that
   is required by both the qla2300 and qla2400 QLogic FC HBA drivers and
   various QLogic SCSI HBA drivers.  nbftsrv_config should not remove the
   qla2xxx unless it has removed all of the drivers depending on qla2xxx.
   Without the proper checks, the attempt to remove qla2xxx would fail on
   machines with QLogic SCSI adapters and fail to complete its work leaving
   the machine without QLogic FC HBA drivers installed and without
   installing the Symantec qla2300_stub driver required for nbhba mode.  
--------------------------------------------------------------------------------
Etrack Incident = ET1479559
Associated Primary Etrack = ET1473938
Titan cases:  230-641-898 240-870-211 320-181-976

Description:
   Client machines running Solaris 10 Update 6 cannot be restored using Bare
   Metal Restore.

Additional Notes:
   The layout of the Solaris 10 installation media has drastically changed
   with the new Update 6. Additionally, the boot methodology of the system
   has also changed so that it is similar in nature to Solaris on the X86
   platform.
   
   It is important to note that to create a Shared Resource Tree that is
   Solaris 10 Update 6, the Boot Server must also be at Solaris 10 Update 6.
   This version of Boot Server can also host a legacy Solaris 10 SRT and any
   others below Update 6. This is a standard convention that BMR has always
   adhered to.
--------------------------------------------------------------------------------
Etrack Incident = ET1480041

Description:
   A fix has been made to address an issue that caused NBPEM to core dump if it
   was unable to obtain the configuration information during startup.
--------------------------------------------------------------------------------
Etrack Incident = ET1467989

Description:
   Some HP clients may experience tar crashes after resuming from checkpoint
   restarts during restore operations. This issue affects HP clients that do
   not have /usr/lib/vxfsutil.so from a VxFS 5.0 or later installed.

Workaround:
   Perform restore operations with checkpoint restart disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET1469706

Description:
   If one image has multiple fragments and the second copy's retention level
   is higher than the first one, bpverify would hang if the user uses bpverify
   to verify the second copy.
--------------------------------------------------------------------------------
Etrack Incident = ET1466996

Description:
   A zero-hour frequency could be set on in the NetBackup-Java Administration
   console. A change has been made to only allow a non-zero value to be set.
--------------------------------------------------------------------------------
Etrack Incident = ET1460837
Associated Primary Etrack = ET1445246
Titan cases:  220-461-434

Description:
   Changes were made to nbjm and pem to address an nbpem asserted/core dump
   issue in SelectionListPair.
   
   A change was made to nbjm to ensure the resume-preprocess call is made
   for the appropriate situation. In addition, a change was made to pem to
   fail the job if an incorrect process call is received.  
--------------------------------------------------------------------------------
Etrack Incident = ET1468318
Associated Primary Etrack = ET1418456
Titan cases:  291-065-387

Description:
   An option was added to restore pre NetBackup 6.5.2 predict behavior.
--------------------------------------------------------------------------------
Etrack Incident = ET1464701

Description:
   Changes were made to improve the efficiency of the code, particularly
   when using the ExecPipe object. These changes ensure that the existing
   ExecPipe object is closed before reusing it.
--------------------------------------------------------------------------------
Etrack Incident = ET1481159
Associated Primary Etrack = ET1481084
Titan cases:  291-112-750

Description:
   MPX was not being used with ITC under certain conditions. Jobs were queued
   instead of being run on MPX storage units in cases where a copy was dropped.

Workaround:
   To resolve this issue, fix the condition that is causing the copy to fail
   (for example, no media, drive down, and so on).
--------------------------------------------------------------------------------
Etrack Incident = ET1480280

Description:
   NBJM would core dump while reading a JobParams file from a previous
   NetBackup version when the contents of the Jobparams file had changed
   between the NetBackup versions.
--------------------------------------------------------------------------------
Etrack Incident = ET1461993
Associated Primary Etrack = ET1443499
Titan cases:  320-136-621

Description:
   Manually executing a bpduplicate process on a media server using inline
   tape copy would result in status code 805 failures.
--------------------------------------------------------------------------------
Etrack Incident = ET1482660

Description:
   UNIX bpbkar would core dump if the following were true:
    - A backup was using compression
    - The logging was enabled
    - bpbkar ran into a file with an exact size of 4 GB or a multiple thereof.

Workaround:
   If you encounter an issue similar to this, disable the logging.
--------------------------------------------------------------------------------
Etrack Incident = ET1478919

Description:
   The Detailed Status field in the Activity Monitor's Backup Jobs Details
   page would show the wrong information regarding the path where it is
   writing data.
--------------------------------------------------------------------------------
Etrack Incident = ET1300129
Associated Primary Etrack = ET1705726
Titan cases:  220-590-863

Description:
   The FT server would create a target device with a host name that was fully
   qualified. A host name that is fully qualified would cause an error in the
   San Client because it could not be matched to the FT server.
--------------------------------------------------------------------------------
Etrack Incident = ET1463877

Description:
   A fix was made to change an incorrect Copyright Year that was found
   during a 2008 Audit script, in a string.
--------------------------------------------------------------------------------
Etrack Incident = ET1458282
Associated Primary Etrack = ET1453232
Titan cases:  240-866-942 312-049-009

Description:
   Database Advanced Client backups would fail (or hang) and not work with a
   SAN Client Fiber Transport Service.  This problem would occur when using
   an Oracle, DB2, SAP, or SQL server.
--------------------------------------------------------------------------------
Etrack Incident = ET1439713

Description:
   A status 23 error and possible exception would occur in the bpbkar32.exe
   executable when attempting an Exchange Granular backup with a
   pre-NetBackup 6.5.3 client or media server.

Additional Notes:
   The appropriate error would be logged to the Activity Monitor instead and
   never execute the backup job to the client.
--------------------------------------------------------------------------------
Etrack Incident = ET1481101
Associated Primary Etrack = ET1478396
Titan cases:  220-423-997

Description:
   Full Flashbackups would fail with the following error message if the file
   system was UFS and there were sockets in the file system.
   
     inode entries missing directory info: File: nbe_cat_c_api.cpp Line: 1518
--------------------------------------------------------------------------------
Etrack Incident = ET1449955
Associated Primary Etrack = ET1412909
Titan cases:  281-397-133

Description:
   Unable to log into the NetBackup-Java Administration Console because of
   repeated status 505 errors that occurred. A fix has been made to correct
   this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1472234
Associated Primary Etrack = ET1461611
Titan cases:  220-459-421

Description:
   The nbsl was not responsive after running for a week. A change has been
   made in this Release Update to address the deadlock issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1483476

Description:
   A problem existed in the way the user interface would pass SharePoint
   restore options values causing the Share Point restore to fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1448155

Description:
   NOM was not updating the Media status as NetBackup for Full, suspended
   media. A change was made to ensure that NOM updates the status as per the
   NetBackup side.
--------------------------------------------------------------------------------
Etrack Incident = ET1483134

Description:
   A change was made in VMWare to support a "hotadd" transport type for the
   proxy inside of a VM.
--------------------------------------------------------------------------------
Etrack Incident = ET1481079

Description:
   FlashBackup would fail on multi-terabyte, UFS file systems. An attempt to
   backup a file system created with ufs -t caused the FlashBackup to fail
   because it did not recognize the number.
--------------------------------------------------------------------------------
Etrack Incident = ET1483362
Associated Primary Etrack = ET1479835
Titan cases:  320-148-372

Description:
   The app_cluster media servers could not be selected in the vault profile
   after an upgrade to NetBackup 6.5 completed.
--------------------------------------------------------------------------------
Etrack Incident = ET1465117
Associated Primary Etrack = ET1439156
Titan cases:  230-605-462

Description:
   vltadm MUI is used to configure and edit vault profiles. When attempting
   to edit and configure a source volume group, vltadm core dumped. This
   happened only when the source volume group entries at the server were
   more than 22.
--------------------------------------------------------------------------------
Etrack Incident = ET1483465
Associated Primary Etrack = ET1481521
Titan cases:  320-155-695

Description:
   The jnbSA -r x.x command would not launch the NetBackup-Java
   Administration Console, including previous releases of NetBackup. A new
   variable was created and the launch command for the NetBackup-Java
   Console includes the value of this variable to launch the console for
   back releases using the command ./jnbSA -r 5.0/5.1/6.0.
--------------------------------------------------------------------------------
Etrack Incident = ET1451817
Associated Primary Etrack = ET1406481
Titan cases:  291-060-008

Description:
   Disk staging schedules would not run automatically, and pem V3 would also
   receive an "ASSERT failed" error.
--------------------------------------------------------------------------------
Etrack Incident = ET1481404
Associated Primary Etrack = ET1481295
Titan cases:  291-090-292

Description:
   bpjobd was not able to utilize file descriptors over 1024.
--------------------------------------------------------------------------------
Etrack Incident = ET1414922 ET1437385 ET1481373
Titan cases:  320-149-798

**Description:
   Resolved a possible data loss issue where SLP marked images as lifecycle
   complete without creating copies at destinations that were configured with
   an INFINITY retention level.
--------------------------------------------------------------------------------
Etrack Incident = ET1484940
Associated Primary Etrack = ET1474473
Titan cases:  281-475-411

Description:
   migmdclean failed with ERROR: Failed to write FHDB entry to stream,
   perror 27: File too large.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1476107

Description:
   The date format was not I18N compatible in the output of bpchangeprimary.
--------------------------------------------------------------------------------
Etrack Incident = ET1374989

Description:
   A change was made to stop the NetBackup client data collection when NOM is
   not connected.
--------------------------------------------------------------------------------
Etrack Incident = ET1482914
Associated Primary Etrack = ET1450213
Titan cases:  240832622

Description:
   nbfirescan crashes when there are devices from IBM SVC mapped on the host.
--------------------------------------------------------------------------------
Etrack Incident = ET1477935 ET1486988
Associated Primary Etrack = ET1454994
Titan cases:  320-145-695

Description:
   An SAP application backup completes successfully (bpbrm, bpdm/bptm, and
   bpbkar processes exit with status 0), however, the backint process(es)
   would hang.  
--------------------------------------------------------------------------------
Etrack Incident = ET1485005

Description:
   Restarting a restore request would sometimes cause erroneous information to
   be logger for the priority.
--------------------------------------------------------------------------------
Etrack Incident = ET1485946
Associated Primary Etrack = ET1294543
Titan cases:  320-106-892 320-186-725

Description:
   Duplications would potentially fail or hang if it had previously failed.
   This would only happen with a UNIX media server, and if the source and
   destination media servers were the same.

Workaround:
   There are two potential workarounds for this issue, either one works:
   
   On the master server, create the following file:
   
     UNIX: /usr/openv/netbackup/NOSHMDUP
     Windows: VERITAS\NetBackup\NOSHMDUP
--------------------------------------------------------------------------------
Etrack Incident = ET1437453

Description:
   In very rare circumstances, a backup failure would cause bpdbm to crash
   as it is ending the backup job.
--------------------------------------------------------------------------------
Etrack Incident = ET1402322
Associated Primary Etrack = ET1366926
Titan cases:  220-353-121

Description:
   The default xinetd.conf settings on RedHat 5 limit the number of
   "per_source" connections to 10. This could cause connection problems
   to busy NetBackup hosts. For example, this could cause multi-stream
   database extension backups to fail.
   
   The fix replaces the bpcd and vnetd configuration files for xinetd with
   new copies that contain the following values:
   
     connections  = UNLIMITED
     per_source   = UNLIMITED
     cps          = 1000 1
   
   If the bpcd and vnetd configuration files are replaced, the old copies
   are saved in /etc/xinetd.d as bpcd.<timestamp> and vnetd.<timestamp>.
   
   If a "per_source" entry already exists in the bpcd and vnetd files, no
   changes are made to these files.
   
   The fix is applicable to all NetBackup-supported operating systems that
   run xinetd.
   
   For more information, please see the following Technote:
      http://seer.entsupport.symantec.com/docs/300810

Additional Notes:
   These changes are not reverted on uninstall.
--------------------------------------------------------------------------------
Etrack Incident = ET1481348

Description:
   The resource broker (RB) would sometimes crash at the time of exit because
   some data structures were not correctly locked.
--------------------------------------------------------------------------------
Etrack Incident = ET1486168
Associated Primary Etrack = ET1470662
Titan cases:  312-059-763

Description:
   bpbackup with the -w option exits at the first failure even the job
   status is waiting_for_retry.
--------------------------------------------------------------------------------
Etrack Incident = ET1484203

Description:
   Jobs were not collected in NOM if the Media used to backup a job was
   deleted.
--------------------------------------------------------------------------------
Etrack Incident = ET1485370
Titan cases:  220-407-683

Description:
   A change was made to show a warning if the wrong disk is selected as a
   system disk during mapping.
--------------------------------------------------------------------------------
Etrack Incident = ET1472633

Description:
   A calendar schedule that crossed multiple days would stop scheduling
   completely after running on the last full day when only one window was
   open for the week.
--------------------------------------------------------------------------------
Etrack Incident = ET1486660
Associated Primary Etrack = ET1449407
Titan cases:   312-037-611 281-580-389 281-606-251 312-163-155

Description:
   If a database agent (such as DB2) or a user of the XBSA SDK performed a
   query and did not specify a start time, the query would only search back
   six months in time.  If the image that was needed was older that six
   months it would not be found.
   

Workaround:
   To avoid this issue, specify a start time of the query.
--------------------------------------------------------------------------------
Etrack Incident = ET1486686
Titan cases:  311-942-240

Description:
   Client containers now include install_client and extract_java scripts.  
   This corrects a potential upgrade problem for client binaries on
   NetBackup servers.
   
   After applying a previous NetBackup 6.5.x Release Update, and running
   install_client_files from a Linux NetBackup Server to push a different
   client type (for example, Solaris), the following error occurred:
   
      Unknown hardware type: "LINUX_RH_X86"
   
   This error occurred because other client platforms were not being
   upgraded properly to NetBackup 6.5GA.
   
   Users must separately update all other client platforms at
   NetBackup 6.5GA, however there was not a warning so it could be easily
   overlooked.  This fix allows this upgrade path to succeed even if it is
   not the correct upgrade path.
--------------------------------------------------------------------------------
Etrack Incident = ET1486807

Description:
   An erroneous warning message with a missing text body would occasionally
   appear on a NetBackup restore.
--------------------------------------------------------------------------------
Etrack Incident = ET1487580

Description:
   A change was made to ensure that the correct parameter is logged in bpbrm
   to begin a secondary restore.
--------------------------------------------------------------------------------
Etrack Incident = ET1487510

Description:
   A change was made to ensure that the correct parameters are logged if
   there is a block mismatch during a synth write or if the current context
   differs from the expected context during a synth write.
--------------------------------------------------------------------------------
Etrack Incident = ET1464678
Associated Primary Etrack = ET1463198
Titan cases:  320-151-451

Description:
   The Job monitor in NOM would timeout after approximately 15 minutes while
   attempting to parse large database or errors files that werere greater
   than 1GB. In addition, it would not collect data.  
--------------------------------------------------------------------------------
Etrack Incident = ET1488267

Description:
   NOM was not showing the operating system (OS) name for a Windows 2008
   master server.
--------------------------------------------------------------------------------
Etrack Incident = ET1444236

Description:
   The nbstserv (duplication manager's) query to get the list of unfinished
   images, should NOT receive fragment records.  A change was made to
   address this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1452950

Description:
   A change has been added to address an issue where a user was unable to
   deactive a storage lifecycle policy (SLP).  
--------------------------------------------------------------------------------
Etrack Incident = ET1391155

Description:
   On the "New Destination" window, the same shortcut key was assigned for
   the "Media (O)wner" input and the "(O)K" input. A change was made to
   assign a unique shortcut key to each input.
--------------------------------------------------------------------------------
Etrack Incident = ET1481714
Associated Primary Etrack = ET1473444
Titan cases:  320-150-493

Description:
   A change was added to address an issue that would cause EMM to stop
   responding under a high load.
--------------------------------------------------------------------------------
Etrack Incident = ET1478999

Description:
   A change has been made to address an issue that caused bpcatlist to core
   dump when running the command line interface (CLI) on a Windows 2008 x64
   system.
--------------------------------------------------------------------------------
Etrack Incident = ET1470973
Associated Primary Etrack = ET1423595
Titan cases:  312-007-188

Description:
   When attempting to run NDMP backup with a large number of files and
   directories from some an NEC filter, it would fail with a status 249 error.
--------------------------------------------------------------------------------
Etrack Incident = ET1486506
Titan cases:  220-407-683

Description:
   For BMR, a fix was made to ensure that the NetBackup-Java Administration
   Console verifies the changed configuration before closing the config-
   mapping user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1478018

Description:
   A new volume pool would not appear in the Volume Pools list of the new
   "barcode rule" window, without restarting the NetBackup-Java
   Administration Console.
--------------------------------------------------------------------------------
Etrack Incident = ET1485977

Description:
   A fix was made to address an issue that would cause bpduplicate to core
   dump.
--------------------------------------------------------------------------------
Etrack Incident = ET1488734

Description:
   bpimagelist now includes functionality to report images that are in the
   progress of being backed up (ONLY_INPROGRESS) or have not yet been
   validated (NO_VALIDATION).
--------------------------------------------------------------------------------
Etrack Incident = ET1475372

Description:
   The Services tab in the Activity Monitor would not show the HP-UX IA64
   media server services but would show HP-UX media server services as
   stopped.
--------------------------------------------------------------------------------
Etrack Incident = ET1484302
Titan cases:  320-156-295

Description:
   Changes were made to correct DNS issues so that SAN Clients will register
   the FT targets that they see.  In addition, changes were added to make
   the logging more clear.
--------------------------------------------------------------------------------
Etrack Incident = ET1500190

Description:
   Changes were made to the adjust the level of information that was being
   displayed in Job details.  In some cases, the level of information was
   simply too detailed.
--------------------------------------------------------------------------------
Etrack Incident = ET1500272
Associated Primary Etrack = ET1506010

Description:
   This release Update contains added support for:
   - A new tape-library device path on HP-UX 11.31
   - TLH on Windows 2008 media servers and HP-UX IA64 media servers
   - IBM ATL version for all supported NetBackup TLH robotic platforms
   For the latest information on supported hardware for each OS, search for
   the, "Veritas NetBackup  Enterprise Server and Server 6.5 Hardware
   Compatibility List," on the Symantec Support Web site.
--------------------------------------------------------------------------------
Etrack Incident = ET1500484

Description:
   Unexpected failures that occurred during the device configuration would
   result in bad data in the EMM logs or an undefined behavior.
--------------------------------------------------------------------------------
Etrack Incident = ET1487577 ET1557578

Description:
   The NetBackup Resource Broker (nbrb) would either crash or would not
   release allocations after an upgrade if there were old allocations in RB
   database before the upgrade.
--------------------------------------------------------------------------------
Etrack Incident = ET1405038

Description:
   UNIX client bpbkar process(es) were not getting cleaned up if the media
   manager process, bptm, crashed unexpectedly.

Workaround:
   If you encounter this issue, kill the bpbkar processes manually if their
   corresponding jobs have already errored out.
--------------------------------------------------------------------------------
Etrack Incident = ET1488525

Description:
   A change has been added to ensure that nbstserv is capable of
   duplicating more than one image at a time.  
--------------------------------------------------------------------------------
Etrack Incident = ET1435092

Description:
   The Import and Restore of Exchange 2003 BE11d images, with "Mailbox
   restore" option enabled, were failing. Even though these mailbox restores
   are not supported through BETR, a change was made to ensure that at a
   minimum, regular restores are successful. This includes an image that has
   extra information to support Granular restores.
--------------------------------------------------------------------------------
Etrack Incident = ET1486202
Associated Primary Etrack = ET1086602
Titan cases:  290-819-727

Description:
   Vault does not use a customized title of consolidated report as an Email
   subject. When Vault reports are configured to use customized titles,
   Vault should use it to generate reports as report headers and email
   subject line.
   
   A fix was added to ensure that Vault makes use of a customized report
   title as an Email subject (if the report distribution was configured to
   use an email notification).
--------------------------------------------------------------------------------
Etrack Incident = ET1501040

Description:
   bpadm would sometimes core dump when exiting some platforms (such as
   Solaris 10 sparc) after adding a client to a policy's client list.

Additional Notes:
   bpadm completed its update successfully, however, it is likely that a
   core file is created.
--------------------------------------------------------------------------------
Etrack Incident = ET1501855

Description:
   A change was made to address an issue that would cause NBJM to crash
   while running an inline tape copy job if all copies were directed to a
   non-existent media pool.
--------------------------------------------------------------------------------
Etrack Incident = ET1450415
Associated Primary Etrack = ET1445633
Titan cases:  312-046-169

Description:
   A change has been added to address an issue that would allow jobs to run
   continuously while the time changed because of daylight savings time.  
--------------------------------------------------------------------------------
Etrack Incident = ET1503555

Description:
   An enhancement was added that enables Sun/STK T10000 tape drives to
   support T10 device encryption.
--------------------------------------------------------------------------------
Etrack Incident = ET1503554

Description:
   Media sharing on tl8/tlm/tlh/tsh robots would unload the media between
   usage by different servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1504217

Description:
   A change has been added to report a specific error when an attempt is
   made to import a tape that has only been bplabeled.
--------------------------------------------------------------------------------
Etrack Incident = ET1502059
Associated Primary Etrack = ET1488743
Titan cases:  312-087-281

Description:
   Bpdbm would generate malformed entries in the error database that would
   cause the bpdbm log to fill with the following message:
     "<2> get_error: malformed db entry: x = 10"

Workaround:
   If you encounter this issue, enable the GENERATE_ENGLISH_LOGS, or try to
   remove the IMAGE_INFO catalog cache files.
--------------------------------------------------------------------------------
Etrack Incident = ET1475402
Associated Primary Etrack = ET1504288
Titan cases:  220-537-204 220-543-738

Description:
   When an optimized duplication fails, it automatically resumes the
   duplication with a normal duplication. The default behavior should be that
   the duplication should fail if the optimized duplication fails.  There
   should be a configuration flag if the user wishes to continue with normal
   duplication if the optimized duplication fails.
     

Additional Notes:
   To renable 6.5.3 in the event of optimized duplication failure, set
   RESUME_ORIG_DUP_ON_OPT_DUP_FAIL = TRUE in bp.conf.
--------------------------------------------------------------------------------
Etrack Incident = ET1503097

Description:
   When jobs fail due to a drive being down or an unavailable condition, the
   failure status was not unique, it would fail with a status 800 error.
--------------------------------------------------------------------------------
Etrack Incident = ET1505138

Description:
   A change was made to address an issue that would cause NBPEM to crash on a
   shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET1504987

Description:
   This Release Updates updates the device mappings to version 1.75 which
   include new device support for the following libraries:
      STK SL3000
      Fujitsu-Siemens FibreCat TX24 S2
      Fujitsu-Siemens FibreCat TX28 S2
      IBM TS7530
      NEC LL009
   
   In addition, this release contains added support for the following tape
   drives:
      IBM TS1130 (3592E06)
      STK 9840D
   
   Finally, this release contains changes to the following library:
      STK L180 library - add mailslot delay
--------------------------------------------------------------------------------
Etrack Incident = ET1505661

Description:
   Due to changes in bpdbm the communication between a FlashBackup single
   file restore and bpdbm would cause bpdbm to hang.
--------------------------------------------------------------------------------
Etrack Incident = ET1483897

Description:
   In the Vault-Java user interface, multiple vault dialogs would not fit
   into the screen. The OK, Cancel, and Help buttons were not visible in
   the screen and also in a few dialogs, even after attempting to size the
   dialogs.  
--------------------------------------------------------------------------------
Etrack Incident = ET1429723

Description:
   A new version of the Veritas Unified Logging (VxUL) has been included with
   this Release.
--------------------------------------------------------------------------------
Etrack Incident = ET1507290

Description:
   AIX servers using the a tape driver would not read the cartridge serial
   number for devices that have them.  This prevented a comparison between
   the expected cartridge data and the actual data.  The comparison was used
   as another verification that the desired media was the loaded media.
--------------------------------------------------------------------------------
Etrack Incident = ET1505203

Description:
   The cluster offline for a NetBackup group would call NetBackup offline
   with incorrect parameters. This lead to the failure to bring NetBackup
   offline.
--------------------------------------------------------------------------------
Etrack Incident = ET1399167

Description:
   A change was added to provide the ability to logout a user if there
   are no user actions for particular time period. The change provides an
   indication to the user after a set, elapsed time is reached. A message
   box appears indicating that a timed-out value has been reached and the
   user is given the opportunity to click OK to log out.
--------------------------------------------------------------------------------
Etrack Incident = ET1505537

Description:
   The Job details in the Activity Monitor showed two fields, "Current File"
   and "Path Name" in the job overview. To be consistent with the Windows
   user interface, the "Path Name" field was removed. The "Current File" field
   remains.  This field shows the current file that is being backed up or
   restored.
--------------------------------------------------------------------------------
Etrack Incident = ET1507663

Description:
   bpclusterkill was not working when called from a cluster offline script.
--------------------------------------------------------------------------------
Etrack Incident = ET1505107

Description:
   An NDMP Restore would intermittently fail with the error, ERROR: 1 leftover
   full buffers. This error only occurred when doing an NDMP restore from a
   backup with multiple paths, and the restore includes files from more than
   one of the backup paths.
   
   Also, this error only occurred when doing an NDMP Remote restore.

Workaround:
   If you encounter this issue, restore only the files that are all from the
   same backup path. If files from more than one backup path are needed,
   restore them in separate restore jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1501647 ET1501118
Associated Primary Etrack = ET1487578
Titan cases:  240-878-756

Description:
   Resolved an issue where some of the small backup jobs are duplicated with
   SLPs immediately or after a short delay, even though the parameter
   MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB (delay for small duplications)
   was set to a value like 240 minutes in LIFECYCLE_PARAMETERS file.
--------------------------------------------------------------------------------
Etrack Incident = ET1417539
Associated Primary Etrack = ET1414528
Titan cases:  320-130-911

Description:
   A change was made to address an issue that caused the connection between
   NOM and the NetBackup master using a certain interface on NOM machine would
   fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1502104

Description:
   Scheduled jobs for a policy of type WindowsNT, with multi-streaming
   selected, and WOFB enabled for the client, were running incorrectly.
--------------------------------------------------------------------------------
Etrack Incident = ET1508567

Description:
   The catalog check for whether a duplication is in progress on Windows was
   leaving a lock on the file for the duration of the catalog operation that
   was doing the check.  This had the potential of causing other catalog
   operations that were running during that time to mistakenly conclude that
   a duplication was in progress and prevent the operation from proceeding.
   
   The duplication protocol calls for bpduplicate to lock the new copy at
   the start of the duplication and unlock the copy at the end of the
   duplication.  bpdbm implements this lock with a file lock on a file with
   the name <image>.cpy, where <image> is the name of the image header file.
   Other catalog operations check whether a duplication is in progress by
   attempting to lock the copy file - failure to obtain the lock indicates
   no duplication is in progress.
--------------------------------------------------------------------------------
Etrack Incident = ET1406063
Associated Primary Etrack = ET1395328
Titan cases:  281-402-493

Description:
   Using the bp interface on some clients (such as, HP-UX IA64 11.23 and
   11.31) would produce a DATE ERROR when changing the date, in the "Change
   Date Range..." part of the user interface.

Workaround:
   If you encounter this issue, use the user interface to do backups, instead
   of bp.
--------------------------------------------------------------------------------
Etrack Incident = ET1507033

Description:
   A change was made to properly display triple-dot (x.x.x.x) NetBackup
   versions with tpconfig -emm_dev_list.
--------------------------------------------------------------------------------
Etrack Incident = ET1487594
Associated Primary Etrack = ET1399253
Titan cases:  230-579-099

Description:
   A Lotus backup would fail on AIX with the following error:
   
      103: error occurred during initialization, check configuration file
--------------------------------------------------------------------------------
Etrack Incident = ET1500451
Associated Primary Etrack = ET1487742
Titan cases:  291-137-582 320-159-200

Description:
   The NetBackup Resource Broker (nbrb) would hang in certain situations.
--------------------------------------------------------------------------------
Etrack Incident = ET1510055
Associated Primary Etrack = ET1510051
Titan cases:  220-550-436

Description:
   migmerge fails to backup a large FHDB, instead logging perror 72,
   "value too large to be stored in datatype".
--------------------------------------------------------------------------------
Etrack Incident = ET1460712
Titan cases:  220-456-198

Description:
   A consolidated eject should not consider sids when having all media
   ejected during a previous session.
   
   A consolidated eject would attempt to eject media from sessions for
   which an eject time-stamp was not set in vlteject.mstr.
   
   For example, assume that, sid1 and sid2 gets qualified for a
   consolidated eject based on the eject time-stamp (vlteject.mstr). The
   eject process would update the eject time-stamp for sid1 and sid2 only
   if all of the media from both sids were ejected successfully. If not,
   these sids were considered again during the next consolidated eject
   session (even if media from one of sid1 and sid2 were ejected completely).
   
   The above behavior had the following impact on the Vault reports:
     - Vault reporting took a longer time due to processing media that had
       already been ejected.
     - Vault reports already-ejected media in every consolidated session
       until all of the media from all sids were ejected completely.
   
   Changes were made to ensure that a consolidated eject updates the eject
   time-stamp of the sid's for which all the media were ejected
   successfully even if the vault job ends up being partially successful.
   This ensures that already-ejected media are not re-processed and reported.

Workaround:
   If you should encounter this issue, you should manually look at the eject
   media list and update the vlteject.mstr session time stamp to indicate
   that it is done.
--------------------------------------------------------------------------------
Etrack Incident = ET1399174

Description:
   A change was made to enable a user to display custom text when attempting
   to log in. The user also has the ability to set or modify the text that is
   presented to users on the user interface login screen.
--------------------------------------------------------------------------------
Etrack Incident = ET1509112

Description:
   Resume of a suspended job would fail to backup all of the files if the
   suspend point was in the root (/) directory.  This would only happen if a
   lot of files existed in the root directory (which should be rare).
--------------------------------------------------------------------------------
Etrack Incident = ET1499426

Description:
   If NBPEM and NBJM were restarted while jobs were running, some
   parent/child check-pointed jobs would not be recovered correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET1509107
Associated Primary Etrack = ET1532095
Titan cases:  320-170-616

Description:
   A change as been made to ensure, "nbstlutil active/inactive/cancel -
   destination" does not hang nbstserv if there are lifecycle incomplete
   images.
--------------------------------------------------------------------------------
Etrack Incident = ET1508224

Description:
   The Pemtask::invokeRun call was incomplete and caused multiple parents jobs
   to hang.
--------------------------------------------------------------------------------
Etrack Incident = ET1155347
Associated Primary Etrack = ET1486637

Description:
   The vendor-unique library handling of barcodes can cause inject
   operations to fail, requiring CLI operations.
   
   LTO/SDLT media barcodes contain special characters ('L1', 'L4').  
   Some libraries report these characters as the last two characters and
   some remove them from the barcode.  If you eject a media from a library,
   and then inject it into another, where the two libraries use a different
   form of barcode, the import of the second library will fail. The reported
   failure is a duplicate media ID exists (due to the fact that the barcodes
   DO NOT MATCH).  An option has been added to the robotic inventory command
   to compare all but the last two characters of the barcode to determine a
   match. To turn this on from the command line you must specify the option,
   "-fix_barcode_suffix", for the vmupdate utility.
   
   To enable this from the user interface, you must create the file,
   "/usr/openv/volmgr/database/FIX_BARCODE_SUFFIX",
   on the machine where the user interface is run.

Workaround:
   Use vmchange to change the barcode in the volume database to match the
   form of the media's current library for each media being injected.
--------------------------------------------------------------------------------
Etrack Incident = ET1454759
Associated Primary Etrack = ET1451320
Titan cases:  291-104-380

Description:
   On a setup with a clustered Master, a user could not create a storage unit
   for an AdvancedDisk pool. The following error was observed:
      status 20 - Invalid Command  
--------------------------------------------------------------------------------
Etrack Incident = ET1462067
Associated Primary Etrack = ET1300053
Titan cases:  311-946-767

Description:
   A restore with a Flashbackup VxFS_Snapshot would fail with status 5 error
   on a Linux client.
--------------------------------------------------------------------------------
Etrack Incident = ET1483007
Associated Primary Etrack = ET1461611
Titan cases:  220-459-421

Description:
   A change was made to perform data collection on separate thread pools
   instead of using orb threads. This change provides better scalability in
   the L/F strategy.
--------------------------------------------------------------------------------
Etrack Incident = ET1475985

Description:
   After canceling an Exchange VSS alternate client backup job, the snapshots
   would remain on the alternate client, and they were not resynced with the
   original volumes.  
--------------------------------------------------------------------------------
Etrack Incident = ET1478387 ET1457797

Description:
   Performing a shallow browse of a database with no content would produce
   an exception.
--------------------------------------------------------------------------------
Etrack Incident = ET1509370

Description:
   The end of session catalog backup job for a differential incremental
   schedule would not run as expected.
--------------------------------------------------------------------------------
Etrack Incident = ET1508901
Associated Primary Etrack = ET1508875
Titan cases:  281-492-327

Description:
   A corrupted Calendar file for a policy would disable all subsequent
   policies that use calendar schedules. When NetBackup reaches the
   corrupted Calendar file, the following log message was printed at
   read_schedinfo():
   
        15:27:31.734 [11861] <2> read_schedinfo: Unspecified error(80000006)
   
   This issue not only affected the policy with a corrupted Calendar file
   but also all subsequent policies with Calendar schedules.
   
   The bppllist -allpolicies -U command is also affected by this issue.

Workaround:
   The problem goes away after deleting the schedule that has the corrupted
   Calendar file.
--------------------------------------------------------------------------------
Etrack Incident = ET1511217

Description:
   A duplication job with the "preserve multiplexing" option would not cancel
   if the source or destination media server was Windows.
--------------------------------------------------------------------------------
Etrack Incident = ET1449853

Description:
   A change was made to remove duplication from bpjava and use bplist-CLI /
   code within it (such as, bprestore).
--------------------------------------------------------------------------------
Etrack Incident = ET1481224
Associated Primary Etrack = ET1473443
Titan cases:  220-486-889

Description:
   A change was made to address an issue that would cause duplication of
   Exchange Granular Restore images to hang.
--------------------------------------------------------------------------------
Etrack Incident = ET1455436

Description:
   An enhancement has been made to make SLPs "smart enough" to not attempt
   an "Inline tape copy" when processing NDMP backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1502073
Associated Primary Etrack = ET1471439
Titan cases:  312-040-549

Description:
   The import of any NDMP images that contained no file history would appear
   to complete but were unable to be restored from. This included "set hist=n"
   and "set type=smtape" backups.

Workaround:
   To correct this issue, modify the catalog header file for the imported
   images so that "NUM_FILES" is any positive non-zero value.
--------------------------------------------------------------------------------
Etrack Incident = ET1406992
Associated Primary Etrack = ET1391258
Titan cases:  240-799-693

Description:
   The NetBackup Monitor programming running on Linux was reporting the
   following message every minute.
     tr: when not truncating set1, string2 must be non-empty
   
   This has no effect on the configuration, and the fix avoids it as it fills
   up the engine_A.log file.
--------------------------------------------------------------------------------
Etrack Incident = ET1509336

Description:
   A manual restore of MaxDB through an SAP agent (backint) with extra empty
   lines in the input file would cause the backint to crash.

Workaround:
   To resolve this issue, remove the extra empty lines from the input file
   and rerun the job.
--------------------------------------------------------------------------------
Etrack Incident = ET1514843
Associated Primary Etrack = ET1406712
Titan cases:  320-131-776

Description:
   Key words in the bppllist output have changed after upgrading to
   NetBackup 6.5 affecting the automated processing of output.
   
   There were differences in the bppllist out between NetBackup 6.5 and
   6.0/5.1/5.0/4.5/3.4.  These changes were not advertised in the release
   notes of the product and could cause automated scripts that parse their
   output to fail.  In addition, the syntax of the output was not
   consistent between LONG (-L) and USER(-U) output formats.
   
   The changes were made by ET264496 in preparation for the 6.5GA release
   and do not affect prior releases of NetBackup.  

Additional Notes:
   The scope of the changes and inconsistencies is detailed below.
   
   The hard coded strings differ from the original macros values. There are
   also differences between the LONG format and USER format within the
   NetBackup 6.5 code including one client/policy type that is not included
   in the USER format output.
   
   6.5 LONG format compared to USER format:
      - Pre-NetBackup 6.5:
        - Apollo-wbak
        - Informix-On-BAR
        - PureDisk_Export
      - In NetBackup 6.5:
        - Apollo-wbaks
        - Informix
   
   6.5 CTS_* macros compared to LONG format:
      - Pre-NetBackup 6.5:
        - CMS-Database
        - NetWare
        - OS/2
        - Oracle-Obackup
        - PureDisk-Export
      - In NetBackup 6.5:
        - CMS Database
        - Netware
        - OS2
        - PureDisk_Export
   
   6.5 CTS_* macros compared to USER format:
      - Pre-NetBackup 6.5:
        - Apollo-wbak
        - CMS-Database
        - Informix-On-BAR
        - NetWare
        - OS/2
      - In NetBackup 6.5:
        - Apollo-wbaks
        - CMS Database
        - Informix
        - Netware
        - OS2
   
   These type of inconsistencies do not affect the schedule types only the
   policy/client types.
--------------------------------------------------------------------------------
Etrack Incident = ET1502251
Associated Primary Etrack = ET1502202
Titan cases:  230-618-917 281-591-557

Description:
   Nbemm would crash while running vmdareq -a if there was insufficient stack
   space.
--------------------------------------------------------------------------------
Etrack Incident = ET1503674

Description:
   A change was made that enables BPJAVA to provide a new protocol to write a
   file in binary format.
--------------------------------------------------------------------------------
Etrack Incident = ET1517224
Titan cases:  281-552-650

Description:
   A change was made that prevents a "permanent data loss" condition from
   happening when performing an upgrade then a downgrade and than an upgrade
   again when using the Bare Metal Restore Java user interface.  
--------------------------------------------------------------------------------
Etrack Incident = ET1502472

Description:
   An Exchange Instant Recovery image that contains multiple snapshot volumes,
   with one of the volumes being mount on a mount point, and the other volume
   being the mount base drive. When expiring the image, the mount point
   snapshot was deleted, but the base drive snapshot was not.  
--------------------------------------------------------------------------------
Etrack Incident = ET1508943

Description:
   A change was made to move the versioninfo command to be a client command
   and part of the default UNIX installation package and Release Updates.
--------------------------------------------------------------------------------
Etrack Incident = ET1476060
Associated Primary Etrack = ET1469659
Titan cases:  220-497-871

Description:
   Tar was truncating LOTUS_NOTES_LOGCACHESIZE to a single byte when reading
   the bp.conf file.

Workaround:
   If you encounter an issue like this, do one of the following:
     - Disable prefetch and cache.
   OR
     - Set LOTUS_NOTES_LOGCACHESIZE to a smaller value.
--------------------------------------------------------------------------------
Etrack Incident = ET1515064

Description:
   The "Restore everything to original location" option, would restore data
   to an alternate location instead of the original location on the
   Windows-Java user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1501622
Associated Primary Etrack = ET1475195
Titan cases:  240-853-280

Description:
   An alternate restore of an online backup would fail when it was run
   using the brrestore command.
--------------------------------------------------------------------------------
Etrack Incident = ET1518716
Associated Primary Etrack = ET1516745
Titan cases:  291-157-845

Description:
   A change was made to fix a core dump issue with nbstserv that would
   occur on the get_any_available_stu_hosts return and subsequent
   ReplicationSession::setDupItemAttributes step.
--------------------------------------------------------------------------------
Etrack Incident = ET1517830 ET1516611 ET1516658 ET1511966 ET1515378 ET1512269

Description:
   Some schedules would run incorrectly when the daylight savings time
   change took affect.
--------------------------------------------------------------------------------
Etrack Incident = ET1515674
Associated Primary Etrack = ET1513217
Titan cases:  312-085-817

Description:
   The bp.kill_all script would hang on an AIX server because the
   nbproxyreq -all command does not return in the bp.kill_all.
   

Workaround:
   To resolve this issue, manually kill the nbproxyreq process.
--------------------------------------------------------------------------------
Etrack Incident = ET1475595

Description:
   A SimpleDisk plugin was enhanced to support a v10 event interface and
   implement a pull event model. When it was configured with nbrmms and a
   storage server was created, nbrmms could not setup correctly as an event
   listener for the pull event model.
   
   A fix was made to enable the STSEventService to send out events by pull
   event channel.  
--------------------------------------------------------------------------------
Etrack Incident = ET1517091

Description:
   While attempting a restore following "bpbrm warning" message would be sent
   to the Job Details dialog:
   
      Warning bpbrm(pid=3200) expected start message from
      oigqevm09.lqdomain.vxindia.veritas.com; read:
--------------------------------------------------------------------------------
Etrack Incident = ET1519186
Associated Primary Etrack = ET1510623
Titan cases:  281-497-698

Description:
   When adding a Storage Unit Group to the Multiple Copies dialog within the
   schedule configuration window, the Volume Pool and Media Owner drop-down
   menus were grayed out. (The same dialog can be seen while creating a
   duplicate image from the Catalog user interface or from the Vault session
   window).
--------------------------------------------------------------------------------
Etrack Incident = ET1519805
Associated Primary Etrack = ET1518632
Titan cases:  230-627-069

Description:
   Bmrsavecfg would fail to store the client configuration for Linux clients
   that utilized the VPATH DMP software.

Additional Notes:
   This fix eliminates the /dev/vpath# disks from the stored configuration.
   If a machine restoration is desired you must either:
   1) Restore to system-only disks, or
   2) Edit the configuration and restrict any underlying DMP attached disks
--------------------------------------------------------------------------------
Etrack Incident = ET1468310
Associated Primary Etrack = ET1437411
Titan cases:  240-803-616

Description:
   When LiveUpdate is run, nbmtrans ignores the "BPCD connect-back using
   VNETD" option and asks BPCD on the client to connect back to it on other
   (non-VNETD) ports.  The update was failing with a Cannot Connect to socket
   error and LiveUpdate would fail with a status code 77.
--------------------------------------------------------------------------------
Etrack Incident = ET1501973
Associated Primary Etrack = ET1477853
Titan cases:  240-862-823

Description:
   User backups at NetBackup 6.5.2 were collecting bmrsavecfg information,
   when user backups at NetBackup 6.0MP6 did not. A change has been made
   to return the functionality as it was in NetBackup 6.0 MP6 because
   there was determined that there was no need to collect the bmrsavecfg
   information for a user backup of a small subset of data.
--------------------------------------------------------------------------------
Etrack Incident = ET1516293

Description:
   Problems would occur if packages with an empty "Architecture" field were
   not listed in the driver mapping user interface, under "Available driver
   packages". This would happened if the packages were created using
   NetBackup versions that were earlier than 6.5.4. The following list
   provides examples of what kind of environment would cause this issue
   would occur.
   
   1. If a user setup contained windows clients and then they upgraded to
      NetBackup 6.5.4. The Architecture field, with NULL value, was updated
      to x86.
   2. On a  NetBackup 6.5.4 master, if a user attempted to import a
      pre-6.5.4 config, the Architecture field was set to x86.
   3. While doing a PTR with a NetBackup 6.5.4 master and pre-6.5.4 boot
      server, the user was asked to upgrade the boot server to at least
      NetBackup 6.5.4.
--------------------------------------------------------------------------------
Etrack Incident = ET1518747

Description:
   A change was made in the NetBackup-Java Administration Console to fix an
   issue that caused a banner to be unreadable in PCK.
--------------------------------------------------------------------------------
Etrack Incident = ET1520790

Description:
   On the NetBackup-Java Administration Console, the "disable VM quiesce"
   option for VMWare FIM needs to list all of the allowed options.
--------------------------------------------------------------------------------
Etrack Incident = ET1517775
Associated Primary Etrack = ET1444339
Titan cases:  240-931-559 281-449-753

Description:
   Error databases that were larger than 2 GB could not be read on some
   platforms, (particularly HP-UX).
--------------------------------------------------------------------------------
Etrack Incident = ET1518415

Description:
   Logging into the NetBackup-Java Administration Console would fail for
   a non-root user, and cause bpjava-susvc to core dump.
   
   After enabling NBAC on RHEL 4 Master server (20090204), if a user other
   than root tried to log in, an error message (139) would appear. A change
   was made to correct the log in and eliminate this error.
--------------------------------------------------------------------------------
Etrack Incident = ET1521169

Description:
   A change was made to address an issue that caused bpdbm to core dump when
   performing a catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1521609

Description:
   For Enterprise Vault jobs, unquiesce of the EV application must be done
   only if the quiesce had been successful.
--------------------------------------------------------------------------------
Etrack Incident = ET1520660

Description:
   NBJM would crash if the AT client was not installed correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET1521319
Associated Primary Etrack = ET1519634
Titan cases:  240-902-898

Description:
   A machine update was not checking for aliases in the database before
   doing a DNS compare.
--------------------------------------------------------------------------------
Etrack Incident = ET1514161

Description:
   A problem existed where you would not be able to deactivate the SLP.
   This issue produced the following error message.
   
     Lifecycle manager operation help: Unable to process. Duplication
     session in progress. return value = [134]
--------------------------------------------------------------------------------
Etrack Incident = ET1519049
Associated Primary Etrack = ET1451722
Titan cases:   291-104-322

Description:
   A fix was made to resolve a bpdbm core dump issue involving two processes,
   hosts_equal verify_string, each from the same request few seconds apart.
--------------------------------------------------------------------------------
Etrack Incident = ET1523991
Associated Primary Etrack = ET1518489
Titan cases:  240-904-424

Description:
   The bpimagelist -l command would show the creator as "NetBackup" rather
   than "root". This would cause issues if the file was used for reporting.
--------------------------------------------------------------------------------
Etrack Incident = ET1521072

Description:
   A change was made to address an issue that caused NBSL to hang or
   deadlock on multiple servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1513309
Associated Primary Etrack = ET1509081
Titan cases:  320-161-715

Description:
   LiveUpdate policies that contained NetBackup clients that were not
   configured with LiveUpdate for NetBackup correctly would complete with a
   status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET1458798
Associated Primary Etrack = ET1454565
Titan cases:  312-045-007

Description:
   Misleading tir_info errors were reported in the user interface for
   excluded files and directories. The reported errors erroneously indicated
   the directory would be backed up.
--------------------------------------------------------------------------------
Etrack Incident = ET1515697
Associated Primary Etrack = ET1441624
Titan cases:  240-845-729 291-133-871

Description:
   Incremental hot catalog backup would take as long as a full backup and
   would sometimes time out.
--------------------------------------------------------------------------------
Etrack Incident = ET1428897
Associated Primary Etrack = ET1428883
Titan cases:  230-597-821

Description:
   In certain locales, the UNIX pack install script would fail on the
   tr command when converting strings from lowercase to uppercase. Depending
   on which tr command failed, the installer failed with various error
   messages about not being able to locate certain files. The tr commands are
   now invoked in the C locale so that the translated commands work as
   expected.
--------------------------------------------------------------------------------
Etrack Incident = ET1158858

Description:
   LiveUpdate jobs fail with status 77, however, within the nbliveup log a
   status 118 was reported. The issue was that the maximum downloadCacheSize
   for JavaLiveUpdate was exceeded. This prevents the failure by increasing
   the maximum cache size from its default of 1GB to 8GB. This issue affects
   UNIX only.

Workaround:
   This issue can still cause failures during the update that applies this
   fix. Symantec recommends that you add the following line to
   /usr/openv/netbackup/nblu.conf on any servers that you plan to update
   using NetBackup LiveUpdate:
   
   downloadCacheSize=8192

Additional Notes:
   NetBackup 6.5GA ships with version 3.5.32 of the JavaLiveUpdate(JLU)
   agent. This Release Update upgrades the JLU agent to version 3.6.20. To
   manually rollback to a previous version of JLU. You would, cd as root to
   /opt/Symantec/LiveUpdate/, and then run the ./uninstall.sh command.
--------------------------------------------------------------------------------
Etrack Incident = ET1523771
Associated Primary Etrack = ET1519906
Titan cases:  320-154-926

Description:
   In NetBackup environments that span multiple sites or have Media servers
   separated by a firewall, resource allocation could choose a remote or a
   Media server that is not accessible for restore that can cause an image
   to be dragged across the WAN or fail.
   
   The following two options provide configurable workarounds:
   1. FORCE_RESTORE_MEDIA_SERVER
      Using the user interface, an administrator can create multiple
      entries to force the usage of a Media server to perform the restore
      operation. The entries can be made in Host Properties > Master
      Server > Master Server Properties > General Server > Media Host
      Override.
   
   2. Use the same Media server that was used to perform the backup. If a
      touch file USE_BACKUP_MEDIA_SERVER_FOR_RESTORE is created in
      db/config, same Media server is used.
--------------------------------------------------------------------------------
Etrack Incident = ET1524262

Description:
   This Release Update contains an enhancement to provide information about
   virtual machines in a new virtual machines report for NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET1525087
Associated Primary Etrack = ET1513456
Titan cases:  320-163-960 312-095-879

Description:
   If you use vault to do a catalog backup and you elect to suspend media
   immediately at the profile eject step,vault would fail to suspend the
   catalog media and produce a status NB_EC=97 error code.
--------------------------------------------------------------------------------
Etrack Incident = ET1524495

Description:
   A change was made to address an issue that caused NBSL to core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET1512307

Description:
   Socket errors would occur during Storage Lifecylce Policy duplications to
   an OpenStorage disk type.
--------------------------------------------------------------------------------
Etrack Incident = ET1514813

Description:
   An OST plug-in log was missing in RMMS->mgmtsvc because of a improper
   log-level setting. A change was made to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1505895

Description:
   Changes were added to improve the NBSL supportability.
--------------------------------------------------------------------------------
Etrack Incident = ET1524277
Titan cases:  320-145-696

Description:
   A change was made to client configuration on the BMR-Java user interface
   to ensure that the device and driver package attributes, "skiptextmode"
   and "usebmrdiscovered" are being updated properly.
--------------------------------------------------------------------------------
Etrack Incident = ET1525307

Description:
   Certain media operations would attempt to use freed memory in the retry logic.
--------------------------------------------------------------------------------
Etrack Incident = ET1518751
Associated Primary Etrack = ET1510197
Titan cases:  281-490-876

Description:
   A hot catalog backup would intermittently fail with a status code 2 with
   an error that validates the NBDB backup in the staging directory. The
   validation error was reported even though the database was in a valid
   state. This has been fixed.
--------------------------------------------------------------------------------
Etrack Incident = ET1524391

Description:
   The address position in the compression frame was not being calculated
   correctly because the cluster size was not the smallest allocation size
   in dealing with a virtual machine.
--------------------------------------------------------------------------------
Etrack Incident = ET1506156
Associated Primary Etrack = ET1504333
Titan cases:  240-889-395 240-910-255

Description:
   A problem existed with bp.start_all while bringing NetBackup online
   during an AIX setup. A change was made to ensure that bp.start_all calls
   mkdev_ovpass on AIX environments.
--------------------------------------------------------------------------------
Etrack Incident = ET1513666

Description:
   Software VSS validation would failed with an MSCS client name on
   Windows 2008 x64.
--------------------------------------------------------------------------------
Etrack Incident = ET1526402

Description:
   Multiple duplication jobs duplicating shared disk images would sometimes
   deadlock against each other in certain situations.

Workaround:
   If you encounter this type of issue, cancel one or more of the deadlocked
   duplication jobs.  The other jobs will then proceed.
--------------------------------------------------------------------------------
Etrack Incident = ET1526648
Associated Primary Etrack = ET1486820
Titan cases:  281-464-996

Description:
   The C:\TEMP directory on the source client would fill with BPFIS-*txt and
   VfMS* files after repeated alternate client backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1527601

Description:
   FAT32 files were not restoring due because of an ordering method being
   used.

Workaround:
   To resolve this issue, you can restore the files singularly.
--------------------------------------------------------------------------------
Etrack Incident = ET1525928

Description:
   1. During a point-in-time recovery (PTR), if the configuration version was
      higher than the NetBackup client version in the SRT, the job would
      return a failure and ask the user to update the SRT to at least level
      of the configuration version.
   2. On the Windows bmrsrtadm wizard, the string, "add NetBackup
      maintenance pack to Shared Resource Tree" was changed to "add Release
      Update or Maintenance pack to Shared Resource Tree"
--------------------------------------------------------------------------------
Etrack Incident = ET1501039
Associated Primary Etrack = ET1474908
Titan cases:  312-030-97 312-030-971

Description:
   Tar would report invalid free space while prefetching TXNs.

Workaround:
   To resolve this issue, disable the prefetch.
--------------------------------------------------------------------------------
Etrack Incident = ET1467372 ET1593966

Description:
   bplabel would report a false-positive if an I/O error occurred while
   writing the label on a tape.
--------------------------------------------------------------------------------
Etrack Incident = ET1529844

Description:
   Partially connected master server should show error messages for monitors
   that are down.
--------------------------------------------------------------------------------
Etrack Incident = ET1529861

Description:
   The nbdb_backup command would not print the correct error string in
   unicode environments.
--------------------------------------------------------------------------------
Etrack Incident = ET1529942

Description:
   A change was made to provide a new EMC TimeFinder vendor key.
--------------------------------------------------------------------------------
Etrack Incident = ET1527862
Associated Primary Etrack = ET1206358
Titan cases:  281-179-782

Description:
   NetBackup performance, both its daemons or services and in the user
   interface, would be negatively impacted if DNS services were slow to
   return a hostname or perform reverse-IP lookups. Because all hostnames
   and aliases on a master or media server may be examined while accepting
   or creating a connection, if some of these names are not in the DNS,
   and the DNS environment is slow to respond, this would delay NetBackup,
   and cause the user interface to be non-responsive.
   
   This change logs the offending hostname whenever such a look-up takes
   longer than five seconds, making it easier to know what to clean out of
   a configuration. The new log messages look like the following:
   
   10:10:23.918 [25766] < 2> vnet_cached_gethostbyname: vnet_hosts.c.377:
   DNS lookup slow for host: : kermit.frog.com
   10:10:24.395 [25766] < 2> vnet_cached_gethostbyname: vnet_hosts.c.378:
   DNS lookup elapsed time: : 30 0x0000001e
   
   The elapsed time is in seconds.
--------------------------------------------------------------------------------
Etrack Incident = ET1461913

Description:
   A change has been made to address an issue that caused SLP's to not
   duplicated in a long time.
--------------------------------------------------------------------------------
Etrack Incident = ET1522273
Associated Primary Etrack = ET1516404
Titan cases:  291-157-838

Description:
   A UNIX multiplexed backup or duplication job would hang indefinitely when
   the number of MPX readers was equal to MAX_MPX.
--------------------------------------------------------------------------------
Etrack Incident = ET1510981
Associated Primary Etrack = ET1452050
Titan cases:  240-883-243 312-050-071

Description:
   Files backed up and restored from VxFS 5.0 or later filesystems with
   layout version 7 that have reservations specified and the growfile
   allocation flag set were not correctly restored.

Additional Notes:
   When a restored file's metadata contains the growfile allocation flag a
   log message is printed that indicates the growfile flag has not been
   restored. File space reservations and other allocation flags are restored
   as appropriate.  
--------------------------------------------------------------------------------
Etrack Incident = ET1474498
Associated Primary Etrack = ET1465759
Titan cases:  291120149

Description:
   If the "keep snapshot after backups" option in alternate client backups
   was used, the subsequent backup would fail to create snapshot. Changes
   were made in bpbrm to initiate a snapshot query on client and delete any
   such old snapshot before creating new snapshot.
--------------------------------------------------------------------------------
Etrack Incident = ET1514334
Associated Primary Etrack = ET1473722
Titan cases:  220-496-236

**Description:
   Windows weekly cumulative backups would not run after applying nbpem v6.
   
   If a policy had multiple schedules and the frequency value was larger for
   the differential than for the cumulative, the incorrect last backup data
   was used to determine the due time.
--------------------------------------------------------------------------------
Etrack Incident = ET1527768

Description:
   Database Manager (bpdbm) would core dump after a cluster failover when
   trying to send a job status to Job Manager (nbjm is down) for a hot
   catalog backup job.
   
   
--------------------------------------------------------------------------------
Etrack Incident = ET1531521
Associated Primary Etrack = ET1523289
Titan cases:  281-533-333 320-162-702

Description:
   The NetBackup-Java Administration Console would hang when displaying the
   Device Monitor at 6.5.3.
--------------------------------------------------------------------------------
Etrack Incident = ET1531249
Associated Primary Etrack = ET1418456
Titan cases:  291-065-387 220-576-353

Description:
   A user would likely encounter incorrect values while using the
   nbpremreq -legacy -predict and -due commands.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1528847

Description:
   NOM was not updating the Media Status as per NetBackup when using a
   MUX policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1523443 ET1587409
Associated Primary Etrack = ET1515253
Titan cases:  312-073-356 312-086-851 312-101-660

Description:
   Canceling a job that was in the process of mounting a tape could lead to
   status code 40 errors from LTID.  Another problem could cause the message
   queue to fill.
--------------------------------------------------------------------------------
Etrack Incident = ET1530121

Description:
   NBJM would crash on a shutdown if an internal job was running to delete
   a snapshot for an expired Windows Open File Backup parent job.
--------------------------------------------------------------------------------
Etrack Incident = ET1525375

Description:
   nbpem.exe would produce a core dump while expiring an NDMP backup image.
--------------------------------------------------------------------------------
Etrack Incident = ET1512052
Associated Primary Etrack = ET1512044

Description:
   The Job Finalized setting could not select multiple policies that span
   a page.
--------------------------------------------------------------------------------
Etrack Incident = ET1531929

Description:
   The last backup time returned by the get_last_backup function for a synth
   backup was incorrect.
--------------------------------------------------------------------------------
Etrack Incident = ET1529030

Description:
   A bpduplicate job had failures however, the job status was shown as
   successful.
--------------------------------------------------------------------------------
Etrack Incident = ET1532955

Description:
   The data in a restored compressed file differed from the original data.
--------------------------------------------------------------------------------
Etrack Incident = ET1529158 ET1537663
Titan cases:  281-508-495

Description:
   The information logged was not clear as to why the SAN Client was failing
   to run (for example, there was no CLIENT_NAME in bp.conf).  
--------------------------------------------------------------------------------
Etrack Incident = ET1531907

Description:
   A differential incremental backup following a synthetic full backup would
   use a delta time based on the run time of the synthetic full backup
   instead of the birth time of the incremental prior to the synthetic full.
--------------------------------------------------------------------------------
Etrack Incident = ET1533986

Description:
   The nbpemreq output that is sent to the monitor (screen) was incorrect
   when run on an AMD64 platform.
       nbpemreq -subsystems screen all
--------------------------------------------------------------------------------
Etrack Incident = ET1516985
Associated Primary Etrack = ET1515630
Titan cases:  230632445 240-926-761

Description:
   A UBAK backup would take too long to go active after upgrading to
   NetBackup 6.5.3. The immediate and manuals were the same.
--------------------------------------------------------------------------------
Etrack Incident = ET1533817

Description:
   A change was added to prevent the loss of any resources when updating
   the mappings file.  
--------------------------------------------------------------------------------
Etrack Incident = ET1534963

Description:
   A new version of the Veritas Unified Logging (VxUL) has been included with
   this Release.
--------------------------------------------------------------------------------
Etrack Incident = ET1535794

Description:
   Added NetBackup Support for Sun Cluster 3.2 on Solaris 10 on x64 platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET1535780
Associated Primary Etrack = ET1532133
Titan cases:  320-170-677

Description:
   The nbproxy would core dump whenever an SLP was modified.
--------------------------------------------------------------------------------
Etrack Incident = ET1536441

Description:
   The parent JobId on Job monitoring page in the NOM user interface was not
   correct.
--------------------------------------------------------------------------------
Etrack Incident = ET1529377

Description:
   A change was made to address an issue that would cause nbstserv to core
   dump on a Solaris Master server.
--------------------------------------------------------------------------------
Etrack Incident = ET1533275

Description:
   A RAW tablespace Offhost HP_EVA_VSNAP restore would fail with the
   following error:
      "backup file not found in the NetBackup catalog"
--------------------------------------------------------------------------------
Etrack Incident = ET1535663

Description:
   The image for a suspended job would expire after the incomplete job
   completion interval. A change has been added to ensure that the suspended
   image is retained until the retention period expires.
--------------------------------------------------------------------------------
Etrack Incident = ET1539736

Description:
   A failed bpdbm query to start an online catalog backup would fail with a
   status 233, rather than a status that indicated the cause of the failure.
--------------------------------------------------------------------------------
Etrack Incident = ET1536918

Description:
   If an NBJM request to initiate the parent job for hot catalog backup
   policy fails, the job would remain ACTIVE and no child jobs would be
   initiated.
--------------------------------------------------------------------------------
Etrack Incident = ET1537820

Description:
   Resources would not get released if a write request with pending
   allocations (in case the media is write-protected) was canceled.
--------------------------------------------------------------------------------
Etrack Incident = ET1520098
Titan cases:  312-097-753

Description:
   During an Exchange VSS backup with an Exchange environment that contained
   a large number of log files, the backup job would end with a status 13,
   and brm would fail because the client read timeout was exceeded.  

Workaround:
   Increased the client read timeout for the Exchange server.  

Additional Notes:
   This fix addresses a number of secondary issues which enhance the
   scalability of Exchange snapshot backups:
   
     1) Make Exchange VSS backup error processing more robust by attempting
        a backup when the Exchange writer status is retryable.
     2) Decrease the number of VSSINFO objects in the bpfis state table to
        speed up the rebuild FIM processing.
     3) Correct some known memory leak issues.
     4) Issue a bpfis delete if brm times out while waiting for a bpfis
        create process to complete.
--------------------------------------------------------------------------------
Etrack Incident = ET1535789
Associated Primary Etrack = ET1586899
Titan cases:  281-575-400

Description:
   A problem existed that allowed users to configure FlashBackup policies
   on a Solaris_x86 master but they could not configure restores.
--------------------------------------------------------------------------------
Etrack Incident = ET1541722
Associated Primary Etrack = ET1527957
Titan cases:  281-516-050

Description:
   The NBSharedDisk List command would fail with NetBackup 6.5.3 if an
   EVA array name contained a space.
--------------------------------------------------------------------------------
Etrack Incident = ET1534880

Description:
   The proxy plug-in (the old proxy plug-in) and the proxy server were
   built at STS_VERSION 9.  When the proxy server attempted to start on a
   NetBackup 6.5.4 server (6.5.4 is installed with a V10 STS core library),
   the proxy server would fail because its call to sts_init fails. A change
   was made to build a proxy server in v10 and leave proxy plug-in in v9.
   This in essence, fools the proxy plug-in by hard coding the proxy server
   version as 9. This means the proxy server will handle the different
   version of interfaces, and translate v10's structure into v9, and pass
   to the plug-in.
--------------------------------------------------------------------------------
Etrack Incident = ET1541682
Associated Primary Etrack = ET1507105
Titan cases:  240-890-742

Description:
   Browsing certain sub-directories with NetBackup 6.5.3 or 6.5.2 would
   produce STATUS 220 or STATUS 227 errors.
--------------------------------------------------------------------------------
Etrack Incident = ET1521076
Associated Primary Etrack = ET1538083
Titan cases:  291-171-869

Description:
   If the hot catalog backup parent job was canceled after the second child
   job starts the jobs would terminate. In addition, a resource was leaked
   that prevented the next hot catalog backup job from going active.
--------------------------------------------------------------------------------
Etrack Incident = ET1541521

Description:
   When performing granular-enabled SharePoint backups and the cataloging of
   the granular items is not done at backup time, there is a possibly that
   the 'live browse' of SharePoint will not work.  This would happen when the
   site name contained square brackets '[]' or curly braces '{}' anywhere in
   the name.
--------------------------------------------------------------------------------
Etrack Incident = ET1542470

Description:
   A VxVM PIT rollback failed beginning with a bppfi failure to unmount the
   snapshot verification directory, /tmp/pfi_nnnnnn_N.
--------------------------------------------------------------------------------
Etrack Incident = ET1542981

Description:
   A change has been made to address a problem that caused a PEM ASSERT
   failure to occur when performing a user backup (database backup) with
   BLI enabled, the jobid defined, and a keyword specified to nbpem on a
   RH4 server.
--------------------------------------------------------------------------------
Etrack Incident = ET1544995

Description:
   On the NetBackup-Java Administration Console, the text, "Enable document
   restore" has been changed to read, "Enable granular recovery" on the
   Policy Attribute Dialog.
--------------------------------------------------------------------------------
Etrack Incident = ET1536999

Description:
   The nbemmcmd command would fail to display localized characters with
   Windows 2008 on the AMD64 architecture.
--------------------------------------------------------------------------------
Etrack Incident = ET1544193
Associated Primary Etrack = ET1539913
Titan cases:  320-175-570

Description:
   When an Optimized Duplication (Opt-Dup) is processing during a
   system/server shutdown NetBackup may remove the original copy.  
--------------------------------------------------------------------------------
Etrack Incident = ET1539274

Description:
   Duplication of hot catalog backups would fail with a premature EOF and
   also cause bpdbm to core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET1545900

Description:
   A change was made to address an issue that would cause nbemm to randomly
   crash.
--------------------------------------------------------------------------------
Etrack Incident = ET1550511
Associated Primary Etrack = ET1555697
Titan cases:  281-528-823

Description:
   Policies that had a window crossing midnight (Saturday PM to Sunday AM)
   were submitted again and run at midnight for that day's backup, even
   though the window actually opened later in the day (Sunday PM).
--------------------------------------------------------------------------------
Etrack Incident = ET1542746
Associated Primary Etrack = ET1541969
Titan cases:  240-920-732

Description:
   A change was made to ensure the AT root password is masked with asterisk
   characters (*****) in the NOM server logs, if the debugging level is set
   to 5 or 6.  In addition, a fix was made to mask the password that a user
   enters when prompted to change a password in the console.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1557316 ET1557318

Description:
   A change was made to include the nbsu version 1.2.7 with the
   NetBackup 6.5.4 release.
--------------------------------------------------------------------------------
Etrack Incident = ET1544010

Description:
   Calendar-based schedule retries were occurring the next day even though
   the "retries allowed after runday" was disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET1545883

Description:
   Jobs were not being scheduled for a policy with a calendar schedule defined
   and if there was no last backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1557845

Description:
   A problem existed that prohibited a user from browsing directories that
   contained special characters in the names when using the NetBackup-Java
   BAR user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1558318

Description:
   A bpbrm core file would occur when restoring via a SAN Client Fibre
   Transport. This issue first appeared on a Solaris 10 SPARC system.
   A fix has been added to correct this issue.  
--------------------------------------------------------------------------------
Etrack Incident = ET1542974
Associated Primary Etrack = ET1504035
Titan cases:  240-878-326

Description:
   The bpexpdate -d 0 command would not delete images properly when media
   sharing was enabled. After running bpexpdate -d on a tape with media
   sharing enabled, all images were expired in EMM ("Valid Images" set to 0
   in nbemmcmd output). However, some images remained on the disk, leading
   to the inconsistency.
--------------------------------------------------------------------------------
Etrack Incident = ET1586474

Description:
   The bpduplicate command, if canceled, would not release resources in some
   scenarios.
--------------------------------------------------------------------------------
Etrack Incident = ET1557304

Description:
   Duplication to a PureDisk storage unit would sometimes fail and core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET1587307

Description:
   A change was added that fixes a problem that caused nbstserv to stop
   and stop logging.
--------------------------------------------------------------------------------
Etrack Incident = ET1558193

Description:
   A change was made to address a performance issue that would cause
   Differential Catalog backups to be very slow if images were being cleaned
   up during the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1590423

Description:
   The following error would occur if an attempt was made to change a DB2
   policy.
   
      /usr/openv/netbackup/bin/admincmd/bpplinf o: munmpa_chunk{}: invalid
      pointer while changing DB2 policy
--------------------------------------------------------------------------------
Etrack Incident = ET1595019

Description:
   Invalid inode entries for Flashbackup and NDMP validation failures were
   not reported correctly with the "cat_convert -check" option.

Additional Notes:
   With this change, the format of the reports that were produced changed
   slightly:
   
   The new format for the Invalid Inode Report is:
   
   Invalid Inode Report
   
   Type Problem Additional Information
   Dir  No Data Path element name: SUNWmlib
   Dir  No Name Filenum: 7
   File No Data Path element name: vmd.uds
   File No Data Path element name: bpcompatd.uds
   File No Name Filenum: 8356
   Dir  No Name Filenum: 8374
   
   NOTE: The "Inode" column has been dropped, the contents of the "Problem"
         column changed slightly (adding "NO" prior to "Name" or "Data")
         and the "Name" column has been relabeled "Additional Information".  
         The "Additional Information" column will list either the path
         element name associated with the inode, the filenum field that the
         catalog received for the inode, or a message that indicates a
         problem in retrieving this data.
   
   The new format for the Invalid Directory report is:
   
   Invalid Directory Report
   
           Inode   1st     1st   Last    Next    Next
   Index   Index   Child   Dir   Child   Index   Dir Name
     9       3       2F    11     11D     -1F    -1 SUNWmlib
   
   The "Inode" column was relabeled "Inode Index" since is not the inode
   number, but rather an index into a temporary file in which inode
   information is stored while the backup is in process.
   
   The new format for the Invalid File report is:
   
   Invalid File Report
   
   Index    Inode Index    Next Index    Name
   2364     12180          2368F         Report.doc
   
   The changes noted above for the Invalid Directory report apply to the
   Invalid File report.
--------------------------------------------------------------------------------
Etrack Incident = ET1413512

Description:
   A change was made to upgrade to a newer HP compiler to resolve memory
   leaks. A few files were adjusted to the new compiler to address this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1598449

Description:
   A null check was added for a security ID to address an issue that would
   occur on an AMD64 system, while exiting NetBackup-Java user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1594679

Description:
   Host Properties were not accessible to all non-admin NBAC users on hosts
   where Shared Disk was configured in an NBAC environment. The permissions
   for a Disk Service Manager API were not set correctly for non-admin NBAC
   users to access the Host Properties of a master server. This fix addresses
   the permission issue.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1545939
Associated Primary Etrack = ET1544289
Titan cases:  281-490-183

Description:
   A change has been made to address a segfault issue that would cause a
   core dump to occur after modifying various policy attributes.
--------------------------------------------------------------------------------
Etrack Incident = ET1599601
Associated Primary Etrack = ET1556412
Titan cases:  281-537-046

Description:
   An enhancement was made that improves how VM's are selected during the
   backup process. This change checks for a registry entry and use the
   Display Names if it is found.  
--------------------------------------------------------------------------------



Release Update History
----------------------

This section contains an accumulative list of all Release Update information
contained in previous releases.

===============
NBLU 6.5.3.UNIX
===============
Etrack Incident = ET1275559

Description:
   A bpdbm core dump would occur because of a badly formatted ovgetmsg routine.
   A change was made to address this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1289330

Description:
   Changes have been added to ensure that the BMR database levels match those
   of the NetBackup server.
--------------------------------------------------------------------------------
Etrack Incident = ET1302929

Description:
   A change was added to fix memory leaks discovered in the bpplsched command
   line and nbproxy which use common free routines.  The cause of the problem
   was that the command line would mix results from different queries.  The
   c_receive_flag determines if the contents of a structure are freed and if
   queries are mixed like this, the value may not be the same.
--------------------------------------------------------------------------------
Etrack Incident = ET1302749
Associated Primary Etrack = ET1300264
Titan cases:  220-369-133 311-946-518 320-117-267 320-122-713

Description:
   User backups with windows configured to be 24x7, would fail at midnight
   with a status code 196.
--------------------------------------------------------------------------------
Etrack Incident = ET1317013
Associated Primary Etrack = ET1292141
Titan cases:  220-319-568 240-781-624 311-955-023

Description:
   Backups would fail with a status code 230 when using the en_GB.ISO8859
   locale.
--------------------------------------------------------------------------------
Etrack Incident = ET1317008
Associated Primary Etrack = ET1295547
Titan cases:  230-554-457

Description:
   The policy execution manager (nbpem) would core dump after restarting a
   job that had been running before the upgrade to NetBackup 6.5.2.
--------------------------------------------------------------------------------
Etrack Incident = ET1317006
Associated Primary Etrack = ET1297993
Titan cases:  291-011-673

Description:
   The policy execution manager (nbpem) would exit with an ASSERT failed
   error that indicated m_due was less than or equal to m_startTime.
   
   
--------------------------------------------------------------------------------
Etrack Incident = ET1317202
Associated Primary Etrack = ET1269997
Titan cases:  320-107-578

Description:
   Resource requests for bpduplicate (vault) were failing because of a
   missing parameter.  The Vault duplications would fail with a status 800.

Workaround:
   This would only occur when duplicating to storage units on
   pre-NetBackup 6.5 media servers where the master server is at 6.5 or later.
   The workaround would be to not target storage units on pre 6.5 media
   servers when duplicating.  It also will not be an issue for single-image
   duplications.
--------------------------------------------------------------------------------
Etrack Incident = ET1317047
Associated Primary Etrack = ET1293461
Titan cases:  240790925 281375544 290011922 291-010-092

Description:
   The Client Attribute "Maximum Data Streams" was being ignored with
   NetBackup 6.5.2 and the global value "Maximum jobs per client" was always
   taking precedence irrespective if the setting was higher or lower.
--------------------------------------------------------------------------------
Etrack Incident = ET1276489

Description:
   The bpexpdate -deassignempty command was failing to expire media on NDMP
   hosts.
--------------------------------------------------------------------------------
Etrack Incident = ET1318091
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 critical policies from the online
   catalog backup policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1318437
Associated Primary Etrack = ET1301899
Titan cases:  240-788-962

Description:
   Lotus Notes databases that were larger than 2GB would be treated as links
   and skipped from the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1316222
Associated Primary Etrack = ET1300428
Titan cases:  320-117-507

Description:
   The Activity Monitor jobs data was displayed wrong when using a
   NetBackup 6.5.2 administration console with a NetBackup 6.5.1 master server.
--------------------------------------------------------------------------------
Etrack Incident = ET1316255
Associated Primary Etrack = ET1292734
Titan cases:  220-320-996

Description:
   A change was made that ensures the NetBackup_Java Administration Console
   can display the Activity Monitor when administering a NetBackup 6.5.1
   master server.
--------------------------------------------------------------------------------
Etrack Incident = ET1316257
Associated Primary Etrack = ET1297807
Titan cases:  220-326-939

Description:
   A change has been added that ensures the NetBackup-Java Administration
   Console can be used to administer (modify or deactivate policies) on
   back-level, NetBackup master servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1289921

Description:
   If backup jobs and synthetic/duplicate jobs were in progress simultaneously,
   some of the drives would become unusable.

Workaround:
   If you encounter this issue, find the unusable drive and release it using
   the nbrbutil utility.
--------------------------------------------------------------------------------
Etrack Incident = ET1322984

Description:
   A change was made to address a bpbdm core dump issue that occurred when
   the client list was being freed when user interface executed a
   Q_IMAGE_HWOS_GET query and the get_hwos() would perform a double free of
   the client list.
--------------------------------------------------------------------------------
Etrack Incident = ET1364407

Description:
   When a policies schedule was changed the retention level was not correct
   when modified to a value other than the default value.
--------------------------------------------------------------------------------
Etrack Incident = ET1364422

Description:
   Synthetic Backup jobs would fail with a status 1 and were retried
   repeatedly.
--------------------------------------------------------------------------------
Etrack Incident = ET1322803
Associated Primary Etrack = ET1266944
Titan cases:  281-351-695 281-459-396

Description:
   If media servers or other hosts not in the server list attempted to connect
   to a master, the connection would be rightly rejected.  However, the
   diagnostic-logging-level 2 logging message itself used a non-threadsafe
   function that would cause memory corruption if threads collided.  This
   would lead to crashes or erratic behavior for services such as EMM and PEM.

Workaround:
   Search for "allow_peer" messages in the logs and reconfigure or
   decommision all of the servers that are logged as "not allowing
   connection".  These servers are not in the master's server list, which
   triggers the log message.  
   
   If the diagnostic logging level is set to not log Level 2 messages, the
   problem is averted.
--------------------------------------------------------------------------------
Etrack Incident = ET1364661

Description:
   A change was made to to correct an issue that caused NBPEM to crash during
   an upgrade from NetBackup 6.5 to 6.5.3. The crash would happen in a
   clustered environment when nbpem was shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET1373019

Description:
   All DSSU schedules were deleted (from PEM point of view) u