I decided to set 'Make latest backup record immutable for' to 3 days and did not change the default 'Refresh immutability every 30 day(s)'.įor testing purposes I wanted the lock to expire in 3 days from now, but not understanding what the second setting is for - I still don't - it created an object lock that expires 33 days (!) from now. I decided to do some experimentation with Backblaze B2 as Storage Location. I believe that Arq has a sane default retention policy: hourly record for the past 24 hours daily records for the past month weekly records for the past year and monthly records up to five years.īut what happens if you combine this with Arq's Immutability options? And what would be a best practice that balances protection and the amount of backup records? So maybe I'm overthinking this and being a bit too paranoid, but I like to setup backup systems to be foolproof.įrom time to time, old backup records need to be cleaned to save space on the backup destination. Precious family photos, videos and other documents. That would be a separate authorized role of another system. In the ideal world, computers are only authorized to create new backups, not delete old ones. Immutable backups in my mind resemble appending to tape, without the possibility to change previous backups.
With other (online) backup solution, I always worry that a human error - me - can cause a large backup history to be damaged or deleted. Arq 7's support for the S3's object lock API caught my attention and it convinced me to start a 30-day trial.
0 kommentar(er)
