Veritas NetBackup™ Upgrade Guide
- Introduction
- Planning for an upgrade
- General upgrade planning information
- About upgrade tools
- Upgrade operational notes and limitations
- Creating the user account to support the NetBackup web server
- About NetBackup 8.3 support for Fibre Transport Media Server with RHEL 7.5
- 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
- Master server upgrade
- About master server upgrades
- Preinstall procedure for upgrading to NetBackup 8.3
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading UNIX and Linux server software to NetBackup 8.3
- Post-install procedure for upgrading to NetBackup 8.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 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
- 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 Master Server
- Post upgrade procedures for Amazon cloud storage servers
- Upgrading clients after servers are upgraded
- Index
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.