Backup and Disaster Recovery · #60

Online Immutable Backup Capacity Calculator

Calculates the extra capacity caused by locked backups living longer than retention.

  • Data is processed in your browser and not sent to a server

Tool

Space it uses in the repository (after compression).

Incremental size relative to the full.

Lock period.

Extra time the product adds to locks; 0 if unknown.

7 = weekly; 0 = forever incremental.

What does this tool do?

An immutable backup against ransomware cannot be deleted before its lock expires. If the lock is longer than retention, or the product extends locks by a 'block generation' period, the repository must be noticeably larger than a normal calculation. The tool compares locked and unlocked scenarios.

How to use it

  1. Enter full backup size (after reduction), daily change and retention.
  2. Enter the immutability period and your product's block generation headroom (10 days typical for Veeam).
  3. Enter the full backup interval (0 = forever incremental) and press Calculate.

Fields

Full backup size
Space it uses in the repository (after compression).
Daily change
Incremental size relative to the full.
Retention (days)
Immutability (days)
Lock period.
Block generation (days)
Extra time the product adds to locks; 0 if unknown.
Full backup interval (days)
7 = weekly; 0 = forever incremental.

Worked example

InputValue
Full backup size10
Daily change5
Retention (days)14
Immutability (days)30
Block generation (days)10
Full backup interval (days)7

Expected result: Effective retention 40 days: 7 fulls + 34 incrementals = 87 TB; 36 TB without lock for 14 days — 51 TB (142 %) extra.

A lock longer than retention more than doubles capacity. Either align retention to the lock (the space is paid for anyway) or reconsider the lock against ransomware detection time.

Second scenario

InputValue
Full backup size4
Daily change3
Retention (days)30
Immutability (days)14
Block generation (days)10
Full backup interval (days)0

Expected result: 30 days retention, 14 days lock, forever incremental: effective 40 days, 8.8 TB; 7.6 TB without lock.

Method and assumptions

Effective days = max(retention, lock) + block generation. With an interval > 0, fulls = ceil(days / interval) + 1, incrementals = days − (fulls − 1); with 0, 1 full plus one incremental per day. Incremental size = full × change.

Using the result and troubleshooting

The lock should be at least as long as the time to detect ransomware. Compare capacity with the RAID and Backup Repository tools; mark the immutable copy in the 3-2-1-1-0 check.

Limits and common mistakes

  • Lock mechanisms differ (S3 Object Lock, XFS immutable bit, WORM tape); block cloning and GFS points are not included.

Frequently asked questions

Does a forever-incremental chain work on immutable storage?

In most products locked blocks cannot be merged, so periodic (synthetic or active) fulls are required; check product documentation.

Related tools and service

Related service: Backup and Disaster Recovery

Systems online tools · See all online tools