What Is an Immutable Backup and How Does Object Lock Work?
An immutable backup cannot be changed or deleted for a set period, even by ransomware, particularly in the strictest mode.
An immutable backup is a copy that cannot be altered or deleted for a set period. Object Lock is a feature of object storage that enforces this, so a backup is better protected against ransomware and mistakes.
What does immutable mean?
Immutable means unchangeable. With an immutable backup, you specify that the data may not be overwritten, changed or deleted for a certain time, for example thirty days. In the strictest mode (compliance) this applies to everyone, including users with the highest permissions. In a milder mode (governance), users with a special permission can lift the lock under conditions. Only after the period has ended can the copy be cleaned up.
The idea comes from WORM: write once, read many. You write data once and can then read it as often as you like, but no longer change it.
An everyday comparison is a postbox with a slot. You can put post in, but you cannot take the contents out again until the retention period is over. Unchangeable storage works the same way: you can add and read, but not change or discard within the agreed period.
That fits with a well-known insight in backup policy: a copy is only valuable if it is also protected against the events you want to guard against. A backup that has the same administrative rights as the production system effectively shares the same risks.
Why is that useful with ransomware and mistakes?
Attackers who gain access to an admin account often also try to delete or encrypt backups, so that recovery is no longer possible. With unchangeable storage, particularly in the strictest mode, that does not work within the set period, even with administrator credentials for the production system. That way you keep a clean copy to fall back on. See also ransomware and backups explained.
It also helps with ordinary human error: an administrator who accidentally deletes the wrong backup set, or a script that cleans up too much. Immutability is therefore not a luxury for large organisations only, but also a common measure in many business set-ups.
How does Object Lock work?
Object Lock is a feature of object storage, such as S3-compatible services. You switch it on for a bucket, a container for objects. After that you can specify a retention period per object or through a default setting. You can read how that works in what is an S3 bucket and what is object storage.
There are often two modes:
- Governance mode: certain users with special permissions can lift the lock under conditions.
- Compliance mode: nobody can shorten the retention period or delete the object before the period is over.
There is also often a ‘legal hold’, a lock with no end date that you can lift yourself. Which options are available and what they are called differs per provider. Consult the documentation for your service.
What should you watch out for?
Unchangeable really means unchangeable. A few points to bear in mind:
- Storage builds up: because you cannot delete anything during the period, you may keep more data than you are used to.
- Choose the period deliberately: too long can be awkward, too short protects less.
- Privacy and retention periods: there are rules for personal data about how long you may keep it. Ask an expert or consult the Autoriteit Persoonsgegevens.
- Support in your software: not all backup programs work with Object Lock. Check the specifications before you choose.
- A configuration error can stay: test with a small set first.
Does immutable suit your situation?
For a private archive, a good basis with several copies, as in the 3-2-1 backup rule, is often already a big step. For businesses that depend on their data, or that have requirements from customers or regulations, immutable storage can be a useful addition. Also look at the options under backup services for businesses.
It remains one part of a bigger whole. Also test recovery with a restore test, because unchangeable storage says nothing about whether the content is correct.
If you like, start with a trial: create a test bucket or test location with a short retention period, write a few files to it and try to change or delete them. That way you see with your own eyes how the lock behaves before you apply it to real data. Also read your provider’s terms on what happens if you end a subscription while locked data is still stored.
What limitations does Object Lock have in practice?
The examples below come from the Amazon S3 documentation. Other providers may do it differently, so read their documentation.
- On S3, Object Lock only works in buckets that have versioning enabled. Once enabled, you cannot turn Object Lock off again.
- The retention period applies per object version. A new upload under the same name creates a new version and leaves the locked version untouched.
- A lifecycle rule for automatic clean-up cannot delete a locked version.
- Locking does not protect against the loss of encryption keys. If the keys are gone, the data may become unreadable.
- In governance mode, a user with a special permission can bypass the lock. So grant that permission sparingly.
- On S3, a delete marker can be placed on a locked object. The object then appears to be gone, but the locked versions remain.
- When replicating to another bucket, Object Lock must be enabled there too.
Frequently asked questions
Is an immutable backup the same as an offline backup?
No. An offline backup is physically or logically disconnected. An immutable backup can be online, but is protected by the storage itself against changes and deletion.
Can I use Object Lock on a NAS?
Some NAS systems offer comparable features, such as locking or snapshots that are protected. This differs per model and software, so check the manufacturer’s documentation.
Can an immutable backup still disappear?
Within the set period it cannot happen through normal administrative actions. Physical damage, cancelling an account or errors at the provider remain points to watch, so an extra copy in another place remains sensible.
Does versioning need to be enabled for Object Lock?
On Amazon S3 it does: Object Lock only works there in buckets with versioning. Other providers may differ, so check the documentation of your service.
Further reading
Last updated on
