Greetings,
I'm using Hyper Backup and Backblaze B2 storage to perform my daily backups, and I'm confused about where Hyper Backups rotation settings intersect with BackBlaze's Lifecycle settings. I currently have HB set to retain daily versions for a week, then weekly for a month, then monthly for a year with maximum 32 versions. On my BackBlaze Lifecycle settings, I have it set to keep prior versions for 60 days. My question is this; what constitutes a "version" in HB as opposed to BackBlaze? Does the version in HB refer to versions of each file or the backup as a whole. i.e. if a single file changes between todays backup and yesterdays, is the entire backup a new version or is it just the file? And if anyone knows, does the same logic apply at the C2 level? As it now stands I know that I will have backups of at least a year for the oldest versions of a file, but where this intersects with the 60 days setting in BackBlaze confuses me. I'd appreciate hearing from anyone who can shed some light on this.
Thanks!
I'm using Hyper Backup and Backblaze B2 storage to perform my daily backups, and I'm confused about where Hyper Backups rotation settings intersect with BackBlaze's Lifecycle settings. I currently have HB set to retain daily versions for a week, then weekly for a month, then monthly for a year with maximum 32 versions. On my BackBlaze Lifecycle settings, I have it set to keep prior versions for 60 days. My question is this; what constitutes a "version" in HB as opposed to BackBlaze? Does the version in HB refer to versions of each file or the backup as a whole. i.e. if a single file changes between todays backup and yesterdays, is the entire backup a new version or is it just the file? And if anyone knows, does the same logic apply at the C2 level? As it now stands I know that I will have backups of at least a year for the oldest versions of a file, but where this intersects with the 60 days setting in BackBlaze confuses me. I'd appreciate hearing from anyone who can shed some light on this.
Thanks!
