NB 6.5 Pack NB_6.5.3 README                                    November 10, 2008
Requirement: NB_CLT_6.5.3
Corequirement: NB_BMR_6.5.3
Directives: NBDB_Upgrade NBDB_Recover
SeqNumber: 20080731
================================================================================
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.3_<6 digit number>.tar must be installed before this
       Release Update is installed.

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

    -- Installation of this Release Update requires version 1.6.4.14.4.2
       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 patches and
       could result in a patch not being delivered.  When upgrading or patching
       client software, any agent software must be upgraded or patched to the
       latest or matching level at the same time as the client software.

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



I.    NEW FEATURES AND PLATFORM PROLIFERATIONS
        Platform Proliferations
        New Features and Enhancements
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.3
        Release Update History
           NB_6.5.2
           NB_6.5.1



============================================
I.  NEW FEATURES AND PLATFORM PROLIFERATIONS
============================================
This section contains subsections that describes the new UNIX and Windows
features and platform proliferations that are being released in NetBackup 6.5.3.
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 platform proliferations were announced in the NetBackup 6.5.3.

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

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

+  Added support VCB 1.5 support for VMWare.




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

+  The release adds support for the following Windows platforms.
    - NetBackup media server support for Windows 2008 X64
    - NetBackup client support for Windows 2008 X64
    - NetBackup client support for Windows 2008 X86

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

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

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

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

+  Support has been added for the following Linux releases for SharedDisk media
  servers:
    - Red Hat 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 Release Update contains the following new features and enhancements.  For
more information about any new feature contained in this release, refer to the
NetBackup 6.5.3 Documentation Updates document contained in the following
TechNote on the Symantec Support Web site.

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

+  NetBackup Exchange Granular Recovery

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

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

  The following parameters were added since 6.5.

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

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

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

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

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

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

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

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

     Default:  8 gigabytes.  Syntax:  MIN_GB_SIZE_PER_DUPLICATION_JOB 8

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

       Syntax:  MAX_GB_SIZE_PER_DUPLICATION_JOB 25

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



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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

+  SharedDisk storage option
  The SharedDisk documentation in the Veritas NetBackup 6.5.2 Documentation
  Updates document packaged with this release supercedes 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
  WMware.

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

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




==================
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:
-------------------------
+  Windows 2008 can only be administered from a remote system, the user
  interface will not allow local administration.  

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

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

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

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

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

+  (ET1218121) An issue exists that causes backups of Distributed File
  System Replication (DFSR) data on Windows 2003 R2 systems using
  NetBackup 6.5 or 6.5.x to fail even though a NetBackup Status Code 0
  (successful) is received.  A documented workaround exists in
  TechNote 290900 on the Symantec Support Web site. If you have already
  implemented this workaround, please continue to monitor the TechNote for
  any changes that may be added.

  See, http://entsupport.symantec.com/docs/290900


Installation, upgrade, and cluster issues:
------------------------------------------
+  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

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

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

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



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

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

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

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

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

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

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

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

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



NetBackup Database Agent issues:
--------------------------------
+  The following items pertain to the new Exchange Granular Recovery feature
  for this release.

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

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

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

  - The following table shows the supported NetBackup media servers and which
    of these platforms support NBFS:
   
      Supported Media Server                Support for NBFS
      AIX 5L...............................       YES
      HP-UX HP 9000 PA-RISC................       YES
      HP-UX HP Integrity (IA-64)...........       YES
      Novell Open Enterprise Server Linux..       NO
      RedFlag Linux Data Center............       NO
      RedHat Enterprise Linux..............       YES
      Solaris Sparc........................       YES
      Solaris x86/x64......................       NO
      SUSE Linux Enterprise Server.........       YES
      Tru64................................       NO
      Windows 2000.........................       NO
      Windows 2003 x86/x64.................       YES
      Windows 2008.........................       NO

  - The following table shows the supported Disk Storage units for Exchange
    granular-enabled backup policies and which of these platforms support
    granular-browse:
   
      Supported Media Server      Granular-browse Support
      BasicDisk..................     YES
      AdvanceDisk................     YES
      NearStore..................     NO
      OpenStorage................     NO
      PureDisk...................     YES
      ShareDisk..................     NO
      SnapVault..................     NO

+  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.
  -  Exchange 2007 Recovery Storage Group
     In NetBackup 6.5.1, the procedure to restore to the Exchange 2007 recovery
     storage group (RSG) is to specify the RSG name as the redirected
     destination. In a future release, redirection to the RSG will be automated
     and will not have to specify a name.

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



Storage-related issues:
-----------------------
+  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)  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.

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

+  (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.)
-------------------------------------------------------------------------------
+  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:
-------------------------
+  ** (ET1391268)  A data loss issue exists with calendar-based schedules that
  have a configured window that spans midnight and then goes active after
  midnight. The issue can cause a client backup, that is suppose to run in the
  next open window, to be skipped without any notification, thus resulting in a
  data-loss situation. This issue can occur in a NetBackup server or Enterprise
  server.

  For information on how to determine if you may be impacted by this issue and
  for a work-around, refer to the following TechAlert on the Symantec Support
  Web site.

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

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



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.3_<6 digit number>.tar and
  NB_6.5.3_<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.3_<6 digit number>.tar has the client binaries and
    NB_6.5.3_<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.3_<6 digit number>.tar into the /tmp directory
    and download and extract the NB_BBS_6.5.2_<6 digit number>.tar
    into the /tmp directory.


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

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

       NB_CLT_6.5.3 will create the files:
       VrtsNB_CLT_6.5.3.README
       VrtsNB_CLT_6.5.3.<platforms>.tar.Z
       VrtsNB_CLT_6.5.3.preinstall
       VrtsNB_CLT_6.5.3.postinstall
       VrtsNB_CLT_6.5.3.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 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 5.x release then it is important that you understand that the
   existing NetBackup databases must be in a consistent state prior to beginning
   the upgrade. Information and tools to assist you in determining the current
   state of your database, as well as instructions to help you address any
   inconsistencies that you might discover can be viewed on the NetBackup Upgrade
   Portal, a part of the Symantec NetBackup Support Web site.

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

 - Do not use a NetBackup GUI running on any other host to monitor the
   NetBackup jobs/processes/daemons/devices on the host 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 GUIs running on remote
   systems which are accessing any host during pack application.


For Release Update installation on 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
  (perform steps 1 through 3 below).

3) Install this Release Update on the active node of the cluster (perform
  steps listed below).

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

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

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


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.3 and NB_CLT_6.5.3 Release Update binaries.

       cd /tmp
       /bin/sh NB_update.install

  NOTE: Selecting the server Release Update will automatically install the
        client Release Update if the client (CLT) .Z file and the README exist
        in the installation directory. The server install will fail if the
        (CLT) .Z file and the README are not present and the CLT 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 will prompt you to restart daemons.
  Otherwise, after the update installation has completed, run:

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

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

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



=========================
V. UNINSTALL INSTRUCTIONS
=========================
Note:  This will ONLY uninstall the Release Update from your local machine.

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

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

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

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

3) Run the un-install script:

    ./NB_update.uninstall

4) Verify that the updatte 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.3
--------
1275559 1302929 1302749 1317013 1317008 1317006 1317202 1317047 1276489 1318091
1289921 1322984 1364407 1364422 1322803 1364661 1373019 1383374 1382658 1383586
1383584 1184889 1276613 1382632 1383839 1383438 1383440 1383434 1383442 1383733
1383750 1383540 1384029 1375483 1383736 1383527 1383523 1384879 1385083 1385111
1386294 1383757 1384675 1383511 1385061 1382599 1376805 1383782 1383502 1383497
1383499 1384270 1386057 1386060 1383811 1383808 1382683 1384822 1386064 1386062
1386073 1383727 1383766 1386069 1384960 1386075 1386077 1384019 1386065 1386070
1387046 1383743 1384952 1387039 1383643 1384946 1384943 1388149 1384948 1383744
1386199 1384909 1389088 1374330 1388180 1383756 1388192 1382684 1383404 1390335
1383742 1383761 1391168 1382623 1391109 1383763 1394025 1383630 1392132 1388236
1384020 1395057 1384919 1383792 1383772 1393919 1384032 1384023 1384966 1395393
1383506 1396153 1391110 1397984 1399794 1393810 1393798 1397604 1398627 1388000
1387827 1393793 1396248 1402394 1396112 1395233 1402922 1403920 1405290 1402967
1320530 1398698 1396083 1392668 1409131 1409154 1411251 1411776 1410874 1412331
1408807 1412417 1413338 1411302 1413269 1410786 1413572 1385085 1414212 1412557
1415612 1413649 1401482 1413567 1415683 1414541 1416768 1421025 1425093 1424266
1423453 1425900 1425285 1428096 1423583 1426958 1427064 1429629 1430825 1428794
1431220 1428632 1432786 1431217 1431957 1432152 1432733 1431905 1436492 1436738
1439637

NB_BBS_6.5.3
------------
1386047 1383479

NB_BMR_6.5.3
------------
1289330 1385881

NB_CLT_6.5.3
------------
1275559 1302929 1302749 1317013 1317008 1317006 1317202 1317047 1276489 1318091
1289921 1322984 1364407 1364422 1322803 1364661 1373019 1383374 1382658 1383586
1383584 1184889 1276613 1382632 1383839 1383438 1383440 1383434 1383442 1383733
1383750 1383540 1384029 1375483 1383736 1382523 1383527 1383523 1384879 1385083
1385111 1386294 1383757 1384675 1383511 1385061 1382599 1384892 1376805 1383782
1383502 1383497 1383499 1384270 1386057 1386060 1383811 1383808 1382683 1384822
1386064 1386062 1386073 1383727 1383766 1386069 1384960 1386075 1386077 1384019
1386065 1386070 1387046 1383743 1384952 1387039 1383643 1384946 1384943 1388149
1384948 1383744 1386199 1384909 1389088 1374330 1388180 1383756 1388192 1382684
1383404 1387984 1390335 1383742 1383761 1391168 1382623 1391109 1383763 1394025
1383630 1392132 1388236 1384020 1395057 1384919 1383792 1383772 1393919 1384032
1384023 1384966 1395393 1383506 1396153 1391110 1397984 1399794 1393810 1393798
1397604 1398627 1388000 1387827 1393793 1396248 1402394 1396112 1395233 1402922
1403920 1405290 1402967 1320530 1398698 1396083 1392668 1409131 1409154 1411251
1411776 1410874 1412331 1408807 1412417 1413338 1411302 1413269 1410786 1413572
1385085 1414212 1412557 1415612 1413649 1401482 1413567 1415683 1414541 1416768
1421025 1425093 1424266 1423453 1425900 1425285 1428096 1423583 1426958 1427064
1429629 1430825 1428794 1431220 1428632 1432786 1431217 1431957 1432152 1432733
1431905 1436492 1436738 1439637

NB_DB2_6.5.3
------------
1388132

NB_DMP_6.5.3
------------
1384031

NB_INX_6.5.3
------------
1404905 1416672

NB_JAV_6.5.3
------------
1316222 1316255 1316257 1383469 1386728 1388080 1393518 1400256

NB_LOT_6.5.3
------------
1318437

NB_LUA_6.5.3
------------
1380529

NB_NOM_6.5.3
------------
1383447 1384380 1390067 1391157 1391161 1395092 1399345 1409923 1409925 1423226


NB_SAP_6.5.3
------------
1227447 1386537 1227458 1411527

NB_SMU_6.5.3
------------
1387861 1387867

NB_SNC_6.5.3
------------
1383582 1383429 1382596 1383498 1384025 1394039 1395089 1383512 1401373 1398467
1410597

NB_VLT_6.5.3
------------
1383258 1385764 1386756 1385614 1386760 1386763 1386750 1396286 1402907 1404850





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



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

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

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

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

   http://entsupport.symantec.com/docs/308583
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------