Backups still made from old webserver?

Hi,

UpdraftPlus will run on whichever WordPress installation that it is installed on. Can you find the backup log for that backup? This can be found in the Existing Backups tab, or in the ‘wp-content/updraft’ directory of the site. This will tell you which site is being backed up.

Looks like the WordPress installation on my old webhost is still making backups on Updraft. Any quick way to disable this via the cPanel file manager?

Also, backups are now taking 8hrs to complete on my new webhost, they used to take less than half an hour.

A lot of time was spent doing this:

28178.547 (0) Googledrive chunked upload: 21.7 % uploaded (73400320)
28179.658 (0) The time we have been running (28179.7) is approaching the resumption interval (28209) - increasing resumption interval to 28210
28179.663 (0) Googledrive chunked upload: 22 % uploaded (74448896)
28180.731 (0) The time we have been running (28180.7) is approaching the resumption interval (28210) - increasing resumption interval to 28211
28180.735 (0) Googledrive chunked upload: 22.3 % uploaded (75497472)
28181.811 (0) The time we have been running (28181.8) is approaching the resumption interval (28211) - increasing resumption interval to 28212
28181.816 (0) Googledrive chunked upload: 22.6 % uploaded (76546048)
28182.899 (0) The time we have been running (28182.9) is approaching the resumption interval (28212) - increasing resumption interval to 28213
28182.905 (0) Googledrive chunked upload: 22.9 % uploaded (77594624)
28183.909 (0) The time we have been running (28183.9) is approaching the resumption interval (28213) - increasing resumption interval to 28214
28183.913 (0) Googledrive chunked upload: 23.3 % uploaded (78643200)
28184.927 (0) The time we have been running (28184.9) is approaching the resumption interval (28214) - increasing resumption interval to 28215

Any ideas on how to fix this?

In that log fragment, 5Mb of data is sent to Google Drive in 6 seconds. That’s fairly typical of how Google Drive normally behaves. Presumably you have a lot of data you’re backing up?

David

Well on my old webhost the backup would complete in an hour or so. After I moved to the new webhost, it seems to be taking 8hrs.

Is it normal for around 1.2GB of data backup to take 8hrs?

Hi,

There isn’t really a normal time; it depends mostly upon the size of backup, the resources provided by the web hosting company (CPU share, disk input/output bandwidth and network bandwidth) and server conditions at the time of the backup. It sounds from your description most likely that your new host’s environment provides significantly less than your old’s.

David

Hi David,

Could I send you some of the old webhost and new webhost logs that I have to an email address of yours?

Just need your help to confirm that backup duration difference is due to the new webhost’s inferior resources.

FYI the new webhost is halfway around the world, but the old webhost did the same backup in about 30mins. 30mins vs 8hrs is a bit extreme.

Hi,

You can use an online service such as pastebin to post the contents of the logs (or use a file-sharing service), and paste the link here.

There seems to be a bit too much potentially compromising data in those logs to put it up on a public link.

Hi,

You can send me a copy of the logs at:
dnutbourne (at) updraftplus.com

Hi DNutbourne,

Thanks! I’ve sent the logs to your email.

Hi,

Apologies for the delay.

From the logs that you sent, there does not appear to be any errors in the backup process on either host. However, the backup on the new host is indeed taking a very long time to process the files.

This is possibly caused by a low I/O resource limit that is throttling the backup’s ability to write to the backup files.

Hi DNutbourne,

As I understand my account I/O usage limit is 900 KB/s. Is that limit considered low and affecting the backup speed?

That’s pretty low, yes. It means that all the processes on your account have a combined limit of 900 KB of disk reading/writing they can do per second. That includes serving up files to website visitors.

So, if your website is 1.2GB, that’s 1.2 * 1048576 KB, needed at least 3 times (once to read the data, once to write it to the backup, once then to read the backup to send it to Google Drive). Then, even if you assume that you have no website visitors at all using any of that limit and bring in all the various inefficiencies, and your theoretical lower limit is in the range of hours.

David