A backup only helps if you can restore it
Make a simple recovery plan for your app files, database and settings, then test it away from production.
App Cities · 2 min · Updated
A backup job marked successful is useful, but it is not the whole test. You need to know what it contains and how to use it. A copy of the code may not include the database. A database copy may need the matching app version.
The steps
- List the data you need to recover: database records, uploads, app version and required settings. Store secret values securely, not in a public backup.
- Check when backups run and how long they are kept. Decide how much recent work you could afford to lose.
- Restore into a separate test environment. Do not overwrite the live app just to see whether a backup works.
- Open the restored app and check important records and files. Record the steps and how long the restore took.
A common question
How often should I test a restore?
Test before relying on the service, after major storage changes and on a schedule that fits the value of your data.
Ready to try your project?
Prepare your project, check the prices and choose how you want to deploy.