Piotr Gbyliczek <p...@forlinux.co.uk> wrote: > I'm having problem with configuring bacula properly. 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.
I assume that NAT is not part of the picture? If I understand your topology correctly, it is analagous to my own where my SD is multi-homed to take advantage of the switched 1GB backbone without saturating the router that would normally join those segments. Rather than messing around with different DNS views, I just defined multiple 'A' records and it works like a charm; clients that are on the same network as one of the SD network interfaces connect to the closest SD interface (ie: same network). (I've got a packet filter on the router mentioned above that blocks bacula-related traffic, and the jobs run correctly, so I know that the traffic is getting routed correctly.) If you have clients that are not on the same network as one of the SD interfaces (or if you have clients with dumb resolvers that won't do result record sorting based on connected interfaces), then you may be able to tell your nameserver to sort the records. (For example, see the 'sortlist' statement for ISC BIND 9.) Devin ------------------------------------------------------------------------------ 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
