Backups and updates routine
This page is for whoever looks after the site: a technical volunteer, a host or a partner, and the staff member who checks that it is done. "Most expensive incidents on small sites come from missing backups, unapplied updates and nobody watching" (Low-budget operations). The routine below prevents all three.
Contents
Backups
A backup has two parts: the database and the storage directory (uploaded images and files). Both, or the backup is useless.
| Part | How | Source |
|---|---|---|
| SQLite database | sqlite3 <file> ".backup <target>", not a file copy while the site is busy | SQLite database support |
| Other databases | The database's own dump tool | Backups and restores |
| Storage | Copy of var/<site>/storage | same |
| Settings | settings/override/ including the audit keys | The audit trail |
Keep at least one copy away from the server, and protect it: backups hold the same personal data as the site (Donor and volunteer data protection).
Owner's view: Backups.
The restore test
A backup that has never been restored is a hope, not a backup. Every quarter:
- Restore the latest backup to a test location (a laptop or a test host).
- Open the site; sign in; open a page with images and a file.
- Write down the date, how long it took, and what went wrong.
Template: Restore test.
Updates
| What | Why | Read |
|---|---|---|
| Exponential releases | Fixes, including security fixes; a published version never changes, a fix comes as the next release | How updates work, Release line and support |
| Extensions | They are updated with Exponential through Composer | Updates and upgrades |
| PHP and the server | The host's job, or yours on a virtual server | PHP versions and extensions |
Good practice:
- Test an update on a copy first; then apply it to the live site.
- Use maintenance mode for longer work (Maintenance mode and planned work).
- After an update, test the key paths: home, Donate, volunteer form, newsletter sign-up, shop checkout if used.
- The administration's upgrade check helps see what changed (Upgrade check).
- Checklist: Upgrade day checklist.
Cron and logs
- Cron runs newsletters, scheduled publishing, approval publishing, view counts and the audit trail's rotation. Check monthly that it runs (Cronjobs).
- Glance at the logs monthly in the log viewer (Log viewer, Logs for owners).
The calendar
| How often | Task | Who (name) |
|---|---|---|
| Daily (automatic) | Backup runs | |
| Monthly | Backup exists and is recent; updates checked; cron ran; logs glanced at | |
| Quarterly | Restore test; access review | |
| On each release | Update tested on a copy, applied, key paths tested | |
| Yearly | Review host, partner and budget; exp:audit verify |
Put this in the shared calendar. The Monthly checklist and Annual checklist carry the same tasks.
If you have a host or partner
Ask them, in writing (What to ask your host, What to ask your partner):
- To do: How often are backups made, and where are they kept?
- To do: When did you last test a restore of our site? Can we see the result?
- To do: How soon after a release are updates applied?
- To do: Who tells us when something was done?
A maintenance agreement makes it explicit (Maintenance agreement template).
Related pages
- Operations for non-profits
- Maintaining your website
- Backups that restore
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.