On 9/4/17 4:02 AM, Julian Poß wrote:
Thank you a lot! :)
You bet.
I think i understand your setup. But just to make sure, let me try to wrap it up in my own words. Your jobs are basically all running with "incremental" job defs, using the "always-incr" pool for incrementals and "consolidated" for the full backups. Then you consolidate every day a new full to the "consolidated" pool. Saturdays, you will run a virtual full, from "consolidated" and "always-incr" pool, and store it in the "offsite" pool, which does mean it will be written to tapes.
Yup, that is close enough. We started out with the normal full, differential, and incremental approach and with the migration to always incremental the names did wander from the doc samples.
The consolidation doesn't always end up re-building a full, there are knobs to limit how often fulls are consolidated to reduce IO. Check out section 23 of the Bareos docs.
So, if i am not mistaken in my explanation above, i just need to configure a jobdef for my tapejob, so it will be doing a virtual full, using the "full" and "incremental" pool (since i sticked to the defaults), and store it in my tape pool, where my tapes will belong to.
Yup, that approach works.
However, i am wondering why you have 15 storage devices configured, but at the same time you only allow 10 concurrent jobs. Is it just performance tweaking, or is this actually recommended?
I seemed to run into contention with 10 on-disk storage devices and 10 concurrent jobs. Although that was probably back on Bareos 15.x.
My goal is to have one large full backup file/volume every monday, and one big incremental for each day the rest of the week. I will always keep two full chains and as soon as the third is complete, i will automatically prune the oldest, based on "maximum volumes" and "volume retention". Any thoughts (for tweaking) and warning for my plans are much appreciated. :)
That will work. We've been quite happy with using always incremental backups of the clients since for some of our clients the full backup was a noticeable load. You could consider not doing full backups (other than the very first backup of a new client) at all and using always incremental and consolidation. With your virtual full approach for off-site you are kind of doing that already.
Were you able to run multiple storage devices in earlier versions, too? Maybe using 16.2.4 is the issue here for me.
Yes, there were no problems that I encountered with multiple storage devices going back to 15.2.
Thanks again Doug, for sharing your experience with such a newbie :) I also attached all (imo) important configuration files, just in case you want to have a look aswell.
You are welcome. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
