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 8.3 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 8.3
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading UNIX and Linux server software to NetBackup 8.3
- Post-install procedure for upgrading to NetBackup 8.3
- 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
- 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
About VxUpdate
VxUpdate provides a policy-based upgrade tool for media servers and clients. By using the policy format, Veritas provides a simplified tool for media server and client upgrades. No additional external tools are required and the configuration is in a familiar policy-based format, similar to a backup policy. Signed packages are verified and installed into the VxUpdate repository on the master server. Once the packages are installed, they become available for use with deployment policies. Additionally, you can use the deployment policies to automate the installation of emergency engineering binaries, as provided by Veritas.
The deployment policy lets you configure and run deployment activities on a schedule or enable the client host owners to upgrade at their convenience. Furthermore, you can split deployment activities into smaller, discrete tasks. You can schedule pre-check, staging, and installation tasks as separate activities with different schedules, each with their own specific deployment windows.
Note:
You can only cancel queued deployment jobs. Once a VxUpdate job enters the active state it cannot be canceled.
The deployment policies are not located with the other policies in the NetBackup Administrative Console. Deployment policies are located in the NetBackup Administration Console under Deployment Management > Deployment Policies.
To successfully create and use deployment policies, Veritas recommends:
Table:
Step | Action | Additional information |
|---|---|---|
1 | Populate the NetBackup repository | |
2 | Create the deployment policy | |
3 | (Optional) Manually run the upgrade from the master server, media server, or the client | See Manually initiating upgrades from the master server using VxUpdate. See Manually initiating upgrades from the media server or client using VxUpdate. |