On Sunday 02 December 2007 16:40, Ralf Gross wrote: > Kern Sibbald schrieb: > > On Sunday 02 December 2007 11:07, Ralf Gross wrote: > > > Ralf Gross schrieb: > > > > [...] > > > > This changes makes the scratch pool useless, because bacula does not > > > > prune volumes during the 'status dir' command, but still decides if a > > > > volume of the scratch pool will be used. This way a volume of the > > > > scrach pool will be moved to the Differential (or Full) pool all the > > > > time the command is issued... > > > > > > ...and no other volume with state Append, Recycle etc. is available in > > > that specific pool. E.g. for each new weekly Differential backup a new > > > scratch pool volume will be used if the status dir command is issued > > > before. > > > > > > Just to make it a bit clearer. > > > > I *think* the patch I attached to your bug report #1019 will fix these > > problems. > > Thanks, I'll apply the patch tomorrow and report what happens next - this > might take one or two weeks. > > Can you confirm that the Recycling Algorithm is still valid after the > changes in 2.2.x?
Yes when the patch is applied. > > http://www.bacula.org/rel-manual/Automatic_Volume_Recycling.html > [...] > 5. Prune volumes applying Volume retention period (Volumes with VolStatus > Full, Used, or Append are pruned). > 6. Search the Pool for a Volume with VolStatus=Purged > 7. If InChanger was set, go back to the first step above, but this second > time, ignore the InChanger flag in step 2. > 8. Attempt to create a new Volume if automatic labeling enabled If Python > is enabled, a Python NewVolume even is generated before the Label Format > check is used. > 9. If a Pool named "Scratch" exists, search for a Volume and if found move > it to the current Pool for the Job and use it. > [...] > > > For me step 5 and 9 are most important, because the volume retention times > of my pools are set to expire just a couple of days before the next backup > happens. > > So I'm depending on step 5 is done before step 9. If it's done during > 'status dir' or at backup time is not that important. The status command > was just a convenient way to trigger pruning before the next backup happed > and see that everything was ok (retention time error or not enough volumes > in a pool). If you want to trigger pruning, you will need to use the prune command. Then you can check with the status command. Kern > > > Ralf > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Bacula-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bacula-devel ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
