To install 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, 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, 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

   • INSTALL_PATH=path

   • 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_10.4_CLIENTS1.tar.gz; tar - xvf NetBackup_10.4_CLIENTS1.tar
     Linux	tar -xzvf NetBackup_10.4_CLIENTS2.tar.gz
     Solaris	tar -xzvf NetBackup_10.4_CLIENTS1.tar.gz

   • Change to the directory for your desired operating system.

     Example:

     AIX	CLIENTS1/NBClients/anb/Clients/usr/openv/netbackup/client/RS6000/AIX7/
     Linux	For Linux Red Hat: 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 Red Hat: 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
     Linux - ppc64le	For Linux-ppc64le Red Hat: CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/ Linux-ppc64le/IBMpSeriesRedHat3.10.0/ For Linux-ppc64le SuSE: CLIENTS2/NBClients/anb/Clients/usr/openv/netbackup/client/ Linux-ppc64le/IBMpSeriesSuSE4.4.21
     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:

     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.

     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 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.
     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 files in the order that is shown with the command shown:

   Note:

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

   AIX	installp - ad VRTSnbpck.image all 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 VRTSnbpck.rpm 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 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.
   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 VRTSnbclibs.pkg VRTSnbclibs 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.

9. (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-100039650