Object Lock Mistakes That Put Immutable Backups at Risk

This post details common mistakes IT teams make when configuring object lock for immutable backups on Backblaze B2. It clarifies that immutability prevents deletion/modification, not access, and that enabling it on existing buckets does not retroactively protect data. The post emphasizes that both the bucket and the backup application (e.g., Veeam) must be configured for object lock to function correctly. It also distinguishes between retention and immutability periods, recommends a 7-14 day immutability window aligned with detection capabilities, and notes that Backblaze B2 does not charge extra for object lock API calls. It warns against conflicting bucket lifecycle rules and highlights that not all backup software supports object lock. Finally, it explains that while object lock prevents deletion within an account, account deletion itself is a separate risk mitigated by account security measures.