I have added a Winders server to our Bacula backup jobs. It is located
in a DMZ. Our web server (running on SLES 10) is also in the DMZ and we
have been backing it up with Bacula for a month now. I created rules in
the firewall for the Windows server that are identical to those for the
web server, just with a different IP address. The Bacula client is
installed and the bacula-fd.conf file has been edited. The bacula-fd
service starts automatically.
Here is the bacula-fd.conf:
#
# Default Bacula File Daemon Configuration file
#
# For Bacula release 1.38.10 (08 June 2006) -- cygwin
1.5.18(0.132/4/2)
#
# There is not much to change here except perhaps the
# File daemon Name to
#
#
# List Directors who are permitted to contact this File daemon
#
Director {
Name = lbackup-dir
Password = "filedaemon"
}
#
# "Global" File daemon configuration specifications
#
FileDaemon { # this is me
Name = ArcIMS-fd
FDport = 9102 # where we listen for the director
WorkingDirectory = c:/bacula/working
Pid Directory = c:/bacula/working
}
# Send all messages except skipped files back to Director
Messages {
Name = Standard
director = lbackup-dir = all, !skipped
}
This is identical to the conf file on systems that work, except for the
filedaemon name.
When I run a backup job for this server, the job runs for two hours
(almost exactly), with the tape drive indicating data being written,
then terminates with an error. The job summary looks like this:
29-Jan 18:07 lbackup-dir: ArcIMS.2007-01-29_16.07.46 Fatal error:
Network error with FD during Backup: ERR=Connection reset by peer
29-Jan 18:07 lbackup-dir: ArcIMS.2007-01-29_16.07.46 Fatal error: No
Job status returned from FD.
29-Jan 18:07 lbackup-dir: ArcIMS.2007-01-29_16.07.46 Error: Bacula
1.36.3 (22Apr05): 29-Jan-2007 18:07:51
JobId: 1462
Job: ArcIMS.2007-01-29_16.07.46
Backup Level: Full (upgraded from Differential)
Client: ArcIMS-fd
FileSet: "ArcIMS" 2007-01-19 15:50:02
Pool: "Weekend"
Storage: "Internal"
Start time: 29-Jan-2007 16:07:48
End time: 29-Jan-2007 18:07:51
FD Files Written: 0
SD Files Written: 13,339
FD Bytes Written: 0
SD Bytes Written: 9,959,280,437
Rate: 0.0 KB/s
Software Compression: None
Volume name(s): Week_2D
Volume Session Id: 3
Volume Session Time: 1170100801
Last Volume Bytes: 19,948,336,363
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: Error
SD termination status: OK
Termination: *** Backup Error ***
Status dir looks like this:
Terminated Jobs:
JobId Level Files Bytes Status Finished Name
========================================================================
[other jobs]
1462 Full 0 0 Error 29-Jan-07 18:07 ArcIMS
I am puzzled why there are 13,339 SD files and 9,959,280,437 bytes
written, but zero FD files and bytes written.
--
Tks n rgds,
Richard White CNE6
Network Engineer
Mason County, Washington
360-427-5501
[EMAIL PROTECTED]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
