NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.5 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.5
- Client push staging area no longer populated
- VRTSpddei.rpm no longer delivered in NetBackup 10.5
- About binaries installed on primary and media servers
- 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.5 upgrade
- How to plan for an upgrade to NetBackup 10.5
- 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
- Minimum operating system versions
- Windows compiler and security requirements for NetBackup 10.5 and later upgrade
- Creating the user account to support the NetBackup web server
- About NetBackup 10.5 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.5
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.5
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.5
- 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 pushing client software from a primary server to clients
- 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 pushing client software from a primary server to clients
You can increase the speed of client installation by pushing the software from the primary server to the clients. This method eliminates the need for a local installation at each client.
The following describes how to prepare your NetBackup environment for client software installation from the primary server.
Install the client type software on the primary server. Be sure to install all of the client types that pertain to your NetBackup configuration.
As of NetBackup 10.5, no client software is populated in the client push install and upgrade staging area. Follow the process that is shown for all client operating systems.
Before you can push client software from the primary server, each client name must be assigned to a NetBackup policy. Policies are created on the primary server.
When you create a policy, you must identify the policy type, which indicates the operating system on the clients that are assigned to that policy. Without a policy, the remote installation (or push) fails because the primary server does not know the operating system of the client.
For information on how to create NetBackup policies, refer to the NetBackup Administrator's Guide, Volume I.
After the required policies are created, you can push client software from the primary server to the clients.