Veritas NetBackup™ Appliance Upgrade Guide
Manually initiating upgrades from the client using VxUpdate
Manually initiate deployment jobs when you are logged into the 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 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 client. You cannot use the nbinstallcmd command on a client to launch jobs on other clients. If you want to launch updates on other 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 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.
- Monitor upgrade status with the NetBackup administrator and the Activity Monitor in the NetBackup Administrative Console.
You can start a 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.