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

VPS backup strategy: protect the data you cannot rebuild

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

A VPS backup strategy should recover the service after losing the VPS, not merely create another file on the same virtual disk. The strategy starts from data classes, acceptable loss, rebuild requirements, retention, and a restore test on independent storage.

Separate rebuildable system from irreplaceable state

Operating-system packages and application code may be reproducible from configuration or repositories, while databases, uploads, keys, configuration, and user-generated data may be unique. Back them up according to how quickly each changes.

Document the versions and secrets needed to rebuild infrastructure that is not captured as data.

Choose backup timing from acceptable data loss

A database receiving orders every minute needs a different schedule from a static brochure site. Define the recovery point objective from the business impact of lost writes. “Nightly” is not automatically the right schedule.

Coordinate database-consistent dumps or snapshots with the application’s write behavior.

Keep copies outside the VPS failure domain

A local snapshot can be convenient but should not be the only copy if account compromise, storage failure, or accidental deletion could remove both production and recovery data. Use an independent destination with separate credentials.

Encrypt sensitive backup data appropriately and protect the encryption/recovery keys separately.

Restore into a test destination

Regularly rebuild or restore enough of the service to prove archives are readable, database state is coherent, configuration is present, and operators know the steps. A successful upload log is not a restore test.

  • Classify data by change rate.
  • Define acceptable data loss.
  • Use an independent destination.
  • Run scheduled restore drills.

Next step

Design VPS backups around application state, databases, configuration, retention, offsite copies and tested restores instead of relying on one server image.

Plan independent backup storage

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux 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