Multiple ethernet adapters, how to bind backup to a particular one?

Henk,
the way NetWorker works is this ( as per my knowledge ). Suppose your server has two addresses and two names, i.e. bcksrv and bcksrv_gb. Your client has bckclnt and bckclnt_gb.
If you want to use the gigabit network you have to:
- define bckclnt_gb as the client into NetWorker
- set "server network interface" to bcksrv_gb into the client bckclnt_gb definition.

There is also a technical bulletin available about this setup. Take a look into the bulletins list into the EMC site and you'll find it for sure.

Hoping this helps

Pierpa

You can have only one entry in the /etc/hosts file of the client for the NIC that you want to use.

Aliases should also have only the desired IP & hostname and the client name should be the desired hostname. Server Network Interface also needs to be for the desired NIC only.

NW does not support 2 NICs we were told. We experienced lots os problems before we disabled one of the NICs. Since then no similar problem occurred.
Disable one of the NICs if you can.

Was this on server or client Habib?

Both the server and the clients had two 1 GB Broadcom NICs. We use the SAN configuration via HBA port and FC switch for the backup.

I my case it's a client which has the two ethernet adapters and I need them both.

I Think I have found the solution for my problem. Both ip-addresses were automatically registered in DNS under the same host name.

I have disabled the ip-address on the 100 Mbps ethernet adapter from automatically registering in DNS and removed the entry in DNS. Then I created a new DNS host entry with a different hostname for this ip-address so NetWorker still would be able to resolve the second ip-address. In order to determine if this solves my problem I will have to wait until tonight when the scheduled backup will run.

You can also use a little dirty hack to separate Backup Traffic from Public LAN. You'll have to edit hosts file on client and server.

On client side append to hosts file

server-fqdn server-hostname

On Server append to hosts file

client-fqdn client-hostname

After that you'll have to set "Server network interface" in NW client's ressource to server backup-ip as well.

Whoever told you that is stupid. I even don't remember system I worked with that didn't have multiple NICs - it is all matter of configuration.

I agree, however as odd as it seemed, at the time I was fairly new to NW ( still am in comparison to lots of you out there ). We just accepted it as bible.

So, what sort of configuration would you have applied for 14 Servers ( Windows platform) all with multiple NICs. ? Thanks

Hrvoje,

No, I have no LAN backup running. All backups are SAN configured using HBA ports and FC switches. All 14 servers are DSN except for the NW server with SN.

It depends... are some of those or all dedicated for backup LAN?

LAN backup is something different than a dedicated backup LAN. Are you using one interface for public traffic and one for admin/backup traffic? Even a DSN is sending index data to NW server so you'll need some kind of ethernet connection between DSNs and NW server anyway.

In that case data connection is local while only LAN traffic is metadata using management interface (primary one). You might change that too with configuration, but given that metadata traffic is small I rarely see valid reason for that.