NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.3 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.3
- License file required for upgrade
- Windows primary server upgrades are slowed if a large number of files are in the installation directory
- About NetBackup database changes
- Windows compiler and security requirements for NetBackup 9.1 and later installation and upgrade
- Java GUI and JRE installation optional for some computers
- Logging directory permissions require reset on rollback
- Upgrades from NetBackup 7.6.0.4 and earlier are not supported
- External certificate authority certificates supported in NetBackup 8.2 and later
- About Veritas Usage Insights
- Best practices for Veritas Usage Insights
- Planning for an upgrade
- General upgrade planning information
- About planning a NetBackup 10.3 upgrade
- How to plan for an upgrade to NetBackup 10.3
- Legacy logging directory security update
- Unified logging security update
- Notifications, Messages, and Resiliency configuration information are not upgraded
- Known catalog backup limitation
- About security certificates for NetBackup hosts
- About automatic file changes from an upgrade
- Reduce the job database size before upgrade
- Known SUSE Linux primary server upgrade issue
- Performance and tuning considerations
- About upgrade tools
- Upgrade operational notes and limitations
- Creating the user account to support the NetBackup web server
- About NetBackup 10.3 support for Fibre Transport Media Server with RHEL 7.5 and later
- MSDP changes in NetBackup 8.1
- Potential required changes for NetApp clusters
- Errors when Bare Metal Restore information is replicated using Auto Image Replication
- Upgrade issue with pre-8.1 clients and 8.1 or later media servers
- General upgrade planning information
- Primary server upgrade
- About primary server upgrades
- Preinstall procedure for upgrading to NetBackup 10.3
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.3
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.3
- About NetBackup startup and shutdown scripts
- Completing your system update after an upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- Client upgrade
- NetBackup Deployment Management with VxUpdate
- Appendix A. Reference
- NetBackup primary server web server user and group creation
- NetBackup database user
- Generate a certificate on the inactive nodes of a clustered primary server
- About the NetBackup Java Runtime Environment
- Add or Remove Java GUI and JRE after upgrade
- About the NetBackup web user interface
- About the NetBackup answer file
- Manually install or uninstall NetBackup IT Analytics Data Collector binaries
- Configure the NetBackup IT Analytics Data Collector manually for NetBackup
- Manually upgrading the NetBackup IT Analytics Data Collector
- Persistent Java Virtual Machine options
- About RBAC bootstrapping
- About NetBackup software availability
- Additional post-upgrade steps for NetApp clusters
- Using NetApp disk arrays with Replication Director
- About compatibility between NetBackup versions
- Upgrade requirements for UNIX and Linux
- Upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster upgrades
- Removing a clustered media server by migrating all data to a new media server
- Post upgrade procedures for Amazon cloud storage servers
- Upgrading clients after servers are upgraded
- Upgrade failure rollback steps
- Size guidance for the NetBackup primary server and domain
Silently upgrading NetBackup primary server software on Linux
You can upgrade NetBackup Linux primary servers with native installers. You can use either the NetBackup install script or your preferred installer method.
For Linux: rpm, yum, etc.
A successful installation or upgrade is recorded in the /usr/openv/pack/install.history file.
Note:
Because of package name changes, native installer methods require additional steps to upgrade primary servers from NetBackup 7.7.3 and earlier to NetBackup 8.0 and later. You have two options to correctly upgrade your primary servers and convert to the Veritas packages. You can use the NetBackup installer to upgrade the primary server to the new Veritas packages. Or you can follow the native installers procedure and perform the conditional steps. More information is available.
See “To upgrade the Linux primary server binaries using native installers:”.
Both of these upgrade options result in the same outcome. Once you have successfully upgraded to the Veritas packages, you can perform future upgrades with the installer of your choice.
To upgrade the Linux primary server binaries using native installers:
- Log on as the root user on the server.
- If the NetBackup Administration Console is open, you must close it now.
- (Conditional) For clustered environments, perform the following tasks:
If necessary, edit the
bp.confand thevm.conffiles as follows:If a
REQUIRED_INTERFACEentry exists, replace it with aCLUSTER_NAMEentry. Otherwise, add a newCLUSTER_NAMEentry. This entry should be defined as the virtual server name.For a primary server, make sure that the first
SERVERentry matches theCLUSTER_NAMEentry for thebp.conffile.Take the NetBackup Group offline. Use the command shown:
/opt/VRTSvcs/bin/hares -offline
Freeze the NetBackup Group so that migrations do not occur while the inactive nodes are upgraded. Use the command shown:
/opt/VRTSvcs/bin/hagrp -freeze group -persistent
If you have a VCS cluster configured, you can freeze the NetBackup Group by using the Cluster Manager interface or the command line.
Before you proceed with a cluster upgrade, refer to the NetBackup Clustered Primary Server Administrator's Guide for other cluster upgrade requirements.
- NetBackup scripts that are not covered in Chapter 1 that you modified are removed when you run the upgrade script. More information about this topic is available.
See About automatic file changes from an upgrade.
Save any files that you have modified and want to keep.
- Please create the NetBackup installation answer file (
NBInstallAnswer.conf) in the primary server's temporary directory. That directory is usually the/tmpdirectory. More information about the answer file and its contents is available. - You can add optional parameters to the
NBInstallAnswer.conffile. The parameters that are shown are examples of some of the parameters you can add. Veritas recommends that you review the NetBackup answer file section that is included in this documentation:LICENSE entries
LICENSE entries are only required on primary servers.
For upgrades from pre-NetBackup 10.3 to NetBackup 10.3 or later, the LICENSE entry is required. LICENSE=TEMP_PRODUCTION | license_file_path. If you have not downloaded your license from Veritas Entitlement management portal, you can use TEMP_PRODUCTION. More information is available: https://www.veritas.com/support/en_US/article.100058779
For upgrades from NetBackup 10.3 or later releases, you don't need to provide a LICENSE entry if you already have valid and unexpired license installed.
SERVER entries
DATABASE_USER
VXDBMS_POSTGRESQL_POOLER_ODBC_PORT
- (Conditional) If you want to assign RBAC security and backup administration roles to a user or a user group, populate
NBInstallAnswer.confwith the following required information:RBAC_DOMAIN_TYPE
Use this field to specify the domain type to which the user or the user group belongs. The following RBAC_DOMAIN_TYPE values are supported: NT, VX, UNIXPWD, LDAP.
RBAC_DOMAIN_NAME
Use this field to specify the name of the domain to which the user or the user group belongs.
RBAC_PRINCIPAL_TYPE
Use this field to specify USER or USERGROUP.
RBAC_PRINCIPAL_NAME
Use this field to specify the user name or the user group.
More information about the RBAC_* options is available.
- Download the server package that matches your server platform to a system with sufficient space. Then extract the contents of the server package file.
Extract the contents of the server package file. Example:
For Linux RedHat:
tar -xzvf NetBackup_10.3_LinuxR_x86_64.tar.gzFor Linux SuSE:
tar -xzvf NetBackup_10.3_LinuxS_x86_64.tar.gz
- Change to the directory for your desired operating system and copy server files to computer to be installed.
Operating system directory:
For Linux RedHat:
NetBackup_10.3_LinuxR_x86_64/linuxR_x86/anbFor Linux SuSE:
NetBackup_10.3_LinuxS_x86_64/linuxS_x86/anb
Copy server files to machine to be installed:
Linux
VRTSnbmqbrkr.rpm
VRTSnbprimary.rpm
VRTSnbslibs.rpm
VRTSnbweb.rpm
VRTSnetbp.rpm
VRTSpddei.rpm
VRTSpddes.rpm
VRTSpostgresql.rpm
- Extract the client binaries and copy them to the primary server.
Extract the client binaries:
tar -xzvf client_dist.tar.gz
Change directory to your desired operating system:
RedHat:
openv/netbackup/client/Linux/RedHat3.10.0SuSE:
openv/netbackup/client/Linux/SuSE3.0.76
Copy the files that are shown to the primary server.
RedHat Linux and SuSE Linux
VRTSnbpck.rpm VRTSpbx.rpm VRTSnbclt.rpm VRTSnbclibs.rpm VRTSnbjre.rpm VRTSnbjava.rpm VRTSpddea.rpm VRTSnbcfg.rpm
RedHat Linux only
VRTSpddeu.rpm
- (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 SYMCnetbp rpm -e SYMCpddes
Copy the
ita_dc.tar.gztarball from the media's/catalog/anb/directory to the/usr/openv/tmpdirectory.The copying of the tarball is only needed if you have to upgrade an existing unconfigured ITA DC installation on the host. Or if you upgrading from pre 10.1.1 release and want ITA DC.
If user doesn't want ITA DC installed they need to make sure the ITA DC value is in the answer file. set no.
(Conditional): If the upgrade is from NetBackup 10.1.1 or earlier and you want to install NetBackup IT Analytics Data Collector; or if you have an unconfigured NetBackup IT Analytics Data Collector you want to upgrade:
- Install the files in the order that is shown with the commands that are shown:
RedHat 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 VRTSpddes.rpm rpm -U VRTSpddeu.rpm rpm -U VRTSpddea.rpm rpm -U VRTSnbcfg.rpm rpm -U VRTSpostgresql.rpm rpm -U VRTSnetbp.rpm rpm -U VRTSnbprimary.rpm rpm -U VRTSnbmqbrkr.rpm rpm -U VRTSnbweb.rpm rpm -U VRTSnbslibs.rpm
SuSE 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 VRTSpddea.rpm rpm -U VRTSpddes.rpm rpm -U VRTSnbcfg.rpm rpm -U VRTSpostgresql.rpm rpm -U VRTSnetbp.rpm rpm -U VRTSnbprimary.rpm rpm -U VRTSnbmqbrkr.rpm rpm -U VRTSnbweb.rpm rpm -U VRTSnbslibs.rpm
- If you decide to install the Java GUI or the JRE after the installation completes, additional information is available.