|
We're running two subnets here, one for data and one for
backup communication. When we upgraded to 6.0 I thoroughly tested this and
found the following.
DNS/HOSTS defines the IP address that the server will try
to contact (via bpcd) Your server will then follow whatever routing it has
internally to find that IP address. The "REQUIRED_INTERFACE" (Unix /
bp.conf) or "Use specified network interface" (Windows, Client Properties) will
bypass routing and force a client to use that interface for backup communication
/ traffic. To figure out which interface your client will use, you really
need to consider where backups initiate.
My configuration:
Public / Routable Fontend for client communication with
whatever
Private / Non-routable "Backend" for backup
traffic.
Master/Medias have 1 IP on the Public and 1 IP on the NBU
"Backend"
Some clients have 1 IP on the Public and 1 IP on the NBU
"Backend"
Some client have 1 IP on the Public
(only)
All servers' primary IPS are public and we've got DNS
pointing to that. example: master.intersil.com (frontend / public IP) so
do the clients - client1.intersil.com. We've also given the backend /
netbackup network interfaces DNS (Host/A) entires - master.be.intersil.com /
client.be.intersil.com.
You can hardcode your master server's jobs to use the FQDN
(client1.be.intersil.com) which will cause the master to use the
"backend". Alternately, I've configured my dns lookup to use
be.intersil.com before intersil.com
Therefore: master scheduled backup of client1 --> master
queries dns for client1 --> finds client1.be.intersil.com --> IP is on the
"backend" --> master uses the "backend" interface to contact the
client
since other clients don't have backend IPs (and thus no
backend IP DNS Entry.) it goes something like:
master scheduled backup of client2 --> master queries
dns for client2 --> does not find client2.be.intersil.com --> finds
client2.intersil.com --> IP is on the frontend --> master uses
the frontend interface to contact the client (per routing
rules.)
The caveat here is in your client configuration. Your
client1.be.intersil.com (above) is going to receive a backup request from
master.be.intersil.com - which it won't allow. You've got to make sure
that
Before I got here we used hosts files to accomplish the
same feat (except no be.intersil.com extentions.) The backup servers just
thought client1's IP was the backend IP.
Let me know if that helps you out. I've got similar
things worked out for DMZ scenarios (internal/external) and even a backup
environment with split routing which is intresting.
-Jonathan
There is a paremeter you can put in
the bp.conf file that is supposed to force the data through a NIC
I think it is called REQUIRED_INTERFACE =
<ip address or dns name> I have always found that
netbackup like to use DNS for all name resolution., so I
would not use the ip address.
This is
documented for UNIX systems, I don't know if windows has a similar option.
I am not sure
if it works with
master initiated backups. Probably what you would need to do is assign
different host name
to your alternate
interface and change the client name in the policy on the master to refer to
the
DNS name you have given for that
NIC. In that case you probably do not need the REQUIRED_INTERFACE
entry
in the bp,.conf file.
Hopefully this
is not too confusing. I have not personally tried it, just a
suggestion..
=============================
Carl Stehman
IT Distributed Services
Team
Pepco Holdings, Inc.
202-331-6619
Pager
301-765-2703
ckstehman AT pepco DOT com
"Esson, Paul"
<Paul.Esson AT Redstor DOT com>
Sent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu
02/29/2008 01:40 PM
|
|
To
| <veritas-bu AT mailman.eng.auburn DOT edu>
|
|
cc
|
|
|
Subject
| [Veritas-bu] Media Server with
multiple NICS |
|
Folks,
Is anyone out there using Media Servers with multiple NICs
on separate networks? I am trying to understand how to force clients to
use specific interfaces on the Media Server when sending backup data or
receiving restore data. Do I need to create multiple storage unit and
Media Server entries to be able to target the clients through the policy?
Or am I on the wrong track altogether?
NBU 6.5 Solaris 10 Master and
Media Servers – Media Servers have 4 NICs and clients are on multiple
subnets.
Regards,
Paul Esson
_______________________________________________
Veritas-bu maillist
- Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This
Email message and any attachment may contain information that is proprietary,
legally privileged, confidential and/or subject to copyright belonging to Pepco
Holdings, Inc. or its affiliates ("PHI"). This Email is intended solely for the
use of the person(s) to which it is addressed. If you are not an intended
recipient, or the employee or agent responsible for delivery of this Email to
the intended recipient(s), you are hereby notified that any dissemination,
distribution or copying of this Email is strictly prohibited. If you have
received this message in error, please immediately notify the sender and
permanently delete this Email and any copies. PHI policies expressly prohibit
employees from making defamatory or offensive statements and infringing any
copyright or any other legal right by Email communication. PHI will not accept
any liability in respect of such communications.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
| 