If you don't want to use the GUI, you can do it from the command line
using bpsetconfig (see manual for details).

 

Regards,

 

Patrick Whelan 
NetBackup Specialist 
Architect & Engineering 
+44 20 7863 5243 

Of all the things I've lost, I miss my mind the most! - Unknown 

There are only 10 kinds of people on earth - those who understand binary

and those who don't. 

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Martin,
Jonathan (Contractor)
Sent: 22 September 2006 14:32
To: veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Multiple-Nics

 

Does anyone know what the equivalent registry entry is for
REQUIRED_INTERFACE for Windows?  Or is this strictly a UNIX/Linux thing?

 

I've been searching Google and support.veritas.com all morning now with
no luck.

 

-Jonathan

 

________________________________

From: Scott Jacobson [mailto:SJACOBSO at novell.com] 
Sent: Monday, September 11, 2006 6:21 PM
To: Martin, Jonathan (Contractor); veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Multiple-Nics

As mentioned from an earlier thread, I'm not sure of your use/need for
the multiple interfaces.

 

If some or all these multiple interfaces are available for teaming or
bonding, I would do that, and use the REQUIRED_INTERFACE for desired
data stream (ip addr)

 

-sj

>>> "Martin, Jonathan (Contractor)" <JMARTI05 at intersil.com> 9/11/2006
1:42 PM >>>

Ok... so three new media servers with 4 nics each are headed my way in
the next few weeks.  That's 12 interfaces I've got to worry about!
According to the NBU Performance Planning & Tuning Guide I should create
DNS entries for each interface, and add all interfaces to each server's
bp.conf (or registry in windows.)  I'm going to get all these values
setup and ready to go before the hardware even arrives.

 

backup1 (IP1)

backup1-neta (IP2)

backup1-netb (IP3)

backup1-netc (IP4)

backup2 (IP1)

backup2-neta (IP2)

backup2-netb (IP3)

backup2-netc (IP4)

backup3 (IP1)

backup3-neta (IP2)

backup3-netb (IP3)

backup3-netc (IP4)

 

So the servers will all talk to each other across the various nics (by
looking up the server name) but how do clients know which IP to use?
Many of those IPs are going to be on a non-routed "backend" network,
which several clients will not have access to.  How does the Master /
Media server know which nic to use to communicate with the client?
Further, how do I tell my jobs which IP to use?!  For example, if I have
6 nics on 3 servers in the "back end" will NBU automatically local
balance between them?  Perhaps I should enable teaming?  Any input on
how this done properly would be appreciated.  Unfortunately the HOSTS
file lookup method we use now is unacceptable (and dumb) so I'll have to
make this work properly.

 

-Jonathan

 



*************************************************************************************
The message is intended for the named addressee only and may not be disclosed 
to or used by anyone else, nor may it be copied in any way. 

The contents of this message and its attachments are confidential and may also 
be subject to legal privilege.  If you are not the named addressee and/or have 
received this message in error, please advise us by e-mailing security at 
colt.net and delete the message and any attachments without retaining any 
copies. 

Internet communications are not secure and COLT does not accept responsibility 
for this message, its contents nor responsibility for any viruses. 

No contracts can be created or varied on behalf of COLT Telecommunications, its 
subsidiaries or affiliates ("COLT") and any other party by email Communications 
unless expressly agreed in writing with such other party.  

Please note that incoming emails will be automatically scanned to eliminate 
potential viruses and unsolicited promotional emails. For more information 
refer to www.colt.net or contact us on +44(0)20 7390 3900.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060922/a05cd578/attachment.html