Acronis Blog

What is immutable backup? Storage, retention and recovery

Learn how immutable backups work, how they differ from air gaps and encryption, and how to configure retention and test recovery

What is immutable backup? A guide to retention and recovery

An immutable backup is a recovery copy protected against alteration or deletion for an enforced retention period. Its purpose is to preserve an earlier state when production data, administrator credentials or ordinary backup operations are compromised.

That protection has a defined scope. It applies to the recovery points, storage and policies covered by the implementation. It does not establish that the original data was correct, that the backup contains no malware, or that an application will recover within its required time.

For IT teams and managed service providers, the useful question is therefore practical: which recovery points remain available, for how long, and under whose authority can their protection change?

How immutable backups work

Backup software captures selected data and writes recovery information to a supported repository. A retention mechanism then restricts changes to the protected data. New activity can create another recovery point while the earlier protected point remains available.

Write once, read many, or WORM, describes a model in which retained information can be read repeatedly without rewriting the protected copy. Storage services implement retention in different ways, including object-level locks and purpose-built backup repositories. Their rules for administration, deletion and expiration are part of the design.

An operational example illustrates the difference. An administrator may remove a backup from the normal view, while a protected copy remains recoverable until its immutable retention period expires. Other products prevent deletion of a protected object version directly. Read the documentation for the actual repository rather than assuming these interfaces behave identically.

Immutable backup versus immutable storage

Immutable storage is the underlying capability to retain protected data without allowing specified changes. Immutable backup uses that capability to protect recovery data and combines it with backup schedules, catalogs, recovery dependencies and restoration tools.

Storage immutability also has uses beyond backup, including retaining records or logs whose history needs protection. Those uses raise separate questions about record formats, search, holds and lifecycle management. Our immutable storage guide covers that broader topic.

The distinction matters when buying a solution. A storage lock alone does not schedule application-aware backups or prove that a complete restore chain exists. A backup product needs to preserve the data and metadata required to reconstruct a usable recovery point.

What immutability does and does not protect

Incident
How immutability can help
What else is needed
An attacker tries to delete backups
Enforced retention can preserve covered recovery points
Restricted administration and monitoring of policy changes
Production files are encrypted
An earlier retained point may support recovery
Investigation, a clean destination and restore testing
A user deletes important information
A retained historical copy may remain available
Appropriate scope, frequency and retention
A repository or site becomes unavailable
Immutability alone does not supply another accessible location
Independent copies and a tested offsite recovery path
Sensitive information is stolen
Retention does not reverse disclosure
Access controls, encryption and incident response

Corrupt or malicious data can also be backed up. Immutability preserves the state that was captured; it does not judge whether that state is trustworthy.

Immutable, offline, encrypted and versioned are different properties

Offline describes a copy that is disconnected while it is offline. Offsite describes location. A cloud copy can be offsite and still reachable through compromised credentials.

Encryption limits readability without the correct key. It does not, by itself, stop an authorized account from deleting ciphertext. Protect the decryption keys separately and verify that recovery personnel can obtain them during an incident.

Versioning retains multiple states, but administrators may still be able to remove those versions. Snapshots can support recovery, but may depend on the same storage or management system as production. Neither label establishes enforced retention.

Continuous data protection concerns how changes are captured. It can improve recovery-point granularity in supported configurations, but does not automatically make the resulting recovery data immutable.

These controls can complement one another. Choose them against the failure scenarios in your data backup plan.

Retention modes and administrator authority

Mode names are product-specific. In some systems, a governance mode allows designated privileged users to bypass retention, while a compliance mode imposes stronger restrictions. For example, Amazon S3 Object Lock distinguishes these modes and applies protection to individual object versions. Do not assume another vendor uses the same permissions or expiration behavior.

Before enabling a policy, establish:

  1. Which existing and newly created backups become protected.
  2. When the retention clock starts and when data becomes deletable.
  3. Who can shorten retention, disable protection or bypass a lock.
  4. Whether the selected mode can be reversed.
  5. How account closure, tenant deletion and storage changes affect recovery.

Test changes in a suitable evaluation environment before committing production data to an irreversible policy.

How to choose a retention period

Start with the time the organization may need to discover and investigate a problem. A copy that expires before unnoticed corruption is detected may not help. Consider how far back different applications need to recover and how long their dependent backup chains must remain intact.

Keep backup frequency and retention separate. Frequency influences the available recovery points; retention determines how long those points remain available. Neither, alone, establishes a recovery time objective.

Estimate storage consumption using a representative initial backup, ongoing change rates and the retained history. Include deleted-but-protected data in the estimate where the service continues to store and bill for it. Review growth and capacity alerts instead of relying on a fixed percentage overhead.

For regulated information, have the responsible legal and compliance teams approve retention and disposal requirements. An immutable feature can support a control objective; enabling it does not certify the organization or make every legal requirement applicable to the same data.

Implement immutable backup in seven steps

  1. Define the recovery scope. Identify files, applications, systems and the dependencies needed to restore an important service.
  2. Check repository support. Verify the deployed product, agent version, archive format and destination against current documentation.
  3. Separate administrative responsibilities. Limit who can operate jobs, change retention and manage storage. Protect privileged access with strong authentication.
  4. Set schedules and retention. Document the intended recovery history, expiration rules and capacity assumptions.
  5. Confirm protection applies. Verify existing archives as well as newly created recovery points. Enabling a setting may not retroactively cover every old backup.
  6. Test the controls safely. Use disposable test data to check expected deletion restrictions and authorized recovery behavior.
  7. Exercise restoration. Recover representative files and an application or system, then record the results and unresolved dependencies.

For MSPs, repeat the relevant checks at customer and storage boundaries. A policy enabled in one tenant does not establish coverage for every client.

Immutable backup with Acronis

The Acronis Cyber Protection service documentation describes immutable storage for supported cloud configurations and TIBX backups. Deleted protected backups remain recoverable during the configured period and continue to occupy storage.

In that service, Governance mode allows retention changes; disabling immutability requires support assistance. Compliance mode is irreversible and prevents disabling the setting or changing the retention period. The documented behavior differs from assumptions about other products' mode names.

Check the current support requirements before deployment. Confirm that each required archive is covered, understand the storage charges, and conduct a recovery test. Product and tenant configuration determine the protection delivered.

Questions to ask before relying on an immutable copy

Can ransomware still affect recovery? Yes. It may compromise production, backup administration, keys or recovery infrastructure. Immutability reduces particular ways of destroying recovery data; it is one part of the response plan.

Do immutable backups replace other copies? No. A retained copy can still be inaccessible because of an outage, damaged infrastructure or lost credentials. Plan independent recovery paths.

Does a successful deletion test prove recovery? No. Retention enforcement and restoration are separate checks. Test both.

Does immutable storage guarantee compliance? No. Requirements also involve data scope, approved retention, access, evidence, disposal and organizational responsibilities.

Sources

https://www.acronis.com/en/blog/posts/immutable-backup/

https://www.acronis.com/en/blog/posts/immutable-storage/

https://www.acronis.com/en/support/documentation/CyberProtectionService/immutable-storage.html

https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html

Written by

About Acronis

Acronis is a leader in AI-native cyber protection, unifying data protection, cybersecurity, IT operations and hybrid infrastructure to deliver business continuity, security and compliance with less cost and complexity. More than 21,000 service providers trust Acronis to protect over 750,000 businesses in 150 countries. Acronis is headquartered in Schaffhausen, Switzerland.