SCHEDULED LARGE BACKUP STOPS

The first thing to check is to make sure WP Cron is working correctly and the CYAN Backup job exists. You can use “Cron GUI” from the plugin repository to make sure the “cyan_backup_hook” task exists.

As the exact same code is called for a manual or automatic backup it seems unlikely there is a problem in the backup code itself, more likely a scheduling problem.

In your backup directory to you see partially complete log files for the scheduled backups?

Hi Greg,

I think CYAN backup and WP cron aren’t working together. Now I see it, after installing one plugin to edit cron jobs.

When I set the schedule using CYAN Backup, the cron job sets properly. When the scheduled backup finishes, the cron job completely disappears and won’t execute anymore.

“Next backup scheduled for:” is set to “None” and WP Cron doesn’t shows any cyan backup hook.

But if I set the backup schedule and, BEFORE it executes, I use WP cron to manually edit the schedule (to hourly, daily or even a custom schedule), then IT WORKS. I can see the hook on WP Cron GUI and the “Next backup scheduled for:” is set properly.

I think it’s working now.

Am I doing it right?

Thank you in advance.

The WP Cron job that CYAN Backup creates is a once only job set for the next schedule backup time. Then during the backup job, a new WP Cron entry is created.

Since you don’t see a new entry being created then CYAN backup is getting terminated before it creates the next WP Cron entry.

Let the scheduled backup run and then take a look in the archive directory and see if a log file exists for the backup. Take a look at what the last line is. It should be the size of the backup. If it’s not let me know what it is.

Hi Greg,

The last lines of one the backups no creatint WP Cron entries, are:

[2014-07-28 17:05:24] Elapsed Time: 1.9 minutes
[2014-07-28 17:05:24] Backup complete!
[2014-07-28 17:05:24] Backup size: 853.95MB

As you can see, the last line is the backup size…

Does the backup show up in the list? Does the zip file exist?

Yes, this backup shows up in the list, but after this one the cron job isn’t created.

Well that’s intriguing… I’ll have to take a look at it tomorrow, I might have to send you a debug version of the code to run to get some more details.

The only thing I can suggest of the top of my head is to make sure your timezone is set correctly.

Two other questions:

– What schedule have you set for the backups?
– How long does the backup take to run?

Try this, edit wordpress\wp-content\plugins\cyan-backup\cyan-backup.php, on lines 614-631 you should find the following code:

public function scheduled_backup() {
		$remote_backuper = $this->remote_backuper();

		// Run the backup.
		$result = $remote_backuper->wp_backup();

		// Get the options.
		$options = (array)get_option($this->option_name);

		// Determine the next backup time.
		$this->schedule_next_backup();

		// Send the backup to remote storage.
		$this->transfer_backups( $result['backup'], $options['remote'], 'schedule' );

		// Prune existing backup files as per the options.
		$this->prune_backups( $options['prune']['number'] );
	}

replace it with:

public function scheduled_backup() {
		$remote_backuper = $this->remote_backuper();

		// Determine the next backup time.
		$this->schedule_next_backup();

		// Run the backup.
		$result = $remote_backuper->wp_backup();

		// Get the options.
		$options = (array)get_option($this->option_name);

		// Send the backup to remote storage.
		$this->transfer_backups( $result['backup'], $options['remote'], 'schedule' );

		// Prune existing backup files as per the options.
		$this->prune_backups( $options['prune']['number'] );
	}

Closing due to inactivity.

Hi Greg,

I’m sorry for the inactivity, I was on holidays.

In reply to your questions:
>> – What schedule have you set for the backups?

Daily.

>> – How long does the backup take to run?

[2014-08-21 17:02:23] Elapsed Time: 2.2 minutes
[2014-08-21 17:02:23] Backup complete!
[2014-08-21 17:02:23] Backup size: 956.82MB

The backups are working fine now, but the prunning doen’t take place. I have to delete old backups manually ??

No problem, so the schedule is working as well? Even without your manual hack to force the WP Cron job? After making the change above?

My guess is your hitting your script execution time limit, can you check your webserver config for what it is set to?

Hi Greg,

I have to try it yet in the dev environment. The schedule is working with the hack (and the original code), but the script doen’t delete old backups.

Is there any schedule for deletion that I can “hack”?

Thank you.

No, the deletion doesn’t happen until after the backup is complete and if you’re hitting your script execution time limit it will never get run.

Look, the last lines of last backup log are:

[2014-08-24 17:03:14] Elapsed Time: 2.2 minutes
[2014-08-24 17:03:14] Backup complete!
[2014-08-24 17:03:14] Backup size: 960.53MB

I think the script doesn’t hit execution limit… not yet.

No, but the next thing the script does is transfer the backup to the remote location, if that takes a while it will never execute the re-schedule of the job or the purging.

Do you have remote storage enabled?