iclanzan

I think you’re referring to a different plugin.

I have planned to migrate to the Drive API, but it is a lot of rewriting to do and haven’t got the time at the moment.

If you would like to contribute, that would be great.
https://github.com/iclanzan/Backup

A blank page means that a backup process is already running or that a previously running backup process did not finish successfully.

Hi AZ2012,

Thank you for your donation.

Please give give me some information about what you did and what did not work as intended. Please also make sure to read the documentation included in the plugin by clicking on the Help button in the top right of the Backup Settings page.

Hi,

On the Cronjobs page (where I assume you got the examples from) you have a Create a New Cron Job section. Under there you have a bunch of fields like minute, hour, etc. If for example you enter 15 in the minute field and 3 in the hour field and leave everything else to *, the cron job will run every day at 3:15 am.

Now for the command field, something like /usr/bin/wget -O /dev/null https://mydomain.com/?backup=PPYmBWUJKq0G should work fine.

Backups are always created on the local filesystem first and then uploaded to GDrive.

You have the option of choosing the maximum number of backups you wish to be stored both locally and on Google Drive.

Thanks for letting me know of the problem. I have been tackling it for a while and came up with a solution.

Please download the patched version of the plugin from here and tell me if it solves the problem for you.

I had that put there by accident. Fixed it.

The hosting company is probably denying the plugin MySQL access seeing as it’s requesting the entire database.

The issue has been fixed in version 2.2 of the plugin.

@wpwebbouw,

You can set up a cron job and use something like this https://username:[email protected]/?backup=43g34g3g5t for the URL.

Sorry to hear about your situation Koperfield.

I can think of one situation when this might happen, if you choose the backup folder to be your wordpress root folder. I do know of this problem and will fix the plugin to not allow the user to save backups in the root of wordpress.

Hi Jason,

I’m glad you like the plugin. There is some documentation built right into the plugin. Just click the help button on the top right of the Backup Settings page.

From there you can read that you can in fact get the ID of the Drive folder from the URL. The ID is the part that comes just after #folders/.

After talking with some of you guys in private about the transient issue it seems the cause of the plugin not working is that only one connection to the database is allowed in your specific setups.

When someone visits your site while the backup process is running the MySQL connection gets stolen from it so that the visitor can access your site. When this happens Backup obviously fails and there is no way for it to let you know about it because it can’t write to the database.

This usually happens on shared hosting environments.

@cgail914, can you confirm that you also have this limitation?

@cgail914

There seems to be a problem with the transient as I’ve seen it happen to other people as well so I’m investigating the issue. Could you tell me what caching plugins (if any) you’re using?

Uploading large files should be no problem even on low memory because the file is split and uploaded in small parts. What does the backup log say?

@mokseo

What you are experiencing has nothing to do with the transient bug and is in fact working properly. The backup process times out because it reaches the time limit you set but after timing out it will resume automatically as long as you have someone visiting your site (to trigger wp-cron).

On the Backup Settings page if you click on Screen (top right) and then select Log File you will see the contents of the log file for that backup which tells you a bit more about what’s happening.