Most businesses only find out whether their backups work on the worst day possible: after a server failure, a cyberattack or a mistake that wiped important data. By then it's too late to fix the backup plan.
Here's what a backup plan you can trust looks like.
A Backup Isn't Just the Database
A complete ERPNext backup has three parts:
- The database, with all your transactions and records
- Your files: attachments, scanned documents, images and private files
- The site configuration, including the encryption key ERPNext uses to protect stored passwords and credentials
Many backups capture only the first. Without the files and the key, a restore leaves gaps.
The Four Rules
1. Back up every day, automatically. Nobody should have to remember to run a backup.
2. Store copies somewhere else. A backup on the same server is lost along with that server. Keep encrypted copies in separate storage.
3. Keep enough history. If a problem goes unnoticed for a week, yesterday's backup already contains it. Keep at least 30 days of backups.
4. Test a full restore regularly. A backup that has never been restored is a hope, not a plan. Restore it onto a separate system every quarter and check that everything is there.
Questions to Ask Your Provider
- When was our last backup, and where is it stored?
- Are files and configuration included, not just the database?
- How many days of backups do we keep?
- When did you last test a restore, and how long did it take?
- If our server failed today, how long until we're working again?
If the answers are vague, it's time to act.
How We Handle It
On Ultrasoft's managed service, backups run daily, are encrypted and kept for 30 days, and a full restore is tested every quarter. The most you can lose is one day's work.
Not sure your backups would hold up? Book a discovery call and we'll check them with you.