You don't have to back up bsr files. True, they can be written after
backup job but they are also created for a restore job based on a file
selection, timerange selection and so on from the data stored in
catalog. So the bsr files are not necessary to back up as far as I know.
Another thing is the database backup. It's possible to import a media
without prior information in catalog but it requires reading of the
whole tape. And if you're not sure where is your database stored, you'd
have to rescan several tapes which would be quite time-consuming.
So it's IMO a good practice to have configuration backup (including
crypto material!) and catalog database backup available on a easily
accessible media (i.e. dumped onto a some directory NFS-exported from
another server). This way in case of a disaster you can easily restore
your bareos installation by simply reinstalling software, restoring
config files and loading database from dump.
It's also worth noting that archiving is a different process than
backup. Sure, you can use bareos for it but archiving process objectives
are different than backup. There is also hugely different time span that
you need to provide data availability for so you'd have to architect
your solution accordingly. YMMV but I'd try to go for more incremental
approach to copying data to tape but also focused on having multiple
copies of every instance of data (possibly at least three).
Best regards
MK
W dniu 16.05.2020 o 21:27, 'DUCARROZ Birgit' via bareos-users pisze: