דילוג לתוכן
BackupONE · Object Lock

Your backup
needs protection too.

Object Lock helps protect your backup copy against modification and deletion for a period you define.

Protect what protects youIT professionals beside a locked cloud backup archive
Locked against changes. Available for authorized reading and recovery.
Another protection layer in the right place

What if the threat
reaches your backup too?

A backup copy is part of your recovery plan. If it can be deleted too, recovery becomes harder. Locking that copy reduces this risk.

Ransomware targeting backup copies

Locking can prevent protected versions from being modified or deleted.

Human error at the wrong moment

Accidental deletion or cleanup should not remove a copy under a valid lock.

Compromised access credentials

Protection also depends on lock mode and separate permissions. Configure both together.

More about immutable backups
A technician explaining cloud backup and copy protection on a board
Another copy. Another layer of confidence.
A simple idea

Back up. Lock.
Recover when needed.

Immutability preserves information without change. WORM allows a copy to be written once and read repeatedly without altering the protected version during the lock period.

Conceptual workflow · Select a step to learn moreThe route to a protected copy

Configure protection in practice. Choose lock mode and duration, then verify that the policy applies to the required backup versions.

Protection over timeInteractive demonstration

Try deleting a copy.
See what protects it.

Change the day, choose a lock mode and check the result. Try recovery too: the protected copy stays in place.

Open this page in a browser with JavaScript enabled to use the demonstration. The explanations remain readable without it.
Lock mode

The copy was created on day 0 and locked for 30 days.
Changing a setting resets the demonstration copy.

Your backup copy

Conceptual illustration · Not a management system
The copy is locked23 days of locking remain
Recovery destination
Copy protected until day 30

Compliance mode prevents deletion of the version during the lock period. Authorized reading and recovery remain available.

Day 7 of 45
The lock period is highlighted in orange.

The demonstration tests deletion of a specific version under S3 principles, assuming read and delete permissions. Lock expiry does not delete the copy automatically. Explore lock principles

Two complementary protections

Encryption protects the content.
Locking protects the copy.

Ask two questions: who can read the data, and who can delete it? Each requires an appropriate protection layer.

Combine encryption, locking and precise permissions to protect both confidentiality and your recovery copy.

Two roles. One shared goal.
Encryption and Object Lock explained

Encryption · Who can read?

Content is unreadable without the correct key or password. Protect those credentials so recovery remains possible.

Object Lock · Who can delete?

The protected version is retained against changes and deletion under its lock conditions. Locking alone does not encrypt content.

Version preserved · Authorized reading remains possible
Choose what to retain and for how long

Everyday protection.
Long-term recovery points too.

Default and GFS determine which copies receive a lock. Protect data written to a destination, selected full backups or a combination.

Default protection at the storage destination

Example lock: 30 days
Daily copy 0130 days
Daily copy 0230 days
Daily copy 0330 days
Weekly full30 days
Monthly full30 days
Yearly full30 days

Set a lock period at the storage destination and align backup settings. In the supported workflow, new data written to the destination receives default protection, even without selecting GFS copies.

Copy types and periods are illustrative, not a recommendation for a particular retention period.Each new copy receives its own protection
For IT teams: how do the policies work together?

Default is configured at storage and destination level. GFS applies to full backup sets selected in the plan retention policy, using a supported format. When combining them, align baseline locking with longer-term copy periods. Verify the effective settings on versions actually written. Microsoft 365 and Google Workspace backup also requires a retention policy assigned to the user or domain.

Default documentation · GFS documentation

Different rules for different lock modes

How strict
should protection be?

Governance allows exceptions with special authorization. Compliance enforces a stricter lock. Choose according to operational requirements and organizational policy.

Comparison of S3 principles. Availability and implementation depend on the provider and configuration.
What should you check?GovernanceProtection with an authorized exceptionComplianceStrict locking for a defined period
Deleting a version during the lockBlocked without bypass permission.Blocked, including for the account administrator and root.
Bypassing before expiryPossible with special permission and an explicit bypass request.No ordinary bypass using user permissions.
Shortening the lock periodOnly possible under the appropriate bypass conditions.A valid lock cannot be shortened or removed. It can be extended.
Reading and recoveryAvailable to authorized users.Available to authorized users.
Who is it for?Organizations needing protection with controlled administrative flexibility.Organizations needing strict enforcement of retention periods.

This comparison concerns object-version protection within an active storage account. Locking does not preserve encryption keys or replace recovery planning. Selecting Compliance mode does not certify regulatory compliance; align the service with the relevant requirements.

Bypass permissions and administration: AWS documentation
Start with suitable infrastructure

The lock is enforced
where your backup is stored.

The documentation lists support for the following destinations. Check backup type, software version, account permissions and destination capabilities before deployment.

Amazon S3Object Lock
WasabiObject Lock
Backblaze B2Object Lock
IDrive e2Object Lock

S3-compatible storage: Compatibility depends on Object Lock implementation and permissions. Verify it in practice before configuring a backup plan.

Microsoft Azure and Google Cloud: Retention locking is configured at storage level. Settings not retrieved automatically require manual alignment in the backup system.

Storage capabilities and support: product documentation
Before you lock

Good questions.
Clear answers.

Details that help you choose appropriately and know what to expect.

Useful to know in advance
Can I restore while the backup is locked?

Yes. Object Lock restricts modification and deletion of the protected version without preventing authorized reading and recovery. Valid permissions, encryption keys and a recoverable backup chain are still required.

Are all my backups locked automatically?

No. Storage and backup settings must be enabled and aligned. Default protects new data written to a suitable destination; GFS protects full copies selected in the policy. Verify that the relevant versions actually received a lock.

What happens when a lock expires?

Expiry alone does not delete the copy. Without Legal Hold or another protection, it may become eligible for deletion under permissions and the configured retention or lifecycle policy.

Does locking guarantee a ransomware-free backup?

No. It protects a locked version against modification or deletion. It does not scan content or repair data damaged before backup. Combine it with cybersecurity, additional copies and recovery testing.

Can I enable locking on an existing destination?

It depends on the provider and product integration. AWS, for example, permits enabling Object Lock on an existing bucket, but default retention does not automatically lock existing versions. Check backup support, existing versions and configuration requirements separately.

How do we choose retention without unnecessary costs?

Start with how far back the business must recover, which points need long-term retention and the data volume. Locked copies continue using storage, so plan backup, retention and lock periods together.

BACKUPONE · PROTECTION STARTS WITH PLANNING

Protect
your route back.

Tell us what you back up and how long you need to retain it. We will explore how backup locking fits your environment.

Your data is worth protecting.
Plan. Back up. Verify.

What will we review together?

  • Systems and copies that need protection
  • Required retention and recovery points
  • Storage, permissions and lock mode
  • Recovery testing and backup monitoring