Updating servers by using NetBackup LiveUpdate
Use the following guidelines when updating NetBackup with NetBackup LiveUpdate policies or the nbliveup command:
LiveUpdate policies
For Windows servers, NetBackup client services must be running on those servers that are listed in the LiveUpdate policy that you plan to use.
nbliveup command
For local upgrades, NetBackup client processes and services must be stopped before servers can be updated.
See Stopping NetBackup processes and services before upgrading locally.
Note:
NetBackup LiveUpdate cannot update servers to a major or a minor release version of NetBackup. If you try to use NetBackup LiveUpdate to update a server to a major or a minor release, the upgrade fails. Windows systems display an error message. On UNIX systems, the attempt appears to be successful even though the updates were not applied.
Use the following procedure to update servers. Start with the master servers and then update any media servers.
To update servers by using NetBackup LiveUpdate
- Make sure that there is no backup or restore job activity on the master server where you run the LiveUpdate policy.
Update master servers with one of the following methods:
nbliveup command (for local updates)
Windows systems:
NetBackup\bin\nbliveup.exe liveupdateServerProtocolOverride <LiveUpdate_Server_Location>
UNIX systems:
/usr/openv/netbackup/bin/nbliveup -v -d liveupdateServerProtocolOverride <LiveUpdate_Server_Location>
Note:
Do not run multiple instances of this command at a time. Before you run the command again, wait until the exit status message appears to verify that the previous instance has completed.
When you use the nbliveup command, enter the complete path of the LiveUpdate server location where the updates reside.
The following examples show the format that you must use to enter the server location:
http://yourWebServer.com/LUServer/
file:/net/yourFileServer/LUServer/
file:\\yourFileServer\LUServer\
LiveUpdate policy
To run the LiveUpdate policy:
From a different server, launch the NetBackup Administration Console.
Click File > LiveUpdate.
In the LiveUpdate Policy window, select the LiveUpdate policy that includes the master server that you want to update.
Click Run LiveUpdate Policy.
Check the Activity Monitor to verify that all LiveUpdate jobs complete.
Clustered servers
Use the nbliveup command as follows:
On Windows systems:
For best practices, update the inactive nodes first and then update the active node.
On each inactive node in the cluster, run the following command:
NetBackup\bin\nbliveup.exe liveupdateServerProtocolOverride <LiveUpdate Server_Location>
On the active node, run the following command:
NetBackup\bin\nbliveup.exe liveupdateServerProtocolOverride <LiveUpdate_Server_Location>
On UNIX systems:
On the active node, run the following command:
/usr/openv/netbackup/bin/bpclusterutil - freeze
On each node in the cluster, run the following command:
/usr/openv/netbackup/bin/nbliveup -v -d liveupdateServerProtocolOverride <LiveUpdate_Server_Location>
Note:
Do not run multiple instances of this command at a time. Before you run the command again, wait until the exit status message appears to verify that the previous instance has completed.
On the active node, run the following command:
/usr/openv/netbackup/bin/bpclusterutil - unfreeze
- If you have media servers, repeat the steps in this procedure to update those servers.
Note:
After you run a LiveUpdate policy on Windows systems to upgrade to NetBackup 7.7.2, the activity monitor may report an exit status 77 error. This error code may indicate that the installation that the LiveUpdate policy executed was unsuccessful. If this error code appears, examine the installation log file on the remote system where the installation error occurred. The log file is located at
% ALLUSERSPROFILE% \Veritas\NetBackup\InstallLogs. Search the log for any strings that includeReturn Value 3or for any log messages that appear in yellow or red text. You can also verify that the upgrade was successful from the NetBackup Administration Console by checking the Host Properties on the server that reported the error.