NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.4 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.4
- License file required for upgrade
- Windows primary server upgrades are slowed if a large number of files are in the installation directory
- About NetBackup database changes
- 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.4 upgrade
- How to plan for an upgrade to NetBackup 10.4
- 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
- Performance and tuning considerations
- About upgrade tools
- Upgrade operational notes and limitations
- Windows compiler and security requirements for NetBackup 10.4 and later upgrade
- Creating the user account to support the NetBackup web server
- About NetBackup 10.4 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.4
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.4
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.4
- 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
- NetBackup database user
- 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
- About the NetBackup IT Analytics Data Collector
- Manually install or uninstall NetBackup IT Analytics Data Collector binaries
- Manually configure the NetBackup IT Analytics Data Collector
- Manually upgrading the NetBackup IT Analytics Data Collector
- 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 NetBackup database changes
The NetBackup database is converted to a new database solution. As a part of the database conversion, NetBackup attempts to determine the number of records in the NetBackup database, and estimate the time that is required for update. If the estimated upgrade time exceeds 2 hours, you are prompted to confirm that you want to continue.
As a part of internal Veritas testing, databases that were roughly 55 GB in size with around 100 million records took the approximate time shown based on operating system:
Linux: Approximately 30 minutes.
Windows: Between 30 minutes and 2 hours, depending on hardware.
The times shown here apply only to the database conversion, not to the upgrade itself.
During upgrade, additional disk space is required for the conversion. The space is necessary to create and migrate the new databases. Internal Veritas testing shows that the upgrade requires approximately twice the space of the current NetBackup database for the conversion.
Veritas recommends that you run the database precheck tool to identify any potential data issues before you upgrade NetBackup. See https://www.veritas.com/support/en_US/article.100055151 for instructions about how to use the precheck tool. Veritas also recommends that you defragment the NetBackup database before upgrade to improve the overall conversion experience. See the NetBackup Administrator's Guide, Volume I for additional information on the option to defragment the database.