Troubleshooting guide

Chapter 2, Troubleshooting Procedures 55
General Test and Troubleshooting Procedures
Windows NT/2000 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.
The first thing to note about this configuration is that the NetBackup class client list
specifies jupiter as the client name for the master server. The list could show either jupiter
or meteor but not both.
Another important item to note is the configuration of the NetBackup server list.
The NetBackup server list on the master server has entries for both jupiter and meteor.
The reason for both names is that when the server does a backup, it uses the name
associated with the client it is backing up. For example, it uses the meteor interface when
backing up pluto and the jupiter interface when backing up mars. The current server entry
(master server name) is jupiter because that is the name used to back up the client on the
master server.
The NetBackup server list for the other systems also have entries for both the jupiter and
meteor interfaces. This is recommended in order to keep the server entries the same on all
clients and servers in the configuration. It would be adequate to list only the master-server
name for the local network interface to the client system or media server (for example,
meteor for pluto).
For the network shown, the differences mentioned for the class client list and the server
list is the only unique configuration required. Assuming that all the standard networking
files (for example, the hosts file, WINS, DNS, and routing tables) are set up correctly, all
required network connections can be made.
If the master server system is a type of router that hides the name of the originating host
when routing requests between networks, you see the same type of restore problem
discussed in example 4. For example, if pluto were on FDDI (token ring), the master
server would use meteor as the peername when it forwarded the request to NetBackup.
NetBackup would then interpret the request as coming from a host named meteor, which
was not in the client list, and the restore would fail.
The solution, in this case, is also identical to that discussed in “Windows NT/2000
Example 4: Clients in Multiple Networks” on page 53.