We do it like this..
All DNS points to the front net Ips (172.17.x.x in your case) and we put
local host files including the backup server (master,media) and clients
Ips on the Back End (192.168.8.x) on each machine. That forces those
machines to use the back end nic for backups.
Using DNS is tricky, because you want DNS to point to yoru front end for
normal applications. If you don't need DNS for your front end, then
that is certainly a first for me.
Master Server Config
FE
IP: 172.17.x.x
Subnet: 255.255.0.0
GW: 172.17.x.x
DNS: 172.17.x.x, 172.17.x.x
BE
IP: 192.168.8.x
Mask: 255.255.255.0
HOSTS FILE C:\WINDOWS\SYSTEM32\DRIVERS\ETC\HOSTS
INCLUDE!!!!
BACKENDIP MASTER SERVER NAME
BACKENDIP Media Server
BCKENDIP CLIENT1
BACKENDIP CLIENT2
Hopefully that helps you out, as that's the general format we're using
here. You can implement DNS on the back end too but its much more
tricky. I'd start with this and see where you go.
Finally, NO if you ping any of the Netbackup Server or Clients from one
another you should get their BACK END Ips, not their front end.
-Jonathan
-----Original Message-----
From: Nemanja Stosic [mailto:nemanja AT finsoft.co DOT yu]
Sent: Thursday, March 02, 2006 11:39 AM
To: Martin, Jonathan (Contractor)
Subject: RE: [Veritas-bu] Nemanja-Backup network problem
Hi thanks for quick reply
We have 2 clients and one server
Clients normal network (172.17.x.x, subnetmask and df gtw), backup
network (192.168.8.x, with subnet mask, with dns without df gtw )
Server has the same network configuration. All dns entry are ok,
nslookup works fine. But when I connect to client from netbackup admin
console, the ip address of the client is 172.17.x.x not 192.168.8.x is
this normal, because the server properties shows the address 192.168.8.x
not 172.17.x.x
Thanks in advance
Nemanja
-----Original Message-----
From: Martin, Jonathan (Contractor) [mailto:JMARTI05 AT intersil DOT com]
Sent: Thursday, March 02, 2006 3:38 PM
To: Nemanja Stosic; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Nemanja-Backup network problem
Windows is probably confusing the routing of the front and back end NICs
and this performance issue is probably not limited to Netbackup but
probably other networked applications as well.
We found that Windows 2003 is much more picky about network routing than
2000. For example we use a 10.10.1.0 network for the routable front end
and 10.10.2.0 for our backend (non-routable.) Even if the system is
correctly setup to find the host its trying to backup on the back-end
(correct IP / Host lookup) if your default gateway is on the front end,
its going to route that traffic through the front end, even though it is
trying to talk to a system on the back end. With multiple default
gateways both assigned the metric 1 its basically a toss up which
interface it will use (which really complicates the matter!)
1 - make sure you only have 1 default gateway setup on the front end!!
(I'm assuming your backend isn't routed.)
2 - Make sure your systems all resolve correctly, either by using "sudo"
DNS (aka Server1 and Server1-be DNS Entries) or by using hosts files to
ENSURE the systems are talking on the backend.
3 - run a "route add" command on your multi-homed servers and force them
to route traffic from the backend to the backend.
Usually steps 1 and 2 work, and I've only had to add route statements
for DMZ servers with firewall issues and special routing involved to
complicate the matter.
Good luck!
-Jonathan
-----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 Nemanja
Stosic
Sent: Thursday, March 02, 2006 9:18 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Nemanja-Backup network problem
Hi to all,
I have I big problem, we have I backup network, the platform is win2003
server and Netbackup ver 6. All computers are in AD, and have extra
nic's, for backup network. We did it all like Veritas suggested for
backup network to work, like the right DNS entry, every client is
configured to use prefered network device, but the backup up is realy
slow, it takes for 5 min just to access the client from Netbackup admin
console. Any ideas what can be wrong or something like that
Thanks
Nemanja Stosic
System Administrator
BEG Finsoft
Kosovska 51
11000 Belgrade
Yugoslavia
Tel: +381 (11) 3305789
+381 (64) 2290249
http://www.finsoft.co.yu
A member of the Global Consulting Alliance http://www.pass-gca.com
*********************************************************
The information in this E-mail is confidential. If you are not the
intended recipient please notify the sender immediately and delete this
E-mail without reading, using or disseminating the information contained
in it.
Although Finsoft Ltd believes this E-mail and any attachments are free
of any virus or other defect which may affect a computer, it is the
responsibility of the recipient to ensure that it is virus free and
Finsoft Ltd does not accept any responsibility for any loss or damage
arising in anyway from its use.
*********************************************************
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
