Recovery Brief

Security and recovery

What is an immutable backup?

An immutable backup is a copy configured so it cannot be changed or deleted during a set period. The exact protection depends on the storage, identity and retention settings.

Retention is not the storage deletion date

Veeam Software · Locked storage can outlast retention

For EC2/RDS image backups in Veeam’s AWS plug-in, the first block generation adds 25 days to retention. Existing block locks cannot be shortened.

Veeam Backup & Replication 13 guide, build 13.1.2.57; this is not a rule for every Veeam repository.

Source

Veeam Software · Changing retention can add requests

Veeam warns that frequent retention changes create new block generations and can increase storage-service requests and cost.

AWS plug-in image-level backups with immutable target repositories.

Source

A vendor's design description does not prove that your copy is protected or that recovery will work.

What the saved vendor pages say

  • Veeam Software: Veeam Backup for AWS describes temporary immutability for EC2, RDS and VPC configuration backups using S3 Object Lock; limitations require bucket Object Lock and versioning, and exclude EFS indexes and appliance configuration database. Read conditions
  • Veeam Software: The vendor article is dated February 19, 2025 and marked updated June 26, 2026; it discusses multiple immutability architectures and says immutable backups should still be tested. Read conditions
  • Commvault: Commvault describes managed immutable cloud storage and on-premises immutable architecture options. Read conditions
  • Rubrik: Rubrik describes Cloud Vault as a managed vault in an isolated Rubrik identity domain where production credentials do not work; copies are immutable on arrival, retention is locked to the configured SLA, production identity has no account in the vault, and quorum authorization is required before a location is paused or deleted. Read conditions
  • Acronis: The page says Cyber Protect Advanced includes scanning backup files for malware before restore and safe recovery intended to avoid reintroducing malware. It then says Cyber Protect Advanced and Backup Advanced offer enhanced features over Standard, while separately identifying SaaS workload support as Backup Advanced-only. Read conditions
  • Druva: The February 5, 2026 EC2 entry describes Recovery Intelligence for EC2 Airgap Backups, threat hunting, restore-point health insights and optional Cloud IOC/antivirus scans before restore. Access to Recovery Intelligence requires one of Security Posture & Observability, Accelerated Ransomware Recovery, or Premium; Threat Hunting details require Premium. Read conditions
  • Cohesity: Cohesity DataProtect describes immutable snapshots that cannot be mounted or altered outside the Cohesity service, DataLock immutability policies, Zero Trust RBAC/MFA/SSO, hash-based threat scanning, and default FIPS 140-3 encryption across VM, database, NAS, cloud, and Microsoft 365 workloads. Read conditions
  • NAKIVO: NAKIVO states support for immutable and air-gapped storage, source-side backup encryption, and pre-recovery backup malware scanning. Read conditions

Each statement has a product scope and conditions. They do not describe the same architecture, so this page does not score them.

What to prove in a demo

  • Which identity can change or delete a copy?
  • Can production credentials reach the recovery copy?
  • What prevents retention from being shortened?
  • Can the team restore while the production identity is unavailable?
  • Which workloads or system metadata are excluded?

Test a recovery plan →

Will these backups restore fast enough?

The comparison can show the workload, edition and published promise. It can’t tell you how long your own recovery will take. The saved comments raise restore speed, bandwidth and the work of rebuilding services. We don’t have a controlled restore test for those cases.

Plan a test with your own workload.