Budget for three complete snapshots of an unchanged 80 GB dataset. Full copies need 240 GB; a hypothetical base plus two 5 GB changes totals 90 GB.
The worked example
| Calculation |
|---|
| 80 * 3 = 240 |
| 80 + 5 + 5 = 90 |
These are constructed inputs. Displayed decimals are rounded; they are not product measurements.
Understand the result before using it
Three full copies contain three sets of bytes, but if all were made after an unwanted edit, none preserves the earlier state. Version history asks when the bytes were captured. Redundancy asks how many copies survive a failure. Those are separate requirements even when storage totals match.
The 90 GB alternative assumes one 80 GB base and two retained 5 GB increments with no further overhead. Losing the base may make those increments unusable, depending on the format. Record which pieces a restore needs before estimating storage savings. Compression, metadata and retention rules can change the total; a capacity estimate cannot substitute for opening a restored file from the chosen backup method.
The boundary of this calculation
The second figure requires a backup method that actually stores those changes; deduplication and recovery are not tested here.
Inspect the example inputs and run the Python checks. They use only the published examples and do not read personal folders.