ProcessDatabaseBackups by Ryan Cramer

Create and/or restore database backups from the ProcessWire admin.

Manage database backups for ProcessWire

Read this blog post about this module

This tool provides an admin interface for the following database backup functions:

  • Creating new backups
  • Uploading backups
  • Restoring backups
  • Providing info on existing backups
  • Managing existing backups (downloading, deleting, etc.)

This is meant to be used as a secondary backup tool, not a primary one. It uses ProcessWire 3.x WireDatabaseBackups class to perform backups and restores. If you are working with really large files, it may be better to perform that task directly in PhpMyAdmin or the native MySQL client.

Requires ProcessWire 3.0.62 or newer.

License: MPL 2.0

Copyright 2021 by Ryan Cramer

Install and use modules at your own risk. Always have a site and database backup before installing new modules.

Twitter updates

  • ProcessWire 3.0.192 (dev branch) contains 11 issue fixes and 5 pull requests, over 20 commits— More
    7 January 2022
  • ProcessWire 3.0.191 core updates: updates to the installer and the profile exporter module— More
    24 December 2021
  • This week ProcessWire went on a diet, trimming the core size from 15.5 MB down to 7.5 MB by moving optional site profiles into their own GitHub repos— More
    17 December 2021

Latest news

  • ProcessWire Weekly #402
    In the 402nd issue of ProcessWire Weekly we'll check out ProcessWire 3.0.193, highlight recent ProcessWire projects and resources, and more. Read on!
    Weekly.pw / 22 January 2022
  • ProcessWire 3.0.190 core updates
    ProcessWire 3.0.190 has 15 commits relative to 3.0.189 and contains a mixture of issue resolutions and feature additions. This post covers them all, in addition to updates for the PageAutosave and ProFields Table modules.
    Blog / 3 December 2021
  • Subscribe to weekly ProcessWire news

“…building with ProcessWire was a breeze, I really love all the flexibility the system provides. I can’t imagine using any other CMS in the future.” —Thomas Aull