This README describes fixes contained in Maintenance Pack NB_ARO_45_7_M.NT for the VERITAS NetBackup (tm) Advanced Reporter product for NT and Windows 2000 servers.

Article:TECH30972  |  Created: 2004-01-29  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH30972
Article Type
Technical Solution

Product(s)

Environment

Issue



This README describes fixes contained in Maintenance Pack NB_ARO_45_7_M.NT for the VERITAS NetBackup (tm) Advanced Reporter product for NT and Windows 2000 servers.

Solution



NB 4.5MP6 Pack NB_45_7_M README                                    June 29, 2004
================================================================================
This Maintenance Pack provides fixes to the VERITAS NetBackup NT server and
clients. It also contains fixes for NetBackup Add-on products and Database
Agents.

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

================================================================================
The following link provides detailed information on how to install all
necessary NetBackup Maintenance Packs in order:    http://support.veritas.com/docs/268937



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

    -- 4.5 MP6 must be installed prior to installing this Maintenance Pack.

    -- For the latest robotics support please also download and install the
       latest Mappings_4.5.<6 digit number>.zip from the support website:
       www.support.veritas.com.


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


=========================
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_45_7_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_45_7_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
=================
The following are known issues with NB_45_7_M.  Please note that
these known issues will NOT be resolved after installing this pack.

Description:
   RSM libraries do not work currently with Windows Server 2003.  
   There is a possible RSM API problem with the OS.

Description:
   IDR is not supported in MP3 for Windows Server 2003.

Description:
   BE tape reader with any version of NBU (4.5 FP3/MP3), will not work
   with Windows Server 2003. This is because BE tape reader uses
   Backup Exec 8.6 to restore tapes and Backup Exec 8.6 does not work with
   Windows Server 2003.

Description:
   NetBackup for Lotus Notes does not support the file list directive,
   ALL_LOTUS_DATABASES.

Workaround:
   Add the Domino data directory, containing the database files with
   extensions .nsf, .ntf or .box, in the file list instead of using the
   ALL_LOTUS_DATABASES file list directive.  There will be an increase in
   performance since the NetBackup for Lotus Notes extension does not have
   to parse the file system for .nsf, .ntf or .box extensions.

Description:
   NetBackup extension for Lotus Notes is not supported in the
   Microsoft Cluster environment (MSCS).  NetBackup does support Lotus Notes
   in a non-clustered configuration.

Description:
   When configuring a Vault profile, if the user goes with the default
   selection criteria for Media Servers (on the Choose Backups tab),
   which is "<all media servers>" (this default is probably good for most
   configs), and if the user uses Advanced Configuration for the
   Duplication step (more likely for bpvault 3.4 users who upgrade to 4.5),
   but specifies fewer Duplication Rules than there are Media Servers,
   then a heavy warning message box should appear, warning the user
   that this configuration may create unexpected behavior and may send
   duplication data (backup images) over the network.  (In a fully connected
   SAN environment where every media server has access to the robot,
   this shouldn't be a problem.)  This warning box does not appear,
   so we may have lead the user blindly into a problematic
   configuration which will cause excessive network traffic.

Description:
   If a Vault profile is configured to do a catalog backup (highly likely),
   and if the catalog is too big for one tape, causing the user to configure
   the Catalog Backup step with a backup policy (2-phase catalog backup),
   and if, at runtime, the backup policy phase of the catalog backup step
   fails, then an empty tape from the catalog backup volume pool
   will be left assigned (but unused).  This tape will never be used by
   NetBackup until the user realizes that it's assigned but empty,
   and manually unassigns it.


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

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

2) Use the MSCS move group command to 'failover' the server 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) Use the MSCS move group command to 'failover'
  the server back to the original node.

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

Installation steps:

NOTE:  If upgrading a NetBackup Windows 4.5 MP7 client to server or
      Administration Console, the 4.5 Maintenance Pack must be uninstalled
      prior to upgrading to 4.5 server or Administration Console.

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
  ControlPanel -> 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 <install_path>\patch\History.Log file to ensure that no
  errors took place during the installation. For example, an error during
  Maintenance Pack installation because of a busy file.

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


===========================
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
  ControlPanel -> Services tool.  Repeat this until all databases have been
  stopped. These services must be restarted once the patch is successfully
  installed.

2) Go to <install dir of NetBackup>\Patch\Pack_Uninstaller.exe and double-click
  on the executable.
  (i.e. C:\Program Files\VERITAS\Patch\Pack_Uninstaller.exe)

3) Select correct Pack to be uninstalled.

4) Click on Uninstall.

5) You may review the trace file
  (<install dir of NetBackup>\Patch\Pack_Uninstall.log)
  to see what files were replaced.


=================================
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, VERITAS strongly
    recommends the "best practice" of being at the latest patch level.

Additional Notes
    Any additional information regarding this problem or feature.


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

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

================================================================================
Description:
   When a Vault session ejects media to a SCSI robot, the session may fail with
   an error code 293 due to the robot being busy.  Vault now retries the eject
   operations when the robot is busy.

Additional Notes:
   This problem can occur when tape mounts or GUI robotic operations are
   performed during a Vault session.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   When different vault sessions are run concurrently, the vlteject.mstr file
   may become corrupted because of timing issues with processes trying to
   read/write to this file at the same time.
   
   This fix reduces the chances of this file getting corrupted.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   When starting several mounts simultaneously, the user may see "unable to
   read ack" messages in the syslog from the robot daemon as it tries to
   communicate to the robot control daemon. This is more likely to occur with
   TL8 libraries, and can occur with either. This may also lead to a hung
   parent daemon that reports a syslog error of being out of file handles.
   (errno = 24, EMFILE)
   
   TLD only: NetBackup re-initializes the ADIC Scalar 10K library before
   downing the drive in the event of a hardware error on the drive.  NetBackup
   will no longer reinitialize this library.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   The number of parallel streams specified in an Oracle RMAN template that is
   built using the Oracle RMAN Backup Wizard will be used for Archived Redo
   Log backups in addition to Tablespace and Datafile backups.  Previously,
   only one stream was used for Archived Redo Log backups even if a greater
   number of streams was specified in the template.

   All NetBackup Windows Clients Alpha Dgux HP Linux2.4 RS6000_433 SGI SOLARIS
--------------------------------------------------------------------------------
Description:
   When doing a detailed import or verify, when there are lots of small
   files, the logging takes longer than it should.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   In some restores from multiple images on the same tape, more than one
   image restore can be started at the same time causing bptm to core dump.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   When restoring large numbers of small files with a detailed progress log
   on a media or master server, the O_SYNC flag on the open of the progress
   log can cause the restore to take much longer than it should.

Workaround:
   Do the restore from the client or don't get a detailed progress log.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   A backup of Lotus R6.0.3 or Lotus R6.5 will not back up subdirectories.

Additional Notes:
   Support of Lotus R6.0.3 on Windows requires a Lotus patch (provided
   as a hotfix) for SPR# THUR5LPPW9 to resolve an enumeration problem
   encountered in the Lotus API function NSFSearch().  Customers should
   contact Lotus Support and provide the SPR# to obtain the Lotus hotfix.
   
   Support of Lotus R6.5 on Windows requires a Lotus patch (provided
   as a hotfix) for SPR# THUR5LPPW9 to resolve an enumeration problem
   encountered in the Lotus API function NSFSearch().  Customers should
   contact Lotus Support and provide the SPR# to obtain the Lotus hotfix.
   
   Without the appropriate hotfix, backups of Lotus Notes will fail and bpbkar
   will log debug messages similar to this:
   
   1:38:22.392 PM: [3444.1200] <3444> nbex_DebugLog: ERR - NBLNtoFINDDATA()
   NSFDbOpenExtended('D:\Lotus\Domino\Data\Partition1\domino\domino\cache')
   Failed: 0x103:File does not exist.
   
   If the hotfix has been installed for Lotus R6.0.3, the Lotus Server console
   will display the following version information:
   
   Lotus Domino (r) Server (603HF80 for Windows/32)
   
   If the hotfix has been installed for Lotus R6.5, the Lotus Server console
   will display the following version information:
   
   Lotus Domino (r) Server (65HF116 for Windows/32)

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Description:
   The Troubleshooting wizard in the Windows NetBackup Administration Console
   does not work on Windows XP and other newer Windows OSs.

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
   The NetBackup Administration Console for Windows may crash on Multi-
   Processor systems due to a threading issue with pending requests in the
   Device Monitor.

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
   The bpbrm -stream_count argument is not correct for frozen image or split
   mirror backups.  The error manifests itself in the "-stream_count" being
   zero for stream number 1, and 'n-1' for streams 2 through n.
   
   It's worse for frozen image or split mirror backups using retention level
   24: the -stream_count argument is zero for all streams.
   
Workaround:
   1) Stagger multi-stream frozen image job start windows.
   2) Avoid retention level 24 for multi-stream frozen image jobs.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   When starting a backup using -i (immediate), and -L (logging) turn on
   progress logging for the client, the job doesn't appear in the bpjobd
   monitor (Activity Monitor).  I get the following error in the
   bpjobd debug log: Jobid came as 0.
   
   Currently adding formal ability to use backup progress logging on clients
   when using the bpbackup -i, which is currently disallowed by bprd and
   bpbackup.  Also, note that bpbkar is successfully receiving the -L
   option, so bpsched seems to pass along the log file successfully.
   
   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   bpsched core dumped on active node of VCS cluster while running jobs.
   
   The problem is: the fixing of memory leaks went a little too far here
   and tried to free a literal character pointer.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Ejecting more than ~642 tapes results in the vlteject process failing.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   All Vault duplications were deemed successful (as stated in the duplicate
   logs); however, the detail.log shows error 308 (no images successfully
   duplicated). This issue happens even for the most simple of vault
   duplication (for example, one image). The speed of the duplication was also
   considered reasonably fast.

Additional Notes:
   This is an issue specific to AIX 5.2, as the fundamental behavior of a
   libc function ( fgets() ) has changed.  Perhaps to be consistent with a
   recent POSIX proposal.
   
   The change to code alleviates the AIX problem, and is benign on other
   platforms.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   For ACS robot types, if a tape that is to be ejected is mounted while an
   eject of that tape is in progress, the eject job may never complete.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   Certain robotic conditions could cause a Vault job to end prematurely.  
   Retry logic has been added around the robotic inventory vault process to
   accommodate this problem.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   The bpsched process core dumped and left a child process still running. The
   remove_from_mpxgrp_activelist() function attempts to free pool information,
   but the pool pointers are really residue.  Changed add_to_active_job_lists
   () function to initialize the malloc'd structure.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Performing consolidated ejects and reports could result in the completion
   status of the individual sessions not being updated correctly.  Vault could
   incorrectly update a session as complete when it is not.  This results in
   the operator being unable to complete the ejects or reports for the
   sessions that were consolidated.

Workaround:
   Do not perform consolidated ejects or reports.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   Performing a consolidated eject could result in volumes being moved into
   the wrong off-site volume group.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   If SQL Server 7.0 is installed as the default instance on a host and one or
   more SQL Server 2000 instances exist, the SQL agent "DBMS log on options"
   dialog may display the incorrect SQL version when one of the other SQL
   instances is selected.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   If an error occurs that leaves the bpbkar process running on a client
   during a Flashbackup, the scheduler will resubmit the backup.  This results
   in a error 20 because the cache file is still being used by the previous
   backup process. A change has been implemented to let bpbrm terminate and
   wait bpbkar to finish before reporting the error to bpsched.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   On the Firewall tab of Host Properities in the Windows GUI, the settings
   for existing clients change when new clients are added or deleted from the
   list.

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
   If the user selects a differential database backup from the SQL Server
   backup history dialog, the SQL agent should attempt to determine a full
   recovery path. This functionality (removed in 4.5 MP1) is restored with
   this patch.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   PROBLEM: The SQL restore dialog box doesn't scroll correctly.
   SOLUTION: The scroll/resize logic has been altered to improve the scrolling
   properties of the restore dialog.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   When a system has more than 62 mounted volumes, backups may fail with
   either a status 41 or a status 54.  The exit status is due to the bpbkar32
   application crashing.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   This change includes version 3.23.58 of MySQL for nbdbd.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   When bperror was run it could not load the localized resource dll
   (Japanese), it should have retried using English resource dll's but did
   not.
   
   admincmd\bperror  Error: Can't find Troubleshooting Guide, or status code
   not available.
   
   The resource dll in place: NBWTroubEN.dll

Workaround:
   Change the NetBackup Machine Default Locale from default to English.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Create SQL Server user_ops directories if they do not already exist. This
   action prevents an SQL backup from failing if the user has deleted the
   directories or if they were not created during the install.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   Alternate buffer method for backup should not be inhibited for SQL Server
   7.0.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   During an NDMP restore, and even though the NAS server reported a
   NDMP_DATA_HALT_CONNECT_ERROR, NetBackup reports the restore as successful.
   (Note: Receiving an NDMP_DATA_HALT_CONNECT_ERROR is rare. Most NAS servers
   report an NDMP_DATA_HALT_INTERNAL_ERROR instead.)

   (All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
   A buffer overrun may cause the volume manager daemon vmd to fail.

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
   When doing a Remote NDMP backup, the backup hangs after hitting EOM several
   times.
   
   This occurs when the tape hits end of media at the very end of the backup
   while Remote NDMP is attempting to flush its internal buffers to tape.

Workaround:
   Retry the backup with a different tape. This condition is not likely to
   occur a second time on a different tape.

   (All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
   If an inline tape copy job starts with multiplexing set to 1, another job
   with multiplexing set greater that one will attempt to multiplex with the
   first job.  The multiplex setting of 1 on the first job caused the job to
   run without multiplexing enabled.  The second job will fail because it
   cannot multiplex with the first job.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   A restore from a Remote NDMP backup that spans tapes may indicate an error
   occurred. This happens only with Remote NDMP on a Windows machine.
   
   The bptm log shows "read_data_ndmp returned 0" which indicates the restore
   was OK. Following this there is an MTFSF 1 tape command that fails with
   IO_ERR.
   
Workaround:
   This error can be ignored. Since read_data_ndmp returned good status, the
   restore was successful. It is only the tape positioning that failed.

   (All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
   If a restore fails because of a media mount timeout, bprd may core
   dump when it finishes processing the restore.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   If the Backup Selection List of an Oracle policy contains a mix of backup
   templates and shell scripts, the shell scripts will not run if they follow
   a template in the list.

   All NetBackup Windows Clients Alpha Dgux HP Linux2.2 NCR RS6000_433
   Sequent4.2 SGI SOLARIS Solaris_x86_2.6
--------------------------------------------------------------------------------
Description:
   When backing up long file names (greater than 256 characters), the
   bpbkar32 process may crash.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   If bpschedreq -predict is executed with a time that is not the current
   day, the exclude dates will not be taken into account.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   An imported backup of a backup copy other than copy 1 would base the
   expiration time on the backup time rather than the current time, which
   would result in the imported backup expiring too early.

Workaround:
   The bpexpdate command may be used to change the expiration of the imported
   backup.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   When multiple densities are used in the same robot, not all drives will be
   used.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Expiring one of the images from a multiple data stream backup causes a
   restore to fail even though the images still exist.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Calendar scheduled jobs may not run when administered from a different
   time zone.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   NetBackup resource DLL's are not being explicitly unloaded. This can cause
   unneeded reboots during an upgrade install.

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
   The "Use Barcode Rules" check box is not checked by default.  The default
   is checked as long as the options dialog is not opened.  Once you open the
   options dialog, the default changes to unchecked.  When you do an
   inventory, the default should always be to use barcode rules.

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
   Restore paths were incorrect for NDMP path-based history.
   
   The list of files for an NDMP backup image are missing the original backup
   path. This occurs with path-based file history running NDMP V4.

   (All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
   A 174 error (media manager - system error occurred) occurred when an end-of-
   media status was returned while trying to write a end-of-file marker on the
   tape.  This may occur on the Windows or SGI platforms.  The bptm log will
   show an entry similar to the following:
   
   00:30:40.803 [3256.4608] <2> io_ioctl: MTWEOF encountered EOM (error 1100),
   return EOT
   
   This is followed by an entry indicating "buffers out of sequence", and the
   174 error.

   (All NetBackup Servers: Intel-NT Sgi)
--------------------------------------------------------------------------------
Description:
   The scheduler "predict" is out of sync with what actually gets run.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   The problem fixed in this patch is related to the Media Going Off-site
   reports for Vault. In particular, the Picking List for Robot and the
   Distribution List for Vault were reporting an "image count" of 0 even when
   there were tapes being ejected with plenty of images on them.
   This issue is now resolved.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   Drives keep going down every few days.  Avrd reports semaphore errors
   similar to the following in /var/adm/messages:
   
   messages.0:Oct 28 21:56:28 server1 avrd[8148]: Error in Semaphore
   Operation - Result too large
   messages.0:Nov  1 03:20:54 server1 avrd[18968]: Error in Semaphore
   Operation - I/O error
   messages.1:Oct 20 01:31:34 server1 avrd[26744]: Error in Semaphore
   Operation - I/O error
   
Workaround:
   Down the NDMP drives that are not working.

   (All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
   Vault run completes, but segment violation occurs at the end of the vault
   run when logs are being closed. This problem only appears to occur on a
   Linux server at kernel level 2.4.9-e.27  

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   Resolves a potential Dr. Watson on Windows NT if an NDMP drive path name is
   too long (exceeds the stack).
   
   With this patch, the new maximum length for drive path name is 128
   characters.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   SAP's backint fails with status 25 when the server value is not set in
   the .utl file and the SAP_SERVER environment variable is not set. The
   server entry is not being picked up from bp.conf and passed to bplist.

Workaround:
   Set server value in SAP init< SID> .utl file or set SAP_SERVER environment
   variable

   (NetBackup Clients:  Alpha HP Intel-NT RS6000_433 SOLARIS )
--------------------------------------------------------------------------------
Description:
   If a client is down when the scheduler is doing autodiscovery, and the
   Windows GUI attempts to modify a policy, the policy may get deleted.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   NDMP backup restore can fail because some NDMP venders do not use "2" as the
   mount point inode number.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Sybase backups fail occasionally with a 143 error if the scheduler is
   unable to connect to the client while writing the progress log.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Restores or backups may erroneously fail with a 52 status (timed out
   waiting for media manager to mount volume).  

Workaround:
   To avoid this issue, set the media mount timeout to zero.

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
   When ejecting media to an ACS robot, the eject process could hang because
   of an unhandled volume status, STATUS_ROBOT_BUSY.  This status is now
   handled appropriately as an error condition.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   When vault sessions are run on a Linux master, the contents of
   vlteject.mstr are deleted during the eject phase. Thus the reports for the
   session and any other pending ejects/reports fail with NetBackup status 296
   (process called but nothing to do). This problem has been resolved.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   On UNIX systems, the tldcd and tl8cd robotic daemons may fail if connections    are opened and closed quickly with no data.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   When restoring NAS data from an NDMP-attached tape drive, the bprecover
   command fails with an EOM (end of media) error.

Workaround:
   Workarounds for this problem:
   - Use a non-NDMP drive.

   (All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
   A missing tape unmount on one of the copies when using Inline Tape Copy may
   cause unnecessary 134 status codes (unable to process request because the
   server resources are busy).

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   When performing drive cleaning from the java GUI, drive names with more
   than 22 characters could cause problems for the GUI.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   During the suspend step of a vault session, a core dump may occur (in
   particular on HP-UX systems).

Workaround:
   The workaround for this issue would be to manually suspend tapes being
   ejected using "bpmedia -suspend -m <media_id>".

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   The NetBackup Administration Console and bpps command lines could crash on
   certain systems while attempting to gather process information via
   Microsoft's Performance Counter APIs if the counter values are not the
   defaults set by Microsoft.

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
   The Remote NDMP ndmpmoverlistener.exe process shows growing handle count
   and page faults, which eventually brings down NDMP drives.

Workaround:
   Stop and then restart the "NDMP Mover Agent" from services.

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
   When NAS vendors don't send a notify data_halted message after sending a
   last file history, remote NDMP waits and eventually fails with a timeout
   error (error 99)

   (All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
   Add support for Oracle 10g.

   All NetBackup Windows Clients Alpha Dgux HP Linux2.2 RS6000_433 SGI SOLARIS
--------------------------------------------------------------------------------
Description:
   In some limited circumstances a change server command will result in the
   console crashing.  This corrects this problem.

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
   bppllist -allpolicies or <policy> -U core dumps

Workaround:
   1) Look for a policy that has an unusually long value for one of its
   attributes, such as the keyword, or that has many clients.  
   2) Run 'bppllist <policy name> -U' to display this one policy.  
   3) If bppllist aborts, modify the policy to reduce the length of
   the long value.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Scheduler gets an occasional core dump when it's preparing to exit. The
   error happens when trying to determine which storage units are busy.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Using a Binary Catalog could cause an inablity to browse for restores under
   certain file selection lists.  This issue has been resolved.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Customers using noauth authentication with the windows GUI would not be
   able to start manual backup jobs if they were not an Administrator on the
   system running the windows GUI.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   The issue fixed by this patch has to do with changing the expiration date
   of disk images from vault after they have been successfully duplicated. If
   bpduplicate is passed a long list of image IDs and never gets a
   chance to return to Vault, then Vault does not have a chance to change the
   expiration date of the image.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   Suppose the master server and media server are different servers.  Also
   suppose that the media server and client are the same machine so that
   shared memory backups and restores are normally done.
   
   Suppose the master server is configured so "connect backs" with the media
   server are done using VNETD. The typical bp.conf entry on the master server
   would look like this:
   
   CONNECT_OPTIONS = mediax 0 1 2
   
   Where "mediax" is the hostname of the media server. The digit "1"
   signifiies that vnetd style connect backs are used.
   
   In this case, restores will fail.  Typically, the job will fail with error
   code 5 and be marked as "incomplete" in the job monitor.
   
Workaround:
   Do not use VNETD style connect backs with the media server if the media
   server is also a client.

   All NetBackup Windows Clients All NetBackup Unix Clients
--------------------------------------------------------------------------------
Description:
   Correct an end-case problem in MPX read processing (for
   restores and duplications) that may try to unmount a media that is already
   in use by another process.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   When verifying very large backup images, the Activity Monitor would
   incorrectly report a failure status that included a client process
   aborted error message.  Testing showed that the verify job had not
   actually failed and the incorrect status was displayed because the
   keep-alive checks were not being sent to bpjobd if the bpbrm socket was
   active for specified amount of time.   This time interval to send
   keep-alive packets has been corrected, resolving this issue.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   If an error is encountered while attempting to open Lotus change
   information during a Lotus backup, the backup will crash if the debug
   logging level is increased. This problem has been resolved.

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Description:
   Exchange backups do not support bandwidth limitation throttling.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Exception error occurs in tar32 when trying to restore an Exchange
   Information Store when the Information Store service has been stopped.  

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Description:
   If an invalid alternate path is specified when performing a mailbox
   restore, the restore fails with a status 5 and a Dr. Watson is generated
   for the tar32.exe process.
   
   This error can occur when selecting the entire Inbox or just a single
   message from one mailbox backup image.

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Description:
   If SQL Server is configured under binary collation, some images may not be
   displayed in the NetBackup SQL agent's backup history window.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   When BATCHSIZE is set in the SQL agent batch file, some of the backups
   fail with errors such as the following:
   
   12:53:45 [2276,2476] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC
   message. ODBC return code <-1>, SQL State <IM002>, Message Text <
   [Microsoft][ODBC Driver Manager] Data source name not found and no
   default driver specified>
   12:53:45 [2276,2476] <16> Dbbackrec::PerformNBOperation: USER - Unable
   to login into ODBC DSN <NBMSSQL_2276_2100> as user <sa>

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   When creating VSP snapshots for backups, the snapshot creation can
   disregard volumes in the VSP "Cache File Volume List" when they could have
   been used as cache file locations.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   When auto-sizing a VSP cache file when it is placed in a volume
   other than the volume being snapshot, NetBackup may calculate its maximum
   size to a value smaller than the correct value. This can cause VSP snapshot
   errors to occur and the backup could end with status 155: disk is full.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   NetBackup SQL Server agent connects to SQL Server 6.5 hosts with integrated
   security.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   After upgrading to NetBackup 3.4_2, the combined job status entry is not
   always written to the progress report log files in the
   install_path\NetBackup\logs\user_ops\teradata\logs directory.  
   The following is an example of a combined job status entry:
   
   07:44:23 <4> [0,candy] Combined job status: Succeeded 2, Failed 0,
   Unknown 0.
   
   The contents of the log files are documented in the "Progress Reports
   Created for NetBackup for Teradata" section of the NetBackup 3.4 for
   Teradata System Administrator's Guide.

   All NetBackup Windows Clients NCR
--------------------------------------------------------------------------------
Description:
   Oracle version 8.1 with Oracle Failsafe in Microsoft Cluster Server (MSCS).
   
   When an Oracle instance in the Backup, Archive, and Restore interface is
   selected, an authentication box is display. The user has to enter a valid
   username/password with DBA priviliges to continue.  After this information
   is entered, the following error is displayed:
   
   Unable to connect to <Instance Name here>. Error Code = 12154
   
   Consequently, the user is unable to continue to create or locally
   administer templates.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   bpdbm's host list is not consistant with that of bprd. The current
   impact of this issue reported by customer
   is "FORCE_RESTORE_MEDIA_SERVER doesn't work for TIR restores."
   
   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   When the NetBackup Oracle agent Backup Wizard is used to create a COLD
   backup script, the backup fails with a status 29 because the script is
   calling the "init<SIDname>.ora" file.  In Oracle 9.2, there is no such
   file.

   (NetBackup Clients:  Alpha HP Intel-NT Linux2.2 RS6000_433 RS6000_51
    Sequent4.2 SGI SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
   Exchange Server shutdowns due to lack of space on the transaction log file
   device.
   
   The transaction logs were probably not truncated because the Exchange
   backup failed. The original backup may have failed due to networking or
   media failures and retry attempts may fail with a status 1.
   
   Investigation of the Error logs would reveal the following error,
   "INF - HrESEBackupSetup: Microsoft Information Store = 0xc80001f9"
   "ERR - XCHG_BackupRead() FS_ReadObj() Failed! 0xFFFFFE30:FS_COMM_FAILURE".
   These errors indicate that the Exchange StorageGroup is already in
   backup mode. Close inspection may also reveal that the bpbkar32 from the
   original backup attempt is still running

   (NetBackup Clients:  Intel-NT )
--------------------------------------------------------------------------------
Description:
   When using the Windows PC Client interface, if the user does not have
   permission to write or modify the folder that contains the NetBackup log
   files, an attempted restore to an alternate path will correctly be
   aborted.  

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   A user that uses Oracle "Template Administration" from the NetBackup
   Windows PC Client interface to run or edit an existing Oracle template will
   have his/her authentication and recovery selections correctly reflected in
   the new template.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   When using the NetBackup PC Client Windows interface to do a Lotus Notes
   user-directed backup, the NOTES.INI path field in the "Specify Backup
   Options > Lotus Notes" page is now processed correctly.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   Problems querying/updating the volume database during an eject could lead
   to the eject job failing prematurely, leaving a session incomplete.
   
   Also, consolidated eject/report jobs that were partially successful could
   be erroneously marked as complete and volumes may have an incorrect off-
   site volume group leading to report inconsistencies.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   If the REQUIRED_INTERFACE entry is present in the vm.conf file, problems
   may occur with the vmquery or vmupdate commands.

Workaround:
   Remove the REQUIRED_INTERFACE entry from the vm.conf file.

   (All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
   Performing consolidated ejects for all robots could malfunction if the
   vault configuration contains multiple robots of the same robot type. This
   problem could result in media being left in an incorrect off-site volume
   group. Also, media ejected from some of the robots doesn't occur but
   appears to have completed successfully.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   Non-root users of vault are unable to eject media with vault. The
   vlteject.mstr.lock file gets created with 600 permissions under unix.
   This will prevent non root NBAC users from aquiring the lock, and ejects
   will hang waiting for that lock file.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   When a duplicate profile name existed in separate vaults, and selecting an
   alternate session number, vltopmenu required that the triplet be fully
   qualified, instead of first defaulting to the current vault.

Workaround:
   To avoid this issue, you should not duplicate profile names.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   When performing backups with TIR plus move detection, some backups may not
   verify correctly due to files/folders having identical file numbers.

   All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
   Managing calendar-scheduled backups when the master server is in a
   different time zone than the Administration GUI causes the jobs to run in
   a restricted time window or not at all.
   
   There is no longer a limit on the number of calendar include/exclude dates
   within a schedule.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   vltrun is frequently failing with a status 282 and also dumping core.
   
   Subordinate commands executed by bv_run_system() must not be allowed to
   return an exit status of 0, when the child was killed by a signal.  Insure
   that children killed by a signal, and have a zero exit status, are actually
   attributed a non-zero exit status (EC_process_killed).

Additional Notes:
   If the image database is corrupt, as it was in the problematic case, the
   problem is exposed.  bpimagelist had returned a 'space' where vault had
   demanded, and expected, a significant entry.  The resultant failure exposed
   a long sequence of erroneous vault behavior.

   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   On a system running Windows 2000 (SP4), you may not be able to browse or
   restore the second volume if 'SET HIST=N' is listed in the middle of the
   policy's file list.

Workaround:
   To avoid this issue, contact your VERITAS customer support office for help
   on manually fixing your catalog files.  

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Duplication of multiple copies using Inline Tape Copy may fail with a 20
   error (invalid command parameter).  The bptm log (the write side of the
   duplication) shows an entry similar to the following:
   
   14:55:48.274 [5586] <16> bptm: not enough parameters specified

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   A media position error can occur when attempting to restore from a copy of
   a backup created by Inline Tape Copy.  The bptm log will show an entry that
   is similar to the following (note the file number of 0):
   
   13:12:27.348 [22187] <2> mpx_read_init: media id A00001, copy 1,
   fragment 1 (839680 Kbytes) filenum 0 being considered for restore
   
   The problem occurs when performing multiplexed backups using Inline Tape
   Copy, and a new backup is started while waiting for a tape mount due to
   hitting end-of-media.  

Workaround:
   To avoid this issue, the restore may be done from the other copy.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   When using Inline Tape Copy, the wrong media-id may be frozen when a media
   error occurs on a copy other than the first copy.  This happens when the
   fail-on-error attribute is set for the failed copy.  In this case, the
   media-id for the first copy is frozen rather than the media-id for the copy
   that obtained the error.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   If a schedule is changed from Frequency to Calendar scheduling and
   "Last Day" is chosen from "Recurring Days of the Month," bpclsched will
   crash.  This occurs from both the command line and from the Java GUI.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Unable to restore NDMP NetWare data due to an invalid path shown in catalog.
           
   If \\Server\Vol1\Dir1 is specified as a file selection that is backed
   up, the Backup, Archive, and Restore screen shows the tree expanded as
   Vol1\Dir1\Vol1\Dir1.  
   
   The restore fails with "Cannot restore from filepath \Vol1\Dir1,
   NDMP_HALT_INTERNAL_ERROR occured" and a status (5). The data cannot be
   restored to the original location or redirected using a valid path.
   
   (All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
   VOPIE Enhanced Authentication may not work when host names are longer than
   32 characters.
   You may see Authentication Failed (error code 160) messages when connecting
   to systems with host names or client names greater than 32 characters.
   
   All NetBackup Windows Clients All NetBackup Unix Clients
--------------------------------------------------------------------------------
Description:
   Exchange restores from multiple images fails with a communications failure
   error. The log will have a message similar to the following:
       
   17:58:45 (158515.002) ERR - unable to create object for restore:
   Microsoft Information Store:\SG01102\Log files_1074011439 (BEDS
   0xFFFFFE30: A communications failure has occurred.
   
Workaround:
   Create a file named /usr/openv/netbackup/NON_MPX_RESTORE to force
   sequential restores from multiple images.
   
   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   Ejects that are partially-successful are erroneously marked as completed.  
   As a result, the operator can't eject the remaining media or re-run reports.
   (All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
   When using "bpexpdate -recalculate" or "bpexpdate -backupid" to extend the
   expiration date of one or more backups that have multiple copies, the media
   expiration may not be correct for copies on removeable media if the first
   copy is on disk.

   (All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
   The W2k platforms were losing MPX groups. The user could not cancel
   orphaned jobs within the MPX group, and additional jobs could not be added
   to the MPX group.
   
   Windows-specific code was added to display questionable pointer values
   prior to releasing the MPX group. Historically, this minor change caused
   the problem to "go away." The thinking being that it's a W2k compiler
   optimization issue. This fix will either mask the problem, or help isolate
   it.

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




Legacy ID



266418


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


Terms of use for this information are found in Legal Notices