> -----Original Message-----
> From: bacula-users-bounces AT lists.sourceforge DOT net [mailto:bacula-users-
> bounces AT lists.sourceforge DOT net] On Behalf Of Mario Constanti
> Sent: Monday, August 18, 2008 9:44 AM
> To: bacula-users AT lists.sourceforge DOT net
> Subject: [Bacula-users] WG: Bacula DIR, SD and CONSOLE are in different
> LANs than FD
>
> Here are the Logfiles and some outputs from the server:
> Fileserver:
>
> fileserver ~ # netstat -tulpen
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address
> State User Inode PID/Program name
> tcp 0 0 172.17.10.5:9102 0.0.0.0:*
> LISTEN 0 66584 15255/bacula-fd
>
> ---> bacula-fd.conf on the fileserver
> Director {
> Name = backup
> Address = 172.23.10.3
> Password = "thecorrectpassword"
> }
> FileDaemon { # this is me
> Name = fileserver # hier stand costor drin -> falsch
> FDport = 9102 # where we listen for the director
> WorkingDirectory = /var/lib/bacula
> Pid Directory = /var/run
> FDAddress = 172.17.10.5
> }
>
> # Send all messages except skipped files back to Director
> Messages {
> Name = Standard
> director = backup = all, !skipped
> }
>
> #######################################################################
> #######################################################################
> ##########
>
> #######################################################################
> #####
>
> Backup-Server:
>
> backupsystem bacula # netstat -tulpen
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address
> State User Inode PID/Program name
> tcp 0 0 127.0.0.1:3306 0.0.0.0:*
> LISTEN 60 7155 6752/mysqld
> tcp 0 0 172.23.10.3:9101 0.0.0.0:*
> LISTEN 0 11969 9353/bacula-dir
> tcp 0 0 172.23.10.3:9102 0.0.0.0:*
> LISTEN 0 11926 9341/bacula-fd
> tcp 0 0 172.23.10.3:9103 0.0.0.0:*
> LISTEN 0 12002 9364/bacula-sd
>
> bacula-dir.conf
>
> Director {
> Name = backup
> DIRport = 9101
> QueryFile = "/usr/libexec/bacula/query.sql"
> WorkingDirectory = "/var/lib/bacula"
> PidDirectory = "/var/run"
> Maximum Concurrent Jobs = 4
> Password = "thecorrectpassword"
> Messages = Standard
> DirAddress = 172.23.10.3
> }
>
> Job {
> Name = " fileserverBackup"
> Type = Backup
> Client= fileserver
> FileSet=" fileserver Set"
> Schedule = "WeeklyCycle"
> Storage = File
> Messages = Standard
> Pool = Default
> Where = /tmp/bacula-restores
> }
>
> Client {
> Name = fileserver
> Address = 172.17.10.5
> FDPort = 9102
> Catalog = MyCatalog
> Password = "thecorrectpassword"
> File Retention = 60d # 30 days
> Job Retention = 180d # six months
> AutoPrune = yes # Prune expired Jobs/Files
> }
>
>
> So i think, the configuration is OK, because the only thing, that
> changed, were the IP-Addresses on the Backup and Fileserver-System. But
> telnet and ping works correctly.
> And there is no firewall!!!!
>
> Does anybody have a running configuration with different lans / vlans?
> Can this be a bug in bacula?
>
> Mario
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: John Drescher [mailto:drescherjm AT gmail DOT com]
> Gesendet: Montag, 18. August 2008 15:28
> An: Mario Constanti; bacula-users
> Betreff: Re: [Bacula-users] Bacula DIR, SD and CONSOLE are in different
> LANs than FD
>
> On Mon, Aug 18, 2008 at 9:14 AM, Mario Constanti
> <Mario.Constanti AT x-cellent DOT com> wrote:
> > Hello,
> >
> >
> >
> > we use Bacula in our company since four years.
> >
> > The Backup-Server with CONSOLE, SD, DIR are in the same network like
> > the other Servers with the FD which are backuped.
> >
> >
> >
> > Last weekend we optimized our it infastructure.
> >
> > So we create a VLAN for the Backup-Server and many other VLANs
> > for the other Servers.
> >
> > The Network works correct, because i can ping from the Backup-Server
> every
> >
> > System, which should be backuped. I can also make "telnet fileserver
> 9102",
> > it works.
> >
> > I can start "bconsole" and run a "status client=fileserver", which
> also
> > works.
> >
> >
> >
> > From the other Servers, for example the Fileserver i can ping to the
> > Backup-Server and also can start
> > "telnet backupsystem 9103", "telnet backupsystem 9101", which works
> > correctly.
> >
> >
> >
> > But when i start a Backupjob, i got this Error-Message:
> >
> >
> >
> > 18-Aug 00:25 fileserver: fileserverBackup.2008-08-18_01.05.01
> Warning:
> > bnet.c:864 Could not connect to Storage daemon on backup:9103. ERR=No
> route
> > to host
> >
> > Retrying ...
> >
> >
> >
> > The Backupsystem have following config:
> >
> > IP-Address: 172.23.10.3
> >
> > Netmask: 255.255.255.0
> >
> > VLAN: 104
> >
> >
> >
> > The Fileserver have following config:
> >
> > IP-Address: 172.17.10.5
> >
> > Netmask: 255.255.255.0
> >
> > VLAN: 110
> >
> >
> >
> > Why don't this work?
> >
>
> The machine with the filedaemon needs to connect directly to the
> storage daemon on what ever ip address is listed in your
> bacula-dir.conf. Is there any reason the filedaemon could not contact
> the storage daemon?
>
> John
>
> -----------------------------------------------------------------------
> --
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
This is not a problem with Bacula based on what you listed in your first email.
This is a problem where you have put the same TCP/IP subnet on two different
VLAN's. You list the IP addresses as:
The Backupsystem have following config:
IP-Address: 172.23.10.3
Netmask: 255.255.255.0
VLAN: 104
The Fileserver have following config:
IP-Address: 172.17.10.5
Netmask: 255.255.255.0
VLAN: 110
You can see that they are on the same subnet (172.23.10.x), yet they are on two
different VLAN's. Unless these VLAN's are bridged these two hosts will not be
able to communicate with each other. If they are bridged then you are
defeating the purpose of using VLAN's. Also, even if they were on separate
VLAN's and separate subnets, the two hosts would still need a router connecting
the two VLAN's to be able to communicate.
Thanks,
Bob Duman
Senior Systems Engineer
Cleantech Group LLC
2250 Genoa Business Park Dr
Suite 130
Brighton, MI 48114
http://cleantech.com
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
