Veritas NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 8.1.2 Upgrade Guide
- About changes in NetBackup 8.1.2
- Veritas Smart Meter introduced
- Upgrades from NetBackup 7.6.0.4 and earlier are not supported
- HP-UX and AIX support change
- Newer Red Hat Linux compilers used with NetBackup 8.1.2
- VxUpdate replaces update_clients script in NetBackup 8.1.2
- Port 443 required for NetBackup web user interface
- About MSDP
- Performance issues with upgrades to NetBackup 8.1.2 from NetBackup 8.0 and earlier
- About certificate requirements for NetBackup 8.1
- SCCM and Chef deployment tools and documentation now available
- Potential required changes for NetApp clusters
- About automatic file changes from an upgrade
- Errors when Bare Metal Restore information is replicated using Auto Image Replication
- Known catalog backup limitation
- Available NetBackup upgrade methods
- About Veritas Services and Operations Readiness Tools
- Recommended SORT procedures for new installations
- Recommended SORT procedures for upgrades
- About the NetBackup preinstall checker
- Planning for an upgrade
- About planning a NetBackup 8.1.2 upgrade
- How to plan for an upgrade to NetBackup 8.1.2
- About Veritas Smart Meter
- Best practices for Veritas Smart Meter
- Creating the user account to support the NetBackup web server
- About NetBackup 8.1.2 support for Fibre Transport Media Server with RHEL 7.5
- MSDP changes in NetBackup 8.1
- About security certificates for NetBackup hosts
- Master server upgrade
- About master server upgrades
- Preinstall procedure for upgrading to NetBackup 8.1.2
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading UNIX/Linux server software to NetBackup 8.1.2
- Post-install procedure for upgrading to NetBackup 8.1.2
- About NetBackup startup and shutdown scripts
- Completing your system update after an upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- 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
- About the NetBackup web user interface
- About the NetBackup answer file
- Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.1.2
- About NetBackup software availability
- Additional post-upgrade steps for NetApp clusters
- Using NetApp disk arrays with Replication Director
- About compatibility between NetBackup versions
- Installation and upgrade requirements for UNIX and Linux
- Installation and upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster installations and upgrades
- Upgrading clients after servers are upgraded
- Install and upgrade of the UNIX and Linux client binaries with native installers
- Removing a clustered media server by migrating all data to a new media server
- Disabling the connection between your NetBackup OpsCenter server and your NetBackup Master Server
- Post upgrade procedures for Amazon cloud storage servers
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 technote that is shown for additional details: