Maintenance Pack NB_51_3A_M.winnt.intel.exe provides fixes to the VERITAS NetBackup (tm) Enterprise Server / Server 5.1 on NT/2000/2003/XP Professional server and clients. It also contains fixes for NetBackup Add-on products and Database Agents.

Article:TECH42582  |  Created: 2006-01-13  |  Updated: 2006-01-13  |  Article URL http://www.symantec.com/docs/TECH42582
Article Type
Technical Solution


Environment

Issue



Maintenance Pack NB_51_3A_M.winnt.intel.exe provides fixes to the VERITAS NetBackup (tm) Enterprise Server / Server 5.1 on NT/2000/2003/XP Professional server and clients. It also contains fixes for NetBackup Add-on products and Database Agents.

Solution



 NB 5.1GA Pack NB_51_3A_M README                                    July 11, 2005
================================================================================
This Maintenance Pack provides fixes to the VERITAS NetBackup NT server and  
clients.  It also contains fixes for NetBackup Add-on products, Database  
Agents, and NetBackup Encryption.  To download this maintenance pack,
click below on the "Download Now" link.

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.

Starting with this release, Symantec Corporation officially supports WORM tape with  
VERITAS NetBackup. A white paper has been written describing this feature and can
be downloaded from the Symantec Support Web site by searching for TechNote
number 271889.


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

    -- For the latest robotics support please also download and install the  
       latest Mappings_5.1.<6 digit number>.zip from the Support Web site:
       www.support.veritas.com.


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

=========================
I. DOWNLOAD INSTRUCTIONS
=========================
This is an update to NetBackup/Media Manager products
with the latest fixes for Windows NT NetBackup servers.

Download instructions:
1) Download the NB_51_3A_M.winnt.intel_<6 digit number>.exe file
  into a temporary directory.

  where <6 digit number> is an internal tracking identifier

2) Extract the NB_51_3A_M.winnt.intel_<6 digit number>.exe
  by double-clicking on it.

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


=================
II. KNOWN ISSUES
=================
Description:
   ATTENTION:  A related TechAlert exists for this issue.  Refer to the
   "Related Documents" section below for more details.
   
   NetBackup 5.1 Maintenance Pack 3 contains a condition under which data loss
   may occur. This data loss may occur if the following conditions are true:
   
   NOTE: This issue only affects duplicate images using NetBackup 5.1_MP3.  
   The original or "source" image remains valid.  
   
   1. The original backup image must be written to tape.  Virtual Tape
   Libraries (VTL) will be affected by this as well.  Disk-based backups are
   not affected by this issue.
   
   2. The original backup image must span more than one fragment.  This would
   be caused when multiplexing is enabled, when a backup image spans more than
   one tape, when the maximum fragment size is reached, or when a checkpoint
   occurs for checkpoint-restart backups.
   
   3. The image must be a duplicate image and meet one of the following conditions:
      - The source image was not multiplexed on tape.
      - The duplication is performed with the "Preserve Multiplexing" option
        disabled.
   
   If all the criteria above apply, then the second and subsequent copies of
   backup images created by the duplicate operation will be written incorrectly.  


Description:
   For VSP users, a reboot will be required before the latest VSP fixes  
   will take effect.


===============================
III. INSTALLATION INSTRUCTIONS
===============================
NOTE: For Maintenance Pack installation on Windows Cluster Environment:

1) Install this Maintenance Pack on the inactive node(s) of the cluster  
  (follow steps 1-4 below)

2) Move the group from the active node to another node.
  This should be done when the NetBackup system is quiet, i.e. no backups
  or restores running.

3) Install this Maintenance Pack on the newly inactive node of the cluster

4) (Optional) Move the NetBackup group back to the original node.

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

Installation steps:

1) Close all NetBackup Windows.
  Make sure the NetBackup system has no active backups, restores,
  duplications, etc., running. If there are NetBackup activities in process,
  the Maintenance Pack will require a reboot 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
  installed.

2) Run Setup.exe (Double-click on the icon from File Manager or Explorer or run
  it from the command prompt)

  Setup.exe begins by stopping the appropriate NetBackup Services required for
  the Maintenance Pack installation. Next, it will install the necessary files  
  into their correct locations. Lastly, Setup.exe will restart the appropriate  
  NetBackup services.

3) Examine the <TEMP>.Log file to ensure that no errors took  
  place during the installation.

4) Remove the temporary directory created in the download instructions.

Note: If you are installing the Maintenance Pack using the silent install script,
please review the <TEMP>.Log after the installation is finished,
a reboot maybe required to complete the installation of the Maintenance Pack.  A
search of the log for the key words "in use" will indicate which files were busy
during the installation.

For Encryption users:  Do the following on the Windows Master that has  
Encryption installed on it:

1) Install the NetBackup 5.1 MP3A Windows patch (NB_51_3A_M) on the master.

2) You must then push the patch to the clients that have encryption installed.


===========================
IV. UNINSTALL INSTRUCTIONS
===========================
**Important notice regarding un-installs on Windows**
Only the last Maintenance Pack installed on a Windows system
can be un-installed.  

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 Maintenance Pack 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
  installed.

2) Go to Add/Remove programs dialog box and select correct Pack to be uninstalled.  

For Encryption users:

You will need to push out restored binaries to affect encryption clients  


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

README Conventions :

Description
    Describes particular problem or feature contained in this Maintenance  
    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 the "best practice" of being at the latest patch level.

Additional Notes  
    Any additional information regarding this problem or feature.


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

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

Etrack Incident = ET384887

**Description:  **
   ATTENTION:  A related TechAlert exists for this issue.  Refer to the
   "Related Documents" section below for more details.
   
   NetBackup 5.1 Maintenance Pack 3 contains a condition under which data loss
   may occur. This data loss may occur if the following conditions are true:
   
   NOTE: This issue only affects duplicate images using NetBackup 5.1_MP3.  
   The original or "source" image remains valid.  
   
   1. The original backup image must be written to tape.  Virtual Tape
   Libraries (VTL) will be affected by this as well.  Disk-based backups are
   not affected by this issue.
   
   2. The original backup image must span more than one fragment.  This would
   be caused when multiplexing is enabled, when a backup image spans more than
   one tape, when the maximum fragment size is reached, or when a checkpoint
   occurs for checkpoint-restart backups.
   
   3. The image must be a duplicate image and meet one of the following conditions:
      - The source image was not multiplexed on tape.
      - The duplication is performed with the "Preserve Multiplexing" option
        disabled.
   
   If all the criteria above apply, then the second and subsequent copies of
   backup images created by the duplicate operation will be written incorrectly.  

   (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------

Etrack Incident = ET264044

Description:  
   In the Windows NetBackup Administration Console, there was a timing issue
   that caused the display to show multiple instances of the same physical
   drive when there should have been one line entry per physical drive in an
   SSO environment.  

   (All NetBackup Servers: Intel-NT Intel64)
--------------------------------------------------------------------------------
Etrack Incident = ET295113

Description:  
   The scheduler was modified to correctly process a status 134 error - race  
   condition in a multiplex backup.
   
   This condition occurred when a multiplex child bpsched started a backup,
   but the storage unit was over committed. A status 134 error was sent back
   to the multiplex child bpsched, but the child sched was already adding
   another backup to the multiplex group.
   
   The child sched attempted to send the new jobs information to bpbrm, but  
   bpbrm had exited and the connection was defunct. The scheduler was
   incorrectly logging the defunct connection in the job progress log. With
   this change, the scheduler will not log the broken socket, but will
   correctly read and process the status 134 from the in-bound connection.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET270622 ET270620

Description:  
   There are cases when a NetBackup administrator can administrate most things
   on a NetBackup master server (such as policy configuration), but is not
   allowed to access Host Properties on clients.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET294713

Description:  
   An problem occurred that caused bpretlevel loops to echo the word, "What?,"
   when changing retention levels.  No input seemed to be a satisfactory
   response to exit the loop until a ctrl-C was entered.  
   
   Solution:
   
   An earlier change had changed all occurrences of gets() to fgets(), but
   failed to recognize that fgets() will return the '', whereas gets()
   did not.  The subsequent strcmp was not expecting the '', and
   always failed.  The solution was to strip the [new] trailing '' to
   emulate the gets() behavior.  

   (All NetBackup Servers)

--------------------------------------------------------------------------------
Etrack Incident = ET265653 ET295655

Description:  
   Oracle Advanced Client FlashBackup backups did not work with the new  
   128-bit Encryption.  The failures produced an error status 25 - cannot
   connect on socket.  The bpfis debug log included messages similar to the
   following:
   
   17:14:27.139 [13628] <16> bpfis main: FTL - snapshot creation failed,  
   status 25
   17:15:19.842 [13628] <4> bpfis Exit: INF - EXIT STATUS 25: cannot connect  
   on socket  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET278777 ET272628

Description:  
   Database agent backups may fail if 128/256-bit Encryption is used and vnetd
   "connect-backs" to the media server is used.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET278777 ET272628

Description:  
   Database agent backups may fail if 128/256-bit Encryption is used and vnetd
   "connect-backs" to the media server is used.  

  ( All NetBackup Windows Clients All NetBackup UNIX Clients)  
--------------------------------------------------------------------------------
Etrack Incident = ET287818

Description:  
   The bpimmedia -spangroups output was not displaying a span group if the  
   span occurred in a copy other than copy 1, and one or more preceding copies
   were expired.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET287614

Description:  
   A Synthetic Backup Image could be expired while it was still being written.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET210298

Description:  
   Backups of NDMP clients were not displaying intermediate directories when
   browsing the backup contents.  For example, if directory A/B/C was backed
   up, /A and /A/B were not appearing when browsing the backup.
   
   Although the NetBackup catalog contained the directory information, it did
   not return it when the directory was not explicitly backed up.  This fix
   will enable browsing of these NDMP backups even if they were created prior
   to the fix.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET297819

Description:  
   The VxBSA global Handles[] and debugFD were not thread safe.
     

   (NetBackup Clients:  ALPHA HP Intel-NT Linux2.4 RS6000_51 SGI Solaris Solaris9 )
--------------------------------------------------------------------------------
Etrack Incident = ET296425

Description:  
   This bpbrm binary fixes an intermittent socket problem that occurred
   during database backups.  The backup would fail with a status of 54.
   
   An examination of the bpbrm debug log showed the following type of message:
   
   07:10:52.662 [3832.2768] <16> bpbrm listen_for_client: listen for client  
   timeout during accept from name listen socket after 60 seconds  
   
   An examination of the dbclient debug log showed the following type of  
   message:
   02:24:07.956 [528.660] <8> connectSock: WRN - connect() to server failed,  
   
   No connection could be made because the target machine actively refused it.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET266316

Description:  
   If the server's root/administrator password was more than eight characters,
   the "set_ndmp_attr -verify server" for remote NDMP would fail.  

   (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET271314

Description:  
   When using encryption of blowfish, set_ndmp_attr of ndmpmoveragent would
   fail with the following data.
       
   [root@galvatron]:/:>set_ndmp_attr -verify
   Verify Host name: galvatron
   Connecting to host "galvatron" as user "root"...
   Waiting for connect notification message...
   Opening session--attempting with NDMP protocol version 2...
   Opening session--successful with NDMP protocol version 2
   host supports TEXT authentication
   Logging in using TEXT method...
   17:44:53.152 [03044] ndmp_net_read: connection 0x3e0d0: (5) end of file
   detected
   17:44:53.153 [03044] ndmp_message_receive: xdr_ndmp_header failed, unable  
   to
   XDR decode  
   ndmp_connect_client_auth failed
   set_ndmp_attr: host "galvatron" failed
   NDMP failed to verify host
     

   (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET292567

Description:  
   Added support for DB2 Stinger.  

  (All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET299102

Description:  
   During a Single Instance Store (SIS) backup of Exchange Mailboxes, one of  
   the attachments failed to backup.  Bpbkar logged the following information
   when this issue was encountered.  
   
   2:04:36.288 AM: [5536.424] <2> ov_log::V_GlobalLog: INF -  
   v_beds_mbox::V_FindNextSpcDblk() ENTER Index:2177
   2:04:36.288 AM: [5536.424] <2> ov_log::V_GlobalLog: INF -  
   v_beds_mbox::V_FindNext() EXIT
   Name:F3168B482D6B4C10172E7DC743C7EE24C833F65189C456FD bRC:true  
   LastError:0x0:
   2:04:36.288 AM: [5536.424] <2> tar_backup::backup_startfile_state: TAR -
   Backup: Microsoft Exchange
   Mailboxes:-Attachments_B482D6B4C10172E7DC743C7EE24C833F65189C456FD
   2:04:36.288 AM: [5536.424] <2> ov_log::V_GlobalLog: INF - StreamInfo  
   Id:MBMG
   FSAttrib:0x0 FSAttrib:0x2 CAlgor:0x0 Flags:0x0 Size:0
   2:04:36.304 AM: [5536.424] <2> ov_log::V_GlobalLog: INF - Exchange Mailbox
   Stream Data
   2:04:36.351 AM: [5536.424] <2> tar_base::V_vTarMsgM: FIL - 498621 105973
   6202357 92 33216 root root 5165926 1098296973 1098296973  
   1098296873 /Microsoft Exchange
   Mailboxes/_Attachments_/F3168B482D6B4C10172E7DC743C7EE24C833F65189C456FD
   2:04:36.351 AM: [5536.424] <2> ov_log::V_GlobalLog: INF -
   v_beds_mbox::V_FindNextSpcDblk() ENTER Index:2178
   2:04:36.351 AM: [5536.424] <2> ov_log::V_GlobalLog: ERR -
   v_beds_mbox::V_FindNextSpcDblk():FS_GetSpecialDBLKS() Index:2179 Failed!
   0xFFFFFEA9:0xa000fea9 (2684419753)
   2:04:36.351 AM: [5536.424] <2> ov_log::V_GlobalLog: INF -  
   v_beds_mbox::V_FindNext() EXIT Name: bRC:false  
   LastError:0xFFFFFEA9:0xa000fea9
   (2684419753)
   
   When this error was encountered, the Exchange mailbox SIS backup was
   aborted without attempting to backup any additional attachments. A status 1
   was returned for the backup.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET275116

Description:  
   With the Vault option installed on a UNIX Master server, the Vault user was
   unable to eject Deferred Eject media of Vault in a cross-platform  
   configuration. This operation was failing with vault log status "Invalid  
   command parameter".  

Workaround:  
   Using the Java GUI (jnbSA), you can perform a Deferred Eject operation of
   Vault.  

Additional Notes:  
   None  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET299437

Description:  
   An extended value (90 days, for example) for the "Keep Logs for x Days"  
   global configuration setting appears not to work.  The debug logs are  
   still deleted after about a month on NetBackup media servers that
   are included as part of the catalog backup configuration.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET300772

Description:  
   Restoring images in UNC format on the network failed, when the Java Console
   was used.  

   (NetBackup Clients:  Intel-NT Intel64 )
--------------------------------------------------------------------------------
Etrack Incident = ET295588

Description:  
   
   When the eject step for a Vault session is partially successful, the media
   that are ejected successfully are listed in the Non-vaulted Images report
   for that session.  With this fix, ejected media are no longer listed in the
   Non-vaulted Images report.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET299670 ET300174 ET300175 ET300176

Description:  
   bpbrm would hang if a database agent backup failed in a certain way.
   The job would appear to be running in the Activity Monitor until an
   administrator terminated it.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET294505

Description:  
   Raw partition backups would fail if a mount point was created using
   mountvol in the bpstart script.  If the mount point existed prior to the
   backup being initiated it would work fine.  

  (All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Etrack Incident = ET301501

Description:  
   A Scheduler race condition was occurring: Child sched was sending a ¿done¿
   to the main sched while the main sched was sending a ¿term one¿ to the
   child sched. The child sched would erroneously treat the ¿term one¿ as the
   response to the ¿done¿ and then exit prematurely.
   
   The correct child response is to discard (ignore) the ¿term one¿
   request and wait for the main sched response to the 'done' command.
   
   Also missing was code to discard (ignore) a ¿suspend¿ request after having  
   sent a 'done' to the main sched.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET279288

Description:  
   When backing up files on Windows that contain extended attributes,  
   bpbkar32.exe may crash.  

  ( All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Etrack Incident = ET300757

Description:  
   Interval-mode backup windows open longer than 6-days (144-hrs) resulted in
   continuous backups on the seventh day, till the window closes.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET277470

Description:  
   Creating a long name in the hosts file and using that in a policy causes  
   various parts of BEDS to crash.  

Workaround:  
   Ensure all names used to reference the host are 15 or fewer characters in  
   length  

   (All NetBackup Windows Clients)  
--------------------------------------------------------------------------------
Etrack Incident = ET299481

Description:  
   ltid on Linux, when starting up vmd, causes the following to be logged  
   in /var/log/messages:
   
   kernel: application bug: vmd(16703) has SIGCHLD set to SIG_IGN but calls  
   wait().
   kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET234558

Description:  
   Tapes can be ejected by the expiration date and not just alphabetically.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET271701

Description:  
   An incorrect STATUS_ROBOT_BUSY message caused the eject process to stay
   active and idle, and prevented other Vault operations from running.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET273779

Description:  
   Removed the check which was causing the error dialog to pop up. This check  
   was not required.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET274190

Description:  
   The VxFS team changed their implementation of ACLs on VxFS file systems on
   the AIX platform.  NetBackup has also changed to handle this new
   implementation.  

   (NetBackup Clients:  RS6000_433 RS6000_51 )
--------------------------------------------------------------------------------
Etrack Incident = ET302288

Description:  
   When bpcd failed to connect on Windows NT it would fail rather than try to
   connect again.  

  ( All NetBackup Windows Clients)  
--------------------------------------------------------------------------------
Etrack Incident = ET234715

Description:  
   When doing a consolidated eject for a vault job that contains multiple
   media types, all media are ejected, but only the media from one media type
   are changed to the off-site volume group. The media from the other media
   types remain in the robotic volume group.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET302801

Description:  
   In the Windows Administration Console Activity Monitor node, a crash would
   occur when viewing the job details dialog for some synthetic backup jobs.  

   (All NetBackup Servers: Intel-NT Intel64)
--------------------------------------------------------------------------------
Etrack Incident = ET299843

Description:  
   Bptm, bpdm, or bpdbm would occasionally crash during TIR incremental
   backups.  Bprd, bpbrm, or bpsched were possibly affected as well.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET302767

Description:  
   The NetBackup Windows Administration Console will crash when attempting to
   view certain jobs details in the Activity Monitor.  

   (All NetBackup Servers: Intel-NT Intel64)
--------------------------------------------------------------------------------
Etrack Incident = ET270191

Description:  
   Vault reports status 281 if a duplication job fails for a some of the  
   images images. With this fix, the correct status code (1 - partially  
   successful) is reported.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET302164 ET287318

Description:  
   Vault can take an extremely long time to complete the media going off-ete the media going off-site
   reports if the NetBackup catalog is large. Vault searches the entire image
   database to determine which images are on the ejected media.
   
   You can limit the search range for images by specifying a start date for  
   the search.  This can reduce the amount of time to generate reports  
   because Vault will search fewer image database records to determine which
   images are on the ejected media.
   
   To limit the search, create the following file and include in the file the
   number of days before the profile runs to search for images to include in
   media going offsite reports:
   
   (UNIX) /usr/openv/netbackup/bin/VLT_MGO_RPT_IMG_INCL_WINDOW_START
   
   (Windows) install_path_MGO_RPT_IMG_INCL_WINDOW_START
   
   The file should contain one number only; if the file is absent or its  
   contents cannot be read, Vault uses the default behavior (searching the  
   entire database).
   
   Specifying a value does not affect whether media are ejected and
   vaulted; however, if a volume is ejected that has an image on it older
   than the period you specify, that image will not be listed on the media
   going off-site reports.  

Additional Notes:  
   This problem has been reported on Windows.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET266612

Description:  
   When performing backups that collect disaster recovery information, the
   collection of the disaster recovery information may be failing.  Upon
   further investigation, it may be because drfile.exe is crashing on the
   client system.  

   (All NetBackup Windows Clients)  
--------------------------------------------------------------------------------
Etrack Incident = ET299846

Description:  
   Multiplexed backup jobs would occasionally hang.  This would happen if the  
   bptm or bpdm parent process crashed, or if bptm could not successfully add  
   the TIR fragment for a TIR backup.  It may also happen because of a timing
   problem in bpbrm when new jobs are started.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET279287

Description:  
   When performing IDR on a system and the backup images are encrypted,  
   statements similar to the following may be seen in the progress log:
   
   WRN - File is 56-bit DES encrypted, but no decryption key is available
   INF - TAR EXITING WITH STATUS = 5  

Additional Notes:  
   After applying this patch, the DR files for the machines whose backup  
   images have been encrypted need to be recreated.
   
   If the machine is in a state where IDR is being performed, the patch can  
   be installed on a different machine and then the files can be manually  
   copied over to the IDR machine.  

  (All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Etrack Incident = ET289069

Description:  
   When Backing up more than 255 databases within the .bch file, the Backup  
   would fail on job 255.  

   (All NetBackup Windows Clients)  
--------------------------------------------------------------------------------
Etrack Incident = ET303188

Description:  
   When ejecting an ACS tape using the Windows Administration Console, the  
   eject would hang if you did not select the first CAP in the drop-down list.  

   (All NetBackup Servers: Intel-NT Intel64)
--------------------------------------------------------------------------------
Etrack Incident = ET163066

Description:  
   When backing up Lotus Notes databases, some databases were skipped.  These
   skipped databases were not reported as an error; the backup exited with a
   status 0 instead of a status 1.  

  ( All NetBackup Windows Clients Linux2.4 RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET292021

Description:  
   A new bperror -jobgroupid option is introduced to search the error database
   based on the job group ID.  This is helpful for an Inline Tape Copy job  
   because it may log to multiple job IDs.  
   
   The syntax of the option is:
   
   -jobgroupid job_group_id
   
   where job_group_id is the job group ID number for the job.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET303111 ET301828 ET275764 ET293905 ET279264 ET284804 ET285117 ET270133 ET295671 ET295695

Description:  
   Added support for the following libraries:
   
   EXABYTE VXA-2 1x10 Autoloader
   EXABYTE 1x7 Autoloader
   
   Added support for the following drives:
   
   EXABYTE VXA-2
   HP VS160
   STK VDRIVE
   
   Updated the following libraries:
   
   COMPAQ TL895
   DEC TL810
   DEC TL895
   HP MSL6000
   HP MSL5000
   HP UHDL
   IBM 3583
   IBM 4560SLX
   IBM 7337
   SONY PETASITE CSM200/100/60  

Additional Notes:  
   Devices can be included in this file before they officially supported.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET293146

Description:  
   NetBackup processes may core if an error occurs. The stack from the core
   file showed the processes were in the ndmp_user_scsi() or ndmp_user_tape()
   functions.  

   (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET293664

Description:  
   You can now restore Backup Exec images to clustered applications on  
   Windows (such as, Microsoft Exchange).  

   (All NetBackup Windows Clients)  
--------------------------------------------------------------------------------
Etrack Incident = ET286656

Description:  
   bpverify would fail with a status 191 on a single master/media server  
   because of a socket timeout.  

Workaround:  
   To avoid this issue, do not run bpverify on very large backups with a slow
   or stressed network.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET266342

Description:  
   bplist returned duplicate listings for a DB2 file; and the .f file showed
   only one instance of the file. This problem did not occur for other similar
   client backups. If IMAGE_LIST file was removed, the file would be listed
   only once.  

Workaround:  
   To avoid this issue, turn off image indexing.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET303564 ET302345

Description:  
   The main sched failed to recognize a media server that was initially  
   off line, and then brought on line after the main sched went active.
   
   If the media server was brought back while the scheduler was not active or
   the master server was bounced, then everything worked correctly.
   
   This fix enables the scheduler to ¿pick up¿ the newly introduced media
   server by using the ¿/bp/bin/admincmd/bpschedreq ¿read_stunits¿ command.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET302345 ET303564

Description:  
   Backups using in line tape copy (ITC) and storage unit groups, failed to  
   give preference and select the local storage unit.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET270775

Description:  
   The IM filename format contains timestamp and the re-generation of IM
   reports is not allowed. This fix changes the IM filename to the following
   format: CustomerNumber_Vault_SID_C/V.IM.  
   
   In addition, the regeneration of IM reports is now allowed.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET234583

Description:  
   The lost media report does not report offsite tapes of a different media
   type. In a scenario where a customer migrates from one media type to
   another, the expiring offsite media of the old media type did not get
   reported in the lost media report or the picklist for vault report.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET293091

Description:  
   The NetBackup-MSSQL GUI encountered pop-up error message on the  
   IA64 platform. The error occurred when opening the GUI. The message is
   "DBBACKUP EXE encountered a problem and needed to close. This error
   occurred at 9/28/2004 at 12:15:23 PM. Please tell Microsoft about this  
   problem."  

   (All NetBackup Windows Clients)  
--------------------------------------------------------------------------------
Etrack Incident = ET299846

Description:  
   bpdbm crashed due to a problem in a CPR case.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET304308

Description:  
   Staging/Duplication from a disk staging unit was not working when more
   than 32765 files were in the staging area.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET304387

Description:  
   NBAR was missing jobs with Swedish (non-ascii) characters.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET304389 ET304390

Description:  
   The media_id field in the nbjobs table was not getting updated even though
   the backup completed successfully.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET208679

Description:  
   Encountered very long loader run times on large systems.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET269768

Description:  
   Added support for RedHat 3.0 on the Z-series platform.  This required a new
   client type which is called IBMzSeriesLinux2.4.21.  The number is based on  
   the operating system (OS) kernel.
   
   256-bit encryption will not be supported by this client, however, 40- and
   56-bit encryption are available.  

 (All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Etrack Incident = ET309104

Description:  
   The VxMS version v4.1.127 contains fixes needed by FlashBackup on Windows.
   These fixes include making FlashBackup on Windows function correctly with  
   DLM, and changes to the vfm_readdir function that fixes a problem when  
   creating the list of files to be excluded.  

   (All NetBackup Windows Clients)  
--------------------------------------------------------------------------------
Etrack Incident = ET309223

Description:  
   Backups were taking too long between job complete and 'end writing'.  
   To fix this problem, a correction was made to a recursive call in
   searching for a storage unit.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET308397 ET323253

Description:  
   Allow backing up over 1 terabyte of data for NDMP by breaking the backup
   into fragments.  

Additional Notes:  
   There is an option to disable NDMP large file support. To do disable this
   option, go to bp/db/config/ndmp.cfg and add the following:
   
   NDMP_LARGE_SUPPORT_DISABLE  

   (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET310953

Description:  
   Standard Encryption (128/256-bit encryption) and Check Point Backups are
   incompatible on Windows clients.  If you configure a Windows file system
   backup policy with both Standard Encryption and Check Points, the backups
   will fail.
   
   For small backups (generally less than 256K of data), the backups will fail
   with a status 90 error. For larger backups, the backups will generally
   finish with a status 0.  However, a verify of the backup image will fail.
   You will not be able to restore files from end of the backup image.  

Workaround:  
   To avoid this issue, do not use Encryption and/or Check Point in backup
   policies for Windows file systems.  

  (All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Etrack Incident = ET289123

Description:  
   Staging of images which were no longer in the catalog caused a 190 error.  

Workaround:  
   Manually delete images which are not in the catalog.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET287633

Description:  
   When simultaneous, differential, incremental backups are done for the same
   client, a subsequent synthetic backup for that client may fail.  

Workaround:  
   To avoid this issue, do not run simultaneous backups on the same client.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET313792

Description:  
   When there is a firewall between the server and the NAS filers, the backup
   would fail while writing the TIR data with connection timeout error.
   
   15:46:57.554 [29981] <2> setup_tir_read: successfully connected to bpdbm  
   to read TIR file, size is 577960 bytes + 0 GB
   15:46:57.554 [29981] <2> io_write_back_header: drive index 12,  
   grzfs03_nafsp02_vol0_1108477090, file num = 50, mpx_headers = 0, copy 1
   15:46:57.658 [29981] <2> io_write_block: ndmp_tape_write_func returned 1024
   15:46:57.758 [29981] <2> NdmpMoverClient: ndmp_mover_set_record_size(64512)
   15:46:57.858 [29981] <2> NdmpMoverClient: ndmp_mover_set_window(0,  
   18446744073709551615)
   15:46:58.058 [29981] <2> NdmpMoverClient: ndmp_mover_listen returned addr  
   10.200.12.10 port 12091
   15:50:42.667 [29981] <16> NdmpMoverClient: ERROR ConnectSocket - connect  
   failed: 145 Connection timed out
   15:50:42.667 [29981] <16> NdmpMoverClient: ERROR ConnectSocket failed
   15:50:42.668 [29981] <16> NdmpMoverClient: ERROR Start failed
   15:50:42.947 [29981] <2> NdmpMoverClient: mover halted reason  
   NDMP_MOVER_HALT_ABORTED
   15:50:42.948 [29981] <4> onnet010: NDMP_LOG_NORMAL 0 mover aborted by  
   client.
     

Additional Notes:  
   The cause of the problem is the server(using NDMP mover interface) cannot
   connect to the NAS filer's port because of the presence of a firewall.
   To avoid this issue, the user must disable the mover interface by inserting
   the following line in the file, /usr/openv/netbackup/db/config/ndmp.cfg.
   
   NDMP_MOVER_CLIENT_DISABLE  

   (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET314642

Description:  
   Client VSP custom settings were lost after upgrading from 5.0MP4.  Now  
   pack installer will only update VSP binaries.  

   (All NetBackup Windows Clients)  
--------------------------------------------------------------------------------
Etrack Incident = ET314580

Description:  
   A capitalization problem with the rename file when doing alternate
   restores of UNIX clients from the Windows PC Client GUI was fixed.  When
   restoring a pathname containing just one letter (for example, "/e") to an  
   alternate destination, the original pathname is now correctly capitalized
   in the rename file.  

   (All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Etrack Incident = ET319469

Description:  
   Restores to alternate locations were not working on Windows.  This was a
   regression introduced in NetBackup 5.1 MP2.  

   (All NetBackup Windows Clients)  
--------------------------------------------------------------------------------
Etrack Incident = ET321994 ET266342

Description:  
   While testing the NetBackup 5.1 MP3 patch, the ability to browse ASCII  
   catalogs did not exist.    

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET323188

Description:  
   Disk-staging of a directory with no images to stage causes the program to  
   terminate without informing its parent program that it has finished.
     

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET323222

Description:  
   Disk-staging only stages the one copy of an image in the directory.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET320557

Description:  
   When a resume backup exits, it would attempt to send a request queue  
   message to the GUI. But the GUI does not read these messages, so the  
   message would stay queued until the main sched exited.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET323183

Description:  
   If the stream in control snap failed on a WOFB, then the other streams were
   allowed to continue a non-snap backup. This was the correct operation. The  
   problem was that the non-control streams performed a backup of all files in
   the file list, but they should have only backed up their specific files.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET316635

Description:  
   User backups failed to check if an exiting backup was the last backup job
   from a specific SPID before removing all user backups from the work list.  
   This oversight caused the removal of active jobs from the work list, and
   resulted in a sched core.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET323827 ET324060

Description:  
   DSSU stage to tape fails with a status 134 if the media becomes full.
   A NON_MPX_RESTORE can cause bptm to select the wrong media during a restore
   operation that spans tape.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET303490 ET315602  ET324213  ET323143 ET323736 ET277364  ET315274

Description:  
   Added the following library:
   CERTANCE LTO3 CLL 6400
   
   Updated the following library entries:
   ADIC 10k
   ADIC Scalar 24
   ATL M2500
   ATL M1500
   Exabyte 480
   IBM 3583  

Additional Notes:  
   Devices can be included in this file before they are officially supported.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET324854

Description:  
   NDMP Snapmirror to tape backup would immediately fail.    

Workaround:  
   make sure
   set type=smtape
   is the first line in the policy's file listing  

   (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET315056

Description:  
   WORM tape support uses sixteen byte SCSI-3 commands.  Some HBA's have  
   problems with these commands, and can cause SCSI Bus Reset's.  A new touch  
   file, volmgr/database/NO_SIXTEEN_BYTE_CDB, can be created to disable these  
   commands.  This will effect your ability to use WORM tape with some drives.
   
   Solaris platforms have been found to not handle sixteen byte commands on  
   Parallel SCSI HBA's, so devices on these HBA's are automatically prevented  
   from using sixteen byte SCSI commands.  

Workaround:  
   To avoid this issue, use an HBA that supports sixteen byte commands.  

   (All NetBackup Servers)
================================================================================

=========
NB_51_2_M
=========
Etrack Incident = ET218330

Description:  
   The synthetic backup timing was incorrect because to the time it took to
   read the large extents.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET257821 ET232038

Description:  
   A large number of down storage units would result in and apparent scheduler
   hang. In reality, the scheduler was timing out to each media server in
   series. This fix recognizes and skips duplicate attempts to a down media
   server.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET220801

Description:  
   "Ghost" backup jobs were appearing in the activity monitor.  For example, a
   deleted backup job could (partially) re-appear in the activity monitor.  
   This would only happen to a deleted job that was one number lower than a
   multi-copy backup.
       
   And example of this scenario is:
   1) Job n finishes.
   2) Job n is deleted from the activity monitor.
   3) Multi-copy job n+1, n+2, n+3 finishes.
   4) Activity monitor incorrectly updates jobs n, n+1, n+2.
   5) Deleted job n (partially) re-appears.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET212797

Description:  
   The interrupt code paths for the Scheduler were simplified to eliminate
   scheduler core dumps because the interrupt handlers were too "noisy".  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET211907 ET210846

Description:  
   If an in-line copy backup is multiplexed, and one of the copies gets a  
   failure (but continues), then subsequent additions to this troubled
   multiplexed group generates excessive failure messages.
       
   This code change inhibits adding new backup jobs to multiplexed groups
   that contain a failing copy.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET218162

Description:  
   The bpplschedrec -deldayomonth command deletes a range of days instead of  
   the specified day.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET230710

Description:  
   A warning message is produced in RedHat 9 that indicates NetBackup is
   issuing a wait after telling the operating system (OS) to ignore the
   relevant signal.  The OS disregards the wait so there is no actual  
   problem.  This only affects bpcd in standalone mode.  

Workaround:  
   The current solution for this issue is to ignore the warning message.  

   All NetBackup Windows Clients All NetBackup Unix Clients  
--------------------------------------------------------------------------------
Etrack Incident = ET236426 ET230514

Description:  
   If NetBackup is configured to duplicate an image and also configured to
   change the retention level of the new copy to a retention level that is
   configured as "expires immediately", then the original image also appears
   to be expired at the end of the duplication. Any backup taken after that,
   returns the original image.  

Workaround:  
   Any subsequent backup would expunge expired copy from the image file, and
   bring back the original image (to image list and for restore operation)
     

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET234522

Description:  
   SCSI-3 library commands have standardized on op code 0x37 for the command  
   INITIALIZE ELEMENT STATUS w/RANGE.  Previous implementations by numerous  
   vendors had used vendor-unique code 0xE7 - which was implemented by  
   NetBackup.  SCSI-3 libraries will return sense data 20/00 when sent an E7.  

Workaround:  
   To avoid this issue, use only tapes with barcodes that are valid for your
   library vendor.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET234298

Description:  
   NetBackup was not properly using the firmware revision to retrieve the  
   correct device mapping in the device mappings file.  This has never been a  
   problem in the field because VERITAS has never had to use the firmware  
   revision in the device mappings file - this is being done for new device
   support.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET218560

Description:  
   In certain cases, a backup job may receive an error, but the job remains  
   active and must be manually cancelled.  

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Etrack Incident = ET223542

Description:  
   The scheduler does not automatically start "bpexpdate -deassignempty" to  
   deassign media that do not have associated images after "bprecover -l" has  
   been run.  

Workaround:  
   If a bprecover -l has been executed, remove the following file:
   
   UNIX:
   /usr/openv/netbackup/bin/deassign_lock
   
   Windows:
   VERITAS_lock
   
   Do not remove this file if a catalog recover (bprecover -r) has been done.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET260510 ET259248

Description:  
   Only fails on a UNIX master. If a user archive fails to remove some files
   (and generates a status 4), then the .f file is removed, and the files, up  
   to the failed file, are removed from the client.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET235410

Description:  
   It was possible that the bpjobd process may hang under certain conditions.  
   It has been demonstrated that this can happen if bpduplicate and bptm
   processes are killed, but it may occur in other situations.  The bpjobd
   process does not die, it just loops consuming CPU time, and nothing is
   written to the debug log.  This prevented the job DB from being updated
   with the status of existing jobs, or new jobs.  bpjobd must be killed and
   restarted by the system administrator to resolve this problem.
       
   This problem is indicated by the following data in the bpjobd debug log,
   referring to non-existent job ID 3:
   
   18:45:00.734 [17433] <2> process_active_job: Frame type is 3 (jobid 3)  
   Sock (93)
   18:45:00.734 [17433] <2> process_active_job: Adding provider(1) for job(3)
   socket (93)
   18:45:00.734 [17433] <2> process_active_job: Begin to write (JOBTRYFILE) at
   offset 68 job (3)  

Workaround:  
   To avoid this issue, kill and restart the hung bpjobd.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET185677

Description:  
   The output from bpcatarc, a Windows file specification, was not parsed
   correctly and resulted in catalogs being archived but not removed.  

Workaround:  
   To avoid the issue, pipe the file list from bpcatlist to bpcatarc and  
   bpcatrm separately.
   
   Instead of running the following command:
   C:Files> bpcatlist | bpcatar |  
   bpcatrm
   
   You should run the following two commands:
   C:Files> bpcatlist | bpcatarc
   C:Files> bpcatlist | bpcatrm  

   (All NetBackup Servers: Intel-NT Intel64)
--------------------------------------------------------------------------------
Etrack Incident = ET223801

Description:  
   Under someUnder some circumstances, an image file might be expired on the Master  
   server and remain on the Media server. When media full is detected for a  
   DiskStaging storage unit, the media server attempts to remove the two
   oldest images. If these images were no longer in the catalog on the Master
   server, they could not be removed and the backup would fail.
       
   The code was changed to remove the image files if the Master server no  
   longer had them in the catalog.  

Workaround:  
   To avoid this issue, manually delete the image files that are causing the
   problems along with their .ds file.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET221591 ET185355

Description:  
   The predict algorithm was not sorting correctly. It failed to position  
   cumulative incremental backups before the differential incremental backups.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET232060

Description:  
   To assist image database cleanup in 24x7 environments, image database
   cleanup will always run in background.  bpsched will not wait until the
   cleanup is complete before scheduling new jobs.  In addition, bpsched will
   initiate an image database cleanup at periodic intervals, 12 hours by
   default.  The time interval may be changed by using the  
   bpconfig -cleanup_int <hours> command.  For example, to change the interval
   to 24 hours, execute the following command:
   
   bpconfig -cleanup_int 24
   
   Use a value of 0 to disable bpsched from starting the periodic image  
   database cleanup.  The maximum value is 744 hours.  Bpsched will still  
   perform an image database cleanup at the end of a session, however, it will
   be run in background.  On UNIX systems, bpadm may also be used to change
   the interval.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET231652 ET224755

Description:  
   NetBackup was not properly examining the SCSI library mail slot status
   bits; therefore, during ejects of more than a MAP-full of media, the eject
   operation may abort after the first MAP-full is removed.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET233382

Description:  
   In one instance, some catalog files were corrupted when the system ran out
   of disk space. This caused bpdbm to crash whenever it tried to load the
   corrupted catalog files. The command "bpdbm -consistency 2" also crashed
   every time these corrupted files were checked.
       
   The cause of this problem was the buffer overrun in libcatalog when loading
   corrupted files: the pointers and string lengths are wrong after mapping
   buffer overrun to fix the crash of bpdbm.  In addition, code was added in
   image.c to move corrupted catalog files out of /db/images (into /db.corrupt
   directory) when running "bpdbm -consistency 2".
       
   This new code resulted in the following new feature:
       
   "bpdbm -consistency" will move corrupted catalog files out of the catalog  
   repository "/netbackup/db/images" and into "/netbackup/db.corrupt"
   directory.
       
   After running the above command, users will need to do the following:  
   1. Record all file paths in /db.corrupt.
   2. Re-import the files in step 1.
   3. Delete files in /db.corrupt.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET225198

Description:  
   The Phase II import of (non-binary) catalog files can fail because the  
   code tries to re-name an imported file before closing the file.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET221883

Description:  
   The file list for stream 1 is listed twice in the job details when stream 1
   is force-started to take a snapshot. This error is only on multi-stream  
   snapshot backups.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET223787

Description:  
   The scheduler debug log was filling with the following message:
       
   "storage unit was not assigned for clientjob <host name> <policy name>  
   <stunit name> <copy>"  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET260902 ET259243

Description:  
   When a user imports and/or restores a NetBackup 3.4 backup image in
   NetBackup 5.0/5.1, files greater than 1GB in size fail to restore and
   produce, "disk full at byte xxxxx", errors in the restore log. Image verify
   also fails with a gigabytes size mismatch error for those files. In
   addition, the Backup, Archive, and Restore GUI shows a discrepancy in
   reporting the size of those files.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET223024 ET200818  ET222663

Description:  
   Vault, when deciding if an image has already been duplicated, looks for
   any image fragments already present in the destination volume pool.  
   Vault does not check if the fragment is of a valid copy.  

Workaround:  
   To avoid this issue, run an Image DB cleanup session to ensure that invalid
   image copies are deleted from the Image DB.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET261216

Description:  
   Vault reduplicates images if the duplication target is a disk storage unit.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET257361 ET256932

Description:  
   For duplication, Vault picks the first image copy on disk as the source  
   image for the copy operation. This can result in Vault ignoring the  
   primary copy on disk, which should be used as the source.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET263308

Description:  
   The Device Configuration user interface can encounter a long delay when  
   selecting a robot.  The time required to filter the lists in one case was  
   reported to be approximately 20 minutes.  

   (All NetBackup Servers: Intel-NT Intel64)
--------------------------------------------------------------------------------
Etrack Incident = ET223261

Description:  
   Bpbrm can core dump if one of the signal handlers interrupts a malloc
   or free when the code is updating the pointers that are used to track
   the free or allocated space.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET263310

Description:  
   Very large Teradata backups had an error where an overflow of an integer  
   byte count of fractional blocks caused the wrong size to be sent to bptm.  
   This size value did not match what bptm counted and the backup was aborted.  

Workaround:  
   To avoid this issue, you can back up the large database using multiple
   streams.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET264088

Description:  
   A multiplexed TIR duplication would fail if the prior backup duplication  
   had a TIR size greater than 1 Gigabyte, and would lead to a bptm crash.  

Workaround:  
   Retry the duplication using non-multiplexed duplication.  It is also  
   possible that the duplication will succeed by trying multiplexed  
   duplication.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET258595

Description:  
   Oracle autobackup of a control file is very slow because of the format of
   the piece name.  

   (NetBackup Clients:  HP HPIA64 Intel-NT Linux2.4 Linux64 RS6000_433  
    RS6000_51 SGI Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET262983 ET262880

Description:  
   The backup job start time in the Activity Monitor was the same value for  
   each attempt. The start time value should be different on each attempt.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET192195

Description:  
   The ltid daemon will report operational issues at startup time using
   localized error messages.  In some cases, the boot-time console device can
   not properly display non-ASCII characters, and can cause the boot-time
   error conditions to be easily understood.
   
   All of the error messages that can be presented at startup time are now
   printed in ASCII only.  No localization of the error messages will be
   attempted by ltid.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET262866 ET261315

Description:  
   Vault does not handle "Disk Staging Storage Unit" source images like "Disk
   Storage Unit" images for duplication.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET258458 ET167719

Description:  
   Added support for the following drive and media types for ACS:
   Drives:
       HP LTO-3  
       
   Media:
       LTO-400G  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET263758

Description:  
   The scheduler would send a message on the wrong queue when it detected an  
   error on a client snapshot. This may result in a scheduler crash, if the  
   error happened frequently, or if the scheduler stayed running for a
   prolonged period of time.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET265188

Description:  
   If an SSO drive is DOWN on all servers, and its scan host unregisters  
   (services are shutdown), vmd/DA will not transfer this drive to another  
   scan host.  If the drive is brought UP on a server(s), it will have no
   scan host, and will stay in the NO-SCAN state.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET265663

Description:  
   The image resume time limit was not always being updated on Checkpoint  
   backup jobs. Multiple attempts to resume a job might result in a backup  
   that is restarted instead of resumed.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET229709

Description:  
   The following bptm logging statement was confusing and has been changed.
           
   09:37:46.035 [16536] <4> ndmp_internal_open_and_auth: NDMP server DEBUG
   suggests protocol version 3
     

   (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET262921

Description:  
   The error "license use has been exceeded", status code 159, may have been  
   erroneously generated when using a SAN media server license for a media
   server that is part of a cluster.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET212904

Description:  
   A failure occurred when attempting to restore from an image that was  
   backed up with the following setting:
   
   "SET FILES = ( Multiple Files ) "
   
   A status 5 would be generated.  

   (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET266252

Description:  
   There are two issues that may have caused backups to fail:
       
   1. bpsched was not updating the RESUME_EXPIRATION time on failed backups.
   2. bpdbm did not update the REQUEST_PID on subsequent Q_IMAGE_NEW requests.  

Workaround:  
   To avoid this issue, make sure any job that has been resumed is finished
   before the cleaning is done.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET262104

Description:  
   When performing a backup of Shadow Copy Components, and the client is setup
   to use WOFB (Windows Open File Backup) and the Snapshot Error Control is
   set to Disable Snapshot and Continue, then 0 bytes will be backed up for  
   Shadow Copy Components.  

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

Description:  
   vmphyinv is unable to read the tape header in NDMP drives. This affects
   NDMP drives and the NetWare media server (that are handled using NDMP
   protocol).  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET209623

Description:  
   An SQL Server object backed up by the NetBackup SQL agent between 12:00 and
   1:00AM cannot be selected in the SQL agent backup history window of the
   restore dialog box. When an attempt is made to select such an object, a  
   pop-up message reading, "Please enter an integer between 1 and 12" is  
   generated.  

Workaround:  
   Since the target object cannot be selected, you must work around this  
   problem by creating the restore script (.bch file) manually. Otherwise, do  
   not do backups between 12:00 and 1:00AM.  

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

Description:  
   A NetBackup SQL agent (version 5.0 MP1) with backup scripts using $ALL and
   BATCHSIZE places the BATCHSIZE directive into all OPERATION requests but
   are only allowed in the first set.  For example, if the script (.bch file)  
   looks like this...
   
   BATCHSIZE 2
   OPERATION BACKUP
   DATABASE $ALL
   SQLHOST ''SQLVIRTUAL''
   SQLINSTANCE ''INST1''
   NBSERVER ''DB-AD02''
   MAXTRANSFERSIZE 0
   BLOCKSIZE 7
   BROWSECLIENT ''SQLVIRTUAL''
   ENDOPER TRUE
   
   ...then the failures will look like the following.
   
   dbclient log:
   23:17:42.677 [2172.2212] < 16> ReadBatch: USER - Error. BATCHSIZE cannot be
   specified after the first operation.
   23:17:42.677 [2172.2212] < 16> ReadBatch: USER - BATCHSIZE and GROUPSIZE  
   cannot both be specified in an operation  

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

Description:  
   A problem occurred when SQL Server images were stored using the fully  
   qualified domain name (such as xxxxx.veritas.com). The fully qualified
   domain name (FQDN) was used, for example, if the client name was an FQDN.
   In this scenario, the SQL Server agent successfully browsed for the images
   but created an incorrect batch file. In particular, the image name was  
   specified incorrectly.  
   
   For example, if the image was stored as xxxx.min.com, the image name would
   be created as:
   MSSQL7.veritas.com_ENT001 0001of00120040620161136\C
   
   However, the agent generated the batch file using:
   
   NBIMAGE "entsql001/MSSQL7/xxxx/db/ePO_ENT001/~/0/001of001/20040620161136//"
   
   This caused the restore to fail. Errors such as the following appeared in
   the dbclient log.
   
   14:46:19.471 [2940.2996] < 32> DBthreads::dbclient: ERR - <  
   VxBSAQueryObject> failed with error < 17> . The text follows:
   14:46:19.471 [2940.2996] < 1> DBthreads::dbclient: CONTINUATION: - No  
   object matched the specified predicate.
   14:46:18.158 [2940.2996] < 8> VxBSAQueryObject: WRN - Query unsuccessful  
   for client ENTSQL001.  

Workaround:  
   To avoid this issue, manually update the batch file using the correct
   image name.  

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

Description:  
   The NetBackup for SQL restore move script is sometimes built without
   specifying the .ldf (log) file. This only happens for multi-striped  
   backups.  

Workaround:  
   To avoid this issue, manually edit the move script to include the MOVE log
   (.ldf) section and the restore will be successful.  

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

Description:  
   If BATCHSIZE is used in the batch file and one of the referenced databases  
   does not exist, then the SQL agent hangs.
   
   Below is sample batch file.
   
   BATCHSIZE 3
   OPERATION BACKUP
   DATABASE "master"
   SQLHOST "CASS"
   NBSERVER "CASS"
   MAXTRANSFERSIZE 0
   BLOCKSIZE 7
   ENDOPER TRUE
   OPERATION BACKUP
   
   DATABASE "johnny"
   SQLHOST "CASS"
   NBSERVER "CASS"
   MAXTRANSFERSIZE 0
   BLOCKSIZE 7
   ENDOPER TRUE
   
   OPERATION BACKUP
   DATABASE "msdb"
   SQLHOST "CASS"
   NBSERVER "CASS"
   MAXTRANSFERSIZE 0
   BLOCKSIZE 7
   ENDOPER TRUE
   
   'Johnny' was not a database that existed on the system. The backup  
   completed successfully for the two databases that existed, but the  
   dbbackex.exe process hung after encountering this message.  

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

Description:  
   A problem existed that caused differential SQL backups to be associated
   with the wrong full SQL backup if multiple full backups were performed
   prior to any differential backups.  
   
   For example, if three full SQL backups of a database were performed and
   then a differential backup was done, that first differential backup will
   correctly show up in the restore GUI under the last full backup. However if
   another differential is done, it will show up under the first full backup.
   Incorrect associations like this would cause the restore to fail.  

Workaround:  
   To avoid this problem, you must manually change the SQL Agent batch file
   before launching it to perform the restore.  

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

Description:  
   Some FlashBackup backups took longer on NetBackup 5.0 than they did for  
   NetBackup 3.4 because of the overhead of the binary catalog.  

Workaround:  
   To avoid this issue, raise the maximum files-per-add value using the
   /usr/openv/netbackup/MAX_FILES_PER_ADD to 9500. This will raise the limit
   for all backups.  

Additional Notes:  
   The number of files added per call to the catalog has been raised to 9500  
   from 500 for FlashBackup. This limit can be modified by putting the desired
   value in /usr/openv/netbackup/FBU_MAX_FILES_PER_ADD, which only affects
   FlashBackup backups.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET267539

Description:  
   An attempt to use $ALL in a Batch file with more than 32 databases on a
   system will result in the following error that appears in the dbclient log:
   
   ReadBatch: USER - Error in the value supplied for GROUPSIZE.. You must  
   provide a size between 1 and 32.
   
   In addition, if a backup batch file contains multiple operations, and one  
   of the operations cannot complete because of an error such as specification
   of an invalid database name, then the batch will halt at the point at which
   the bad operation is reached and will not continue.  

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

Description:  
   Despite the successful completion of a scheduled SQL Server backup, a
   message of severity <16> would be generated in the bphdb log:
   
   14:45:48.093 [1652.868] <4> bphdb sync_server: INF - BACKUP START
   14:45:48.265 [1652.868] <4> bphdb sync_server: INF - CONTINUE BACKUP  
   message
   received.
   14:45:48.265 [1652.868] <2> bphdb get_filelist: INF - Read filename:
   <test_otm.bch>
   14:45:48.265 [1652.868] <2> bphdb get_filelist: INF - Read filename:
   <CONTINUE>
   14:45:48.265 [1652.868] <4> bphdb.do_launch_ex: INF - Processing t
   14:46:11.812 [1652.868] <4> bphdb.CreateProcessForNT: INF - command
   successfully initiated
   14:46:11.812 [1652.868] <16> bphdb.do_launch_ex: ERR - exit status  :  (0)
   14:46:11.828 [1652.868] <4> bphdb Exit: INF - bphdb exit normal
   14:46:11.828 [1652.868] <4> bphdb Exit: INF - EXIT STATUS 0: the requested
   operation was successfully completed  

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

Description:  
   The Non-vaulted Images Report does not allow the user to specify the date
   range for the report.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET267530

Description:  
   Scheduler code was too inflexible and did not allow for easy addition of
   new Windows Open File Backup (WOFB) snapshot clients. This change corrected
   the scheduler and eased the addition of future Microsoft clients.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET268568

Description:  
   The scheduler would take a long time scheduling multiple data stream jobs  
   if there were many policies that were due to be auto discovered at once.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET232056

Description:  
   When selecting a media ID for backup, if the allocation date in the media
   database does not match the assigned date in the media manager database,
   FREEZE the media because there could be database inconsistencies.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET233573

Description:  
   After upgrading from NetBackup 4.5 to 5.0 MP2, generating reports is much
   slower.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET224601

Description:  
   The Detailed Distribution List for Vault and Summary Distribution List for  
   Vault reports use more memory than required when they are generated.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET261183

Description:  
   When generating Vault reports, memory is allocated but not released
   properly.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET230377

Description:  
   The text "Media that have not been ejected" in the Non-vaulted Images  
   report is not internationalized, therefore it is not translated when  
   NetBackup is localized.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET267132

Description:  
   In the Iron Mountain electronic report, an extra space prevents Iron  
   Mountain from parsing the report successfully.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET258429

Description:  
   Eliminated errors appearing in the bpbkar log when performing a backup  
   using a Windows UNC pathname with a Lotus Notes policy.  Error  
   messages reporting NSFDbOpen() failures for the first two pathname  
   components (\hostname and \hostname)are no longer reported.
   
   A Lotus backup job with a pathname of only one or two components, (i.e.  
   \hostname or \hostname) causes the backup to fail and an error  
   status 71 is reported.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET223772

Description:  
   A dual-stream backup starts only one backup for each redo log group after  
   the first redo log group is backed up correctly (two backups).
   
   This problem occurred in following configuration:
   1. BRARCHIVE was called with an -f option.
   2. The SAP Agent configuration file (init<SID>.utl) contained the  
   sched_log parameter.
   
   The sched_log parameter is the value of the second schedule that SAP Agent
   can use to backup archive logs. When this parameter is enabled two backup
   of archive logs will be performed. This enables backing up same archive
   logs to different media.
   
   This parameter is processed correctly by the SAP Agent when BRARCHIVE is  
   called without -f option.  However, when  BRARCHIVE is called with a -f  
   option, only the first group of archive logs are backed up to both
   schedules. Any subsequent group of archive logs are backed up to only one
   (original) schedule.    

   (NetBackup Clients:  ALPHA HP HPIA64 Intel-NT Intel64 Linux2.4 Linux64  
    RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET266303

Description:  
   For NDMP restores on NetApp filers, more than 1024 files can be restored  
   using DAR.  

   (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET258177

Description:  
   When collecting disaster recovery information, a process named
   'drfile.exe' is executed to generate a file that contains the disaster
   recovery information.  On some machines, after the file has been
   generated, the 'drfile.exe' process does not exit.  

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

Description:  
   Errors occurred when the Sony TSL-11000 tape library would put the  
   cleaning tape away to its appropriate slot.  

Workaround:  
   The cleaning actual works, but the cleaning statistics do not get updated.
   Running a tpclean -M <drive name> after the failed clean will correct this.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET262898 ET262473

Description:  
   Vault Duplication performance degrades significantly for large images
   (spanning media) in NBU setups that have TIR enabled.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET233460

Description:  
   NetBackup for Lotus Notes will successfully backup Domino transaction log  
   extents, but will NOT truncate them.  

Workaround:  
   Do not specify the TRANSLOG_Path for the Lotus transaction log directory in  
   the notes.ini as a symbolic link.  Make sure the Lotus transaction log  
   directory is always the actual physical path.  

   (NetBackup Clients:  Intel-NT Linux2.4 RS6000_433 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET267414 ET218054

Description:  
   A Vault policy that ejects media (using vlteject in the policy) creates an  
   extra Job in the Activity Monitor.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET262906 ET229932

Description:  
   Incremental backups with FlashBackup on Windows were experiencing two
   problems.  First, too much space was being allocated for certain tables.
   Second, incremental backups were failing because freed space was being
   referenced.  

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

Description:  
   Add support for RedHat 3.0 on the Zseries platform.  This required a new
   client type which is called IBMzSeriesLinux2.4.21.  The number is based off
   the operating system (OS) kernel.  

   (All UNIX NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET264130 ET266195  ET265296  ET262877  ET258096  ET223049  
                 ET258202 ET258252  ET257553  ET230175  ET223889  ET223643

Description:  
   Added support for the following libraries:
   
   - ATL M2500 (fixed inventory issue)
   - Certance CLL3200 (fixed TLD(AVR) issue)
   - HP DAT72X6
   - IBM 3623 2SX
   - IBM DDS4  
   - NEC T40A
   - Sony Lib-162
   - Sony Petasite CSM200/100/60 (serialization change with 4.01)
   
   Added support for the following drives:
   
   - Benchmark VS640  
   - Sony SDX-900V  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET269541

Description:  
   An extra invocation of a function was resetting the delay time on tape UN  
   mounts for user backups. Removal of the extra invocation should produce  
   more optimal UN mounting of tapes when performing user backups.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET269768

Description:  
   Added support for IBMzSeriesLinux2.4.21.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET258155

Description:  
   Jobs that have both TIR with Move Detection and 128-bit encryption set  
   fail with either status 249 or 24 for Tru64 clients.  

   (NetBackup Clients:  ALPHA )
--------------------------------------------------------------------------------
Etrack Incident = ET270921

Description:  
   Because of a race condition, ACSLS drives may get downed during mount  
   processing.  

Additional Notes:  
   The signature of this race condition is that the event viewer (or syslog)  
   will note errors in semaphore operations from ACSD, and then the drive
   will be DOWNed.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET274324

Description:  
   When multiple disk staging jobs are initiated and the DSSU is at or  
   near capacity, some jobs may fail with a status 84 error, "disk full,
   attempting to remove the same staged images".
   
   BPDM logs contain entries that indicate no matching entries found in the  
   catalog, (db_IMAGE: db_end_sts() failed: no entity was found).  

Workaround:  
   If the DSSU is nearing capacity, manually remove the previously staged  
   images. These images are identified by an additional zero-length file of  
   the same name, with a ".ds" extension.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET274137

Description:  
   A bug in write_data_tir() had corrupted the TIR file when the disk was full
   and when writing to a disk staging unit.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET276040

Description:  
   Maintenance Pack 1 for the NetBackup 5.1 release introduced a performance
   issue with NDMP DAR restores for catalogs with a large number of files.
   This fix corrects the performance problem.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET272137 ET274040

Description:  
   Corrected a case where incremental backups were backing up complete data
   sets (full backup). This happened only for multi-stream WOFB or advanced
   client where a previous non-control stream backup failed.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET273464

Description:  
   Corrected a problem where tapes would not unmount in a reasonable amount of
   time.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET271482

Description:  
   Re-naming a schedule, and then attempting an immediate backup using the  
   newly named schedule caused a core dump in the scheduler.  

Workaround:  
   To avoid this issue, do not add, remove, or modify policy or schedule
   information and then attempt an immediate backup while scheduler is
   running.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET275271

Description:  
   In a rare circumstance, the last block of a multiplexed, duplicated copy of
   a TIR backup may be corrupt. A verification of the copy would not be
   successful. The original backup is not affected. This does not affect  
   non-multiplexed duplications of a multiplexed TIR backup.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET276018

Description:  
   The NAS snapshot policy validation failed with a, "DataOntap 70RC1
   (ndmp_fsutil call failed)" error. The following excerpt is from the
   online_util log.
   
   09:57:28.312 [2024.440] <2> onlfi_vfms_logf: ndmp_fsutil call failed,  
   is_nfs =
   0, status = 0x1b, (NDMP_CLASS_NOT_SUPPORTED_ERR)  

   All NetBackup Windows Clients Solaris Solaris9  
--------------------------------------------------------------------------------
Etrack Incident = ET276969

Description:  
   Corrected a problem that allowed an incorrect block size to be put in tape
   backup headers.  This problem occurred when the file SIZE_DATA_BUFFERS
   exists to change default tape block size, a backup is duplicated to tape
   and the source/destination media is on the same machine.  The incorrect
   block size in the tape backup headers would not prevent restores from
   working, however, it would prevent import phase 2 from working if that
   copy (with the incorrect backup header) was ever imported.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET276830

Description:  
   User archive or synthetic backups that have checkpoint enabled, and receive
   a 134 (resource busy) will be rescheduled. But the Activity Monitor lists
   the job as "done" status 134.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET272608

Description:  
   If a set of configuration options in bp.conf is very large, it can cause
   bpgetconfig and the GUI to not display any of the items.  This applies to
   items in bp.conf with the same name, for example CONNECT_OPTIONS or SERVER.
   
   Additionally, if that set of configuration options is edited in the GUI,
   for example, to add a new server to the CONNECT_OPTIONS, all of the
   previous data for that set of options will be lost and only the new data
   will be in bp.conf.  

Workaround:  
   To avoid the issue, reduce the number of configuration options with the
   same name.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET273254

Description:  
   NDMP restores fail with Hitachi NAS when restoring the entire backup image.
   The NDMP log shows the path being sent twice in the NDMP_DATA_START_RECOVER
   message.  

Workaround:  
   Restores will work as long as the file system path is not selected (the
   path that was initially backed up). If the entire image is needed for
   restore, select all the files and directories in the file system path
   instead.  

   (All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET272608

Description:  
   If a set of configuration options in bp.conf is very large, it can cause
   bpgetconfig and the GUI to not display any of the items.  This applies to
   items in bp.conf with the same name, for example CONNECT_OPTIONS or SERVER.
   
   Additionally, if that set of configuration options is edited in the GUI,
   for example, to add a new server to the CONNECT_OPTIONS, all of the
   previous data for that set of options will be lost and only the new data
   will be in bp.conf.  

Workaround:  
   To avoid this issue, reduce the number of configuration options with the
   same name.  

   All NetBackup Windows Clients All NetBackup PC Clients  
   All NetBackup Unix Clients  
--------------------------------------------------------------------------------
Etrack Incident = ET258096 ET270045 ET268600 ET260459 ET273679 ET220083 ET260459
                 ET274370

Description:  
   Added support for the following libraries:
   
   - ARCHIVE Python 06241-XXX910B
   - Certance CLL3200
   - Diligent VTF Open
   - IBM DDS4 Autoloader
   - IBM 3623 2SX
   - SEAGATE DAT 9SP40-400910B"
   
   Added support for the following drives:
   
   - HP LTO3
   - IBM Ultirum-TD3, 3580-TD3  

Additional Notes:  
   Devices can be included in this file before they officially supported.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET259704

Description:  
   When running Windows Open File Backup enabled backups using VSS on  
   Windows 2003 clients, performance of the backup is considerably slower
   compared to when running a Windows Open File Backup enabled backup using
   VSP or with Windows Open File Backup disabled. Only backup performance is
   affected and no data loss occurs as a result of using VSS as the Windows
   Open File Backup snapshot provider.  

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

Description:  
   When backing up encrypted data on Windows 2000 clients using Windows Open  
   File Backup to backup an open/active file, the encrypted data will be  
   inaccessible to the backup, and the backup will end partially successful.  

Additional Notes:  
   In NetBackup 5.1 MP2, Windows Open File Backup snapshots will be disabled
   when backing up encrypted data on Windows 2000 clients. This is not
   applicable to Windows operating systems newer than Windows 2000 such as
   Windows XP and Windows 2003. A logging message similar to the one below may
   appear in the bpbkar32 debug logs indicating this on Windows 2000 clients:
   
   4:29:09.328 PM: [2620.2648] < 4> file_access::V_OpenForRead: INF -
   Disabling  
   snapshots for: D:_SN.txt
   
   By disabling snapshots for Windows encrypted data on Windows 2000 clients,  
   these files may not be accessible to the backup if they are busy or locked
   by another process. If Windows Open File Backup protection is important,  
   Windows encryption should be disabled on the files being backed up.  

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

Description:  
   Image fragments are sometimes left behind on the disk storage unit after
   the image expiration has occurred, and the accumulation of such "rogue"  
   fragments can eventually create backup failures unless the rogue fragments  
   are manually deleted by an administrator.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET279250

Description:  
   Backups of encrypted files completed with a "partially successful"
   message, however, the encrypted files were not backed up.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET283490

Description:  
   Initiating multiple Oracle backups caused crashes in scheduler. Each of the
   Oracle backups attempted to read/update/write a group ID file (used for
   synching snap backups), but there was no lock mechanism on the file access,
   so each Oracle backup had the potential to corrupt another¿s file access.
   
   When this problem was discovered, the environment was running about  
   20-Oracle backups (one policy per client).  

Workaround:  
   To avoid the issue, stagger window openings for Oracle backups.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET277862

Description:  
   With multi-streaming enabled, the bpfis command will attempt to take a VSP  
   snapshot of the root drive on Windows platforms when backing up a file list
   item that is a logical entity (not the name of an actual file or directory)
   such as "SYSTEM_STATE".  

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

Description:  
   When performing duplication and direct shared memory was being used instead
   of sockets, increase the timeout the writing bptm/bpdm waits for the
   reader to setup the shared memory.  Previously, if the system was
   very busy, the timeout was not enough.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET277797

Description:  
   Robot inventory update was not taking into account the media type for  
   existing standalone media that have been moved into a robot. It was only  
   looking at the barcode rules. This was the basic cause of the error "media  
   type and volume group mismatch (101)". Robot inventory update now updates  
   the media residences to be robotic without changing the media type.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET284896

Description:  
   When running a Restore job, the information about the job does not appear
   in the Job Details -> Job Overview tab in the Activity Monitor, however,
   the job still completes successfully.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET287015

Description:  
   When running backups with Windows Open File Backup and running multi-
   streamed and multiplexed backups, some backups may end with status  
   41, "network connection timed out". When these errors occur, there should
   be multiple (at least 30) log statements such as the one below in the
   bpbkar32 logs for the same bpbkar32 process:
   
   12:04:07.788 AM: [4008.3816] <4> V_Snapshot::V_Snapshot_TimeoutCheck: INF -
     
   Attempting to query volume snapshots: bpfis query -id 1103259068
   12:04:08.788 AM: [4008.3816] <4> V_Snapshot::V_Snapshot_Destroy: INF -  
   Attempting to destroy volume snapshots: bpfis delete -id 1103259068
   12:04:11.788 AM: [4008.3816] <4> V_Snapshot::V_Snapshot_Destroy: INF -  
   Snapshot Destroy EXIT STATUS 0: the requested operation was successfully  
   completed
   
   This is not an issue for non multi-streamed Windows Open File Backup jobs  
   or backup jobs that have Windows Open File Backup disabled.  

Workaround:  
   To avoid this issue, disable Windows Open File Backup for the client that
   have backups end with status 41.  

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

Description:  
   The .f and non-.f files were not getting deleted on a NAS snapshot client.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET289149

Description:  
   Corrected possible skipped backups if the frequency is a multiple of  
   24-hours (interval mode) and the backup window is greater than 24-hours.
   
   Only the first backup was run in the failure scenario.  

Workaround:  
   To avoid this issue, make the backup windows no greater than 24-hours.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET289704

Description:  
   The XBSA Agent PFI backups resulted in status 156 errors.  In this
   failure, the scheduler is receiving a file list, ¿start¿(FI_FILE_START)  
   and file list ¿end¿(FI_FILE_END), however, it would not receive a file  
   list ¿body¿.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET292496 ET289149

Description:  
   Corrected possible skipped backups if the frequency is a multiple of  
   24 hours (interval mode) and the backup window is greater than 24 hours.
   
   Only the first backup was run in the failure scenario.  

Workaround:  
   To avoid this issue, make the backup windows no greater than 24-hours.  

   (All NetBackup Servers)
================================================================================



=========
NB_51_1_M
=========
Etrack Incident = ET199231

Description:  
   Duplication flags in vault do not work correctly when a disk storage unit  
   is defined as a destination for a copy.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET199237

Description:  
   Vault does not check that all fragments of the source image to be copied  
   are resident in the tape library.  

Workaround:  
   This is a rare occurrence that only happens when media is removed from the  
   tape library manually.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET176746

Description:  
   SQL Server backups fail if more than 32 databases are backed up together.
   This occurs because the SQL agent interface places a GROUPSIZE count into
   the batch file. However, if the count is greater than 32, then the job
   fails with the following information written to the dbclient log.  
   
   15:29:34.565 [4520.5140] <16> ReadBatch: USER - Error in the value supplied  
   for GROUPSIZE.. You must provide a size between 1 and 32
   15:29:34.565 [4520.5140] <4> CDBbackmain::dbbackup: INF - Results of  
   executing <C:
   Files-_15_29_32_628_00.bch>:  
   
   <0> operations succeeded. <0> operations failed.
   
   The GROUPSIZE is used for grouping advanced client backups. To resolve this
   problem, GROUPSIZE will not be specified if the number of databases
   selected for backup exceeds 32.  

Workaround:  
   The workaround for this problem is to edit the script used for launching  
   the backup and remove the BATCHSIZE parameter.  

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

Description:  
   The drives used for disk staging backups are not counted correctly. This  
   results in under utilization of drives for other backup operations.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET207814

Description:  
   When scheduler verbose is set greater than 0, there is the potential for  
   jobs to exit with a status 50. This is more likely to occur on systems that
   experience connection issues. The situation occurs when the scheduler
   prints a message and loses the errno value. Armed with the incorrect errno
   value, the scheduler exits (status 50) the current running job.  

Workaround:  
   Set scheduler verbose to zero.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET206000

Description:  
   A correction to potential scheduler problems with memory leaks and  
   non-initialized malloc space has been made.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET205980

Description:  
   The restart of a frozen image backup job failed.  The issue was found using
   the following setup:
    - VxVM snapshot method to backup a VxFS/VxVM file system.
    - checkpoint every 5 minutes.
    - scheduled frequency is 1 hour.
    - backup attempts are set 2 tries per 1 hour.
   
   The following was the attempted failure scenario:
    - Launch the backup and wait for a checkpoint to be taken.
    - killed bpbkar processes to put the job into an incomplete state.
    - waited for the job is restarted (1 hour later).
    - the attempt fails.
    - bpfis is attempting to create a new frozen image.
    - the previous frozen image still exists.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET193022

Description:  
   When performing an Exchange DB backup (IS, KMS or SRS), bpbkar32.exe gets  
   TCP socket read failures after the client receives a server status at the
   end of the backup.  This issue does not cause critical errors because the
   client completes post backup activities successfully.
   
   The end of the bpbkar log looks like the following:
   9:41:22.091 AM: [616.644] <4> tar_backup::OVPC_WaitForServerComplete:  
   INF - 'INF - Server status = 0' received
   9:41:22.091 AM: [616.644] <4> dos_backup::V_ExchgKMSBackupEnd: INF -  
   dos_backup::V_ExchgKMSBackupEnd: cleaning up
   9:41:22.091 AM: [616.644] <2> ov_log::V_GlobalLog: INF -  
   bedsExchangeKMSTerm() Enter
   9:41:22.091 AM: [616.644] <2> ov_log::V_GlobalLog: INF -  
   bedsExchangeKMSTerm():DeAttaching from DLE '\exch_srvrKey  
   Management ServiceManagement Service'
   9:41:22.091 AM: [616.644] <2> tar_base::V_vTarMsgW: INF - Exchange  
   Transaction Logs truncated
   9:41:22.101 AM: [616.644] <16> dtcp_write: TCP - failure: send socket  
   (308) (TCP 10058: Can't send after socket shutdown)
   9:41:22.101 AM: [616.644] <16> dtcp_write: TCP - failure: attempted to  
   send 6 bytes
   9:41:22.101 AM: [616.644] <16> dtcp_write: TCP - failure: send socket  
   (308) (TCP 10058: Can't send after socket shutdown)
   9:41:22.101 AM: [616.644] <16> dtcp_write: TCP - failure: attempted to  
   send 36 bytes  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET193049

Description:  
   Performing an Exchange Information Store restore causes misleading bpbrm
   errors in the Activity Monitor.  The restore is successful.
   
   The Activity Monitor description looks like the following:
   3/2/2004 9:07:01 AM - begin Restore
   3/2/2004 9:07:11 AM - restoring image backrest_1078166427
   3/2/2004 9:07:21 AM - connecting
   3/2/2004 9:07:26 AM - connected; connect time: 00:00:05
   3/2/2004 9:07:27 AM - started process bpdm (2716)
   3/2/2004 9:07:27 AM - started process bpdm (3000)
   3/2/2004 9:07:37 AM - begin reading
   3/2/2004 9:07:38 AM - Error bpbrm(pid=268) from client backrest: TAR -  
   Restoring Exchange 2000 ESE object C:
   Files.edb
   3/2/2004 9:07:58 AM - Error bpbrm(pid=268) from client backrest: TAR -  
   Restoring Exchange 2000 ESE object C:
   Files.stm  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET207390

Description:  
   With NetBackup 5.0, the NetBackup client interface changed the general
   verbose logging range from (0-5) to (0-2) to match the available values
   from the host properties on the NetBackup Administration console.
   
   The Exchange code needs to match these levels, and instead of increasing
   verbosity up to 5, Exchange should offer full verbosity in level 2.  

Workaround:  
   To avoid this issue, use a Windows Registry editor, and set the following:
   
   HKEY_LOCAL_MACHINE
   Debug_Level to 5.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET206043

Description:  
   With NetBackup 5.0 MP1, Exchange cumulative or user-directed backups fail  
   when media multiplexing is greater than 1 on the policy schedule. The
   backups fail with a status 14, "file write failed". In the progress log,
   the following error appears: FTL - tar file write error (40).  

Workaround:  
   To avoid this issue, in the cumulative incremental or user directed type
   schedule in the Exchange policy, set media multiplexing to 1.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET207493

Description:  
   When using the bpexpdate -recalculate or the bpexpdate -backupid commands
   to extend the expiration date of one or more backups that have multiple
   copies, the media expiration may not be correct for copies on removable
   media if the first copy is on disk.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET207498

Description:  
   You may encounter an occasional failure when duplicating True Image Restore
   (TIR) backups.  The failure may occur if there is a delay in mounting the  
   write media.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET206332 ET207817

Description:  
   After installing NetBackup 5.0 MP1, the SQL backups fail with the following  
   error:
   
   VxBSACreateObject: ERR - CreateObject called from invalid transaction  
   state: 0
   
   This problem occurs with clustered SQL Server backups.  

Workaround:  
   To avoid this issue, remove the keyword-value pair from the batch file,  
   <GROUPSIZE n>.  

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

Description:  
   With STK's new version of SSI, certain environment variables are required  
   to be set when the vm.conf entry ACS_TCP_RPCSERVICE is set.  The variables  
   are set to a default behavior unless they are set differently in the  
   vm.conf.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET207157

Description:  
   tar32 will sometimes terminate with an access violation error when
   restoring files that are larger than 8MB and have an object identifier
   attribute.  

Workaround:  
   You can avoid an access violation if you disable NTIO according to the tech  
   support note 264633.  

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

Description:  
   Support of volume rollback for Veritas Volume Manager (VxVM) Instant
   Recovery methods is added for the NBU SQL Server agent. To access this
   capability, an SQL Server backup must use the VxVM advanced client method
   with snapshots retained for instant recovery. In addition, the snapshot
   volume must be configured so that all of the files in the backup exactly
   match the files in the backup image. This is accomplished by placing all of
   the database files on the primary volume and ensuring that no additional  
   files are placed there.  
   
   To activate volume rollback, use the SQL Server agent to create a restore  
   script for a "pfi" or "pfi-to-tape" backup image, save the script as a .bch  
   file, and then edit the .bch file by inserting the keyword-value pair,  -value pair,  
   ROLLBACKVOLUME TRUE.  
   
   If SQL Server volume rollback fails because the files on the snapshot
   volume do not match the files in the primary volume, then the following
   line will be written to the progress log:  
   
   INF - A recovery using volume rollback has failed. To attempt this recovery  
   without volume rollback, remove keywords <ROLLBACKVOLUME TRUE> from the  
   batch file.
   
   If this happens, retry the restore without attempting volume rollback.
   
   Finally, if rollback does fail, then the SQL Server database may be left in
   an unusable state. If this happens, you can still restore the database
   through the normal procedure without specifying ROLLBACK.  

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

Description:  
   A failed or interrupted VSP snapshot attempt can cause the backup to hang,  
   and can crash the bpfis process, or leave it hanging.  

   All NetBackup Windows Clients All NetBackup Unix Clients  
--------------------------------------------------------------------------------
Etrack Incident = ET207891

Description:  
   The archive bits were cleared for the entire incremental backup job when
   the job was resumed and completed successfully.  

   (NetBackup Clients:  Intel-NT Intel64 )
--------------------------------------------------------------------------------
Etrack Incident = ET185363

Description:  
   Corrected compile warnings in the bpadm storage unit free and print  
   schedule calendar invocations.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET185146

Description:  
   Bpduplicate, during disk staging duplication, prints the following message  
   even though no error has occurred.  
   
   11/22/2003 11:25:35 AM - Error bpduplicate(pid=1636) from host dcdell1,  
   COMPLETE_MOUNT QUANTUMDLT70000 0  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET207956

Description:  
   The Microsoft Exchange 2000 Mailbox backup can fail with a status 13.  
   The access violation occurs in bpbkar32.exe.  
   
   Application exception occurred:
          App: bpbkar32.exe (pid=5124)
          When: 2/8/2004 @ 18:59:27.448
          Exception number: c0000005 (access violation)
   
   function: sprintf
          780238c9 8d45e0           lea     eax,[ebp+0xe0]          
   ss:00948fea=????????
          780238cc ff750c           push    dword ptr [ebp+0xc]    
   ss:00948fea=????????
          780238cf c745e4ffffff7f                                  
   ss:00948fea=????????
                                    mov     dword ptr [ebp+0xe4],0x7fffffff
          780238d6 50               push    eax
          780238d7 e8b2bbfeff       call    setvbuf+0x1c3 (7800f48e)
          780238dc 83c40c           add     esp,0xc
          780238df ff4de4           dec     dword ptr [ebp+0xe4]    
   ss:00948fea=????????
          780238e2 8bf0             mov     esi,eax
          780238e4 780b             js      hypot+0x23b (7802c3f1)
          780238e6 8b45e0           mov     eax,[ebp+0xe0]          
   ss:00948fea=????????
   FAULT ->780238e9 802000           and     byte ptr [eax],0x0            
   ds:00c88000=??
          780238ec 8bc6             mov     eax,esi
          780238ee 5e               pop     esi
          780238ef c9               leave
          780238f0 c3               ret
          780238f1 8d45e0           lea     eax,[ebp+0xe0]          
   ss:00948fea=????????
          780238f4 50               push    eax
          780238f5 6a00             push    0x0
          780238f7 e814c5feff       call    flsbuf (7800fe10)
          780238fc 59               pop     ecx
          780238fd 59               pop     ecx
          780238fe ebec             jmp     mktime+0x57 (78028eec)
   
   *----> Stack Back Trace <----*
   
   FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
   0012F104 0044770F 00C87E00 0048B7A8 005C9268 006768D0 !sprintf  
   0012F194 0043ED1C 00000000 0013406E 00000006 00670048 bpbkar32!<nosymbols>  
   0012F1E0 00428AEB 0012FF24 004215C4 00670048 00F300F2 bpbkar32!<nosymbols>  
   0012F1E8 004215C4 00670048 00F300F2 00F500F4 005C3FE0 bpbkar32!<nosymbols>  
   0012FF24 00470AB0 00400000 00000000 0013406E 0000000A bpbkar32!<nosymbols>  
   0012FFC0 7C5987E7 00000000 77F89964 7FFFF000 C0000005 bpbkar32!<nosymbols>  
   
     

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET192993

Description:  
   If eseutil.exe is removed (or probably not found correctly), the Exchange  
   VSS snap and backup still proceeds without a validation being done.  
   Failure to execute eseutil should cause the backup process to fail.
   
   bpbkar log snippet:
   
   8:58:37.586 AM: [5252.4256] <4> VssSnapshot::V_VssVolumeSnapshot():  
   INF - VSS Volume Set snapped
   8:58:37.586 AM: [5252.4256] <4> dos_backup::V_InitializeShadowCopy:  
   INF - ShadowCopy PrePost: End
   8:58:37.586 AM: [5252.4256] <4> dos_backup::V_InitializeShadowCopy:  
   INF - ============================================
   Directory: 'C:Files\NetBackup'
   8:58:40.555 AM: [5252.4256] <2> ov_log::V_GlobalLog: ERR -  
   ubsStart_eseutil():CreateProcess() failed for "C:
   Files.exe" /k "\?
     

Additional Notes:  
   In addition, the following new Internationalization message has been added:
   "Unable to perform consistency check of Exchange Shadow Copy database  
   files."  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET193054

Description:  
   During an Exchange VSS backup, if the Exchange volumes are present on VxVM  
   volumes but the snapshot fails, the backup will still occur. However, only  
   the MIS object is backed up with metadata. No actual databases are backed  
   up.  
   
   A restore browse only shows that object with no storage groups is
   available.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET193052

Description:  
   When backing up a storage group with the correct name, but the wrong case,  
   the backup will succeed but end in a status 1.
   
   The restore also works after the proper EDB validation occurs.  Data  
   loss is not an issue.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET209248

Description:  
   When restoring a system that contains the 'Cluster Database' portion of  
   System State, the restore may fail with a status of 5.  While examining the  
   progress log from the operation, you will see that the number of files  
   restored does not equal the number of files attempted.  

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

Description:  
   For an Exchange VSS backup, checksum validation is now required of the  
   Exchange DB on the snapped volume.  There is a back-door registry key  
   called "Checksum_Database_Files" that enables a user to disable the  
   validation process.  If this key is set to NO, a VSS backup of a  
   multi-storage group server will fail for any storage groups after the first
   it enumerates.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET172212

Description:  
   When restoring a system, and the file system is restored prior to  
   System_State:, the restore process may generate errors indicating that  
   it "can't create directory" with the following WIN32 error code : (WIN32  
   3: The system cannot find the path specified. )  

Workaround:  
   The only known workaround to this issue is to make sure that  
   System_State: is restored prior to anything else on the system.  

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

Description:  
   Resume of a single-stream, suspended job would backup the complete policy  
   file list instead of only the stream's portion of the file list.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET193021

Description:  
   Exchange Mailbox backups may hang for Exchange 2003 running on a  
   Microsoft 2003 Cluster.
   
   This hang happens on Exchange 2003 after mailboxes are migrated from
   Exchange 5.5.
     
   The last log entry in the Debug logs would be:
   "INF - MAPISession::ImpersonateUser():     Logging on to server  
   <Exchange_Virtual_Name>
   as user <MailBox_Alias>! MessageStoreDN=/O=<Org>/OU=first administrative  
   group/
   CN=Configuration/CN=Servers/CN=<Exchange_Virtual_Name>/CN=Microsoft Private  
   MDB
   !MailBoxDN=/O=<Org>/OU=first administrative  
   group/CN=recipients/CN=<MailBox_Alias>"  

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

Description:  
   bpbkar32 can generate an "Exception number: c0000005 (access violation)"  
   error (DrWatson) when doing a cumulative backup of an Exchange 2000 Storage
   Group and the first transaction logs to be backed up are missing. The
   backup ends with a status 13.
   
   If the Log file is missing, it may have been deleted.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET185135

Description:  
   bpexpdate would not notify the user that they were unable to use bpexpdate
   because of access control limiting their access. Even though the binary  
   returned the appropriate error level (such as, 117, 116, or 118) a human-
   readable message was not returned.  

Workaround:  
   To avoid this issue, manually check the error level that bpexpdate returns
   (for example, echo %ERRORLEVEL% or echo $?).  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET185137

Description:  
   Even though the NBU_Operators group did not have backup permission on
   Policies, they were still able to perform manual backups. The NBU_Operator
   group should be able to do manual backups, however, it should always
   require the Backup permission on Policies.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET206796

Description:  
   Using the options that allow a UNIX file system to be restored without  
   crossing mount-points fails when restoring all files under the path  
   instead of just the single file system.
     

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET184717

Description:  
   Bptm or bpdm may crash after bpsched restarts following a bpsched crash
   and subsequently resuming checkpointed backup jobs on media servers.  This
   change cancels existing duplicate jobs when this situation occurs, or
   prevents the crash from occurring.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET210525

Description:  
   When performing a backup on a Windows 2003 server, the event log files may  
   not get backed up.  An error containing the following message can be seen
   in the bpbkar32 debug log:
   
   ERR - unable to backup event log: 'C:.Evt'
   (WIN32 87: The parameter is incorrect. )  

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

Description:  
   When performing full backups of using the UNC naming convention, the  
   archive bits on some files are not getting cleared.  

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

Description:  
   The TLH robotics does not wait for the library auto drive cleaning to finish
   before an error occurs and passes off to bptm.  

Additional Notes:  
   In addition, two new syslog entries have been added.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET167537 ET187652

Description:  
   This enhancement enables NetBackup to work in a Plug and Play  
   environment.  You can now use NetBackup with Plug and Play tape class  
   drivers and the Storport driver.  

   (All NetBackup Servers: Intel-NT Intel64)
--------------------------------------------------------------------------------
Etrack Incident = ET195691 ET210934 for 5.0MP3

Description:  
   File system verification for Point-in-Time rollback restore passes on a
   Windows client when there are new files on the file system. In addition,  
   file system verification for Point-in-Time rollback restore 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 )
--------------------------------------------------------------------------------
Etrack Incident = ET184971 ET187776

Description:  
   The VOPIE Enhanced Authentication may not work when host names are greater
   than 32 characters.  You may see Authentication Failed (error code 160)
   messages when connecting with systems with host names or client names
   greater than 32 characters.
     

   All NetBackup Windows Clients All NetBackup Unix Clients  
--------------------------------------------------------------------------------
Etrack Incident = ET184975

Description:  
   When bpinst -ENCRYPTION pushes the bpkeyutil binary to a UNIX client, the
   mode bits of the binary are 0500 on the client.  The bits should be 0555.
   This could cause a problem if the NetBackup administrator is not running
   as "root".  

Workaround:  
   To avoid this issue, login as root on the client and enter this command:
   
   chmod 555 /usr/openv/netbackup/bin/bpkeyutil  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET211098

Description:  
   The tldcd and tl8cd parent did not check for unit attentions every  
   15 seconds and caused the AUTO_UPDATE_ROBOT feature to not working properly.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET211885 ET204900ET209071

Description:  
   DB2 advance client backup failed when another session established a
   database connection.  To avoid this issue, support was added for DB2 BLI.  

   All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433  
   RS6000_51 SGI Solaris  
--------------------------------------------------------------------------------
Etrack Incident = ET204472

Description:  
   HTML Help for BackupExec SQL restores is once again available from the  
   Windows client GUI's restore confirmation dialog box.  

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

Description:  
   The following compiler warnings indicate that part of the stack is being  
   overwritten on these calls.
   
   warning C4133: 'function' : incompatible types -from 'unsigned int *'  
   to 'time_t *'  

Workaround:  
   This is a rather broad problem that has not appeared in testing, rather as
   warnings during a compile.  Without these changes, the user should verify
   the output of bpcatlist and also verify that bpcatarc is working by
   checking the CATARC value after the .f file is archived (of any backup  
   image that is archived).  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET210388

Description:  
   Job shows an incomplete status (status = 5), after a successfully initiated  
   restore when the "Restore the file using a temporary file name" option is
   selected.  

   (NetBackup Clients:  Intel-NT Intel64 )
--------------------------------------------------------------------------------
Etrack Incident = RSVmn50653

Description:  
   Synthetic Backup fails if the "image copy 1" has been expired, even if a
   secondary copy exists.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET212038

Description:  
   In the Windows NetBackup Administration Console Activity Monitor, if the  
   services details dialog is used to start and stop services, the  
   NBConsole.exe process will crash if the dialog has been up longer than the  
   configured refresh time and the service is then started or stopped.  

Workaround:  
   To avoid this issue, use the Services list to start and stop services.  

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Etrack Incident = ET212072

Description:  
   The SAP Alternate Client restore no longer fails.
   
   First, this problem occurred intermittently because the SAP Agent is unable
   to read output file of restore_filter script. This failure would produce a
   log similar to the following:
   
   "14:30:00.381 [7082] <16> backint_restore_filter: cannot open restore  
   working file:
   /oracle/BD1/sapbackup/backint_dir/.backint.filter.1085772595.7082
   14:30:00.381 [7082] <16> backint_do_restore: ERROR: running restore filter"
   
   Second, the restore_filter script was unable to handle a use case where the
   source client (backed-up client) did not have soft links to the actual file
   paths of the SAP data files. During a restore on target client (new
   destination client), the agent would think that it should not adjust the  
   file paths to match the originally backed-up paths.  The output of this
   problem looked similar to the following:
   "**************************************************************************
   Program:                ./backint 5.0GA
   Input File:             ./in_re
   Profile:                ./initSAP.utl
   Function:               RESTORE
   ****************************************************************************
   #NOTFOUND <input file name>
   ***************************************************************************"
   
   In the backint log, the output looked like the following:
   
   "10:56:07.093 [2838] <2> backint_find_master_time: exit status = 2
   10:56:07.094 [2838] <4> backint_do_restore: #NOTFOUND /tmp/bd1/file1"  

   (NetBackup Clients:  ALPHA HP HPIA64 Intel-NT Intel64 Linux2.4 Linux64  
    RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET203202

Description:  
   A problem in the NetBackup console cache has been corrected.  To replicate  
   the problem, display the media graphical user interface with 100,000 volume
   records.  Change the server to another master.  Click on the media tree  
   node to display its 1,000 volume records.  Next, change the server back
   to the original host and displayed its media list.  It now displays only
   ~98,360 volume records.  If you do a "refresh all", the cache is cleared
   and 100,000 volumes are displayed again.  This seems happen whenever you
   administer multiple volume databases with more than 1635 records.  

Workaround:  
   To avoid this issue, select the "view|refresh all" menu item to clear the
   internal cache, after doing a change server.  

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Etrack Incident = ET212099

Description:  
   The SAP DB Environment Agent reports a success despite an actual failure
   occurring.
   
   This problem does not occur when using the SAP Agent in a SAP environment
   using an Oracle database. This problem only occurs when agent is called in
   a SAP DB environment with an adapter program. The problem will occur if
   there were previously successful backups and the current backup fails.
   
   When this problem happens the log will look similar to the following:
   "
   ...
   08:16:49.143 [1433628] <16> backint_system: ERROR: executing  
   command  /usr/openv/netbackup/bin/bpbackup -w -t 17 -h pollux_bk -S  
   frsux071 -c ASV_SAP_A30_online -s Default-Policy -
   L /usr/openv/netbackup/logs/user_ops/sap/.backint.log.0.1083392186.1282186 -
   08:16:51.208 [1282186] <16> dbc_Wait: ERR - job (1433628) failed status (71)
   ...
   08:16:52.853 [1282186] <4> backint_do_backup: #SAVED  
   NS1083106428 /home/adasav/A10/NB_puffer1/STAGE3.0
   08:16:52.853 [1282186] <4> backint_do_backup: #SAVED  
   NS1083364604 /home/adasav/A10/NB_puffer1/STAGE1.0"
   
   The above log shows that the backup command failed, but the agent reported
   input files were saved. This is because the agent saved these files in a
   previous backup. This may lead user to conclude that the backup of SAP on
   a SAP DB was successful when it actually failed. Again, this is not a  
   problem for SAP on Oracle.  

   (NetBackup Clients:  ALPHA HP HPIA64 Intel-NT Intel64 Linux2.4 Linux64  
    RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET213234

Description:  
   The command, backint -p <utl file> -f inquire, may fail when it is called
   without the input file list.  This caused the SAP Agent to fail.
   When user runs this command, the reported error looks similar to:
   "ERROR: couldn't open file: <file name>"
   
   The SAP BR-tools do not fail with this error because they always provide
   input file list.  

Workaround:  
   To avoid this issue, call "backint -p <utl file> -f inquire -i <file_name>".  

   (NetBackup Clients:  ALPHA HP HPIA64 Intel-NT Intel64 Linux2.4 Linux64  
    RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET210484

Description:  
   For Exchange Advanced Client (VSS) backups, a snapshot consistency check  
   must be run on all Exchange log files with a file generation number equal  
   to or greater than the checkpoint log file.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET213216

Description:  
   Systems with multiple tld or multiple tl8 robots may see strange behavior  
   across robot numbers on remote (not control hosts) media servers when the  
   daemon is bounced.  In the worst case, this can include the drives going  
   into "AVR" control mode on the noncontrol host media servers.  Generally,  
   this is started by a catastrophic failure of one of the robots.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET212553

Description:  
   Vault currently does not give the user the ability to specify which host
   is selected for use as the "robotic control host" for an API robot.  

Workaround:  
   Hand editing the Vault Configuration file  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET213176

Description:  
   While setting dates for containers, even after identifying and
   reporting "Invalid date:", vltopmenu continued to change the date.  
   This no longer occurs.
     

Additional Notes:  
   These are the guidelines for changing the date:
   * If no year is provided then the current year is considered.
   * The year (if provided) is interpreted as:
     * two digit year yy 0-38 interpreted as 20yy
     * two digit year yy 39-69 are illegal UNIX dates and will be converted  
       to 0 (which is 1/1/70)  
     * two digit year yy 70-99 interpreted as 19yy
     * four digit year yyyy interpreted as it is
     * dates before Jan 1 1970 are converted to Jan 1 1970
     * dates after Jan 19 2038 are converted to Jan 19 2038
   * It is considered valid to provide a date prior to the current date.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET213084 ET211806

Description:  
   Running the Vault job from either a vltrun command or by right clicking on  
   the profile runs successfully. However, "status 23" results when running
   the job from the Vault policy either manually or through bpsched.
     

Workaround:  
   If there is a directory or file, named "program", on the drive on which  
   NetBackup is installed (such as, Z:.exe), then rename it to
   something else.  

   (All NetBackup Servers: Intel-NT Intel64)
--------------------------------------------------------------------------------
Etrack Incident = ET209681 ET207797

Description:  
   Using the command, bpimage -cleanout -client dill-bk, to reduce size of a
   database can cause bpimage to core dump.  

Workaround:  
   To avoid this issue, allow the nightly clean-up to clean the catalog.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET212040

Description:  
   Added support for Lotus Notes databases and transaction logs residing in  
   Windows UNC paths. The pathname must have a minimum of three components,
   such as, \hostname.  A Lotus backup job with a pathname of
   only one or two components, (for example, \hostname or \hostname)
   gives a successful status of 0, but no files are backed up.  

Additional Notes:  
   Support for UNC paths in the file list for Lotus policies has been added.  
   This support includes both Lotus Domino databases and transaction log  
   extents.  User-directed backup of Lotus databases that reside on a shared  
   drive referenced by UNC paths is not currently supported.
   
   Please refer to the "NetBackup System Administrator's Guide for Windows,  
   Volume I" for more information on configuring a file list for NetBackup  
   policies using UNC paths.
   
   When using a Windows UNC pathname with a Lotus Notes policy, two error  
   messages will appear in the bpbkar log when performing a backup.  Both  
   messages report NSFDbOpen() failures for the first two pathname components  
   (hostname and shared folder).  For instance, if the pathname is  
   \pepper, these errors are reported:
   
   4:21:07.478 PM: [4884.3344] <4884> nbex_DebugLog: ERR - NBLN_OpenEnumerate
   ()  NSFDbOpen(\pepper) Failed:0x103:File does not exist
   4:21:07.478 PM: [4884.3344] <4884> nbex_DebugLog: ERR - NBLN_OpenEnumerate
   ()  NSFDbOpen(\pepperFailed:0x110:Access to data denied.  
   
   These messages can be safely ignored and will be removed in a future  
   release.
     

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET213846

Description:  
   NetBackup 5.1 installs the VSP v1.03 snapshot driver which causes problems
   with the VSS snapshot creation for other requesters (for example, EMC
   TimeFinder) when it is installed as part of Veritas Storage Solutions 4.0
   for Windows.  VSS snapshot creation for non-NetBackup requesters will fail
   when NetBackup and VxVM is installed as part of Veritas Storage  
   Solutions 4.0 for Windows because of an issue with the VSP driver, v1.03.
   VSP driver version 1.04 will resolve this issue.  

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

Description:  
   NBU_Operators did not have the backup permission on Policies, yet they were
   able to perform manual backups. The NBU_Operator group should be able to do
   manual backups, but it should always require the Backup permission on Policies.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET212361

Description:  
   Tapes get suspended when NetBackup is upgraded from version 4.5 to  
   version 5.1 and the older vault profile (which does not want the tapes to
   be suspended)is selected to run without being touched after the upgrade.  

Workaround:  
   The workaround to resolve this problem is to open the following  
   file, /usr/openv/netbackup/bin/jnbSA, and go to the Vault Management > "Your
   robot type and number" > "your vault name".  Then, select the profile name
   in the right side of the interface.  Next, right-click the profile name,
   select change, and click on the Eject tab on the dialog box that appears.  
   You are now able to modify and change back any option, and click OK.  
   This will add the SuspendMode="NEVER" item (if this matches your selected  
   configuration) in the vault.xml file for the profile selected and resolve  
   the problem.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET164190 ET164186 ET208178  ET217630  ET218069  ET219861  
                 ET220083 ET223049 ET217198

Description:  
   Fixed inventory issues for the following libraries:
   DELL PV-132T, IBM 3582, Sepaton S100, All STK Libraries, HP A5617A
   The added libraries are:  
   Certance CLL3200
   EMC Disk Library
   STK SL500
   IBM 3590H11
   IBM 36232LX
   The added drives:
   Sony SDX-400V
   Added Sony SDX-500V
   Certance Ultrium 3  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET162354 ET206109

Description:  
   An NDMP backup in an ASCII catalog format no longer fails.  The error that  
   was produced in the bptm log is shown below.
   
   08:42:17.202 [5704.5624] <2> write_data_ndmp: calling  
   ndmp_bpfsmap_create
   08:42:18.304 [5704.5624] <2> write_data_ndmp: bpfsmap longjmp: setjmp  
   returned 6; aborting backup
   ...
   08:42:18.764 [5704.5624] <2> write_data: write_data_ndmp() returned -8,  
   EXIT_Status 6, Kbytes = 1359099
   08:42:18.774 [5704.5624] <2> write_backup: write_data() returned,  
   exit_status = 6, CINDEX = 0, TWIN_INDEX = 0, backup_status = -8  

   (All NetBackup Servers: HP Intel-NT Intel64 Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET213982

Description:  
   Corrected a restore problem from disk that resulted in a status 92:
        - Image contained multiple disk fragments and first file of the
          restore was not in the first fragment.
        - The size the fragments prior to the one containing the first
          file were not a multiple of 1K.
   
   The above conditions can occur during an MPX multiple-copy backup, one
   or more copies to disk, and one or more copies to tape.
   
   
     

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET216511

Description:  
   A problem using a template with a DB2 scheduled backup has been resolved.  

   All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433  
   RS6000_51 Solaris  
--------------------------------------------------------------------------------
Etrack Incident = ET206031

Description:  
   A memory leak encountered in XBSA library has been fixed.  

   All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433  
   RS6000_51 SGI Solaris  
--------------------------------------------------------------------------------
Etrack Incident = ET217243

Description:  
   Adjusted a loop used during the deletion of an MPX group. This loop was not  
   functioning correctly on the Windows 2000 platform and resulted in the
   removal of additional MPX groups.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET176030

Description:  
   The Advanced Client FlashSnap alternate client backup fails if NetBackup is
   not installed under the same drive letter on both the primary and secondary
   clients.  

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

Description:  
   When trying to perform a Lotus PIT restore (using PIT) when a secondary  
   restore is required to restore the requested Lotus transaction log extents,
   the following error is encountered:
   
   "Invalid start date: 11/15/99" syntax error in bprestore.  Only applies to  
   restoring Transaction Logs function - standard nsf files are ok.
   
   The tar debug log shows the following:
   16:32:19 (101307.001) INF - Begin Lotus point in time database recovery to:
   06/05/2004 16.29.22 CEDT
   16:32:19 (101307.001) INF - Transaction Log:/A1VG3DATA/S0000160.TXN Required
   for Recovery
   16:32:19 (101307.001) INF - Requesting Restore of  
   Log:/A1VG3DATA/S0000160.TXN
   Id:001c6243c1256e7d-f762d76fa9030000  
   LogNo:160
   16:32:19 (101307.001) Invalid start date: 11/15/99
   16:32:19 (101307.001) EXIT STATUS 144: invalid command usage
   16:32:19 (101307.001) INF - NBLN_RecoverDb() RecoverErrorCode:0x13E3  
   DbIndex:0
   16:32:19 (101307.001) ERR - /A1VG1DATA/c59admin_domino/testtl.nsf Recovery
   Failed!  
   (0x13E3:Recovery Manager: Error from Logging Subsystem.)
   
   In addition, bprestore demonstrates the following incorrect syntax:
   16:32:19.346 [83270] <2> logparams: -B -w -t 25 -s 11/15/99 -R
   /usr/openv/netbackup/logs/user_ops/LN_Restore_Rename_File_87834.chg  
   /Transaction Logs/S0000160.TXN~001c6243c1256e7d-f762d76fa9030000  
   16:32:19.361 [83270] <16> process_args: Invalid start date: 11/15/99
   16:32:19.361 [83270] <2> bprestore: exit with status = 144
   
   Finally, bplist can recreate the error with the following options:
   # bplist -t 25 -l -R -s 11/15/1999  
   Invalid start date: 11/15/1999  
   EXIT STATUS 144: invalid command usage  

   (NetBackup Clients:  Intel-NT Linux2.4 RS6000_433 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET217320

Description:  
   A DB2 Proxy restore was being attempted for an incomplete Proxy Backup. The  
   restore did not check for the availability of all the backup images before  
   attempting the restore. This caused some of the files to be restored whose  
   images were available and this left the database in an inconsistent state.  

   All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433 Solaris  
--------------------------------------------------------------------------------
Etrack Incident = ET218075

Description:  
   Bprd hits a segmentation fault and core dumps. The issue appears to occur
   when the log file path for the bprestore log exceeds 58 characters.  This
   only occurs when the media server involved is not the master server, and
   when FQDN names are used.
   
   This issue was resolved by increasing the command buffer size to  
   BUFFLEN (4096), and implemented bounds checking on all string buffers,
   where practicable, via the use of V_strlcpy, V_strlcat, and snprintf().  

Additional Notes:  
   While libVcom.so contains no changes, it is required to resolve new entry
   points introduced in libsfr.so.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET217923

Description:  
   Added Solaris10 and Solaris_x86_10 to drop-down menu.  

Additional Notes:  
   For "Solaris Solaris10" to show when configuring clients into a backup
   policy, you must execute the following command:
   
   /usr/openv/netbackup/bin/goodies/new_clients  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET213860

Description:  
   The wrong name for VxFS_Checkpoint snapshot for Instant Recovery DB2  
   backups was used.  

   (NetBackup Clients:  HP Intel-NT Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET218127

Description:  
   On an Exchange server with localized Chinese, we are unable to enumerate  
   the Exchange mailboxes from the NetBackup client GUI (Backup, Archive, and  
   Restore GUI).  
   
   An attempt to backup the Exchange mailboxes results in a failure, with the  
   following entries shown in the bpbkar log:
   
   14:08:46.932: [488.5380] <2> ov_log::V_GlobalLog: INF -  v_beds::V_FindFirst
   ()
   ENTER Name:Microsoft Exchange Mailboxes: Mode:2
   14:08:46.932: [488.5380] <2> ov_log::V_GlobalLog: INF -
   bedsExchangeMailboxInit():ENTER (Reason:2)
   14:08:47.025: [488.5380] <2> ov_log::V_GlobalLog: INF - HrCreateProfile():
    Profile ''Backup Exec Exchange Agent 71728ea7.00001504''  
   successfully created
   14:08:47.291: [488.5380] <2> ov_log::V_GlobalLog: INF - ConfigureMsgService
   ()
   returned 81002746.!user żÁ§!
   14:08:47.307: [488.5380] <2> ov_log::V_GlobalLog: INF - Somehow we failed  
   but without setting the return code  hres =81002746!
     

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET217394

Description:  
   A c0000005 (access violation) exception occurs in tar32.exe during the  
   restore of an Exchange Storage Group from a VSS backup image.  
   
   The tar32 log ends with:
   
   9:31:06.581 AM: [916.4272] <2> ov_log::V_GlobalLog: INF - StreamInfo  
   Id:SCBD FSAttrib:0x0 FSAttrib:0x0 CAlgor:0x0 Flags:0x0 Size:2566
   9:31:08.206 AM: [916.4272] <2> ov_log::V_GlobalLog: INF - ShadowCopy Backup  
   Component Doc Stream Header
   9:31:08.206 AM: [916.4272] <2> ov_log::V_GlobalLog: INF - StreamInfo  
   Id:SCWT FSAttrib:0x0 FSAttrib:0x0 CAlgor:0x0 Flags:0x0 Size:22868
   9:31:08.206 AM: [916.4272] <2> ov_log::V_GlobalLog: INF - ShadowCopy Writer  
   Table
     

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET206031 ET211885ET211834

Description:  
   Resolutions to the following issues have been added.
   ET206031  Memory leak encountered in the XBSA library.
   ET211885  DB2 BLI backup failure
   ET211834  BLI backups with multiple streams fail  

   All NetBackup Windows Clients HP Linux2.4 Linux64 RS6000_433 RS6000_51 SGI
   Solaris Solaris9  
--------------------------------------------------------------------------------
Etrack Incident = ET219207 ET229830

Description:  
   Added Solaris10 and Solaris10 x86 to the client drop-down list.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET218484 ET219090

Description:  
   ET 218484 : The NetBackup server from the user's configuration was ignored  
   when the DB2 policy was read.  As a result, a backup started from a policy  
   residing on a server listed in the user's configuration would fail if the  
   same policy was not present on the server listed in the master's  
   configuration.  
   
   ET 219090 : Starting BLI Incremental backups from the scheduler using an  
   Advanced Client Backup (Proxy) script starts a full BLI backup.  
     

Workaround:  
   ET 218484 : Ensure that the required NetBackup server is configured in the  
   master's configuration (/usr/openv/netbackup/bp.conf).
   
   
   ET219090 : The problem is encountered on a BLI scheduled backup using a  
   Proxy (Advance client) script. The workaround is to use a template instead  
   of a script.  

   All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433 Solaris  
--------------------------------------------------------------------------------
Etrack Incident = ET221820

Description:  
   There is a potential for missed files if all the following conditions  
   exist:
    1) Advanced client backup.
    2) Incremental backup.
    3) Multi-stream backup.
    4) Backup stream is not stream 1.
   
   Files modified after the snapshot is taken but before the (non-stream 1)  
   image is created may be missed.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET219245

Description:  
   After an NDMP import, the file count drops by a very large number.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET222556 ET222796

Description:  
   ET222556 : bpdb2proxy failed to perform the backup. The DB2 library cannot  
   be loaded.
   
   ET222796 : Proxy Restore failed. Incorrect keyword used.  

   All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433 Solaris  
--------------------------------------------------------------------------------
Etrack Incident = ET225034

Description:  
   An incremental multi-stream snap backup with forced stream 1 can miss files.
   The problem exists when the following conditions are true:
    - Snap backup (advanced client, WOFB).
    - Incremental backup.
    - Multi-stream backup.
    - Stream 1 is not due, but is force-started to perform the snapshot  
   operation. Aggravated by ¿frequency¿ mode (frequency is NOT a multiple of
   24-hours).
   
   The problem can be minimized/eliminated by configuring for an "all stream"  
   backup:
    - Use calendar-based scheduling.
    - Use ¿interval¿ mode (frequency is multiple of 24-hours).
    - Avoid multi-streaming snap backups.
   
   This problem occurs because of an oversight in cloning a due stream into  
   a non-due stream1. Remember, stream1 is not due, but is required to  
   perform the snap shot operation. The due stream information is copied in  
   mass to create the stream1 information, and then adjusted to make it  
   stream1 unique. The error occurs because the backup times (last backup,  
   last full backup, last incremental backup) were not updated to the correct  
   stream1 values. As a result of this, stream1 uses the stream2 image  
   creation times. Image creation times are used to compute the delta time  
   which determines the targeted incremental backup files.
   
   Unfortunately stream2 also suffers the same failure. The stream2  
   incremental backup should be based upon the stream1 snap time, but stream1  
   is using the incorrect time for the snap. So, all the due streams suffer  
   this failure.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET219966

Description:  
   Resume of a checkpoint backup could select a different media server if a
   failure on initial backup attempt occurred.
   
   The failure scenario is:
     1) Backup reached a checkpoint.
     2) Then failed (this case was a 13 "read failed").
     3) Scheduler attempts to programmatically re-submit.
     4) But the drives were re-set & downed.
     5) So, the job exited with a 213 "no storage units available".
   
   The original storage unit information was "lost" so the job could  
   potentially resume on a different media server. If resumed in this way,  
   the backed up data would reside on two different media servers and any  
   subsequent restore would fail.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET229834

Description:  
   A loss of MPX groups within bpsched.exe resulted in the failure to cancel
   MPX backups.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET229844

Description:  
   An intermittent problem with installer no longer occurs when trying to
   install to remote clients.  The following two files were not being copied
   to %TEMP%, and caused the following error to appear, "The system  
   cannot find the file specified" on Install GUI.
   
   VERITAS Maintenance Pack.msi
   Data1.cab  

Workaround:  
   To avoid this issue, do the following:
   
   1) Start the installer. Select "Select from available computer on the
   network".  Click Next.
   
   2) Copy VERITAS Maintenance Pack.msi Data1.cab to the %TEMP%directory.
   (easiest way to find what %TEMP% is, is to open a cmd shell and run echo
   %TEMP%, usually its something like C:and  
   Settings<UserName>Settings).
   
   3) Proceed with install.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET230865

Description:  
   An initialization failure against nbwin.exe is generated when a  
   non-administration account initiates a restore.  A pop-up is generated
   stating that nbwin.exe failed to initialize 0xc0000022.  A change to the
   permissions was made to msvcr71.dll so that the user "Users" has Read and  
   Execute permissions.  

Workaround:  
   Manually change the security permissions on msvcr71.dll to allow Read and  
   Execute permissions for "Users" user.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET230374

Description:  
   Changes were made to the bpimmedia command to display proper values in the  
   MGO reports.  

   (All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET230944

Description:  
   Exchange Mailbox backups fail with 69 status if the file list contained  
   an entry which did not exist.  
   
   Changed to have Exchange Mailbox backups exit with a status of 1 if a file  
   list entry does not exist.  

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

Description:  
   The condition where folders are not included in the backup is only noticed  
   during restore operations when attempting to select the folders/files for  
   restore. The folder, sub-folder and or files are missing from the backup  
   selection. This is a randomly occurring condition that does not occur in  
   every NetBackup environment. The problem is related to a suspected memory  
   corruption and may occur without notice and warning.
   
   NOTE: The error may never occur because not all Windows systems are  
   susceptible to the memory corruption.  Not every Windows system will skip  
   folders and files during the backup.
   
   This issue applies to the following:
   
    - MS-Windows-NT and FlashBackup-Windows policies for both full and  
   incremental schedules.  
    - Any Windows client using VSP or VSS.  
    - Windows Open File Backup (WOFB) and Advanced Client backup.
   
   Although VERITAS has been unable to duplicate the issue, the following  
   conditions have been reported:
   
    - The policy must contain a file list stating the drives in alphabetical  
   drive order.
    - The policy must not use Multi-Streaming.
    - The Client must be configured for individual snapshots.
   
   This issue is not noticed when multi streaming or if the file list  
   directive is ALL_LOCAL_DRIVES or when using a global snapshot.
   
   If all of the above conditions are met, the backup will include only root  
   or top level directories, no sub folders or files.
   In severe cases, only the drive letter is visible in restore selections.
   
     

Workaround:  
   The following workarounds are available that reduce but do not guarantee  
   complete success if the Client is susceptible to the memory corruption:
   
   1. Enable multiple data streams
   2. Change the client to use a global snapshot.
   3. If using 5.0GA MP1, uninstall MP1 and execute the backup schedule with  
   5.0 GA.
   4. Disable WOFB and Advanced Client backup methods.  

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

Description:  
   The cancel_all_exceeded_max_wait() function does not scale well in large  
   environments. This change modifies the way incomplete jobs are processed  
   when they have exceeded the maximum incomplete time.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET233426

Description:  
   A DB2 Proxy shell script generated from a template fails when executed from  
   the command line. The same script runs when executed from the scheduler.
     

   All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433 Solaris  
--------------------------------------------------------------------------------
Etrack Incident = ET224678

Description:  
   Improved VMD debug logging to better enable analysis for slow servers.
   
   Allow control of VMD child timeouts, such that slow servers can be  
   interrupted, before VMD encounters connection timeout's on other
   connections.
   
   Add "VMD_CHILD_TIMEOUT = xx", to the vm.conf file.  The value "xx" is the
   number of seconds to wait for a child to release its lock on the volume
   database.  Allowable time is 60 - 360 seconds, where 360 is the default
   (and value used prior to this patch).  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET218653

Description:  
   A race condition existed when two restore jobs needed the same piece of  
   media, from the same server, when this media was not already in the media  
   database.  The condition could cause the media to be added twice and one  
   of the restores to fail.  

   (All NetBackup Servers)
================================================================================



Attachments

NB_51_3A_M_277825.winnt.intel.exe (40.3 MBytes)


Legacy ID



277825


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


Terms of use for this information are found in Legal Notices