Hi,
Am 04.11.22 um 11:50 schrieb Burkhard Linke:
An example would be keeping daily incrementals for the last two month,
weekly merged incrementals for the next 4 month, and monthly
incrementals for the next 6 months. This would cover a whole year,
result in (1+6+4*4+2*7=) 83 backup datasets per job, assuming 4 weeks
and 30 days per month. The virtual full job merging the full and oldest
incremental set can be scheduled to run at certain times of the year
with low activity.
That sounds feasible and like something that AI should be able to do at
some point in the future. I'm just not (yet) sure how to get this
working as a general approach that we could ship in core.
We would implement this scheme as an external script and disable the
standard consolidate job. Does the python binding allow to specify which
jobs should be merged in a virtual full job, similar to the code in the
consolidate job?
Yes and no.
What the core does is that it runs a virtualfull explicitly stating the
jobids. Basically like running 'run job=your-job level=VirtualFull
jobid=1,2,3 accurate=yes'. This will produce a backup with the level of
the first job mentioned (in your case an Incremental).
If the job has AlwaysIncremental and AlwaysIncerementalJobRetention
configured, it will also prune the jobs that were consolidated.
So you can implement that if (and that's the hard part) you can reliably
figure out which jobids should be consolidated together.
If you can come up with a good solution for that, maybe you could share
it and maybe we can implement it in core then.
Best Regards,
Andreas
--
Andreas Rogge andreas.ro...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221-630693-86
http://www.bareos.com
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz
--
You received this message because you are subscribed to the Google Groups
"bareos-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bareos-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-devel/8ac9ee76-ab6f-d90d-3f4b-76a26f5ae449%40bareos.com.