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 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
- 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
- Post-install procedure for upgrading to NetBackup 9.0
- 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
Deployment job status
Monitor and review deployment job status in the Activity Monitor in the NetBackup Administration Console. The Deployment job type is the new type for VxUpdate policies. Deployment policy parent jobs that exit with a status code 0 (zero) indicate that all the child jobs successfully completed. Parent jobs that finish with a status code 1 indicate that one or more of the child jobs succeeded, but at least one failed. Any other status code indicates failure. Review the status of the child jobs to determine why they failed. Otherwise, there are no differences between deployment jobs and other NetBackup jobs.
Your deployment job may receive a status code 224. This error indicates that the client's hardware and operating system are specified incorrectly. You can correct this error by modifying the deployment policy with the bpplclients command found in:
UNIX or Linux: /usr/openv/netbackup/bin/admincmd
Window: install_path\netbackup\bin\admincmd.
Use the syntax shown:
bpplclients deployment_policy_name -modify client_to_update -hardware new_hardware_value -os new_os_value
Deployment policies use a simplified naming scheme for operating system and hardware values. Use the values as shown for the bpplclients command:
Table: Deployment policy operating system and hardware
Operating system | Hardware |
|---|---|
hpux | ia64 |
debian | x64 |
redhat | x64 |
suse | x64 |
redhat | ppc64le |
suse | ppc64le |
redhat | zseries |
suse | zseries |
aix | rs6000 |
solaris | sparc |
solaris | x64 |
windows | x64 |
Security certificates are not deployed as part of the VxUpdate upgrade if the is set to . This setting is located in the in the NetBackup Administration Console.
If you cannot communicate with your clients after you use VxUpdate to upgrade your clients, please ensure that the proper security certificates were issued during upgrade. You may need to manually deploy the certificates. Refer to the following article that is shown for additional details:
https://www.veritas.com/content/support/en_US/article.100039650