A few words of caution though to anyone that tries it. As previous user commented keeping backups in the wordpress directory poses quite a security risk as anyone can just download the tarball. Keep the backups in a directory that’s not accessible through the website.

A little modification to make life yet a bit easier:

Add a line below the directories array to handle the database names.
directories=(/home/dir1 /home/dir2 /home/dir3)
databasenames=(db1 db2 db3)

Then replace wp_db in the mysqldump connection strin g with ${databasenames[$i]}

Make sure the database names are in the same order as the directory. This can be done for the database users as well. I wouldn’t recommend keeping the passwords there though…

Good luck!

/Patrik

Thank you for the script. I found some additional ways to automate the upgrade. Also, the script creates some security issues, as it keeps a tarball with a somewhat predicable name in the document root directory, so I moved the storage location for the backups outside of the document root.

The updated script can be found here: http://www.jerry-bell.com/2008/04/29/wordpress-backup-script/

I’m sure my code can be improved on – I’m not the worlds best coder, but I am pretty lazy and motivated to find ways to automate things.

Jerry

The second thing i’ll extend: if there’s no wp_images and so on, there souldn’t be any scary error messages from cp.

The biggest problem i had in upgrading, the “latest” 2.1.2 latest.tar.gz was a plain TAR, shame on wordpress.org

Greg