Veritas NetBackup™ LiveUpdate Guide
- About NetBackup LiveUpdate
- NetBackup LiveUpdate operational notes
- Setting up a LiveUpdate server
- Updating servers and clients
- About LiveUpdate logs
- Appendix A. Reference
About updating servers
After you have created LiveUpdate policies and downloaded release updates to your NetBackup LiveUpdate server, you are ready to update your NetBackup environment.
Review the following guidelines before you begin any updates.
For Windows clients, NetBackup client services must be running on those servers that are listed in the LiveUpdate policy that you plan to update.
NetBackup servers and clients must be updated in a specific order. Master servers must always be at the same or a later version as media servers or clients. Clients that use a later version of NetBackup than servers can cause problems and prevent backups or restores.
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.
The following describes the order that updates should take place:
Always update master servers first.
Master servers that run LiveUpdate policies cannot be updated with those policies. These servers must be updated with one of the following methods:
Use the nbliveup command locally on each server that you want to update.
Before you perform a local update, you must stop the NetBackup client services on that server.
Run a LiveUpdate policy from a different NetBackup master server.
For example, to update master server A from a policy on master server B you must perform the following steps:
Create a LiveUpdate policy on master server B.
Add master server A as a client to the policy on master server B.
Add master server B to the
registry entryfile (Windows) or the
bp.conffile (UNIX) on master server A.
Run the policy on master server B.
After all master servers are updated, media servers can be updated.
However, the media servers that are involved with the master servers that run LiveUpdate policies cannot be updated with those policies. These servers must be updated locally or with a LiveUpdate policy on a master server that does not involve the media server to be updated.
To update media servers, use the same methods that are used for master server updates.
After master servers and media servers are updated, you can update clients.
A known issue exists when the nbliveup command is used on AMD64 systems. Use the nbliveup command on these systems with one of the following methods:
Method A - Local update
You must log on to the computer as the console user either locally or through a remote desktop session, by using the following command:
mstsc -v:your.machine.name.com /F -console
For complete details, go to the following link:
Method B - Remote update
Initiate the LiveUpdate session from a different NetBackup master server.