UPDATE: Due to some problems with the WordPress.org plugin repo, we needed to release AWB 2 with the current feature set. The feature mentioned below will be going into beta soon.
We were going to be releasing AWB 2.0 soon (like a week ago) but now we’re reworking a gigantic part of the plugin so that it doesn’t backup the entire site as one big zip, but instead uploads each individual file and only uploads files that have been changed since the last update. This will have 3 main benefits:
- Cuts down on wasted bandwidth
- Cuts down on wasted storage on s3 (even though it’s dirty cheap)
- Allows gigantic sites to be backed up without a ton of memory issues.
We’re going to be dropping at least one more beta pretty soon and then release the final version of v2. It’s going to be fantastic!
{ 11 comments… read them below or add one }
Are you still going to allow for an option for us to zip up the whole site as one big package? For those of us with more memory and/or smaller sites ….
Also – how will this effect site recovery? will it be automatic/transparent? will we be able to recover from a specific date since this is essentially an incremental backup?
Thanks
Good questions Matthew.
> Are you still going to allow for an option for us to zip up the whole site as one big package? For those of us with more memory and/or smaller sites …
It would be expensive and a big hassle to maintain as we continue improving the plugin so we’re not going to have the option to zip up the files.
> how will this effect site recovery? will it be automatic/transparent? will we be able to recover from a specific date since this is essentially an incremental backup?
You’ll still be able to restore from a specific date, given that you’ve got WordPress installed and the AWB 2.0 plugin activated.
We’re working out the details of how a manual restore (without WP + AWB installed) would go. We likely won’t have a way to do a manual restore in the next version but it’ll be the next priority after we release.
How about support for Multi Site WordPress 3 and WPMU? I’ve tried using the RC and it works but missed one pretty big directory for WPMU and WP3 MultiSites which is blogs.dir.
hello!
no plans for option for saving on my own server/account?
regards
mike
Additional storage options will not be added in this version but they are in the plans.
sounds very nice melvin!
if I can do a complete backup on the entire blog or choose to backup certain directorys – and save it on my own server/host – then I´ll start use this plug!
keep up the good work!
I return…;)
regards
mike
Why? S3 is secure and cheap. I wouldn’t choose no backup over s3 backup in the mean time.
Hey folks,
I actually put in the line of code to get the blogs.dir directory for WPMU and WP3.0 Sites with Multiple Sites enabled. Just add to line 683:
$backups[] = WP_CONTENT_DIR . ‘/blogs.dir’;
Love the plugin, great job.
Thanks mentioning that Jose. We’re going to add support for WP 3 soon but this will help people in the mean time. Also, glad you love the plugin. Hope you’ll share your thoughts on it in a review somewhere.
The backup “only uploads files that have been changed since the last update.” So if I do want to backup all files, can I somehow trick the plugin by saying that the last update was, say, Jan. 1, 2000?
Not able to download the plugin. The URL http://downloads.wordpress.org/plugin/automatic-wordpress-backup.zip is broken. Returns 404. Any other source to download the plugin?