AUTO-UPDATED

What IT Teams Get Wrong About Immutable Backups and Object Lock

Understanding the nuances of cloud object lock is essential for IT administrators to ensure immutable backups are correctly configured to protect against ransomware and accidental data deletion.

Key Points

  • Object lock prevents file modification or deletion for a set period, but it does not retroactively protect existing files in a bucket.
  • Immutability must be configured at both the bucket level and within enterprise backup software like Veeam or Commvault to function correctly.
  • A 14-day immutability period is generally sufficient for most organizations to detect and respond to ransomware attacks.
  • Backup applications often extend immutability periods beyond user settings to provide a safety buffer, which impacts storage capacity planning.
  • Bucket-level lifecycle rules should be avoided when using backup software to prevent conflicts with the application's own data management processes.
  • Object lock does not protect data if an entire cloud account is deleted, making robust account-level security and multi-factor authentication critical.

Why it Matters

Misconfiguring immutable backups creates a false sense of security that can leave organizations vulnerable to data loss during a ransomware event. Properly aligning backup software settings with cloud storage capabilities ensures that recovery points remain intact and accessible when needed most.
Backblaze.com Published by Kari Wilson
Read original