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

Snapshots vs backups: know which failures each recovery method can survive

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

A snapshot records storage or filesystem state at a point in time, often quickly and efficiently. A backup is a recoverable copy designed to survive loss of the source. Snapshots can be excellent rollback tools, but snapshots stored only on the same platform are not automatically independent backups.

Identify snapshot scope and consistency

Determine whether the snapshot captures one filesystem, volume, entire VM, or storage dataset and what happens to attached/external data. Crash-consistent snapshots may need database recovery on boot; application-consistent snapshots coordinate writes before capture.

Read the specific platform semantics before depending on memory/state claims.

Map snapshot failure domain

If snapshots depend on the same storage pool, account, provider, or credentials as production, they may disappear in the same incident. Replicating/exporting them to an independent target changes that risk.

Do not count a local ZFS snapshot as an offsite copy.

Use snapshots for fast short-term rollback

Before upgrades or configuration changes, a snapshot can make rollback quick when discarding all post-snapshot writes is acceptable. For active transactional systems, define how newer writes are protected.

Set snapshot retention so old points do not silently consume all storage.

Pair with tested backups

Maintain independent versioned backups for source loss and verify restores onto a clean destination. Measure both snapshot rollback and full backup recovery.

  • Know snapshot scope.
  • Identify shared failure domain.
  • Use for controlled rollback.
  • Keep independent backups.

Next step

Compare snapshot speed and storage coupling with independent backup retention, application consistency and offsite recovery before relying on one mechanism.

Explore DotMoose backup storage

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