– If thats the flow, will it choke up the server’s storage ?

“It would be nice if it was possible to download just the database file from the backup. Currently waiting for an email of the backup, so I can sift through it.

I’d accidentally deleted some users from a WordPress database, and just wanted to download the SQL and copy the info back over. Alas!”

I believe there are some plugins that does that.

If your website is unavailable, there are several methods you can use to restore your site, and The Hub will instruct you on what steps to take.

This is a great feature!

I’d accidentally deleted some users from a WordPress database, and just wanted to download the SQL and copy the info back over. Alas!

Hi there Baldafrican and thanks for the comment :)

It’s true that “the Amazon S3 integration merely stores a copy of your backup that was made to wpmudev storage”. That’s because of our incrementality feature that can be applied only if the backups get through our own storage first.

That being said, we do intend to make the Storage Limit on WPMU DEV storage user-configurable (instead of hardcoded to 30 backups, as it currently is) really soon.

That would be mean that the user will be able to select to keep, for example, just 1 backup on WPMU DEV storage (1 being the minimum possible value for that storage limit) and, say, 20 backups on their AWS S3 storage.

Doing that, would mitigate costs for the user and allow them to keep the majority of backups on the storage of their choice (Google Drive, Dropbox, FTP integrations coming up with the next Snapshot releases!).

I hope this change/feature will help us win you over :)

Best regards,
Leonidas

I think it is worth pointing out (..and correct me if I am wrong) but the Amazon S3 integration merely stores a copy of your backup that was made to wpmudev storage. It does not change your storage of your backups exclusively to Amazon. Using this method I would need to pay for both services once the size of the backup got larger.

I hope this will change in the near future but until then updraft does the job for our wordpress sites.

Hi Alexandre and thanks for the comment.

I’m afraid that there’s no easy way of saying the required server configuration as it depends on too many variables, not only the server resources but also site size, plugins and themes installed, additional folders (like caching or leftovers from other backups) etc.

All of those come into play so it can really be installation-specific, I for example, have some of my test sites on (probably) cheapest shared hosting out there, and backups work for me without any issues.

So there are a lot of factors to consider but for any troubleshooting you can always reach out to our support and we’ll gladly help out :)

Best regards,
Predrag

You should specify in your post the necessary configuration of WordPress for backup to go smoothly.

I set up the weekly automatic backup on 10 sites hosted on shared servers, I came back to see the status of backups 1 month later. No backups have been made on any of my 10 sites. Backups have always failed. In the logs I saw errors like “napshot_failed_SiteNotRespondedZipstreamError” or “snapshot_failed_SiteNotRespondedError”. Yet most of my sites had between 3 and 10 pages without heavy photos and with the Twenty Ten theme.

Through Snapshot Pro user guide I managed to solve the problem. But I think readers should know that it’s better to have a rather beefy WordPress configuration