Veritas NetBackup™ Upgrade Guide
- Introduction
- Planning for an upgrade
- General upgrade planning information
- About upgrade tools
- Upgrade operational notes and limitations
- Master server upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- Client upgrade
- NetBackup Deployment Management with VxUpdate
- Appendix A. Reference
Silently upgrading NetBackup media server software on UNIX and Linux
You can upgrade 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.
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 media server binaries using native installers:
- 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. - (Conditional) If your environment uses a NetBackup Certificate Authority, and the media server is already configured for NetBackup Certificate Authority, proceed to 4. 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.
- (Conditional) If your environment uses an external certificate authority, and the media server is already configured for external certificate authority, proceed to 4. Otherwise, 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.
- Additionally, you can add the optional parameters shown to the
NBInstallAnswer.conf
file.Additional LICENSE entries
Additional SERVER entries
More information about each option is available.
- 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_8.3_LinuxR_x86_64.tar.gz
For Linux SuSE:
tar -xzvf NetBackup_8.3_LinuxS_x86_64.tar.gz
For Solaris SPARC:
tar -xzvf NetBackup_8.3_Solaris_Sparc64.tar.gz
For Solaris x86:
tar -xzvf NetBackup_8.3_Solaris_x86.tar.gz
- Change to the directory for your desired operating system and copy server files to the media server.
Operating system directory:
For Linux RedHat:
NetBackup_8.3_LinuxR_x86_64/linuxR_x86/anb
For Linux SuSE:
NetBackup_8.3_LinuxS_x86_64/linuxS_x86/anb
For Solaris SPARC:
NetBackup_8.3_Solaris_Sparc64/solaris/anb
For Solaris x86
NetBackup_8.3_Solaris_x86/solaris_x86/anb
Copy server files to the computer to be installed
Linux:
VRTSnetbp.rpm
andVRTSpddes.rpm
Linux RedHat:
VRTSpddei.rpm
Solaris:
VRTSnetbp.pkg
andVRTSpddes.pkg
- 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 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
andVRTSnbjre
packages.Veritas recommends the removal of the old Java GUI and JRE packages if you decide not to upgrade them.
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.
- (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
- Install the Veritas precheck package.
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 rpm -e SYMCpddes rpm -e SYMCnetbp
- Install the files in the order that is shown with the commands shown:
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
andVRTSnbjre
packages.Veritas recommends the removal of the old Java GUI and JRE packages if you decide not to upgrade them.
Linux
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 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.
- 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