Hello, I am using bacula storage and director version 2.0.3 on freebsd 6.1. with bacula-fd 2.0.3 on windows 2003 SP2. I have spooling turned up and concurrent jobs set to 150 on the SD and 20 on the clients. I am testing a single windows client and running jobs serially. Every job that I attempt to run on the windows client errors out within the first minute after spooling begins. All machines are on a local switched lan with no intervening routers or firewalls. I played with heartbeat settings, network buffers, toggled encryption and VSS but nothing seems to help. Just over a megabyte is spooled to the SD before the job fails with the following errors. I've tried this job over 20 times with various configuration changes and I always get the same result.
Fatal error: ../../filed/backup.c:873 Network send error to SD. ERR=Input/output error Error: ../../lib/bnet.c:406 Write error sending len to Storage daemon:sd.example.com:9103: ERR=Input/output error I am using the win32 client from sourceforge. "fd.example.com-fd" 2.0.3 (06Mar07) Linux,Cross-compile,Win32 FD Files Written: 14 SD Files Written: 0 FD Bytes Written: 1,330,789 (1.330 MB) SD Bytes Written: 0 (0 B) Rate: 7.0 KB/s Software Compression: 52.3 % VSS: no Encryption: yes The files being backed up are the bacula client (C:/Program Files/Bacula). An interesting data point is that the job errors out but the SD still lists active data and attribute spooling related to the failed job(s). Subsequent failed job attempts accumulate as active jobs on the SD. The last two lines of status storage command after 2 failed jobs lists active jobs despite the fact that no jobs are running from the point of view of the director and the client. Data spooling: 2 active jobs, 2,387,388 bytes; 0 total jobs, 2,387,388 max bytes/job. Attr spooling: 2 active jobs, 0 bytes; 0 total jobs, 0 max bytes. The spool directory has the spool files and bacula's home directory has the attrib spool files, too. Stopping and starting the SD fixes the perception of active jobs in the status storage console command. The data arrives at the SD, but the windows FD stops sending almost as soon as it starts. The 2.0.3 linux clients I have do not exhibit this behavior. I have searched the archives and have found both old and new reports of this error but no one seems to discuss it beyond the point of seeing the errors. I'm not sure where to go from here. I have attempted to turn on debugging and tracing for the FD and the SD, but I cannot find the trace file for the FD or the SD. Please help me. Thank you. Adam ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
