This is a bit more complicated.  The actual TCP connection that carries the
backup DATA is always initiated from the media server (which is picked 
according to your class/storage unit definition) to the client.  Therefore
the local routing table on the media server decides which interface it'll
use to contact the client.  Most of the Unices will use that particular
interface's address's IP address as the source IP address for that
connection.  

If the both the media server and the client are multi homed, and you want
the backup to flow on a particular subnet, you can either use an interface
specific name of the client in the client name definition, or you can have
the media server use its local host file first for name resolution (like
/etc/nsswtich.conf on Solaris, file before dns) and force
the media server to think the client being on a particular subnet.

--Mike


> From veritas-bu-admin AT mailman.eng.auburn DOT edu  Tue Mar 20 16:43:20 2001
> 
> This question has probably been answered before but I thought I would
> pose it again.
> 
> In my environment where I use DNS, how do I ensure that a client's
> backups and restores go over the correct subnet when my master server
> has multiple network interfaces?
> 
> Thanks in advance
> 
> 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 


-- 
Mike Wei       Collective Technologies, a Pencom Company
Email: wei AT colltech DOT com