Veritas NetBackup™ Upgrade Guide

Last Published:
Product(s): NetBackup (8.1)
  1. Introduction
    1.  
      About the NetBackup 8.1 Upgrade Guide
    2. About changes in NetBackup 8.1
      1.  
        About MSDP changes
      2.  
        About certificate requirements for NetBackup 8.1
      3.  
        NetBackup Bare Metal Restore functionality not supported for restoring NetBackup 8.1 clients
      4.  
        SCCM and Chef deployment tools and documentation now available
    3.  
      Potential required changes for NetApp clusters
    4.  
      About automatic file changes from an upgrade
    5.  
      Errors when Bare Metal Restore information is replicated using Auto Image Replication
    6.  
      Known catalog backup limitation
    7.  
      About Veritas Services and Operations Readiness Tools
    8.  
      Recommended SORT procedures for new installations
    9.  
      Recommended SORT procedures for upgrades
    10.  
      About the NetBackup preinstall checker
  2. Planning for an upgrade
    1.  
      About planning a NetBackup 8.1 upgrade
    2.  
      How to plan for an upgrade to NetBackup 8.1
    3.  
      Creating the user account to support the NetBackup web server
    4.  
      Special guidelines for AIX master servers
    5.  
      MSDP changes in NetBackup 8.1
    6.  
      About security certificates for NetBackup hosts
  3. Master server upgrade
    1.  
      About master server upgrades
    2.  
      Preinstall procedure for upgrading to NetBackup 8.1
    3.  
      Performing local, remote, or clustered server upgrades on Windows systems
    4.  
      Performing silent upgrades on Windows systems
    5.  
      Upgrading UNIX/Linux server software to NetBackup 8.1
    6.  
      Post-install procedure for upgrading to NetBackup 8.1
    7. About mounting the NetBackup software media
      1.  
        Mounting NetBackup software media on UNIX or Linux systems
    8.  
      About NetBackup startup and shutdown scripts
    9.  
      Completing your system update after an upgrade
  4. Media server upgrade
    1.  
      Upgrading NetBackup media servers to NetBackup 8.1
  5. MSDP upgrade for NetBackup
    1.  
      MSDP upgrade considerations for NetBackup 8.1
    2.  
      About MSDP rolling data conversion
    3.  
      About MSDP fingerprinting algorithm changes
  6. Appendix A. Reference
    1.  
      NetBackup master server web server user and group creation
    2.  
      Generate a certificate on the inactive nodes of a clustered master server
    3.  
      About the NetBackup Java Runtime Environment
    4.  
      About the NetBackup answer file
    5.  
      Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.1
    6.  
      About NetBackup software availability
    7.  
      About the NetBackup media kit
    8.  
      About the NetBackup Electronic Software Distribution (ESD) images
    9.  
      Additional post-upgrade steps for NetApp clusters
    10.  
      Using NetApp disk arrays with Replication Director
    11.  
      About compatibility between NetBackup versions
    12.  
      Installation and upgrade requirements for UNIX and Linux
    13.  
      Installation and upgrade requirements for Windows and Windows clusters
    14.  
      Requirements for Windows cluster installations and upgrades
    15.  
      Upgrading clients after servers are upgraded
    16.  
      Install and upgrade of the UNIX and Linux client binaries with native installers
    17.  
      Removing a clustered media server by migrating all data to a new media server
    18.  
      Disabling the connection between your NetBackup OpsCenter server and your NetBackup Master Server
    19.  
      Post upgrade procedures for Amazon cloud storage servers

Install and upgrade of the UNIX and Linux client binaries with native installers

You can now install and upgrade NetBackup UNIX and Linux clients with native installers. You can use either the NetBackup install script or your preferred installer method. This change does not include those clients that use the Debian package. Those clients must be installed or upgraded with the NetBackup install script.

  • For AIX: lslpp, installp

  • For HP-UX: swlist, swinstall

  • For Linux: rpm, yum, etc.

  • For Solaris: pkginfo, pkgadd

A successful installation or upgrade is recorded in the /usr/openv/pack/install.history file.

Converting from Symantec RPM packages to Veritas RPM packages

Because of package name changes, rpm -U does not work to upgrade Linux clients from NetBackup 7.7.2 and earlier to NetBackup 7.7.3 and later. You have two options to correctly upgrade your client and convert to the Veritas RPM packages.

  • Remove the old SYMC* RPM packages with the command shown. This process preserves your NetBackup client configuration.

    rpm -e SYMCnbjava
    rpm -e SYMCpddea
    rpm -e SYMCnbclt
    rpm -e SYMCnbjre

    Then upgrade to the new Veritas RPM packages using the RPM installer of your choice. More information is available.

    See “To install or upgrade the UNIX or Linux client binaries using native installers:”.

  • Alternatively, you can use the NetBackup installer to upgrade the client to the new Veritas RPM packages.

Both of these upgrade options result in the same outcome. Once you have successfully upgraded to the Veritas RPM packages, you can perform future upgrades with rpm -U or the RPM installer of your choice.

To install or upgrade the UNIX or Linux client binaries using native installers:

  1. Please create the NetBackup installation answer file (NBInstallAnswer.conf) in the client /tmp directory. More information about the answer file and its contents is available.

    See About the NetBackup answer file.

  2. Populate NBInstallAnswer.conf with the following information:
    SERVER=master_server_name
    CLIENT_NAME=client_name
    CA_CERTIFICATE_FINGERPRINT=fingerprint

    Example (the fingerprint value is wrapped for readability):

    SERVER=master_01
    CLIENT_NAME=client_101
    CA_CERTIFICATE_FINGERPRINT=01:23:45:67:89:AB:CD:EF:01:23:45:67:
    89:AB:CD:EF:01:23:45:67

    Depending on the security configuration in your NetBackup environment, you may need to add the AUTHORIZATION_TOKEN option to the answer file. Additional information about the AUTHORIZATION_TOKEN option is available.

    See About the NetBackup answer file.

    Additionally, you can add either of the options shown to the NBInstallAnswer.conf file. More information about each option is available.

    See About the NetBackup answer file.

    • CLIENT_NAME=XLOCALHOSTX

    • SERVICES=no

  3. Extract the required client files from the appropriate client package and copy them to the client computer.
    • Download the CLIENTS1 package for UNIX clients to a system with sufficient space.

    • Download the CLIENTS2 package for Linux clients to a system with sufficient space.

    • Extract the contents of the CLIENTS1 or the CLIENTS2 file.

      Example:

      AIX

      gunzip NetBackup_8.1_CLIENTS1.tar.gz; tar - xvf NetBackup_8.1_CLIENTS1.tar

      HP-UX

      gunzip -dc NetBackup_8.1_CLIENTS1.tar.gz | tar -xvf

      Linux

      tar -xzvf NetBackup_8.1_CLIENTS2.tar.gz

      Solaris

      tar -xzvf NetBackup_8.1_CLIENTS1.tar.gz

    • Change to the directory for your desired operating system.

      Example:

      AIX

      CLIENTS1/NBClients/anb/Clients/usr/openv/netbackup/client/RS6000/AIX6/

      HP-UX

      CLIENTS1/NBClients/anb/Clients/usr/openv/netbackup/client/HP-UX-IA64/HP-UX11.31/

      Linux

      For Linux RedHat:

      CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/Linux/RedHat2.6.18/

      For Linux SuSE:

      CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/Linux/SuSE3.0.76

      Linux - s390x

      For Linux-s390x RedHat:

      CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/Linux-s390x/IBMzSeriesRedHat2.6.18/

      For Linux-s390x SuSE:

      CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/Linux-s390x/IBMzSeriesSuSE3.0.76

      Solaris

      For Solaris SPARC:

      CLIENTS1/NBClients/anb/Clients/usr/openv/netbackup/client/Solaris/Solaris10/

      For Solaris x86

      CLIENTS1/NBClients/anb/Clients/usr/openv/netbackup/client/Solaris/Solaris_x86_10_64/

    • Copy the files that are shown to the client computer.

      AIX

      VRTSnbpck.image
      VRTSpbx.image.gz
      VRTSnbclt.image.gz
      VRTSnbjre.image.gz
      VRTSnbjava.image.gz
      VRTSpddea.image.gz
      VRTSnbcfg.image.gz

      HP-UX

      VRTSnbpck.depot
      VRTSpbx.depot.gz
      VRTSnbclt.depot.gz
      VRTSnbjre.depot.gz
      VRTSnbjava.depot.gz
      VRTSpddea.depot.gz
      VRTSnbcfg.depot.gz

      Linux

      VRTSnbpck.rpm
      VRTSpbx.rpm
      VRTSnbclt.rpm
      VRTSnbjre.rpm
      VRTSnbjava.rpm
      VRTSpddea.rpm
      VRTSnbcfg.rpm

      Solaris

      .pkg_defaults
      VRTSnbpck.pkg.gz
      VRTSpbx.pkg.gz
      VRTSnbclt.pkg.gz
      VRTSnbjre.pkg.gz
      VRTSnbjava.pkg.gz
      VRTSpddea.pkg.gz
      VRTSnbcfg.pkg.gz

      Note:

      The Solaris client binaries include a hidden administration file called .pkg_defaults. This administration file contains default installation actions.

    Note:

    The NetBackup Java Console RPM, VRTSnbjava, is optional. You may not want to install the NetBackup Java Console on every client in your environment.

    Note:

    Be aware there is no VRTSpddea.rpm for the z/Architecture client.

  4. (Conditional) For Solaris, HP-UX, and AIX, extract the compressed package files with the command shown:

    gunzip VRTS*.*

    This action extracts all the package files as shown:

    VRTSnbpck.pkg
    VRTSpbx.pkg
    VRTSnbclt.pkg
    VRTSnbjre.pkg
    VRTSnbjava.pkg
    VRTSpddea.pkg
    VRTSnbcfg.pkg
  5. Install the files in the order that is shown with the command shown:

    AIX

    installp  - ad VRTSnbpck.image all
    installp  - ad VRTSpbx.image all
    installp  - ad VRTSnbclt.image all
    installp  - ad VRTSnbjre.image all
    installp  - ad VRTSnbjava.image all
    installp  - ad VRTSpddea.image all
    installp  - ad VRTSnbcfg.image all

    Alternatively use a single command to install all packages:

    installp - ad folder_name all

    HP-UX

    swinstall  - s VRTSnbpck.depot \*
    swinstall  - s VRTSpbx.depot \*
    swinstall  - s VRTSnbclt.depot \*
    swinstall  - s VRTSnbjre.depot \*
    swinstall  - s VRTSnbjava.depot \*
    swinstall  - s VRTSpddea.depot \*
    swinstall  - s VRTSnbcfg.depot \*

    Alternatively use a single command to install all packages:

    swinstall -s ./VRTSnbpck.depot \*;swinstall -s ./VRTSpbx.depot \*;swinstall -s ./VRTSnbclt.depot \*;swinstall -s ./VRTSnbjre.depot \*;swinstall -s ./VRTSnbjava.depot \*;swinstall -s ./VRTSpddea.depot \*;swinstall -s ./VRTSnbcfg.depot \*

    Linux

    rpm  - U VRTSnbpck.rpm
    rpm  - U VRTSpbx.rpm
    rpm  - U VRTSnbclt.rpm
    rpm  - U VRTSnbjre.rpm
    rpm  - U VRTSnbjava.rpm
    rpm  - U VRTSpddea.rpm
    rpm  - U VRTSnbcfg.rpm

    Solaris

    Use the pkgadd -a admin -d device [pkgid] command as shown to install the files:

    pkgadd -a .pkg_defaults -d VRTSnbpck.pkg VRTSnbpck
    pkgadd -a .pkg_defaults -d VRTSpbx.pkg VRTSpbx
    pkgadd -a .pkg_defaults -d VRTSnbclt.pkg VRTSnbclt
    pkgadd -a .pkg_defaults -d VRTSnbjre.pkg VRTSnbjre
    pkgadd -a .pkg_defaults -d VRTSnbjava.pkg VRTSnbjava
    pkgadd -a .pkg_defaults -d VRTSpddea.pkg VRTSpddea
    pkgadd -a .pkg_defaults -d VRTSnbcfg.pkg VRTSnbcfg
    • The -a option defines a specific admin (.pkg_defaults) to use in place of the default administration file. The admin file contains default installation actions.

    • The -d device option specifies the source of the software packages. A device can be the path to a device, a directory, or a spool directory.

    • Use the pkgid parameter to specify a name for the package being installed. This parameter is optional.

  6. (Conditional) If you do not have the answer file in place or you do not populate it correctly, you receive the error message shown:

    WARNING: There is no answer file present and no valid bp.conf. Therefore, security configuration is not complete. Manual steps are required before backups and restores can occur. For more information: https://www.veritas.com/support/en_US/article.000127129

    Change to the /usr/openv/netbackup/bin/private directory and run the nb_init_cfg command to configure the bp.conf file. You can also manually configure bp.conf file. You may have to set up the security and the certificate configuration manually. More information is available.

    https://www.veritas.com/support/en_US/article.000127129

Customers who use the NetBackup installation script for their UNIX and Linux clients only see a single change to the installation behavior. The NetBackup installation script no longer copies the installation package into the /usr/openv/pack/ directory on the client. A successful installation or upgrade is recorded in the /usr/openv/pack/install.history file.

Installation error messages on UNIX and Linux, their causes, and their solutions

Installation attempts that vary from the procedure that is shown may generate error messages. Table: Installation error messages and solutions shows some of the actions and the message that is generated.

Table: Installation error messages and solutions

Install action

Error message

Solution

For AIX

User attempts to install the binaries on top of the same version of the binaries.

# installp -ad VRTSnbpck.image all

package VRTSnbpck.image is already installed

Use the lslpp - L package_name command to determine the name of the installed package. Uninstall this package and then retry the operation.

User attempts to install the binaries in the incorrect order.

# installp -ad VRTSnbcfg.image all

error: Failed dependencies:

VRTSnbclt >= 8.1.0.0 is needed by VRTSnbcfg-version-platform

Refer to the documentation for the correct image package installation order. More information is also available in the error which lists the dependent packages.

See “To install or upgrade the UNIX or Linux client binaries using native installers:”.

User attempts to install an older version of a binary over the top of a newer version of the binary.

# installp - d VRTSnbclt.image all

WARNING:

file /usr/openv/lib/java/nbvmwaretags.jar from install of VRTSnbclt-version-platform conflicts with file from package VRTSnbclt-version-platform

Use the lslpp - L package_name command to determine the name of the installed package. Uninstall this package and then retry the operation.

For HP-UX

User attempts to install the binaries on top of the same version of the binaries.

# swinstall - s ./VRTSnbpck.depot

1 filesets have the selected revision already installed.

Use the swlist command to determine the name of the installed package. Uninstall this package and then retry the operation.

User attempts to install the binaries in the incorrect order.

# swinstall -s ./VRTSnbcfg.depot

ERROR: "hostname:/": The software dependencies for 1 products or filesets cannot be resolved.

Refer to the documentation for the correct depot package installation order. More information is also available in the error which lists the dependent packages.

See “To install or upgrade the UNIX or Linux client binaries using native installers:”.

User attempts to install an older version of a binary over the top of a newer version of the binary.

# swinstall - s ./VRTSnbclt.depot

WARNING: "hostname:/": 1 filesets have a version with a higher revision number already installed.

Use the swlist command to determine the name of the installed package. Uninstall this package and then retry the operation.

For Linux

User attempts to install the binaries on top of the same version of the binaries.

# rpm -U VRTSnbpck.rpm

package VRTSnbpck.rpm-version-platform is already installed

Use the rpm command to determine the name of the installed package. Uninstall this package and then retry the operation.

User attempts to install the binaries in the incorrect order.

# rpm -U VRTSnbcfg.rpm

error: Failed dependencies:

VRTSnbclt >= 8.1.0.0 is needed by VRTSnbcfg-version-platform

Refer to the documentation for the correct RPM installation order. More information is available.

See “To install or upgrade the UNIX or Linux client binaries using native installers:”.

User attempts to install an older version of a binary over the top of a newer version of the binary.

# rpm -U VRTSnbclt.rpm

file /usr/openv/lib/java/nbvmwaretags.jar from install of VRTSnbclt-version-platform conflicts with file from package VRTSnbclt-version-platform

Use the rpm command to determine the name of the installed package. Uninstall this package and then retry the operation.

For Solaris

User attempts to install the binaries on top of the same version of the binaries

pkgadd -a .pkg_defaults -d
VRTSnbpck.pkg VRTSnbpck

Processing package instance
<VRTSnbpck> from
</root/packages/Solaris/
Solaris_x86_10_64/VRTSnbpck.pkg>

NetBackup Pre-Check(i386) 8.1.0.0
This appears to be an attempt to
install the same architecture and
version of a package which is
already installed. This
installation will attempt to
overwrite this package.

Copyright 2017 Veritas
Technologies LLC. All rights
reserved.

## Executing checkinstall script.

Using </> as the package base
directory.

## Processing package information.

## Processing system information.

6 package pathnames are already
properly installed.

## Verifying disk space
requirements.

Installing NetBackup Pre-Check as
<VRTSnbpck>

## Executing preinstall script.

Wednesday, May 10, 2017 03:15:44
PM IST: Installing package
VRTSnbpck.

Installing NB-Pck.

## Installing part 1 of 1.

[ verifying class <NBclass> ]

## Executing postinstall script.

Wednesday, May 10, 2017 03:15:45
PM IST: Install of package
VRTSnbpck was successful.

Use the pkginfo command to determine the name of the package that is currently installed. Uninstall this package and then retry the operation.

Alternatively, use the admin file that is provided with the package to reinstall the package.

User attempts to install the binaries in the incorrect order.

# pkgadd -a .pkg_defaults -d VRTSnbclt.pkg VRTSnbclt

ERROR: VRTSnbpck >=8.1.0.0 is required by VRTSnbclt. checkinstall script suspends

Refer to the documentation for the correct package installation order. More information is available.

See “To install or upgrade the UNIX or Linux client binaries using native installers:”.

User attempts to install an older version of a binary over the top of a newer version of the binary.

# pkgadd -a .pkg_defaults -d VRTSnbclt.pkg VRTSnbclt

Processing package instance <VRTSnbclt> from </root/80packages/Solaris/ Solaris_x86_10_64/VRTSnbclt.pkg>

NetBackup Client(i386) 8.0.0.0

The following instance(s) of the <VRTSnbclt> package are already installed on this machine:

1 VRTSnbclt NetBackup Client

(i386) 8.1.0.0

Do you want to overwrite this installed instance [y,n,?,q]

Use the pkginfo command to determine the name of the package that is currently installed. Uninstall this package and then retry the operation.