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

Problem

Maintenance Pack NB_CLT_60_7_M.tar provides fixes for the 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_7_M README                           September 15, 2008
Corequirement: NB_60_7_M NB_BBS_60_7_M NB_BMR_60_7_M NB_JAV_60_7_M

================================================================================
This Maintenance Pack provides fixes for the Veritas NetBackup (tm) UNIX
clients.  NetBackup UNIX Add-on products, Database Agents and the Java user
interface have separate Maintenance Packs.  

This Maintenance Pack may require as much as 400MB in free space in the /usr
partition to install. This Maintenance Pack contains a full replacement of all
client binaries for all platforms.  If applying this Maintenance pack locally,
up to 50MB of free space is required in /usr partition, depending on platform.
If applying this pack to a server that has had other client platform types
loaded (for example, push install of client binaries) more space is required,
up to 400MB. For more information, please refer to the following TechNote:

  http://seer.support.veritas.com/docs/280824.htm
================================================================================


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

   -- On a server, NB_CLT_60_7_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_7_M_<6 digit number>.<server>.tar
      must be installed after this Maintenance Pack is installed.

   -- Only if Bare Metal Restore Boot Server is installed,
      NB_BBS_60_7_M_<6 digit number>.<platform>.tar must be installed after this
      Maintenance Pack is installed.

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

   -- Deliverables for the agents or options such as DB2, Oracle, Veritas
      Storage Migrator (tm) (VSM) do not always change between patches and could
      result in a patch not being delivered.  When upgrading or patching client
      software, any agent software must be upgraded or patched to the latest or
      matching level at the same time as the client software.

    -- Added support for multiple ACSLS servers to Windows.  This requires
       all Windows ACS customers upgrade to SUN/STK Libattach version 1.4.1.

 

I.    NEW FEATURES AND PLATFORM PROLIFERATIONS
II.   KNOWN ISSUES
III.  DOWNLOAD INSTRUCTIONS
IV.   INSTALLATION INSTRUCTIONS
V.    UNINSTALL INSTRUCTIONS
VI.   CURRENT MAINTENANCE PACK INDEX  
VII.  MAINTENANCE PACK CONTENT
VII.  MAINTENANCE PACK CONTENT
        Conventions
        Current Maintenance Pack
          NB_CLT_60_7_M
        Maintenance Pack History
          NB_CLT_60_6_M
          NB_CLT_60_5_M
          NB_CLT_60_4_M
          NB_CLT_60_3_M
          NB_CLT_60_2_M
          NB_CLT_60_1_M


============================================
I.  NEW FEATURES AND PLATFORM PROLIFERATIONS
============================================
Many new features, enhancements, and platform proliferations have been made
to NetBackup 6.0 MP7  in general.  For a complete list of these additions, refer
to the New Features and Platform Proliferations section in the NB_CLT_60_7_M
online Readme that you installed prior to installing this package.

Platform Proliferations:
------------------------
This maintenance pack supports the following new platform proliferations.
Symantec recommends that you refer to the NetBackup 6.0 Operating System
Compatibility Matrix for the latest information regarding supported platforms:
   http://entsupport.symantec.com/menu_ddProduct_NBUESVR_view_CL.htm

The following Operating System proliferations have been added with this release.

+   Added AIX 6.1 Client support.

+   Added support for OpenAFS 1.4.1 Client however, this release will not
   support AES 128 Encryption.

The following database agent proliferations have been added in this release.

+   DB2 9.1 - AIX 6.1

+   Informix 11.1 - AIX 6.1, HP-UX PA-RISC 11.31, HP-UX IA64 11.31

+   Oracle 11G - AIX 6.1

+   Sybase 15 - AIX 6.1, HP-UX PA-RISC 11.31, HP-UX IA64 11.31

 

New Features and Enhancements:
------------------------------
New Features and Enhancements:
------------------------------
This maintenance pack primarily focuses on fixes to known issues that
include customer-specific issues that have been documented in the form of
a Titan Case.  This release does not contain any major new enhancements.

 


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

This section contains known issues with this maintenance pack that have not
yet been fixed in NetBackup.  These issues will likely be fixed in future
Maintenance Packs for this version of NetBackup.

+  (ET1185725) When running on an AIX 5.3 system, Symantec recommends that you
  install the patch APAR IY92889 if you are installing NetBackup on a system
  using the xlC.aix50.rte C++ runtime version 8.0.0.0 or later.  You can find
  this patch on the www.ibm.com Web site by entering, IY92889 in the search
  field.

+  (ET1182594) You may encounter a core dump of dbeng9 after performing a Full
  Catalog Backup Recovery. This is not a Symantec NetBackup issue; thus, you can
  delete or ignore the core dump. Testing showed that the catalog recovery
  completed successfully and that bprecover handled the core dump issue
  appropriately.

+  (ET1208336) When using NBAC on a Linux system running a kernel at or
   above 2.6.9-*, it is possible that backups may fail after 1000 jobs have
   completed. To avoid this issue, you will need to update your VxAT version
   to 4.2.2.40 or greater.

+  (ET1212445) NetBackup will not import tapes in an ACSLS library when the
  barcode label is different than the media ID or recorded volume serial
  number (RVSN). A mismatch occurs when the barcode and media ID do not
  match in the volume database.

  A mismatch can occur for multiple reasons. Two examples include:
  1. When using tapes previously written by a different barcode, labels
     are placed into an ACSLS library using a new barcode label.
  2. The administrator attempts to change the media ID field (using
     vmchange) to match the RVSN. In this example when the inventory is
     updated, the barcode and media ID will be synchronized.

  To be able to restore from these tapes, the media ID used when mounting
  the tapes using the automatic cartridge system daemon (ACSD) needs to
  match the recorded media ID as found in the header on the tape (RVSN).

  The recommended approach is to use a barcode label that matches the
  recorded media ID.  Tapes can then be mounted in a drive with AVRD
  running so that the recorded media ID is displayed. Then, a barcode
  with that label needs to be placed on the tape. For more information
  on how to resolve this issue, refer to the following TechNote on the
  Symantec Support Web site.

     http://entsupport.symantec.com/docs/279257

+  (ET1189468) At the next major release of NetBackup, the NetBackup
  Administrator's Guide for UNIX will be updated to clarify how to set and
  use the Busy File Settings host properties.  The NetBackup 6.0
  Administrator's Guide instructs the user to copy bpend_notify_busy script
  to the /usr/openv/netbackup/bin/bpend_notify location.  However the guide
  does not specify that the bpend_notify_busy script resides on the master
  server and needs to be copied to the client machine.  Thus, the each
  client system will have a goodies directory, but it will not contain the
  bpend_notify_busy file.

+  The Veritas Private Branch Exchange (PBX) software is installed along with
  Veritas NetBackup 6.0.  Depending on how NetBackup is installed, PBX may log
  messages by default to the UNIX system logs  /var/adm/messages or
  /var/adm/syslog, or to the Windows Event Log.  This can cause additional
  system logging that the system administrator may not desire.  The messages
  written to the system logs are the same as those written to the PBX logs
  (/opt/VRTSpbx/log on UNIX and <install_path>\VxPBX\log on Windows).

  To disable PBX logging to the system or event logs after NetBackup has been
  installed, enter the following commands:

  UNIX:
       cd /opt/VRTSicsco/bin
       ./vxlogcfg -a -p 50936 -o 103 -s LogToOslog=false

  Windows:
       cd <install_path>\VERITAS\VRTSicsco
       vxlogcfg –a –p 50936 –o 103 –s LogToOslog=false

  It should not be necessary to restart PBX for this setting to take effect.
  Any future PBX log information should no longer appear in the system logs.

  For more information about this issue or information on how to disable the
  option, refer to the following TechNote on the Symantec Support Web site.

  http://entsupport.symantec.com/docs/280746


+  On all platforms, if the server pack install fails for any reason after the
  Client pack has completed, be sure not to restart the daemons before you
  attempt to install the pack again.

+  Reminder: Synthetics is not supported on Tru64 platforms.

+  The NetBackup 6.0 Commands document contains some incorrect information for
  the bplist command.  The following accurately explains this command.  

   The bplist command shows a list of previously archived or backed up files
   according to the options that you specify. You can choose the file or
   directory and the time period that you want the listing to cover.
   Directories can be recursively displayed to a specified depth.

   The bplist command shows only the files that you have read access to.  It
   lists the files only if a user backup is performed by the user owning the
   files (that is, an administrator account). A non-administrator or backup
   operator cannot bplist the files. You also must own or have read access to
   all directories in the file paths. You can list files that were backed up
   or archived by another client only if you are validated to do so by the
   NetBackup administrator.

   If you create the following directory /usr/openv/netbackup/logs/bplist/
   with public-write access, bplist creates an debug log file in this
   directory that you can use for troubleshooting. The output of bplist goes
   to standard output.

+  The NetBackup 6.0 Commands document contains incorrect information for
  the vxlogcfg -r command.  The following is the revised description for this
  command.  

  -r, --remove

  Unregisters and removes the log configuration settings for the specified
  OID and product from the product logging configuration file. Individual
  settings can be removed with the “–s, --setting keyname=value“ option.

  Caution: Always use the -r option with the –o option. Otherwise, all of the
           existing NetBackup log settings are removed and no further logging
           is performed for all of NetBackup.

 


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

  where <6 digit number> is an internal tracking identifier

    NOTE: NB_CLT_60_7_M_<6 digit number>.tar contains all client binaries.
 
    NOTE: Only if Bare Metal Boot Server is installed, download
          and extract NB_BBS_60_7_M_<6 digit number>.<platform>.tar
          into the /tmp directory.


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

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

 


=============================
IV. 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.

Before installing this maintenance pack, please review the following items:
 - Symantec recommends that you perform catalog backups before and after you
   apply this maintenance pack.

 - If you are planning to install this Maintenance Pack as a part of an
   upgrade from a 5.x release then it is important that you understand that the
   existing NetBackup databases must be in a consistent state prior to beginning
   the upgrade. Information and tools to assist you in determining the current
   state of your database, as well as instructions to help you address any
   inconsistencies that you might discover can be viewed on the NetBackup Upgrade
   Portal, a part of the Symantec NetBackup Support Web site.

     http://www.symantec.com/business/support/overview.jsp?pid=15143

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

 - If upgrading a NetBackup client on which this Maintenance Pack has been
   installed to a NetBackup server, you must first uninstall this Maintenance
   Pack, perform the upgrade from client to server,then re-apply this
   Maintenance Pack to the new server.


For Maintenance Pack installation on a UNIX Cluster Environment:
--------------------------------------------------------------------------------
1) Before you install this Maintenance Pack, make sure that NetBackup is at
  release level 6.0 and configured to run in a cluster.

2) Freeze the NetBackup group. (By freezing the group, you will prevent a
  'failover' from occurring during a patch installation).

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

  IMPORTANT: If you are using HP Service Guard and upgrading from a
  pre-NetBackup 6.0 MP4 version, you must complete the installation of
  this pack to the inactive node(s), and then copy the following file from
  an inactive node to the active node before beginning the pack install on
  the active node:

  /usr/openv/netbackup/bin/cluster/util/monitor

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

5) If the cluster is in a faulted state, clear the fault.

6) 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:

NOTE:  This pack contains NetBackup Client binaries for Linux, Red Hat 4,
and SuSE 9, on Power PC from IBM.  To install these binaries on a NetBackup
Server (for pushing to clients), you must first create the following
directories:
      mkdir /usr/openv/netbackup/client/Linux/IBMpSeriesRedHat2.6
      mkdir /usr/openv/netbackup/client/Linux/IBMpSeriesSuSE2.6


As root on the NetBackup Master/Media Server:

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) Install NB_60_7_M and NB_CLT_60_7_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.  Therefore, Symantec recommends that you also apply
  the NB JAV Maintenance Pack before running 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.


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

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

5) 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/IBMpSeriesRedHat2.6
   Linux/IBMpSeriesSuSE2.6
   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) 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) Install NB_CLT_60_7_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.

 


=========================
V. 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.EN_US} in the following command:

          cd /usr/openv/pack/${PACK.EN_US}/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

 


==================================
VI. CURRENT MAINTENANCE PACK INDEX
==================================

This section contains a master index for all UNIX packages of Etracks that
have been fixed in this release, sorted according to the containers that
they comprise.


NB_60_7_M
---------
1128726 1145685 1146635 1150657 1172971 1178481 1194284 1175361 1196200 1160439
1191148 1193696 1197056 1201124 1186553 1201289 1200945 1193183 1186256 1202780
1181024 1046203 1188094 1193241 1200911 1196151 1204133 1194711 1203203 1203315
1204149 1203341 1196108 1206982 1149072 1203743 1206988 1209668 1141942 1210324
1181990 1205097 1157872 1028523 1193739 1202703 1139683 1213186 1210997 1213398
1194467 1198779 1163522 1194630 1186713 1159797 1215592 1215486 1213931 1146675
1213936 1217081 1019035 1003076 1199328 1173094 1211957 1209824 1210121 1219899
1206849 1204494 852979 1168028 1190482 1223027 1223019 1229928 1159536 1200897
1224637 1214052 1201393 1152608 1042411 1211653 1137917 1135737 1227823 814704
1175373 1236186 1237077 1237818 918372 1200166 1216170 1039111 1238630 1229969
1238098 1239178 1236032 1242512 1245566 1244766 1245997 1244622 1221477 1036931
1200190 1089296 1251778 1252326 1219002 1252345 1268942 1184332 1223173 1212526
1259059 1195231 1260503 1259252 1262091 1150199 1240367 1261507 1261430 1269061
1273387 1275369 1269918 1228938 1261282 1097416 1275549 1281153 1270235 1253532
1283873 1283865 1277786 1077528 1189875 1190428 1291060 1260324 1287242 1292773
1294647 1291761 1295792 1302098 1251842 1316727 1316894 1321914 1178607

NB_ADC_60_7_M
-------------
1179426 1220903 1227575 1239595 1235529 1231895 1219116 1134888 1211678 1275147
1227541 1210195 1361434

NB_BBS_60_7_M
-------------
1194900 1198426 1201794 1240183

NB_BMR_60_7_M
-------------
1201741 1212630 1213219 1219751 1222733 1231109 1228989 1212202 1175891 1195956


NB_CLT_60_7_M
-------------
1128726 1145685 1146635 1150657 1172971 1178481 1194284 1175361 1196200 1160439
1191148 1193696 1197056 1201124 1186553 1201289 1200945 1193183 1186256 1202780
1181024 1046203 1188094 1193241 1200911 1196151 1204133 1194711 1203203 1203315
1204149 1203341 1196108 1206982 1149072 1203743 1206988 1209668 1141942 1210324
1181990 1205097 1157872 1028523 1193739 1202703 1139683 1213186 1210997 1213398
1194467 1198779 1163522 1194630 1186713 1159797 1215592 1215486 1213931 1146675
1213936 1217081 1019035 1003076 1199328 1173094 1211957 1209824 1210121 1219899
1206849 1204494 852979 1168028 1190482 1223027 1223019 1229928 1159536 1200897
1224637 1214052 1201393 1152608 1042411 1211653 1137917 1135737 1227823 814704
1175373 1236186 1237077 1237818 918372 1204203 1200166 1216170 1039111 1238630
1229969 1238098 1239178 1236032 1242512 1245566 1244766 1245997 1244622 1221477
1036931 1200190 1089296 1251778 1252326 1219002 1252345 1268942 1184332 1223173
1212526 1259059 1195231 1260503 1259252 1262091 1150199 1240367 1261507 1261430
1269061 1273387 1250877 1275369 1269918 1228938 1261282 1097416 1275549 1281153
1271278 1270235 1253532 1283873 1283865 1277786 1077528 1189875 1190428 1291060
1260324 1287242 1292773 1294647 1291761 1296282 1295792 1302098 1251842 1316727
1316894 1321914 1178607

NB_DB2_60_7_M
-------------
1294774

NB_DMP_60_7_M
-------------
1152587 1213695 1222258 1214070 1235538 1233401 1249754 1257297

NB_ENC_60_7_M
-------------
1238098

NB_INX_60_7_M
-------------
1145850

NB_JAV_60_7_M
-------------
1188650 1194367 1135270 1187772 1205636 384091 1278056 1255609 1301700

NB_LOT_60_7_M
-------------
1314264

NB_NOM_60_7_M
-------------
1226692 1233746 1195149 1238422 1204000 1122893 1036931 1283800 1291729

NB_ORA_60_7_M
-------------
1226883 1224664 1294774

NB_SAP_60_7_M
-------------
1209710 1142467 1210594

NB_SMU_60_7_M
-------------
1280906

NB_VLT_60_7_M
-------------
1238369 1166277 1283692 1297162 1385494

=============================
VII. MAINTENANCE PACK CONTENT
=============================
This section has been moved to the attached text file.

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)