Security help › Websites and servers
Backups that actually work
A step-by-step guide for everyone, with fixes for common problems.
Steps
- Decide what you can't lose: databases, game server configs, bot data, website files.
- Follow 3-2-1: 3 copies, on 2 different kinds of storage, 1 somewhere else (not on the same server or account).
- Back up databases with their own tools (pg_dump, mysqldump, mongodump), not by copying the data folder while it runs.
- On the Starter and Team plans the watcher does this for you, locked with your own key: see the guide "Back up your databases (and put one back)".
- Encrypt backups that leave the server.
- Test a restore at least once a month on a spare machine. A backup you've never restored is a guess.
- Keep old versions for at least 30 days, so ransomware that encrypted things last week can still be undone.
What you should see
A test restore gives you a working copy with recent data.
Common problems
- The backup file is tiny or empty The backup command probably failed (wrong password or permissions). Run it by hand and read the error.