Deployment job status
Monitor and review deployment job status in the Activity monitor. 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 |
|---|---|
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 settings.
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