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

Full vs incremental backups: what is the difference?

Published August 2026 · 9 min read

Backup strategy is a tradeoff between how much data you copy, how long the backup takes, how much storage it consumes, and how complicated the restore becomes. “Full” and “incremental” describe how the copies are built, not whether they are trustworthy.

A full backup copies the selected dataset

A full backup captures the selected files, database dump, image, or other dataset as a new complete backup set. Full copies are straightforward to reason about but can require more time, bandwidth, and storage.

An incremental backup records change

An incremental strategy stores changes since an earlier backup according to the backup system’s design. This can reduce repeated data transfer and storage, especially when the protected dataset is large and daily change is relatively small.

Restore complexity matters

A backup plan that creates tiny daily jobs can still be a poor fit if recovery requires a fragile or excessively long dependency chain. Understand how the software reconstructs the requested restore point and what happens if part of that chain is damaged.

Retention changes the storage calculation

Capacity depends on the live dataset, change rate, compression and deduplication behaviour, how many restore points you retain, and whether old full copies are recycled. Measure real growth over time and revise the capacity model as the dataset changes.

Verification is more important than the label

Whichever method you choose, monitor job failures, protect backup credentials, keep copies away from the live system, and perform restore tests. A beautifully efficient incremental chain that cannot be restored is not a successful backup.

Next step

Compare full and incremental backups, including storage use, backup windows, restore chains, retention, verification, and why the right strategy depends on recovery goals.

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