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
Configuring hosts locally
When you create a LiveUpdate policy, Veritas recommends that you enable the feature.
However, if you want the clients in a single LiveUpdate policy to use different LiveUpdate servers, you must disable this option in the policy. You must also ensure that each listed client in the LiveUpdate policy is locally configured to receive updates from a valid LiveUpdate server.
All servers and clients that were updated using LiveUpdate are already locally configured. If the existing configuration is still valid, no additional steps are required.
LiveUpdate server configuration is stored in a local file on each host that runs a LiveUpdate agent.
This file cannot be read or edited in a text editor.
Use the following procedures to locally configure a Windows or a UNIX host.
To locally configure a Windows host
- Use the command-line interface to edit the following line:
<IDrive>\Program Files\NetBackup\Bin\LU_Registration.exe - OperationType CreateHostFile - Server <LU_Server_Location>
Make sure that the syntax matches one of the following examples:
<IDrive>\Program Files\NetBackup\Bin\LU_Registration.exe -OperationType CreateHostFile -Server http://<webserver>/<LiveUpdatePackageDirectory>/
<IDrive>\Program Files\NetBackup\Bin\LU_Registration.exe -OperationType CreateHostFile -Server \\<fileshare>\<LiveUpdatePackageDirectory>\
This example illustrates if you have mapped the L:\ drive to the network share that contains LiveUpdate packages:
<IDrive>\Program Files\NetBackup\Bin\LU_Registration.exe -OperationType CreateHostFile -Server L:\<LiveUpdatePackageDirectory>\
For file shares, enter the directory path in the same format as you would to execute a "copy" command from the Windows Run dialog box.
To locally configure a UNIX host
- Use a text editor to modify
/usr/openv/netbackup/nblu.confas shown in the following examples:
nblu.conffile is created the first time that you run nbliveup. If
nblu.confdoes not yet exist on the system, you must create it by using the following command:
cp /usr/openv/netbackup/nblu.conf.template /usr/openv/netbackup/nblu.conf