Using one backup for multiple jobs / retention schedules

[Marc Stirnweiss]

Hi everyone,

We do weekly full backups and incremental backups on the days in
between. Backups are stored on our bareos sd server on disk, and the
following week, the full backup is migrated to tape via a migration job.
Right now, retention is set to one year.

We’re looking for a way to add another backup job, maybe once a month,
that we could keep for, say, 10 years, or to create a yearly backup with
a longer retention.

We’ve tried copying the migrated backup to another tape with a copy job,
but that was pretty slow since it copies tape-to-tape.

So far, we haven’t really figured out an easy way to do this via the
schedule. Maybe we need a separate job just for the monthly or yearly
backup.

Any tips or ideas would be really appreciated.

Thanks!

Marc




--
Marc Stirnweiß
Teamleader Junior Engineers

Plus.line AG
Erlenstrasse 2
60325 Frankfurt am Main

Managed Cloud / Kubernetes - Network Services - IT Outsourcing

[Bruno Friedmann (bruno-at-bareos)]

HI Mark, 

A quick answer, I guess you should investigate to run a virtual full + set it as archive jobs before your migration

like what is done here 

https://docs.bareos.org/bareos-24/TasksAndConcepts/AlwaysIncrementalBackupScheme.html#virtual-full-jobs

The bonus is that now you will be able to restore directly from them even from the webui too.