I'm pleased to announce the immediate availability of WP-DB-Backup 1.6!
This version has received a major overhaul, courtesy of Owen:

As you can see from the screenshot above, there's a progress meter now, telling you how far along in the backup process you are. Each table is still backed up individually, but now each table is also backed up just a few rows at a time, to better support tables with huge numbers of rows (as might be found from stats or anti-spam plugins).
WP-DB Backup should now handle databases of all sizes! Indeed, it's been tested successfully on two large databases -- one nearly 10 megs, and one over 32 megs -- as well as several small ones.
WP-DB Backup now also automatically detects gzip support. If available, your backup will be compressed on the fly; if not available, no compression will occur (obviously).
Now that huge databases can be backed up reliably, I have added support for optional tables to be included in the scheduled backups. Remember, though, that most email servers block attachments larger than about 5 megabytes. If you have an enormous database, the scheduled backup email delivery may fail.
French translation available -- thanks Ozh!
About | Policies | skippy.net
/wp-content/plugins/ regardless of whether you store the actual plugin in a sub-directory. So make sure you place the .po and .mo files there, configure WordPress to use Dutch, and then everything should just work.#!/bin/sh DATE=`date +%Y%m%d`; mysqldump --opt -uuser -p'password' database > /home/user/database.$DATE.sql; gzip /home/user/database.$DATE.sql; done; echo "MySQL backup complete."INSERT INTO `wp_Counterize_Pages` VALUES (2, 'blablabla', 2, NULL);But with wp-db backup I obtain:INSERT INTO `wp_Counterize_Pages` VALUES (2, 'blablabla', 2,);and I have an error if I try to restore the database. The table is created by the counterize II plugin Send my an email if you don't understand the problem: i'm not a mysql expert! Sorry for my awful english ;-)