I don't recall the original email and can't seem to find it anywhere... but I'm not sure I understand the problem, unless your network doesn't allow access between the VLANs? You should be able to route a client on one VLAN to another. If you don't want to do this for efficiency reasons (router becomes a bottleneck), just create a dummy /32 ip address for each SD (eg 172.16.254.1/32, 172.16.254.2/32, 172.16.254.3/32) on the loopback device, and add a route on each client to each SD (or use dynamic routing), eg: ip route add 172.16.254.1/32 via link_local_ip_address_of_sd1 ip route add 172.16.254.2/32 via link_local_ip_address_of_sd2 Then the director just has to tell each client the dummy ip address of the sd and it will find the best way there.
If that doesn't make sense (quite likely, I badly need sleep :), then I'll draw a diagram. Failing that, could you give some more details, specifically: . IP addresses of routers between vlans (and a summary of firewall rules between them that would prevent access) . IP address(es) of director . IP addresses of storage daemons . IP addresses of clients Make up the IP address details if you don't want to use the actual ones for security reasons. If all this was in the original email (which I can't find), could you just forward it to me off-list? James > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:bacula-users- > [EMAIL PROTECTED] On Behalf Of Mindaugas > Sent: Thursday, 11 May 2006 22:36 > To: bacula-users@lists.sourceforge.net > Subject: [Bacula-users] Multihomed backup server > > > Hello, > > Few days ago I wrote about the problem but I would like to discuss about > possible solutions. > > Description: > I have backup server which is connected to multiple VLANs and has > several > IP addresses. Director sends to clients Address from Storage resource > where > clients has to connect. Problem is that clients from different VLANs has > to > connect to different IP addresses. > > In 1.36 to resolve the issue I had several Storage resources (one per > VLAN) > and clients were using Address from the coresponding Storage resource. > But in 1.38 support for multiple autochangers was added and this method > no > longer works. > > Kern suggested to put something like "bacula-sd" in Address field and > then > put appropriate IP address in /etc/hosts file of the client. I modified my > configuration in this way and everything works. But I do not like such > solution > because it decentralizes management. What if IP of my SD will change? Also > I > do > not have full control of the hosts file of several Windows machines - > domain > controller is overwriting hosts file and I cannot change this behaviour. > > Maybe some other way exists? > > If not I would like to suggest adding SDAddress (and maybe SDPort?) > configuration > settings to Job resource. Then I could control where job (and client) > should > connect > for backup. > > Thanks, > > Mindaugas > > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
