I screwed up my migration to Always Incremental backups, and I'm hoping that
there is a path back for me. I had been doing a classic incremental,
differential, and full set of backups to disk. When switching to AI backups
Bareos noticed that there was a full backup available, and then just continued
to use that. Which is way cool.
And also use the incremental and differential backups also. When consolidation
jobs ran it just did the right thing. Until my screwed up config caught up
with me though.
I was only retaining the incremental backups (not the AI backups, but the
original incrementals) for 18 days. And differential backups for 21 days, and
full backups for 28 days. But when deploying always incremental I set:
always incremental job retention = 30 days
always incremental keep number = 10
always incremental max full age = 38 days
Which means it won't run consolidation until there are 30 days of
incrementals, but I was only keeping the old ones for 18 days.
How did my original testing succeed you ask? Good question! Because I had
somehow disabled pruning when originally setting things up. And did my testing
when nothing was being pruned. Then I noticed my database was HUGE and catalog
backups kept getting bigger. So I turned on pruning. And then consolidation
jobs started to fail.
Gun, meet foot. Sigh.
Is there a way back from this? I've extended all of my retention periods to
40 days and turned off auto pruning. But damage has been done.
Help please.
--
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.
