Maintenance Pack NB_51_3A_M.winnt.IA64.exe provides fixes to the VERITAS NetBackup (tm) Enterprise Server / Server 5.1 on Windows XP/2003 64 bit clients.

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


Environment

Issue



Maintenance Pack NB_51_3A_M.winnt.IA64.exe provides fixes to the VERITAS NetBackup (tm) Enterprise Server / Server 5.1 on Windows XP/2003 64 bit clients.

Solution



 NB 5.1GA Pack NB_51_3A_M README                                    July 11, 2005
================================================================================
This Maintenance Pack provides fixes to the VERITAS NetBackup Windows 64 bit  
server and clients.


I.   DOWNLOAD INSTRUCTIONS
II.  KNOWN ISSUES
III. INSTALLATION INSTRUCTIONS
IV.  UNINSTALL INSTRUCTIONS
V.   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.IA64_<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.IA64_<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 Microsoft Cluster Environment:

1) Install this Maintenance Pack on the inactive node(s) of the cluster  
  (follow steps 1-4 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:

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.


===========================
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 <install dir of NetBackup>_Uninstaller.exe and  
  double-click on the executable.

3) Select correct Pack to be uninstalled.

4) Click on Uninstall.
 
5) You may review the trace file  
 (<install dir of NetBackup>_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, Symantec strongly  
    recommends the "best practice" of being at the latest patch level.

Additional Notes  
    Any additional information regarding this problem or feature is included.


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

=========
NB_51_2_M
=========
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 = 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 = 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 )




=========
NB_51_1_M
=========
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 = ET204471

Description:  
   A GPF occasionally occurs when exiting the NetBackup Administration Console  
   or the NetBackup license GUI.  There are no negative impacts, it just fails  
   to close cleanly.  

   (All NetBackup Servers: Intel64)
--------------------------------------------------------------------------------
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 = 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 = 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 = 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  
================================================================================


Attachments

NB_51_3A_M_277824.winnt.IA64.exe (55.8 MBytes)


Legacy ID



277824


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


Terms of use for this information are found in Legal Notices