Problem Mixing Always Incremental, job copies, and consolidations

[Gaetan SLONGO]

Hi,

I'm facing to a serious issue regarding the Always Incremental backup scheme.

The goal is to use AI jobs, daily copy full+incrementals on tapes, and consolidate disks jobs weekly

The tape copies have different retention (longer). In the documentation I found :

"When a job is selected for consolidation, all job runs are taken into account, independent of the pool and storage where they are located."

This means, when original jobs will disapear from disk pool, Bareos will ask tapes for consolidating job copies. This is a problem. There is any way to force consolidation on specific pools ? Or suggestion to meet the requirements ?

Thank you !

[Gaetan SLG]

Hi

Does anyone has any idea on this issue ?

Thanks !

[Dan]

Gaetan -

This sounds a bit like a bug I opened with Bareos a couple of years ago.  See this issue in the bug tracker ... https://bugs.bareos.org/view.php?id=778.

I posted a script there to work around the problem and perhaps this will take care of your issue.

The specific issue is this ... A copy job, in your case copy to tape, is created as an archive job.  When the Consolidate job purges the 'primary' version of that job, the archive job (on your tape) is promoted to the 'primary' copy.  Next time around that job is consolidated again.  The script is run after every consolidate job to find these 'promoted' backup copies and properly set them back to 'archive' so they won't be processed again.