On-demand backup of your WordPress database.
Briefly, use phpMyAdmin, which is included with most hosting control panels. More details and links to further explanations are here.
Although WP-DB-Backup provides the option of saving the backup file to the server, I strongly discourage anyone from leaving backed-up database files on the server. If the server is not perfectly configured, then someone could gain access to your data, and I do not want to make it easy for that to happen.
If you edit the text of wp-db-backup.php in a text editor like Notepad, you’ll see around line 50 the following:
/** * Set MOD_EVASIVE_OVERRIDE to true * and increase MOD_EVASIVE_DELAY * if the backup stops prematurely. */ // define('MOD_EVASIVE_OVERRIDE', false); define('MOD_EVASIVE_DELAY', '500');
Do what it says: un-comment MOD_EVASIVE_OVERRIDE and set it to true like so:
That will slow down the plugin, and you can slow it even further by increasing the MOD_EVASIVE_DELAY number from 500.
Better yet, put the lines that define the
MOD_EVASIVE_DELAY constants in your wp-config.php file, so your settings don't get erased when you upgrade the plugin.
This files is used by non-English users to translate the display into their native language. Translators are encouraged to send me translated files, which will be made available to others here: http://austinmatzko.com/wordpress-plugins/wp-db-backup/i18n/ http://plugins.trac.wordpress.org/browser/wp-db-backup/i18n/
Because it's a fairly safe bet that the core WordPress files will be successfully backed up. Plugins vary wildly in the amount of data that they store. For instance, it's not uncommon for some statistics plugins to have tens of megabytes worth of visitor statistics. These are not exactly essential items to restore after a catastrophic failure. Most poeple can reasonably live without this data in their backups.