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

Offsite backup strategy: keep a recovery copy outside the failure domain

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

An offsite backup strategy puts a recovery copy outside the failure domain that can destroy production. “Offsite” should be defined by realistic threats: separate storage system, account/credentials, physical location or provider boundary as needed, plus a restore path that still works when production access is gone.

Name the failure domain you are escaping

A second disk in the same server protects against some disk failures but not server theft, controller failure, ransomware with root access, account deletion, or site loss. A provider snapshot may escape a guest disk but still share account/control-plane risk.

Choose the independent boundary based on the incidents that matter.

Separate destructive credentials

If a compromised production server can authenticate to the backup system with permission to delete every historical copy, malware can erase both. Use append-only/immutable features where available or credentials with narrower rights.

Protect the backup account with independent MFA/recovery and monitor deletions.

Plan transfer and retention economics

Estimate backup bytes, daily change, schedule, retention, bandwidth window, and restore egress/time. Compress/encrypt appropriately and avoid saturating production during peak traffic.

Monitor both repository capacity and transfer duration as data grows.

Practice recovery without production

Assume the source account/server is unavailable during drills. Retrieve credentials, select a recovery point, restore onto a clean destination, and verify the service.

  • Define the failure domain.
  • Separate deletion credentials.
  • Budget transfer/retention.
  • Drill with production assumed lost.

Next step

Separate backup copies from the production account, server and location where appropriate, then test access during the kind of outage the copy is meant to survive.

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