On Friday, December 13, 2024 at 3:12:34 AM UTC-6 Andreas Rogge wrote:
Am 12.12.24 um 20:23 schrieb Jon Schewe: > > Am I correct that this is a safe operation to run regularly and won't > end up losing data that is within my retention periods? Correct. Thank you for that confirmation. However, if there is a fixed amount of disk-space (which is usually the case) my preferred method is as follows: * Configure your disk pools as you need them (i.e. Full, Differential, Incremental, Whatever) * Disable auto-labeling * Set maximum volume bytes for each of the pools to the same value * Add a scratch pool * Set "scratch pool" and "recycle pool" in your backup pools to point to that scratch pool * Pre-label N volumes in the scratch pool where N = total space / maximum volume bytes Now when your backups write to one of the pools, they'll fetch volumes from the scratch pool as required. When a volume is recycled it will go back to the scratch pool, so it is available to be reused in any other backup pool. I see how that makes sense in most cases. Where I'm at right now is that I have a set number of machines that need to be backed up and a requirement for how long I need to keep backups. Tthat is what is driving the amount of space that is needed for backups. Unfortunately I don't know how much space I expect the backups to take, so I'm starting with a small partition and growing it as needed and expect the usage to level off as long as we stop adding systems to the backup system and hit the max retention period. -- 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 visit https://groups.google.com/d/msgid/bareos-users/2a59a107-36ad-4661-b822-10ee6ac3a248n%40googlegroups.com.
