Drupal backups
Encrypted backups and restores for Drupal sites
The module compresses and encrypts the database and files on the client's server, then uploads them to storage. A restore puts tables and files back without disconnecting the site from the platform.
The problem
A Drupal restore has more traps than it seems.
Restoring an old database also brings back the list of enabled modules, the routes and the caches of that moment. If the backup module was not enabled then, it disappears after the restore.
Drupal's database layer gives braces and semicolons special treatment: a dump reimported through it can corrupt content.
How it works
How we do it on Drupal.
- 1
Own connection
Dump and restore use a direct PDO connection with the credentials from
settings.php, so data comes back byte for byte. - 2
Module state
Before swapping the tables we save the module's connection, enabled state and routes, and put them back right after.
- 3
Caches
We empty the cache tables: Drupal rebuilds the container and routes on the next visit.
In detail
In detail.
- Drupal 7 and 8.9 to 12 beta, tested with a real restore of a value and a file
settings.php,settings.local.phpandservices.ymlstay as they are now, unless you choose otherwise- In Composer projects the backup covers the web folder:
vendor/andcomposer.jsoncome back withcomposer install - Needs MySQL or MariaDB
- Restores also from the offline file, which reads the database details from
settings.php
FAQ
Frequently asked questions
Can I leave out the images?
Yes, the profile without uploads skips the site's public files folder.
Does it work with PostgreSQL?
Backups do not, today only MySQL and MariaDB. Monitoring and security work with any database.
Related features
Goes well with
Try it on your clients' sites.
During the beta we let in a few agencies at a time and set up the first sites with you.