דילוג לתוכן

Object Lock: How to protect the backup from modification and deletion

What is Object Lock, how it integrates with immutable backup, and what is important to check in Governance, Compliance, and retention policy.

27.10.2026 · 4 minutes read
Illustration of an orange lock and shield around cloud backup data with retention period board

Backup is truly useful when it is possible to reach a valid copy even on the day something goes wrong. Object Lock adds a layer of protection that prevents modification or deletion of backup data for a defined period. This way, an operational error or an attempt to compromise the backup repository does not necessarily result in the loss of the protected copy.

What is actually locked?

The mechanism is based on WORM: write once, read many. In Amazon S3, the protection applies to a specific version of an object. You can create a new version under the same name, but the locked version remains protected. Versioning must be enabled, and the lock period determines how long the protection is retained. Explanation in AWS documentation.

Three concepts worth knowing

Governance
Restricts modification and deletion. In S3, special permission and explicit override action may allow exceptions, so it is important to check who holds the storage permissions.
Compliance
Strict lock: even the root user cannot delete the protected version or shorten the period. This mode is chosen only after checking the implications.
Legal Hold
Retention without a fixed end date, until an authorized party removes it explicitly. It can operate alongside a lock period.

Lock and permissions modes in S3.

How does this fit into the backup workflow?

Version 8.6 expanded support for locking, including FFI, SQL Server backups and the legacy format. Settings include default locking at the storage destination and locking of GFS copies according to plan settings. For Microsoft 365 and Google Workspace backups, also ensure the appropriate retention policy has been configured. Availability depends on the product, version and destination.

The source article describes creating a suitable bucket as part of the software’s configuration process. This is not necessarily a limitation applying to every provider or configuration method. Before making changes, check the current documentation for both the backup software and storage service.

What locking does not replace

Locking does not guarantee that the file was intact at the time of backup, nor does it check whether the application will be successfully restored. It also does not protect against loss of encryption keys: the data may remain stored and locked, but it will not be readable without the key.

In S3, the Lifecycle policy does not delete a version protected before the lock period expires. In addition, a Delete Marker can hide a version in the normal view without actually deleting it. It's worth understanding the difference during testing or recovery. Operational considerations in AWS documentation.

Pre-activation checklist

  1. Define which data needs protection and for how long.
  2. Check the alignment between the storage target, the backup plan, and user permissions.
  3. Assess volume and cost: Locked information may continue to occupy space even when no longer needed for daily operation.
  4. Start with test data and ensure that the lock was actually applied.
  5. Perform a test restore and document who is responsible for the keys and for emergency procedures.

Frequently asked questions

Is every cloud backup locked?

No. You need to ensure that the target and plan support the mechanism and that the policy has been applied to the data.

Is it possible to recover during the lock period?

The lock is intended to prevent modification and deletion. Reading and restoration are possible according to permissions and key availability.

Is this full protection against ransomware?

This is one layer in the recovery plan. It is combined with access control, monitoring, additional copies, and recovery tests.

For backup and recovery planning with BackupONE →

Continue reading