WordPress Database Backup 
Announcing the WordPress Database Backup plugin!
This is an easy-to-use plugin to quickly backup your WordPress database. You may download the backup file, or have it emailed to the address of your choice.
Click Manage -> Backup:
By default, the core WordPress tabels are backed up. You may select additional tables, if any, and choose how you'd like to receive your backup file. Then simply click Download!
But wait, that's not all!
If you also have WP-Cron installed, you'll be able to schedule daily backups of your database, sent direct to your Inbox!
Installation
Please be sure to read the installation instructions included in the zip file. For the impatient, here they are:
- Create a directory
/wp-content/backup/inside your WordPress directory.
$ cd wordpress/wp-content
$ mkdir backup - Make this directory writable by your webserver.
$ chgrp www-data backup
$ chmod g+w backup - Insall and activate the plugin
- Navigate to Manage -> Backup
- Backup!
- None
- This will save the database backup in your
/wp-content/backup/directory on your server. This is provided as a convenience only. Please do not leave your database backup files lying around! - The backup file will be emailed to the address you specify. Gzip compression is strongly encouraged. Once delivered, the backup file will be deleted from the server.
- Download
- The backup file will be sent to your browser, where you can save it to your local workstation. Gzip compression is strongly encouraged. Once downloaded, the backup file will be deleted from the server.
- PHP memory limit: server operators can limit the amount of memory a PHP script may use. If the size of your database backup exceeds this limit, the backup will not succeed.
- PHP time out: server operators can limit the amount of time for which a PHP script may run. If it takes longer than this amount of time to backup your database, the backup will not succeed.
- Email attachment file size limitations: many email providers do not accept email attachments greater than a certain size. If your database backup is excessively large, it may not make it to your Inbox.
- insufficient disk space: although extremely unlikely, if your server does not have space to store the temporary backup file, the backup will not succeed.
Delivery Method Details
The Fine Print
This plugin works for me. Currently, I have about 160 posts, with a little over one thousand comments. A gzip compressed backup of my database produced with this plugin is about 460 KB. This plugin was successfully tested on another blog with 1369 posts and 4000 comments. The gzipped backup file was ahout 1.3 megabytes, and was successfully emailed and downloaded. If you have a huge database (tens of thousands of posts and comments) this plugin may not work for you, for any of the following reasons:Please note that including the database tables for your plugins in the backup is likely to introduce any (or all) of the problems listed above. Plugins like user and statistics tracking, or spam filter logs, can grow to enormous sizes.
Finally, although this plugin works for me, I will not accept any responsibility for any problems that this may cause for you. Use this plugin at your own risk.
Download WP-DB-Backup 1.4 today!
Thanks go to the following people for helping me develop and test this plugin:
the details
- Published 2005-07-13
- Tagged general, wordpress, plugins and wp-db-backup
- 157 comments
wp-cron-db-backup.php: the functionality provided by the supplemental plugin has been included into the file you downloaded. I will update the documentation to remove mention of the now-non-existentwp-cron-db-backup.php.foreachovernull- ignore the contents of theforeach loopand other's won't. :( I'm using 4.3.11 here and it foreach's over null's fine. A quick workaround for anyone until this is fixed by skippy is to ensure that you have a least one post/page, one comment, and one link on your site. I suspect that comments/links are the likely culprits for most people.mysqldump --opton your database.www-datais the group used by default on Debian systems; Red Hat uses (I think)nobody. Others may useapache, or something else. You may need to contact your host to find out.register_globals. The WP-DB Backup documentation specifically recommends mode 600 or 660, but as the comments here indicate some people have success only with 777. On my blog, I use this plugin just fine with mode 660. But don't take my word for it. Try it for yourself. If this plugin doesn't work for you, or if it works in a way that you find less-than-ideal, then simply don't use it. There are plenty of other ways to backup your blog.