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 scrub planning: how often to verify stored data and mirror health

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

ZFS scrub planning is about finding latent checksum/read problems while redundant copies still exist. The ideal cadence depends on disk size, workload, pool activity, hardware error history, and how long a scrub takes; blindly running too frequently can add unnecessary I/O while never scrubbing leaves silent faults undiscovered.

Measure current scrub duration

Run a controlled scrub and record pool size/allocated data, start/end time, throughput, errors repaired, workload latency impact, and whether any devices show SMART or transport errors.

A scrub that takes days changes how much overlap you should allow with backups or other maintenance.

Choose a cadence shorter than your comfort window

Monthly is common for many always-on pools, but the correct interval is an operational choice. High-risk or archival patterns may justify different schedules.

Never schedule overlapping scrubs; ensure automation detects an existing scrub.

Coordinate with workload and SMART monitoring

Scrubs generate sustained reads. Run them in a window with I/O headroom and continue drive-health monitoring between scrubs. A failed SMART test, growing checksum error, or degraded vdev should trigger investigation without waiting for the next schedule.

Do not cancel every scrub because users notice a small performance change; fix scheduling/capacity instead.

Alert on result, not just timer execution

Capture zpool status after completion and alert on repaired/unrecoverable errors, degraded state, or a scrub that did not finish. Retain history to see error trends by device.

  • Measure scrub duration/impact.
  • Avoid overlap.
  • Pair with SMART/pool alerts.
  • Record and review results.

Next step

Schedule ZFS scrubs around pool size, disk workload and monitoring, then investigate checksum errors and degraded devices instead of treating a scrub as repair by itself.

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