Kern --
Thanks for the advice. I can't count how many times this machine has
been rebooted :o It is scheduled for upgrade to XP but won't happen for
another month or so. And I'd like to have a complete backup before the
upgrade.
Thanks again.
Karl
Kern Sibbald wrote:
I'd reboot the machine to be sure, but it is also possible, even though we
tried, that we no longer properly support Win98 -- it isn't so easy with all
the new VSS code we have added. I personally no longer have a Win98 system
on which I can test. Perhaps Thorsten would have some comments ...
If you can afford the upgrade, I would *highly* recommend upgrading to WinXP
Home (or Pro) both of which are much better than Win98 in terms of stability.
On Tuesday 08 November 2005 00:35, Karl Cunningham wrote:
Hi --
Upgraded to 1.38.0 and am having problems with one client. This is a
Win98 machine that worked well with Bacula version 1.36.3. This machine
is backed up daily and did not show these errors until upgrading to 1.38.0.
When doing a full backup it is generating hundreds of errors such as:
07-Nov 11:22 mech-fd: mech-job.2005-11-07_11.22.12 Error: Read error on
file c:/ACCESS/DATA/Snfile.mdb. ERR=The handle is invalid.
07-Nov 11:23 mech-fd: mech-job.2005-11-07_11.22.12 Error: Read error on
file c:/Agent/Temp/00005AB5.DAT. ERR=The handle is invalid.
07-Nov 11:23 mech-fd: mech-job.2005-11-07_11.22.12 Error: Read error on
file c:/BORLANDC/LIB/CWM.LIB. ERR=The handle is invalid.
07-Nov 11:23 mech-fd: mech-job.2005-11-07_11.22.12 Error: Read error on
file c:/BORLANDC/BIN/TDW.EXE. ERR=The handle is invalid.
These only occur in a small percentage of files beging backed up, maybe
1% or so. And the particular files that show these errors are different
for different backup jobs. Eventually the jobs fails with:
07-Nov 12:06 mech-fd: mech-job.2005-11-07_11.22.12 Fatal error: Too many
errors.
Also, doing a client status from the director to the file daemon is
intermittant. It works perhaps 60% of the time but otherwise says it
can't connect. Again, this was not a problem with 1.36.3.
I ran the file daemon with -d 500 but didn't see any problems. I am
going to try a higher debug level.
The network seems to be working ok. Transferred about 1GB of data from
this client without error. Other Win98 machines don't show these
problems, so it would indicate a problem with the client rather than
Bacula. But this client worked fine before upgrading Bacula too.
Questions --- Has anyone else seen this? Is there a way to change the
number of errors the FD can encounter before the job fails?
Thanks in advance for any help. This client is an important one for us
to back up.
Karl Cunningham
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
