About Cronjob Database Backup
Periodic automatic backup of the database. Set interval in settings.
|Category 1||Admin Helpers|
Admin helper modules are those that provide helpful tools, UI enhancements or optimizations to the admin panel (excluding Fieldtype or Inputfield modules).
|Category 2||Development Tools|
Modules that have more to do with assisting development of a site rather than managing its content.
|Category 3||Process Modules|
Process modules are apps that run in the ProcessWire admin.
|Category 4||Proof of Concept|
Proof of concept modules are designed as examples or starting points for others to build from. May not be ideal for users wanting to plug-n-play.
Should be safe for use in production environments. *
|Compatibility||2.5, 2.6, 2.7, 3.0|
|Date Added||November 7, 2014|
|Last Updated||August 11, 2019|
This module's files should be placed in /site/modules/CronjobDatabaseBackup/
How to install or uninstall modules
Auto backup of your database. Triggered periodically by a cycle interval or via user logout.
Use 'Process Database Backup Module' to restore from backup or delete them.
This module could slow down your processes since backups may take some time,
depending on how much there is to backup. This cronjob (hooks on LazyCron) is executed by a call to module: ProcessPageView.
Each run is logged in site/assets/logs/messages.txt.
Select a time interval for automated database backups or one of the options to force backup after a user (role) with 'trigger-db-backup' permission assigned has been logged in or logged out. Permission 'trigger-db-backup' will be added with module installation. You just need to assign it to certain roles. If you want to disable automated backups choose 'never'. No need to uninstall the module for this. (default: every 4 weeks)
Maximum Number of Backups
Select how many backups you want to keep in the storage. Minimum 1, default and maximum 100 (defined in constant MAXFILES). Executed with each cron.
Remove backups older than
Will remove backups older than selected time interval with each cron.
Choose a name for the backup files. No older file will be overwritten. If left blank default setting is the name of the database (set in config) with a number suffix (counter) to make it unique. Name format syntax: # placeholder for db-name. Escape date() format with surrounding %. If filename exists a unique filename will be generated: [filename]-[n].sql. Allowed types: A-Z, a-z, 0-9, #, %, dash and underscore.
Define custom fileinfo string here. Format syntax: # placeholder for db-name. Escape date() format with surrounding %. Any $user property surrounded with curled brackets will be replaced by the corresponding value. If left blank default setting will be 'backup made by CronjobDatabaseBackup'.
Path to custom storage directory. If left blank or path doesn't exist default pass will be used. (The Path is displayed under the field. Normally: /site/assets/backups/database/)
By default, the backup will include all tables. If you only want certain tables to be included, select them from the list.
Remove backups now
Select how many backups you want to keep in storage. Klick SAVE to execute.
Not a real requirement but ProcessDatabaseBackups.module is useful to restore the database from a file or to delete older backup files.
I took some nice code from ProcessDatabaseBackups.module. Thanks to Ryan!
kixe (Christoph Thelen)
- Admin Helpers
- Core Modules
- Development Tools
- Field Types
- Input Fields
- Language Modules
- Language Packs
- Markup Generation
- Premium Modules
- Process Modules
- Proof of Concept
- Site Profiles
- Social, Feeds, Services
- Text Formatters
- Other Modules
- Users and Access
*Use modules at your own risk. There are no guarantees or warranties. It is recommended that you backup your site and database before installing new modules.