Hello Dirk, Bugs are more easy to track and to fix with mantis tool http://bugs.bacula.org
Le Thursday 05 March 2009 15:00:15 Dirk Bartley, vous avez écrit : > Greeting > > I'm using the head development version in my live active work server to > get a better chance of solving some issues in bat. Now however I'm > having some issues that I hoping can be solved on the list. > > Revision: 8498 > > My recollection is that this particular issue started after updating the > storage daemon. My storage daemon runs on my workstation. > > So I have been getting lots of failures with the last couple of nights > backups. Failures with tape (hardware or software) can desynchronize File count between the volume and the catalog. In this case, bacula will put the Volume in Error state until you fix it (which is a good idea if the volume is dirty or broken). > This morning I tried to reproduce in a simple way and > succeded. I started with a tape that was freshly purged and relabeled. > Started a job which would use the main server as the client as well. It > started along backing up to tape just fine. Then I started a job which > uses a different file daemon and backing up on the tape drive just > stopped. You describe the most common case, i don't see the problem. Is your first job OK ? or you've got an error somewhere ? The job ouput is welcome. > All efforts to set the tape back to append, Which one ? What is the error message ? "update volume" command permits to change the volume status or the file count easily. > umount and mount the drive > to get the jobs going to tape again have failed. > > > Here is the log from the second job. > > Log records for job 7910 > 2009-03-05 08:36:30 > srvalum3-dir > Using Device "LTO" > > Start Backup JobId 7910, Job=UPSJob.2009-03-05_08.36.27.05 > 2009-03-05 08:36:58 > srvalum2-sd > Volume "LTO_WDay_004_" previously written, moving to end of data. > 2009-03-05 08:37:14 > srvalum2-sd > Marking Volume "LTO_WDay_004_" in Error in Catalog. > > Error: Bacula cannot write on tape Volume "LTO_WDay_004_" because: > The number of files mismatch! Volume=1 Catalog=0 > 2009-03-05 08:37:28 > srvalum2-sd > Job UPSJob.2009-03-05_08.36.27.05 waiting. Cannot find any appendable > volumes. > Please use the "label" command to create a new Volume for: > Storage: "LTO" (/dev/nst1) > Pool: LTO_TueThu > Media type: LTO > > After that job is started, the tape in the medialist goes from > status=append to status=error. This is normal if bacula founds a difference between the catalog and the volume. For example, if you shutdown the storage daemon during a job, you will have this behavior > Here are my config files that I think my be pertainent. > http://www.schupan.com/baculaconfs/bacula-dir.conf > http://www.schupan.com/baculaconfs/bacula-sd.conf > > As always thank you very much in advance for any assistance. Let me > know if there is any information I can provide. The support page on www.bacula.org provides many information on how to report a problem. Bye > Dirk > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
