Example 1 - client with multiple network interfaces

The NetBackup client name setting on both the client and server is fred_nb.

When client fred starts a backup, restore, or list operation, the request goes out on the fred_nb interface and over the backup network. The operation assumes that fred and the network are set up to do so. If this configuration is not in place, fred can send out the request on the fred interface and over the regular network. The server receives the request from client fred_nb with host name fred and refuses it because the host and the client names do not match.

One solution is to set Use specified network interface on fred to fred_nb. All backup, restore, and list requests use the fred_nb interface. The server receives requests from client fred_nb with host name fred_nb and everything works as intended.

Another solution is to set up the master server to allow redirected restores for client fred. Redirected restores allow the server to accept the request, but leaves NetBackup traffic on the regular network.

Example 2 - server with multiple network interfaces

The server list on all NetBackup servers and clients have an entry for barney_nb.

When barney connects to a client for a backup, the request goes out on the barney_nb interface and over the backup network. The operation assumes that barney and the network are set up to do so. If this configuration is not in place, barney can send out the request on the barney interface and over the regular network. The client now receives the request from barney rather than barney_nb and refuses it as coming from an invalid server.

One solution is to set Use specified network interface on barney to barney_nb. Now, when barney connects to a client, the connection is always through the barney_nb interface and everything works as intended.

Another solution is to add an entry for barney to the server list on the client. The client now accepts requests from barney, but NetBackup traffic continues on the regular network.