Veritas NetBackup™ Upgrade Guide
- About changes in NetBackup 9.0
- 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
Preinstall procedure for upgrading to NetBackup 9.0
Use the following procedure to upgrade your environment to NetBackup 9.0.
Several tools are available to help you perform the extra step that is required for the guided method. For more details, contact your Business Critical Services (BCS) representative.
Additional steps are required if the NetBackup upgrade includes an upgrade to RHEL 7.5 and you use Fibre Transport Media Server (FTMS). More information is available.
See About NetBackup 9.0 support for Fibre Transport Media Server with RHEL 7.5.
Remember to update OpsCenter to version 9.0 before you update your NetBackup master servers to version 9.0. You must also disable OpsCenter data collection. See the OpsCenter Administrator's Guide for complete information.
Be aware there is a known issue for OpsCenter upgrades on 64-bit Windows platforms. If language packs or Maintenance Packs are installed, the upgrade can fail. More information about this issue is available.
You can disable the OpsCenter data collection for a specific master server. If you disable data collection, you can upgrade your master server before your OpsCenter server. Disabling data collection results in known issues. More information about disabling data collection and the risks is available.
See Disabling the connection between your OpsCenter server and your NetBackup Master Server.
For NetBackup installations that include globally clustered master servers using the Global Cluster Option (GCO), follow the upgrade planning guidelines in this guide. Then, refer to the following document for the specific steps to upgrade these servers: https://www.veritas.com/support/en_US/article.100041191
Preinstall steps to upgrade to NetBackup 9.0 and complete the image metadata migration
- Perform environment checks with the SORT tool.
- Download the Customer Registration Key for Veritas Usage Insights. More information about Veritas Usage Insights is available.
See About Veritas Usage Insights.
During install and upgrade to NetBackup 9.0, please allow the installer to copy the
veritas_customer_registration_key.jsonfile to its final destination. NetBackup can set the file permission and ownership correctly through this process. If you place the file onto your systems outside of the install or the upgrade process, the process may not work correctly.
- (Conditional) On UNIX, if the NetBackup database files reside on
btrfsfile system, move it to a supported file system (such as
xfs) before you upgrade. It is not supported to reside the NetBackup database on a
btrfsfile system. The database files reside on the master server in the directories under
To move the NetBackup database files on UNIX:
Perform a catalog backup.
Shut down all NetBackup daemons:
Start the SQL Anywhere daemon:
Move the existing data, index, and transaction log files:
/usr/openv/db/bin/nbdb_move -data data_directory -index index_directory -tlog log_directory
If you use mirrored transaction log, use the command shown:
/usr/openv/db/bin/nbdb_move -data data_directory -index index_directory -tlog log_directory -mlog log_mirror_directory
Start all NetBackup daemons:
Perform a catalog backup.
Perform any pre-upgrade tasks that you would normally do in regard to your NetBackup environment. For example:
Stop all customized or third-party scripts.
Perform any cluster-specific tasks.
Run a hot catalog backup.
Disable OpsCenter data collection for this master server.
Disable all storage lifecycle policies (SLPs).
Deactivate all NetBackup policies.
Deactivate all disk staging storage units for all pre-NetBackup 7.5.x environments.
For clustered systems only, take the following NetBackup resources offline:
Windows Server Failover Clusters (WSFC): Take all of the NetBackup group resources offline except for the disk, the virtual name, and the virtual IP address. Refer to the Microsoft Cluster Administration documentation to determine how to take the NetBackup group resources offline through the cluster administrator interface.
Cluster Server (VCS) clusters: Take the NetBackup resource offline.
Freeze the NetBackup group with the -persist option using the command shown:
hagrp -freeze NetBackup_service_group -persistent
Refer to the Veritas NetBackup Clustered Master Server Administrator's Guide for the commands to take these resources offline.
- (Conditional) If you plan to change your NetApp cluster to Vserver mode from node scope mode, create a detailed image report for each filer. You can generate this report with the bpimagelist command. The example that is shown is one possible option. Use whatever options are necessary for your environment.
bpimagelist - client ndmp_host_name
- Beginning with NetBackup 8.0, the NetBackup master server includes a configured Tomcat web server to support critical backup operations. This web server operates under user account elements with limited privileges. These user account elements must be available on each master server (or each node of a clustered master server). More information is available:
See NetBackup master server web server user and group creation.
It is recommended that you save the details of the user account that you use for the NetBackup Web Services. A master server recovery requires the same NetBackup Web Services user account and credentials that were used when the NetBackup catalog was backed up.
If the NetBackup PBX is running in secure mode, please add the web service user as authorized user in PBX. More information about determining PBX mode and how to correctly add users is available.
- (Conditional) If you have customized the settings for your Tomcat web server, determine if those settings persist across upgrades. More information is available:
- Stop any applications on the system that interact with NetBackup. This step includes any databases or system components being backed up. Failure to stop these applications may result in unexpected behavior. Observed behavior includes aborted upgrades and application failures.
For Oracle users, ensure that no backups are running. Stop the RMAN processes before you install NetBackup. If you use AIX, you should run /usr/bin/slibclean as the root user after you stop the RMAN processes.
If you cannot stop your Oracle database, a procedure is available that may let you install NetBackup with the Oracle database active. More information on this topic is available.
Stop all NetBackup services.
On UNIX systems: /usr/openv/netbackup/bin/bp.kill_all
On Windows systems: install_path\NetBackup\bin\bpdown -f
The preinstall procedure is completed. Proceed to upgrade the NetBackup binaries, based on your platform. More information is available about this topic.