Schedule complete automatic backups of your WordPress installation. Decide which content will be stored (Dropbox, S3…). This is the free version
BackWPup uses WordPress’ own cron job system (WP Cron) to execute scheduled backup jobs. In order for WordPress to “know” when to execute a job, its “inner clock” needs to be set regularly. That happens whenever someone (including yourself) visits your site. If your site happens to not being visited for a period of time, WordPress’ inner clock gets sort of slow. In that case it takes an extra server-side cron job to regularly call http://your-site.tld/wp-cron.php and tell WordPress what time it is.
A simple way to find out whether WP Cron works as it should on your site is to create a new post and set its publishing date to some point in the future, i.e. 10 minutes from now. Then leave your site (that’s important), come back after 11 minutes and check whether your scheduled post has been published. If not, you’re very likely to have an issue with WP Cron.
That means a backup job has started, but BackWPup doens’t know where to store the backup files. Please cancel the running job and re-edit its configuration. There should be a Tab “To: …” in your backup job’s configuration. Have you set a backup target correctly?
if ( !defined('ABSPATH') ).
define( 'ALTERNATE_WP_CRON', true );
Not really a solution, but a way to identify the real problem: see remarks on WP Cron at the top.
BackWPup performs a simple HTTP request to the server itself every time you click
run now or whenever a backup job starts automatically. The HTTP response test message could mean:
* Your host does not allow loop back connections. (If you know what
WP_ALTERNATE_CRON is, try it.)
* Your WordPress root directory or backup directory requires authetification. Set username and password in Settings->Network.
* The Server can’t resolve its own hostname.
* A plugin or theme is blocking the request.
* Other issues related to your individual server and/or WordPress configuration.
Please set CHMOD 775 on the /wp-content/ directory and refresh the BackWPup dashboard. If that doesn’t help, try CHMOD 777. You can revert it to 755 once BackWPup has created its folder.
Up to now, there is no feature in BackWPup to restore a backup. But we are eagerly working on a restore functionality, which is in beta right now. If you like to participate to test the restore feature, please write an email. Meanwhile you can follow these instructions from the WordPress Codex or this tutorial (also Codex) for more detailed information on cPanel, Plesk, vDeck and others.
Go to Settings->General and disable “Display folder sizes on files tab if job edited”. Calculating folder sizes can take a while on sites with many folders.
Try opening the text file in an editor software like Notepad++ (Windows) or TextMate (Mac) to preserve line-breaks.
Go to Settings->Jobs and try a different option for “Reduce server load”.
Yes. Go to your BackWPup temp directory and find a file named
backwpup-xyz-working.json where “xyz” is a random string of numbers and characters. Delete that file to cancel the currently running backup job.
Yes. You need to have writing access to the wp-config.php file (usually residing in the root directory of your WordPress installation).
if ( !defined('ABSPATH') ).
define( 'WP_TEMP_DIR', '/absolute/path/to/wp/your/temp-dir' );
/absolute/path/to/wp/with the absolute path of your WordPress installation and
your/temp-dirwith the path to your new temp directory.
Requires: 3.8 or higher
Compatible up to: 4.5.3
Last Updated: 5 days ago
Active Installs: 400,000+
21 of 71 support threads in the last two months have been marked resolved.
Got something to say? Need help?