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

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:

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

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_9.1_CLIENTS1.tar.gz; tar - xvf NetBackup_9.1_CLIENTS1.tar
HP-UX	gunzip -dc NetBackup_9.1_CLIENTS1.tar.gz \| tar -xvf
Linux	tar -xzvf NetBackup_9.1_CLIENTS2.tar.gz
Solaris	tar -xzvf NetBackup_9.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 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 upgrade of the Java GUI and the 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 GUI and JRE packages if you decide not to upgrade them.

See Add or Remove Java GUI and JRE after upgrade.

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 Note: Please be aware the `VRTSnbjre.rpm`, `VRTSnbjava.rpm`, and `VRTSpddea.rpm` files are not supported on the IBM pSeries clients.
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:

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

Note:

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

(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
```
Install the Veritas precheck package.
- AIX: installp - ad VRTSnbpck.image all
- HP-UX: swinstall - s VRTSnbpck.depot \*
- Linux: rpm - U VRTSnbpck.rpm
- Solaris: pkgadd -a .pkg_defaults -d VRTSnbpck.pkg VRTSnbpck
(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
```

Install the files in the order that is shown with the command shown:

Note:

The upgrade of the Java 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 GUI and JRE packages if you decide not to upgrade them.

See Add or Remove Java GUI and JRE after upgrade.

AIX	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 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 VRTSpbx.rpm rpm - U VRTSnbclt.rpm rpm - U VRTSnbjre.rpm rpm - U VRTSnbjava.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.
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 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.

(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
You can remove the old versions of the Java GUI and the JRE if you no longer plan to use them.
- Linux:
  rpm -e VRTSnbjava.rpm
  rpm -e VRTSnbjre.rpm
- Solaris:
  pkgrm VRTSnbjava
  pkgrm VRTSnbjre
- HP-UX
  swremove VRTSnbjava
  swremove VRTSnbjre
- AIX
  installp - u VRTSnbjre
  installp - u VRTSnbjava

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

Upgrade of the UNIX and Linux client binaries with native installers

Feedback

Feedback