Brand new default installation doesn't work.

And now, I’ve managed to get it working, by disabling the “Restart the job on every main step on a working job” setting.

Since the default settings had that turned on, I only found that by chance (it was a guess this might be the problem because the job would always stall after the first step).

I might still have a problem with wp-cron, but my guess is that’s a service-provider problem, and hopefully I can work around that with either a cron job making a call to wp-cron or the “with a link” schedule start setting. I’ll leave it set as a scheduled backup overnight and see if it works — if not, I’ll try setting up a cron job as said.

Of course, the problem isn’t really resolved because not being able to kick off the restarts may mean I run into problems with larger backups — but I’m done investigating for now.

Thanks for the plugin — I submit the above as it may help with your diagnosis and/or help you to improve the documentation.

Ok, that ran overnight on wp-cron, so other than performing a test-restore, I’m done testing until I roll out to other blogs.

Thanks for your help Daniel — if you want me to test anything else, please let me know — as you know, I’m still having a trouble with the “run now” which gives the response

“couldn’t connect to host”The HTTP response test get a false http status ()

but I can get around that on the rare occasion I need to by having a second job that is set to use the nonce call, or just temporarily setting the schedule on this job to that.

Thanks again — if you want to mark this as resolved, feel free — I can always raise another thread later if necessary.