Maintenance Pack NB_CLT_60_1_M.tar provides fixes for VERITAS NetBackup (tm) Enterprise Server / Server 6.0 on UNIX clients. NetBackup UNIX Add-on products and Database Agents have separate Maintenance Packs.

Article:TECH45687  |  Created: 2005-01-22  |  Updated: 2005-01-22  |  Article URL http://www.symantec.com/docs/TECH45687
Article Type
Technical Solution


Environment

Issue



Maintenance Pack NB_CLT_60_1_M.tar provides fixes for VERITAS NetBackup (tm) Enterprise Server / Server 6.0 on UNIX clients. NetBackup UNIX Add-on products and Database Agents have separate Maintenance Packs.

Solution



 CLT 6.0GA Pack NB_CLT_60_1_M README                            December 22, 2005
Corequirement: NB_60_1_M
================================================================================
This Maintenance Pack provides fixes for the VERITAS NetBackup (tm) UNIX  
clients.  NetBackup UNIX Add-on products, Database Agents and the Java GUI have  
separate Maintenance Packs.

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

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

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

    -- On a server, NB_CLT_60_1_M (this Maintenance Pack) can be installed on a
       client using a remote installation procedure or a local installation  
       procedure.
     
    -- Only on a NetBackup server, NB_60_1_M_<6 digit number>.<server>.tar
       must be installed after this Maintenance Pack is installed.

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

NOTE: This Maintenance Pack requires approximately 1.5-2GB in disk space to  
extract and install. This Maintenance Pack contains a full replacement of all  
client binaries for all platforms.  For more information, please refer to the  
following TechNote:    http://support.veritas.com/docs/280824

 

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

      Pack History
        None


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

  where <6 digit number> is an internal tracking identifier

    NOTE: NB_CLT_60_1_M_<6 digit number>.tar contains all client  
          binaries.

2) Extract the NB_CLT_60_1_M_<6 digit number>.tar file
       tar xvf NB_CLT_60_1_M_<6 digit number>.tar

       This will create the files:
       VrtsNB_CLT_60_1_M.README
       VrtsNB_CLT_60_1_M.tar.Z
       VrtsNB_CLT_60_1_M.preinstall        
       VrtsNB_CLT_60_1_M.postinstall
       VrtsNB_CLT_60_1_M.postuninstall  
       Vrts_pack.install


==================
II.  KNOWN ISSUES
==================
Nothing to report at this time.



===============================
III. INSTALLATION INSTRUCTIONS
===============================
NOTE: Click on the "Download Now" link, near the bottom of this document  
prior to running the following installation procedure for this pack.

NOTE:  Symantec recommends that you perform catalog backups before and after
you apply this maintenance pack.

NOTE: If you are upgrading from 5.x to 6.0, you must install this Maintenance
Pack before you run nbpushdata.  Failure to install this Maintenance Pack  
first will result in a failed upgrade.


For Maintenance Pack installation on a UNIX Cluster Environment:
--------------------------------------------------------------------------------
1) Ensure that prior to installing the maintenance pack, NetBackup is at
  release level 6.0 and configured to run in a cluster.

2) Freeze the NetBackup group (This will avoid a 'failover' during a patch
  installation).

3) Install this Maintenance Pack on the inactive node(s) of the cluster  
  (follow the steps below).

4) Install this Maintenance Pack on the active node of the cluster (follow
  the steps below).

5) Unfreeze the NetBackup group.

--------------------------------------------------------------------------------
There are two ways to install the client maintenance pack software.

1. Remote Installation:  Loads the software on a master server with
   the intent of pushing client software out to affected clients.

2. Local Installation:   Loads and installs the software only to this
   local machine.

Remote client install:

As root on the NetBackup Master/Media Server:

1) Install NB_60_1_M and NB_CLT_60_1_M Maintenance Pack binaries.

       cd /tmp
       /bin/sh Vrts_pack.install

  NOTE: Selecting the client Maintenance Pack on a Master/Media server will  
  automatically install the server maintenance pack if the server (NB) .Z file  
  and README exist in the installation directory. The client install will fail  
  if the (NB) .Z file and README are not present and the server pack has not  
  been previously installed. The server maintenance pack will NOT be installed
  automatically during a reinstall of the client maintenance pack.  

  NOTE: The installation of the client pack on a server copies the appropriate  
  client binaries into place on the server.  Additionally, any other client  
  binaries on the server will be updated so that they can then be pushed out
  using update_clients.

  NOTE: It is important that Server and Client binaries are kept at the same  
  pack level on all NetBackup Servers.  This is enforced by the Pack install  
  process.


2) On a server ONLY: The Vrts_pack.install script will prompt you to restart  
  daemons.  Otherwise, after the pack installation has completed, run:

       /usr/openv/netbackup/bin/goodies/netbackup start

3) The pack install logs can be found in /usr/openv/pack/pack.history once the  
  installation is complete.

4) On a server ONLY, update the remote NetBackup clients with the  
  update_clients script.

       /usr/openv/netbackup/bin/update_clients <hardware> <os>

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

       ALPHA/OSF1_V5
   HP-UX-IA64/HP-UX11.23
   HP9000-700/HP-UX11.00
   HP9000-700/HP-UX11.11
   HP9000-700/HP-UX11.23
   HP9000-800/HP-UX11.00
   HP9000-800/HP-UX11.11
   HP9000-800/HP-UX11.23
   INTEL/FreeBSD5.3
   Linux-IA64/RedHat2.4
   Linux-IA64/SuSE2.4
   Linux/IBMzSeriesLinux2.4.21
   Linux/RedHat2.4
   MACINTOSH/MacOSX10.3
   RS6000/AIX5
   SGI/IRIX65
   Solaris/Solaris8
   Solaris/Solaris9
   Solaris/Solaris10
   Solaris/Solaris_x86_8
   Solaris/Solaris_x86_9
   Solaris/Solaris_x86_10

           
      Note: The /usr/openv/netbackup/bin/update_clients command without
            any parameters will update all the UNIX clients.
             
      Note: When updating an RS6000 client, there may be circumstances
            where update_clients will fail with an error similar to
            this:

            Couldn't open /usr/openv/lib/libVmangle.so on client  
            Client open errno = 26

            If this happens, execute /usr/sbin/slibclean on the client
            to be updated and re-run update_clients.

If the client (CLT) .Z file and README exist in the installation  
directory during the installation of the server maintenance pack,  
the Vrts_pack.install script will install the client
maintenance pack automatically.  The client maintenance pack will NOT
be installed automatically during a reinstall of the server  
maintenance pack.  

Local client install:

The install script will determine if a local client install is appropriate  
and choose the appropriate client type to install.

As root on the NetBackup client:

1) Install NB_CLT_60_1_M Maintenance Pack binaries.

      cd /tmp
      /bin/sh Vrts_pack.install

NOTE:  Again, Symantec recommends that you perform catalog backups after you
have applied this maintenance pack.



===========================
IV. UNINSTALL INSTRUCTIONS
===========================
Note:  This will ONLY uninstall the maintenance pack from your machine
      if the client maintenance pack software was installed directly on the
      machine.  This uninstall procedure will NOT work on clients that were
      installed by pushing the software from a server.
   
As root on the NetBackup Master/Media Server in which the maintenance pack was
installed:

   1) Close the NetBackup user interfaces.

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

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

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

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

   3) Run the un-install script:

         ./Vrts_pack.uninstall

   4) Verify that the pack uninstalled successfully by checking:

       /usr/openv/pack/pack.history.

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

   6) If necessary, restart the NetBackup and Media Manager daemons:

       /usr/openv/netbackup/bin/goodies/netbackup start


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

README Conventions:

Description
    Describes a particular problem contained in this 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 = ET415495

Description:  
   Do not allow a down/disabled media server to block the entire Device
   Allocator (DA) thread pool.  
--------------------------------------------------------------------------------
Etrack Incident = ET423713

Description:  
   There were a few places in the code where the image query protocol version
   was set to 0, which is a pre-NetBackup 5.0 image version ID.  Some image
   queries would fail if the size of the total data being backed up was larger
   than 2TB in one job.
       
   This issue has been corrected enabling image queries on backups greater  
   than 2TB work properly.  
--------------------------------------------------------------------------------
Etrack Incident = ET424051

** Description: **
   A change has been made to avert a potential vulnerability in a Java  
   authentication service that runs on VERITAS NetBackup servers and clients.
   This change prohibits remote attackers from executing arbitrary code on a
   targeted system.  In addition, Symantec recommends that users block the
   affected ports from external network access.  
     
--------------------------------------------------------------------------------
Etrack Incident = ET423045

Description:  
   When sharing tape drives between media servers that were running both
   NetBackup 6.0 and NetBackup 5.x, a problem existed with the NetBackup 6.0
   Scan Hosts.  If the drive being scanned was assigned to a 5.x media server,
   the 6.0 Scan Host might not stop scanning.  This resulted in SCSI
   reservation conflicts and DOWN'ed drives on the NetBackup 5.x assigned host.  

Workaround:  
   To avoid this issue, do not share drives between media servers running
   different versions of NetBackup.  Instead, pool your drives such that all
   of your NetBackup 5.x media servers are sharing one pool of drives and all
   of your NetBackup 6.0 media servers are sharing a pool of different drives.  
--------------------------------------------------------------------------------
Etrack Incident = ET422837

Description:  
   When running multi-streamed Windows Open File Backup backups to back up
   open and/or active files, some VSP cache files in the format of
   _vxfiVspCacheFile_1.VSP, for example, may have been left behind by the
   backup jobs that had already completed.  This did not occur with
   non-streamed backup jobs.  
--------------------------------------------------------------------------------
Etrack Incident = ET428719

Description:  
   Because of a logic error in the handling of "bptm ¿delete_all_expired",
   the expired media was not getting deleted. This would prevent recycling
   of the media.  

Workaround:  
   To avoid this issue, the user can expire the media using bpexpdate.  
--------------------------------------------------------------------------------
Etrack Incident = ET424660

Description:  
   If a hot catalog backup fails and retries, an end of session function is
   executed when jobs are still active.  This could result in extra catalog
   backups to run, extra start and session scripts to run in addition to
   extra catalog cleanup operations.  
--------------------------------------------------------------------------------
Etrack Incident = ET429008

Description:  
   When upgrading from NetBackup 5.x to NetBackup 6.0, the  
   NETBACKUP_RELATIONAL_DATABASE_FILES directive was not added to the list of
   files included in cold catalog backup.  The command, bpsyncinfo -add_paths,
   "NETBACKUP_RELATIONAL_DATABASE_FILES" is run automatically during patch
   installation to add this directive to the cold catalog backup configuration.  
--------------------------------------------------------------------------------
Etrack Incident = ET421370

Description:  
   The NBDB database recovery (for Enterprise Media Manager (EMM) and Bare
   Metal Restore (BMR)) will fail if the master server has a newer catalog
   backup image than the one used in disaster recovery (DR).  On Windows
   platforms, it logged an error message in the progress log and displayed an
   error message box.  On UNIX platforms, because of a defect in the Java  
   user interface, it reported an error message in the log and all of the
   restore jobs appeared in the job monitor as being successful.  

Additional Notes:  
   This maintenance pack enables a user to recover from an older catalog
   backup even though a newer catalog backup image exists on the master  
   server.
       
   Full catalog disaster recovering from an older catalog backup is a  
   ¿roll-back¿ operation that has the risk of data loss. Users should fully
   understand the implications and use it with caution.  
--------------------------------------------------------------------------------
Etrack Incident = ET431863

Description:  
   For a Hot Catalog Backup, the relational database (NBDB/Sybase ASA) backup
   job treated a cumulative and differential incremental backup the same and
   only included the transaction log in the backup.  This can create problems
   recovering the ASA database if the differential backup media created before
   the last cumulative has expired.  These differential backups contained the
   transaction logs that were necessary to roll forward from the last full
   backup.    

Workaround:  
   To resolves this issue, the cumulative incremental backup is actually a
   full backup for the ASA files.  
--------------------------------------------------------------------------------
Etrack Incident = ET406999

Description:  
   Transport of log messages from NBSL to NOM Server was failing and causing
   the Host Session to go down. PSP's TAO_Transport was not checking for  
   EAGAIN.  
--------------------------------------------------------------------------------
Etrack Incident = ET428760

Description:  
   The vmd process would dump core if the EMM service (nbemm) was not running.  
--------------------------------------------------------------------------------
Etrack Incident = ET425765

Description:  
   The nbpushdata function failed when a pool name had a hyphen in the actual
   pool name.  
--------------------------------------------------------------------------------
Etrack Incident = ET492438

Description:  
   Data tapes are no longer treated as cleaning tapes and be FROZEN by  
   NetBackup.  
--------------------------------------------------------------------------------
Etrack Incident = ET494547

Description:  
   Device monitor showed the same tape mounted in multiple drives.  This tape
   in this scenario was also assigned to a NetBackup 5.x media server.  

Workaround:  
   To avoid this issue, do not share drives between NetBackup 6.0 media
   servers and NetBackup 5.x media servers.  
--------------------------------------------------------------------------------
Etrack Incident = ET492704

Description:  
   A Null Reference Exception is produced when creating a custom filter for
   the Driver Detail table (Monitoring -> Drivers -> Details table).  
--------------------------------------------------------------------------------
Etrack Incident = ET425186

Description:  
   Oracle backups no longer end prematurely with a status 25.  
--------------------------------------------------------------------------------
Etrack Incident = ET495004

Description:  
   The nbpushdata function failed with the following messages in the  
   nbpushdata log file:
   
   <4> get_host_info: CEMM_MACHINE_DISK_ACTIVE being set for <your_host>
   <16> emmlib_UpdateHost: (0) UpdateMachine failed, emmError = 2007079,  
        nbError = 0
   <16> get_host_info: (-) Translating
        EMM_ERROR_SQLSyntaxErrorOrAccessViolation(2007079) to 193 in
        the media context  
--------------------------------------------------------------------------------
Etrack Incident = ET418546

Description:  
   The NOM database server uses less CPU utilization over GA.  
--------------------------------------------------------------------------------
Etrack Incident = ET495339

Description:  
   The Windows Open File Backup was not showing retries in the Activity  
   Monitor.  
--------------------------------------------------------------------------------
Etrack Incident = ET495403 ET497074

Description:  
   For media with image expiration set to infinity, nbpushdata passed an
   incorrect value for infinity to the EMM database.  This resulted in the
   media not being queried.  
       
   nbemmcmd -listmedia -mediaid <media_id> NBEMMCMD, Version:6.0(20050906)
   The function returned the following failure status:  
   generic EMM SQL error (193)
   Command did not complete successfully.
       
   vmquery -m <media_id>
   Could not query by media ID A00001 with debug: generic EMM SQL error (193)  
--------------------------------------------------------------------------------
Etrack Incident = ET425768

Description:  
   An issue in nbpushdata caused the nbpushdata ¿remove function to fail.  

Workaround:  
   To avoid this issue, drop the EMM data base and then recreate it.  
--------------------------------------------------------------------------------
Etrack Incident = ET496010

Description:  
   Restores failed with the following errors in the job log and tar debug log:
       
   job log:
   22:16:27 (4753.046) data buffers out of sequence, expected number 157884,  
      received 157886
   23:32:46 (4753.053) data buffers out of sequence, expected number 404927,
      received 404932
       
   debug log:  
   22:16:27 (4753.046) data buffers out of sequence, expected number 157884,
      received 157886
   23:32:47 (4753.053) data buffers out of sequence, expected number 404927,
      received 404932
       
   This issue occurred because the HP 11.23 compiler optimized out references
   to the shared memory control variables.  
--------------------------------------------------------------------------------
Etrack Incident = ET425178

Description:  
   Data Lifecycle Manager consolidation jobs now complete successfully.  
--------------------------------------------------------------------------------
Etrack Incident = ET430806 ET419127

Description:  
   Changed bprd and the Policy Execution Manager (PEM) so that the bprd child
   could terminate and not wait for the job exit status from PEM, unless  
   the -w flag was used on the request.  
--------------------------------------------------------------------------------
Etrack Incident = ET493607

Description:  
   Could not inventory legacy TS8 libraries as TL8.  
--------------------------------------------------------------------------------
Etrack Incident = ET497080

Description:  
   If any inetd entry is missing on a client and update_clients is used to
   push NetBackup client software to it, update_clients will show an error
   message in the log file.  A change was made that corrected the temporary
   file names so that inet.conf on the client will be updated properly and no
   error will be generated.  
--------------------------------------------------------------------------------
Etrack Incident = ET497761

Description:  
   An extremely heavy load in the Device Allocator (DA) may cause EMM to crash.  
--------------------------------------------------------------------------------
Etrack Incident = ET496437

Description:  
   Some vital logs were not displaying correctly.  To be more specific, the
   form that Log:DbLogMsg is being called in the emmserver source files was
   incorrect whenever it was multi-lined in the code. As a result, only part
   of the log message survived and important log information was lost.  
--------------------------------------------------------------------------------
Etrack Incident = ET496608

Description:  
   Non-robotic tape drives that contain unlabelled media will no longer be
   automatically assigned to non-robotic media specific mount requests.  
--------------------------------------------------------------------------------
Etrack Incident = ET498523

** Description: **
   In a rare condition one or more backups would be corrupt when using Inline
   Tape Copy (ITC) with multiplexed backups.  This would potentially happen
   under the following conditions:
       
   - ITC was enabled with two or more active copies.
   - Multiplexing was enabled with two or more active backups.
   - The schedule configuration had the "continue if the copy fails" flag set
       for the copy that failed in the next step.
   - A copy other than the first active copy encountered an "end of media", so
       a new media was needed for this copy.  In addition, there was a problem
       of getting or setting up media (for example, writing the media header)
       such that this copy failed before continuing the backup.
   - The last buffer written to the first active copy prior to the "end of
       media" on the other copy was not the first active backup.  

Workaround:  
   To avoid this problem, do one of the following:
   
   - Edit the schedule configuration to disable the "continue if copy fails"
       flag.
   - Disable multiplexing.
   - Disable ITC.
     
--------------------------------------------------------------------------------
Etrack Incident = ET423206

Description:  
   The back-level media server V_QUERY_CLEAN_BYROBNUM request caused an SQL  
   error.  
--------------------------------------------------------------------------------
Etrack Incident = ET424796

Description:  
   NetBackup Job Manager (NBJM) deadlocks or halts when the connection to
   bpbrm breaks in the middle of a backup job.  
--------------------------------------------------------------------------------
Etrack Incident = ET431510

Description:  
   On initial install the Policy Execution Manager failed to start the first
   time because no IOR file existed for nbproxy.  Once an IOR file existed
   and it is not empty, then the NetBackup Service Monitor was able to restart
   the Policy Execution Manager.  

Workaround:  
   To avoid this issue, delete the IOR files listed below before starting the
   Policy Execution Manager.
       
   On UNIX:
     /usr/openv/var/nbproxy_pem.ior
     /usr/openv/var/nbproxy_pem_email.ior
       
   On Windows:
     VERITAS_pem.ior
     VERITAS_pem_email.ior  
--------------------------------------------------------------------------------
Etrack Incident = ET425564

Description:  
   The Policy Execution Manager would crash after submitting a user-directed
   or manual backup.  
--------------------------------------------------------------------------------
Etrack Incident = ET499610

** Description: **
   Synthetic backup had potential data loss issues in following cases:
   -  The last full/synthetic or full expired/deleted occurred,
        followed by one or more incrementals and a synthetic backup.
   -  The last incremental/full backup catalog was compressed before
        next incremental backup took place.
   -  The TIR records in the last incremental backup are missing for
        various reasons.  
--------------------------------------------------------------------------------
Etrack Incident = ET505873

Description:  
   Media servers sharing drives on versions of NetBackup older than  
   NetBackup 6.0 will receive host_not_registered errors when attempting to
   determine if another media server is unavailable.  
--------------------------------------------------------------------------------
Etrack Incident = ET506551 ET499474 ET506690

Description:  
   This entry resolves three seperate issues described in the following list:
   - Under certain conditions backups would not schedule.  This happened
       because of a problem in computing the next time a job was due.  Windows
       were not processed correctly if a backup should have run in a previous
       window if the next window opened or closed at a different time.
       
   - Advanced client VSS snapshot backup no longer causes an 805 error to
       occur.  
   
   - The scheduler always executes Full backups, even for incrementals, if the
       BMR option is on.  nbpem would use the wrong criteria for the last
       backup query made for a parent job that did not have multiple data
       streams enabled.  The result was no last full backup being found, so a
       full would be run instead of an incremental.  
----------------------------------------------------------------------------------------
Etrack Incident = ET496102

Description:  
   As the number of VxUL log files grew, the start-up performance of bprd
   would degrade.  

Workaround:  
   To avoid this issue, delete the log files on a regular basis.  
--------------------------------------------------------------------------------
Etrack Incident = ET506045

Description:  
   nbpushdata was using emmlib_DeleteHost to remove the NDMP host when the
   following error occurred in the nbemm log.  The following is a portion of
   the log associated with the delete.  Although log-level 6 was used, it
   appeared that some log messages were missing.
   
   11/11/05 15:54:41.185 [Debug] NB 51216 nbemm 111 PID:13393 TID:1196157872
   [No context] 1 [DbConnection::Execute] SQL - retval=2007085(2007085)  
   retdal=-1native=<-143> sqlerror=<[Sybase][ODBC Driver][Adaptive Server
   Anywhere]Column 'FQMachineName' not found> sqlstate=<42S22>  
--------------------------------------------------------------------------------
Etrack Incident = ET507645

Description:  
   In certain cases, when NetBackup Access Control is enabled, long-lived
   processes such as nbemm, nbpem, nbjm, nbrb, nbproxy, nbsl and vmd would
   leak memory.  
--------------------------------------------------------------------------------
Etrack Incident = ET500006

Description:  
   The Policy Execution Manager VxUL message catalog was missing some messages
   causing it to crash when trying to log the new messages.    
--------------------------------------------------------------------------------
Etrack Incident = ET500061

Description:  
   SQL SERVER backup completes normally but the client interface Displayed  
   a -1 status.  This was caused by improper progress log updates.    
--------------------------------------------------------------------------------
Etrack Incident = ET509509

Description:  
   When spanning media, jobs occasionally appeared to be hung and the request
   was continually failing with the message, "ROBOTIC LIBRARY IS DOWN ON  
   SERVER".  This would happen after an earlier failure causing the message,
   "MEDIA SERVER IS CURRENTLY NOT CONNECTED TO MASTER SERVER".  However, the
   media server properly showed the robot as up and the host as ACTIVE or
   ACTIVE-TAPE.  
--------------------------------------------------------------------------------
Etrack Incident = ET509293

Description:  
   The NetBackup Service Layer (NBSL) occasionally sent negative values for
   freespace and totalcapacity of a storage unit (if the values are greater
   than 2^32-1).  
--------------------------------------------------------------------------------
Etrack Incident = ET508191

Description:  
   vmd now retries the connection to EMM forever, instead of shutting down
   if it cannot connect to EMM.  
--------------------------------------------------------------------------------
Etrack Incident = ET511728

Description:  
   From the NOM user interface, it is not possible to start the service/deamon
   when NetBackup is on a UNIX Operating System.  
--------------------------------------------------------------------------------
Etrack Incident = ET512560

Description:  
   It is now be possible for SAN media servers to be used as write hosts for  
   duplicate jobs.  
--------------------------------------------------------------------------------
Etrack Incident = ET510335

Description:  
   VxUL queries were failing on AIX platforms.  
--------------------------------------------------------------------------------
Etrack Incident = ET510255

Description:  
   Appending parentheses in the NOM filtering criteria is no longer an issue.  
--------------------------------------------------------------------------------
Etrack Incident = ET510415

Description:  
   New DRIVE and ROBOT Reports have now been created along with multiple
   entries for some column names.  
--------------------------------------------------------------------------------
Etrack Incident = ET512866

Description:  
   Removed change events for Error LogMonitoring. For example, error log
   collection functionality is removed.  In addition, the getLogMessages()
   idle method supports the error log source too; thus, NOM will call this
   method for getting error logs.  Finally, the getEventChannel()
   functionality has been removed, resulting in an AFException.
     

Additional Notes:  
   Because of this fix, log monitoring of NOM 6.0 MP1 will only work with
   NetBackup 6.0 MP1.  
--------------------------------------------------------------------------------
Etrack Incident = ET513093

Description:  
   vmscd no longer dumps core. This occurred because vmscd received an invalid
   drive type for one of the drives while polling the drive status and vmscd
   was not handling the invalid drive type properly.  
--------------------------------------------------------------------------------
Etrack Incident = ET513390

Description:  
   The NetBackup Notification Service (NBNos) was running in single-threaded
   mode.  
--------------------------------------------------------------------------------
Etrack Incident = ET516440

Description:  
   nbemm no longer core dumps on a clustered master server.  
--------------------------------------------------------------------------------
Etrack Incident = ET516103

Description:  
   Vault can fail while logging very long strings.  

Workaround:  
   Disable Vault logging.  
--------------------------------------------------------------------------------
Etrack Incident = ET515838

Description:  
   When the parent job (nbgenjob) performed stream discovery and it received
   an exception asking for policy information through nbproxy, it would then  
   perform several retries.  On the first retry attempt the parent job would
   core dump.  
--------------------------------------------------------------------------------
Etrack Incident = ET429245

Description:  
   On HP-UX platforms, scheduled backups with file lists that contain  
   multi-byte characters failed with an error 71 (None of the files in the  
   files list exist).  On the Activity Monitor, the multi-byte characters  
   were unreadable in the file lists within job properties.  

Workaround:  
   To prevent this issue, please apply the following patches:  
   
   - HP-UX 11.00
       Patch Name: PHCO_29903  
       Patch Description: s700_800 11.11 iconv cumulative patch  
   - HP-UX 11.11.  
       Patch Name: PHCO_29924  
       Patch Description: s700_800 11.00 iconv cumulative patch  
--------------------------------------------------------------------------------
Etrack Incident = ET514603

Description:  
   Change made to bpexpdate such that media IDs that are less than six
   characters returned from EMM were not padded with spaces.  This caused
   bpexpdate -deassignempty to mistakenly deassign media that still had
   valid images on them.  

Workaround:  
   To avoid this issue, turn off the automatic start of  
   bpexpdate -deassignempty by performing one of the following items:
   
     - On a UNIX master servers, create the file,
       /usr/openv/netbackup/bin/bpsched.d/CHECK_EXPIRED_MEDIA_INTERVAL,
       and enter a 0 (zero) on the first and only line of the file.
   
     - On a Windows master server, create the file,
       <install_path>.d_EXPIRED_MEDIA_INTERVAL,
       and enter a 0 (zero) on the first and only line of the file.  
--------------------------------------------------------------------------------
Etrack Incident = ET514622

** Description: **
   An NBSL core dump happened while stopping it when it was connected to a
   client (NOM).  The core dump would occur on Solaris and AIX platforms.
   On Windows platforms, it would hang in a 'stopping' state in the Windows  
   Service Manager.  
--------------------------------------------------------------------------------
Etrack Incident = ET515553 ET515559

Description:  
   vmscd, before the fix, was a single process and it used to service  
   requests from the EMM server synchronously. Because of this, the EMM server
   was not receiving the request response in a timely manner. In some cases,
   the EMM server would think that vmscd had exited and which then triggered
   certain operations that were redundant, and in some, cases harmful.  
--------------------------------------------------------------------------------
Etrack Incident = ET511340

Description:  
   Several issues have been fixed that related to back-level SSO  
   interoperability:
   
   - Numerous re-registrations were consuming all of vmd's bandwidth on  
     the EMM server.
   
   - Registration failures due to no scan host setting registration retry
     timer which would block back-level servers from releasing drives.
   
   - Back-level remote scanning of NetBackup 6.0 media servers was failing
     with ENOTSCANHOST and forcing still more re-registrations.  

Workaround:  
   To avoid these issues, do not share drives between NetBackup 6.0 and  
   NetBackup 5.X media servers.  
================================================================================

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

Nothing to report in this release.




Attachments

NB_CLT_60_1_M_281107.tar (342 MBytes)


Legacy ID



281107


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


Terms of use for this information are found in Legal Notices