Hello, I have been able to get Always Incremental backups using Max Full Age working per the documentation
https://docs.bareos.org/TasksAndConcepts/AlwaysIncrementalBackupScheme.html as well as this example: https://groups.google.com/forum/?hl=en#!searchin/bareos-users/Always$20incremental$20example%7Csort:date/bareos-users/i5H0ScDWA4Y/JUBDGex-AQAJ My question is on when the Max Full Age expires and Bareos tries to do a consolidation/Full Virtual Backup, it needs to keep around the old full backup (to read from it) as well as write to the new full backup, which means I need to effectively have twice the space on my archive drive than I do for my data drive; i.e. if I have 6TB, I would need a 12TB drive for backup. Is this a correct assumption? If so, is there a way to do full virtual backups more efficiently? I have seen some other postings about jobs/scripts that cleanup the unused volumes, which are cool, but one would still need 2x the space so that the full virtual backup operation can successfully complete. I have tried setting my Maximum Volume Bytes to a number where I would get a number of different volumes, along with playing with options like Action On Purge = Truncate and Purge Oldest Volume = yes but to no avail. Is there anyway to configure Bareos to purge/remove/delete a volume as soon as it's read/copied? From my experiments, it looks as though Bareos needs to read all the backup volumes first before moving the data over during a Full Virtual backup -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/66e7658d-1a91-4ee9-a467-ade53b00e798n%40googlegroups.com.
