Depending on your network provider (Comcast), you might run into trouble with such a rapid growth of data throughput. From a timing perspective that took more than a week, and consumed a ton of bandwidth doing so (I am more than 5x my normal data throughput so far this month). The down side is that Hyper Backup had to delete 424 differentials from the B2 Storage bucket. To correct my error, I implemented a 30-day retention period in Hyper Backup. The fix is easy, but could be painful depending on your network bandwidth or provider. I was paying about 2.5 times as much as was budgeted.
In my case I had achieved 454 backups before I recognized the error. Backblaze sees the pool, no matter how many Hyper Backup differentials are there, as a single version that will grow to infinity (theoretically) if allowed. Choose Task Settings -> Rotation to choose how many backup versions to keep. To manage the number of differentials Hyper Backup maintains, you must do this in Hyper Backup. I discovered this when my storage pool swelled above the size of the original data it was backing up. In my mind, this was the setting that would manage the number of Hyper Backup differentials were retained. You can select “keep all versions”, or change the Lifecycle setting to adjust how many copies of data you retain. When setting up a storage bucket in Backblaze one of the options is “File Lifecycle”. The fix was also painful, so I wanted to share what I learned to help others who may be setting up their own backup strategy. This resulted in a growing storage pool in Backblaze along with increasing monthly storage cost. I send daily backups to Backblaze B2 from my Synology NAS, but figured out recently the configuration was not optomized.
0 kommentar(er)
