Troubleshooting guide

General Test and Troubleshooting Procedures
44 NetBackup Troubleshooting Guide - UNIX
First, we examine the configuration of the router system. The NetBackup class client list
shows this system as mars because that is the name of the interface to the master server.
There is no special configuration to note other than the client name setting. This name
must be set to mars, because this is the name that the master server recognizes.
The second client, pluto, is also configured no differently than if it were in the same
network as the master server. Assuming that all the standard networking files (for
example, hosts, NIS, DNS, WINS, and routing tables) are set up correctly, all the required
network connections can be made.
There would be a problem, however, with restoring files from pluto if the mars/meteor
system was a type of router that hides the name of the originating host when it routes
requests between the two networks. For example, a router between an Ethernet and a
token ring network exhibits this behavior.
To illustrate what occurs, assume that pluto is on FDDI (token ring) and the server is on
Ethernet. If a user on pluto starts a restore, the router could use the name of its network
interface to pluto (meteor) as the peername when it forwards the request to the server. The
server interprets the request as coming from a host named meteor and does not allow the
restore because meteor is not in the client list.
To resolve this problem, the administrator creates altnames directory on the master
server and adds a file for meteor to that directory.
On a Windows NT/2000 NetBackup server, the file path is:
install_path\netbackup\db\altnames\meteor
On a UNIX NetBackup server, the file path is:
/usr/openv/netbackup/db/altnames/meteor
Then, the administrator adds the following line to this file:
pluto
The master server now recognizes, as legitimate, any restore requests that show a
peername of meteor and client name of pluto. Refer to the NetBackup System
Administrator’s Guide - UNIX for more information on altnames configuration.
Regardless of the type of router, the configuration for the media server, saturn, is the same
as in example 2. If a media server is involved in a backup or restore for pluto, the master
server provides the correct peername and client name for the media server to use in
establishing connections.
UNIX Example 5: Server Connects to Multiple Networks
The network in this example (see the next figure) shows a NetBackup server
(jupter/meteor) that has two Ethernet connections and clients in both networks. The
server’s hostname is mars on one network and meteor on the other.