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. Veritas NetBackup™ Installation Guide
  5. Installing server software on UNIX systems
  7. Installing NetBackup media server software on UNIX
  9. Silently installing NetBackup media server software on UNIX and Linux
Veritas NetBackup™ Installation Guide

Silently installing NetBackup media server software on UNIX and Linux

You can install NetBackup UNIX and Linux media servers with native installers. You can use either the NetBackup install script or your preferred installer method.

  • For Linux: rpm, yum, etc.

  • For Solaris: pkginfo, pkgadd

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

To install the UNIX or Linux media server binaries using native installers:

  1. Please create the NetBackup installation answer file (NBInstallAnswer.conf) in the media server /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 required information:
    SERVER=master_server_name
CLIENT_NAME=media_server_name
MACHINE_ROLE=MEDIA
LICENSE=license_key

    Be aware you can use CLIENT_NAME=XLOCALHOSTX instead of stating the media server name explicitly.

  3. (Conditional) If your environment uses a NetBackup Certificate Authority, 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.

  4. (Conditional) If your environment uses an external certificate authority, populate NBInstallAnswer.conf with the following required information:

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

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

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

    • ECA_KEY_PASSPHRASEFILE

      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.

    • ECA_CRL_CHECK_LEVEL

      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.

      • SKIP: Used to skip setting up the certificate authority. To skip the ECA configuration, you must set all required ECA_ values to SKIP. Be aware that if you continue with the installation without a certificate authority, the backups and restores fail.

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

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

    • INSTALL_PATH

    • Additional LICENSE entries

    • Additional SERVER entries

    More information about each option is available.

    See About the NetBackup answer file.

  6. Download the server package that matches your server platform to a system with sufficient space. Then extract the required server package.

    Extract the contents of the server package file. Example:

    • For Linux RedHat:

      tar -xzvf NetBackup_9.0_LinuxR_x86_64.tar.gz

    • For Linux SuSE:

      tar -xzvf NetBackup_9.0_LinuxS_x86_64.tar.gz

    • For Solaris SPARC:

      tar -xzvf NetBackup_9.0_Solaris_Sparc64.tar.gz

    • For Solaris x86:

      tar -xzvf NetBackup_9.0_Solaris_x86.tar.gz

  7. Change to the directory for your desired operating system and copy server files to the media server.

    Operating system directory:

    • For Linux RedHat:

      NetBackup_9.0_LinuxR_x86_64/linuxR_x86/anb

    • For Linux SuSE:

      NetBackup_9.0_LinuxS_x86_64/linuxS_x86/anb

    • For Solaris SPARC:

      NetBackup_9.0_Solaris_Sparc64/solaris/anb

    • For Solaris x86

      NetBackup_9.0_Solaris_x86/solaris_x86/anb

    Copy server files to the computer to be installed

    • Linux: VRTSnetbp.rpm and VRTSpddes.rpm

    • Linux RedHat: VRTSpddei.rpm

    • Solaris: VRTSnetbp.pkg and VRTSpddes.pkg

  8. Extract the client binaries and copy them to the media server:

    Extract the client binaries:

    tar -xzvf client_dist.tar.gz

    Change directory to your desired operating system:

    • RedHat: openv/netbackup/client/Linux/RedHat2.6.32

    • SuSE: openv/netbackup/client/Linux/SuSE3.0.76

    • SPARC: openv/netbackup/client/Solaris/Solaris10

    • Solaris_x86: openv/netbackup/client/Solaris/Solaris_x86

    Copy the files that are shown to the media server.

    Note:

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

    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.

  9. (Conditional) For Solaris, 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
  10. Install the files in the order that is shown with the commands shown:

    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 VRTSpddes.rpm
rpm  - U VRTSpddei.rpm
rpm  - U VRTSnbcfg.rpm
rpm  - U VRTSnetbp.rpm

    Note that VRTSpddei.rpm is for Linux RedHat only.

    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 VRTSpddes.pkg VRTSpddes
pkgadd -a .pkg_defaults -d VRTSnbcfg.pkg VRTSnbcfg
pkgadd -a .pkg_defaults -d VVRTSnetbp.pkg VRTSnetbp

    • 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. If you decide to install the Java GUI or the JRE after the installation completes, additional information is available.

    See Add or Remove Java GUI and JRE after install.

Feedback

Was this page helpful?
Previous

Installing NetBackup media server software on UNIX

Next

About pushing client software from a master server to clients

Feedback

Was this page helpful?