Docs Navigation Open
Backups
Back up files and database before updates, migrations, and any risky operational change.
A useful backup always includes both files and the database. Backing up only one of them is not enough for a real restore.
What to Back Up
- project files and custom code
- uploaded assets and media
- templates, chunks, snippets, plugins, and modules
- database dump
- environment-specific notes needed to reconnect the site
When to Back Up
- before updates
- before replacing extras
- before deployment or server migration
- before large structure or content changes
Restore Checklist
- restore files
- restore database
- verify configuration and paths
- clear cache
- log into manager and test frontend pages
A backup is only trustworthy if you know how to restore it.
Previous
Security
Keep the manager protected, use limited permissions, and review legacy code and extras carefully.
Next
Updating Evolution
Update carefully: back up first, preserve customizations, run the updater, and verify the install is closed again.