Bob,

Unfortunately Networker doesnt allow you the flexibility that DNS does. 
Networker needs to resolve one IP address to one name. End of story. I have 
struggled with this aspect a couple of times - especially in larger multihomed 
networks and environments.

You can get by performance issues by teaming up NIC's or using "Server Network 
Interface" field in the client setup to specify which network is used. 
Obviously normal name resolution rules still aply. Or specifying multiple NIC's 
but ensuring that these resolve to a unique name (I have a client system that 
has 8 gigabit network cards in it working fine using this principle).

If you get in a scenario where one name resolves to multiple IP's you might get 
the backup working sometimes but you will most definately have some RPC errors, 
or unrecognised client, or similar IP related problems somewhere if not the 
whole time.

Hope this clarifies it a bit better.

Regards,
Riaan

-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]On Behalf Of Bob Payne
Sent: Tuesday, November 09, 2004 1:11 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Clients with two NICs


Hi Networkers,
Networker Server: Solaris 8, Networker 7.1.1
I'm trying to understand an aspect of Networker.
We have two W2K clients (Networker 7.1.1) each with two NICs.Hostnames are
resolved through DNS. DNS has an ip address for each NIC where there are
two.
These two clients have  a D: and an E: drive plus the usual SYSTEM STATE,
SYSTEM FILES, SYSTEM DB.
When a backup starts for a client with two NICs, how is it decided which
NIC is used?Are both used? Is it possible that different NICs are used for
each save-set?
Can anyone out there throw any light on this?
Thanks

Bob

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.788 / Virus Database: 533 - Release Date: 11/1/04
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.788 / Virus Database: 533 - Release Date: 11/1/04
 

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=