About LiveUpdate file share servers and LiveUpdate policies with Windows and UNIX clients
If your LiveUpdate Server Location is configured as a file share, you can still include both Windows and UNIX clients in your LiveUpdate policy. NetBackup then attempts to map the specified location to the appropriate path name syntax on the target platform.
The following examples describe how this process works:
Example 1: Windows path name In a LiveUpdate policy, you specify a Windows path name for the LiveUpdate Server Location. For example:
| If LiveUpdate packages have been downloaded correctly from the NetBackup support site, this example works as is for Windows clients in the policy. For UNIX clients in the policy, nbliveup converts that path as follows:
Notice that |
Example 2: UNIX path name In a LiveUpdate policy, you specify a UNIX path name for the LiveUpdate Server Location. For example:
| If LiveUpdate packages have been downloaded correctly from the NetBackup support site, this example works as is for UNIX clients in the policy. For Windows clients in the policy, nbliveup converts that path as follows: \\fileserver\LUServer\7.0.4 Notice that |
If this conversion does not work, Veritas recommends that you create separate LiveUpdate policies for your Windows and UNIX clients.