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 retention policy: how many restore points do you need?

Published August 2026 · 8 min read

Backup retention decides how long historical recovery points remain available. Keeping only the newest copy can fail when a problem started days or weeks before anyone noticed, while retaining everything forever can create unnecessary cost, privacy, and management burden.

Estimate how long failures can remain hidden

Immediate hardware failures are obvious, but corrupted data, deleted records, compromised files, or bad automation can go unnoticed. Retention should extend far enough to reach a known-good state from before the likely detection window.

Use different frequencies for different ages when appropriate

A common pattern keeps frequent recent restore points and fewer older points. The correct schedule depends on recovery objectives and the backup product; the goal is useful history without storing redundant copies that provide little additional recovery value.

Include growth and change rate in capacity planning

Retention cost depends on how much data changes between backups, compression or deduplication, database churn, large binary files, and how full backups are constructed. Measure real backup-set growth instead of multiplying live storage by a fixed number.

Document deletion and compliance requirements too

Some data should not be retained indefinitely. Align backups with contractual, privacy, legal, and business requirements, and understand how deletion requests interact with protected historical copies and expiry schedules.

Next step

Design backup retention around recovery windows, data change rate, unnoticed corruption, legal or business requirements, storage growth, and the time needed to detect incidents.

Plan backup capacity

Keep reading

Related guides.

Backup capacity planning: estimate storage from change rate and retention

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

Read the guide

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

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