Thanks, Mark --

I had been hoping to avoid assigning a name to the interface;
It adds another wrinkle to the installation of client software
on systems not sharing the subnet.  I'll see if it'll work with
just having the name in the client's server configuration first
and then add the name into the NB master and media servers only
if it's absolutely necessary.


--kathy

Kathryn Hemness
kfhemness AT ucdavis DOT edu



On Tue, 10 Feb 2004, Mark Steel wrote:

> Date: Tue, 10 Feb 2004 10:35:36 +0000 (GMT)
> From: Mark Steel <mark AT steelfamily DOT org>
> To: Kathryn Hemness <kfhemness AT ucdavis DOT edu>
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] NB Servers with 2 network interfaces
>
> Hi
>
> It really depends on your name resolution. if the 2nd interface returns
> the same host name, no issues. if its a different name, then you need to
> add that name to the client properties servers list so that it recognises
> the server as valid.
>
> regards
> mark
>
>
> On Mon, 9 Feb 2004, Kathryn Hemness wrote:
>
> > Greetings -
> >
> > I've added a second network interface to my NetBackup Master and Media 
> > servers
> > to backup some Windows systems on a common network.  Is there something
> > I can do to make NB server requests to these clients recognized as
> > requests from the NB master?  I only want this second network
> > interface to be used for backups and restores for these specific
> > clients.
> >
> > My Master and Media servers are Solaris 8 running on Sun E450's.
> >
> >
> > --kathy
> >
> > ===============================================================================
> > Kathryn Hemness
> > kfhemness AT ucdavis DOT edu
> >
> >
> > _______________________________________________
> > Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
>
>