Setting Up a Server Backup System
Contents
Article
Backups are what people remember once it is already too late. A reliable backup system protects against data loss from failure, mistake or compromise — provided it is automated, offsite and verified by restore.
The principles of reliable backup (3-2-1)
- 3 copies of the data;
- 2 different media or locations;
- 1 copy offsite (away from the server).
What gets backed up
- site files and configuration;
- databases (consistent dumps);
- mail where required;
- system settings.
Tools and offsite storage
I use restic or borg (deduplication, encryption) with storage in S3 or a separate repository. Backups are encrypted, so even if the storage is compromised the data stays protected.
The crucial part: restore verification
A backup that does not restore is worth nothing. So periodic restore verification is configured too, not merely the creation of copies.
Rotation
A retention policy is set (daily/weekly/monthly) so you have depth of history without filling the storage.
Common questions
Where should backups be stored?
Offsite: S3-compatible storage or a separate server — not on the same disk.
Are backups encrypted?
Yes, restic and borg encrypt by default.
Do you verify restores?
Yes, that is a mandatory part of the work.
No reliable backups? I will set up an automated system with restore verification.
