Example of host name and service entries on UNIX server that connects to multiple networks
The following illustration shows a NetBackup server with two Ethernet connections and clients in both networks. The server host name is jupiter on one and meteor on the other.
Consider the following about Figure: UNIX server connects to multiple networks:
All applicable network configuration must be updated to reflect the NetBackup information. For example, this information could include the
/etc/hostsfile and NIS, and DNS (if used).
This example illustrates a UNIX server that connects to multiple networks. The NetBackup policy client list specifies jupiter as the client name for the primary server. The list can show either jupiter or meteor but not both.
The NetBackup server list on the primary server has entries for both jupiter and meteor. The reason for both is that when the server does a backup, it uses the name that is associated with the client it backs up. For example, it uses the meteor interface when it backs up pluto and the jupiter interface when it backs up mars. The first server entry (primary server name) is jupiter because that is the name used to back up the client on the primary server.
The NetBackup server list for the other computers also has entries for both the jupiter and the meteor interfaces. This setup is recommended to keep the server entries the same on all clients and servers in the configuration. It would be adequate to list only the primary-server name for the local network interface to the client computer or media server. (For example, list meteor for pluto.)
For the network that is shown, the only configurations that are required are the differences for the policy client list and the server list. If all the standard networking files (hosts, WINS, NIS, DNS, and routing tables) are set up correctly, all required network connections can be made.