We're using client-bk as the client name.  In our environment we have multiple 
firewall-segregated subnets, none of which are particularly different 
address-wise (i.e. not 10.x vs 192.x) but rather 10.x.y.z vs 10.x.z.z).  So the 
master/media (although multi-homed to allow backup of some subnets without 
going through a firewall) talks to the this client over its (the media 
server's) public IP.

Looks like Solaris is handling the routing back so although the request comes 
in to the client on the backup interface, Solaris routes it back over the most 
appropriate interface according to the routing table, which in this instance is 
the public interface.

cheers, Phil

> -----Original Message-----
> From: rcarlisle [mailto:rcarlisle AT serverwarecorp DOT com] 
> Sent: 05 June 2007 15:01
> To: Weber, Philip; VERITAS-BU AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] REQUIRED_INTERFACE Problem?
> 
> 
>  
> REQUIRED_INTERFACE is only valid for client initiated 
> backups.  So, it is
> very important to use in multiple nic environments with database agent
> backups since, technically, they are client initiated.  With 
> non-database
> scheduled backup, the client will respond back over whatever 
> interface the
> request was initiated on.  Are you using client-bk or 
> client-pub as the
> client name in the policy?  If you specify client-bk as the 
> client name, the
> media server will go out the backup nic.  However, if the 
> media server name
> is associated with the public nic, all meta data will still go out the
> public interface.
> 
>  
>  
> Reneé Carlisle 
> ServerWare Corporation
> 
> 
> -----Original Message-----
> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Weber,
> Philip
> Sent: Tuesday, June 05, 2007 9:31 AM
> To: VERITAS-BU AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] REQUIRED_INTERFACE Problem?
> 
> Master/Media Solaris9 NBU 5.1 MP6.
> Client Solaris10 NBU 5.1 MP6.
> 
> Client has two network interfaces client-pub & client-bk.
> 
> I want all backup traffic to go via the client-bk interface, 
> but unless
> I add a network route for the backup server subnet over the client's
> backup interface, backups fail with a 41.  I was under the impression
> that REQUIRED_INTERFACE was all I should need.
> 
> e.g. with bp.conf "CLIENT_NAME = client-bk" and "REQUIRED_INTERFACE =
> client-bk", but with no specific network route, client-initiated
> backup/restore requests appear to go OK.  When I snoop the various
> network interfaces during a server-initiated backup attempt, I see the
> media server talking to client-bk (and getting no response), client-bk
> sees incoming requests from media server, client (interface) sees
> outgoing requests from client-bk to the media server... so 
> responses are
> going back over the wrong interface (and never getting there due to
> firewalls).
> 
> Add the route "route add net media-server-subnet.0 
> subnet-defaultrouter"
> and backups work fine.
> 
> So I guess REQUIRED_INTERFACE only works for traffic 
> initiated from the
> client, and the OS handles routing of reply information?
> 
> Phil Weber
> Business Technology (Egg)
> Storage Technical Services - Senior UNIX Technologist
> Phone: 01384 26 4136
> Mobile: 07748 333503
> 
> 
> -----------------------------------------
> Egg is a trading name of the Egg group of companies which includes:
> Egg plc (reg no 2448340), Egg Financial Intermediation Ltd (reg no
> 3828289), and Egg Banking plc (reg no 2999842). Egg Banking plc and
> Egg Financial Intermediation Ltd are authorised and regulated by
> the Financial Services Authority (FSA) and are entered in the FSA
> register under numbers 205621 and 309551 respectively. These
> members of the Egg group are registered in England and Wales.
> Registered office: Citigroup Centre, Canada Square, London E14 5LB.
> 
> This e-mail is confidential and for use by the addressee only. If
> you are not the intended recipient of this e-mail and have received
> it in error, please return the message to the sender by replying to
> it and then delete it from your mailbox. Internet e-mails are not
> necessarily secure. The Egg group of companies do not accept
> responsibility for changes made to this message after it was sent.
> 
> 
> Whilst all reasonable care has been taken to avoid the transmission
> of viruses, it is the responsibility of the recipient to ensure
> that the onward transmission, opening or use of this message and
> any attachments will not adversely affect its systems or data. No
> responsibility is accepted by the Egg group of companies in this
> regard and the recipient should carry out such virus and other
> checks as it considers appropriate.
> 
> This communication does not create or modify any contract.
> 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
> 
> 

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu