214
NetBackup System Administrator’s Guide - Windows NT Server
5
Example 2
This example explains how the
altnames
file can provide restore capabilities
to clients that do not use their own host name when connecting to the
NetBackup server.
By default, the NetBackup client name of the requesting client must match the
peername used in the connection to the NetBackup server. When the
NetBackup client name is the host name for the client and the host name
matches the peername (normal case), this requirement is met.
However, problems arise when clients connect to multiple Ethernets or connect
to the NetBackup server through a gateway. Consider the configuration on
Figure 11.
Figure 11 Example Restore from Token Ring Client
In this example network, restore requests coming from the clients, alf, cheech,
and chong, are routed through the TCP gateway. Because the gateway uses its
own peername rather than the client host names for connection to the
NetBackup server, NetBackup refused the requests. This means that clients
cannot restore even their own files.
To correct this situation proceed as follows:
1. Determine the peername of the gateway:
a. Attempt a restore from the client in question. In this example, the request
fails with an error message similar to the following:
client is not validated to use the server
b. Examine the NetBackup problems report and identify the peername used
on the request. Entries in the report will be similar to:
01/29/93 08:25:02 bpserver - request from invalid
TCP
Token
Ring
NetBackup
Server
Gateway
cheech
alf
chong
NetBackup 3.2 System Administrator's Guide for Windows NT
NetBackup 3.2 System Administrator's Guide for Windows NT
