Hello, thank you that you finally admit there is a bug.
As when we first discovered the bug, we could reproduce it almost on every test. I will provide feedback if this is fixed in 2.2.3 once it is released. Just one question - is the bug in dir or sd? I am asking that to know what to update and if it would be sufficient to do that at the server only, not the clients. For the tests we are using a spare server set up as bacula server backing up our live servers - that way it is OK, if there is no need to update the clients for those tests. So the questions is - is it OK to have dir and sd 2.2.3 and 2.1.28 for the clients to successfully test the bug fix? Regards. Monday, September 10, 2007, 12:46:24 AM: KS> Hello, KS> I regret to have to announce that there is a rather serious bug in Bacula. KS> Bacula bug #935 reports that during a restore, a large number of files are KS> missing and thus not restored. This is really quite surprising because we KS> have a fairly extensive regression test suite that explicitly tests for this KS> kind of problem many times. KS> Despite our testing, there is indeed a bug in Bacula that has the following KS> characteristics: KS> 1. It happens only when multiple simultaneous Jobs are run (regardless of KS> whether or not data spooling is enabled). KS> 2. It has only been observed on disk based backup, but not on tape. KS> 3. Under the right circumstances (timing), it could and probably does happen KS> on tape backups. KS> 4. It seems to be timing dependent, and requires multiple clients to KS> reproduce. KS> 5. Analysis indicates that it happens most often when the clients are slow KS> (e.g. doing Incremental backups). KS> 6. It has been verified to exist in versions 2.0.x and 2.2.x. KS> 7. It should also be in version 1.38, but could not be reproduced in testing, KS> perhaps due to timing considerations or the fact that the test FD daemons KS> were version 2.2.2. KS> 8. The data is correctly stored on the Volume, but incorrect index (JobMedia) KS> records are stored in the database. (the JobMedia record generated during KS> the Volume change contains the index of the new Volume rather than the KS> previous Volume). KS> 9. You can prevent the problem from occurring by either turning off multiple KS> simultaneous Jobs or by ensuring that while running multiple simultaneous KS> Jobs that those Jobs do not span Volumes. E.g. you could manually mark KS> Volumes as full when they are sufficiently large. KS> 10. If you are not running multiple simultaneous Jobs, you will not be KS> affected by this bug. KS> 11. If you are running multiple simultaneous Jobs to tapes, I believe there is KS> a reasonable probability that this problem could show up when Jobs are split KS> across tapes. KS> 12. If you are running multiple simultaneous Jobs to disks, I believe there is KS> a high probability that this problem will show up when Jobs are split across KS> disks Volumes. KS> I have uploaded patches to bug #935 (bugs.bacula.org) that will correct KS> version 2.2.0, 2.2.1, and 2.2.2. The patch has been tested only on version KS> 2.2.2 and passes all regression tests as well as the specific test that KS> reproduced the problem. KS> After a little more testing, I plan to release version 2.2.3 probably on KS> Monday the 10th or Tuesday. KS> At this time, I do not have a patch for 2.0.x versions, and unless there is KS> some really compelling reason to create one, I would prefer not -- it would KS> not be a huge effort to back port the patch, but it would require rather KS> extensive testing. Though it is hard to make a specific recommendation, I KS> believe that it probably will be the wisest and simplest to either patch KS> version 2.2.x if that is what you are currently running, or upgrade to KS> version 2.2.3 when it is released. KS> It *could* be possible to manually correct the bad JobMedia records in the KS> catalog, but it is not something that I would personally recommend. If you KS> *really* need data off an old tape, I recommend first trying a restore. KS> Sometime tomorrow, I will provide more detailed instructions on several ways KS> how to correct the problem if necessary -- all of them are somewhat painful. KS> Kern KS> ------------------------------------------------------------------------- KS> This SF.net email is sponsored by: Microsoft KS> Defy all challenges. Microsoft(R) Visual Studio 2005. KS> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ KS> _______________________________________________ KS> Bacula-users mailing list KS> Bacula-users@lists.sourceforge.net KS> https://lists.sourceforge.net/lists/listinfo/bacula-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
