NB_6.5.4.Winx64_CD.exe provides a media refresh to 6.5.4 for Veritas NetBackup (tm) servers and clients only on Windows 2008 and Windows 2008 Server Core x64 platforms for NEW INSTALLS, and for NEW INSTALLS of Windows 2003 x64 platforms

Article:TECH71299  |  Created: 2009-01-09  |  Updated: 2011-02-04  |  Article URL http://www.symantec.com/docs/TECH71299
Article Type
Technical Solution



Issue



NB_6.5.4.Winx64_CD.exe provides a media refresh to 6.5.4 for Veritas NetBackup (tm) servers and clients only on Windows 2008 and Windows 2008 Server Core x64 platforms for NEW INSTALLS, and for NEW INSTALLS of Windows 2003 x64 platforms


Solution



NB 6.5GA Pack NB_6.5.4 README                                       May 11, 2009
================================================================================

NOTE:  Do not install this CD image for existing NetBackup Windows x64 Server or Client installations as this CD is for NEW NetBackup Installs only.  This CD image SHOULD NOT be used as a Release Update to perform an upgrade.  Please install the NetBackup 6.5.4 Windows x64 Release Update.

This CD image provides support for Veritas NetBackup (tm) servers and clients
only on Windows 2008 and Windows 2008 Server Core x64 platforms, and for new
installs on Windows 2003 x64 platforms. It also contains fixes for NetBackup
Add-on products, Database Agents, and NetBackup Encryption that are contained
in the 6.5.4 Release Update. This CD image is intended to be used to support
new installations of NetBackup 6.5.4.  This CD image should not be used as a
Release Update to perform an upgrade. If you want to upgrade to NetBackup 6.5.4
from a previous version of NetBackup, you should install the proper
NetBackup 6.5.4 Release Update.



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


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

    -- There are no dependencies for this CD image.



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




============================================
I.  NEW FEATURES AND PLATFORM PROLIFERATIONS
============================================
The following is a comprehensive list of the platform proliferations that were
added in this CD image of NetBackup. (This list contains both UNIX and
Windows proliferations.) For additional information about platform
proliferations, see the following TechNote on the Symantec Support Web site:

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

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

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


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

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

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


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

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

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

+  Added support VCB 1.5 support for VMWare.



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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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



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

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

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

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

+  New Database Agent features and enhancements

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

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

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

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

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

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

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

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

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

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

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

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

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

  - Instant recovery log truncation option
  - Granular cataloging option

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

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

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

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

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

  - Granular restores can be redirected to a file system.

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

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

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


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

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

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

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

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

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


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

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


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

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

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

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

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

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

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

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

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

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

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

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


+  Storage Lifecycle Policy Features and Enhancements

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

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

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

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

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

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

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

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

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

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

    A. If duplication jobs are to run at the same time as backup jobs, or if
       you need enough concurrent duplication jobs to keep all of the
       destination tape drives spinning (see the previous paragraph), then one
       of the following parameters must be used to limit the size of the
       duplication jobs:
       - MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB
       - MIN_GB_SIZE_PER_DUPLICATION
       - MAX_GB_SIZE_PER_DUPLICATION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


+  NOM Features and Enhancements

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

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

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

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

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

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

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

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

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

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

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


+  New Tools and Supportability

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

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



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

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

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

+  For restores of individual items with Exchange Server or SharePoint Server,
  note the following:

  - You must be running Windows 2008 or Windows 2003 R2. Information about how
    to upgrade Windows Server 2003 with Service Pack 1 to Windows Server 2003 R2
    is available from the following Microsoft web site:
       http://support.microsoft.com/kb/912309

  - For Windows 2008, you must enable Services for Network File System under
    File Services. See the NetBackup 6.5.3 Documentation Updates for more
    information.

+  A new TechNote is available with updated information for using Granular
  Recovery with SharePoint Server 2003/2007. This TechNote is available on the
  Symantec Support Web site:
 
     http://entsupport.symantec.com/docs/305549

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

  The following parameters were added since 6.5.

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

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

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

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

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

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

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

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

     Default:  8 gigabytes.  Syntax:  MIN_GB_SIZE_PER_DUPLICATION_JOB 8

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

       Syntax:  MAX_GB_SIZE_PER_DUPLICATION_JOB 25

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



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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  BasicDisk storage units and Windows UNC

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

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

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

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

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

+  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



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

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

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

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

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

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

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

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


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

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

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

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

     * VTL
     * OpenStorage
     * AdvancedDisk with standalone disk or NFS

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

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

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

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

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

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

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

  Service and Support

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

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

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



==================
II.  KNOWN ISSUES
==================
This section contains a list of known issues with this CD image. 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
- Certified for Windows 2008 issues
- Installation, upgrade, and cluster issues
- NetBackup Access Control issues
- NetBackup Database Agent issues
- Storage-related issues
- NetBackup user interface issues
- General NetBackup issues
- NetBackup Snapshot Client (and NetBackup Hyper-V)
- Bare Metal Restore (BMR) issues
- Localization issues
- General Documentation issues



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

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

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

+  (ET1320943) FAT32 file systems are not supported on Windows x86 and x64.

+  (ET1268229) The backuptrace.exe executable fails on Windows AMD64 systems.
  On AMD64 systems, when using the backuptrace command, add the following
  option with any other options that you are using.  This ensure that the
  registry will not be called and the command will function properly.

  -install_path <path> (This is the directory path where NetBackup resides.)

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

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

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

+  (ET1233823) There is a problem regarding backing up Windows 2008 encrypted
  files.  This is a Microsoft issue. A NetBackup fix will likely occur in a
  future 6.5 release. For now, to avoid this issue, run NetBackup as
  Administrator and not as a Backup Operator.

+  ** (ET1220681) This issue applies to all 64- and 32-bit Windows platforms,
  using Microsoft System Provider.

  When using the Microsoft System Provider, any Instant Recovery snapshot
  backups relative to the backup used for restore that are kept online should
  remain valid after attempting a Point-in-Time rollback from any of the online
  snapshots. However, attempting a Point-in-Time rollback from any of the
  online snapshots can cause all of the other online snapshots, taken from the
  same volume to become invalid. This issue can occur when the snapshot "shadow
  copy device name" is changed after a rollback

  To avoid this issue, the user should use CopyBack to restore data from an
  online Instant Recovery Snapshot.  A fix for this issue will be included in a
  future Release Update of NetBackup 6.5.

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

+  (ET1534457) If RHEL5.3 Media (CDs) are used for shared resource tree (SRT)
  creation, the SRT creation fails with an error message that is similar to
  the following:

  V-125-380 /var/tmp/bmrmediaDb1K6p/.discinfo(2): expected "Red Hat Enterprise
  Linux Server 5", got "Red Hat Enterprise Linux Server 5.3"
  The loaded media is not correct ... please try again.
  Unmounting media ... ok.

  One workaround for this issue is to use the RHEL5.0, 5.1, or 5.2 operating
  system media to create a shared resource tree (SRT). You can use SRTs to
  restore an RHEL5.3 client.

  A second workaround for this issue:
  On the BMR Boot server, open the /usr/openv/var/global/createsrt.conf file
  and search for the string, Red Hat Enterprise Linux Server 5.  Replace all
  the occurrences of this string with the following string, Red Hat Enterprise
  Linux Server 5.3.  That should enable the creation of RHEL5.3 SRTs.

  NOTE:  This workaround disables the ability to create RHEL5.0/5.1/5.2 SRTs.
         Because RHEL5.3 introduces new device drivers that were not a part
         of the default kernel in RHEL5.2, Symantec recommends that you use this
         workaround to create a RHEL5.3 SRT for restoring RHEL5.3 clients.



Certified for Windows 2008 issues:
----------------------------------
+  NetBackup installs the files noted below that do not have file properties
  that contain Company, Product Name, and Product Version.

  The file noted below is installed with the application but is no longer
  used. This file will be removed in the next major release of the
  application.
    C:\Program Files\Veritas\NetBackup\bin\goodies\supportnow.exe

  The file noted below is installed with the application. The fix to this
  issue is committed to be incorporated in the next major release of NetBackup.
    C:\Program Files\Veritas\NetBackup\bin\vxace_3mfc.dll

+  NetBackup uses various third-party files and tools (listed below) that do
  not include or create requestedExecutionLevel tags.
    C:\Program Files\Veritas\NetBackupDB\java\java.exe
    C:\Program Files\Veritas\NetBackupDB\java\javaw.exe
    C:\Program Files\Veritas\NetBackupDB\java\keytool.exe
    C:\Program Files\Veritas\NetBackupDB\java\policytool.exe
    C:\Program Files\Veritas\NetBackupDB\java\rmid.exe
    C:\Program Files\Veritas\NetBackupDB\java\rmiregistry.exe
    C:\Program Files\Veritas\NetBackupDB\java\tnameserv.exe
    C:\Program Files\Veritas\NetBackup\bin\uconv.exe

+  NetBackup includes a limited number of files (listed below) that do not
  include or create requestedExecutionLevel tags. These executables are a
  special case. They are not intended to be run on Windows Server 2008. These
  binaries are used only in a limited set of circumstances when connecting to
  an older version of NetBackup that runs on an older OS platform. Under those
  specific circumstances NetBackup will push install these binaries to the
  system that is running the older OS.  This is done to allow for back-level
  compatibility for NetBackup.  
    C:\Program Files\Veritas\NetBackup\bin\goodies\misc\PC\WindowsNT
         \bemcmd50.exe
    C:\Program Files\Veritas\NetBackup\bin\goodies\misc\PC\WindowsNT
         \bemcmd51.exe
    C:\Program Files\Veritas\NetBackup\bin\goodies\misc\PC-IA64\WindowsXP
         \bemcmd50.exe
    C:\Program Files\Veritas\NetBackup\bin\goodies\misc\PC-IA64\WindowsXP
         \bemcmd51.exe

+  NetBackup includes a limited number of files (listed below) that do not
  include or create requestedExecutionLevel tags:
    C:\Program Files\Common Files\Symantec Shared\VxFI\4\Bin\nbfirescan.exe
    C:\Program Files\Common Files\VERITAS\VxMS\Map\rvp\vxpvdump.exe
    C:\Program Files\Veritas\NetBackup\bin\SpsWrapperV3.exe
    C:\Program Files\Veritas\NetBackup\bin\bpclusterkill.exe

+  NetBackup utilizes a third-party tool to create the files (listed below)
  that does not provide a valid signature mechanism.
    C:\Program Files\Veritas\NetBackup\bin\support\NBCC.exe
    C:\Program Files\Veritas\NetBackup\bin\support\NBCCR.exe
    C:\Program Files\Veritas\NetBackup\bin\support\nbsu.exe



Installation, upgrade, and cluster issues:
------------------------------------------
+  (ET1557527) When installing NetBackup on a Windows 2008 VCS cluster
  configuration, the Next button on the Settings dialog is highlighted.
  However, if you change data on that dialog, the Next button may become
  grayed out.  If you encounter this issue, navigate through each of the
  cluster input fields in the dialog.  After that is complete the Next button
  will be enabled and you can select it to continue with the install.

+  (ET1635638) Performance impact with a Snapshot backup on a Clustered (VCS)
  Windows 2008 configuration.

  On a clustered (VCS) Windows 2008 environment, a Snapshot backup takes longer
  to complete as compared to a backup on a non-clustered environment. The
  Snapshot technology used in this case was Microsoft Volume Shadow Copy (VSS).
  In an engineering test environment, a substantial time delay was noted for
  the VSS APIs. A single NetBackup backup job took more than 10 minutes to
  complete.

  Symantec is currently in discussions with Microsoft to develop a solution for
  this issue. A possible fix is planned to be released in the next release of
  this product.

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

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

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

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

+  (ET1530250)  When running the NetBackup 6.5 GA installation on a system that
  has Symantec Endpoint Protection (SEP) 11.0 installed with the network threat
  protection options enabled, your system will lose network connectivity during
  the install. This is a known Windows-only issue with the SEP MR4-MP1
  (11.0.4010) version.  Symantec recommends that you upgrade to the latest
  SEP 11 version using the following link to the Symantec Support Web site.

     http://www.symantec.com/business/support/downloads.jsp?pid=54619

+  This Release Update Windows installation will set the MaxLogFileSizeKB in
  nblog.conf to a value of 51200. The value of MaxLogFileSizeKB will be set
  to the new value even if it was changed before the Release Update was
  applied.  

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

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

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

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

+  If you are updating a clustered NetBackup server in a VCS configuration,
  Symantec recommends that you run the manual patch install.

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

+  When upgrading a media server using NetBackup LiveUpdate in environments
  that have master and media servers residing on separate domains, you must
  stop tracker.exe on the target media server or the LiveUpdate upgrade will
  fail.

  To avoid this issue, you must ensure that the tracker.exe is not running on
  the media server prior to executing a LiveUpdate upgrade.

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

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

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

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

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

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

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

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

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

+  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

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

+  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


NetBackup Access Control issues:
--------------------------------
+  If you are using NBAC and you may receive the following warning after
  installing the Release Update:

  "The NetBackup Access Control upgrade failed and must be run manually. Make
  sure the Symantec Product Authorization Service is started and then run: \n
  <INSTALL_DIR>Program Files\VERITAS\NetBackup\bin\admincmd\bpnbaz-Upgrade."

  Please open up the install log and search for: NetBackup\bin\admincmd\
  bpnbaz.exe" -CheckUpgrade. If you see a message similar to the following,
  verify the error code value:

  10-10-2008,20:10:16 :  ERROR in running NBAC Command : "C:\Program Files\
  Veritas\NetBackup\bin\admincmd\bpnbaz.exe" -CheckUpgrade Returned error code:
  0 10-10-2008,20:10:16 :  Action ended 20:10:16: NBAC_Upgrade. Return value 1.

  - If the error code is 0 you can ignore this issue altogether.
  - If the error code is something other than 0, then there is an issue and you
    should run the command manually on the affected system.

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


NetBackup Database Agent issues:
--------------------------------
+  NetBackup for Hyper-V known issues:

  - (ET1656180) NetBackup for Hyper-V has a virtual machine restore option
    called "Overwrite virtual machine." This option removes a virtual machine
    on the destination server before the same virtual machine is restored from
    its backup. If the "Overwrite virtual machine" option is not selected and a
    virtual machine with the same GUID exists on the destination server, the
    restore fails with NetBackup status code 5. This failure is a normal
    (expected) result.

    However, if you restore a virtual machine without choosing the "Overwrite
    virtual machine" option, and the virtual machine exists on the destination
    Hyper-V server, the restore fails (as expected) but the existing virtual
    machine is turned off.

  - (ET1663569) A minor problem occurs when attempting to change an option
    in a FlashBackup-Windows policy for Hyper-V, on the Snapshot Client
    Options dialog. When changing an existing policy, if you use the keyboard
    to enter a new value for one of the configuration parameters, the value is
    not retained when the policy is saved. This issue will be fixed in a later
    release of NetBackup.

  - When common (or parent) .vhd files and child .vhd files are restored to a
    drive other than their original drive (such as to G:\ instead of to E:\),
    the restored child .vhd files may not correctly point to the restored
    parent .vhd file on the G:\ drive. As a result, the restored virtual
    machines that rely on the common (parent) .vhd file are invalid. Make sure
    to restore the parent and child .vhd files to the same relative path names
    that they had before the restore.

    For example, assume the following:
    - The original parent was in E:\folder1\parent.vhd.
    - The original child was in E:\folder2\child.vhd.
    - The parent and child .vhd files are restored to the G: drive.

    To allow the child .vhd file to correctly refer to the parent .vhd file on
    the G: drive, you could restore the parent .vhd file to
    G:\restore_folder\folder1\parent.vhd and the child to
    G:\restore_folder\folder2\child.vhd.

    This issue may be fixed in a Windows 2008 Hyper-V update from Microsoft.
    When fixed, it will not be necessary to maintain the same relative paths in
    the restore locations.

  - (ET1514145) If you restore the full virtual machine to a different location
    on the original Hyper-V server or to a different Hyper-V server, the
    virtual machine may fail to start. This failure may be due to a bug in the
    Microsoft Hyper-V writer. The problem occurs when the virtual machine has
    two or more levels of differencing disks. For example: a child.vhd file
    points to a parent.vhd file that points to a grandparent.vhd file.

    After the restore, use the Hyper-V Manager to manually re-establish the
    relationship between the differencing disks (such as child.vhd to
    parent.vhd. to grandparent.vhd).

    A fix for this issue should be available in Windows 2008 SP2.

  - NetBackup for Hyper-V and Logical Disk Manager (LDM)
    If a virtual disk on a Hyper-V virtual machine has been configured for
    LDM volumes, and the NetBackup policy specifies the "2-Mapped FullVM"
    option, in certain cases a backup of the virtual machine may not
    complete. The NetBackup job may issue status 1, "the requested operation
    was partially successful." This error can occur if the controller type of
    the .vhd disk was SCSI when the disk was initially formatted, but the
    controller type was later changed to IDE (or vice versa).

    In this case, the NetBackup progress log may contain the following message:

       ERR - Unable to retrieve volumes from virtual machine, error = 1

    You must restore the controller type of the .vhd disk to the controller
    type originally assigned before the LDM volume was created. Then retry
    the backup.

+  NetBackup Enterprise Vault agent known issues:

  - (ET1500728) An issue exists that can cause the backup of an Index location
    to fail if the index location is configured on the Enterprise Vault server
    within the Enterprise Vault environment and there is no <enterprise vault
    install folder/Reports> folder present on the system. If you attempt to
    backup the Index location, the backup fails because the <enterprise vault
    install folder/Reports> folder is not present on the host. If this folder
    is not on the server, then the discovery job fails and causes the entire
    backup job to fail. This folder may not be present on the system if you are
    only running the Enterprise Vault Indexing service on the Enterprise Vault
    server.

    To work around this issue, create the <enterprise vault install
    folder/Reports> folder manually and then run the backup job again.

  - (ET1475102) If you install the Enterprise Vault Agent on a NetBackup client
    that has Windows 2008 installed, the NetBackup client properties appear in
    READONLYmode. If you encounter this privileges issue, perform the following
    steps to disable the User Account Control (UAC) check box in Windows 2008:

    -  Select Start > Settings > Control Panel > User Accounts > Turn User
       Account Control ON or OFF.
    -  Uncheck the UseUACto help protect your computer check box (it is checked
       by default).

  - (ET1503078) There are instances where the BAR user interface shows a
    default file icon for some files or folders. This issue can occur when the
    complete path size of a file or folder exceeds to a specific value.

  - (ET1533469 and ET1533488) The Enterprise Vault online Help has not been
    updated for the NetBackup 6.5.4 release. The next major release of
    NetBackup contains the Enterprise Vault online Help .

  - The NetBackup Enterprise Vault agent does not support the following user
    interface:

       Host Properties > Master Servers > Server name > Enterprise Vault Hosts

    This user interface was created to enable the federated restore feature.
    However, existing circumstances prohibit the use of this interface for
    6.5.4. This user interface will be supported in a future version of
    release of NetBackup.

+  Exchange Granular Recovery known issues

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

  - 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

  - The following application event log message may appear on an Exchange
    server during an Exchange granular operation (backup, browse or restore)
    and can safely be ignored.
        EventID 16384
        Description: The remote server does not have locking support.  A mount
                     was requested with locking enabled.  The share is being
                     mounted anyway.  Some functionality may not be available.

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

  - For Windows 2008 the following applies:

      - Backups and restores using granular recovery or Mailbox-level backups
        and restores may fail with the MAPI logon error x80040115.  Please
        refer to the following TechNote on the Symantec Support Web site for a
        solution to disable IPv6 for MAPI access.

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

      - The following application event log message may appear on a Windows 2008
        Exchange server if a user does not have the Active Directory or the User
        Name Mapping identity mapping set up and configured using the Services
        for NFS properties. This message occurs during an Exchange granular
        operation (backup, browse or restore) and can safely be ignored.
          EventID 16397
          Description: Windows(R) Lightweight Directory Access Protocol (LDAP)
          failed a request to connect to Active Directory Domain Services(R)
          for Windows user <DOMAIN\USER>. Without the corresponding UNIX
          identity of the Windows user, the user cannot access Network File
          System (NFS) shared resources.  Verify that the Windows user is in
          Active Directory Domain Services and has access permissions.

+  (ET1174583) An enhancement has been made that adds base NetBackup support for
  SQL Server 2008. However, database moves from Snapshot backups taken of
  databases that contain file stream data are not supported.

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

+  (ET1595100) NetBackup requires that a portal use the IP address when
  backing up and restoring a portal. Using a portal name will result in site
  not being found condition, then there will need to be manual steps to
  complete the restore.  The databases do get restored to SQL. Use the
  SharePoint Central Administrator to Recover a Portal, use the IP for the
  URL address, and also enter the names of the SITE, SERV and PROF databases
  that are restored. After the portal is recreated, use the SharePoint
  Central Administrator Manage Content databases for the virtual server, to
  add any Team Sites that are associated to the Portal Site - these will also
  get backed up and then restored to SQL.

  The steps to recover the named URLportal after retore.
    1. Verify the content databases are restore to SQL.
    2. Use SharePoint Central Administrator - List and Manage Portal Sites
         Restore a Portal
    3. Select the virtual server and place the names of the SITE, PROF and
         SERV databases in their respective fields
    4. Use the portal IP address for the portal URL site address.
    5. If there are additional team sites associated to the portal, use
         SharePoint Administrator Virtual Server Manager to Manage Content
         Databases to add them back to the portal site.
    6. The portal should now be available for browse.
    7. Using the IP for the portal site URL address should void the need to
         have to manually do these steps to recover the site going forward.

+  The following issues are specific to SharePoint 2007.

  - (ET1255700) When restoring a SharePoint WSS 2.0 site where the site is
    gone but the database still remains, the site may not be extended after a
    restore has completed successfully.  In this case, the user must extend
    the site using the SharePoint administrator user interface.

  - To view a SharePoint node in Backup, Archive,and Restore user interface
    for a SharePoint backup, you must install the Microsoft .NET framework 3.5
    on the SharePoint servers.

  - Document-level restores will fail if the string "_Granular_" is contained
    within the document name. You can restore the document using a full
    database restore.  To avoid this issue, rename the documents that contain
    the string "_Granular_" to a name without the string "_Granular_" prior to
    performing the backing up.

  - (ET1594142) When performing a Disaster Recovery of a SharePoint web
    application and the last restore is complete, verify that the web
    application appears in the list of web applications and then perform a
    iisreset.  The iisreset command can be performed by opening a command
    prompt window and typing the command "iisreset /noforce".

  - (ET1588836) When restoring a Data Connection Library document from a GRT
    backup, the documents in the library will have the appropriate approval
    status however the version history may state that 'This is the current
    approved version' when it may not be.  The workaround for this issue is
    to have the user set the appropriate status for the item.  

  - (ET1502252) Restoring a document/picture library item when the library or
    folder does not exist will not be restored.  The library or folder is not
    recreated and the item is not restored The work around for this issue would
    be to redirect the restore to a file system and then upload the items into
    SharePoint.

  - (ET1485122) The application, SPSRecoveryAsst.exe, gives an application
    error when trying to restore an invalid object selected from the Backup,
    Archive, and Restore user interface.  The workaround for this issue is to
    select the correct item to restore.

  - (ET1594331) Performing a granular back up of content databases that do not
    contain any sites sresult in an error message being generated and the
    backup completes with a status 1.  The error message in the progress log
    is:
      ERR - Error encountered while attempting to get additional files for
            Microsoft SharePoint Resources:\Windows SharePoint Services Web
            Application\SharePoint - XXXXX \Content-DB 1 ...
      ERR - SharePoint granular restores from this image will not work.

    Granular restores will work from all databases in the image that contain
    sites.

  - (ET1589445) Using AllWebs to perform a granular backup of secure and
    non-secure web applications will result in a status 1.  The secure sites
    can be backed up individually or together successfully

  - (ET1540667) After restoring a subsite the link is not restored in both
    quick launch and top link bar.  There is an option to add a link so the
    user could do that as a workaround.

  - (ET1539923) Special characters in item names are excluded when displayed in
    the Backup, Archive, and Restore user interface.  When the items are
    restored, the special characters do appear in the restored item.

  - (ET1639566) Restoring a document from a NetBackup 6.5.3 image of a
    SharePoint 2003 portal may be reported as successful but the document does
    not get restored. To avoid this issue, restore the database or perfrom a
    redirected database restore and access the desired document.

  - (ET1637318) Restoring a Web Application that contains webparts from a
    granular image results in missing webparts. Once the restore has been
    completed, you must reapply the webparts.

  - (ET1633472) Unable to browse sites after multiple db restore. The IIS
    settings are not preserved when running this restore. To resolve this issue,
    restore the SharePoint Web Application from a FULL and DIFF(s) images in
    one job.

  - (ET1630657) A redirected restore of granular content to the filesystem
    (using a unc path) from multiple content databases the restore fails and
    informs the user that the restore failed to recover the requested files.
    The workaround is to restore content from one db at a time.

  - (ET1653526) The SharePoint Shared Services database does not get restored.
    The SharePoint farm can be recoverd from backup without this database, All
    the web applications can be restored successfully along with their content.
    A new SSP service is created as part of the recovery.

  - (ET1640309) A redirected restore of a SharePoint Web Application using FULL
    and DIFF images in seperate jobs will fail.  The workaround is to perform
    the redirected restore of a SharePoint Web Application using a FULL and
    DIFF images in a single job.

  - About restores of SharePoint Server and Windows SharePoint Services

    When you perform restores, you should administer the restores from the
    NetBackup master server or the SharePoint front-end server. When you run the
    restores from the master server, the restores run but no progress log
    appears. You must monitor the job status from the job details on the master
    server. Symantec recommends that you run the restores from the SharePoint
    front end server.

  - You can redirect SharePoint sites, documents, lists or items to a path, a
    workspace, or a document library, as follows:

    -  Redirect to path.  In the Restore to drive or UNC path box, enter the
       drive letter or UNC Path. Use the following format for a UNC path:
       \\servername\share.

       In the Restore to path box, enter the path to which you want to direct
       the restore.

    -  Redirect to workspace or document library (WebStorageSystem-based only).
       This option only applies to SharePoint 2001 restores.

    NOTE: When you direct items to a file system, any list items you selected
          are not restored and appear as 0 KB files. If redirecting list items
          to a file system, the item itself will be a 0 KB file but if the list
          item has any attachments they will get restored.

    -  Redirect to the Windows file system. When using a drive letter it must
       be entered C:\  (or whatever drive letter the users chooses) and the
       "Restore to Path" must be entered as "restored data". The granular
       restore will run on the backend server.

       If the user does not follow this then the granular restore fails with a
       status 5: and the following appears in the log:

       17:14:37 (2180.001) TAR - Unable to restore. Skipping file: SharePoint -
       38951\Content-DB 1    

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

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

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

+  (ET1278383) Exchange 6.5.2 - LCR/CCR backup support

  To ensure that the CCR client attributes are set properly for both nodes in
  the cluster, the user needs to update the Exchange client attributes for
  each node individually. Changing the attributes for the virtual CCR name
  will only affect the active node at the time of change.

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

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

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



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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  If the config directory does not exist, create it.

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

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

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

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

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

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

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

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

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

+  (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,
  you need to 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.

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

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

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

+  (ET1052487) For SharedDisk on Windows systems, you can use either GUID
  Partition Table (GPT) or Master Boot Record (MBR) to format LUNs on Windows
  systems that support GPT.  GPT allows disks larger than 2 TB in size.

  However, NetBackup 6.5.1 and earlier cannot read or write disks that use GPT.
  Therefore, if you use both 6.5.1 and earlier and 6.5.2 and later for disk
  pool access, all LUNs must be formatted with MBR. MBR disks are limited to
  2TB maximum size.

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

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

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

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


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

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

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

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

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

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

+  (ET1424582) The Windows Administration Console will crash if the user has a
  SAN Client connected to the setup and performs the following steps:

  1. Click on Devices node and view the SAN Clients attached to the setup.
  2. Then click on Host Properties and view the Master server properties.
  3. Windows Administration Console will crash if user performs a Refresh All
     operation any time after viewing the Master server properties from
     Host Properties.

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

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

+  (ET1224679) The NetBackup Administration Console for Windows may crash when
   two instances of Administration Console are running on two separate remote
   desktop sessions on the same server. This issue rarely occurs and is not
   easily reproducible. The issue is not a regression and is outside of the
   normal scope of operations. Hence, this issue is planned to be addressed in
   a future NetBackup 6.5 Release Update.

+  (ET1238485) The NetBackup Administration Console for Windows may crash if
  the user clicks on the Activity Monitor node and then clicks on Media node.
  This issue is associated with ET1219769 and a temporary patch has been
  applied to prevent the crash. A proper fix for this issue is planned a future
  NetBackup 6.5.x Release Update.


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

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

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

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

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

  Potential workarounds are the following:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

+  (ET1174736) This release contains a 32-bit Windows memory management
  limitation. Windows can only address 4GB of memory. If an attempt is made
  to perform a Flashbackup of volumes that are larger than 10TB, that it
  requires more than 4GB of memory to store the bitmap that needs to be
  created for the restore of single files.  To work around this issue,
  Symantec recommends that you make smaller volumes or use a UNIX Master
  server.

+  (ET1412544) The Windows NTFS file system has a feature called junction
  points. A junction point can be set up to provide access to files in a local
  directory (similar in function to a symbolic link). For backups of a VMware
  virtual machine, NetBackup for VMware does not currently support a junction
  point as the snapshot mount point on the VMware backup proxy server. The
  snapshot mount point must be a local directory on the proxy server, not a
  junction point that refers to a local directory. Support for junction points
  as the snapshot mount point on the proxy server will be added in a future
  release.

  CAUTION: if a junction point is used as the snapshot mount point, the backup
  appears to succeed, but the actual files that were backed up may be the wrong
  files.

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

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

+  (ET1259882) NetBackup for VMware does not support a USB drive as the snapshot
  mount point on the VMware backup proxy server. This support will be added in
  a future release of NetBackup.

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

+  (ET125074) Attempting to restore Bare Metal Restore (BMR) Windows clients
  using Broadcom NetXtreme II network adapters that are rebranded by certain
  OEM vendors (such as HP NC373i) fails with the following error message.

  "Failed to install network driver - check WINBOM."

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

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

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

+  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

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

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

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

+  A BMR Fast Restore of a Windows client with a single partition fails with the
  following error message.

     Failed to run X:\BMR\NBU\BIN\BMRRST.EXE - begin

  When attempting a BMR restore of Windows clients with a single system or boot
  partition, the process could fail during the Finalizing Restore step with the
  error message mentioned above:

  If you encounter any issues attempting a BMR Fast Restore of a Windows client
  with a single partition, please consult with a Symantec Support representative
  for further guidance.



NetBackup Snapshot Client (and NetBackup Hyper-V)
-------------------------------------------------
+  (ET1418453) The following is a known issue pertaining to redirected restores
  of Hyper-V virtual machines that were backed up in the "Saved" or "Paused"
  state.

  If a Hyper-V virtual machine is in the "Saved" or "Paused" state when
  NetBackup backs it up, the virtual machine will be in the "Off" state (rather
  than Saved or Paused) after it is restored to a different location. The
  change of state to Off is caused by the current Microsoft Hyper-V writer.

  If the virtual machine is restored to its original location on the original
  Hyper-V server, the state of the virtual machine when it was backed up is
  correctly restored. If the virtual machine was in the Saved or Paused state,
  it is set to Saved or Paused after the restore.



Bare Metal Restore (BMR) issues
---------------------------------
+  With 6.5.4 AIX BMR Boot Server, bmrsrtadm fails to create media shared
  resource tree (SRT) with version "AIX5.3TL9" and above

  Changes that were introduced in AIX5.3 TL9, with the 6.5.4 AIX Boot
  Server installed, causes bmrsrtadm to fail to create an ISO with version
  "AIX5.3TL9" and above.  Hence, it fails to do a media restore.

  To avoid this issue, use the following procedure to create an ISO from
  the SRTs with a version of "AIX5.3TL9" and above.

  1. Verify if an AIX5.3TL9 SRT already exists on a boot server in a specific
     path (for example, "aix53tl9" resides inside the path /export/srt>).
  2. Create a soft link /export/srt/aix53tl9/usr/lpp/bos/inst_root/unix to
     /usr/lib/boot/unix before you attempt to create the ISO using bmrsrtadm.
     The following is an example of how to create the soft link:
        ln -s /usr/lib/boot/unix /export/srt/aix53tl9/usr/lpp/bos/inst_root/unix
  3. Use bmrsrtadm to create the ISO out of the modified AIX5.3TL9 SRT (for this
     example use, aix53tl9).

+  DOS-based Restore is not supported for Windows x64 Clients:

  Windows x64 Client systems cannot be restored using the legacy DOS-based
  Restore.  This is because a DOS-based Restore requires a 16-bit OS installer
  application (winntsetup.exe) that can be invoked from within DOS environment.
  For 64-bit versions of Windows OS, Microsoft did not ship 16-bit installers.
  Hence, the temporary OS installation of 64-bit OS for BMR cannot be initiated
  from DOS environment. As a result, Windows x64 Client systems cannot be
  restored using the legacy DOS-based Restore.

  In addition, the BMR "FastRestore" is the only mechanism of BMR Restore for
  Windows x64 Client systems.

+  Storage Foundation for Windows (SFW) is not supported on Windows x64 Clients:

  Windows x64 Client systems running VERITAS Storage Foundation for Windows
  (SFW) cannot be restored. This issue is valid because Windows clients running
  SFW cannot be restored using "FastRestore" mechanism of BMR. This means,
  Windows clients running SFW can be BMR restored using only a legacy DOS-based
  Restore mechanism. For Windows x64 Client systems, the legacy DOS-based
  Restore mechanism cannot be used for reasons stated above. Hence, Windows x64
  Client systems running VERITAS Storage Foundation for Windows (SFW) cannot be
  restored.

  Because of this issue, BMR in NetBackup 6.5.4 is not able to protect
  Windows x64 Client systems that are running VERITAS Storage Foundation for
  Windows (SFW). Currently, there is no work-around available.

+  "Legacy Boot Floppy Wizard" is not supported on Windows x64 Boot Server:

  With NetBackup 6.5.4, a BMR Boot Server can be installed on a Windows x64
  system as well. In general, BMR does not distinguish between the 32-bit and
  64-bit Boot Server on Windows. What this means is that a 32-bit (x86) Windows
  Boot Server upgraded to NetBackup 6.5.4 is able to correctly host both 32-bit
  or 64-bit SRTs. Similarly, a 64-bit (x64) Windows Boot Server at
  NetBackup 6.5.4 is able to correctly host both 32-bit and 64-bit SRTs.
  However, "Legacy Boot Floppy Wizard" is not available on a 64-bit Boot
  Server. If attempted to run, BMR informs the user that it is not supported on
  that particular version of the OS, and closes the wizard.

  Running this wizard can involve running some 16-bit code. On a 32-bit Boot
  Server, this code executes under WOW32. On 64-bit Boot Server, however,
  16-bit code cannot be executed. This is a limitation of the 64-bit Windows OS.

  At least one 32-bit Boot Server is required to create a Boot Floppy for any
  32-bit Windows clients that need to be BMR restored using the legacy DOS-based
  Restore.

+  Windows x64 Clients' data would get deleted in case of a downgrade from
  NetBackup 6.5.4:

  After upgrading to NetBackup 6.5.4, if user is required to (even temporarily)
  downgrade BMR Master Server to a pre-6.5.4 version, then the downgrade process
  deletes all of the data from the BMR database that pertains to the Windows x64
  Client systems, 64-bit SRTs, and the driver packages. This data is deleted
  forever. After upgrading again to NetBackup 6.5.4, the user would need to take
  fresh full backups of all Windows x64 Client systems to have them protected
  by BMR.

  BMR code and database schema was changed in NetBackup 6.5.4 to allow for
  distinction between 32-bit and 64-bit data (SRTs, driver packages and Client
  configurations). If a user downgrades from NetBackup 6.5.4, the BMR database
  schema and code changes are rolled back to a previous version, and any data
  that pertains to the Windows x64 Client systems loses its identity. The
  previous version, being ignorant of any x64 data, is then likely to use this
  data and treat it as 32-bit data. This creates a data integrity issue in the
  BMR database and impacts BMR's ability to restore even the old, 32-bit Client
  systems that were protected even in a previous version.

  Therefore, a BMR downgrade process in 6.5.4 deletes all such x64 data, and
  leaves only 32-bit data in the BMR database to preserve the database integrity
  and BMR's ability to continue to protect any existing 32-bit Windows Client
  systems.

  If you downgrade NetBackup 6.5.4, AND there was x64 data in the BMR database
  at the time of downgrade, then this data will get deleted during the
  downgrade. There is no work-around to this issue.  If you encounter this issue
  you need to take fresh full backups of the x64 Windows Client systems if and
  when you upgraded back to NetBackup 6.5.4 again.

+  GPT disks are not supported.

  BMR does not support GPT disks. Windows x64 Client systems that have one or
  more GPT disks are not supported by BMR. There is no work-around to completely
  support GPT disks; but BMR backup may succeed in case of such systems. If the
  backup was successful, BMR may be able to restore the system; although the
  GPT disks are implicitly restored as MBR-based disks. Also, as Windows 2003
  and XP do not support system or boot volumes on GPT disks, a "System-only"
  Restore should work correctly. In cases of self-Restore to the physically same
  GPT disks, the behavior is undefined and unknown

+  Starting with NetBackup 6.5.4, the BMR Master Server will not work correctly
  with pre-6.5.4 Windows Boot Servers.

  Starting with 6.5.4, BMR Master Server does not work correctly with pre-6.5.4
  Windows Boot Servers. After upgrading the BMR Master Server to 6.5.4, all of
  the Windows Boot Servers need to be upgraded to NetBackup 6.5.4.

  Certain changes were done for Windows x64 Client support in 6.5.4. These
  changes were done to the Master Server as well as Windows Boot Server. An
  older Windows Boot Server is not able to correctly perform tasks like
  "Prepare to Restore". Thus, any Windows Boot Servers also need to be upgraded
  to 6.5.4 along with the Master Server, to successfully restore Windows Client
  systems.

  When upgrading BMR Master Server to 6.5.4, you also need to upgrade any
  Windows Boot Servers to 6.5.4. This limitation does not apply to UNIX/Linux
  Boot Servers.

+  Limited availability of localized "FastRestore" SRTs for Windows x64 Clients.

  For 32-bit (x86) Windows Client systems, BMR provides two localized versions
  of the 32-bit "FastRestore" SRT - Japanese and Simplified Chinese. For 64-bit
  Windows (x64) Client systems, BMR is not able to provide localized versions
  of the 64-bit "FastRestore" SRT. (More updates on the possibility of
  availability for the localized versions of 64-bit "FastRestore" SRTs will be
  published in near future.)

  Certain technical constraints that arise out of availability/compatibility of
  the localized versions of the involved components have delayed the
  availability. In addition, localized versions of some of the components are
  also missing from Microsoft.

  Users may experience difficulties while restoring localized Windows x64 Client
  systems using FastRestore method of BMR. No current work-around exists for
  this issue.

+  (ET1597920) Disaster recovery email and AdvancedDisk storage units
  If an online, hot catalog backup is directed to an AdvancedDisk storage unit
  and a catalog backup policy identifies a critical policy that has a backup

  image located on the same AdvancedDisk storage unit, the disaster recovery
  email does not list that critical policy.

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

+  "Prepare To Restore" wizard fails on 6.0MPx client configurations

  If you upgrade the BMR master server to 6.5.4 and still run the boot server
  at 6.0MPx (6.0MPx SRT), restores to 6.0.x clients fail. This occurred because
  certain checks were retained for this wizard in 6.5.4 for restores on a
  client configuration with a low-level SRT. These checks do not work well
  with older versions because of a change in the version style.

  To restore to 6.0.x clients with a BMR master server at 6.5.4, you must
  upgrade the boot servers to 6.5 or later.


Localization issues:
--------------------
+  (ET1592679) An unexpected log conversion may occur with the vxlogview log.
  The localized name of the strings that represent the backup targets were
  invalid. A fix will be made in a future release that ensures vxlogview will
  be able to convert lines that contain any multibyte character.

+  (ET1556155) The Japanese vault store name becomes unreadable in the
  bpresolver log.

+  (ET1556191) After selecting, "Full Check including indexes" an issue
  occurred that caused ENTERPRISE_VAULT_DBCC_CHK_PREBKUP to be created,
  however ENTERPRISE_VAULT_DBCC_CONT_ONERR was not created even though the
  "Continue with backup if consistency check fails" was checked as the default
  setting in the Client Properties dialog. The ENTERPRISE_VAULT_DBCC_CONT_ONERR
  should have been created and set to 1 or the "Continue with backup if
  consistency check fails" is not checked as the default.

+  (ET1592462) The ffile of the root job is correctly encoded with UTF-8,
  however, the ffile of the child jobs are incorrectly encoded with Shift-JIS.

+  (ET1592583) Unexpected log conversion with vxlogview caused invalid
  localized names for the backup targets.  vxlogview should be able to convert
  lines that contain any multi byte character.

+  (ET1633814) If a logon account was not raised with UAC, nothing would
  happen even if an attempt was made to right-click the tracker icon. And if the
  tracker icon was double-clicked the tracker.exe would crash.

  If you encounter this issue, check "Run this program as an administrator" on
  the compatibilities tab for the properties of the tracker.exe executable.


General Documentation issues:
-----------------------------
+  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.

+  (ET1197993) The 6.5 NetBackup Administrator's Guide, Volume I, incorrectly
  states that the Virtual Tape Option is necessary 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.1 -
        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.1 -
        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
==========================
The following procedure explains how to download this CD image, which is an
update to NetBackup/Media Manager products with the latest fixes for
Windows NetBackup servers.

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

  where <6 digit number> is an internal tracking identifier

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

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



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

Before you install, review the following list of notes:

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

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

  - To install a NetBackup media server on Windows 2008 x64, use the separate
    Windows 2008 x64 CD (the separate CD installation was developed primarily
    to meet Microsoft's Works With certification standards).

  - To install a NetBackup client on Windows 2008 x64 Server Core, use the
    silent install script present on the Windows 2008 x64 CD.

  - If you have BMR Boot server you should take down those processes before
    performing the install/uninstall.

  - Symantec recommends that you perform a catalog backup before and after
    you apply this CD image.

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

For installation on Windows CLUSTER Environment:

Refer to the Veritas NetBackup Installation Guide for Windows when installing
NetBackup in a clustered environment.


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

For Windows 2008 customers running Windows x64:

The following list contains information that pertains only to those users who
are installing Windows 2008 on a Windows x64 platform.

  - For new Windows 2003 and 2008 customers, Symantec recommends that you

    download the CD-ROM image of this particular version of the release from
    the Symantec Support Web site.

  - One of the requirements to achieving Microsoft's "Works-with Certified",
    Symantec must record any Works-with" errors that are received. The
    following list represents the known issues that were received during
    testing. These errors does not affect a customer's ability to install
    and run this release.

    - ICE40 WARNING REINSTALLMODE is defined in the Property table.
    - ICE84 WARNING An action was found in the InstallExecutiveSequence table.

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


Installation steps:

This CD image contains all of the 6.5.4 fixes for the NetBackup that were
included in the 6.5.4 Release Update. This CD image contains all of the fixes
for NetBackup Add-on products, Database Agents, and NetBackup Encryption that
are contained in the 6.5.4 Release Update. (If you are a Windows 2003 user
and have NetBackup currently installed, do not install this CD image, you
should install the NetBackup 6.5.4 Release Update.)


1) Click on the Launch.exe (Double-click on the icon from File Manager or
  Explorer or run it from the command prompt)

2) Using the CD Browser, select the appropriate installation type and follow
  the installation procedures documented in the NetBackup 6.5 Installation
  Guide for Windows.

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

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

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

4) Remove the temporary directory created in the download instructions

  Symantec recommends that you perform a catalog backup after you have
  pplied this CD image.

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

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

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

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

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

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

To use Open File Backup:

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




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

To uninstall:

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

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

2) Go to Add/Remove programs dialog box and select Veritas NetBackup to be
  uninstalled.

NOTE: To uninstall NetBacku in a clustered environment, refer to the
     Veritas NetBackup Installation Guide for Windows.




 

Attachments

NB_6.5.4.Winx64_CD_326387.exe (654.4 MBytes)

Legacy ID



326387


Article URL http://www.symantec.com/docs/TECH71299


Terms of use for this information are found in Legal Notices