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 8.2 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 8.2
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading UNIX and Linux server software to NetBackup 8.2
- Post-install procedure for upgrading to NetBackup 8.2
- 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
- About the NetBackup web user interface
- About the NetBackup answer file
- About RBAC bootstrapping
- Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.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
- 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
- Upgrading clients after servers are upgraded
Manually initiating upgrades from the media server or client using VxUpdate
Manually initiate deployment jobs when you are logged into the media server or client locally and want to force an immediate update. You can either use a deployment policy to initiate an immediate upgrade or specify an upgrade without an associated policy. You can use the upgrade to update the NetBackup version or for other upgrades such as emergency binaries.
Among the reasons for a media server or a client initiated upgrade using VxUpdate is mission critical systems with specific maintenance windows. One example of these systems is database servers with limited available down time.
Note:
You can only launch updates on the local media server or client. You cannot use the nbinstallcmd command on a media server or client to launch jobs on other media servers or clients. If you want to launch updates on other media servers and clients, you must initiate them from the master server.
VxUpdate also provides the ability to launch upgrades from the master server with the command line. More information is available.
See Manually initiating upgrades from the master server using VxUpdate.
To start a media server or client initiated deployment job based on an existing policy
- Navigate to the binary directory from a command prompt.
UNIX or Linux: /usr/openv/netbackup/bin
Windows: install_path\netbackup\bin
- Use the nbinstallcmd as shown:
nbinstallcmd -policy policy -schedule schedule -master_server name
Example: nbinstallcmd -policy all_clients -schedule install812 -master_server master1
If the job initiated successfully, you are returned to the command prompt without an error message.
Note:
When you initiate a media server upgrade with the nbinstallcmd command, you must include both the -master_server and the -media_server options. In this case, the value for both these options must be the same.
- Monitor upgrade status with the NetBackup administrator and the Activity Monitor in the NetBackup Administrative Console.
You can start a media server or client initiated deployment job without an associated policy from the command line. The options required for the nbinstallcmd command vary depending on your security configuration. Please refer to the nbinstallcmd command documentation for a list of all possible options and examples of command usage.