Does Retrospect actually retain the last version of every file indefinitely? Or does it retain the last version of every backup indefinitely? I suspect it is the latter.
The difference is that you cannot restore a deleted file after the last backup that contained it has been deleted. It is easy to configure Bacula to keep the last n copies of each Bacula job. You just need to run a job with level=full every m days and set the retention periods to at least n times m. See http://www.bacula.org/9.2.x-manuals/en/main/Automated_Disk_Backup.html for example. __Martin >>>>> On Sun, 2 Sep 2018 14:51:18 +0100, Chris Wilkinson said: > > Many thanks to all. > > I previously used Retrospect and this had a facility to set the number of > versions to be retained 1+. Earlier versions would be removed through a > scheduled "groom" job where storage space would be reclaimed. This meant > that there would always be exactly 1+ versions retained indefinitely. > > It doesn't appear that that behaviour can be replicated in Bacula, the > nearest being to retain everything always. > > Regards > Chris Wilkinson > > On Wed, 29 Aug 2018, 1:52 p.m. Dan Langille, <d...@langille.org> wrote: > > > > On Aug 28, 2018, at 2:54 AM, Chris Wilkinson <winstonia...@gmail.com> > > wrote: > > > > > > One of my requirements for backups is that the last version of every > > file should remain in the backup storage indefinitely or at least for a > > long time. > > > > > > Could I achieve this by writing "File Retention = 10 years" in the pool > > or client definition? > > > > Yes. But you'll also need Volume and Job retention also set to 10 years if > > you want to easily restore that data. > > > > This will keep all records, not just the latest. > > > > Yes, this will use more database records, but my view is that this is a > > cheap price to pay. > > > > Also, as mentioned by others, does this requirement mean that a file > > deleted 6 years ago needs to be kept for another 4 years? > > > > You'll need to clarify that 10 years meets the "indefinitely" requirement. > > > > Given the originally stated requirements, it seems your only solution is > > not to ever recycle volumes or allow the Catalog to be pruned. > > > > > My concern is that, if this is possible, then it would stop automatic > > volume truncation and recycling and eventually result in out of space > > storage errors. > > > > Yes, you need to have enough storage. > > > > > > -- > > Dan Langille - BSDCan / PGCon > > d...@langille.org > > > > > > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
