|
Hi all, I'm running the latest bacula, and everything works fine when I backup on the LAN. However, I need to backup a server on the DMZ. This is what I did; 1) Install the file daemon on the dmzserver. 2) opened port 9101-9103 in the firewall for traffic going from DMZ, to the LAN. 3) configured both the FD and DIR. When I start a job, it seems to run fine. After a while (about 580 MB) it loses the connection. Here's what I get in Console: ________________________________________________________ 13-Feb 15:25 beagle-dir: dmzsvr.2006-02-13_15.20.49 Fatal error: Network error with FD during Backup: ERR=Connection reset by peer 13-Feb 15:26 beagle-dir: dmzsvr.2006-02-13_15.20.49 Fatal error: No Job status returned from FD. 13-Feb 15:26 beagle-dir: dmzsvr.2006-02-13_15.20.49 Error: Bacula 1.38.5 (18Jan06): 13-Feb-2006 15:26:22 JobId: 182 Job: dmzserver.2006-02-13_15.20.49 Backup Level: Full (upgraded from Differential) Client: "dmzsvr-fd" i686-redhat-linux-gnu,redhat,Enterprise 3.0 FileSet: "dmzsvr" 2006-02-13 10:02:46 Pool: "NAS-Files" Storage: "FileNAS" Scheduled time: 13-Feb-2006 15:20:37 Start time: 13-Feb-2006 15:20:51 End time: 13-Feb-2006 15:26:22 Priority: 10 FD Files Written: 0 SD Files Written: 0 FD Bytes Written: 0 SD Bytes Written: 0 Rate: 0.0 KB/s Software Compression: None Volume name(s): Volume Session Id: 6 Volume Session Time: 1139503850 Last Volume Bytes: 1,111,287,193 Non-fatal FD errors: 0 SD Errors: 0 FD termination status: Error SD termination status: Running Termination: *** Backup Error *** ________________________________________________________________ Note that it says SD Bytes written = 0. If I cancel the job somewhere, this is > 0 (Depending on how long I wait several hundreds of MB's.) This space also gets allocated on the storage, but only in the event of a timely cancellation. Looks to me that it loses connection when the job either completes or reaches another threshold. I've tried to configure a heartbeat Interval = 5 minutes on the FD, but to no avial. Any help very much appreciated! Many thanks, Ger Apeldoorn. __________________________________________________________ |
