Hi Jürgen,
Am 24.12.21 um 09:58 schrieb 'Jürgen Echter' via bareos-users:
> I just wanted to try out the new mariadb-plugin, i never used any plugin
> yet, and i got the following message in my incremental job:
> python-fd-mod: start_backup_job: Accurate backup not allowed please
> disable in Job
>
> As i'm using always incremental scheme is this not going together with
> the mariabackup plugin?
the problem with AI and plugins (especially the database plugins) is
that we cannot produce a suitable new full backup on the server by
merging an older full + incrementals.
It is probably easiest to imagine that the full backup takes a snapshot
of the database and the incrementals only pick up the change-sets to
that snapshot.
So when we do a full backup on the client (i.e. no AI) we will get a new
snapshot.
However, doing a virtual full backup without the client (i.e. what
Consolidation does) you will get a new full backup that contains the
original snapshot and lots and lots of change-sets to that snapshot.
This would leave you with full backups that keep growing and - what is
even worse - with an awful performance on restore, as you'll restore
some ancient snapshot and the apply lots and lots of change-sets to that.
Hope that sheds some light on why this doesn't work.
Best Regards,
Andreas
--
Andreas Rogge
andrea...@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