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

ZFS snapshot planning: use retention and naming that make rollback understandable

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

ZFS snapshots are cheap point-in-time references to existing blocks until data changes. They are useful for rollback, accidental deletion recovery, replication, and short-term history, but they consume space as changed blocks remain referenced and share the source pool unless replicated elsewhere.

Choose snapshot points around change risk

Create snapshots before upgrades, configuration changes, deployments, bulk data operations, and on a schedule tied to recovery needs. Databases may need application-aware quiescing/dumps when a filesystem-consistent point is not enough.

Name snapshots predictably with timestamps/purpose so operators can select them under pressure.

Set retention from change rate

Snapshot “size” reflects referenced changed blocks and can grow unexpectedly when large files/databases are rewritten. Monitor dataset used/available space and per-snapshot referenced behavior.

Automate pruning carefully and protect special pre-change snapshots when required.

Understand rollback versus clone/restore

Rolling a dataset back can discard all newer snapshots/data depending on command/path. Cloning or copying selected files from a snapshot may be safer when only one mistake needs recovery.

Practice the exact recovery method in a non-production dataset.

Replicate for independent backup

Use ZFS send/receive or another backup path to copy recovery history to separate storage when source-pool loss must be survivable. A local snapshot alone is not offsite protection. Verify the replicated destination can be imported or restored without depending on the failed source pool.

  • Snapshot before risky changes.
  • Monitor retained changed blocks.
  • Choose rollback/clone deliberately.
  • Replicate outside source pool.

Next step

Choose snapshot frequency and retention from change rate and recovery needs, monitor space use, and replicate important recovery points outside the source pool.

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