NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.4 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.4
- 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
- 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.4 upgrade
- How to plan for an upgrade to NetBackup 10.4
- 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
- Windows compiler and security requirements for NetBackup 10.4 and later upgrade
- Creating the user account to support the NetBackup web server
- About NetBackup 10.4 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.4
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.4
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.4
- 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
- About the NetBackup IT Analytics Data Collector
- Manually install or uninstall NetBackup IT Analytics Data Collector binaries
- Manually configure the NetBackup IT Analytics Data Collector
- 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
MSDP upgrade considerations for NetBackup 8.1
Because of the changes in the fingerprint algorithm for MSDP in NetBackup 8.1, consider your MSDP environment as you plan your upgrade path. Any NetBackup 8.0 and older host cannot access the NetBackup 8.1 MSDP because of the new fingerprint algorithm. Failed NetBackup jobs can result from a failure to plan for this condition.
If the media servers list for an 8.1 MSDP storage server contains 8.0 or older servers, you can experience failures because of the new algorithm. If the common media server between an 8.1 server and an 8.0 server is the 8.0 server, jobs can fail. If you use client direct, the client must be upgraded to 8.1 or you can experience client direct restore errors. These failures are because the 8.0 and older hosts cannot access the 8.1 server.
As you plan your upgrade, if you have multiple media servers as part of an MSDP environment, consider the options shown:
Upgrade all MSDP media servers that share access rights to each other together. Upgrade all clients that use client direct to these MSDP disk pools.
This option insures there are no interruptions in your environment.
Upgrade MSDP media servers and clients using client direct as your environment allows and make no configuration changes.
If the selected common media server is not a NetBackup 8.1 server, the risk is restores, verifies, imports, and optimized duplication may fail. If client direct is used on older clients, you can experience client direct restore errors. This failure is because of the algorithm change.
Upgrade MSDP media servers and clients using client direct as your environment allows. Modify your list of credentialed media servers for the upgraded storage servers to only include NetBackup 8.1 servers.
This action effectively revokes access rights for the non-upgraded servers to the upgraded servers. The risk is previously configured operations may stop working because of the access change. If you choose this option, you should make detailed notes about the configuration changes so you can revert those changes once all media servers are upgraded.
If duplication jobs copy from an 8.1 MSDP to an 8.0 or older MSDP, then create a storage unit for the older MSDP. Restrict the list on that new storage unit to the 8.1 host. You must change any storage lifecycle policy (SLP) controlled duplication jobs if they copy from an 8.0 or older MSDP host to an 8.1 MSDP host. Set the Alternate Read Server on the duplication stage to the 8.1 media server.