Veritas NetBackup™ Upgrade Guide
- Introduction
- About changes in NetBackup 8.1.2
- Planning for an upgrade
- Master server upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- NetBackup Deployment Management with VxUpdate
- Appendix A. Reference
- About the NetBackup web user interface
About VxUpdate
Veritas introduces VxUpdate in NetBackup 8.1.2. VxUpdate is the replacement for LiveUpdate. The main component of VxUpdate is the new deployment policy that serves as a client upgrade tool. With the release of VxUpdate, Veritas no longer supports LiveUpdate.
With support for policies, Veritas provides a simplified tool for 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 new 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.
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 or the client | See Manually initiating upgrades from the master server using VxUpdate. See Manually initiating upgrades from the client using VxUpdate. |