============
DEPENDENCIES
============

    -- NB_CLT_7.1.0.2 (this Maintenance Release) can be installed on a
       standalone NetBackup client using a remote installation procedure or a
       local installation procedure.
    
    -- Only on a NetBackup server, NB_7.1.0.2_<6 digit number>.<server>.tar
       must be installed after this Maintenance Release is installed.

    -- Installation of this Maintenance Release requires version 1.42.24.7
       of the NB_update.install script.

============================
I. INSTALLATION INSTRUCTIONS
============================

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

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

To install this Maintenance Release in a UNIX Cluster Environment:
1) Before you install this Maintenance Release, make sure that NetBackup is at
   release level 7.1 and configured to run in a cluster.

2) Offline the cluster by following the procedures outlined in the
    "NetBackup High Availability Guide."

3) Freeze the cluster by following the procedures outlined in the
    "NetBackup High Availability Guide."

4) Install this Maintenance Release on the inactive node(s) of the cluster
   first. (Perform the steps in the, "To install this Maintenance Release as
   root on the NetBackup Server" procedure).

5) Install this Maintenance Release on the active node of the cluster.
   (Again, perform the steps in the, "To install this Maintenance Release as
   root on the NetBackup Server" procedure).

6) Unfreeze the cluster by following the procedure outlined in the "NetBackup
   High Availability Guide."

7) Online the cluster by following the procedures outlined in the
    "NetBackup High Availability Guide."

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

   NOTE: A directory "NB_CLT_7.1.0.2" is created in the cluster shared
         directory. This directory contains files that are needed during an
         uninstall.  Do not remove it.

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

There are two ways to install the client Maintenance Release software.

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

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

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

To install this Maintenance Release remotely as root on the NetBackup Master or
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 installed, such as Oracle, ensure that the database
     services are stopped.

2) Install NB_7.1.0.2 and NB_CLT_7.1.0.2 Maintenance Release binaries.

        cd /tmp
        /bin/sh NB_update.install

   NOTE: Selecting the client Maintenance Release on a Master/Media server
   automatically installs the server Maintenance Release if the server (NB)
   .gz file and README exist in the installation directory. The client install
   fails if the (NB) .gz file and README are not present and the server release
   has not been previously installed. The server Maintenance Release is NOT
   installed automatically during a reinstall of the client Maintenance Release. 

   NOTE: The installation of the client Maintenance Release on a server copies
   the appropriate client binaries into place on the server.  Additionally,
   any other client binaries on the server are updated so that they can then
   be pushed out using update_clients.  If other client binaries are installed
   after applying this Maintenance Release, this Maintenance Release needs to
   re-run to patch those other client binaries.

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

3) The NB_update.install script prompts you to restart the daemons.  Otherwise,
   after the Maintenance Release installation has completed, run:

        /usr/openv/netbackup/bin/bp.start_all

   You can find the Maintenance Release install logs in
   /usr/openv/pack/pack.history after the installation is complete.

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

 HP-UX-IA64/HP-UX11.31
 HP9000-800/HP-UX11.11
 INTEL/FreeBSD6.0
 Linux-IA64/RedHat2.6
 Linux-IA64/SuSE2.6
 Linux/IBMpSeriesRedHat2.6
 Linux/IBMpSeriesSuSE2.6
 Linux/IBMzSeriesRedHat2.6
 Linux/IBMzSeriesSuSE2.6
 Linux/RedHat2.6
 Linux/SuSE2.6.16
 MACINTOSH/MacOSX10.5
 RS6000/AIX53
 Solaris/Solaris10
 Solaris/Solaris9
 Solaris/Solaris_x86_10_64

       Note: The /usr/openv/netbackup/bin/update_clients command without
             any parameters updates all the UNIX clients.

   If the client (CLT) .gz file and README exist in the installation directory
   during the installation of the server Maintenance Release, the
   NB_update.install script installs the client Maintenance Release
   automatically. The client Maintenance Release is NOT installed
   automatically during a reinstall of the server Maintenance Release. 

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

To perform a Local client install this Maintenance Release:

NOTE: The install script determines if a local client install is appropriate
      and chooses 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 installed, such as Oracle, ensure that the
     database services are stopped.

2) Install NB_CLT_7.1.0.2 Maintenance Release binaries.

       cd /tmp
       /bin/sh NB_update.install

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

==========================
II. UNINSTALL INSTRUCTIONS
==========================
Note: This will ONLY uninstall the Maintenance Release from your machine if the
      client Maintenance Release 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.
   
--------------------------------------------------------------------------------
To uninstall this Maintenance Release in a UNIX Cluster Environment:

1) Freeze the cluster to prevent failover during the uninstall.

2) Uninstall this Maintenance Release on the inactive node(s) of the cluster
   first.

3) Uninstall this Maintenance Release on the active node of the cluster.

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

5) Be sure to uninstall both client and server updates on each node before
   proceeding to the next step.

6) Unfreeze the cluster.
--------------------------------------------------------------------------------

As root on the NetBackup Master/Media Server in which the Maintenance Release
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 installed, such as Oracle, ensure that the
          database services are stopped.

    2)Change directory to the Maintenance Release save directory. 
        Substitute the Maintenance Release name for ${PACK.EN_US} in the following
        command:

           cd /usr/openv/pack/${PACK.EN_US}/save

    3)Run the un-install script:

          ./NB_update.uninstall

    4)Verify that the Maintenance Release uninstalled successfully by
        checking:

        /usr/openv/pack/pack.history.

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

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

        /usr/openv/netbackup/bin/bp.start_all