Veritas NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 8.1.2 Upgrade Guide
- About changes in NetBackup 8.1.2
- Veritas Smart Meter introduced
- Upgrades from NetBackup 7.6.0.4 and earlier are not supported
- HP-UX and AIX support change
- Newer Red Hat Linux compilers used with NetBackup 8.1.2
- VxUpdate replaces update_clients script in NetBackup 8.1.2
- Port 443 required for NetBackup web user interface
- About MSDP
- Performance issues with upgrades to NetBackup 8.1.2 from NetBackup 8.0 and earlier
- About certificate requirements for NetBackup 8.1
- SCCM and Chef deployment tools and documentation now available
- Potential required changes for NetApp clusters
- About automatic file changes from an upgrade
- Errors when Bare Metal Restore information is replicated using Auto Image Replication
- Known catalog backup limitation
- Available NetBackup upgrade methods
- About Veritas Services and Operations Readiness Tools
- Recommended SORT procedures for new installations
- Recommended SORT procedures for upgrades
- About the NetBackup preinstall checker
- Planning for an upgrade
- About planning a NetBackup 8.1.2 upgrade
- How to plan for an upgrade to NetBackup 8.1.2
- About Veritas Smart Meter
- Best practices for Veritas Smart Meter
- Creating the user account to support the NetBackup web server
- About NetBackup 8.1.2 support for Fibre Transport Media Server with RHEL 7.5
- MSDP changes in NetBackup 8.1
- About security certificates for NetBackup hosts
- Master server upgrade
- About master server upgrades
- Preinstall procedure for upgrading to NetBackup 8.1.2
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading UNIX/Linux server software to NetBackup 8.1.2
- Post-install procedure for upgrading to NetBackup 8.1.2
- About NetBackup startup and shutdown scripts
- Completing your system update after an upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- 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
- About the NetBackup web user interface
- About the NetBackup answer file
- Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.1.2
- About NetBackup software availability
- Additional post-upgrade steps for NetApp clusters
- Using NetApp disk arrays with Replication Director
- About compatibility between NetBackup versions
- Installation and upgrade requirements for UNIX and Linux
- Installation and upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster installations and upgrades
- Upgrading clients after servers are upgraded
- Install and upgrade of the UNIX and Linux client binaries with native installers
- Removing a clustered media server by migrating all data to a new media server
- Disabling the connection between your NetBackup OpsCenter server and your NetBackup Master Server
- Post upgrade procedures for Amazon cloud storage servers
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.