Master/Media Server with 2 NICs

[Urdle]

Hello,

I currently try to make NetBackup work with 2 network interface cards on a server (a master & media; another server that is just media with the same 2 NICS is also in project)

Here's some informations about what I did and the network :
- All servers and clients are Windows 2000.
- The 2nd card was added after Netbackup installation.
- The 2 interfaces have a different DNS name.
- I indicated the 2nd DNS Name as an alternate master server on all the clients.

For the moment, even after several reboots, all the backup network trafic still goes to the 1st NIC.

I can't find any option to indicated that Netbackup must do load balancing, and I can't find how to make any client use the 2nd dns name as its media server.

How must I do ?

Is DNS round robin is the only solution ? (I just don't consider this solution as a graceful solution, as if the NIC has a problem, I'll have to ask a DNS change, instead of changing something on the netbackup server)

Do I also have to specify the 2nd DNS name as an alternate media server and Netbackup will do load balancing alone ?
(As it's production servers, I can't do many tests or try blindly, so I would like to be sure it will work)

Regards,
Michael Genay

 

[dazzagp]

Do you have the two nics setup for load balancing/etherchannel? You may have to set the nics up as teamed from within the OS.
Sorry if I've misunderstood your question I had a similer problem some time ago

 

[Urdle]

as I remember, load balancing/etherchannel work only for outgoing trafic (i.e. from the media to the client)

Am I wrong ?

 

[mfearnuk]

Required Network Interface - set in client properties

Specifies the network interface that NetBackup uses when connecting to another NetBackup client or server. A NetBackup client or server can have more than one network
interface. To force NetBackup connections to be made on a specific network interface, use this entry to specify the network host name of that interface. By default, the operating system determines the one to use.

Example 1 - Client with multiple network interfaces.
Assume a NetBackup client with two network interfaces:


One network interface is for the regular network. The host name for the regular interface is fred.

One network interface is for the backup network The host name for the backup interface is fred_nb.
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. This assumes that fred and the network are set up to do so. If this configuration is not in place, fred can send the request out 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 client names do not
match.

One way to solve this problem is to set up the master server to allow redirected restores
for client fred. This allows the server to accept the request, but leaves NetBackup traffic on
the regular network.
A better solution is to set Required Interface on fred to fred_nb. Now, 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.
Example 2 - Server with multiple network interfaces.
Assume a NetBackup server with two network interfaces:

One network interface is for the regular network. The host name for the regular
interface is barney.

One network interface is for the backup network The host name for the backup
interface is barney_nb.

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 ideally goes out on the barney_nb interface and over the backup network. This assumes that barney and the network are set up to do so. If this configuration is not in place, barney can send the request out 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 way to solve this problem 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. A better solution is to set Required 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.

 

[Urdle]

Hi,

Unfortunatly, none of the solutions you're proposing me suit my problem.

Concerning dazzag's answer, load balancing would only work only for output (server -> client) bandwidth; and EtherChannel (which would load balance input bandwidth too) needs adapted network equipment, that I don't have.

Concerning mfearnuk's answer, REQUIRED INTERFACE will not work because :
- Only the master/media has 2 network interfaces
- I want to distribute the backup trafic between the 2 interfaces; I don't want to separate media/master trafic from backup trafic... my problem is to "feed" a big robot, and I don't have enough bandwidth to do so (looks like I never told about that, which is THE point... I'm an idiot)
- The 2 Interfaces are on the same subnetwork.

(Isn't there an integrated Netbackup solution for load balancing ? LTO2 drives are now sold, and they can write 3 times faster than a 100Mbps network can deliver... such situations will soon be quite common)

If anyone has some ideas, please respond

Thank you

 

[timmy90210]

PCI-X GIG NIC

 

[Urdle]

timmy, if what you're doing is giving me a model of network card EtherChannel compliant, be aware that we currently have EtherChannel compliant NIC, but the problem is on the switch side

thank you all again for your answers

 

[pruanju]

Hello Urdle, I have the same problem but with Sun Enterprise 10000.

The server has two network interface (one for drives backups and other for disk backups), the two in the same subnet.

I don't know if you have the solution for the problem, if you have more information, please send me it.

 

[Urdle]

unfortunately, I found no solution for my issue.

Too summarize, There are two workarounds (But I couldn't apply any because of logistic issue)

- Use EtherChannel, with will distribute bandwidth through the 2 network adapters
- Use a Gigabit network interface (copper or fiber. Copper gigabit now works well and is not so expensive)

both workarounds will require to have compliant NIC and Switch/Router