NetBackup™ Upgrade Guide
- Introduction
- About changes in NetBackup 10.0
- Planning for an upgrade
- General upgrade planning information
- About upgrade tools
- Upgrade operational notes and limitations
- General upgrade planning information
- Primary server upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- Client upgrade
- NetBackup Deployment Management with VxUpdate
- Appendix A. Reference
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:
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
Your deployment job may receive a status code 7207. This error can occur if NetBackup precheck or upgrade processes take longer than expected to finish or never finish. To configure the amount of time VxUpdate waits before jobs end with status 7207, you can define the following values in the NetBackup configuration on the primary server.
VXUPDATE_CLIENT_READ_TIMEOUT_SECONDS
This value controls how long the precheck operations and the client upgrade operations are allowed to take, in seconds. The default value is 1800, or 30 minutes. It can be decreased to as little as 600, 10 minutes, or increased to as much as 3600, 60 minutes.
VXUPDATE_SERVER_READ_TIMEOUT_SECONDS
This value controls how long server upgrade operations are allowed to take, in seconds. The default value is 2700, or 45 minutes. It can be decreased to as little as 600, 10 minutes, or increased to as much as 5400, 90 minutes.
See the NetBackup Commands Reference Guide for details on how to use the bpsetconfig command to add values to the NetBackup configuration of a primary server.