ADC 5.0GA Pack NB_ADC_50_7_M README                             December 5, 2006
Requirement: NB_CLT_50_7_M
================================================================================
** All 5.0 MP7 Maintenance Packs for NetBackup server, client, all Add-on  
products, Database Agents, and Java GUI must be applied so that the entire  
system is at the same Maintenance Pack level. **

This Maintenance Pack provides an update to Veritas NetBackup (tm) Advanced  
Client.

Symantec recommends that the backing up of active file systems be avoided,  
or the use of snapshot technologies be implemented. The directory structure  
reported back from the file system (to NetBackup) may not contain all of the  
files available during the time of backup. NetBackup will not report errors  
in many cases where the file's existence is not known to NetBackup as reported  
by the file system.

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


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

    -- Installation of this Maintenance Pack requires version 1.17.4.40 of  
       the Vrts_pack.install.

    -- Maintenance Pack NB_CLT_50_7_M must be installed prior to installing  
       this Maintenance Pack.



I.   DOWNLOAD INSTRUCTIONS        
II.  KNOWN ISSUES
III. INSTALLATION INSTRUCTIONS
IV.  UNINSTALL INSTRUCTIONS
V.   DESCRIPTION OF PROBLEMS FIXED
       Current Pack
          NB_ADC_50_7_M

       Pack History
          NB_ADC_50_6_M  
          NB_ADC_50_5_M
          NB_ADC_50_4_M
          NB_ADC_50_3_M
          NB_ADC_50_1_M


=========================
I. DOWNLOAD INSTRUCTIONS
=========================
1) Download NB_ADC_50_7_M_<6 digit number>.tar into the /tmp directory.

  where <6 digit number> is an internal tracking identifier

2) Extract NB_ADC_50_7_M_<6 digit number>.tar
       /bin/tar -xvf NB_ADC_50_7_M_<6 digit number>.tar

       This will create the files:
       Vrts_pack.install
       VrtsNB_ADC_50_7_M.README
       VrtsNB_ADC_50_7_M.tar.Z



=================
II. KNOWN ISSUES
=================

ET854799 - When performing an alt client snapshot backup, the following bpbrm
          error message appears in the Job Details:

          Error bpbrm (pid=6226) from client dawnstar: ERROR: Message not Found!

          The job continues to run, producing a status 0, however the files can
          still be restored.



==============================
III. INSTALLATION INSTRUCTIONS
==============================
UNIX:

As root on the NetBackup Server with NetBackup for Advanced Client:
1) Install Maintenance Pack binaries.

   cd /tmp
   /bin/sh Vrts_pack.install

2)  Update the NetBackup Advanced Client clients, which should
   include the NetBackup master server if the master server
   is an HP or Solaris machine, with the new Advanced Client  
   software.

   Distribute the NetBackup Advanced Client software to all currently  
   defined clients by executing the following command:
   
   /usr/openv/netbackup/bin/update_clients -Install_ADC <hardware> <os>

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

       HP9000-700 HP-UX11.00
       HP9000-800 HP-UX11.00
       HP9000-700 HP-UX11.11
       HP9000-800 HP-UX11.11
       Solaris Solaris7
       Solaris Solaris8
       Solaris Solaris9



============================
IV. UNINSTALL INSTRUCTIONS
============================
Note:  This will ONLY uninstall the Maintenance Pack from your local machine.

   1) Close the NetBackup user interfaces.

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

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

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

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

   3) Run the un-install script:

         ./Vrts_pack.uninstall

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

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

   6) If necessary, restart the NetBackup and Media Manager daemons:
       /usr/openv/netbackup/bin/goodies/netbackup start



==================================
V. DESCRIPTION OF PROBLEMS FIXED
==================================
The following are descriptions of the problems fixed.  Please read the entire
document before installing.

README Conventions:

Description
    Describes a particular problem contained in this pack.

** Description **  
    Describes a problem that can lead to potential data loss. Please  
    read these problem descriptions carefully.

Workaround
    Any available workarounds to a problem are also listed. Workarounds  
    can be used INSTEAD of applying the patch, however, Symantec strongly  
    recommends that you are at the latest patch level.

Additional Notes  
    Any additional information regarding a problem is included.



=============  
Current pack  
=============  

================================================================================
Etrack Incident = ET422442

Description:  
   VSP snapshot creation would leave miscellaneous files in the following
   location:
       
   C:Files_util_cntl  
--------------------------------------------------------------------------------
Etrack Incident = ET519756

Description:  
   msvcrt.dll errors were appearing in the Event Viewer and caused pop errors
   on a Windows x64 client.  
--------------------------------------------------------------------------------
Etrack Incident = ET419062

Description:  
   bpfis was not recovering well if the server tried to requeue jobs when a
   status 134 occurred.  
--------------------------------------------------------------------------------
Etrack Incident = ET518757

Description:  
   Disk group cloning failed because Advanced Client did not recognize
   different format types of the disk. It only recognized the default disk
   type labeled, cds.
     
--------------------------------------------------------------------------------
Etrack Incident = ET540212

Description:  
   Make messages failed in the cl/client directory because of  
   duplicate message strings.  
--------------------------------------------------------------------------------
Etrack Incident = ET536883

Description:  
   FlashBackup was recoding directory inodes as possible hard links. This
   caused a lot of overhead activity during the restore that greatly
   increased the restore time.  
--------------------------------------------------------------------------------
Etrack Incident = ET546316

Description:  
   FlashBackup core dumps during the changed block handling stage
   of an offhost backup.  In addition, restores fail during the
   changed block processing.  
--------------------------------------------------------------------------------
Etrack Incident = ET537248

Description:  
   Advanced Client VxFS_Checkpoint snapshot method could not create more than
   one Veritas (tm) File System by Symantec (VxFS) storage checkpoint within
   a second on the same file system. This was because the VxFS storage
   checkpoint name was based on the local time and a second is the minimal
   resolution, this makes the name within a second not unique.
       
   bpfis process errors as follows :
       
   vxfs_ckpt_freeze: Cannot create checkpoint, status=17 - Unknown Checkpoint  
   API error  
--------------------------------------------------------------------------------
Etrack Incident = ET580984

Description:  
   There are two methods for fast recovery of files from VxFS_Checkpoint
   snapshot, Block Level Incremental (BLI) and File Promotions. BLI restore
   requires that the file to restore exists and File Promotion requires the
   file to be deleted. Therefore, the two methods cannot be used at the same
   time.  
--------------------------------------------------------------------------------
Etrack Incident = ET575347 ET609338 ET609487 ET609540 ET608376 ET609623 ET614668
ET612687 ET616976 ET617837 ET616940 ET622225 ET624432 ET633297 ET641183 ET699951
ET701953 ET781198 ET597210 ET598796 ET575338 ET596635 ET612761 ET787052 ET788824
ET786896 ET814652 ET575351 ET575352 ET575097 ET575330 ET575331 ET575345 ET575337
ET575335 ET577778 ET575333 ET596395 ET575334 ET575313 ET583770 ET575353 ET581028
ET575346 ET575329 ET575343 ET575308 ET575732 ET575309 ET575341 ET577306 ET575350
ET596637 ET596130 ET597780 ET601849 ET596188 ET596645 ET596654 ET596697 ET597281
ET597219 ET597298 ET596342 ET597379 ET598052 ET598865 ET599823 ET598813 ET600384
ET601396 ET601454 ET601344 ET600735 ET602205 ET600844 ET602349 ET603659 ET605285
ET602850 ET575311 ET607666 ET608687    

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



============
Pack History
============

=============
NB_ADC_50_6_M
=============
Etrack Incident = ET410097

Description:  
   The snap driver needed to be compiled on Solaris 10 to run on Solaris 10.  
--------------------------------------------------------------------------------
Etrack Incident = ET409615

Description:  
   VxVM 4.1 required the addition of a mapping library for offhost backups.  
--------------------------------------------------------------------------------
Etrack Incident = ET406247

Description:  
   When there is a LOFS (loopback file system) mount, a bpfis create  
   function fails and places the following message in the bpfis log:
   
   14:25:29.673 [12271] <16> bpfis main: FTL - process_fs_list() failed,  
   status 11  
--------------------------------------------------------------------------------
Etrack Incident = ET374100

Description:  
   On very busy HP-UX systems, the mount of the VxFS snapshot took long  
   enough for the process to be killed by a signal when an error was  
   detected. The snapshot then was not able to be removed.  
--------------------------------------------------------------------------------
Etrack Incident = ET321763

Description:  
   When a Flashbackup job was cancelled from the interface, the snapshot was
   not deleted.  

Workaround:  
   To avoid the issue, manually kill the backup by issuing the following
   command:  
   
   kill -TERM to bpbkar.  
--------------------------------------------------------------------------------
Etrack Incident = ET322790

Description:  
   The NBU_snap snapshot creation failed if the cache device was more
   than 1 Terabyte.  

Workaround:  
   To avoid this issue, reduce the cache size to less than 1 Terabyte.  
--------------------------------------------------------------------------------
Etrack Incident = ET410523

Description:  
   Incremental backups would not show all files backed up, or would have
   incomplete directory paths if a write to a temp file failed.  

Workaround:  
   To avoid this issue, increase the file space available to change
   /usr/openv/netbackup/BPFSMAP_TMPDIR a link to a file system with more  
   space.  
--------------------------------------------------------------------------------
Etrack Incident = ET203296

Description:  
   When browsing a UNIX FlashBackup image on a Windows master server, you  
   were unable to browse the entire path for raw partitions.  
--------------------------------------------------------------------------------
Etrack Incident = ET419469

Description:  
   Storage foundations 4.1 on Solaris 10 would return a value of -1 for the
   disk address to indicate a hole in a sparse file. However, the code  
   expected a 0 to indicate a hole. This caused incremental backups that  
   include sparse files to fail with the following in the bpbkar log:
   
   4:07:29.132 [20414] <4> bpfsmap: INF - put_imghdr: byteorder=0
   04:07:29.226 [20414] <32> bpfsmap: FTL - mark: assertion failed (at
   fsmap.c.1448)
   04:07:29.240 [20414] <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 130:
   system error occurred
   04:07:29.242 [20414] <4> bpbkar Exit: INF - EXIT STATUS 130: system error
   occurred
     
================================================================================



=============
NB_ADC_50_5_M
=============
================================================================================
Etrack Incident = ET289663 ET232819

Description:  
   A BusinessCopy backup with keep_fi=1 failed when a non-default mirror was  
   used.  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET287102

Description:  
   After running FlashBackup backups that were aborted, a snapcachelist
   command showed the snapshot cache device still in use even though the
   snaplist command did not return any snapshots. Eventually, the snapshots
   would fail because of the 32 snapshots per cache device limit. A reboot is
   required to recover the use of the cache device.  

Additional Notes:  
   The snap driver has been modified to use a different flag bit to denote a
   snapshot in creation versus a snapshot that is being deleted. A snapshot in
   creation is allowed to be listed by snaplist, and can be deleted.
   FlashBackup has been changed to remember the snapshot ID between the time
   that the snapshot is initially created to the time that the snapshot device
   is opened so that it can be deleted.  

   (NetBackup Clients:  Solaris Solaris9 )
--------------------------------------------------------------------------------
Etrack Incident = ET288797

Description:  
   With NetBackup 5.0 MP4 in place, shadowimage backups are working, but the
   disks are not being resynchronized. The "resync" is failing on the rebuild.
   
   For an alternate client shadowimage/businesscopy backup, if client can only
   see the primary disks, then the backup fails. The online_util log showed  
   find_pair failed and bcv_raw_device is the same as dev_raw_device.
   
   16:52:56.767 [9383] <2> rebuild_fim_list: INF - line is PRIM_MIR_INFO=START
   16:52:56.767 [9383] <2> rebuild_fim_list: INF - line is
   PMINFO-dev_raw_device=/dev/rdsk/c6t0d53s2
   16:52:56.767 [9383] <2> rebuild_fim_list: INF - line is
   PMINFO-p_dev_raw_device=/dev/rdsk/c6t0d53s2
   16:52:56.768 [9383] <2> rebuild_fim_list: INF - line is
   PMINFO-bcv_raw_device=/dev/rdsk/c6t0d53s2
   ...
   16:52:57.327 [9383] <2> onlfi_vfms_logf: INF - find_pair: Cannot find
   secondary device for primary device /dev/rdsk/c6t0d53s2
   16:52:57.700 [9383] <2> onlfi_vfms_logf: INF - find_pair: Cannot find
   secondary device for primary device /dev/rdsk/c6t0d53s2  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET229930 ET295123

Description:  
   FlashBackup on Windows for incremental backups was allocating 32 times the  
   needed space for the bitmaps it needed.  In addition, during incremental
   backups the possibility existed that the FlashBackup code would attempt to
   use structures in space that had previously been freed.  

   All NetBackup Windows Clients  
--------------------------------------------------------------------------------
Etrack Incident = ET216480

Description:  
   Storage Foundations 4.0 full-sized instant snapshots did not work if the
   policy snapshot method was set to FlashSnap.
   
   The following was recorded in the online_util log, if the volume had full-
   sized instant snapshots and the policy's snapshot method was FlashSnap.
   
   9:30:35.576 [18050] <2> onlfi_vfms_logf: INF - --- Dumping file
   /var/tmp/VfMSCAA5YaqqJ (stdout):
   09:30:35.576 [18050] <2> onlfi_vfms_logf: INF - --- End of file
   /var/tmp/VfMSCAA5YaqqJ
   09:30:35.576 [18050] <2> onlfi_vfms_logf: INF - --- Dumping file
   /var/tmp/VfMSDAA6YaqqJ (stderr):
   09:30:35.576 [18050] <2> onlfi_vfms_logf: INF -     VxVM vxsnap INFO
   V-5-1-6168
    Volume PFIvol1_00 does not require any syncing
   
   09:30:35.577 [18050] <2> onlfi_vfms_logf: INF -
   
   09:30:35.577 [18050] <2> onlfi_vfms_logf: INF - --- End of file
   /var/tmp/VfMSDAA6YaqqJ
   09:30:35.577 [18050] <32> onlfi_fi_split: FTL - VfMS error 11; see following
   messages:
   09:30:35.577 [18050] <32> onlfi_fi_split: FTL - Fatal method error was
   reported
   09:30:35.577 [18050] <32> onlfi_fi_split: FTL - vfm_freeze_commit: method:
   FlashSnap, type: FIM, function: FlashSnap_freeze_commit
   09:30:35.577 [18050] <32> onlfi_fi_split: FTL - VfMS method error 3; see
   following message:
   09:30:35.577 [18050] <32> onlfi_fi_split: FTL - do_cmd: Command failed with
   status=40: /usr/sbin/vxadm -g fs snap syncstart source=PFIvol1_00  
   </dev/null >
   /var/tmp/VfMSCAA5YaqqJ 2>/var/tmp/VfMSDAA6YaqqJ  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET296006

Description:  
   Advanced Client offhost backups of EMC/PowerPath failed with a bpbkar
   Status 11.  The following log was generated:
   
   bpbkar log:
   15:12:09.286 [12600] <4> bpmap_file_seg: INF - bpmap_file: map: sizeleft
   1007616 off 0, ents 0
   15:12:09.286 [12600] <16> bpmap_file_seg: ERR - VfMS error 20; see  
   following
   messages:
   15:12:09.286 [12600] <16> bpmap_file_seg: ERR - Method name is invalid
   15:12:09.286 [12600] <16> bpmap_file_seg: ERR - vfm_fm_init: Cannot find
   file mapping handle for device: 56885291
   15:12:09.286 [12600] <16> bpmap_file_seg: ERR - bpmap_file failed: err 20
   15:12:09.287 [12600] <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 11:
   system call failed
   15:12:09.287 [12600] <4> bpbkar Exit: INF - EXIT STATUS 11: system call  
   failed  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET297660

Description:  
   The v41.1.127 VxMS release level contains fixes for two problems.  The first
   fix enables DLM to work with FlashBackup on Windows. The second fix prevents
   the VxMS function, vfm_readdir, from looping.  

   All NetBackup Windows Clients  
--------------------------------------------------------------------------------
Etrack Incident = ET194804

Description:  
   FlashBackup, using a FlashSnap alternate client snapshot method, fails on  
   Windows 2000 and Windows 2003.  

   All NetBackup Windows Clients  
================================================================================



=============
NB_ADC_50_4_M
=============
Description:  
   During incremental backups using FlashBackup, the child process to generate  
   catalog entries could core dump, resulting in a log entry like this:
   
   11:42:38.632 [9672] <4> bpfsmap: INF - pass_4: pass4 completion time: 1
   11:42:38.633 [9672] <4> bpfsmap: INF - bpfsmap: calling childwait(18646)
   11:42:50.530 [9672] <4> bpfsmap: INF - childterm: failed=18646 exit=0  
   signo=11
   core=yes
     

   (NetBackup Clients:  HP Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:  
   Some FlashBackup backups took longer using NetBackup 5.0 than they did for
   NetBackup 3.4 because of the overhead created by the binary catalog.  

Workaround:  
   You can raise the maximum files per add value by placing a value of 95000  
   in the file /usr/openv/netbackup/MAX_FILES_PER_ADD. This raises the limit  
   not only for FlashBackup but for all backups.  

Additional Notes:  
   For FlashBackup only, this patch raises the number of files added per call  
   to the catalog from 500 to 95000. You can modify this limit by putting the  
   desired value in file /usr/openv/netbackup/FBU_MAX_FILES_PER_ADD, which  
   only affects FlashBackup backups.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:  
   A system panic occurred when a snapshot was being closed at the same time  
   as another snapshot using the same cache partition was being read. The  
   panic occurred because the partition was a DRL-enabled (Dirty Region  
   Logging) VxVM volume that had not been opened by the snap driver, and the  
   DRL threads were being destroyed while the read was attempting to access  
   them.  

Workaround:  
   Remove support for DRL from the cache partition if it is a VxVM volume.  

   (NetBackup Clients:  Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:  
   Storage Foundations 4.0 full-sized instant snapshots don't work if the  
   policy snapshot method is set to FlashSnap.
   
   The following is reported in the online_util log, if the volume has full-
   sized instant snapshots and the policy's snapshot method is FlashSnap.
   
   
   9:30:35.576 [18050] <2> onlfi_vfms_logf: INF - --- Dumping file
   /var/tmp/VfMSCAA5YaqqJ (stdout):
   09:30:35.576 [18050] <2> onlfi_vfms_logf: INF - --- End of file
   /var/tmp/VfMSCAA5YaqqJ
   09:30:35.576 [18050] <2> onlfi_vfms_logf: INF - --- Dumping file
   /var/tmp/VfMSDAA6YaqqJ (stderr):
   09:30:35.576 [18050] <2> onlfi_vfms_logf: INF -     VxVM vxsnap INFO
   V-5-1-6168
    Volume PFIvol1_00 does not require any syncing
   
   09:30:35.577 [18050] <2> onlfi_vfms_logf: INF -
   
   09:30:35.577 [18050] <2> onlfi_vfms_logf: INF - --- End of file
   /var/tmp/VfMSDAA6YaqqJ
   09:30:35.577 [18050] <32> onlfi_fi_split: FTL - VfMS error 11; see following
   messages:
   09:30:35.577 [18050] <32> onlfi_fi_split: FTL - Fatal method error was
   reported
   09:30:35.577 [18050] <32> onlfi_fi_split: FTL - vfm_freeze_commit: method:
   FlashSnap, type: FIM, function: FlashSnap_freeze_commit
   09:30:35.577 [18050] <32> onlfi_fi_split: FTL - VfMS method error 3; see
   following message:
   09:30:35.577 [18050] <32> onlfi_fi_split: FTL - do_cmd: Command failed with
   status=40: /usr/sbin/vxadm -g fs snap syncstart source=PFIvol1_00  
   </dev/null >
   /var/tmp/VfMSCAA5YaqqJ 2>/var/tmp/VfMSDAA6YaqqJ  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Description:  
   In a Standard policy, on HP-UX 11.11, a TimeFinder snapshot backup results  
   in a bpfis core dump. In addition, bpfis creates a failure for SYMAPI  
   versions that are lower than 5.0.  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Description:  
   On a Windows client, the System Volume Information directory is causing the
   file system verification for Point-in-Time rollback check #2 to fail. The
   function of check #2 is to make sure that all of the files in the restore
   file list exist in the snapshot.  

Workaround:  
   On the restore user interface, check "Overwrite the existing file" to skip
   the file system verification for Point-in-Time rollback.  


=============  
NB_ADC_50_3_M
=============  

================================================================================
Description:  
   There was a 32 bit to 64 bit disk address conversion problem when a soft  
   link target exceeded the 96 bit immediate data length for a VxFS inode that
   required a disk block to be read to get the target.  This caused the link
   file backup to be aborted.  If enough of these types of links existed, the
   entire backup would be aborted.  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Description:  
   When backing up multiple volumes with EMC TimeFinder snapshot method,
   and the volumes have VxVM mirrors, the snapshot of the second volume will
   fail.  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Description:  
   The following message was changed from:
   
   "frozen image processing failed, status ...."  
   
   to
   
   "snapshot processing failed, status  ....".  

   All NetBackup Windows Clients HP Solaris  
--------------------------------------------------------------------------------
Description:  
   VxFS_Checkpoint rollback fails on a VCS cluster.  The backup progress and  
   online_util logs look like the following examples.
   
   backup progress log:
   11:43:08 (95.001) FTL - Command failed, status  
   =24: /usr/openv/netbackup/bin/bpfis restore -id hechianb_1084982114 /cfs1  
   >/dev/null  2>/dev/null
   11:43:09 (95.001) FTL - Unable to rollback file system /cfs1 - can not  
   unmount
   
   online_util log:
   11:43:02.263 [4287] <2> onlfi_vfms_logf: INF -  
   umount_ops: /sbin/umount /cfs1
   </dev/null >/var/tmp/pfi_vAAA3Ra4xi 2>/var/tmp/pfi_vBAA4Ra4xi
   11:43:02.331 [4287] <2> onlfi_vfms_logf: INF - umount_ops: Umount failed  
   with:1: Not owner.
   11:43:02.332 [4287] <2> onlfi_vfms_logf: INF - vxfs_ckpt_thaw: cannot  
   umount the file system /cfs1(/dev/vx/dsk/cfs_dg/cfs_vol_01)  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Description:  
   EMC FIM needs to work in Symmetrix Remote Data Facility (SRDF)/concurrent  
   Business Continuance Volume (BCV) replication environment .
   
   In an SRDF (EMC version of remote replication) and concurrent BCV
   environment, two items need to added:
   1. Select the correct BCV from two concurrent BCVs.  
   2. Need to skip locking the primary device. This device has been locked  
      by SRDF.  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Description:  
   File system verification for Point-in-Time rollback restores passes on  
   Windows client when there are new files on the file system.  File system
   verification for Point-in-Time rollback also restores passes when the
   restore list does not match the file list on the snapshot.  In both cases,
   file system verification should fail.  

   (NetBackup Clients:  HP Intel-NT Solaris )
--------------------------------------------------------------------------------
Description:  
   Point in Time rollback is failing the file system verification check #2.
   The purpose of this verification check it to make sure that all the files
   specified in the restore list exist on the snapshot backup.  

   (NetBackup Clients:  Intel-NT Solaris )
--------------------------------------------------------------------------------
Description:  
   On a Windows client, the System Volume Information directory is causing the
   file system verification for Point-in-Time rollback check #2 to fail. The
   functions of Check #2 is to make sure that all of the files in the restore
   file list exist in the snapshot.  

Workaround:  
   On the restore user interface, check "Overwrite the existing file" to skip
   the file system verification for Point-in-Time rollback.  

   (NetBackup Clients:  HP Intel-NT Solaris )
--------------------------------------------------------------------------------
Description:  
   A standard TimeFinder FIM backup on HP-UX 11.11 results in a bpfis core
   dump.  In addition, bpfis creates a failure for SYMAPI versions that are
   lower than 5.0.  

   (NetBackup Clients:  HP Solaris )
================================================================================


=============
NB_ADC_50_1_M
=============
Description:  
   The snaplist command core dumps if there are 64 or more active snapshots.  

   (NetBackup Clients:  Solaris )
--------------------------------------------------------------------------------
Description:  
   A Flashbackup backup will terminate if a file in the file system has an
   access control list (ACL) with this entry in the bpbkar log:
   
   "<32> bpfsmap: FTL - ufs_get1inode: assertion failed (at ufsmap1.c.182)"  

   (NetBackup Clients:  Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:  
   bpbkar would core dump at the start of changed block processing for
   offhost backups using fsclone as the frozen image.  

   (NetBackup Clients:  HP Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:  
   The backup of VxFS attributes was previously turned off because of problems
   with the restore. The restore problems have been corrected, so the backup is
   being enabled again.  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Description:  
   A backup using VxFS_Snapshot as the Snapshot method caused a core dump in
   bpfis if the file system was not mounted.  

   (NetBackup Clients:  HP Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:  
   The online_util log is flooded by a warning message that may cause a slow  
   down during a FIM backup. This unnecessary warning message has been  
   removed to resolve this issue.  

   (NetBackup Clients:  HP Solaris )
--------------------------------------------------------------------------------
Description:  
   FlashBackup, configured with CACHE=/dev/rdsk/cxtxdxsx, should be  
   prevented to backup a cfs (clustered) file system, because the nbu_snap  
   driver cannot handle a cluster mount.  

   (NetBackup Clients:  HP Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:  
   The following enhancements have been added to snapshot backups:
   1. Performance improvement for the EMC TimeFinder snapshot method
   2. Improved snapshot error handling during creation and deletion
   3. Improved multistreaming coordination with snapshot
   4. Improved error logging
     

   (NetBackup Clients:  HP Intel-NT Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:  
   1. If a vxvm snapshot is mounted and the umount operation fails, the  
   rollback operation should abort.    
   2. Need to use VxFS CFS mount/umount command, cfsmount/cfsumount to  
   mount/umount a VxFS CFS file system during the rollback operation.  

   (NetBackup Clients:  HP Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:  
   When resuming a suspended backup job with Windows Open File Backup enabled,  
   the resumed backup will not re-use the original backup job's volume  
   snapshots. Instead, if the WOFB Error Control configuration setting was set  
   to Abort on Error, the resumed backup job will abort and a status 156-
   snapshot error will be encountered. If the WOFB Error Control configuration  
   setting was set to Disable Snapshots & Continue, the resumed backup job  
   will be resumed without any volume snapshots. This behavior is not correct  
   and the resumed backup job should re-use the original, suspended backup  
   job's snapshot volumes if they were successfully created.  

   All NetBackup Windows Clients HP Solaris Solaris9  
--------------------------------------------------------------------------------
Description:  
   The Volume Shadow Copy Service (VSS) frozen image method is not included in  
   the drop-down list in an Oracle policy.  

   (NetBackup Clients:  HP Intel-NT Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:  
   Dynamic browsing and restore fail for VxFS_Checkpoint snapshot backup with  
   Instant Recovery option on VxFS Cluster File System.  

   (NetBackup Clients:  Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:  
   VxFS file promotion does not support alternate location restore. A check is  
   required for Instant Recovery restore, for alternate location restore, file  
   promotion method needs to be turned off.
     

   (NetBackup Clients:  Solaris )
--------------------------------------------------------------------------------
Description:  
   IR backup(disk only) failed due to error of generating catalog info.
   The online_util log:  
   09:12:39.415 [2140.604] <32> add_catalog_info: Cannot lstat SE. Errno =  
   2: No such file or directory
   
   It tried to catalog a keyword "SNAP ID <Backup_id>" and failed stat64().
     
   (NetBackup Clients:  HP Intel-NT Solaris )
--------------------------------------------------------------------------------
Description:  
   VxFS checkpoint backup with Instant Recovery option restore fails on HP_UX  
   clients.  

   (NetBackup Clients:  HP )
================================================================================