NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.1.1 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.1.1
- 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.1.1 upgrade
- How to plan for an upgrade to NetBackup 10.1.1
- 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.1.1
- About NetBackup 10.1.1 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.1.1
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.1.1
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.1.1
- 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
- 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
- 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
About MSDP rolling data conversion
NetBackup 8.0 introduced the AES encryption algorithm to replace the existing Blowfish algorithm. NetBackup 8.1 introduces the SHA-2 fingerprint algorithm to replace the existing MD5-like algorithm. The upgrades to both the encryption and the fingerprint algorithms are designed to enhance data security.
The environments that are upgraded to NetBackup 8.1 may include Blowfish encrypted data and the MD5-like fingerprints that need to be converted to the new format. To handle the conversion and secure the data, a new internal task converts the current data container to the AES encryption and the SHA-2 fingerprint algorithm. This new task is referred to as the rolling data conversion.
Rolling data conversion traverses all existing data containers. If the data is encrypted with the Blowfish algorithm, the data is re-encrypted with the AES algorithm. Then a new SHA-2 fingerprint is generated. After the conversion, the data container has a new file with a .map extension, in addition to the .bhd and .bin files. The .map file contains the mapping between the SHA-2 and the MD5-like fingerprints. The .bhd file includes the SHA-2 fingerprints.
In a new installation of NetBackup 8.1, the rolling data conversion is marked as Finished and doesn't start in the future. For an upgrade to NetBackup 8.1, the rolling data conversion is enabled by default and works in the background after the MSDP conversion completes. Only the data that existed before upgrade is converted. All new data uses the new SHA-2 fingerprint and does not need conversion.
You can manage and monitor the rolling data conversion using the crcontrol command. More information about its use is available.
See the NetBackup Deduplication Guide and the NetBackup Commands Reference Guide.