I wish that the setup you describe would work, but it CAN'T.
 
The backup job will assign a port on the NIC that receives the request.  If
the master (10.1.1.1) sends the request to systemA (10.1.1.10) to use the
storage unit on mediaA (10.1.1.2), the data will travel over the NIC that
the master sent the data on.  If the master (10.1.1.1) sent the request to
systemA (10.1.1.10) to backup using the storage unit on mediaA-b (backup nic
10.2.1.2) it would never work.  
 
If you use the "required interface" setting on the client, then the request
MUST come in to the client on that interface and the data can ONLY go out on
that interface.
 



Bobby Williams 
2205 Peterson Drive 
Chattanooga, Tennessee  37421 
423-296-8200 

 

  _____  

From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Whelan,
Patrick
Sent: Friday, December 01, 2006 5:45 AM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] Backup networks



Does anyone have a similar setup?

Separate backup network from clients in one location to media servers in
same location, but the master server can only see the clients and media
servers on the public network. This causes 41 errors, we have come up with
different work arounds but all of them are hooey. Is there a clean solution
to this dilemma? I know the real solution is to have one backup network for
everything, but this is politically impossible at the moment. Any
suggestions welcomed.

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.

... Als sie mich holten,
gab es keinen mehr, der protestieren konnte 

-- Martin Niem?ller



****************************************************************************
*********
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/20061201/fbe047e7/attachment.html