On 2024-08-15 09:14, Mehrdad Ravanbod wrote:
Thank you Josip
Appreciate your response, so if i understand correctly the whole ten
year backup data need not be kept in DB?? Not sure about the bootstrap
file and the rest though, new to bacula and trying to figure it out as
yet
Hello Mehrdad,
I apologize for missing your post and thus responding only now.
You need to keep the metadata in your database only for the most
recent, successful full backup job and all the related backup jobs
(differential and incremental).
For example, if you run full backup every three months, you don't
need to keep metadata that belong to older backup jobs.
I would still keep them at least for a year.
In case you remove all the metadata that belong to a certain very
old job but you still have access to volumes that hold the actual
data, you could read the data from the volume and populate the
database with the metadata using the bscan tool.
That would allow you to browse the data the usual way.
Bacula is exceptionally powerful backup system and I appreciate
the possibility for recovering the data even in the worst possible
scenarios (without the database and bacula daemons).
For archival purposes you mentioned, you could form a special
pool of volumes with different defaults for volumes and then
copy or migrate the jobs to that pool.
You will have to ensure that volumes in that pool don't get recycled.
So, yes, you don't need to keep 10 years of metadata in your
database but you need to keep in mind that you have to protect
your volumes from getting recycled and you need to keep at least
the last successful full backup job in your catalog (database) in
order for incremental backup to work.
--
Josip Deanovic
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
