Hello,
wt., 28 sie 2018 o 08:56 Chris Wilkinson <winstonia...@gmail.com>
napisał(a):
> One of my requirements for backups is that the last version of every file
>
I'm not a native English speaker, so I need an explanation here. What is
your understanding of the "last version". I understand it as the recent one
(the opposite to the first one), so every time you change the file it
become "the last version".
> should remain in the backup storage indefinitely or at least for a long
> time.
>
>
It sounds to me as you want to archive a single file version in your long
time retention storage.
> Could I achieve this by writing "File Retention = 10 years" in the pool or
> client definition?
>
>
File Retention parameter applies to catalog records only. The Volume
retention is a parameter which preserve backup data from recycling.
> 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.
>
No, the Volume Retention parameter has precedence to File Retention and Job
Retention, so you can set any insanely long time value to FR/JR parameters
(i.e. 100Y) and your backup will be archived no longer then VR parameter.
best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net
------------------------------------------------------------------------------
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
