stemcelltechnologies

Thanks for the quick reply!

I suspected that may be the case unfortunately… I’m looking for a simple click to restore option so perhaps this plugin isn’t going to work for us.

This is not a live site but the database is technically in use as I’m logged into the WordPress site to perform the restore.

This is a test environment that can be spun up from a template in ~15 mins. Once up the plan was to simply install a plugin, connect to the S3 bucket, pull down the backup and restore it. Having to manually restore the database outside of WordPress or to a 2nd database then switch it is a bunch of extra effort I’m looking to avoid.

Compared to some other plugins though your scheduled backups to S3 works perfectly and is one of the better ones I’ve used.

Seems to be a lot of these time out support posts popping up…

As there doesn’t appear to be any working solution we gave up on waiting and switched to the BackWPup plugin which is working well for daily scheduled backups.

We are seeing the same error message for scheduled backups as well (manual to S3 works fine), very interested to hear the resolution if you do manage to resolve the issue.

Our enviro is a little different – running self managed AWS stack (EC2 + RDS + ELB) however I would not be surprised if GoDaddy is using similar or the very same AWS cloud based architecture for their managed service.

Nothing should be blocking the EC2 server from communicating with “itself” (internal firewall is fully open), no security plugins are enabled either and still seeing the error.

For anyone else who may end up searching for the same thing – it just costs more to have this option available, you need “Developer”:
https://backup-guard.com/products/backup-wordpress#pricing
“Specify cloud subdirectories” in the comparison chart.

We just created a separate dedicated S3 bucket for the site.