Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Backups

Backup capacity planning: estimate storage from change rate and retention

Published August 2026 · 2 min read · Updated 2026-09-05

Backup capacity planning combines protected data size, growth, change rate, retention, full/incremental behavior, compression or deduplication, temporary workspace, and restore headroom. Buying backup storage equal to today’s live disk size rarely covers a useful retention window.

Measure protected bytes, not allocated disk

Inventory actual database dumps, files, VM/application data, configuration, and other material you intend to retain. A 500 GB VPS with 80 GB used may not need 500 GB per backup, while an application with generated database dumps can briefly need more than live data.

Exclude reproducible caches/build artifacts unless recovery really depends on them.

Estimate daily change and growth

Track changed data over representative weekdays, weekends, imports, release cycles, and month-end jobs. Use measured compression and deduplication ratios from your own data.

Add business growth and new workload expectations to the horizon.

Model retention and temporary operations

Full-plus-incremental schedules, synthetic full operations, pruning, verification, and restores can require extra workspace. Keep headroom so the repository does not fail while deleting old copies.

Set alerts before capacity reaches the point where a new backup cannot complete.

Reforecast from repository history

Monthly review of source size, backup size, daily growth, oldest point, and capacity runway provides better purchasing evidence than one initial spreadsheet. Keep the same metrics after major application imports or retention changes so the forecast reflects how the repository actually behaves under new data patterns.

  • Measure actual protected data.
  • Track change rate.
  • Include retention/workspace.
  • Monitor capacity runway.

Next step

Model source size, daily change, compression, deduplication, retention and growth so backup storage is sized from the workload instead of one full-copy estimate.

Explore DotMoose backup storage

Keep reading

Related guides.

Backup encryption basics: protect copies at rest and in transit

Choose where backup data is encrypted, how keys are stored and recovered, and how restore operators gain access without putting the only key beside the backup.

Read the guide

Backup recovery drills: prove the restore process before an outage

Run isolated recovery tests, measure restore time, verify application state and record missing dependencies so the backup plan is based on tested recovery.

Read the guide

Backup retention planning: choose how many recovery points to keep

Set backup retention from recovery needs, change rate, storage cost, compliance and deletion risk so recent mistakes and older corruption remain recoverable.

Read the guide

More backups guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move