NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.0.0.1 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.0.0.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.0.0.1 upgrade
- How to plan for an upgrade to NetBackup 10.0.0.1
- 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
- About upgrade tools
- Upgrade operational notes and limitations
- Creating the user account to support the NetBackup web server
- About NetBackup 10.0.0.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.0.0.1
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.0.0.1
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.0.0.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 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
- 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
- Installation and 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
- Disabling the connection between your OpsCenter server and your NetBackup Primary Server
- Post upgrade procedures for Amazon cloud storage servers
- Upgrading clients after servers are upgraded
- Upgrade failure rollback steps
- Index
MSDP changes in NetBackup 8.1
The NetBackup 7.7.x or 8.0 to 8.1 upgrade includes a rolling Media Server Deduplication Pool (MSDP) data conversion. This conversion works in the background to convert all existing data containers to the AES encryption and the SHA-2 fingerprint algorithm. You can manage and monitor the rolling data conversion with the crcontrol command. More information about the use of the crcontrol command is available. See the rolling data conversion sections in the NetBackup Deduplication Guide. Additionally, refer to the crcontrol command in the NetBackup Commands Reference Guide.
The rolling conversion is performed when the system is not busy. In other words, the conversion runs when backups, restores, CRQP, CRC checks, compaction, etc. are not active. This conversion is not expected to affect normal system operations. After the rolling conversion is finished, there is no difference between the converted system and a new installation.
No explicit steps are required for conversion process during the upgrade of NetBackup. After upgrade, the rolling conversion begins to work in the background. Once the rolling conversion is started, is not possible return to the original NetBackup version. More information about the rolling conversion is available. See the rolling data conversion sections in the NetBackup Deduplication Guide.