NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.2 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.2
- 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.2 upgrade
- How to plan for an upgrade to NetBackup 10.2
- 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
- Performance and tuning considerations
- About upgrade tools
- Upgrade operational notes and limitations
- Creating the user account to support the NetBackup web server
- NetBackup IT Analytics Data Collector installed for NetBackup 10.2
- About NetBackup 10.2 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.2
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.2
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.2
- 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
- Manual install or uninstall of the NetBackup IT Analytics Data Collector
- Configure Data Collector manually for NetBackup
- Manually upgrading the 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
Upgrade issue with pre-8.1 clients and 8.1 or later media servers
With the NetBackup 8.1 upgrade, the fingerprinting algorithm was upgraded from MD5 to SHA2 to provide improved protection against security vulnerabilities. Veritas introduced two conversion methods to convert existing MD5 fingerprint data to SHA2: rolling conversion and inline conversion. Problems occur under the conditions shown:
Client is pre-8.1 NetBackup.
Client uses Client Direct, which performs deduplication at the client.
Client is backed up by a NetBackup 8.1 or later media server.
Under these conditions, the fingerprint conversion happens inline. As a result, backup performance is negatively effected and the CPU processing load on the media server increases. The media server has to rehash the MD5 information and create a SHA2 fingerprint.
To prevent this issue:
For pre-8.1 clients, change their backup to use media server deduplication (MSDP) with a media server that is at NetBackup 8.1 or later. This action avoids the backup performing the inline conversion.
Do not use Client Direct on pre-8.1 clients that are backed up by 8.1 and later media servers.