NB 6.5 Pack NB_6.5.4 README                                         May 11, 2009
Requirement: NB_CLT_6.5.4
Corequirement: NB_BMR_6.5.4
Directives: NBDB_Upgrade NBDB_Recover
SeqNumber: 20090214
================================================================================
This Release Update provides fixes for Veritas NetBackup (tm) UNIX servers.
NetBackup UNIX Add-on products, Database Agents, and the Java Interface have
separate Release Updates.

The UNIX CLT Release Update, which is required to be installed with this server
update, contains a full replacement of all client binaries for all platforms.
The local CLT binaries for this server may require as much as 100MB of free
space in the /usr partition to install, depending on platform.  If client
binaries are being loaded on a server to be pushed to clients, as much as 400MB
of free space may be required in the /usr partition.

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



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

    -- NB_CLT_6.5.4_<6 digit number>.tar must be installed before this
       Release Update is installed.

    -- Only if Bare Metal Restore is installed,
       NB_BMR_6.5.4_<6 digit number>.<platform>.tar must be installed after
       this Release Update is installed.

    -- Installation of this Release Update requires version 1.6.4.38 of the
       NB_update.install script.

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

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



I.    NEW FEATURES AND PLATFORM PROLIFERATIONS
        Platform Proliferations
        New Features and Enhancements
        End-of-Life Notifications
II.   KNOWN ISSUES
III.  DOWNLOAD INSTRUCTIONS
IV.   INSTALLATION INSTRUCTIONS
V.    UNINSTALL INSTRUCTIONS
VI.   CURRENT RELEASE UPDATE INDEX  
VII.  RELEASE UPDATE CONTENT
        Conventions
        Current Release Update
           NB_6.5.4
        Release Update History
           NB_6.5.3
           NB_6.5.2
           NB_6.5.1




============================================
I.  NEW FEATURES AND PLATFORM PROLIFERATIONS
============================================
This section contains subsections that describe 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 11.5 on Red Hat 4, 32 and 64 bit platforms. Also
  added support for Informix 11.5 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
    - SuSE 9 SP 3 on Intel/AMD x86 and x64
  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 (SLP) 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.



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




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

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

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



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

+  Exchange Granular Recovery known issues

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

+  NetBackup for SharePoint policies do not support multiple data streams.

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

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

+  (ET1446398) The Low water mark storage unit setting has no effect unless
  backups are written through a storage lifecycle policy, using the capacity
  managed retention type.

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

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




==========================
III. DOWNLOAD INSTRUCTIONS
==========================
1) Download the NB_CLT_6.5.4_<6 digit number>.tar and
  NB_6.5.4_<6 digit number>.<server>.tar files into the
  /tmp directory,

  where <6 digit number> is an internal tracking identifier

  where <server> is one of: alpha_5, hp_ux, hpia64,linux, linuxR_ia64,
  linuxS_ia64, linuxR_x86,linuxR_ia64, rs6000, solaris, solaris_x86
                   
    NOTE: NB_CLT_6.5.4_<6 digit number>.tar has the client binaries and
    NB_6.5.4_<6 digit number>.<server>.tar has the server binaries and BOTH
    must be installed.

    NOTE: Only if Bare Metal Restore is installed, download and extract the
    NB_BMR_6.5.4_<6 digit number>.tar into the /tmp directory and then
    download and extract the NB_BBS_6.5.4_<6 digit number>.tar file into
    the /tmp directory.


2) Extract the NB_CLT_6.5.4_<6 digit number>.tar and the
  NB_6.5.4_<6 digit number>.<server>.tar files.
       tar xvf NB_CLT_6.5.4_<6 digit number>.tar
       tar xvf NB_6.5.4_<6 digit number>.<server>.tar

       NB_6.5.4 will create the files:
       VrtsNB_6.5.4.README
       VrtsNB_6.5.4.<server>.tar.Z
       VrtsNB_6.5.4.preinstall
       VrtsNB_6.5.4.preuninstall
       VrtsNB_6.5.4.postinstall
       VrtsNB_6.5.4.postuninstall
       NB_update.install

       NB_CLT_6.5.4 will create the files:
       VrtsNB_CLT_6.5.4.README
       VrtsNB_CLT_6.5.4.<platforms>.tar.Z
       VrtsNB_CLT_6.5.4.preinstall
       VrtsNB_CLT_6.5.4.postinstall
       VrtsNB_CLT_6.5.4.postuninstall
       NB_update.install

       where <platforms> are: ALPHA,HP-UX-IA64,HP9000-800,INTEL,Linux-IA64,
       Linux,MACINTOSH,RS6000,SGI,SOLARIS




=============================
IV. INSTALLATION INSTRUCTIONS
=============================
** The content of this online Readme supersedes the information in the Readme
contained in the download. **

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

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

 - If you are planning to install this Release Update as a part of an upgrade
   from a NetBackup 6.0 MPx release, you must first install NetBackup 6.5 GA
   before you install this Release Update.

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

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

 - Do not use a NetBackup user interface running on any other host to monitor
   the NetBackup jobs/processes/daemons/devices on the host that is being
   patched during the installation. On AIX this may cause text busy errors to
   occur during the installation. The safest approach is to not have any user
   interfaces running on remote systems that are accessing any host during
   pack application.


To install this Release Update in a UNIX Cluster Environment:

1) Before you install this Release Update, make sure that NetBackup is at
  release level 6.5 and configured to run in a cluster.

2) Install this Release Update on the inactive node(s) of the cluster first.
  (Perform the steps in the, "To install this Release Update as root on the
   NetBackup Server" procedure).

3) Install this Release Update on the active node of the cluster.
  (Again, perform the steps in the, "To install this Release Update as root
   on the NetBackup Server" procedure).

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

  NOTE: A directory "NB_6.5.4" is created in the cluster shared directory.
        This directory stores files that will be needed during an uninstall.
        Do not remove it.

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

To install this Release Update as root on the NetBackup Server:

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

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

2) Install NB_6.5.4 and NB_CLT_6.5.4 Release Update binaries.

       cd /tmp
       /bin/sh NB_update.install

  NOTE: Selecting the server Release Update automatically installs the
        client Release Update if the client (CLT) .Z file and the README exist
        in the installation directory. The server install fails if the (CLT)
        .Z file and the README are not present and the CLT update has not been
        previously installed. The client Release Update will NOT be installed
        automatically during a reinstall of the server Release Update.  

3) The NB_update.install script prompts you to restart daemons.
  Otherwise, after the update installation has completed, run:

       /usr/openv/netbackup/bin/bp.start_all

  You can find the update install logs in /usr/openv/pack/pack.history after
  the installation is complete.

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

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

NetBackup 6.5.4 adds server support for AIX 6.1.  Use the following steps to
install this Release Update on an AIX 6.1 system:

 1. Install PBX from the NB_65_ICS_1.4.40.0_AIX image.  
 2. Install NetBackup 6.5 GA.
 3. Apply the NetBackup 6.5.4 Release Update.




=========================
V. UNINSTALL INSTRUCTIONS
=========================

Note:  This will ONLY uninstall the Release Update from your local machine.


--------------------------------------------------------------------------------
To uninstall this Release Update in a UNIX Cluster Environment:

1) Freeze the cluster to prevent failover during the uninstall.

2) Uninstall this Release Update on the inactive node(s) of the cluster first.

3) Uninstall this Release Update on the active node of the cluster.

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

5) Be sure to uninstall both client and server updates on each node before
  proceeding to the next step.

6) Unfreeze the cluster.
--------------------------------------------------------------------------------

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

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

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

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

3) Run the un-install script:

    ./NB_update.uninstall

4) Verify that the 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
 



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





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

Description:
   A change has been added to address an issue that caused a bpdbm core dump
   while creating a new policy .
--------------------------------------------------------------------------------
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 = 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 = 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 = ET700722

Description:
   A change was made to improve the time it would take for NBSL to send the
   DriveThroughput information.
--------------------------------------------------------------------------------
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 = ET1221450

Description:
   NOM requires NBSL interface for collecting media server information.  
--------------------------------------------------------------------------------
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 = ET1245767

Description:
   Some error descriptions could not be found for errors within nbemm.  
--------------------------------------------------------------------------------
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 = 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 = ET1365476

Description:
   Virtual Synthetics code changes have been added to the release update.  
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = ET1384505

Description:
   The ps output showed arguments out of order causing bpps to not detect a
   running nbemm on an AIX system.  
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = ET1413113

Description:
   The "make messages" failed because of a duplicated ID issue of the file
   bpfis.c.
--------------------------------------------------------------------------------
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 = 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 = 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 = ET1410798

Description:
   After NBJM was shutdown, the Windows Event Manager would sometimes
   report that job manager service stopped unexpectedly.  
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = ET1441498

Description:
   A change has been made to address an issue that would cause NBPEM to
   sometimes crash during a shutdown operation.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = ET1437425

Description:
   The Hitachi_CopyOnWrite FIM was not supported for the USP/USP-V series
   of arrays.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = ET1458226

Description:
   The vnet_connect would retry infinitely for Address Not Available errors.
   This would result in very large log files.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = ET1474475

Description:
   NBJM would crash while starting a lifecycle job (bpduplicate) on a
   Windows IA64 platform.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = ET1478915

Description:
   The job details in the bpdbjobs output (with -all_columns) would show
   misleading text for the file path being written.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = ET1488525

Description:
   A change has been added to ensure that nbstserv is capable of
   duplicating more than one image at a time.  
--------------------------------------------------------------------------------
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 = 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 = ET1507663

Description:
   bpclusterkill was not working when called from a cluster offline script.
--------------------------------------------------------------------------------
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 = ET1507033

Description:
   A change was made to properly display triple-dot (x.x.x.x) NetBackup
   versions with tpconfig -emm_dev_list.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = ET1529861

Description:
   The nbdb_backup command would not print the correct error string in
   unicode environments.
--------------------------------------------------------------------------------
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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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 = 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.
--------------------------------------------------------------------------------



Release Update History
----------------------

This section contains an accumulative list of all Release Update information
contained in previous releases.

========
NB_6.5.3
========

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 = 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 = 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) upon updating one
   DSSU schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET1383374
Associated Primary Etrack = ET1300103
Titan cases:  320-117-348

Description:
   bprd would core dump under certain circumstances when there was an invalid
   media server in the server list and the configuration was being updated.
--------------------------------------------------------------------------------
Etrack Incident = ET1382658
Titan cases:   220-327-515

Description:
   If the VNET_OPTIONS entry was defined in your configuration (bp.conf
   on UNIX or the Registry on Windows) and if some values in the entry were
   zero, problems would occur if you attempted to upgrade to NetBackup 6.5.2
   or later.  An example entry would be:
   
   VNET_OPTIONS = 120 3600 0 0 0 0 0 0 0
   
   If you attempt to run with this entry in NetBackup 6.5.2 or later,
   networking will not work on your machine.
   

Workaround:
   If you encounter this issue, remove the VNET_OPTIONS entry from your
   configuration before you upgrade, or replace the 0-values in the entry
   with the NetBackup 6.5.2 defaults before upgrading.
   
   For example:
   
   VNET_OPTIONS = 120 3600 200 40 3 1 30 0 0 0
--------------------------------------------------------------------------------
Etrack Incident = ET1383586
Associated Primary Etrack = ET1295782

Description:
   For SharedDisk volumes, the unmount event triggers a clean up of all the
   committed space allocated for the backup. If the unmount event is missed,
   the volume may appear over-committed and may not get picked for future
   backups. As a results, MDS would not find any available Shared Disk volumes
   and backups in a pure Shared Disk environment would queue indefinitely.
--------------------------------------------------------------------------------
Etrack Incident = ET1383584

Description:
   An issue existed that caused jobs to fail with a status 16: unimplemented
   feature error.
--------------------------------------------------------------------------------
Etrack Incident = ET1184889
Titan cases:  220-111-009

Description:
   Cache results of server list comparisons for CORBA communications. The
   cache is intended to improve performance for configurations with a large
   number of hosts in the server list.
--------------------------------------------------------------------------------
Etrack Incident = ET1276613
Associated Primary Etrack = ET1135854
Titan cases:  281-213-065

Description:
   During long running back up jobs, the firewall between the master and
   media server will close connection if it is configured to do so. This
   causes a break in communication between the master and media server and
   a failure of backups.

Workaround:
   If you encounter this issue, disable the firewall timeout.  However, this
   may be detrimental to firewall security.
--------------------------------------------------------------------------------
Etrack Incident = ET1382632
Associated Primary Etrack = ET1238838
Titan cases:  311-880-802

Description:
   A NetBackup service such as nbjm would sometimes abort, leaving a core
   dump. A change has been made to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1383839
Titan cases:  220-337-212

Description:
   On some AIX systems, it was discovered that ltid would not start. The
   stdout error is "Unable to get external file version from EMM database".
   The logs show the following CORBA error: "Msg exceeds maximum allowed size".

Workaround:
   You can avoid this issue by setting LANG=C in the shell before starting
   ltid.
   
   You an also change the system default by editing /etc/environment.
--------------------------------------------------------------------------------
Etrack Incident = ET1383438
Associated Primary Etrack = ET1322123
Titan cases:  240-776-132

Description:
   A change was made to improve the parsing of the Job Try file in nbproxy
   because it would take a long time.
--------------------------------------------------------------------------------
Etrack Incident = ET1383440
Associated Primary Etrack = ET1269781
Titan cases:  290-988-768

Description:
   The NetBackup Service Layer (NBSL) would core dump under a load from NOM
   data queries: NBPolicyCollector::Collect.
--------------------------------------------------------------------------------
Etrack Incident = ET1383434
Associated Primary Etrack = ET1234532
Titan cases:  220-236-821

Description:
   When you stop the services from the NetBackup Administration Console, the
   services would go away and you could not restart them from user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1383442
Associated Primary Etrack = ET1281452
Titan cases:  230-535-095

Description:
   After running activate and deactivate policies in NOM the NetBackup-Java
   Adimistration Console was unable to read policies.
--------------------------------------------------------------------------------
Etrack Incident = ET1383733
Associated Primary Etrack = ET1372893

Description:
   If NetBackup services are restarted when jobs using shared disk are active,
   the NetBack Resource Broker (nbrb) may not be able to de-allocate resources
   properly on a restart. nbrb unmounts the shared disks correctly but fails
   to inform MDS to de-allocate the resources.

Workaround:
   If you encounter this issue, re-start the services, then wait between 5
   and 10 minutes, and then run "nbrbutil -resetall" if no jobs are active.
   This will de-allocate the resources. If the jobs are active, you should
   wait for the jobs to finish before you run nbrbutil -resetall.
--------------------------------------------------------------------------------
Etrack Incident = ET1383750
Associated Primary Etrack = ET1361178
Titan cases:  220-349-593 320-132-770

Description:
   If the MDS allocations were removed directly either using the
   nbrbutil -releaseMDS command or by deleting the record from database,
   the NetBackup Resource Broker (nbrb) would not be able to remove the
   corresponding allocation records from its database. This would cause the
   resource broker's drive cache to misbehave, for example, jobs may not
   get the resources even when the drives were available, and perform other
   redundant operations which consumes CPU cycles.
--------------------------------------------------------------------------------
Etrack Incident = ET1383540
Associated Primary Etrack = ET1296912
Titan cases:  220-325-975 281-378-560

Description:
   A change has been made to address an issue that would cause a multiple
   copy, Oracle database backup to fail in some situations.
--------------------------------------------------------------------------------
Etrack Incident = ET1384029
Titan cases:  291-009-192

Description:
   The FT Target Mode HBA was unable to login to the switch in F-Port mode.
   Only the L-port login would work. This issue applied to all HBA firmware
   variants that are supported - ISP2312, ISP2422 and ISP2432.
   
   If a particular fabric setup only supports F-Ports, then FT backups could
   not be performed.  
--------------------------------------------------------------------------------
Etrack Incident = ET1375483

Description:
   A change was made to correct a timing issue that bpduplicate would
   encounter when it tried to get the job priority from bpjobd, which would
   sometimes take longer than expected.
--------------------------------------------------------------------------------
Etrack Incident = ET1383736
Associated Primary Etrack = ET1278280
Titan cases:  320-111-786

Description:
   The nbemmcmd -renamehost command would not update the hostname that the
   DA_Thread_Pool uses for the heartbeat check.

Workaround:
   If you encounter this type of issue, rename a host with the nbemmcmd
   -renamehost command and then stop and start nbemm.
--------------------------------------------------------------------------------
Etrack Incident = ET1383527
Titan cases:  222-222-222

Description:
   When applying a NetBackup server patch, a change was made so that local
   modifications to the server.conf file will not be lost.

Workaround:
   To ensure any local modifications to the server.conf are not removed, add
   the following line to the vxdbms.conf file to turn off automatic
   server.conf updates:
   
      VXDBMS_SELF_TUNING=OFF
--------------------------------------------------------------------------------
Etrack Incident = ET1383523
Associated Primary Etrack = ET1300087
Titan cases:  240758288

Description:
   The stale port connection on the media server was being terminated by the
   firewall.

Workaround:
   If you encounter this issue, lengthen the firewall's timeout time or
   disable that feature for an approved IP address.
--------------------------------------------------------------------------------
Etrack Incident = ET1384879

Description:
   The NetBackup Database Manager would core dump when trying to log a debug
   message while adding an image fragment.
--------------------------------------------------------------------------------
Etrack Incident = ET1385083 ET1385111 ET1386294
Associated Primary Etrack = ET1278625
Titan cases:  230-605-520

Description:
   On an extremely busy system, the bpdbm service could experience two
   intermittent problems:
   
   1. The service could hang for 30 minutes after starting a
      Q_IMAGE_READ_FILES_FILE query, and eventually cause bpdbm to
      terminate with a status code 63.
   
   2. A Q_IMAGE_READ_FILES_FILE query would be processed successfully by
      bpdbm, but the socket would be closed on Windows platforms in a
      manner that caused the bptm process that issued the query to fail
      with a Windows status code of 10054.
--------------------------------------------------------------------------------
Etrack Incident = ET1383757
Associated Primary Etrack = ET1316106
Titan cases:  320-117-413

Description:
   NetBackup Job Manager (nbjm) delays 90 minutes making thousands of
   JMUtility::updateParamsFileWOFB calls between receiving resources and
   starting bpbrm.  This delay affected scheduled and user-directed backup
   jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1384675
Associated Primary Etrack = ET1318016
Titan cases:  240-790-104

Description:
   Restoring a backup taken with a storage unit that contains the application
   cluster virtual name would fail because NetBackup was unable to determine
   the NetBackup version of the application cluster name.
--------------------------------------------------------------------------------
Etrack Incident = ET1383511
Associated Primary Etrack = ET1318015
Titan cases:  281-380-220

Description:
   A FlashBackup restore from an AIX RS6000 master would fail with a
   status 5 error.
--------------------------------------------------------------------------------
Etrack Incident = ET1385061
Associated Primary Etrack = ET1269930
Titan cases:  220-289-048

Description:
   If the primary lifecycle policy was set to inactive for a long period
   of time (for example, four days) then reactivated, it was possible that
   a large number of images would need to be processed. In this scenario,
   nbstserv would use so much memory that a core dump would occur.
--------------------------------------------------------------------------------
Etrack Incident = ET1382599

Description:
   The snapshot policy wizard would recommend the obsolete VSS_Transportable
   FIM. This has been corrected to recommend the VSS FIM, which can be used
   in local and offhost (Alternate Client) backup environments.
--------------------------------------------------------------------------------
Etrack Incident = ET1376805

Description:
   The NetBackup Job Manager (NBJM) would crash on shutdown because expired
   snapshots taken during non-streamed windows open file backup (WOFB) jobs
   were deleted.  
--------------------------------------------------------------------------------
Etrack Incident = ET1383782

Description:
   Synthetic schedules with a space specified in the keyword field would
   make the job fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1383502

Description:
   A change was made to correct an issue that caused the Point-in Time (PIT)
   restore to fail on an AIX platform.
--------------------------------------------------------------------------------
Etrack Incident = ET1383497
Associated Primary Etrack = ET1262210
Titan cases:  281-343-506


Description:
   A change was made to resolve an issue in the V_string function that
   would cause bpfis to crash.
--------------------------------------------------------------------------------
Etrack Incident = ET1383499

Description:
   A change was made to ensure proper cleanup occurs when a Snapshot backup
   fails at a stage after a Flashcopy was created at the array level.
--------------------------------------------------------------------------------
Etrack Incident = ET1384270
Associated Primary Etrack = ET1297816
Titan cases:  240-786-065

Description:
   The NetBackup cluster monitor for AIX would incorrectly detect the
   unavailability of the NB_dbsrv daemon.
--------------------------------------------------------------------------------
Etrack Incident = ET1386057
Associated Primary Etrack = ET1253903
Titan cases:  290-975-130

Description:
   A change was made to correct a bpdbm core dump issue found in the
   function, db_get_image_info() in strerror().
--------------------------------------------------------------------------------
Etrack Incident = ET1386060
Associated Primary Etrack = ET1281512
Titan cases:  311-821-936

Description:
   Crosschecking Oracle images (Q_IMAGE_BY_FILE) would fail if the image list
   existed for the client.

Workaround:
   Remove the index files.
--------------------------------------------------------------------------------
Etrack Incident = ET1383811 ET1383808 ET1382683
Associated Primary Etrack = ET1244548 ET1241226
Titan cases:  230-521-343 311-880-025 290-934-270

Description:
   A change was added to address an issue that caused NetBackup Policy
   Execution Manager (nbpem) to shut down.
--------------------------------------------------------------------------------
Etrack Incident = ET1384822

Description:
   NBPEM would deadlock if restarted while jobs were in an INCOMPLETE state
   and new jobs were started for the same policy/client.
--------------------------------------------------------------------------------
Etrack Incident = ET1386064

Description:
   A change has been added to eliminate a potential vmd core dump issue when
   the EMM initialization failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1386062

Description:
   The required tape parameters for NetBackup were not being set correctly
   on multi-path drives on AIX platforms. Only the first path had extended
   files marks and variable block set correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET1386073

Description:
   Could not delete the virtual_machine machine type with the nbemmcmd
   command.
--------------------------------------------------------------------------------
Etrack Incident = ET1383727

Description:
   Policy Execution Manager would schedule a disk staging policy to run when
   it should not. This happened because a policy event was not sent to the
   Policy Execution Manager when a disk staging schedule was added.
--------------------------------------------------------------------------------
Etrack Incident = ET1383766
Associated Primary Etrack = ET1369292
Titan cases:  320-121-094

Description:
   If a policy had a client named more than once with different aliases,
   the Policy Execution Manager (PEM) would start both even though only one
   was requested.  If the backup was a user in which bprd supplies the jobid,
   it would use the same jobid for both jobs and would assert when trying to
   add it to the map.
   
   A fix was added to ensure that a client is not specified more than once
   in a policy by different names.
--------------------------------------------------------------------------------
Etrack Incident = ET1386069
Associated Primary Etrack = ET1266200

Description:
   Running bpgetmedia would not return tapes from all robots.
--------------------------------------------------------------------------------
Etrack Incident = ET1384960

Description:
   Calling changeMediaDBAllMediaForServer with NetBackup Access Control (NBAC)
   enabled would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1386075
Associated Primary Etrack = ET1366874
Titan cases:  240-724-837

Description:
   The performance of the API which lists shared drives and hosts would
   decreases significantly as the amount of hosts and drives increased.
--------------------------------------------------------------------------------
Etrack Incident = ET1386077
Titan cases:  240-829-613

Description:
   An SQL error was received when attempting to delete a cluster.
--------------------------------------------------------------------------------
Etrack Incident = ET1384019
Associated Primary Etrack = ET1273804
Titan cases:  281-334-212

Description:
   Setting the Media Mount timeout to a value other than 0 minutes can
   sometimes result in the Media Mount Timeout occurring even if the mount
   succeeds.  A chance signal timing issue resolved this problem.
--------------------------------------------------------------------------------
Etrack Incident = ET1386065

Description:
   When the initial try of an Exchange VSS snapshot parent job failed, the
   second try would fail with a status 801.
--------------------------------------------------------------------------------
Etrack Incident = ET1386070

Description:
   The bpmedialist command, when given parameters involving a particular
   media ID whose length is less than six characters, would fail.  

Workaround:
   If you should encounter this issue, execute the command with the volume
   name enclosed in double quotes and padded by spaces so that the length of
   the volume name is six characters.  
--------------------------------------------------------------------------------
Etrack Incident = ET1387046

Description:
   When attempting to run an Oracle backup on a Master server that is
   configured with the Required_Interface setting, bpdbsbora would fail to
   connect and the job failed with a status 29. This occurred because nbjm
   did not pass the "-ri <reqd interface>" option to the bpbrm command line
   by nbjm. The NetBackup Job Manager passed the new option only if the
   media server version was 6.5.2 or greater. Since nbrb is returning the
   media server version as 0, nbjm did not pass the new
   "-ri <reqd interface>" option.
--------------------------------------------------------------------------------
Etrack Incident = ET1383743
Associated Primary Etrack = ET1318931
Titan cases:  220-337-034

Description:
   Implementing media_deassign_notify script resulted in <defunct> processes.

Workaround:
   To resolve this issue, setIgnoreSigChild() was added to OrbService() to
   ensure that EMM does not leave <defunct> processes when children complete
   from NOTIFY script execution.
--------------------------------------------------------------------------------
Etrack Incident = ET1384952
Associated Primary Etrack = ET1374144
Titan cases:  320-123-939

Description:
   Duplication of NDMP disk image to tape would fail with a status 191 error.
--------------------------------------------------------------------------------
Etrack Incident = ET1387039

Description:
   Libraries that provide self-cleaning would sometimes cause normal media to
   be frozen if they self-clean very quickly after a normal media was unloaded.
--------------------------------------------------------------------------------
Etrack Incident = ET1383643
Associated Primary Etrack = ET1321325
Titan cases:  281-358-993

Description:
   The following error would occur after an App_cluster was failed over.
      EMM status: Disk volume is down resource request failed(800)
--------------------------------------------------------------------------------
Etrack Incident = ET1384946
Associated Primary Etrack = ET1361273
Titan cases:  320-121-830

Description:
   A change was made to address an nbjm core dump issue that occurred in
   BPCRConnector handleReferenceCnt.
--------------------------------------------------------------------------------
Etrack Incident = ET1384943
Associated Primary Etrack = ET1316765
Titan cases:  220-338-008

Description:
   A change was made to address an nbjm core dump issue that occurred near
   JobState::endItemChange +1c0.
--------------------------------------------------------------------------------
Etrack Incident = ET1388149

Description:
   The command line interface, nbdb_admin -validate, would not return the
   full result set on Windows platforms.  

Workaround:
   If you should encounter this issue, use the NbDbAdmin Windows user
   interface to run validation.
--------------------------------------------------------------------------------
Etrack Incident = ET1384948
Associated Primary Etrack = ET1287214
Titan cases:  220-289-079

Description:
   The status code within the Try # was incorrect.  The status code would
   show 0 even though it had failed and another attempt was made.
--------------------------------------------------------------------------------
Etrack Incident = ET1383744
Associated Primary Etrack = ET1261795
Titan cases:  220-280-182

Description:
   Changes were made to improve slow resource allocations for jobs using
   storage unit (STU) groups and prioritized allocation. The behavior that
   was seen is thus:
     - An STU group is looked at and an STU is identified within the group.
     - The Enterprise Media Manager (EMM) finds a drive (even if it is
         waiting for an unload) on the highest ranking media server in the
         group (regardless if there are drives that are immediately
         available on other STU's in the group)
     - EMM then allocates that drive - without looking for any other
         available drives.
     - The process is repeated, again, not looking for any other STU's in
         the group (which have many available drives).
--------------------------------------------------------------------------------
Etrack Incident = ET1386199
Associated Primary Etrack = ET1294136
Titan cases:  291-009-192

Description:
   On some T5220 systems running Solaris 10 SPARC, the system would hang
   during a reboot if windrvr6 was configured in the /etc/driver_aliases
   file to bind to QLogic devices.
   
   This issue can be prevented by installing FT server module windrvr6 only
   after the system boots. In addition, it can be impelemented in the
   configuration scripts - nbftsrvr_config and nbftsrvr
   
   To avoid hangs on subsequent reboots, remove windrvr6 entries from the
   /etc/driver_aliases file.
--------------------------------------------------------------------------------
Etrack Incident = ET1384909
Associated Primary Etrack = ET1204445
Titan cases:  220-302-209 320-083-263

Description:
   After upgrading to NetBackup 6.5, 5.X DSSU images were not appropriately
   expired from disk, causing the DSSU to fill to capacity.

Workaround:
   If you encounter this issue, you can invoke the nbdelete -allvolumes
   command repeatedly until images are removed from disk.
--------------------------------------------------------------------------------
Etrack Incident = ET1389088
Associated Primary Etrack = ET1387311
Titan cases:  240-813-600

Description:
   Logging from vnet_cached_gethostbyname() would increase significantly in
   NetBackup 6.5.2 if VERBOSE = 5 in the bp.conf file.

Workaround:
   To avoid this issue, reduce VERBOSE to a value less than 5.
--------------------------------------------------------------------------------
Etrack Incident = ET1374330
Associated Primary Etrack = ET1374122
Titan cases:  311976123

Description:
   The UNIX pack install now supports IBM zSeriesRedHat and zSeriesSuSE client
   installs.
--------------------------------------------------------------------------------
Etrack Incident = ET1388180

Description:
   The NetBackup Administration Consoles for Windows and Java, and the NOM
   user interface display "No" in the "Incompliance Column" for
   capacity-based licenses (for example, Flexible Disk, OpenStorage, and
   PureDisk) when an unlimited key is installed and the used capacity for the
   licensed feature is greater than 0.  
--------------------------------------------------------------------------------
Etrack Incident = ET1383756
Associated Primary Etrack = ET1304028
Titan cases:  291-010-529

Description:
   After an upgrade from NetBackup 6.5.1 to 6.5.2, a progress log message was
   missing and caused monitoring scripts to fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1388192
Associated Primary Etrack = ET1210846
Titan cases:  320-074-322

Description:
   A change has been made to address an issue that caused duplication from
   disk staging to fail with a status 50.  The fix involved adding a missing
   acknowledge in bptm. bpduplicate sends put_short message to bptm as an
   acknowledge in communication, however bptm was missing a get_short message
   so it would hang while waiting for a get_long from message bpduplicate.
--------------------------------------------------------------------------------
Etrack Incident = ET1382684
Associated Primary Etrack = ET1375497
Titan cases:  220-404-140 230-572-942 240-806-831

Description:
   The time required to start nbpem can be large when there are a number of
   client names in the client attributes list.

Workaround:
   To avoid this issue, reduce the size of the client attributes list.
--------------------------------------------------------------------------------
Etrack Incident = ET1383404
Associated Primary Etrack = ET1378835
Titan cases:  291-031-055

Description:
   Catalog backups initiated by Vault profiles were not restorable because
   no True Image Restore (TIR) information was generated.
--------------------------------------------------------------------------------
Etrack Incident = ET1390335
Associated Primary Etrack = ET1167923
Titan cases:  230-482-665 240655547 311-873-262

Description:
   Certain backup and archive jobs would fail because of a timing issue with
   bpbrm.  The following error string would be recorded in the bpbkar log.
   
      get_string_: protocol error - string read failed (Timer expired)

Workaround:
   If you encounter this issue, try restarting the job to fix the issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1383742
Associated Primary Etrack = ET1238943
Titan cases:  220-250-211

Description:
   Changes were added to improve hostname caching.
--------------------------------------------------------------------------------
Etrack Incident = ET1383761
Associated Primary Etrack = ET1319339
Titan cases:  220-369-133 281-386-485 291-011-047

Description:
   If a calendar schedule window spanned midnight, jobs were started at
   midnight, not when the calendar schedule window actually opened.  Also,
   calendar schedules that span midnight could fail at midnight with a
   status 196.
--------------------------------------------------------------------------------
Etrack Incident = ET1391168
Associated Primary Etrack = ET1198807
Titan cases:  240707776

Description:
   In the NOM user interface, the Reports were not being emailed after a few
   days, however, the reports would appear as "Sending Email..." in the
   status column.  
--------------------------------------------------------------------------------
Etrack Incident = ET1382623
Associated Primary Etrack = ET1297752
Titan cases:  290-937-204

Description:
   Restore of a backup with a large number of mangled filenames can be slow
   due to searching the file @MaNgLeD.<pid> to find the non-mangled name.  
--------------------------------------------------------------------------------
Etrack Incident = ET1391109

Description:
   bpjobd would core dump on some platforms while changing the job priority
   dynamically.
--------------------------------------------------------------------------------
Etrack Incident = ET1383763
Associated Primary Etrack = ET1321939
Titan cases:  220-335-223 291-058-053

Description:
   Script-based BLI incremental backups would run as full backups after an
   upgrade from NetBackup 6.5.1 to 6.5.2. The Scheduler was starting bpbrm for
   incremental BLI backups with inappropriate options that forced a full
   backup.  
--------------------------------------------------------------------------------
Etrack Incident = ET1394025
Associated Primary Etrack = ET1382322
Titan cases:  281-251-179

Description:
   If the MPX was greater than 1 within the policy schedule, then the
   checkpoints on the disk backups would hang.
--------------------------------------------------------------------------------
Etrack Incident = ET1383630
Associated Primary Etrack = ET1319057
Titan cases:  220-371-648 291-015-879

Description:
   SQL Server backups would failed with a Status 6 and "SET SNAP_ID" errors.
--------------------------------------------------------------------------------
Etrack Incident = ET1392132
Associated Primary Etrack = ET1363804
Titan cases:  291-026-369

Description:
   The granular_proxy option has been added in bpjava. This was required
   for the Exchange policy for NetBackup 6.5.2 and above.  This fix ensures
   that the BPRD_BPLIST protocol/224 will be executed correctly for the
   Exchange policy type.
--------------------------------------------------------------------------------
Etrack Incident = ET1388236
Associated Primary Etrack = ET1252473
Titan cases:  320-105-171 320-122-006

Description:
   bpgp was removed, and a replacement to set and get the include and
   exclude lists from clients was not provided.  
--------------------------------------------------------------------------------
Etrack Incident = ET1384020
Associated Primary Etrack = ET1276427
Titan cases:  220-269-379

Description:
   A change was made to address an issue where a Storage Lifecycle Policy
   (SLP) would attempt to duplicate an image even when all of the required
   copies were already made.
--------------------------------------------------------------------------------
Etrack Incident = ET1395057
Associated Primary Etrack = ET1394282
Titan cases:  311-968-542

Description:
   Basic disk staging jobs would always start with a priority of 99999 even
   if the priority defined in staging schedule was different.
--------------------------------------------------------------------------------
Etrack Incident = ET1384919

Description:
   The duplication manager should process successful backup-only images as
   lifecycle complete even if the lifecycle is inactivated.
   
   As of NetBackup 6.5.2, the duplication manager would ignore all images
   if the lifecycle is inactivated. This was to stop any duplication jobs
   running for such images while backups are happening.
   
   However, this also stops the processing of backup-only (ITC) images that
   have created expected backup copies to be considered as lifecycle
   complete. Therefore, until the lifecycle is not activated back, such
   images, though have been completed, will sit as lifecycle incomplete and
   will not expire even if their expiration date arrives.
--------------------------------------------------------------------------------
Etrack Incident = ET1383792

Description:
   A change was added to address an issue that caused duplication jobs for
   a Storage LifeCycle Policy to not run.
--------------------------------------------------------------------------------
Etrack Incident = ET1383772
Associated Primary Etrack = ET1378715

Description:
   Shared disk images were not being deleted from the LUN's.  
--------------------------------------------------------------------------------
Etrack Incident = ET1393919

Description:
   The nbemmcmd command would crash if the emmname parameter provided was
   longer than the emmname parameter in the bp.conf file.
--------------------------------------------------------------------------------
Etrack Incident = ET1384032
Associated Primary Etrack = ET1366836
Titan cases:  311-972-942 320-124-684

Description:
   SLP would not remove the NDMP tape copies or image records from EMM even
   after expiration occurred.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1384023
Associated Primary Etrack = ET1297806
Titan cases:  220-320-623

Description:
   Duplication of an image after it is SLP complete would result in
   re-insertion in EMM.

Additional Notes:
   When nbstlutil lists backups, the images that were previously listed in
   an UNKNOWN state were now labeled as NOT MANAGED.
--------------------------------------------------------------------------------
Etrack Incident = ET1384966
Associated Primary Etrack = ET1269930
Titan cases:  220-289-048

Description:
   When there were many lifecycle-managed backups needing to be completed, it
   would take inordinately long to process them.
--------------------------------------------------------------------------------
Etrack Incident = ET1395393
Associated Primary Etrack = ET1316801
Titan cases:  220-336-949

Description:
   A change was made to resolve a deadlock issue between BRMComm and
   ExportedResourceMgr where the BRMComm and ERM locks were being obtained
   in reverse order.  
--------------------------------------------------------------------------------
Etrack Incident = ET1383506
Associated Primary Etrack = ET1375866
Titan cases:  240-839-625 320-122-461

Description:
   SAP with RMAN restore would fail because of a missing Oracle license.
   The Oracle license was not required for SAP backup or restore.
--------------------------------------------------------------------------------
Etrack Incident = ET1396153

Description:
   NOM could not export Job logs from the Job details page.
--------------------------------------------------------------------------------
Etrack Incident = ET1391110

Description:
   If a storage lifecycle is configured without duplication copies and if one
   of the backup copies is configured with "Expire After Duplication", then
   the copy (and the image if there was only a single backup copy) is
   expired from the catalog by the storage lifecycle. However, this is an
   incorrect configuration and the "Expire After Duplication" retention type
   should not be allowed for backup destinations if there are no duplication
   destinations in the storage lifecycle.
--------------------------------------------------------------------------------
Etrack Incident = ET1397984

Description:
   The std::istringstream.str string did not work on a TRU64 platform to
   initialize an istringstream object.
--------------------------------------------------------------------------------
Etrack Incident = ET1399794

Description:
   Missing content was added to the NetBackup UNIX help that appears in the
   NetBackup Archive and Restore interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1393810

Description:
   A change was added to resolve an NBPEM core dump issue that occurred on
   a Tru64 master server.
--------------------------------------------------------------------------------
Etrack Incident = ET1393798

Description:
   A change was made to address a core file issue that was generated by
   nbshareddisk when formatting Shareddisk LUNs using the -novm option.
--------------------------------------------------------------------------------
Etrack Incident = ET1397604

Description:
   Unable to delete an app_cluster machine record.
--------------------------------------------------------------------------------
Etrack Incident = ET1398627
Associated Primary Etrack = ET1397478
Titan cases:  320-129-580

Description:
   The NetBackup Service Layer (nbsl) was consuming too many file descriptors
   when NOM was enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET1388000
Associated Primary Etrack = ET1380098
Titan cases:  220-371-768

Description:
   Some of the values in LIFECYCLE_PARAMETERS file did not have reasonable
   upper limits for enterprise environments. For example, the
   MIN_KB_SIZE_PER_DUPLICATION_JOB and MAX_KB_SIZE_PER_DUPLICATION_JOB
   parameters are internally read into long type variables that would
   overflows before a reasonable value could be met.  
--------------------------------------------------------------------------------
Etrack Incident = ET1387827

Description:
   A change was made to address a nbstserv core dump issue that caused
   duplication job to longer run.  
--------------------------------------------------------------------------------
Etrack Incident = ET1393793
Associated Primary Etrack = ET1386040
Titan cases:  311-991-329

Description:
   There would be slow performance for bptm -delete_all_expired when attempting
   to deassign media that had expired before all the fragments had been
   duplicated to their final destination.
--------------------------------------------------------------------------------
Etrack Incident = ET1396248

Description:
   In SLP, if the duplication STU is "any available", it could also pick
   the basic disk STU.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1402394

Description:
   Storage servers and snap vault filers were being listed as NDMP in
   nbemmcmd.  The verbose output will indicate that these servers are snap
   vault and storage server.
--------------------------------------------------------------------------------
Etrack Incident = ET1396112

Description:
   A change was made to address issue that would cause NBJM crash on shutdown
   on Linux.
--------------------------------------------------------------------------------
Etrack Incident = ET1395233
Titan cases:  311-907-984

Description:
   ltid would hang if REQUIRED_INTERFACE was specified and the EMM server was
   rebooted.
--------------------------------------------------------------------------------
Etrack Incident = ET1402922

Description:
   LTID would send an UpdateMountStat request with a corrupted MediaId
   parameter.
--------------------------------------------------------------------------------
Etrack Incident = ET1403920

Description:
   A change was made to address a BPTM core dump issue that would occur on
   AIX and HP-UX media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1405290
Associated Primary Etrack = ET1288659
Titan cases:  320-111-170

Description:
   The "Failover" selection method of storage unit groups may not be
   respected with multiplexing set.
--------------------------------------------------------------------------------
Etrack Incident = ET1402967

Description:
   In BAR user interface, after selecting the "Point in Time Rollback" option,
   the backed-up images were not visible in the Restore tab.
--------------------------------------------------------------------------------
Etrack Incident = ET1320530

Description:
   If a synthetic schedule is added to a policy after the regular schedules
   have run and created the streams file information, immediate execution of
   the schedule will fail with a 200 status and scheduled execution never
   happens. This is due to missing streams file information.

Workaround:
   If you encounter this issue, run a non-synthetic backup after adding the
   synthetic schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET1398698
Associated Primary Etrack = ET1383617
Titan cases:  240-806-831

Description:
   The nbpem startup can be slow in large environments with a large number
   of clients.  Jobs are not scheduled until nbpem startup is complete.
--------------------------------------------------------------------------------
Etrack Incident = ET1396083

Description:
   A change was added to address an nbpem core dump issue that would occur on
   Linux after a hot catalog backup job completed.
--------------------------------------------------------------------------------
Etrack Incident = ET1392668

Description:
   Checkpointed jobs were not resumed automatically after a cluster failover.
--------------------------------------------------------------------------------
Etrack Incident = ET1409131
Associated Primary Etrack = ET1206358
Titan cases:  281-179-782

Description:
   NetBackup performance, both its daemons or services and in the user
   interface, will be negatively impacted when DNS services are slow to
   return hostname or 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 will delay NetBackup, and cause the
   user interface to be non-responsive.
   
   This change logs the offending hostname whenever such a lookup 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 = ET1409154

Description:
   When suspended jobs were resumed more than once, it would cause jobs to
   fail with a status 801.
--------------------------------------------------------------------------------
Etrack Incident = ET1411251
Associated Primary Etrack = ET1285409
Titan cases:  290-994-546

Description:
   The Remote Windows XP Administration Console would display the pop-up,
   COMM_FAILURE (IDL:omg.org/CORBA/COMM_FAILURE:1.0), when accessing media.
--------------------------------------------------------------------------------
Etrack Incident = ET1411776
Titan cases:  230-572-386

Description:
   The first fragment written by BPTM will not be position checked, allowing
   a rogue rewind to go undetected. If a rogue rewind occurred during the time
   between reading the empty header and writing the first backup header, the
   rewind could go undetected.
--------------------------------------------------------------------------------
Etrack Incident = ET1410874
Associated Primary Etrack = ET1402736
Titan cases:  320-130-796

Description:
   Unable to perform a multi-stream FlashBackup using an "old" method, such
   as not using Snapshot Client options.
--------------------------------------------------------------------------------
Etrack Incident = ET1412331

Description:
   With Snapshot destination in SLP, there was a difference in the value of
   the Storage unit in NetBackup-Java Administration Console and in the
   "nbstlutil list".
   
   A change was added so when a Snapshot destination is in SLP, the backup
   destination and duplication destination will pick up the actual STU.
--------------------------------------------------------------------------------
Etrack Incident = ET1408807

Description:
   A PIT Restore with an HPEVA_Snapclone FIM type would fail if there were
   two resources (for example, two storage stacks - HPEVA UDID, HPLVM, or
   VxFS FileSystem) in the backup selection.
--------------------------------------------------------------------------------
Etrack Incident = ET1412417

Description:
   A fix was made to address an nbrmms core dump issue that would occur
   because of a memory access violation in the VxFI code.
--------------------------------------------------------------------------------
Etrack Incident = ET1413338

Description:
   An inaccurate log message was being written when bpdbm failed to update a
   STREAMS file in image validation.
--------------------------------------------------------------------------------
Etrack Incident = ET1411302
Associated Primary Etrack = ET1269930
Titan cases:  220-289-048

Description:
   A change was made to resolve an nbstserv core dump issue that would occur
   while processing a large number of images.
--------------------------------------------------------------------------------
Etrack Incident = ET1413269
Associated Primary Etrack = ET1414241

Description:
   Jobs were not being scheduled for a newly added policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1410786

Description:
   Jobs for a policy with multi-streaming enabled and with a bad client name
   failed with status 200.
--------------------------------------------------------------------------------
Etrack Incident = ET1413572 ET1385085
Associated Primary Etrack = ET1381455 ET1288113
Titan cases:  230-534-351 281-379-673 220-289-644

Description:
   NBJM would cancel a duplication job (larger backups consistently fail
   with status 50) that was initiated using Storage Lifecylce Policies (SLP).
--------------------------------------------------------------------------------
Etrack Incident = ET1414212
Associated Primary Etrack = ET1222342
Titan cases:  220-208-577

Description:
   Running bpjobd -cleanup on a large number of jobs in conjunction with
   bpduplicate may result in a status 12 or status 50 error.  This would likely
   happen in a large environment where the nightly pruning of the jobs
   database could take in upwards of ten minutes.

Workaround:
   If you encounter this issue, perform more frequent recycling with fewer
   jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1412557

Description:
   Multiple jobs for the same policy, client, and schedule combination would
   erroneously run simultaneously, or nearly so.
--------------------------------------------------------------------------------
Etrack Incident = ET1415612
Associated Primary Etrack = ET1415270
Titan cases:  220-411-437 291026372

Description:
   A fix has been added to resolve an error that would occur when
   attempting to browse directories with apostrophes in the name. A similar
   fix was provided to resolve "Invalid Character" errors that would occur
   when selecting directories with an ampersand (&) character in the name.
--------------------------------------------------------------------------------
Etrack Incident = ET1413649
Associated Primary Etrack = ET1407104
Titan cases:  320-129-510

Description:
   Storage Lifecycle Policy (SLP) duplications would create one batch per
   image for a tape with multiple images.  
--------------------------------------------------------------------------------
Etrack Incident = ET1401482
Associated Primary Etrack = ET1416629
Titan cases:  240-839-682 281-439-493

Description:
   An old image was not being deleted for more space in lifecycle storage
   unit when the "staged capacity managed" retention type was selected. The
   job would fail with the error, "Disk storage unit is full" and a
   status 129.
--------------------------------------------------------------------------------
Etrack Incident = ET1413567

Description:
   Duplicate, restore, and verify from a NearStore FSE Storage Unit would
   fail with the following error.
     "Cannot read image from disk, Invalid argument"
--------------------------------------------------------------------------------
Etrack Incident = ET1415683

Description:
   A change was made to address an issue that caused NBPEM to stop scheduling
   jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1414541

Description:
   The restore functionality would fail with an HPLVM stack for Oracle
   Snapshot backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1416768

Description:
   bptm would core dump when a Nearstore restore failed due to slow network
   issues.
--------------------------------------------------------------------------------
Etrack Incident = ET1421025

Description:
   Jobs started to backup transaction logs for an SQL policy configured with
   instant recovery and off host backup would fail with a status 41.
--------------------------------------------------------------------------------
Etrack Incident = ET1425093

Description:
   During stress testing, the event manager service would occasionally go
   down and come back up. nbpem asserted:!m_getAllNamesCall
   PemPolicyCache.cpp 104 while stress testing nbevtmgr with repeated start,
   stop, and sending events.
--------------------------------------------------------------------------------
Etrack Incident = ET1424266
Associated Primary Etrack = ET1417414
Titan cases:  240-828-934

Description:
   Policies with schedules set to frequency of 52 weeks and multi-stream would
   fail with a status 196 with nbpem v5.
--------------------------------------------------------------------------------
Etrack Incident = ET1423453

Description:
   Suspended jobs for an inactive policy could not be resumed after a failover.
--------------------------------------------------------------------------------
Etrack Incident = ET1425900
Associated Primary Etrack = ET1416156
Titan cases:  220-406-370

**Description:
   If a VCB proxy backup of a virtual node joins an MPX group, all subsequent
   normal jobs in that MPX group would back up the proxy host.

Workaround:
   The following list contains workarounds for this issue:
     - Turn off multiplexing on the VCB backups.
     - Run the VCB backups on a different storage unit.
     - Use a different volume pool for the VCB backups.
   
   For additional information about this issue, refer to the following
   TechNote on the Symantec Support Web site.
   
   http://entsupport.symantec.com/docs/308906  
--------------------------------------------------------------------------------
Etrack Incident = ET1425285

Description:
   When a cluster failover was initiated while a duplication job was active,
   the bpdbm child processes that were active for the duplication job could
   take a long time to terminate.
--------------------------------------------------------------------------------
Etrack Incident = ET1428096
Associated Primary Etrack = ET1409844
Titan cases:  220-406-066

Description:
   A change was made to address an nbpem version 4 issue (originating in
   ET1322956), mixed calendar schedule types in policies, where the daily WCT
   evaluates to 23:59:59, resulting in a status 196 error.
--------------------------------------------------------------------------------
Etrack Incident = ET1423583

Description:
   Duplication jobs would fail with a status 50, but continue on to complete
   the duplication.
--------------------------------------------------------------------------------
Etrack Incident = ET1426958

Description:
   If a multi-streamed policy with multiple schedules is blocked by failure
   history, the child job that runs after the failure history is expired may
   fail with a status 196.  
--------------------------------------------------------------------------------
Etrack Incident = ET1427064

Description:
   Storage Lifecycle Policies processing was failing occasionally while
   processing images with a large number of fragments because the bpdbm
   connection was timing out.
--------------------------------------------------------------------------------
Etrack Incident = ET1429629

Description:
   If PEM restarted with a parent and child job in a WAITING_FOR_RETRY state,
   it would retry the child job only. After the child job completed, no more
   jobs were scheduled for this policy/client.
--------------------------------------------------------------------------------
Etrack Incident = ET1430825
Associated Primary Etrack = ET1373028
Titan cases:  311-971-198

Description:
   For duplicate multiple copies, all duplicate jobs would fail if any of
   the Disk Copies have a Dummy Allocation supplied when executing on
   Windows.
--------------------------------------------------------------------------------
Etrack Incident = ET1428794

Description:
   nbstserv would halt processing while waiting for an nbdelete call to
   complete.
--------------------------------------------------------------------------------
Etrack Incident = ET1431220

Description:
   A failed attempt to validate a copy during a duplication job was holding a
   write lock on the image file and causing other bpdbm child processes to
   hang until the duplication job finished.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1428632

Description:
   Changes were made to address two memory leak errors found in the VxFI
   code that lead to a SharedDisk backup failure.
--------------------------------------------------------------------------------
Etrack Incident = ET1432786
Associated Primary Etrack = ET1424199
Titan cases:  281-416-722

Description:
   A change has been made to address an issue that could cause file system
   corruption on a Disk. This issue would cause a media server to go into a
   panic state while mounting a corrupted file system. The fix ensures that
   the mount operation verifies the device mount state independent of the
   return code of the mount command.  
--------------------------------------------------------------------------------
Etrack Incident = ET1431217

Description:
   Bpduplicate would not allow a copy of a backup to be started if another
   duplication for the same backup was in progress.  Also, if more than one
   duplication to different destination copies from the same disk source copy
   occurs simultaneously, the duplications would either hang or error.

Workaround:
   To work around the simultaneous duplications from the same disk source
   copy hang or error issue, disable shared memory duplications.  Touch the
   following file on the master server:
   
   UNIX:
      /usr/openv/netbackup/NOSHMDUP
   
   Windows:
      <installed_path>\NetBackup\NOSHMDUP
--------------------------------------------------------------------------------
Etrack Incident = ET1431957
Associated Primary Etrack = ET1417636
Titan cases:  311-991-075

Description:
   EMM would crash because it was not handling a CNOS exception that was
   leaked through the Event Manager supplier-side library.
   
   The createConnectObjects() method makes calls directly to CNOS but in
   some cases it does not surround those calls in try/catch blocks. This
   caused CNOS exceptions to be leaked to the caller, in this case EMM. EMM
   catches specific exceptions; those not caught are pushed up the stack
   until it exits as an unhandled exception.
--------------------------------------------------------------------------------
Etrack Incident = ET1432152

Description:
   A change was made to address an Incremental backup data loss issue that
   would occur if bpbkar took more than 10 seconds to start.
--------------------------------------------------------------------------------
Etrack Incident = ET1432733

Description:
   A failed job waiting to be retried would prevent a job session from being
   closed. Therefore, the cold catalog backup to be run at the end of session
   was delayed until after all of the job-tries end and the job is done.
--------------------------------------------------------------------------------
Etrack Incident = ET1431905

Description:
   A change was made to address an issue that caused nbpem to be caught in an
   infinite loop, resulting in no jobs being able to start.
--------------------------------------------------------------------------------
Etrack Incident = ET1436492
Associated Primary Etrack = ET1368270
Titan cases:  240-779-778

Description:
   During a True Image Restore (TIR) data backup, if the socket used to get
   the data failed, the format of the tape could be written incorrectly.  
--------------------------------------------------------------------------------
Etrack Incident = ET1436738
Associated Primary Etrack = ET1400885
Titan cases:   291-058-781

Description:
   The requested Start Time calculation caused a full backup to be scheduled
   repeatedly if the last incremental backup occurred between windows and the
   frequency was a multiple of 24 hours. To fix this issue, pre-window
   checking was added so that if the last backup falls between windows, the
   due time can pick up the next window even if it is the same day.
--------------------------------------------------------------------------------
Etrack Incident = ET1439637

Description:
   A change has been added to address a core dump issue that would occur
   with nbdelete.
--------------------------------------------------------------------------------




========
NB_6.5.2
========

Etrack Incident = ET1072956
Associated Primary Etrack = ET1051977
Titan cases:  290-795-451

Description:
   During multiplexed and Inline Tape Copy (ITC) backups or duplications an
   error would occur during an end-of-media (EOM) event that resulted in a
   status code 229.
--------------------------------------------------------------------------------
Etrack Incident = ET1129738
Associated Primary Etrack = ET1125756
Titan cases:  320-063-046

Description:
   bprd would prematurely terminate during startup if bpdbm took longer to
   come up.  A change was made to the amount of time bprd will wait for
   a connection to bpdbm to be configurable.
--------------------------------------------------------------------------------
Etrack Incident = ET1146636
Associated Primary Etrack = ET1112853
Titan cases:  281-124-171

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

Description:
   Added SAN client 4gBit/s QLogic QLA/QLE 246x target mode FC HBA support for
   Fibre Transport (FT) media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1167180

Description:
   If NetBackup Access Control (NBAC) was activated on a Windows system,
   NetBackup Enterprise Media Manager (nbemm) would not shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET1163707 ET1214679

Description:
   In the Activity Monitor user interface, it is common for jobs to display
   as "queued".  However, it is not clear to a user as to why the job is
   in a waiting state.  In situations where a user may have hundreds of
   queued jobs, it would be beneficial to have a way to see what resources
   are in contention.
   
   The Job Display in the NetBackup Administration Console, Activity Monitor
   will include a new column that shows the reason why a job is queued and
   in a waiting state. In addition, some of the information that is displayed
   in the new column is available by using the job details.  
--------------------------------------------------------------------------------
Etrack Incident = ET1166535
Titan cases:  311-336-415

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

Description:
   This release contains a new feature that enables the user to choose which
   machines should 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 supports specification of preferred or required media
     servers for restore and duplication operations. This new capability
     replaces the FORCE_RESTORE_MEDIA_SERVER option.
--------------------------------------------------------------------------------
Etrack Incident = ET1166301

Description:
   Additional support has been added that enables AdvancedDisk disk pools to
   be configured for multiple StorageServers.
--------------------------------------------------------------------------------
Etrack Incident = ET1062687

Description:
   Catalog backups could fail if a pre-NetBackup 6.0 media server is selected
   for backup.

Workaround:
   To avoid this issue, make sure catalog backups are configured to go to
   storage units on NetBackup 6.0 (or later) media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1161381

Description:
   bpduplicate would report job success after an optimized-duplication failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1065511

Description:
   This release contains additional support of Flash Copy snapshot for an
   IBM array.
--------------------------------------------------------------------------------
Etrack Incident = ET1172272

Description:
   The vfm_master.conf file was added for Solaris x86 server installs.
--------------------------------------------------------------------------------
Etrack Incident = ET1128543

Description:
   A change was made to ensure that the VxFI code correctly uses tstr2str in
   the VxFI providers.
--------------------------------------------------------------------------------
Etrack Incident = ET1166793
Associated Primary Etrack = ET1164173
Titan cases:  220-135-395

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

Description:
   Changes have been added to address a scalability issue with update calls
   for disk volumes and storage units.
--------------------------------------------------------------------------------
Etrack Incident = ET1174568

Description:
   An API has been created that enables a server to determine the patch
   level of a remote host.
--------------------------------------------------------------------------------
Etrack Incident = ET1164151

Description:
   Unreadable date format strings were printing out when bpduplicate -help
   would print after the -s start date and -e end date commands.
--------------------------------------------------------------------------------
Etrack Incident = ET1172972
Associated Primary Etrack = ET1162893
Titan cases:  240-666-528

Description:
   The LIMIT_BANDWIDTH setting was not working on an HP-UX system running on
   an IA64 platform.
--------------------------------------------------------------------------------
Etrack Incident = ET1153448

Description:
   The nbdevconfig -setSharedDiskSPR 1 command would cause an error if a
   SharedDisk storage server did not exist prior to the command being run.
   A change has been made that allows the command to be run without creating
   a storage server before you run the command.
--------------------------------------------------------------------------------
Etrack Incident = ET1073129

Description:
   A change has been added that makes the DSM (un)mount request asynchronous.
--------------------------------------------------------------------------------
Etrack Incident = ET1058133 ET1241088
Titan cases:  240-588-298

Description:
   Changes were added that allow the SQL Anywhere database server to run with
   the -m option, where the transaction log is truncated when a checkpoint
   occurs. This option is set to the server.conf file. If the -m option is
   set, an incremental hot catalog backup will always be a full.
   
   In addition, options to nbdb_backup command were added to only backup the
   tlog and to truncate it as shown in the following example.  
     nbdb_backup -online dest [-tlog_only] [-truncate_tlog]
--------------------------------------------------------------------------------
Etrack Incident = ET1173808 ET1191396 ET1225254 ET1224352 ET1224326 ET1229771
ET1232968 ET1233220 ET1232369

Description:
   Changes have been added that improve the consistency and usability of the
   Job Priority Scheme.
--------------------------------------------------------------------------------
Etrack Incident = ET1162316
Associated Primary Etrack = ET1153592
Titan cases:  220-097-876 281-213-614

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

Description:
   bprecover would crash while attempting to recover a Bare Metal Restore (BMR)
   database file that exceeded 2GB in size.  
--------------------------------------------------------------------------------
Etrack Incident = ET1149230

Description:
   If an image has aged beyond its longest retention, Lifecycles continue to
   try to copy the image.  Lifecycles attempt to copy the image until the
   copy is complete or until a user cancels it by using nbstlutil.
   
   Changes have been made that change this behavior so that the "persistent
   duplication" of an image will stop attempting to complete the copy once
   the image has reached the age of the longest specified fixed retention.
--------------------------------------------------------------------------------
Etrack Incident = ET1178482
Associated Primary Etrack = ET1175871
Titan cases:  290-898-929

Description:
   A change has been added that ensures a user does not receive full
   NetBackup Administration (root user) privileges via the NetBackup Java
   Administration Console after logging in as a normal user.
--------------------------------------------------------------------------------
Etrack Incident = ET1178234 ET1178268

Description:
   A change was made to NBEMM that resolved an issue that caused a core dump
   to occur after the patch was applied and the services were recycled.
--------------------------------------------------------------------------------
Etrack Incident = ET1173798

Description:
   The NetBackup Resource Broker (nbrb) could generate a core file.  

Workaround:
   If you encounter this issue, make sure nbemm is running, then restart nbrb.
--------------------------------------------------------------------------------
Etrack Incident = ET1175290

Description:
   A NetBackup server was unable to connect to a NOM server after generating
   some media and then restarting the nbemm service.
--------------------------------------------------------------------------------
Etrack Incident = ET1180414

Description:
   The ACE Timer did not work with embedded fields (as it does under 7.0).
--------------------------------------------------------------------------------
Etrack Incident = ET1141941
Associated Primary Etrack = ET1046705
Titan cases:  240576707

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

Additional Notes:
   A large warning would appear when no files were recovered because no files
   met the criteria.
--------------------------------------------------------------------------------
Etrack Incident = ET1087412

Description:
   When a cancel or suspend was initiated, Job Manager's parent job was not
   executing clean-up steps to delete the snapshot or run the parent end notify
   script.
--------------------------------------------------------------------------------
Etrack Incident = ET1172948

Description:
   A change was made to increase the cleaning time for TL4 libraries to five
   minutes for all brands.
--------------------------------------------------------------------------------
Etrack Incident = ET1175391

Description:
   Changes were added to correct AUTO_UPDATE_ROBOT issues on TL8 libraries.
--------------------------------------------------------------------------------
Etrack Incident = ET1140138
Titan cases:  280-882-431

Description:
   The catalog has a query that compares a backup to the previous backup and
   lists the files that were deleted between the two backups.  This is used
   for certain backups on NearStore devices.  The query had two issues:
   
   1.  The images being queried were not locked, so if one of the images was
   expired by a different process prior to opening up the .f file, the query
   was failing in an unusual way (attempting to open the IMAGE_FILES file).
   
   2.  The query was not checking if the .f file had been successfully opened.
--------------------------------------------------------------------------------
Etrack Incident = ET1158501

Description:
   An unreadable value would display in the Job ID, Job type, and status
   fields.
--------------------------------------------------------------------------------
Etrack Incident = ET1078362

Description:
   The NetBackup Service Layer (NBSL) would crash when the nbsl.xml file was
   not created.  In addition, the NBSL logging would not occur under such
   circumstances.
--------------------------------------------------------------------------------
Etrack Incident = ET1177686

Description:
   A change was added that increases the maximum cap and maximum drives per
   panel for ACS in support of the new Sun SL3000 robot.
--------------------------------------------------------------------------------
Etrack Incident = ET1156305
Associated Primary Etrack = ET1181987

Description:
   Canceling one child stream of a multi-stream Exchange backup would cause
   all peer Exchange stream backups to be canceled. This behavior occurred for
   all compound jobs, such as, parent and multiple-child jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1113521

Description:
   A change was made to provide information about the (un)mount status for
   SharedDisk disk volumes.
--------------------------------------------------------------------------------
Etrack Incident = ET1173803

Description:
   Changes were made to address a vmadm error that would occur in the
   DiskPool list operation.
--------------------------------------------------------------------------------
Etrack Incident = ET1089294
Titan cases:  290-807-298

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

Workaround:
   If you were to encounter this issue, you can use the bpimage -deletecopy
   command to remove the copies manually.
--------------------------------------------------------------------------------
Etrack Incident = ET1182125

Description:
   Enhancements were made to add Snapshot support in a Lifecycle policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1132745

Description:
   When user performed an Inventory Disk Pools > Start Inventory operation on
   Disk Pools, it would not update the old value.
--------------------------------------------------------------------------------
Etrack Incident = ET1124825
Associated Primary Etrack = ET1120934
Titan cases:  230-424-265

Description:
   The NetBackup-Java Administration Console would incorrectly report the
   license-key expiration.
--------------------------------------------------------------------------------
Etrack Incident = ET1170793

Description:
   A Point-in-Time (PIT) restore would fail when configured with two mirrors.
--------------------------------------------------------------------------------
Etrack Incident = ET1153528

Description:
   Due to incorrect memory management, some memory would get released while
   it was still in use, resulting in a potential memory corruption. This
   issue would occur during that shutdown sequence in STSSvc.
--------------------------------------------------------------------------------
Etrack Incident = ET1175038

Description:
   A change was made to address a possible deadlock issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1183650
Associated Primary Etrack = ET1037368
Titan cases:  220-096-910 220-123-945 220-124-001 220-135-401 220-141-599
281-218-316 290-883-680

Description:
   NOM provides reports for jobs that do not run but are due to run. The
   NetBackup Service Layer (NBSL) provides the required job data to NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET1065835

Description:
   The Resource Event Manager creates unnecessary errors while attempting to
   get information for pre-NetBackup 6.5 Storage Units. The Disk Service
   Manager directs the Resource Event Manager to not pursue information for
   back-level storage units using normal methods in NetBackup 6.5.
--------------------------------------------------------------------------------
Etrack Incident = ET1065761

Description:
   Allow new versions of OpenStorage plug-ins to re-register themselves with
   EMM/Disk Service Manager (DSM).  In addition, allow DSM to rescan the
   plug-in and determine what its capabilities are and store the new ones in
   the database.
--------------------------------------------------------------------------------
Etrack Incident = ET1159570 ET1197410

Description:
   Changes have been made to fix library signal handling so that a preexisting
   handler cannot be overwritten. In addition, a new function,
   common_signal_revert has been added.  This function intelligently sets the
   handler back if it was changed.
--------------------------------------------------------------------------------
Etrack Incident = ET1167158

Description:
   A change was made to ensure that the user does not see the wrong storage
   server (or multiple storage servers) deleted when they were to run the
   nbdevconfig -deletests command.
--------------------------------------------------------------------------------
Etrack Incident = ET1134749

Description:
   An insuffucient error message would appear when attempting to delete a
   DiskPool with active StorageUnit association.
--------------------------------------------------------------------------------
Etrack Incident = ET1183710

Description:
   A new version of the Veritas Unified Logging (VxUL) has been included with
   this Release.
--------------------------------------------------------------------------------
Etrack Incident = ET1182952

Description:
   NBJM would hang while jobs were being canceled and the BPBRM processes were
   being killed during a manual test.
--------------------------------------------------------------------------------
Etrack Incident = ET1145121

Description:
   A confusing error message would appear for a busy disk group.
--------------------------------------------------------------------------------
Etrack Incident = ET1072786

Description:
   Local VxUL logs were not displaying correctly in NOM. The logs contained
   an unreadable hex number for each log line instead of a log message.
--------------------------------------------------------------------------------
Etrack Incident = ET1169863 ET1182021

Description:
   Changes were added in this release to address potential security issues.
--------------------------------------------------------------------------------
Etrack Incident = ET1176346

Description:
   Added support for the production of additional copies of synthetic backups
   using the synthetic read and write process.
   
   This new feature is called Second Copy Synthetics, and it enables a user to
   produce more than one copy of a synthetic backup and utilize image copies
   other than the primary as the source of image data for the synthetic backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1151267

Description:
   The NBSL would create multiple sessions with EMM. A change has been made
   that prevents multiple sessions from being created. Only one EMM session
   will be created.
--------------------------------------------------------------------------------
Etrack Incident = ET1182008
Associated Primary Etrack = ET1167923
Titan cases:  230-482-665 240655547 311-873-262

Description:
   A issue exists that could cause a "Numerical result out of range" error to
   occur during a long backup.

Workaround:
   If you encounter this error,turn TIR off and reduce the size of the jobs
   into smaller jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1103640
Associated Primary Etrack = ET1103581
Titan cases:  240-620-126

Description:
   bpbackupdb returns a status code 50 when it is issued from the command line
   interface (CLI) and when VxSS is enabled. The administration log reports a
   success, Status 0, when initiated from pbadm or the NetBackup-Java
   Administration Console.  

Workaround:
   If you encounter this issue, use the NetBackup-Java Administration Console.
--------------------------------------------------------------------------------
Etrack Incident = ET1167175
Associated Primary Etrack = ET1165582
Titan cases:  240-665-067 281-261-075 290-875-726

Description:
   A Zeta file system (ZFS) filesystem is not backed up when the
   ALL_LOCAL_DRIVES directive is used.

Workaround:
   To resolve this issue, manually add the drive to the include list.
--------------------------------------------------------------------------------
Etrack Incident = ET1159796
Associated Primary Etrack = ET1159696
Titan cases:  220-129-851

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

Workaround:
   To resolve this issue, perform the following:
   
   1. Run ./nbac_cron -Add[At|Cron]
         Username: <user>
         Password: <pass>
         Password: <pass>
         Access Control Group: <group>
   
   2. Register account locally as root [Y/N]?: N  <-- !!!!
   
   3. Replace ./nbac_cron -Setup[At|Cron] with:
        export VXSS_CREDENTIAL_PATH=~/.vxss/credential.crat
        bpnbat -login
        Broker: <broker>
        Port: <enter, probably>
        Authentication Type: vx
        Authentication Domain: CronAt_<user> <-- same <user> as above
        Name: CronAt_<user> <-- same <user> as above
        Password: <pass> <-- same <pass as above Operation completed
          successfully
   
   4. Once this is finsihed, set the env var VXSS_CREDENTIAL_PATH as above
      for the vbr agent.
--------------------------------------------------------------------------------
Etrack Incident = ET1060575 ET1214253 ET1216815 ET1216692 ET1217125 ET1217868
ET1215768 ET1216893 ET1217051 ET1213165 ET1219082 ET1212454 ET1219020 ET1230246
ET1230243
Titan cases:  240-576-203 240-588-298

Description:
   An enhancement has been made to provide a Database Administrator Tool for
   the NetBackup relational databases.  This new tool is designed to make it
   easier for users to perform database administration tasks on NetBackup
   databases.
--------------------------------------------------------------------------------
Etrack Incident = ET1185176
Associated Primary Etrack = ET1183187
Titan cases:  311-786-349

Description:
   Using the -L option with the bpduplicate, bpimport, and bpverify commands
   would cause a failure and core dump on HP-UX IA64 system.

Workaround:
   To avoid this issue, do not use the -L option.
--------------------------------------------------------------------------------
Etrack Incident = ET1146898

Description:
   An enhancement has been added to this release that enables VBR to gain
   access to the size and physical size variable data for Open Storage. This
   enables VBR to more accurately report on Open Storage plug-ins that do
   de-duplication.
--------------------------------------------------------------------------------
Etrack Incident = ET1056443
Associated Primary Etrack = ET1039776
Titan cases:  280-885-521 290-938-579

Description:
   If the bp.conf SERVER entry was changed from a short name to a fully
   qualified domain name (FQDN) or vice versa, and a hot catalog backup with
   vault was performed, the Vault job would fail with a status 294, even
   though the catalog backup was successful.
   
   Now, instead of using gethostname() results when Vault performs a
   validation, the client name (as configured in the policy) is used.  

Workaround:
   If you encounter this issue (on UNIX systems only), create a symbolic link
   between the FQDN and the short names in the imageDB directory.  
--------------------------------------------------------------------------------
Etrack Incident = ET1152640
Associated Primary Etrack = ET1144027
Titan cases:  220-109-428

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

Description:
   The NetBackup Release Broker (NBRB) would crash if it could not connect or
   communicate with EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET1186087

Description:
   Changes were added in this release to improve product stability by fixing
   NULL references in the NetBackup Service Layer (NBSL).
--------------------------------------------------------------------------------
Etrack Incident = ET1188492

Description:
   Changes have been added to this release to enhance the job-priority
   capabilities within NetBackup.  New default values have been added for each
   job type, a user can set the priority from the command line interface, and
   a user can now dynamically change the job priority from the NetBackup
   Administration Consoles (including Java, Windows, and NOM).
--------------------------------------------------------------------------------
Etrack Incident = ET1188093
Associated Primary Etrack = ET925827
Titan cases:  280-912-721

Description:
   Catalog compression routines were attempting to compress images which had
   been archived.  This resulted in unnecessary entries in the NetBackup Error
   report.
--------------------------------------------------------------------------------
Etrack Incident = ET1189537

Description:
   This release contains NBSL changes to support Storage life cycle policies
   for Snapshots.  More specifically, the converter has been modified to
   incorporate the following two new constants:
     1)SS_USE4_SNAPSHOT->NBSS_USE4_SNAPSHOT
     2)SS_USE4_MAX->NBSS_USE4_MAX
--------------------------------------------------------------------------------
Etrack Incident = ET1143916

Description:
   NOM would not start or stop services on media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1189076

Description:
   A problem existed that allowed the HSManager list to contain the same entry
   multiple times.
--------------------------------------------------------------------------------
Etrack Incident = ET1189094

Description:
   Changes were made to address NBSL core dump issues after creating a tape
   STU.
--------------------------------------------------------------------------------
Etrack Incident = ET1081659 ET1099902 ET1183054 ET1173791 ET1183182 ET1193043
ET1081659 ET1143425 ET1183211 ET1155436 ET1200208 ET1158077 ET1197526 ET1129982
ET1156265 ET1151156 ET1201126 ET1204321 ET1211954 ET1214165 ET1220078 ET1220695
ET1219827 ET1221698 ET1221686 ET1222264
Associated Primary Etrack = ET1147612
Titan cases:  320-071-197

Description:
   The NetBackup Policy Execution Manager (PEM) has been refactored to improve
   stability, scalability, and extensibility.
--------------------------------------------------------------------------------
Etrack Incident = ET1189901
Associated Primary Etrack = ET1178444
Titan cases:  240-689-644

Description:
   The NetBackup Resource Broker (RB) may not respect the MUST_USE_LOCAL_DRIVE
   and DONT_USE_SLAVE setting when joining a job to an existing multiplexed
   (MPX) group.
--------------------------------------------------------------------------------
Etrack Incident = ET1139682
Associated Primary Etrack = ET1129815
Titan cases:  311-694-272

Description:
   A raw partition restore failed on HP-UX.  In addition, the restored
   partition was corrupted.

Additional Notes:
   Depending on where the corruption occurred the partition might not be
   mountable.
--------------------------------------------------------------------------------
Etrack Incident = ET1190785

Description:
   The release of NetBackup contains a new feature that allows Fibre Transport
   jobs to write to tape storage units.
--------------------------------------------------------------------------------
Etrack Incident = ET1154385

Description:
   Formatting Logical Unit Numbers (LUNs) of an HP EVA disk array with
   UFS or VXFS caused an error to occur on Solaris 10 with an Emulex card.
   
   In the above configuration, the HP-EVA targets were shown as array-ctrl
   and did not get scan, which caused the device discovery to fail for
   HP-EVA LUNS.
--------------------------------------------------------------------------------
Etrack Incident = ET1157874
Associated Primary Etrack = ET1154612
Titan cases:  311-639-750

Description:
   Small spare files on HP-UX were not being restored properly.
--------------------------------------------------------------------------------
Etrack Incident = ET1190511

Description:
   The NetBackup Job Manager failed to cancel a job because it determined that
   bpbrm had not started yet. A change was made to the Job Manager to set the
   state to indicate bpbrm had been started.  Thus, if a cancel is processed,
   it then sends a signal to bpbrm allowing the cancel to work properly.
--------------------------------------------------------------------------------
Etrack Incident = ET1187864

Description:
   The stream discovery was not honoring the preprocess interval.  A change
   was made to the stream discovery to honor the preprocess interval on a
   per-policy basis by creating a separate stream file for each policy. In
   addition, the -streams option was removed from the bpcoverage command to
   allow the duplicate stream discovery code to be purged.
--------------------------------------------------------------------------------
Etrack Incident = ET1190656

Description:
   A change was made to disable the use of multiple StorageServers for the
   AdvancedDisk option on Windows media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1157433

Description:
   The NetBackup Job Manager (nbjm) would pass an unintended keyword phrase,
   "-P" for a Synthetic backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1101618

Description:
   Changes were added to address performance issues with Policy Manager
   collector. The initial loading of policies were timing-out in NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET1189511

Description:
   A change was made to the NetBackup Service Layer (NBSL) that ensures a
   RequestID is sent instead of a Request GUID in PendingRequestInfo.
--------------------------------------------------------------------------------
Etrack Incident = ET1176221
Associated Primary Etrack = ET1157114
Titan cases:  290-652-172

Description:
   A change has been made to address an issue that caused a core dump in NBJM.
--------------------------------------------------------------------------------
Etrack Incident = ET1180939

Description:
   The new Preserve multiplexing option is available to preserve
   multiplexing for tape-to-tape duplication within a storage lifecycle.
   This option option works best in environments where duplicating backups
   to lifecycle destinations serves to vault backups and where the
   possibility of a restore from a multiplexed backup is small.
   
   For more information about this new feature, refer to the following
   TechNote on the Symantec Support Web site.
   
     http://entsupport.symantec.com/docs/302438
--------------------------------------------------------------------------------
Etrack Incident = ET1186550
Associated Primary Etrack = ET1166359
Titan cases:  290-887-145

Description:
   The detailed status of successful restore from a Basic Disk showed a
   Warning status 800, "Fibre Transport resources are not available".
--------------------------------------------------------------------------------
Etrack Incident = ET1124933
Associated Primary Etrack = ET1120656
Titan cases:  290-821-914 311-887-438

Description:
   A PureDisk export policy would fail with a status 227 because a wrong image
   path was being used to try and write to the file.
--------------------------------------------------------------------------------
Etrack Incident = ET1168735

Description:
   A change has been made to ensure that NOM sends complete error logs.
--------------------------------------------------------------------------------
Etrack Incident = ET1192856

Description:
   Changes have been added to address memory leak issues in NBSL.
--------------------------------------------------------------------------------
Etrack Incident = ET1176263
Associated Primary Etrack = ET1160602
Titan cases:  290-869-698

Description:
   The bpplcatdrinfo command ignores the -Modify and -Set options when
   changing the setting on a remote master server from a local master server.

Workaround:
   To resolve this issue, you can temporarily change the default master server
   to be one of those specified with the -M option.  Or you can create a dummy
   catalog policy on the default master server so that when bpplcatdrinfo
   checks whether the name is valid, it finds something.

Additional Notes:
   The command checks whether the given policy name is for a catalog-backup
   policy, but it does so on the default master server instead of on the
   servers specified with the -M option.
--------------------------------------------------------------------------------
Etrack Incident = ET1194916

Description:
   If a user configuration has one symetrix array and another array attached
   to the local array in a DR setup, then in such a configuration the user
   would not be able to list the devices for creating a DiskPool. Because this
   listing would fail, the user would not be able to create a DiskPool for
   any symetrix array.
--------------------------------------------------------------------------------
Etrack Incident = ET1090933

Description:
   An issue existed that could cause the nbproxy for jobs to wait indefinitely
   if NOM had issues.
--------------------------------------------------------------------------------
Etrack Incident = ET1193420 ET1164441

Description:
   Users were unable to create a Standard and DB2 policy with the option
   "Perform Snapshot backup" enabled. bpjava was rejecting the bpplinfo
   command because it contained a ";" character in the command to be
   executed by the shell.

Workaround:
   If you encounter this issue, do not use a ";" character in the
   -snapshot_method_args argument.
--------------------------------------------------------------------------------
Etrack Incident = ET1167178
Associated Primary Etrack = ET1160557
Titan cases:  220-126-112

Description:
   Changes were made to address some allocation and unload issues that were
   occurring.
--------------------------------------------------------------------------------
Etrack Incident = ET1051426 ET1199018

Description:
   The policy command line interface (CLI) did not have a mechanism to
   prevent one operator from overwriting policy updates made by another
   operator.  This patch displays the current "generation" for the policy in
   the output from bppllist command.  Policy commands such as bpplinfo and
   bpplinclude now have a "-generation" option.  If the generation is
   supplied, the catalog will verify that it matches the current generation
   for the policy and fail the request if it does not.
--------------------------------------------------------------------------------
Etrack Incident = ET1134820

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

Description:
   A change was made to address a Resource allocation management problem that
   would occur after an (un)mount failure for SharedDisk occurred.
--------------------------------------------------------------------------------
Etrack Incident = ET1159723
Associated Primary Etrack = ET1086130
Titan cases:  290-821-682

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

Description:
   The parent job's estimated size and file count are always zero and need to
   be set for the correct volume to be selected by resource broker.  A change
   to the Policy Execution Manager was made to set the parent's estimated size
   to the largest value of all of its children.
--------------------------------------------------------------------------------
Etrack Incident = ET1117080

Description:
   If for a netapp filer, both credentials (such as, fas3020c1 and
   fas3020c1.vxind.veritas.com) are added, only one of them is added to the
   connection list, because the filer serial number is same for both.
   
   Now suppose that the fas3020c1 credential was the one that was added. If a
   user tried to find a connection object for fas3020c1.vxdind.veritas.com,
   the connection fails even though proper credentials were supplied.

Workaround:
   To avoid this issue, remove the duplicate entries from the credential list
   and then give the FQDN of the filer.  
--------------------------------------------------------------------------------
Etrack Incident = ET1124031

Description:
   Snapshot backups fail during a device import for non-Sun-branded HBA drivers
   due to lun number caching.

Workaround:
   To work around this issue, populate sd.conf with 256 entries. Once the limit
   has been reached the caching logic defaults to array for assigning  a lun.
   One side effect to this work around is that a large sd.conf will increase
   the device rescanning time.
--------------------------------------------------------------------------------
Etrack Incident = ET1132295

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

Description:
   With the Language Pack installed, the nbshareddisk release command would
   not capture the user-defined identifier's (UDID). The following error
   message appears in Japaneses and the UDID for each LUN is not captured.
   
     "List of the UDID that can't access to the host"
   
   If Language Pack is not installed or used, it correctly displays the
   following message and captures UDID for each LUN.
     "Released reservation on device"
--------------------------------------------------------------------------------
Etrack Incident = ET1195919

Description:
   Changes were made to add more exception handling.  
--------------------------------------------------------------------------------
Etrack Incident = ET1107364
Associated Primary Etrack = ET1105708
Titan cases:  281-158-304

Description:
   The Resource Broker would not honor an "Allow multiple retentions per
   media" setting while joining a new job to an existing Multiplex group.
--------------------------------------------------------------------------------
Etrack Incident = ET1182274

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

Description:
   Changes have been added to ensure that nbemm does not crash while running
   the "Device Configuration Wizard".
--------------------------------------------------------------------------------
Etrack Incident = ET1163525
Associated Primary Etrack = ET1161321

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

Additional Notes:
   This increases the size of an overall backup and restore operation.
--------------------------------------------------------------------------------
Etrack Incident = ET1199959

Description:
   Changes have been added to address the following issues:
   
   1) The return status of bpcr_read_dir_rqst was checked and it was
      determined that the bpcr_read_dir_rqst() call returns positive
      values. A change was made to correct this call.
   
   2) The bpcr_get_process_list_rqst call returns either a 0 or a positive
      error number while checking was only occurring for a negative number.
      This may have caused a memory leak.
   
   3) Input validation should be tighter in Volume* files.  
--------------------------------------------------------------------------------
Etrack Incident = ET1195138

Description:
   Changes have been made to address NBSL core dumps on the master server.  
--------------------------------------------------------------------------------
Etrack Incident = ET1201579

Description:
   A change has been added to address a potential crash issue with NBSL.
--------------------------------------------------------------------------------
Etrack Incident = ET1200944
Associated Primary Etrack = ET999515
Titan cases:  281-010-333

Description:
   Backups that have True Image Restore (TIR) fragments that span media would
   fail because of an issue found in the media reservation calculation. This
   issue caused bpduplicate jobs to fail with an status 96 error similar to
   the following.
   
     00:00:00 INF - Cannot obtain resources for this job : error [96]
--------------------------------------------------------------------------------
Etrack Incident = ET1187778

Description:
   A possible security weakness in the Windows user interface schedule
   component that could have led to a crash or potential unauthorized access
   has been resolved.
--------------------------------------------------------------------------------
Etrack Incident = ET1193100 ET1225573
Associated Primary Etrack = ET1179480
Titan cases:  240-682-949

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

Workaround:
   After adding the drive path, use the following command to "UP" the drive
   path.
   
     tpconfig -update -drpath -drstatus up
--------------------------------------------------------------------------------
Etrack Incident = ET1202995

Description:
   A catalog message would not show the replacement string for messages that
   were logged by array.
--------------------------------------------------------------------------------
Etrack Incident = ET1194501

Description:
   Added Device Mappings for new hardware updates.
--------------------------------------------------------------------------------
Etrack Incident = ET1181027
Associated Primary Etrack = ET1162500
Titan cases:  220-131-929

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

Additional Notes:
   Like -preview, the -preview_range option is not documented.
--------------------------------------------------------------------------------
Etrack Incident = ET1067020
Associated Primary Etrack = ET1062088
Titan cases:  320-049-434

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

Workaround:
   To avoid this issue, manually remove all damaged image files before
   attempting a recovery.
--------------------------------------------------------------------------------
Etrack Incident = ET1152607
Associated Primary Etrack = ET1136267
Titan cases:  320-064-173

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

Description:
   Modifications were made to the bpdm volume cleanup process, which deletes
   images from disk, to return the proper error code after a failure occurs.
--------------------------------------------------------------------------------
Etrack Incident = ET1203224

Description:
   When a suspended job was canceled, the NetBackup Job Manager (NBJM) would
   not notify the Policy Execution Manager (PEM).
--------------------------------------------------------------------------------
Etrack Incident = ET1108377

Description:
   Changes have been made to ensure media deassignment will not proceed if
   fragment records still exist on the media. If fragments do not exist, then
   deassignment will proceed normally.
--------------------------------------------------------------------------------
Etrack Incident = ET1187942 ET1234158
Titan cases:  320-081-486

Description:
   The create_nbdb command will display the actions that it will be performing
   when deleting and creating a new NBDB database, and, get confirmation
   from the user before continuing.
--------------------------------------------------------------------------------
Etrack Incident = ET1203477

Description:
   The client name in required resources was not using the client name from
   the policy.  In addition, the ShareGroup and pool fields were being set
   correctly and was changed to follow the order of precedence which is
   schedule, policy, and default value, respectively.
--------------------------------------------------------------------------------
Etrack Incident = ET1200903
Associated Primary Etrack = ET1194575
Titan cases:  320-074-249

Description:
   A change was added to correct an issue that occurred during an ACS multiple
   eject that caused Vault to loop while waiting for an eject status.
--------------------------------------------------------------------------------
Etrack Incident = ET1200907
Associated Primary Etrack = ET1114189
Titan cases:  220-091-399

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

Description:
   A change has been made to address a bpdbm crash issue that would occur
   when it was passed invalid start and end dates. It is recommended practice
   that the start date precede the end date.
--------------------------------------------------------------------------------
Etrack Incident = ET1205079

Description:
   Canceled SharedDisk jobs would not always release the disk volume.
--------------------------------------------------------------------------------
Etrack Incident = ET1202336

Description:
   A change was made to improve performance for NBSL.
--------------------------------------------------------------------------------
Etrack Incident = ET1202335

Description:
   Multiple changes have been added to improve stability in the NBSL.  
--------------------------------------------------------------------------------
Etrack Incident = ET1206062

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

Description:
   A change was made to address an NBConsole crash issue that would occur in
   the Activity Monitor or when switching servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1187198 ET1206945

Description:
   During the SharePoint SSP SQL database restore sequence, the services,
   administration site, and search databases are left loading with or without
   the commit flag being set.
--------------------------------------------------------------------------------
Etrack Incident = ET1203349

Description:
   A FAIL_MODE configuration for a multiple copy synthetic backup would
   default to a value of ALL. The default mode was not being set correctly for
   both the default case (not set in configuration file) or when it was set in
   the configuration file.
--------------------------------------------------------------------------------
Etrack Incident = ET1158733

Description:
   Backups to storage units that exceed the high water mark would fail with
   a status code 129 (disk full). In addition, Activity Monitor would not
   indicate that reason may be due to the high water mark being exceeded.
--------------------------------------------------------------------------------
Etrack Incident = ET1203235

Description:
   A change was added to detect a failed stream discovery job if the file list
   is empty.  If, in this situation, the file list is empty, a status 112 will
   occur, thus enabling the user to detect the problem.
--------------------------------------------------------------------------------
Etrack Incident = ET1190471

Description:
   bpmedialist would fail to use the EMM database for mlist functions.
--------------------------------------------------------------------------------
Etrack Incident = ET1207061
Associated Primary Etrack = ET1102562
Titan cases:  220-102-040

Description:
   A change was made that ensures NOM will show accurate job data of inline
   tape jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1205296

Description:
   Changes to the attributes in the Host Properties > Master Server >
   Properties > SharedDisk window were not displaying correctly in the
   user interface.  
--------------------------------------------------------------------------------
Etrack Incident = ET1207047
Associated Primary Etrack = ET1182905
Titan cases:  320-055-726

Description:
   An issue existed where users were unable to cancel certain jobs and the
   active job would exit with a status -1. A change has been made to address
   this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1204443

Description:
   If all the FAT pipes are unavailable or unallocated, then a job must fail.
   Media and Device Selection (MDS) should not queue on those FT resources.
--------------------------------------------------------------------------------
Etrack Incident = ET1196910
Associated Primary Etrack = ET1196861
Titan cases:  240-760-340 290-907-979 320-094-359

Description:
   Bare Metal Boot Server install is fixed for linux2.6 platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET1197310

Description:
   The nbdbms_start_server -stat command would parse and use an incorrect
   value for the port.
--------------------------------------------------------------------------------
Etrack Incident = ET1077508

Description:
   NBJM has been changed to shutdown gracefully instead of exiting.
--------------------------------------------------------------------------------
Etrack Incident = ET1209325

Description:
   If multiple duplications are run simultaneously using the same source image
   (with different copy numbers), one of the duplications will fail.

Workaround:
   To avoid this issue, do not run multiple duplications simultaneously using
   the same source image, too close together.  You may need to create a script
   to do this.
--------------------------------------------------------------------------------
Etrack Incident = ET1193064

Description:
   NBFSD would not support files larger than 3GB. In addition, some issues
   might occur if any files within an image were larger than 4GB.
--------------------------------------------------------------------------------
Etrack Incident = ET1164771

Description:
   A request would not be properly retried if an error occurred while getting
   the device list.
--------------------------------------------------------------------------------
Etrack Incident = ET1033253 ET1169737

Description:
   A change has been made to reclassify the Veritas Unified Logging (VxUL)
   Log messages, per new developer guidelines.
--------------------------------------------------------------------------------
Etrack Incident = ET1209400 ET1214062 ET1212619 ET1217901 ET1217907 ET1216959
ET1219557 ET1219635 ET1219526 ET1219430 ET1219437 ET1220562 ET1222057 ET1224127
ET1225893 ET1225770 ET1225833 ET1221466 ET1229628 ET1229008 ET1230396 ET1220532
ET1230961 ET1229752 ET1228886 ET1232418

Description:
   The addition of an Encryption Key Management Service (KMS) has been added
   to NetBackup in this release.
--------------------------------------------------------------------------------
Etrack Incident = ET1089306

Description:
   The nbpushdata -remove option now completely removes disk storage unit
   related information from the EMM database.
--------------------------------------------------------------------------------
Etrack Incident = ET1210332

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

Workaround:
   To avoid this issue, label the media using bplabel before you use it in a
   standalone drive.
--------------------------------------------------------------------------------
Etrack Incident = ET1133195
Associated Primary Etrack = ET1032373
Titan cases:  240-540-817

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

Workaround:
   After running bpstuadd, manually modify the server list to remove the
   SERVER entry.
--------------------------------------------------------------------------------
Etrack Incident = ET1193951

Description:
   Policy Execution Manager failed to start scheduled jobs on Tru64 ALPHA
   platforms because a timer was not initiated due to ACE_Time_Value::max_time
   being zero.

Workaround:
   If you should encounter this error, use NB_INFINITY.
--------------------------------------------------------------------------------
Etrack Incident = ET1117658

Description:
   A change has been made to correct an issue with inline tape copy (ITC) to
   BasicDisk duplications that span BasicDisk type storage units (STUs).  
--------------------------------------------------------------------------------
Etrack Incident = ET1207651

Description:
   The NetBackup Job Manager would fail to delete the snapshot for WOFB backup
   jobs when streaming was disabled.  A change was made in the Job Manager to
   save the snapshot ID so that when the Policy Execution Manager initiates a
   snapshot cleanup, the Job Manager can find the snapshot ID in the PARAMS
   file.
--------------------------------------------------------------------------------
Etrack Incident = ET1152497

Description:
   A problem was found that caused the NOM server thread count to increase to
   a high number.  This increased thread count rendered the NOM user interface
   non-accessible.  A change was made to endure that the NOM login does not
   take more than two or three minutes, even if the server has a sizable load.
--------------------------------------------------------------------------------
Etrack Incident = ET1206423
Titan cases:  220-184-367

Description:
   Some of the EMC CLARiiON LUNs were not enumerated as part of nbshareddisk
   list output.
   
   Some of the LUNs of the array were considered, "hot spare" and cause the
   parsing for this to fail in such a way that subsequent LUN information was
   ignored.  Because of this, some of the valid LUNS were not enumerated.
--------------------------------------------------------------------------------
Etrack Incident = ET1193738
Associated Primary Etrack = ET1187817
Titan cases:  281-276-313 290-860-580

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

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

Description:
   Deleting a server that was the last write host of an allocated media would
   fail even if there were other valid servers in the media group that could
   still use the media.

Workaround:
   Manually move the media to another server in the media group before deleting
   the server.
--------------------------------------------------------------------------------
Etrack Incident = ET1177472

Description:
   IBM DS credentials would appear in log file whenever an IBM provider would
   produce an exception while executing various commands. A change was made to
   suppress the password in the exception.
--------------------------------------------------------------------------------
Etrack Incident = ET1213670

Description:
   In case there are more than one device in a single call to import,
   NetBackup would provide some intelligence by storing the host connection
   information within the storage unit.
   
   In most instances, the hostConnection name on the array was given as,
   "exampleHost" while the actual hostname was exampleHost.subnet.domain.com.
   This caused the comparison to fail with no host name left for the mapping
   or unmasking operation on the array.
--------------------------------------------------------------------------------
Etrack Incident = ET1146542

Description:
   Changes were added in this release to allow an import of a media from a
   scratch pool.
--------------------------------------------------------------------------------
Etrack Incident = ET1047988

Description:
   The error message returned by bpmedia attempting to do an operation on a
   media not assigned to that server is misleading.

Workaround:
   A more descriptive error code and message is found in the logs for bpmedia
   and nbemm.
--------------------------------------------------------------------------------
Etrack Incident = ET1214101
Associated Primary Etrack = ET1159481
Titan cases:  311-718-110 281-277-146

Description:
   The following sequence of events would cause the catalog recovery to
   complete with a status 0, however you would be unable to freeze the used
   media in the catalog recovery.
     1. Run a full online catalog backup.
     2. Remove the NetBackup package and then reinstalled a new package.
     3. Setup a storage unit and run an inventory.
     4. Run a catalog recovery using the wizard.
--------------------------------------------------------------------------------
Etrack Incident = ET1045886

Description:
   Added the ability to display disk-mount, failure reason codes in the
   Activity Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET1205703

Description:
   A change was made to address a bpjobd core dump issue originally discovered
   on a Tru64 master server and it spans all platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET1192264

Description:
   bpmedialist would list media multiple times if it was assigned to a cluster.
--------------------------------------------------------------------------------
Etrack Incident = ET1214150

Description:
   A change was made to ensure that you can install this release on a
   SunCluster.
--------------------------------------------------------------------------------
Etrack Incident = ET1215593

Description:
   A change was made to address an NBEMM core dump issue that occurred during
   internal testing efforts.
--------------------------------------------------------------------------------
Etrack Incident = ET1215487
Titan cases:  320-087-606

Description:
   A change was made to address "allocation failed" errors receiving in the
   Activity Monitor.

Additional Notes:
   This issue only affected Solaris and Unixware.
--------------------------------------------------------------------------------
Etrack Incident = ET1210546

Description:
   JobPolicies were not visible in NOM for a Solaris 10 X64-managed server.
--------------------------------------------------------------------------------
Etrack Incident = ET1201414

Description:
   Fixed a problem with taking a snapshot with a true device name on Solaris.
   Devices with a namespace like the following could not be supported.
   
     /devices/pci@1d,700000/fibre-channel@1,1/fp@0,0/ssd@w50060e801029f700,12:
     c,raw
   
   Improvements to logging have been made for both UNIX and Windows.
--------------------------------------------------------------------------------
Etrack Incident = ET1194146

Description:
   A change was made to remove older, unused code and files from NBSL.
--------------------------------------------------------------------------------
Etrack Incident = ET1169475

Description:
   After enabling NBAC, then running bpnbat -login for the first time and
   providing an empty domain value would cause it to abort and dump core.
--------------------------------------------------------------------------------
Etrack Incident = ET1193751

Description:
   A change was added to remove an extraneous dependency from the Makefile.
--------------------------------------------------------------------------------
Etrack Incident = ET1216307

Description:
   Attempting a Snapshot backup for an IBMDS4K-fim would cause a hang to
   occur. This issue was observed when the output of some of the SMCLI commands
   were not in an expected format.
--------------------------------------------------------------------------------
Etrack Incident = ET1217553

Description:
   A change was made to ensure that there are no duplicate message IDs as new
   message strings are being added.
--------------------------------------------------------------------------------
Etrack Incident = ET1219038

Description:
   Added SharedDisk support for RedHat Linux and SuSe Linux systems.
--------------------------------------------------------------------------------
Etrack Incident = ET1202823

Description:
   It was possible that after a duplication was started bptm could be delayed
   by mounting issues or something similar. In this case it might be delayed
   long enough for bpdm to attempt to connect to bptm over the socket that it
   expects to be available, and timeout before bptm has a chance to create the
   socket. The lack of vnet connection retries caused this scenario to fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1219898
Associated Primary Etrack = ET1220320
Titan cases:  220-216-339

Description:
   The bppllist -inventory option would fail to detect deleted policies, and
   schedule and clients that were deleted from clients.
--------------------------------------------------------------------------------
Etrack Incident = ET1219039

Description:
   Added support for SharedDisk using SCSI Persistent Reservations on the
   RedHat 4.0 Update 5 OS platforms. This proliferation encompasses Intel and
   AMD x86 and x64 platforms for SharedDisk media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1202383

Description:
   An issue can occur with an Instant Recovery Backup Policy with new
   hardware FIMs that have an unequal number of targets associated with all
   of the sources. For example, an Instant Recovery Backup Policy with new
   hardware FIMs, has two resources, resource A and resource B.  Resource A
   has three targets: A1, A2, and A3 while resource B has one target, B1. In
   this example, the first backup is successful, however, for the second
   backup the snapshot resource spec for B is not received and it fails.

Workaround:
   If you encounter this issue, change the policy so that you have an equal
   number of targets for all of the sources.
--------------------------------------------------------------------------------
Etrack Incident = ET1214304

Description:
   The schedule name was not displayed in the Activity Monitor for the jobs
   that would only take snapshots.
--------------------------------------------------------------------------------
Etrack Incident = ET1220901
Associated Primary Etrack = ET1218116
Titan cases:  311-842-209

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

Workaround:
   If you encounter this issue, remove the IGNORE_XATTR setting on the Master
   server when performing the cold catalog backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1102370

Description:
   Modified backup selections would display as unreadable characters in the
   output.
--------------------------------------------------------------------------------
Etrack Incident = ET1203744
Associated Primary Etrack = ET1195316
Titan cases:  311-783-307

Description:
   A backup job with the DISABLE_JOB_LOGGING option would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1204493
Associated Primary Etrack = ET1204113
Titan cases:  240-713-639

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

Workaround:
   To avoid this issue, perform a full restore of the image.
--------------------------------------------------------------------------------
Etrack Incident = ET1212228
Associated Primary Etrack = ET1220745
Titan cases:  290-914-792 290-956-352

Description:
   NetBackup services would crash on AIX systems if the services were down.
--------------------------------------------------------------------------------
Etrack Incident = ET1208344

Description:
   Additions and modifications have been made for NOM in the NBSL interfaces.
--------------------------------------------------------------------------------
Etrack Incident = ET1208227

Description:
   A change was made to address a core dump issue with nbfirescan.
--------------------------------------------------------------------------------
Etrack Incident = ET1220060

Description:
   NBJM would sometimes crash on shutdown if there were active parent jobs
   trying to use the connection factory.
--------------------------------------------------------------------------------
Etrack Incident = ET1222212

Description:
   The StorageServer attributes were incomplete for some OST servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1221166

Description:
   Policy updates were not reflected in NOM after stopping a policy proxy in
   NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET1220066

Description:
   The automatic duplication would not start on time for a snapshot-based
   backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1210010

Description:
   Changes have been made to TLD robotics multipath control and setup, such as
   the ability to add manual path control, the ability to view paths, and the
   ability to turn a feature on or off using robtest/tldtest.
--------------------------------------------------------------------------------
Etrack Incident = ET1220679

Description:
   Memory leaks would occur when devices were fetched.  In addition, the client
   program would crash if a memory allocation failed during a device fetch.
--------------------------------------------------------------------------------
Etrack Incident = ET1166549

Description:
   This release contains multiple changes to enhance FlashBackup VMWare.
--------------------------------------------------------------------------------
Etrack Incident = ET1136148

Description:
   If media server is in administrative pause state, the nbemmcmd -listhosts
   -verbose command should show this paused state.

Workaround:
   nbemmcmd -listhosts -verbose displays an integer value for machineState.
   If this is an odd number (least significant bit set), the host is in an
   administrative pause state.
--------------------------------------------------------------------------------
Etrack Incident = ET1172024 ET1184726 ET1226766

Description:
   On a very busy system nbemm could deadlock or core dump.

Workaround:
   If you encounter this issue, increase the number of DB connections.
--------------------------------------------------------------------------------
Etrack Incident = ET1222434 ET1220233 ET1215831 ET1214310 ET1221294 ET1227571
ET1229090 ET1228402 ET1231929 ET1230782 ET1235565 ET1230708 ET1236958 ET1231255
ET1233979 ET1194635 ET1242006 ET1242896 ET1237329 ET1241922 ET1239700 ET1238896
ET1235638 ET1236954 ET1247224
Associated Primary Etrack = ET1134318
Titan cases:  311-682-546

Description:
   PEM has been refactored for improved stability, scalability, and
   extensibility.
--------------------------------------------------------------------------------
Etrack Incident = ET1209391

Description:
   Both nbemm and nbrb invokes the notification script. They start the script
   and wait for the script to complete. This can cause a block for some time
   with the calling thread, and if the script started by nbemm calls back into
   nbemm, it can lead to a deadlock.
--------------------------------------------------------------------------------
Etrack Incident = ET1219962

Description:
   Sharepoint backups would fail if the allow multiple data streams was set to
   false. A change was made to the Policy Execution Manager to ignore this
   flag.  In addition, the change validates the place holder image so that
   Sharepoint jobs are not continually being restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET1215377 ET1223858

Description:
   Changes have been added to correct some SIS issues in capacity management.
--------------------------------------------------------------------------------
Etrack Incident = ET1219687

Description:
   A change was made to merge sections two and three of the job params file to
   allow a Windows Open File Backup (WOFB) job that has streaming disabled to
   save the snapshot ID of the parent job to the params file so that the
   snapshot can be deleted later using the snapshot ID that is stored in the
   jobs params file.   The original design did not allow the signature of the
   params file to change once created.
--------------------------------------------------------------------------------
Etrack Incident = ET1147842

Description:
   A change has been made in NOM so that it relies on the hostSession.ping
   (synchronous) method for finding the liveness of a connection, rather than
   using heartbeats.  This change means the recovery strategy must change for
   NBSL so that it too no longer relies on heartbeats.
--------------------------------------------------------------------------------
Etrack Incident = ET1224240

Description:
   A change was made to address an issue that would cause NBJM to crash on
   shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET619166

Description:
   A change has been made to ensure that the correct messages are logged in
   the syslog when there are zero cleanings remaining for a media. A message
   similar to the following should be logged.
   
     Cleaning tape CLN065 has 0 cleanings left
--------------------------------------------------------------------------------
Etrack Incident = ET1221669

Description:
   A change has been made to address a core dump issue found with nbrmms.
--------------------------------------------------------------------------------
Etrack Incident = ET1219679

Description:
   An NBSL deadlock may occur with a volume fetch and getNextPage operation and
   may cause the NBSL to not terminate cleanly.

Workaround:
   If you encounter this issue, stop and restart the NBSL service.
--------------------------------------------------------------------------------
Etrack Incident = ET1182185

Description:
   The NetBackup 6.5.1 patch install would remove PureDisk from the Disk Pool
   Type offering when no PureDisk Disk Pools were configured.
--------------------------------------------------------------------------------
Etrack Incident = ET1204359
Associated Primary Etrack = ET1204445
Titan cases:  220-302-209 320-083-263

Description:
   This release contains enhancements for better support management of
   NetBackup 5.1 legacy images on upgraded DSSUs.
--------------------------------------------------------------------------------
Etrack Incident = ET1210921

Description:
   A multi-path, standalone, non-shared drive caused confusion in EMM. EMM
   would think the scan path was different than the one that ltid was using.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1178113

Description:
   A change was made to implement server-side caching for the device monitor on
   the EMM server.
--------------------------------------------------------------------------------
Etrack Incident = ET1225918

Description:
   A change was made to correct a failure that would occur with pairvolstat
   on high end Hitachi arrays.
--------------------------------------------------------------------------------
Etrack Incident = ET1226849

Description:
   The bpfrag command used to replace a fragment record fails with a
   "no entity found" found error.

Workaround:
   If you encounter this error, configure a non-fully-qualified client name
   in the NetBackup policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1215580

Description:
   NetBackup will queue backup jobs to a disk storage unit if it thinks there
   is not enough space on the disk to store the backups.  For disk storage
   units with SIS devices, the device may be able to store the backup because
   of data deduplication.  The change causes NetBackup to not queue backup
   jobs to SIS devices.
--------------------------------------------------------------------------------
Etrack Incident = ET1226421 ET1212341

Description:
   In an IBM RS/6000 system the volume snapshot information is cached as
   part of a select call and then use it in a make operation. If only one
   target has "maintain snapshot for instance recovery" set then during a
   second backup, the delete call for the previous image and the create call
   of new image were being interleaved. This resulted in a backup failure.
--------------------------------------------------------------------------------
Etrack Incident = ET1225755

Description:
   The state details were not being shown for jobs that were run outside of
   NBJM's control, such as bpverify, bpduplicate, bpimport, etc..
--------------------------------------------------------------------------------
Etrack Incident = ET1229830

Description:
   The device allocator (DA) would not respect a NetBackup 5.1 host's
   SSO_SCAN_ABILITY zero setting.  A host's scanability must be set using
   nbemmcmd on the EMM server.  The vm.conf entry is no longer honored.
--------------------------------------------------------------------------------
Etrack Incident = ET1228237

Description:
   The nbproxy processes would hang during a cluster failover and could not
   be killed.
--------------------------------------------------------------------------------
Etrack Incident = ET1227068

Description:
   Enhancements have been made to the product code to address potential
   memory errors.  
--------------------------------------------------------------------------------
Etrack Incident = ET1229429

Description:
   The media contents job would fail when NBAC was configured. It would fail
   when using the user interface and the command line.
--------------------------------------------------------------------------------
Etrack Incident = ET1228937
Associated Primary Etrack = ET1225195
Titan cases:  290-061-961

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

Description:
   A change has been made to address an issue that would cause NBJM to crash
   on a shutdown.
--------------------------------------------------------------------------------
Etrack Incident = ET1231401

Description:
   Storage subsystems from the SMcli -d -i command's output was not being
   fetched correctly and lead additional failures. Incorrect logic of
   retrieving the data was the cause of this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1174590

Description:
   A change was made to correct a core dump issue in mmcrawl when it was run
   prior to configuring devices.
--------------------------------------------------------------------------------
Etrack Incident = ET1229149

Description:
   Changed Job Manager to only validate the SharePoint granular parent job
   which performs the discovery (using bpresolver).
--------------------------------------------------------------------------------
Etrack Incident = ET1222888

Description:
   The VxFI hpeva provider would log no error message if the HPEVA CLI was not
   installed.
--------------------------------------------------------------------------------
Etrack Incident = ET1176199
Associated Primary Etrack = ET1117350
Titan cases:  220-099-084 281-168-660

Description:
   ACS mounts would intermittently fail with a DISMOUNT failure.

Additional Notes:
   LTO drives now can take up to 15 minutes to come ready with tapes. Because
   of this, a change wasmade to acsd to allow for a 15 minute timeout on mount.
--------------------------------------------------------------------------------
Etrack Incident = ET1219001
Associated Primary Etrack = ET1130589
Titan cases:  290-822-170

Description:
   This release contains an enhancement to increase the efficiency of
   bpexpdate for tape in comparison with the time it took to complete with
   the NetBackup 6.0 release.  
--------------------------------------------------------------------------------
Etrack Incident = ET1221162

Description:
   An NBAC upgrade fails during a patch install with the following message:
   
   ERROR:  NetBackup Access Control upgrade has failed and must be run
   manually (Error Code 38).  Run "/usr/openv/netbackup/bin/admincmd/bpnbaz
   -Upgrade" after this installation completes.

Workaround:
   If you encounter this issue, run "bpnbat -login" as root/Administrator
   before the patch installation or before you manually execute the command
   "bpnbaz -upgrade".
--------------------------------------------------------------------------------
Etrack Incident = ET1185547

Description:
   Deletion of certain machine types would not clean up all of the references
   to that machine in the database.
--------------------------------------------------------------------------------
Etrack Incident = ET1231294
Associated Primary Etrack = ET1019103
Titan cases:  290-706-957

Description:
   The bpexpdate -deassignempty command may not work if one or more media
   servers were offline.
--------------------------------------------------------------------------------
Etrack Incident = ET1225909 ET1234586

Description:
   The following enhancements were added in this release to ensure that
   NetBackup 6.x supports back-revision 5.x media servers.
   
   Vmscd    - Clear the restart bit if ltid is confirmed to not be running.
            - Increased the 45 second timeout to 5 minutes.
   
   vmd      - Global DB and DA requests now handled in child vmd process.
            - Fix for master that does not have any drives (respond to
              registration with no scan host)
   
   mmcrawl  - Added an option to display ltid restart status on all
              drives and drive paths
            - Updated the repair option to clear the restart bit
   
   Vmoprcmd - Display a list of hosts that need to be restarted using the
              -show_restart option.
--------------------------------------------------------------------------------
Etrack Incident = ET1227943

Description:
   An NBAC user would not see the node for a licensed feature in the user
   interface.

Additional Notes:
   The default NBAC authorization schema has been updated to give Read
   permission on the License resource to all User Groups.
--------------------------------------------------------------------------------
Etrack Incident = ET1187087

Description:
   Installing Solaris X64 platform keys for NetBackup Enterprise Server would
   fail because the define for SOLARIS_X86 was not included in the make files
   for the server bpminlicense command and bpcd on the client.  This caused
   the compiled platform in the licensing header file to be incorrect and
   resulted in a platform mismatch for Solaris X64 keys.

Workaround:
   To avoid this issue, customer keys have been modified until the NetBackup
   problem is corrected.  

Additional Notes:
   Only master and media servers were affected because licenses were not
   installed on client servers.  
--------------------------------------------------------------------------------
Etrack Incident = ET1232796

Description:
   The state details of jobs like bpduplicate (for example, not started using
   NBJM) was not cleared when it went from a QUEUED state to a ACTIVE state.
--------------------------------------------------------------------------------
Etrack Incident = ET1193274
Associated Primary Etrack = ET1188782
Titan cases:  281-258-571

Description:
   Shared memory was not disabled during an encrypted database backup. This
   caused backups to not be encrypted.

Workaround:
   If you encounter this issue, add the /usr/openv/netbackup/NOSHM touch file.
--------------------------------------------------------------------------------
Etrack Incident = ET1177242
Associated Primary Etrack = ET1177238
Titan cases:  290-881-887

Description:
   bpmedia -movedb -allvolumes -newserver <hostname> -oldserver <hostname>
   
   When decommissioning a media server, a user may need a more efficient way
   of moving multiple tapes between media servers when the image database is
   very large.

Workaround:
   Run the following command for each volume assigned to the media server you
   are decommissioning.
   
   bpmedia -movedb -m <media_id> -newserver <hostname>
--------------------------------------------------------------------------------
Etrack Incident = ET1232143 ET1241235
Titan cases:  320-067-351

Description:
   Cannot remove drives with missing drive index records.
--------------------------------------------------------------------------------
Etrack Incident = ET1058986

Description:
   After upgrading from NetBackup 5.1MP6, you were not able to list images
   from a NAS snapshot backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1023503

Description:
   Authorization support in NBSL for services and processes information was
   not available.
--------------------------------------------------------------------------------
Etrack Incident = ET1234749

Description:
   A change has been made to ensure that the duplication manager always adds
   pending copies for all destinations (even if the destination is INACTIVE)
   into EMM.  In addition, a copy will not be considered for duplication if
   it is INACTIVE in every session.  
--------------------------------------------------------------------------------
Etrack Incident = ET1223697
Associated Primary Etrack = ET1143995
Titan cases:  230-438-228 290-891-616 290-913-205 320-080-024 220-107-441

Description:
   Multiple E-mail notifications were being sent for failed backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1040379 ET1163386 ET1136975 ET1157122 ET1157917 ET1157948
ET1145678 ET1077568 ET1026946 ET1021274 ET1200188 ET1211737
Associated Primary Etrack = ET1158195 ET1126744 ET1126744 ET1177307
Titan cases:  290-881-088 220-105-996 220-105-996 220-153-246

Description:
   The following issues have been addressed in this Release of NetBackup:
   
   - The NetBackup Notification Service would stop intermittently after
     upgrading to NetBackup 6.0 MP5.
   
   - Several core dump issues with the NetBackup Event Manager.
   
   - Several core dump issues with the NetBackup Enterprise Media Manager
     (NBEMM).
   
   - Memory leak issues with the NetBackup Event Manager.
   
   - Enhancements to performance and stability for the NetBackup Event
     Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET1232018

Description:
   An Inline tape copy job would fail instead of being queued if the drive was
   in use for one of the copies.
--------------------------------------------------------------------------------
Etrack Incident = ET1235456

Description:
   NetBackup would sometimes add multiple tape libraries in the database while
   configuring a shared non-serialized tape library.
--------------------------------------------------------------------------------
Etrack Incident = ET1235005

Description:
   A change was made to clean up duplicate and improper messages found.
--------------------------------------------------------------------------------
Etrack Incident = ET1078765

Description:
   Synthetic Backup jobs would fail when the destination media for the
   synthetic image was the same as the media on which one of the source
   images resided.
--------------------------------------------------------------------------------
Etrack Incident = ET1057296

Description:
   NBAC Logging did not adhere the log levels causing legacy and VxUL logs to
   flood.
--------------------------------------------------------------------------------
Etrack Incident = ET1211652
Associated Primary Etrack = ET1174784
Titan cases:  220-147-432

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

Description:
   When a catalog backup is started that contains AT VxSS backup directives
   for NABC that point to a nonroot broker, an error would occur during the
   snapshot attempt of AT.
--------------------------------------------------------------------------------
Etrack Incident = ET1232083
Titan cases:  311-826-710

Description:
   PrevPoolName was being set even if the pool was changed manually. A change
   has been made to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1216897

Description:
   A change was made to maintain the protocol of sending exceptions instead
   of nil objects in case of failures.
--------------------------------------------------------------------------------
Etrack Incident = ET1225310
Associated Primary Etrack = ET1217065
Titan cases:  240-717-814

Description:
   Image cleanup would fail because of incomplete backup images in the catalog.

Workaround:
   If you encounter this issue, delete the offending catalog files from
   the disk.

Additional Notes:
   An improper shutdown of the NetBackup services caused the problem images.
   When shut down normally, incomplete backup images cannot occur.
--------------------------------------------------------------------------------
Etrack Incident = ET1235448

Description:
   NBJM crashed on shutdown when there were pending requests in the Callback
   queue.
--------------------------------------------------------------------------------
Etrack Incident = ET1170652

Description:
   bpplinfo would crash when listing policies that require snapshots.
--------------------------------------------------------------------------------
Etrack Incident = ET1177789
Associated Primary Etrack = ET1163418
Titan cases:  240-659-059

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

Workaround:
   The workaround for this scenario is to ignore the error message because
   it is benign.
--------------------------------------------------------------------------------
Etrack Incident = ET1209428

Description:
   A verify of a large backup image would potentially fail with a "client
   process aborted" error.
--------------------------------------------------------------------------------
Etrack Incident = ET1216741

Description:
   Running vmphyinv on some hosts would result in the following error:
   
     Unable to get global device list: invalid host name (136)
--------------------------------------------------------------------------------
Etrack Incident = ET1236418
Associated Primary Etrack = ET1230008
Titan cases:  290-908-260 240-730-144

Description:
   The debug files produced when a backup was run with the touch file
   NetBackup/db/images/<client>/debug_file_history in place were not accurate
   for some NDMP and FlashBackup file entries.
--------------------------------------------------------------------------------
Etrack Incident = ET1221440

Description:
   A Snapshot backup takes a longer time to complete. These were issues in the
   IBM provider, device provider, and VxFS provider.
--------------------------------------------------------------------------------
Etrack Incident = ET1230757

Description:
   When PEM recovers a parent job that has not yet created children, it fails
   with an EC_client_aborted error.  But when it is retried, it continues to
   fail with the same error.  A change has been added to ensure that this
   job is not tried again to avoid a continuous loop.

Workaround:
   If you encounter this issue, manually cancel the job.
--------------------------------------------------------------------------------
Etrack Incident = ET1162296

Description:
   If a duplication job is in progress, expiration of the read media will not
   be allowed at that time.
--------------------------------------------------------------------------------
Etrack Incident = ET1146475

Description:
   The message given by a hot catalog backup job in the Activity Monitor
   was confusing. It said, "Offline catalog backup FAILED". A change was made
   to the message to avoid confusion.
--------------------------------------------------------------------------------
Etrack Incident = ET1236185
Associated Primary Etrack = ET1217146
Titan cases:  311-824-283

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

Description:
   Could not perform an autodiscover for ACS robots on ACSLS servers without
   ACS 0 defined on the ACSLS server.
--------------------------------------------------------------------------------
Etrack Incident = ET1229033
Associated Primary Etrack = ET1198237
Titan cases:  311-813-853

Description:
   vmdareq -h ignores the command line specification for the EMM server, and
   it pulls the server name from bp.conf instead.
--------------------------------------------------------------------------------
Etrack Incident = ET1032515

Description:
   A gethostname failure would not produce an error message.
--------------------------------------------------------------------------------
Etrack Incident = ET1234295

Description:
   With the Language Pack installed, the nbshareddisk release command would
   not capture the user-defined identifier's (UDID). The following error
   message would appear in Japaneses and the UDID for each LUN was not
   captured.
   
     List of the UDID that can't access to the host
   
   If Language Pack is not installed or used, it correctly displays the
   following message and captures UDID for each LUN.
   
     Released reservation on device
--------------------------------------------------------------------------------
Etrack Incident = ET1236042
Associated Primary Etrack = ET1225889
Titan cases:  320-091-983

Description:
   When a backup is started using the wait (-w) option, the bprd child
   process is alive during backup execution and pings pem to check that it
   is alive. This ping mechanism prints a log message every second and can
   cause the bprd log to fill quickly and unnecessarily.
   
   A change has been added that ensures the message queue is read only when
   there is a message in the the queue, and not reading message queue every
   second.
--------------------------------------------------------------------------------
Etrack Incident = ET1161380

Description:
   bpplinfo and bpadm would crash if the policy type was NBU-Catalog and the
   residence specified is a storage life cycle.
--------------------------------------------------------------------------------
Etrack Incident = ET1141296

Description:
   Disk staging storage units (DSSUs) going from basic disk to advanced disk
   would create multiple duplicates.
--------------------------------------------------------------------------------
Etrack Incident = ET1200165
Associated Primary Etrack = ET1169657
Titan cases:  290-843-958

Description:
   Received the following warning message when deassignempty was run on an
   unassigned media and image indexing was in use.
   
     Could not deassign media due to Media Manager error (177)

Workaround:
   Do not use image indexing.

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

Description:
   NBJM crashed when a SQL Persistent Frozen Image (PFI) backup with VxVM was
   run. It would crash on receipt of a BRMBackupHost message which was added
   with this release.
--------------------------------------------------------------------------------
Etrack Incident = ET1225284
Titan cases:  220-220-209

Description:
   A change was made that provides the ability to add a timeout to resource
   requests in Resource Broker.
--------------------------------------------------------------------------------
Etrack Incident = ET1238631
Titan cases:  290-960-740

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

Description:
   The online catalog backup email report and disaster recovery file were
   not listing all of media for critical policies.
--------------------------------------------------------------------------------
Etrack Incident = ET1234618

Description:
   A change was made to not destroy the manager in case of user-defined
   exceptions.
--------------------------------------------------------------------------------
Etrack Incident = ET1238097
Associated Primary Etrack = ET1215629
Titan cases:  290-934-270

Description:
   A change was made to address an NBNOS core dump issue that would occur on
   an AIX master server.
--------------------------------------------------------------------------------
Etrack Incident = ET1235414

Description:
   The number of volumes that can be configured in a TLD robot has been
   increased to 32767 slots.
--------------------------------------------------------------------------------
Etrack Incident = ET1196526

Description:
   If the localization of the install is not English, then it is possible that
   a duplication will hang indefinitely because of a string being improperly
   localized. (This issue has been observed with French and Chinese locals.)

Workaround:
   If you encounter this issue, set the localization to default, or English.
--------------------------------------------------------------------------------
Etrack Incident = ET1239571

Description:
   Disk to Tape duplication jobs would not always terminate properly if they
   were canceled or interrupted.
--------------------------------------------------------------------------------
Etrack Incident = ET1242510
Associated Primary Etrack = ET1225587
Titan cases:  240-705-124

Description:
   A change was made to correct a display issue for the Drive and Robot
   diagnostics to display the status of the test back to a remote user
   interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1238594
Titan cases:  220-220-209

Description:
   Vault duplication performance is impacted by "waiting on resources" while
   a tape is currently "in use" by a backup. A timeout value for NBRB "waiting
   on resources" has been created to ensure that Vault will move on to the
   next image after a specific amount of time.
--------------------------------------------------------------------------------
Etrack Incident = ET1242645

Description:
   When backing up to a PureDisk storage unit, the backup would fail with a
   status 27: "child process killed by signal" error.
--------------------------------------------------------------------------------
Etrack Incident = ET1223956

**Description:
   The storage service would not retry a failed duplication.
--------------------------------------------------------------------------------
Etrack Incident = ET1241071

Description:
   It was possible for bpjobd to lose jobs when stopped abruptly. When bpjobd
   was restarted, the jobid file was reset to the highest jobid known to
   bpjobd. This could lead to duplicate jobids because the lost jobids may be
   known to NBPEM as suspended or incomplete jobs. In addition, the restart,
   try logs and files files for the lost jobs were removed when bpjobd recycled
   the unused files. As a result the lost jobs could not be resumed or
   restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET1230334

Description:
   A change has been made to enable bpclusterutil to log its actions to aid
   troubleshooting during isCluster, isActive, addSvc, deleteSvc, enableSvc,
   disableSvc calls.
   
   The log file will be created if the following directories exist.
   UNIX:
   - For NetBackup: /usr/openv/netbackup/bin/cluster/logs
   - For NOM: /opt/VRTSnom/bin/cluster/logs
   
   Windows:
   - For NetBackup: C:\Program FIles\Vertias\NetBackup\bin\cluster\logs
   - For NOM: C:\Program Files\Veritas\NetBackup Operations Manager\bin
              \cluster\logs
--------------------------------------------------------------------------------
Etrack Incident = ET1232394

Description:
   An SQL Server backup job would fail because the Policy Execution Manager
   was incorrectly passing snapshot options -fi, -fim, -catalog, and -pfi to
   the backup job.  These options are only for file-based backups and not
   stream-based backups which was the case here.
--------------------------------------------------------------------------------
Etrack Incident = ET1243077

Description:
   The Resource Broker (RB) would crash when allocating resources for
   duplicate backups, synthetic backups, or multiple copy jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET1231197

Description:
   The Policy Execution Manager was passing duplicate -alt_client options to
   the Exchange off-host backup.  In addition, it would pass the -alt_client
   option when it was not required because the parameter was not initialized
   correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET1241424

Description:
   Authorization-related changes have been added for NBAC and NBSL.
--------------------------------------------------------------------------------
Etrack Incident = ET1232362

Description:
   Added additional logic checking within NBSL to ensure that REQUIRED mode
   under VxSS does not create a PBXIOP transport end point when user calls
   are proxied through NBSL.
--------------------------------------------------------------------------------
Etrack Incident = ET1176451

Description:
   Truncated messages without a trailing newline character were being emitted
   by bpfis.
--------------------------------------------------------------------------------
Etrack Incident = ET1187803

Description:
   Truncated messages without a trailing newline character were being emitted
   by bpfis.
--------------------------------------------------------------------------------
Etrack Incident = ET1187920

Description:
   The bpbrm (pid=20271) process from a client system failed with a status 20.
--------------------------------------------------------------------------------
Etrack Incident = ET1244764

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

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

Description:
   NBJM would crash on shutdown when jobs were active.
--------------------------------------------------------------------------------
Etrack Incident = ET1238066
Titan cases:  281-285-952

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

Description:
   The Catalog record would not get deleted when performing a cancel operation
   in nbstlutil.  
--------------------------------------------------------------------------------
Etrack Incident = ET1221476
Associated Primary Etrack = ET1135854
Titan cases:  281-213-06 281-213-065

Description:
   During large backup jobs, connections between master and media servers
   were closed due to long periods of inactivity.  This caused jobs to be
   orphaned and resources released. A change was made that enables
   SO_KEEPALIVE handling on the PBX and ACE/TAO level making it possible to
   send keep alive packets periodically and prevent the connection from
   closing.
--------------------------------------------------------------------------------
Etrack Incident = ET1247671

Description:
   A negative job status was being shown for a running job.
--------------------------------------------------------------------------------
Etrack Incident = ET1249057
Associated Primary Etrack = ET1248292
Titan cases:  290-970-903 311-846-532

Description:
   Imports would fail (potentially backups as well) in a busy UNIX environment
   where the reading of a catalog record by bpbrm was interrupted in the
   middle of the record.
--------------------------------------------------------------------------------
Etrack Incident = ET1242003

Description:
   Images would not get deassigned if they are taken on a disk staging storage
   unit on a cluster node.
--------------------------------------------------------------------------------
Etrack Incident = ET1249129
Associated Primary Etrack = ET1247786
Titan cases:  320-096-794

Description:
   NetBackup would not expire empty media in a media sharing group using
   "bpmedia -deassignempty" if UNRESTRICTED_MEDIA_SHARING was enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET1233754

Description:
   The nbproxy would crash when a Pure Disk Export job was run.
--------------------------------------------------------------------------------
Etrack Incident = ET1251779
Associated Primary Etrack = ET1242682
Titan cases:  290-962-969

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

Description:
   Drives would become stuck in AVR mode until ltid was restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET1252344

Description:
   After upgrading from NetBackup 5.x or manually configuring an ACS robot on
   NetBackup a 6.x server, running autodiscovery will add a new NetBackup ACS
   robot to the configuration instead of using the one already configured.  
--------------------------------------------------------------------------------
Etrack Incident = ET1253274 ET1261508
Associated Primary Etrack = ET1251645
Titan cases:  290-960-008

Description:
   NetBackup 6.5 was not respecting the settings MUST_USE_LOCAL_DRIVE and
   DONT_USE_SLAVE for a multiplexed (MPX) group (greater than 1).
--------------------------------------------------------------------------------
Etrack Incident = ET1253326

Description:
   If a spanned request was canceled, the original resources would not be
   released again and would not be available for use for other jobs even
   though they were not being used.
--------------------------------------------------------------------------------
Etrack Incident = ET1244703

Description:
   On Windows platforms, a change was made to add support in the "nbsharddisk
   format" command to format with either a Master Boot Record (MBR) or GUID
   Partition Table (GPT) partition style. By default, the disk is formatted
   with the MBR partition style. This style has a maximum disk size limit of
   2TB.  To format a disk with the GPT partition style the -gpt option needs
   to be passed with the "nbsharddisk format" command.
--------------------------------------------------------------------------------
Etrack Incident = ET1252276

Description:
   An unmask operation for HPeva LUNs would fail, if the folder name of an
   array under which the hostname is registered contains a space.
   
   For example, If hostname OIGTWIN18 is registered on an array under the
   folder, "\Hosts\WIN Hosts" which contains a space. An unmasking operation
   on this host using nbshareddisk would result in a failure. Removing the
   space from the folder name corrects the error and enables the operation
   to succeed.
--------------------------------------------------------------------------------
Etrack Incident = ET1255224
Associated Primary Etrack = ET1167945
Titan cases:  220-204-657 230-518-698 240-719-166 240-766-752 281-242-138
290-916-950 290-935-090 290-943-738 290-985-114 290-986-582 290-994-641
311-821-582 320-105-655

Description:
   DSSU duplication jobs would fail with a status 50 that appeared in the
   Activity Monitor if more than one copy was made concurrently.
   
   For Duplications with two copies being created at the same time, BPJOBD
   appeared to cancel the duplication after 20 minutes
   
   The problem would occur if duplicating more than one copy concurrently.
--------------------------------------------------------------------------------
Etrack Incident = ET1252754
Titan cases:  240-724-837

Description:
   A change has been made to prune old server entries from the vnet server
   version cache and rely on the cache during DA_REGISTRATION processing.
--------------------------------------------------------------------------------
Etrack Incident = ET1256135

Description:
   SAN Client's nbhba mode on Linux RedHat systems could not be loaded without
   unloading the Qlogic driver first.
--------------------------------------------------------------------------------
Etrack Incident = ET1257773
Titan cases:  281-334-212

Description:
   The NetBackup Resourse Broker (NBRB) does not guarantee spans have top
   priority when nbrb.conf setting RESPECT_REQUEST_PRIORITY = 0, and
   SECONDS_FOR_EVAL_LOOP_RELEASE is nonzero.

Workaround:
   This issue is only seen when the nbrb.conf settings are used to modify the
   NBRB job evaluation behavior.

Additional Notes:
   Because the Resource Broker may now be configured to not respect a request
   priority for the purposes of increasing throughput, spans must be treated
   differently to guarantee they are always given top priority.
--------------------------------------------------------------------------------
Etrack Incident = ET1259057
Associated Primary Etrack = ET1175415
Titan cases:  220-148-833

Description:
   A bpbrmds application error would appear (faulting module) randomly on
   Windows.  
--------------------------------------------------------------------------------
Etrack Incident = ET1258889

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

Description:
   Duplication of some images would fail when Media Sharing was enabled, media
   was written by multiple media servers, and an alternate read media server
   was not used for the duplication.

Workaround:
   If you encounter this issue, use the duplication alternate read server
   option.
--------------------------------------------------------------------------------
Etrack Incident = ET1260423
Associated Primary Etrack = ET1196883
Titan cases:  311-766-587

Description:
   A differential backup to a NearStore storage unit would fail with a
   status 26 after expiring a full backup image.
--------------------------------------------------------------------------------
Etrack Incident = ET1260502
Associated Primary Etrack = ET1180335
Titan cases:  320-076-645

Description:
   User-directed backups would fail with the following status 12 error.
     "using bpdm when root umask=066; ERR - Could not open file <filename>
      to get shared memory information."
--------------------------------------------------------------------------------
Etrack Incident = ET1140864

Description:
   A change was made to ensure synthetic backups calculate the correct delta
   time. In addition, the change ensures an image does not leave a place
   holder image behind after the backup expires.
--------------------------------------------------------------------------------
Etrack Incident = ET1261506
Titan cases:  240-724-837

Description:
   The nbpushdata -add command fails while contacting media servers to get
   the host information.  The following is the error information that appears
   in the nbpushdata log:
   
     RetrieveFile: fdopen <filename> failed: Too many open files (24)

Workaround:
   To work around this issue, run nbpushdata -add again.  A second attempt
   will be successful when contacting the media servers that were not
   successfully contacted previously.
--------------------------------------------------------------------------------
Etrack Incident = ET1248919
Associated Primary Etrack = ET1248266
Titan cases:  320-097-705

Description:
   The Disk Service Manager (DSM), the Resource Event Manager (REM), and
   nbstserv need to honor the app_cluster machine type and nbu_cluster machine
   type as a media server for disk and volume queries.
--------------------------------------------------------------------------------
Etrack Incident = ET1259995
Associated Primary Etrack = ET1262089

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

**Description:
   Backup images are not accessible after upgrade from 6.5 SharedDisk
   installations to 6.5.1 or beyond on Solaris media servers. In worst case
   backup images may get overwritten causing data loss. bpverify can be
   used to verify that backup images are accessible after upgrade.
   
   For more information about this issue, refer to the following TechNote on
   the Symantec Support Web site.
   
     http://entsupport.symantec.com/docs/303369
   
   If a disk currently has Slice 6 formatted, the NetBackup 6.5 formats
   would not clean Slice 6. In this case, if a user upgrades from
   NetBackup 6.5 to a higher version, the online logic uses Slice 6 if it
   detects a valid filesystem and starts copying the backup to Slice 6 by
   overwriting the already written backups on Slice 2.

Workaround:
   To resolve this issue, use bpverify to detect such a disk immediately
   after the upgrade.  If some of the backup images are not accessible, this
   could be a likely reason. The disk, for which a failure occurred, can be
   found from the ShareDisk logs.
   
   Again, refer to the following TechNote on the Symantec Support Web site
   for a complete set of instructions on how to work around this issue.
     http://entsupport.symantec.com/docs/303369
   
   (If you cannot use the SPR options use the following procedure.)
     1.  Use nbsharedisk unmask to make the disk visible to one of the
         media servers.
     2.  Mount slice 2 (using OS mount command) and copy the data to the
         temporary disk.
     3.  Remove the partitions from the disk.
     4.  Clean and format the disk using nbsharedisk.
     5.  Copy the data back from the temporary disk to the original disk.
--------------------------------------------------------------------------------
Etrack Incident = ET1262100

Description:
   A change was added to address a issue that caused bpdbm to hang on some
   queries.
--------------------------------------------------------------------------------
Etrack Incident = ET1262650

Description:
   The following debug message, "MSRDbConnection::ReleaseOldestResultSet", is
   being erroneously logged at a DebugLevel 1. In NetBackup 6.5.2 this
   message is very common and could occur hundreds of times per minute. This
   message should really appear only at debug level 5. This issue will cause
   the log files to grow very rapidly.  

Workaround:
   To avoid this issue, set the DebugLevel to 0.  
--------------------------------------------------------------------------------
Etrack Incident = ET1261953

Description:
   A change has been made to the Policy Execution Manager to log the Locale
   setting on startup to debug Internationalization (I18N) issues.
--------------------------------------------------------------------------------
Etrack Incident = ET1260960

Description:
   Job Manager performed stream discovery (calling bpmount on the client)
   without checking preprocess interval. Then, when it attempted to process
   the discovery data from bpmount, it checked the preprocess interval and
   decided no discovery was needed; thus, the bpmount output was not used to
   create the stream alternate (alt) file.  End result was the file list
   from the policy was used by bpfis to create the snapshot instead of the
   streams file that caused it to expand the wild card to 70 entries. Since
   the file list did not start with a NEW_STREAM, each entry was considered
   an separate stream.
--------------------------------------------------------------------------------
Etrack Incident = ET1264708

Description:
   Two variables in sfr.h were changed to 64-bit. When these two variables
   were something other than 64-bit, FlashBackup Windows restores would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1265914

Description:
   Manual configuration of an ACS robot would fail when adding more than one
   library per API host.
--------------------------------------------------------------------------------
Etrack Incident = ET1263185

Description:
   There were instances where the parent place holder image had zero for the
   stream number instead of -1.  The backup and restore user interface would
   then display these place holder images as real images to restore from when
   in fact they were not real images because the image attribute was 0 and
   not 203 (the place holder image).
--------------------------------------------------------------------------------
Etrack Incident = ET1266636

Description:
   After a successful import and format of IBM6000 LUNs, taking them offline
   caused a failure with a provider-specific error.

Workaround:
   If you encounter this error, ensure that the "hostname" command on Solaris
   and the host name that is registered with the IBMTS array are an exact
   match. If the FQDN name is specified, then both of the names MUST be FQDN.
--------------------------------------------------------------------------------
Etrack Incident = ET1266832

Description:
   A change was made to the NetBackup Access Control authorization CLI to
   upgrade the authorization information to support the Key Management
   Services.
--------------------------------------------------------------------------------
Etrack Incident = ET1267444

Description:
   A change was made to address an NBSL core dump issue that would occur when
   job logs were fetched from NOM user interface and when the backuptrace in
   NetBackup server command was not working.
--------------------------------------------------------------------------------
Etrack Incident = ET1268822

Description:
   The NetBackup Policy Execution Manager (nbpem) would core dump under a
   heavy load.

Workaround:
   If you encounter this issue, change the default in VxUL of
   MaxLogFileSizeKB to 51200 as shown below.
   
      vxlogcfg -a -p 51216 -o default -s MaxLogFileSizeKB=51200
--------------------------------------------------------------------------------
Etrack Incident = ET1269897

Description:
   A change was made to correct a potential nbemm core dump issue that could
   occur while shutting down the services on Windows x64 Master server.  This
   issue was not present in NetBackup 6.5GA or 6.5.1. However, it was
   determined that this issue could have occurred on a very busy system.
--------------------------------------------------------------------------------
Etrack Incident = ET1270380

Description:
   Oracle scheduled backups would run before they were due.
--------------------------------------------------------------------------------
Etrack Incident = ET1137172
Associated Primary Etrack = ET1119164
Titan cases:  220-105-447

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





========
NB_6.5.1
========

Etrack Incident = ET1081404
Associated Primary Etrack = ET1064989
Titan cases:  290-661-307

Description:
   A .f catalog file that was corrupted by a disk failure or other
   issue could cause bpdbm -consistency to core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET1082281

Description:
   Cancellations for span requests would get lost in the NetBackup
   Resource Broker (RB).
--------------------------------------------------------------------------------
Etrack Incident = ET1081354

Description:
   Resolved an issue where you were unable to backup the NBAC database
   in catalog backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1081698

Description:
   Enhancements were added in preparation for future improvements
   to nbpem.exe.
--------------------------------------------------------------------------------
Etrack Incident = ET1077267

Description:
   Resolved an issue that may cause nbrb to crash while shutting down.
--------------------------------------------------------------------------------
Etrack Incident = ET1089270
Associated Primary Etrack = ET1089215
Titan cases:  240-603-428

Description:
   nbpemreq is not correctly predicting backups in policies
   that do not have a window open that is spanning when a
   schedule is due.  
--------------------------------------------------------------------------------
Etrack Incident = ET1095231

Description:
   A change was added to make use of the co-location of RDSM and
   STSSvc when making CORBA calls by calling
   resolve_initial_references() prior to calling connectToObject().
--------------------------------------------------------------------------------
Etrack Incident = ET1088607

Description:
   Added SharedDisk SCSI persistent reserve (SPR) code changes in the
   VxFI library.
--------------------------------------------------------------------------------
Etrack Incident = ET1084993

Description:
   The resource broker (RB) would fail some jobs (mainly cleanup
   jobs) with a resource broker internal error.
--------------------------------------------------------------------------------
Etrack Incident = ET1060897
Titan cases:  220-099-064

Description:
   Characters that violate the naming conventions were accepted as a media ID.
   These characters caused issues in the database that caused it to be
   unusable and not deletable.
   
   Valid characters are: alphanumerics, ., +, -, and _.
--------------------------------------------------------------------------------
Etrack Incident = ET1088606 ET1100978 ET1118302

Description:
   Added a Disk Service Manager (DSM) API needed for the SCSI
   Persistent Reservation (SPR) feature.
--------------------------------------------------------------------------------
Etrack Incident = ET1079723
Associated Primary Etrack = ET1079721

Description:
   nbemm would occasionally crash (core dump) on busy systems.
   This happened more frequently when NetBackup was restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET1090571

Description:
   The NBProxy that is used to collect jobs was being terminated
   by NBSL randomly. This occurred because initialDataLoadStatus()
   was performing the wrong logic.  This cause the job data collection
   to not function properly.
--------------------------------------------------------------------------------
Etrack Incident = ET1084947

Description:
   The NBproxy core dumped while NOM was connected to NetBackup
   and collecting skipped-file data.
   
   
--------------------------------------------------------------------------------
Etrack Incident = ET1088608 ET1111471

Description:
   Added a configuration option for SCSI-Persistent Reserve.
--------------------------------------------------------------------------------
Etrack Incident = ET866629

Description:
   On HP-UX platforms, stale physical volumes (PVs) in a volume
   group (VG) prevent VxFI from importing snap volumes. As a result,
   the user would see an "Invalid LVMREC" error.
--------------------------------------------------------------------------------
Etrack Incident = ET1039048

Description:
   Changes were added that fix nbdevquery and nbdevconfig parsing.
--------------------------------------------------------------------------------
Etrack Incident = ET1041354

Description:
   A change was made to correct a usage statement (error message).
--------------------------------------------------------------------------------
Etrack Incident = ET1046330

Description:
   The -media_server option is no longer required to create a
   direct-attached storage server.
--------------------------------------------------------------------------------
Etrack Incident = ET1050492

Description:
   A usage message showed an incorrect default for the
   -creatests operation.
--------------------------------------------------------------------------------
Etrack Incident = ET1076912

Description:
   Added the new -EMM option to the nbdevquery command.
--------------------------------------------------------------------------------
Etrack Incident = ET1096261

Description:
   Changes were made to enhance the DSM logging performance.
--------------------------------------------------------------------------------
Etrack Incident = ET1003906

Description:
   Shutdown of the NetBackup database (NBDB) and BMRDB databases
   was prevented if the vxdbms.conf file did not exist.  This caused
   bprecover from a cold catalog backup to fail.  This issue has
   been fixed.
--------------------------------------------------------------------------------
Etrack Incident = ET1088607

Description:
   Implemented SCSI3 Persistent Reservation on a SharedDisk LUN to
   avoid data curruption.
--------------------------------------------------------------------------------
Etrack Incident = ET1094608

Description:
   Importing EMC Symmetrix Meta Luns would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1100617
Associated Primary Etrack = ET1091665
Titan cases:  290-823-681

Description:
   NetBackup Service Layer (NBSL) failed to terminate using the
   "netbackup" script or "nbsl -terminate" command after starting
   with an "at" command.
--------------------------------------------------------------------------------
Etrack Incident = ET1059862
Associated Primary Etrack = ET1056231
Titan cases:  240-512-525

Description:
   bprecover fails if the executing user never launches the NetBackup-
   Java Administration Console.  It fails because the
   user_ops/<username>/jobs does not exist unless the Java Administration
   Console was started.  bprecover now checks that this directory exists
   for the user and creates it if necessary.

Workaround:
   To avoid this issue, launch the NetBackup-Java Administration
   Console and then run bprecover.
--------------------------------------------------------------------------------
Etrack Incident = ET1098378

Description:
   Span requests may fail with an error code 4000002. This occurred
   because the storage unit (STU) count was incorrectly decremented.
--------------------------------------------------------------------------------
Etrack Incident = ET1047276
Associated Primary Etrack = ET1044565
Titan cases:  290-777-895

Description:
   After catalog recovery, the Sybase ASA server name that was
   stored in the NetBackup configuration files was checked to make
   sure that all copies were consistent with each other.
--------------------------------------------------------------------------------
Etrack Incident = ET1061031

Description:
   A Sig Sched call was not thread safe.
--------------------------------------------------------------------------------
Etrack Incident = ET1100839
Associated Primary Etrack = ET1052610
Titan cases:  311-480-661

Description:
   On HP-UX IA64, restores of large sparse files (4 gigs+) would fail
   to correctly restore the file holes that were present.

Additional Notes:
   Running ls -ls would show that the restored files occupy fewer
   blocks than the original. The checksum of the file would also be
   different, simply because the file holes would be absent.
--------------------------------------------------------------------------------
Etrack Incident = ET1070220

Description:
   A duplication job for multiple images would terminates with a
   "STUs not available" error.
--------------------------------------------------------------------------------
Etrack Incident = ET1005055

Description:
   Added support for SharePoint 2007 and Windows SharePoint
   Server (WSS) 3.0.

Additional Notes:
   Use the Microsoft SharePoint Directive "MS SharePoint - 2003"
   for SharePoint 2007.
--------------------------------------------------------------------------------
Etrack Incident = ET1100685

Description:
   When attempting to perform a full VM restore the newly entered staging
   location did not take effect. A problem existed when writing the restore
   "rename" file.
--------------------------------------------------------------------------------
Etrack Incident = ET1100697

Description:
   Currently the VMWare framework does not support overwriting
   existing Virtual machines (VMs). Hence these options have been
   removed from the RestoreDialog options.
--------------------------------------------------------------------------------
Etrack Incident = ET1056259

Description:
   During a duplication job of multiple images and after a
   successful duplication of the first image, if all the drives are
   in use by the same job, then the duplication hangs forever
   waiting for drives.
--------------------------------------------------------------------------------
Etrack Incident = ET1104423

Description:
   Fixed the Windows 2003 SAN Client Fibre Transport device discovery
   on some Emulex FC adapters.
   
   The SAN Client would fail to discover Fibre Transport devices and
   would report an IO_DEVICE_ERROR from DeviceDiscovery when viewed
   using the following command on the affected client machines.
      vxlogview -o 200 -i 200  

Additional Notes:
   Similar changes were made to both the Windows client and the
   various Fibre Transport Media Server to resolve this issue.
   
   WARNING: If you update any FT Media Server with this Release Update,
   you must update all of the Windows SAN Clients with this pack.
   
   WARNING: If you update any Windows SAN Client with this Release
   Update, you must update all of the FT Media Servers with this pack
   and all of the other Windows SAN Clients.
--------------------------------------------------------------------------------
Etrack Incident = ET1080484

Description:
   The Disk Polling Service(DPS) calls into the Resource Event
   Manager (REM) with capacity update information that can take a
   long time in a heavily loaded or large system. Such blocking calls
   could cause communication errors or down media servers for disk
   activity.
--------------------------------------------------------------------------------
Etrack Incident = ET1100881
Associated Primary Etrack = ET1086608
Titan cases:  240-597-110


Description:
   On AIX, a common Internet file system (CIFS) was backed up under
   the local drives directive, when it was actually a remote drive.

Workaround:
   To avoid this issue, create an exclude entry for drives that are
   CIFS if they are not wanted in the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET1077695
Associated Primary Etrack = ET936099
Titan cases:  220-084-917 220-097-471

Description:
   Changes have been added to resolve some issues that caused the
   NetBackup Resource Broker (nbrb) to hang.
--------------------------------------------------------------------------------
Etrack Incident = ET1096284

Description:
   VMware backups hung when multiplexed.

Workaround:
   To avoid this issue, turn off multiplexing for VMware policies.
--------------------------------------------------------------------------------
Etrack Incident = ET1102886

Description:
   This Release Update contains support for the new SPR (SCSI3
   Persistent Reservation) feature for disk.
--------------------------------------------------------------------------------
Etrack Incident = ET1072317

Description:
   The format of EMC Clariion LUNs would fail if the hostname was
   not exactly same as was registered on the Clarrion array because
   the logic of the hostname was case sensitive. A change has been
   to ensure the hostname comparison logic is no longer case
   sensitive.
--------------------------------------------------------------------------------
Etrack Incident = ET1110605
Associated Primary Etrack = ET1094524
Titan cases:  240-610-300

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

Description:
   A change has been added that makes catalog queries for processed
   images more efficient.  This change ensures that large numbers of
   images are processed in a reasonable time.
--------------------------------------------------------------------------------
Etrack Incident = ET1102521

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

Workaround:
   To avoid this issue, run bpnbat -loginmachine on the target host
   once every 14 days.
--------------------------------------------------------------------------------
Etrack Incident = ET1094558

Description:
   Under NetBackup Access Control (NBAC)and during a catalog restore,
   error messages would appear in the debug logs because of missing
   permissions.
--------------------------------------------------------------------------------
Etrack Incident = ET1102639

Description:
   A restore of a SAN client would potentially hang.  The bptm processes
   on the server would complete, but the bpbkar process on the client
   would remain active.
   

Workaround:
   To resolve this issue, on the media server, create the following
   file:
   
   /usr/openv/netbackup/WAIT_TO_CLOSE
   
   and enter a value in the file for the number of seconds for bptm
   to wait prior to terminating to allow the client to read all of
   the data.  A value of 60 should be sufficient.
--------------------------------------------------------------------------------
Etrack Incident = ET1093595

Description:
   When trying to view media using the NetBackup-Java Administration
   Console, you would receive a time-out and NOM would report the
   server as being down.  The root cause of this problem was that
   too many threads in NBSL were busy collecting client NetBackup
   versions.  Changes have been made to correct this issue.
   
--------------------------------------------------------------------------------
Etrack Incident = ET1103786

Description:
   A change was made to resolve an issue that caused a NetBackup
   Service Layer (nbsl) core dump to occur in an exceptional case.
--------------------------------------------------------------------------------
Etrack Incident = ET1103600

Description:
   A change was made to resolve an issue that caused a NetBackup
   Service Layer (nbsl) to crash.
--------------------------------------------------------------------------------
Etrack Incident = ET1105269

Description:
   While adding NDMP credentials from NetBackup-Java Administration
   Console for UNIX and Windows, an improper error message would
   appear if the NDMP add-on product was not installed on the master
   server.
--------------------------------------------------------------------------------
Etrack Incident = ET1088609

Description:
   Added support for the new SPR (SCSI3 Persistent Reservation)
   feature for disk.
--------------------------------------------------------------------------------
Etrack Incident = ET1053712
Associated Primary Etrack = ET1044565
Titan cases:  290-777-895

Description:
   During a hot catalog recovery, if the NetBackup database (NBDB)
   and the BMRDB database were recreated (a clean install) before
   recovering from the backup, the current online transaction
   log would not be able to be applied.  This was normal and expected
   behavior, however, the debug and progress logs did not give an
   adequate explanation of what occurred.  This issue has been fixed.
--------------------------------------------------------------------------------
Etrack Incident = ET1106710

Description:
   When upgrading from NetBackup 6.0 to NetBackup 6.5, Enterprise
   Media Manager (EMM) data for SnapVault and NearStore disk
   storage units were not upgrading correctly resulting in either
   a failed upgrade or failed backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1050155

Description:
   Device Configuration Cache would configure drives with no paths
   as enabled.  By default, any drives without a proper drive path
   (for example, only a SCSI pass-through path) should be configured
   as disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET1111547

Description:
   Memory was leaked in some error conditions during various disk
   storage unit operations.
--------------------------------------------------------------------------------
Etrack Incident = ET1112392

Description:
   Robotic drive 128 was treated as a negative number in tldd/tldcd
   robot.  For example, in a robot with 128 configured drives, the
   last drive always failed a mount request and the syslog showed
   tldd/tldcd trying to mount drive "-128".
--------------------------------------------------------------------------------
Etrack Incident = ET1099020

Description:
   When a drive from a back-level media server is deleted from
   the NetBackup-Java Administration Console on UNIX and Windows,
   the wrong drive can be deleted.

Workaround:
   If the drive indices do not match between the NetBackup 5.x media
   server and the NetBackup 6.x master server, then the best way of
   reliably and safely deleting the drive is by using the following
   variation of the tpconfig command on the NetBackup 5.x media server:
   
   tpconfig -delete -drive -asciiname <asciidrvname>
--------------------------------------------------------------------------------
Etrack Incident = ET1096195 ET1109567
Associated Primary Etrack = ET1109565

Description:
   This change addresses two problems.  nbstserv would
   intermittently crash while assembling duplication jobs,
   particularly on Windows X64 systems.  And a retried lifecycle
   duplication job would fail with a status 12 after the original
   job failed for any reason.
--------------------------------------------------------------------------------
Etrack Incident = ET1099115
Associated Primary Etrack = ET1073973
Titan cases:  281-138-275

Description:
   The start of job could be delayed because of a busy thread
   not yielding control.
--------------------------------------------------------------------------------
Etrack Incident = ET1101044
Associated Primary Etrack = ET1101043

Description:
   A problem existed where a multi-threaded program using emmlib
   would crash if its connection to nbemm was reset.
--------------------------------------------------------------------------------
Etrack Incident = ET1102615
Associated Primary Etrack = ET1104498

Description:
   The target of soft links were not being restored correctly
   from FlashBackup images.
--------------------------------------------------------------------------------
Etrack Incident = ET1085060

Description:
   The retry functionality in some of the storage unit functions
   in emmlib did not behave correctly and retries would fail for
   those functions.
--------------------------------------------------------------------------------
Etrack Incident = ET1106918

Description:
   Added code to determine if fibre transport (FT) is licensed in
   NBSL to avoid a situation where multiple threads wait unnecessarily
   to connect to the FT service that is not running when it is
   unlicensed.
--------------------------------------------------------------------------------
Etrack Incident = ET1094270

Description:
   NetBackup policies and clients are not updated in NOM.
   NOM is not receiving policy updates from NBSL.  Thus, any policy
   updates such as added, changed, deletes are not reflected in NOM.

Workaround:
   To avoid this issue, disable and enable data collection from NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET1098815

Description:
   If there are a large number of media servers connected to a
   master server, then NOM would receive a timeout while collecting
   service information if some the media servers were down or not
   responding.
--------------------------------------------------------------------------------
Etrack Incident = ET1082399

Description:
   An NetBackup pem core dump occurred when NBJM was terminated
   with active multi-streamed jobs but nbpem remained active.
--------------------------------------------------------------------------------
Etrack Incident = ET1052425 ET1076085

Description:
   A synthetic job that failed due to a media failure or other
   issue could cause a subsequent synthetic job for the same
   policy and client to fail.

Workaround:
   To avoid this issue, manually remove the catalog image for the
   failed synthetic job.
--------------------------------------------------------------------------------
Etrack Incident = ET1109705

Description:
   Changes were made to resolve an NBSL core dump issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1098718

Description:
   A change was added to parse invalid start and end times in case
   of incorrect db/jobs/try-files.
--------------------------------------------------------------------------------
Etrack Incident = ET1091111

Description:
   A change was added to ensure that NOM properly collects SkippedFiles.
--------------------------------------------------------------------------------
Etrack Incident = ET1065773

Description:
   The potential for crashing nbemm existed in some error cases
   when a value could not be properly initialized before the
   function returned.
--------------------------------------------------------------------------------
Etrack Incident = ET1102710
Associated Primary Etrack = ET1044565
Titan cases:  290-777-895

Description:
   On servers with multiple NICs, it was possible the second NIC
   would be set as the EMM server name.

Workaround:
   To avoid this issue, edit the files that name the EMM server.
--------------------------------------------------------------------------------
Etrack Incident = ET1082277
Associated Primary Etrack = ET916709
Titan cases:  280-859-612

Description:
   In certain circumstances the delay between bptm and bpdm sending
   their exit status to bpduplicate, and bpduplicate receiving it
   could be great enough where bptm and bpdm would shutdown before
   the transaction was complete. This caused bpduplicate to wait far
   past the end of the actual job, and eventually fail the entire job.
--------------------------------------------------------------------------------
Etrack Incident = ET1109757

Description:
   Backups would fail on HP-UX 11.31 RISC systems, and a core file
   from bpnbat_helper would also be left behind.
--------------------------------------------------------------------------------
Etrack Incident = ET1098045

Description:
   NetBackup 6.5 SharedDisk feature disk size is limited to 1TB
   on Solaris platforms. VTOC labeling on Solaris supports disks
   that are less than 1TB. For sizes greater than or equal to 1TB
   EFI labeling should be used. In NetBackup 6.5 VxFI does not
   support formating of EFI labeled disks. This fix adds support
   for EFI labeling on Solaris.  
--------------------------------------------------------------------------------
Etrack Incident = ET1082109

Description:
   A BMR report did not show data.
--------------------------------------------------------------------------------
Etrack Incident = ET1016904

Description:
   Potential free space was not updated correctly for Disk Staging
   Storage Units.
--------------------------------------------------------------------------------
Etrack Incident = ET997644

Description:
   If the hostname length was greater than 16 characters than the
   import and deport (used for backup and restore) of an EMC Symmetrix
   LUN would fail.
   
   This occurred because of an EMC bug, symmask discover hba -rename
   corrupts the entry in vcmdb database.
--------------------------------------------------------------------------------
Etrack Incident = ET1081452

Description:
   NBproxy crashes when getting the list of virtual machines for
   VMware and the call fails.

Additional Notes:
   If this occurs, you must restart nbproxy.
--------------------------------------------------------------------------------
Etrack Incident = ET1086598

Description:
   NearStore jobs would fail with a status 800 while all children
   jobs finished with a status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET1106385

Description:
   PEM would core dump when starting up and synchronizing with
   Job Manager jobs that were still active and have not reported
   status to PEM.
--------------------------------------------------------------------------------
Etrack Incident = ET1095098

Description:
   Changes were added to resolve PEM crashes and core dumps.
--------------------------------------------------------------------------------
Etrack Incident = ET1073905
Associated Primary Etrack = ET1073903

Description:
   Sybase was generating world-writable files.  Changes from Sybase
   have been added that resolve this security flaw by preventing ASA
   from writing world-writable files.
--------------------------------------------------------------------------------
Etrack Incident = ET1122374

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

Description:
   NDMP incremental backups that included two or more paths where
   the first path had no changed files were failing to verify.

Additional Notes:
   This fix prevents the problem from occurring with backups taken
   after this fix is installed.  Backups that were taken prior to
   this patch could still fail to verify.  The problem does not
   prevent a successful restore.
--------------------------------------------------------------------------------
Etrack Incident = ET1110736

Description:
   Instant Recovery policies do not validate for hardware array
   FIMs with a Linux master server.

Workaround:
   Ignore the policy validation failure.
--------------------------------------------------------------------------------
Etrack Incident = ET1112256

Description:
   Incremental hot catalog backups could hang.
--------------------------------------------------------------------------------
Etrack Incident = ET1121427

Description:
   The format of luns, in the case of lunmasking, would fail with
   errors such as the following:
   
   UDID##DGC##CLARIION##APM00062204899##60:06:01:60:1F:B0:18:00:09:
   75:34:97:A9:31:DC:11 failed with error [Rescan of device failed.]
--------------------------------------------------------------------------------
Etrack Incident = ET1117637

Description:
   The release reservation was failing because readReservation was
   being called on the block device instead of the raw device.
--------------------------------------------------------------------------------
Etrack Incident = ET1106502

Description:
   Machines that were deleted when they had last written media
   in a server group would leave dangling references in the
   database that caused the media to become unusable.
--------------------------------------------------------------------------------
Etrack Incident = ET1125017
Associated Primary Etrack = ET1110081
Titan cases:  220-104-676

Description:
   bpdbm could core dump when reading corrupted .f files.
--------------------------------------------------------------------------------
Etrack Incident = ET1119165

Description:
   Backups created from Instant Recovery VSS snapshot policies may
   not be able to be expired.
--------------------------------------------------------------------------------
Etrack Incident = ET1119910

Description:
   A library used for SCSI persistent reservation was not being
   linked to the library that provided some support functions.
--------------------------------------------------------------------------------
Etrack Incident = ET1128110

Description:
   A change was added to address a potential core dump issue in
   the nbemm process. This issue was not observed in the
   NetBackup 6.5 GA release.  It was discovered after the release,
   when using a new Microsoft compiler.
--------------------------------------------------------------------------------
Etrack Incident = ET1123618

Description:
   A disk online operation would fail if a NetBackup 6.5.1 disk was
   formatted using an oder version of NetBackup such as NetBackup 6.5.
--------------------------------------------------------------------------------
Etrack Incident = ET1125795
Associated Primary Etrack = ET1124254
Titan cases:  220-106-791

Description:
   Added a change to correct an nbpem core dump issue that occurred
   after installing 6.0 MP5.
--------------------------------------------------------------------------------
Etrack Incident = ET1130490

Description:
   An incorrect patch version was being shown in NOM. Added a new
   common function to send the correct patch version to NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET1126033

Description:
   After an SPR (SCSI3 Persistent Reservation) unmount operation,
   LUN Reservations were not being released after the backup was
   complete. A change was made the ensures reservations are released
   so that future backups are successful.  
--------------------------------------------------------------------------------
Etrack Incident = ET1090463

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

Description:
   A Policy Execution Manager (PEM) crash occurred after policies
   were deactivated and then activated.  To address this issue,
   an earlier fix that prevented memory leaks was removed to prevent
   a double free from crashing the Policy Execution Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET1129917

Description:
   Change was made to better filter the visibility of 'potential'
   storage servers.
--------------------------------------------------------------------------------
Etrack Incident = ET1132942

Description:
   A problem exists in the EMM library where a conversion from
   an Image Sequence might fail, but would still be reported
   as a success.
--------------------------------------------------------------------------------
Etrack Incident = ET1130566

Description:
   NetBackup Resource Broker (nbrb) would fail a SharedDisk request
   with an, "RB internal error," if ltid on one or more of the
   media servers went offline.
--------------------------------------------------------------------------------
Etrack Incident = ET1133603
Associated Primary Etrack = ET936099
Titan cases:  220-084-917 220-097-471

Description:
   The NetBackup Resource Broker (nbrb) would hang in some
   scenarios, and the backup jobs would remain queued.
--------------------------------------------------------------------------------
Etrack Incident = ET1107693
Associated Primary Etrack = ET1037368
Titan cases:  220-096-910 220-123-945 220-124-001 220-135-401 281-218-316
290-883-680

Description:
   Recomputing the due time of parent jobs when a child terminated
   caused the parent-child association to be lost.  Changed the startup
   sequence so that if the Job Manager (JM) is out of sync with
   pempersist, then the persistence is over-ridden by the active or
   non-active jobs reported by JM.
--------------------------------------------------------------------------------
Etrack Incident = ET1128957

Description:
   Incorrect error messages were being logged as specific error codes
   making it difficult for the user to determine the actual problem.
--------------------------------------------------------------------------------
Etrack Incident = ET861231

Description:
   Added a fix to correct an ENODEV issue that occurred on HP-UX IA64
   while importing a Snapshot.
--------------------------------------------------------------------------------
Etrack Incident = ET1062790
Titan cases:  290-791-634

Description:
   bpps would cause a Segmentation Fault (FLTBOUNDS) if the UID did
   not exist in S10 global zone.  This issue occurred only on
   Solaris systems.
--------------------------------------------------------------------------------
Etrack Incident = ET1059880

Description:
   Manually-submitted, immediate backups queue very slowly if there
   are no backups scheduled.

Workaround:
   To avoid this issue, create a policy that schedules a job to run
   in the future.  
--------------------------------------------------------------------------------
Etrack Incident = ET1128914
Associated Primary Etrack = ET1114286
Titan cases:  290-836-488

Description:
   When run against a successful Windows FlashBackup Image,
   bpverify would core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET1136472 ET1134253 ET1148528

Description:
   Adding checks for SCSI3 Persistent Reservation (SPR) that, when
   turning this off, the storage servers are valid to use LUN Masking.
--------------------------------------------------------------------------------
Etrack Incident = ET1130915 ET1131223

Description:
   On a Solaris platform, some backup jobs would fail while
   mounting a resource.
--------------------------------------------------------------------------------
Etrack Incident = ET1137735

Description:
   Currently, a shared disk is released after a backup is complete.
   NetBackup should not release reservation after a device is taken
   offline.
--------------------------------------------------------------------------------
Etrack Incident = ET1138740

Description:
   A race condition exists between the nbemm startup and shutdown
   sequence. When the sequence of starting and stopping nbemm is
   just right, nbemm can hang during shutdown with the following
   message.
   
   nbemm -terminate will not terminate nbemm in a timely fashion.

Workaround:
   If this issue occurs, use a hard kill (kill -9) to shut down nbemm.  
--------------------------------------------------------------------------------
Etrack Incident = ET1079753

Description:
   While logging to the DB Error logs, nbemm made a unsafe thread
   call that could potentially cause nbemm to crash. In NetBackup 6.5,
   the db error logging was turned off.  In addition, the command,
   bperror -disk and some disk reporting functionality was impacted.
   
   With this fix, nbemm error logging is turned on and the
   bperror -disk and disk error reports are available.  

Workaround:
   Generate application logs using vxlogiew for nbemm (fid: 111)
   for REM (oid: 219) to see disk volume related errors.
--------------------------------------------------------------------------------
Etrack Incident = ET1134817

Description:
   A cold catalog backup failed with the following error after the
   Sybase ASA database was rebuilt.
   
   NB database backup failed, a path was not found or is inaccessible
   
--------------------------------------------------------------------------------
Etrack Incident = ET1137031 ET1141201

Description:
   For a redirect restore of a SharePoint object to be successful,
   bprd must obtain the correct NetBackup version information from the
   media servers to determine if the SharePoint 2007 parameter values
   should be encoded.  
   
   Encoding is performed because the SharePoint 2007 object parameters
   may have spaces in them that causes command arguments to parse
   improperly.
--------------------------------------------------------------------------------
Etrack Incident = ET1138126

Description:
   On a Windows platform, if the media server hostname contained
   a small letter a backup or restore using EMC Symmetrix array
   would fail. For example, if the hostname is "Abcdef", then the
   backup fails, however if the hostname is "ABCDEF" it passes.
--------------------------------------------------------------------------------
Etrack Incident = ET1100611

Description:
   A change was made to fix an incorrect value that was displayed
   in the Job ID, Job type, and status fields in NOM. NOM should
   not show a jobId 0 value.  
--------------------------------------------------------------------------------
Etrack Incident = ET1124780

Description:
   Some servants in the NetBackup Service Layer (NBSL) were not
   being evicted in case of errors.
   
   NBSL has a health check mechanism that checks the health of
   each manager. If any manager has a problem like, an EMM call
   failed or the nbproxy went down for some reason, then that
   manager was marked as failed and would be evicted. For new
   managers implemented in NetBackup 6.5 such as disk, Media, Fat,
   License, this was not done and the new managers would not be
   evicted when there was some problem with DSM/FSM/proxy.
--------------------------------------------------------------------------------
Etrack Incident = ET1128031

Description:
   Performing a Shareddisk operation should reserve a LUN before a
   format operation. In the case of a UNIX reservation, it should be
   released before formatting as the reservation device depends on the

   storage stack.
--------------------------------------------------------------------------------
Etrack Incident = ET1137782
Associated Primary Etrack = ET1131135
Titan cases:  230-431-828

Description:
   Unable to connect to the NetBackup Service Layer Service on a
   particular host after selecting Media and Device Manager > Media.
--------------------------------------------------------------------------------
Etrack Incident = ET1133931

Description:
   A change was added to address some deadlock issues encountered in NBSL.
--------------------------------------------------------------------------------
Etrack Incident = ET1138854
Associated Primary Etrack = ET1135473
Titan cases:  240-628-279

Description:
   A CORBA communication error (195) would occur during a vault
   V_QUERY_BYPOOL. This error would cause the vault session to fail
   with an error 332.
--------------------------------------------------------------------------------
Etrack Incident = ET1131287

Description:
   IOR files written by the Job and Log managers were different than
   those sent to the NBProxy. This indicated that the proxy was not
   reading the manager's IOR.
--------------------------------------------------------------------------------
Etrack Incident = ET1139765
Associated Primary Etrack = ET1116213
Titan cases:  220-105-172

Description:
   A change was made that corrects a case where bpmedialist would
   exit without properly releasing its result set.  In an environment
   with a large amount of media, this "result set leak" produces
   noticeable growth in nbemm memory consumption over time.
--------------------------------------------------------------------------------
Etrack Incident = ET1137270

Description:
   When using SCSI3 Persistent Reservation (SPR), if the Array
   command line interface (CLI) was not installed on the host,
   then the "nbsharedisk release" commands would not release the
   reservation.
--------------------------------------------------------------------------------
Etrack Incident = ET1140241

Description:
   Added VxFI functionality to verify a reservation while offlining
   the LUN to ensure that the reservation was not changed.
--------------------------------------------------------------------------------
Etrack Incident = ET1139982

Description:
   If one host (host A) was holding the reservation and the other
   host (host B) tried to release it, when host A executed a
   "nbshareddsik release" command, it would return an error stating
   that the reservation was not released.  However, if the command
   was run a second time, the reservation would be released.
--------------------------------------------------------------------------------
Etrack Incident = ET1136304

Description:
   Threads that were allowed to be reused when an outbound CORBA
   call was made would cause a deadlock when calling emmlib.
--------------------------------------------------------------------------------
Etrack Incident = ET1141863

Description:
   A logic error in bpduplicate was preventing it from sending an
   exit status acknowledgment to bpdm.  bpdm would wait a few minutes
   and then would give up, causing it to print an error in the logs
   when there actually was no error. A false positive was produced.

Additional Notes:
   There is no actual error and this issue happens only after the job
   is already successful.
--------------------------------------------------------------------------------
Etrack Incident = ET1109608
Associated Primary Etrack = ET1052591
Titan cases:  240-578-685

Description:
   Upon an Oracle Duplication to an alternative client, Recovery
   Manager (RMAN) failed to restore all of the data. The data was
   being restored, and each time a restore was run, a little more
   data would be restored. However RMAN passed an ORA-07445.
   
   A change has been made that ensures an ORACLE restore to
   an alternate client passes.
--------------------------------------------------------------------------------
Etrack Incident = ET1141191

Description:
   A change was made to ensure that NBSL can connect to the SAN client.
--------------------------------------------------------------------------------
Etrack Incident = ET1141195
Associated Primary Etrack = ET1117970
Titan cases:  220-102-189

Description:
   When vault tried to suspend media that was given an application
   cluster name instead of the active node name, the operation failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1144319
Associated Primary Etrack = ET1142577
Titan cases:  311721921

Description:
   NetBackup 6.5 was not using the NUMBER_DATA_BUFFERS_DISK entry.
--------------------------------------------------------------------------------
Etrack Incident = ET1141844

Description:
   A change has been made to address deadlock issues in NBSL.
--------------------------------------------------------------------------------
Etrack Incident = ET1139701

Description:
   A parent job can remain active more than 24 hours after both
   children jobs completed.

Workaround:
   If a failed multistreamed job fails and is manually restarted,
   do not attempt to restart the resulting job.
--------------------------------------------------------------------------------
Etrack Incident = ET1145202

Description:
   When using the LUN reserve command an issue with a corrupt DMP
   cache resulted in two paths for the DMP node (Disk_7) when there
   should have been only one path.  When obtaining the UDID a
   corrupt DMP cache produced an invalid path that was used as the
   active path to issue the reservation instead of the correct path.  
--------------------------------------------------------------------------------
Etrack Incident = ET1139621

Description:
   Bpduplicate was not setting the affinity ID when making a media
   reservation request for a spanned duplication.
--------------------------------------------------------------------------------
Etrack Incident = ET1117736

Description:
   Changes have been made to correct a core file that was generated
   because of a login failure.  This random failure was seen using the
   NetBackup-Java Administration Console and it did not affect Windows
   platforms.  
--------------------------------------------------------------------------------
Etrack Incident = ET1146745
Associated Primary Etrack = ET1145215
Titan cases:  220-118-313

Description:
   The expiration manager expires more than the expected number of images
   if any of the images have fragment(s) that are greater than or equal
   to 2GB.
   
   1. After a volume or disk pool gets a HWM (High Water Mark) event and
   after the expiring images have passed the try_to_keep date (first pass
   of expiration), the volume size should decrease to the LWM (Low Water
   Mark).
   
   If the volume size does not decrease to the LWM and if any of the
   volume's total_capacity or free_capacity is greater than or equal to
   2GB, then the expiration manager MAY not attempt to expire any of the
   other images even though they were marked as "eligible_for_expiration".
   
   This may cause volumes to not go below the HWM or the LWM even though
   there are "eligible_for_expiration" images.
   
   2. If any of the eligible_to_expire image fragment sizes are greater
   than or equal to 2GB, then the expiration manager may expire more than
   the required images at a HWM event for a volume in an attempt to get
   the volume size below the LWM.
--------------------------------------------------------------------------------
Etrack Incident = ET1130840

Description:
   Consider a scenario of a duplicate job of multiple images that
   have a disk volume in common. Allocation for that disk volume
   was not held until the job was done using that disk volume if
   one of the images spans from that disk volume to another. This
   would make the job deadlock against itself.
--------------------------------------------------------------------------------
Etrack Incident = ET1146673
Associated Primary Etrack = ET1143471
Titan cases:  281-221-795

Description:
   Changing a machine's master server could leave invalid
   references in the database.  The server must be removed from the
   database before it can be used with a different master server.
--------------------------------------------------------------------------------
Etrack Incident = ET1145768

Description:
   nbemm takes a long time to shutdown when it is heavily loaded.
   In a cluster environment, the cluster is unable to offline
   under such circumstances.
   
   nbemm waits until the Resource Event Manager processes all requests
   to update the disk capacity. This can take a long time based on the
   responsiveness of Disk Service Manager.

Workaround:
   To avoid this issue, issue a hard kill.
--------------------------------------------------------------------------------
Etrack Incident = ET1145871
Associated Primary Etrack = ET1137937
Titan cases:  220-108-064

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

Description:
   An exception caught during disk activities may cause memory
   corruption.
--------------------------------------------------------------------------------
Etrack Incident = ET1140439

Description:
   The Snapshot wizard user interface did not have the capability
   to clear the VM cache.
--------------------------------------------------------------------------------
Etrack Incident = ET1147391

Description:
   bpmedia would clear the IMPORTED and MEDIA_FULL bits when you
   freeze, unfreeze, suspend, or unsuspend media.
   
   
--------------------------------------------------------------------------------
Etrack Incident = ET1146512

Description:
   In High Availability (HA) with VCS 5.0 (secure), the NetBackup
   Administration Console was showing the following error message.
   
   6006:Unable to connect server.
--------------------------------------------------------------------------------
Etrack Incident = ET1149222

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

Description:
   Attempting to format multiple UDID's using the
   "nbsharedisk format" command failed with the following error.
   
   "Generic error for format failure at VM"
--------------------------------------------------------------------------------
Etrack Incident = ET1150310

Description:
   The automatically scheduled bpdbm Q_IMAGE_DELETE image cleanup
   query would produce a core dimp in the is_catalog_backup_configured()
   function when the /usr/openv/netbackup/db/class directory contained
   a file or folder that was not a valid policy folder.
--------------------------------------------------------------------------------
Etrack Incident = ET1140798

Description:
   An import or deport using nbsharedisk of an EMC symmetrix LUN fails
   on the SUSE 9 Linux platform.  In addition, a TimeFinder clone backup
   fails. This issue occurs because the gethostbyname_r funtionality
   does not work if a host name with a short name is present in
   "/etc/hosts" file.  

Workaround:
   To resolve this issue, replace the following entry in the file
   "/etc/nsswitch.conf":
      -hosts:  files nis dns
   
   With the following entry:  
       hosts:  nis dns files
--------------------------------------------------------------------------------
Etrack Incident = ET1150834

Description:
   The media fetch operation initiated from the NetBackup Administration
   Console was taking more than 20 seconds, which was the default timeout
   value for a connection timeout.  This resulted in media not appearing
   in the console.

Workaround:
   If you encounter this issue, increase the time-out value from 20
   seconds to 40 seconds on the NetBackup Administration Console.
--------------------------------------------------------------------------------
Etrack Incident = ET1143453
Associated Primary Etrack = ET1136246
Titan cases:  240-637-777

Description:
   The Policy Execution Manager (PEM) ignores all streams that follow
   two consecutive NEW_STREAM directives in the file list.  A changed
   was made to the PEM to remove consecutive NEW_STREAM directives from
   the include file list prior to submitting the job to the Job Manager.
   This enables the job to run without having to modify the include file
   list.  In addition, it backs up all of the files specified in the
   include file list.

Workaround:
   To resolve this issue, remove any extra NEW_STREAM directives from
   the file list.
--------------------------------------------------------------------------------
Etrack Incident = ET1152707

Description:
   Canceled SharedDisk jobs would not always release the disk volume.
--------------------------------------------------------------------------------
Etrack Incident = ET1154516
Associated Primary Etrack = ET1141889
Titan cases:  240-624-463

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

Description:
   Hot catalog backups would fail with a status 190 when using a remote
   EMM server and incremental hot catalog backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1133898

Description:
   Certain files were restoring incorrectly because they were truncating
   because of zero data.  A change was made to insure the zero data is
   properly restored.
--------------------------------------------------------------------------------
Etrack Incident = ET1155366

Description:
   Incremental FlashBackups with mount points that have no changed files
   or folders could fail when the backup starts to process the next mount
   point or attempts to validate the image.
--------------------------------------------------------------------------------
Etrack Incident = ET1155556
Associated Primary Etrack = ET1152563
Titan cases:  281-229-451

Description:
   Backups to Disk Staging Storage Units (DSSU) in NetBackup 6.5 would not
   work properly when using a cluster configuration.  For more information
   about this issue refer to the following TechNote on the Symantec
   Support Web site.
   
     http://entsupport.symantec.com/docs/293873
--------------------------------------------------------------------------------
Etrack Incident = ET1155361

Description:
   In NetBackup 6.5 GA, the mmcrawl process would consume more than 1.4GB
   of memory.  This issue meant that mmcrawl could not be run on a
   Windows 32-bit system because this type of system is limited to 2GB of
   virtual space for processes and applications.
--------------------------------------------------------------------------------
Etrack Incident = ET1151172

Description:
   A raw SNC Oracle backup failed with an fopen () error.  The owner and
   group ID of the primary resource, after the backup/snapshot, would get
   reverted back to superuser. Similarly, the alternate resource that
   resulted out of the snapshot did not have the similar owner and group
   ID as that of the primary one.
--------------------------------------------------------------------------------
Etrack Incident = ET1152716

Description:
   bpdm would not respond to terminate signals or terminate events.  This
   kept the cluster software from stopping bpdm during long deletes.  In
   addition, nbdelete on the master server could not remotely interrupt a
   bpdm process.
   
   A change was made to address both of these issues.
--------------------------------------------------------------------------------
Etrack Incident = ET1153439

Description:
   Phase 1 import fails. Import aborts (bpdm core dump).
   
   A phase 1 import would fail because of an incorrect header file that
   was not null-terminated being read. bpdm would core dump and cause the
   remaining images to not be imported.
--------------------------------------------------------------------------------
Etrack Incident = ET1159304

Description:
   The NetBackup-Java Administration Console displayed the wrong number
   of media after a refresh operation.
--------------------------------------------------------------------------------
Etrack Incident = ET1145768

Description:
   An issue exists in NetBackup where you are unable to offline the
   NetBackup resources with a VCS cluster because nbemm could not be
   terminated.

Workaround:
   To resolve this issue, kill the nbemm process.
--------------------------------------------------------------------------------
Etrack Incident = ET1141469

Description:
   VMWare-related changes were added in the NetBackup Service Layer
   (NBSL) to improve performance.
--------------------------------------------------------------------------------
Etrack Incident = ET1161183
Associated Primary Etrack = ET1137130
Titan cases:  290-857-049

Description:
   There is a problem with the NetBackup upgrade process when upgrading
   (from NetBackup 5.x to NetBackup 6.5) in a NetBackup cluster
   environment that results in the EMM database being created in
   /usr/openv, rather than on the shared disk.  

Workaround:
   To determine if this issue affects you, refer to the following TechNote
   on the Symantec Support Web site.
   
   http://entsupport.symantec.com/docs/293034
--------------------------------------------------------------------------------
Etrack Incident = ET1160463

Description:
   The -L option for the bpverify command creates an empty log file with
   no information. Normally it creates a progress log file in the path
   that is supplied.

Workaround:
   If the full path is supplied rather than just a filename, it should
   create the file and populate it where you direct.
--------------------------------------------------------------------------------
Etrack Incident = ET1158609

Description:
   The NetBackup Policy Execution Manager (NBPEM) would crash if a
   job was restarted whose schedule had been deleted from the policy.
--------------------------------------------------------------------------------
Etrack Incident = ET1159821

Description:
   A change was made to resolve an issue with volume cleanup that caused
   bptm to crash under certain circumstances.
--------------------------------------------------------------------------------
Etrack Incident = ET1163509
Titan cases:  281-245-969

Description:
   If a user "loses" a drive path (for instance, the OS deletes it for
   some reason) and the user tries to start ltid, ltid would fail to
   initialize because the drive path was invalid.  Instead ltid will now
   DOWN the drive/path and continue its initialization.
--------------------------------------------------------------------------------
Etrack Incident = ET1163509
Titan cases:  281-245-969

Description:
   If a user "loses" a drive path (for instance, the OS deletes it for
   some reason) and the user tries to start ltid, ltid would fail to
   initialize because the drive path was invalid.  Instead ltid will now
   DOWN the drive/path and continue its initialization.
--------------------------------------------------------------------------------
Etrack Incident = ET1149056

Description:
   Processes would hang when an interrupt occurred during some socket
   writes.
--------------------------------------------------------------------------------
Etrack Incident = ET1163626
Associated Primary Etrack = ET1162799
Titan cases:  281-241-360

Description:
   Attempting to restore a Basic DSU backup from a different media
   server would fail.
--------------------------------------------------------------------------------
Etrack Incident = ET1162837

Description:
   Changes were made to address an issue that caused nbstserv to core
   dump while processing images.
--------------------------------------------------------------------------------
Etrack Incident = ET1162890

Description:
   Restore for legacy Exchange would fail because the SNAP_TIME
   parameter was non-zero in the image header.  The restore failed
   because nbwin was reading the image as being a snapshot image. If the
   image was a snapshot image (SNAP_TIME was non-zero), nbwin would not
   supply a valid TEMP_DIR parameter to tar32.
--------------------------------------------------------------------------------
Etrack Incident = ET1163390

Description:
   Bpdm and bptm would not seek when performing a Windows FlashBackup,
   single-file restore.  The restore would hang.
--------------------------------------------------------------------------------
Etrack Incident = ET1167359

Description:
   The ability to seek to a new image location was not allowed for
   FlashBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET1169734

Description:
   A change was added to correct a potential EMM core dump issue that
   would occur during a createMedia() operation.
--------------------------------------------------------------------------------