Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  3. NetBackup™ Upgrade Guide
  5. Client upgrade
  7. Upgrade of the UNIX and Linux client binaries with native installers
NetBackup™ Upgrade Guide

Upgrade of the UNIX and Linux client binaries with native installers

You can 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 upgraded with the NetBackup install script.

  • For AIX: lslpp, installp

  • For Linux: rpm, yum, etc.

  • For Solaris: pkginfo, pkgadd

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

Caution:

You must remove the NetBackup Nutanix plug-in package before you upgrade NetBackup Red Hat and SUSE Linux with the native installers. Both the Nutanix plug-in and NetBackup install the same libraries to the same location, which results in a failure to upgrade. The upgrade fails with an install of package_name conflicts with file from package package_name error message.

Use the command that is shown to uninstall the plug-in before attempting the NetBackup upgrade.

rpm -e VRTSnbntnxahv*

To 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. (Conditional) If your environment uses a NetBackup Certificate Authority, and the client is already configured for NetBackup Certificate Authority, proceed to 5. Otherwise, populate NBInstallAnswer.conf with the following required information:
    CA_CERTIFICATE_FINGERPRINT=fingerprint

    Example (the fingerprint value is wrapped for readability):

    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.

  3. (Conditional) If your environment uses an external certificate authority, and the client is already configured for external certificate authority, proceed to 5. Otherwise, populate NBInstallAnswer.conf with the following required information:

    • SET ECA_CERT_PATH=path

      Use this field to specify the path and the file name of the external certificate file. This field is required to set up an external certificate from a file.

    • SET ECA_TRUST_STORE_PATH=path

      Use this field to specify the path and the file name of the file representing the trust store location. This field is required to set up an external certificate from a file.

    • SET ECA_PRIVATE_KEY_PATH=path

      Use this field to specify the path and the file name of the file representing the private key. This field is required to set up an external certificate from a file.

    • SET ECA_KEY_PASSPHRASEFILE=path

      Use this field to specify the path and the file name of the file that contains the passphrase to access the keystore. This field is optional and applies only when setting up an external certificate from a file.

    • SET ECA_CRL_CHECK_LEVEL=value

      Use this field to specify the CRL mode. This field is required. Supported values are:

      • USE_CDP: Use the CRL defined in the certificate.

      • USE_PATH: Use the CRL at the path that is specified in ECA_CRL_PATH.

      • DISABLED: Do not use a CRL.

    • SET ECA_CRL_PATH=path

      Use this field to specify the path to the CRL associated with the external CA certificate. This field is required only when ECA_CRL_CHECK_LEVEL is set to USE_PATH. If not applicable, leave this field empty.

  4. (Conditional) If the NetBackup primary server is configured to support network address translation (NAT) clients, populate NBInstallAnswer.conf with the following required information:

    ACCEPT_REVERSE_CONNECTION=TRUE

    More information is available. See About the NetBackup answer file.

  5. Additionally, you can add the optional parameter shown to the NBInstallAnswer.conf file.

    • SERVICES=no

    • MERGE_SERVER_LIST=value

    More information about each option is available.

    See About the NetBackup answer file.

  6. 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_11.2_CLIENTS1.tar.gz; tar - xvf NetBackup_11.2_CLIENTS1.tar

      Linux

      tar -xzvf NetBackup_11.2_CLIENTS2.tar.gz

      Solaris

      tar -xzvf NetBackup_11.2_CLIENTS1.tar.gz

    • Change to the directory for your desired operating system.

      Example:

      AIX

      CLIENTS1/NBClients/anb/Clients/usr/openv/netbackup/client/RS6000/AIX7.1/

      Linux

      For Linux Red Hat:

      CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/Linux/RedHat4.18.0/

      For Linux SuSE:

      Linux - s390x

      For Linux-s390x Red Hat:

      CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/Linux-s390x/IBMzSeriesRedHat4.18.0/

      For Linux-s390x SuSE:

      CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/Linux-s390x/IBMzSeriesSuSE5.3.18

      Linux - ppc64le

      For Linux-ppc64le Red Hat:

      CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/
Linux-ppc64le/IBMpSeriesRedHat4.18.0/

      For Linux-ppc64le SuSE:

      CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/
Linux-ppc64le/IBMpSeriesSuSE5.3.18

      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.

      Note:

      Where supported, the upgrade of the Java BAR GUI and the JRE is optional. If you don't want to upgrade them, don't copy or install the VRTSnbjava and VRTSnbjre packages. Remove the old Java BAR GUI and JRE packages if you decide not to upgrade them.

      See Add or remove Java components after upgrade.

      Note:

      The installation of the NetBackup DirectIO is optional. If you do not want it installed, omit the copy and the install of the VRTSnbdirectio package.

      AIX

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

      Linux

      VRTSnbpck.rpm
VRTSpbx.rpm
VRTSnbclt.rpm
VRTSnbclibs.rpm
VRTSnbjre.rpm
VRTSnbjava.rpm
VRTSnbdirectio.rpm (Red Hat x86 only)
VRTSpddeu.rpm
VRTSpddea.rpm
VRTSnbcfg.rpm

      Note:

      Please be aware the VRTSnbjre.rpm, VRTSnbjava.rpm, and VRTSpddea.rpm files are not supported on the IBM pSeries clients.

      Note:

      The VRTSpddeu.rpm package is optional, and is not supported on IBM pSeries and zSeries clients.

      Note:

      The VRTSnbdirectio.rpm package is optional, and is only supported on the Red Hat x86 platform.

      Solaris

      .pkg_defaults
VRTSnbpck.pkg.gz
VRTSpbx.pkg.gz
VRTSnbclt.pkg.gz
VRTSnbclibs.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:

    Be aware the VRTSnbjre.pkg.gz and VRTSnbjava.pkg.gz files are not supported on Solaris clients.

    Note:

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

    Note:

    Be aware the VRTSnbjre.rpm, VRTSnbjava.rpm, and VRTSpddea.rpm files are not supported on the IBM pSeries clients.

  7. (Conditional) For Solaris 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
VRTSnbclibs.pkg
VRTSnbjre.pkg
VRTSnbjava.pkg
VRTSpddea.pkg
VRTSnbcfg.pkg

    Note:

    The VRTSnbjre.pkg and VRTSnbjava.pkg files are not supported on Solaris clients so they are not included.

  8. Install the Cohesity precheck package.

    • AIX: installp - ad VRTSnbpck.image all

    • Linux: rpm - U VRTSnbpck.rpm

    • Solaris: pkgadd -a .pkg_defaults -d VRTSnbpck.pkg VRTSnbpck

  9. (Conditional) If you are upgrading from pre-NetBackup 8.0, remove the old SYMC* packages. The example shown indicates the commands used to remove the SYMC RPM packages. This process preserves your NetBackup configuration. 
    rpm -e SYMCnbjava
rpm -e SYMCpddea
rpm -e SYMCnbclt
rpm -e SYMCnbjre
  10. Install the files in the order that is shown with the command shown:

    Note:

    The upgrade of the Java BAR GUI and JRE is optional. If you do not want them upgraded, omit the copy and the install of the VRTSnbjava and VRTSnbjre packages.

    It is recommended to remove the old Java BAR GUI and JRE packages if you decide not to upgrade them.

    See Add or remove Java components after upgrade.

    AIX

    installp  - ad VRTSpbx.image all
installp  - ad VRTSnbclt.image all
installp  - ad VRTSnbclibs.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

    Linux

    rpm  - U VRTSpbx.rpm
rpm  - U VRTSnbclt.rpm
rpm  - U VRTSnbclibs.rpm
rpm  - U VRTSnbjre.rpm
rpm  - U VRTSnbjava.rpm
rpm  - U VRTSpddeu.rpm
rpm  - U VRTSnbdirectio.rpm (Red Hat x86 only)
rpm  - U VRTSpddea.rpm
rpm  - U VRTSnbcfg.rpm

    Note:

    Please be aware the VRTSnbjre.rpm, VRTSnbjava.rpm, and VRTSpddea.rpm files are not supported on the IBM pSeries clients.

    Note:

    The VRTSpddeu.rpm package is optional, and is not supported on IBM pSeries and zSeries clients.

    Note:

    The VRTSnbdirectio.rpm package is optional, and is only supported on the Red Hat x86 platform.

    Solaris

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

    pkgadd -a .pkg_defaults -d VRTSpbx.pkg VRTSpbx
pkgadd -a .pkg_defaults -d VRTSnbclt.pkg VRTSnbclt
pkgadd -a .pkg_defaults -d VRTSnbclibs.pkg VRTSnbclibs
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

    • Be aware the VRTSnbjre.pkg.gz and VRTSnbjava.pkg.gz files are not supported on Solaris clients.

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

  11. (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://support.cohesity.com/s/article/article-100039650

    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://support.cohesity.com/s/article/article-000127129

  12. You can remove the old versions of the Java BAR GUI and the JRE if you no longer plan to use them or if they are no longer supported.

    • Linux:

      rpm -e VRTSnbjava.rpm

      rpm -e VRTSnbjre.rpm

    • Solaris:

      pkgrm VRTSnbjava

      pkgrm VRTSnbjre

    • AIX

      installp - u VRTSnbjre

      installp - u VRTSnbjava

  13. You can remove the old versions of the NetBackup DirectIO if you no longer plan to use it or if it is no longer supported.

    rpm -e VRTSnbdirectio.rpm

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 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 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 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 (c) 2025 Cohesity, 
Inc. 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 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.

Feedback

Was this page helpful?
Previous

Upgrading UNIX and Linux clients with the NetBackup upgrade script

Next

NetBackup Deployment Management with VxUpdate

Feedback

Was this page helpful?