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 9.0.0.1 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 9.0.0.1
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading UNIX and Linux server software to NetBackup 9.0.0.1
- Post-install procedure for upgrading to NetBackup 9.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 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
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.
Table: MSDP upgrade details
Activity | Details |
|---|---|
Original NetBackup version | 7.7.x and 8.0 |
Final upgraded NetBackup version | 8.1 |
Conversion required | A rolling conversion to the AES encryption and the SHA-2 fingerprint algorithm. The rolling conversion starts automatically after NetBackup upgrade installation completion. |
Monitor, control, and time calculations for the conversion | More information about the rolling conversion is available. See the rolling data conversion sections in the NetBackup Deduplication Guide. |
Required downtime? | No downtime is required. 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. |