Database Backups vs File Backups
Most applications are made of two very different things: the files that make up the code and uploads, and the database that holds your live data. Backing up one without the other leaves you with half a system.
Understanding the distinction explains why our backup plans always cover both, and why they are sometimes handled differently.
Two Different Kinds of Data
Files change relatively rarely; databases change constantly as people use the system.
- Files: code, images, documents and other uploads.
- Database: orders, accounts, content and settings.
- Together: both are needed to fully rebuild a working site.
Why They Are Backed Up Differently
Databases need a consistent snapshot taken with the right tools so that a backup is not captured mid-change. Files can usually just be copied. We use the correct method for each.
Keeping Them in Sync
The two also need to line up in time. If your file backup and database backup are taken hours apart, a restore can leave records pointing at files that do not yet exist, or vice versa. We coordinate both so a restore produces a coherent, working system rather than a mismatched one.
| Type | Changes | Backup method |
|---|---|---|
| Files | Occasionally | File copy / sync |
| Database | Constantly | Consistent dump or snapshot |
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.