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.

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 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.

Want to try it on a real site? The 30-day trial needs no credit card.

Start free trial

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.

Try it on your clients' sites.

Connect your first sites today and see what SitePing finds on them.

  • Every Complete feature except backups
  • Up to 10 sites
  • No credit card needed to start
  • At the end you choose a plan or move to Free, and nothing is charged
Start the 30-day trial

Already have an account? Log in. Prefer to look at one site first? Free read-only audit.