On Tue, Mar 9, 2010 at 9:02 AM, Bob Hetzel <beh AT case DOT edu> wrote:
> 3 things that have given me grief due to the windows FD stopping or being
> unresponsive (but still mysteriously running)...
> a) buggy network driver--in one case I was able to update the driver to fix.
> b) bad network switch or network port
> c) infection with a virus/malware that was using up the "max tcp
> connections". Check the event log for that error.
> d) regex in the fileset had a bug but that's been fixed around bacula
> version 2.5 or so. Along the way I learned that regex was slower to
> process than wilddir and wildfile so I stopped using it for windows
> filesets anyway.
>
> In all cases these issues caused the windows FD to stop during a backup, so
> I hope this helps but if not, you may have to turn on debugging in the FD
> and cross your fingers that it happens and logs what went wrong.
>
> Bob
Yeah, I think I'll need to turn on debugging.
Unfortunately for me, the FD dies or stops running before the backups
even kick off. If I manually restart (after notification that it
errored), then kick off another backup for the client, it seems to run
without issues. I'm using the latest version of the Windows client. No
infections are on the machine for malware or virus and network seems
to be good. I don't think it's anything with bacula though, my only
guess is the Intuit software on the machine that might be causing
issues.
Thanks,
-Drew
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
