If the client has an (back end) interface on the same subnet as the
media server, since backups are not session based, the client should, by
default, without any additional intervention, use that interface to talk
to the media server, even if the request goes to the front end of the
client.

If the back-end interface isn't on the same subnet as the media server,
a static route should take care of it.

Restores would require the media server talking to the backend interface
of the client in order to use that interface, however.

Paul

> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu 
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Ed Wilts
> Sent: March 2, 2006 12:57 PM
> To: Martin, Jonathan (Contractor)
> Cc: Nemanja Stosic; veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Nemanja-Backup network problem
> 
> 
> Yuck.  We use DNS exclusively.  We register two names for the hosts -
> one on the front-side network and one for the backup network. 
>  For those
> cases where the server doesn't have backup network interface but is
> expected to have one soon, we'll add a CNAME entry for the backup
> network DNS entry to point to the front side, but in general we don't
> like doing that.  DNS and the appropriately configured routing tables
> are all we need.
> 
> This works like a charm and the right thing happens.