On Thursday 11 December 2008 13:10:14 you wrote:
> On Thu, 11 Dec 2008 09:43:47 +0000, Piotr Gbyliczek wrote:
> > We have one director,
> > three storages and lot of clients. Clients are in different networks, so
> > we need to use different IP to connect from client to storage and
> > different IP to connect from director to storage.
>
> Why is that? In a properly routed network that should not be necessary.
> Can you describe a bit more what your network structure looks like and why
> it would require using different IP addresses for the same storage daemon?

We have three cabinets in datacentre with three networks. In each cab we have 
storage, to avoid traffic between cabs, as datacentre will charge us for it. 
Because we have networks mixed up between cabs, we have situation like that : 

storage1 : 192.168.10.10
client1 : 192.168.10.20
client2 : 192.168.20.20

Setting up backup storage with ip causes second client  to go to it's gateway 
and back to cab to hit that ip, which gives us traffic being counted on edge 
router. Because it is not our part of network, we can't do much with routing 
there. So, we have secondary ip on storage1, storage setup in director with 
name instead of ip, and views to answer with storage ip in same network as 
asking client. We unfortunately not in position to change any IP on machines. 
Hope this is clear enough.

> > Only issue could be that
> > bind server is bacula storage and director, so it may be under load at
> > night. Is that possible, I mean can it be bind not responding to clients
> > because storage traffic is hammering server ??
>
> Possible. But in that case, your problem isn't caused by the different
> IP addresses and would occur the same way if you always use the same IP
> address for the same SD.

It is not. Problem here is I believe that dns is on same server as storage, 
and this service is timing out only during night, because storage client 
traffic is causing dns not responsive at the time of query.

> I don't know. But even if there is, IMHO a better solution would be to
> (a) put the name service on a different server or (b) install nscd (name
> service caching daemon) on the clients.

(a) is where I think solution lies. 


-- 
Piotr Gbyliczek
Second Line Support 
Forlinux LTD



------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users