Hello Bacula-Users,

I want to create an offsite archive for our bacula setups that keeps
backups on a different storage and also with a longer retention time and
I'm looking for suggestions on how to best implement this.

We're running three bacula instances, each with its own dir/sd and in
total about 550 clients/fds. For the offsite archive I would use one
dedicated sd and then configure archive pools with long retention times
using the archive sd on each of the directors.

So far my best guess would be to either use Job-overrides in all job
schedules to have a job use an archive pool instead of the normal backup
pool once a week or alternatively to configure copyjobs for all jobs to
copy backups over to the archive.

While both of these solutions would be rather simple it would be quite
an effort to apply them to over 600 jobs and before I get started I
wanted to ask around if there maybe is something I overlooked and that
would make it easier for me.

Thanks,

Martin

------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users