Backup strategy with retention times

[Trym Eska]

I am running Bareos in a small environment in my home network, for the time being, only backing up my profile folder in windows each night.

I am also experimenting with different backup schemes, to see what suits me best. My configuration headaches often comes from choosing the right retention times and number of volumes while trying not to exceed available hdd space.

Please give me your thoughts about this backup setup of a folder with not so important files, with the following premises:

I want 10 full backups available. How far back in time, doesent matter (either I will launch the job manually, or fixed schedule/day.)

Can I configure a pool like this:

autoprune and recycle = yes

retentiontime 1 day. (or 1 minute, for that matter!!)

Only 1 job per volume

maximum 10 volumes.

Is this a working setup? In my theory, the full backup will launch e.g. every night. But if I manually launch additional 1-3 full backups during the same day because I feel like it, and since the retention time is minimal, bareos will always have loads of volumes to prune/purge/recycle. (yes, the oldest backup will not be 10 days old anymore, but I dont care.)

So the idea is that since Bareos always tries to preserve data, even if half of the volumes/backupjobs in a pool have passed its retentiontime, its still a valid backup, until a new job overwrites it.

Will it work like this?

I feel like this would make my head lighter, stopping to care about retention times, and instead caring about how many volumes/backups that actually exists. (remember, this if for a home user, not a big corporation).