I followed the instructions on that page and the clicking the “Debug Full Backup” button returned a 500 error.
The advice on the page says that if this happens it’s likely to be a conflict with caching plugin – but the site has none.
Or that it’s password-protected by HTTP .htaccess – it isn’t.
Or that I should try re-configuring my wp-config.php with the new command – that didn’t solve the issue.
The info then says my hosting provider may have disabled loopback connections that allow WordPress to run its scheduler. My hosting company says it has not done this. Furthermore, the scheduler is not broken anyway since I successfully made scheduled posts.
Frankly this seems more trouble than it’s worth.