Hello, On 20.10.2005 00:42, Michael Dauer wrote:
Hello, I use backup strategy of the sample config (3 level). But it does only work if there is no interuption. Because the selection of the proper media is done by RetensionPeriod and VolumeUseDuration. If I specify a VolumeUseDuration of 6 for inc level for each day of the week except sunday and it happens the the client is not connect during the time of a planned backup the sixed usage happens the next monday and media is switched not before tuesday.
Somehow, I would need more information on your setup here... assuming you've got one volume for incremental jobs, and it can be used 6 days, the "next monday" would require a new tape.
If the client is not connected on sunday (day for diff backup) the diff level is kept out completely and if the inc level is configured to keep the media of up to 2 weeks then it may happen that a necessary inc level media is reused before a new diff level backup was made. And all this just because the client was not connected on one certain day.
Well, setting up the retention times is your responsibility :-) Seriously, I always try to keep more than one backup generation around, and not only to avoid the problems you describe.
I think it would be much better that a missed scheduled backup would be done at the next schedule time even when there was lower level planned then.
Wouldn't the directive "Rerun failed levels" not do what you want?
And it would be better if I could specify that the run of a higher level backup triggers the media change for the lower levels.
Well, you could do something with scripts. Though I think that your problems arise mainly when you try to work with very few volumes - if you've got enough volumes, you don't have to worry much about which voume is recycled when.
Since I think my scenario is quite common I hope that there is already a way to configure it properly which I am not awere of, yet. Please tell me!
I at least prefer to have Bacula working the way it does and I try not to interfere with it too much. I found that Bacula manages volumes quite good, but lacks when it comes to things requested often in the last few months: Automatic unloading and marking for archival, and, as you point out, a setting to say "mark current incremental (differential) volume as used on differential (full) backup". (Although I suspect that wouldb't work reasonably when you have many clients, many filesets, many pools and many schedules.)
Arno
Regards, Mick ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
-- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
