Re: [Bacula-users] bacula backuping on wrong network interface

2010-03-17 Thread Laurent HENRY (EHESS/CRI)
Hello, SD, FD, and networks are fine. I think i am getting it ! Putting the private adresse in the client config is not enough. You have to put the private FQDN of the bacula server in the Storage config for the client coming back on the good NIC Storage { Name = Autochangeur # Do not use

Re: [Bacula-users] bacula backuping on wrong network interface

2010-03-16 Thread Carlo Filippetto
Enable the firewall, so only the internal IP is allowed to accede that server on those ports Ciao --- Carlo Filippetto 2010/3/16 Radosław Korzeniewski : > Hello, > > Check if SD is listening on private network address, using telnet, for > example - check from client (FD) machine. Next, check if

Re: [Bacula-users] bacula backuping on wrong network interface

2010-03-16 Thread Radosław Korzeniewski
Hello, Check if SD is listening on private network address, using telnet, for example - check from client (FD) machine. Next, check if Bacula SD configuration uses private address (on private network) instead of public. And finally check communication from FD to SD using traceroute and private SD

[Bacula-users] bacula backuping on wrong network interface

2010-03-16 Thread Laurent HENRY (EHESS/CRI)
Hello all, I have a problem to understandhow to configure bacula to make backups on different network interfaces. My config: - backuped server (server1) with 2 network cards, one for internet traffic (public IP), one for backups (private IP). - bacula server (2.4 on debian) with 2 network