NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.0 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.0
- 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.0 upgrade
- How to plan for an upgrade to NetBackup 10.0
- Legacy logging directory 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
- About upgrade tools
- Upgrade operational notes and limitations
- Creating the user account to support the NetBackup web server
- About NetBackup 10.0 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.0
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.0
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.0
- 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 master server web server user and group creation
- Generate a certificate on the inactive nodes of a clustered master 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
- 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
- Installation and upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster installations and upgrades
- Removing a clustered media server by migrating all data to a new media server
- Disabling the connection between your OpsCenter server and your NetBackup Primary Server
- Post upgrade procedures for Amazon cloud storage servers
- Upgrading clients after servers are upgraded
- Upgrade failure rollback steps
- Index
Available NetBackup upgrade methods
Table: UNIX and Linux upgrade and EEB and Table: Windows upgrade and EEB provide details on the ways in which you can upgrade NetBackup. To better understand which upgrade method is best for your environment, consider:
Interactive: Requires user input through the UI during the upgrade process.
Silent or native: Upgrades that use the Windows command files, or directly call the UNIX and Linux native package managers.
Push or remote: Includes options such as VxUpdate, Chef, and SCCM. Additionally, you can do a remote upgrade with Windows or use ssh or sftp with UNIX and Linux.
Table: UNIX and Linux upgrade and EEB
Method | Primary | Media | Client |
|---|---|---|---|
Interactive | See Upgrading NetBackup media servers to NetBackup 10.0. See About VxUpdate. | Yes. See the information about primary servers. See About VxUpdate. | |
Silent or native | See Silently upgrading NetBackup primary server software on Linux. | See Silently upgrading NetBackup media server software on Linux. See About VxUpdate. | See Upgrade of the UNIX and Linux client binaries with native installers. See About VxUpdate. |
Push or remote | Upgrade: No EEB: Push upgrade of EEBs may work through 3rd party deployment tools. You can also use the Chef and SCCM templates provided by Veritas. | See About VxUpdate. | See Upgrading clients after servers are upgraded. Chef and SCCM templates https://sort.veritas.com/utility/netbackup/deployment See About VxUpdate. |
Table: Windows upgrade and EEB
Method | Primary | Media | Client |
|---|---|---|---|
Interactive | See Performing local, remote, or clustered server upgrades on Windows systems. | See Upgrading NetBackup media servers to NetBackup 10.0. See About VxUpdate. | Yes. See the information about primary servers. See About VxUpdate. |
Silent | See Performing silent upgrades on Windows systems. See About VxUpdate. | Yes. See the information about primary servers. See About VxUpdate. | |
Push or remote | Upgrade: See Performing local, remote, or clustered server upgrades on Windows systems. EEB: Push upgrade of EEBs may work through 3rd party deployment tools. You can also use the Chef and SCCM templates provided by Veritas. | See Upgrading NetBackup media servers to NetBackup 10.0. See About VxUpdate. | Yes. See the information about primary servers. Chef and SCCM templates https://sort.veritas.com/utility/netbackup/deployment See About VxUpdate. |
VxUpdate provides a policy-based and on demand upgrade tool for media servers and clients. The policy format provides a simplified tool for media server and client upgrades. The on demand ability provides immediate upgrades as needed.
The VxUpdate configuration is in a familiar policy-based format, similar to a backup policy. You can use the deployment policies to automate the installation of emergency engineering binaries, as provided by Veritas. The deployment policy lets you configure and run deployment activities on a schedule or enable the client host owners to upgrade on demand. Veritas recommends use of VxUpdate for push or remote upgrades where possible.