Not Backing Up

Hi,

The log suggests that the server is badly overloaded – operations are taking far longer than you’d expect. If you go into the expert settings at the bottom of the ‘Settings’ tab on the UD page, you could reduce the ‘split’ setting to 25Mb, which will minimise resource usage, if it’s not possible to find out why the server is performing badly (which may be temporary).

David

Can you expand on “performing badly”?

Can you tell from the log what may be causing this?

I’ll contact my host (Newtek) but I have a feeling they will need more detailed info.

thanks!

Hi,

I was meaning that in the log file, things which should take a short time, take a very long time. One example (though really, it’s the pattern throughout):

3180.998 (14) Adding batch to zip file (UpdraftPlus_ZipArchive): over 500 files added on this batch (15.8 Mb, 1598 files batched, 501 (501) added so far); re-opening (prior size: 11639.7 Kb)
3223.087 (14) Zip: backup_2015-06-24-0844_Expediter_Services_e46491d3aec1-uploads.zip.tmp: 1100 files added (on-disk size: 27773.2 Kb)

There, an 11Mb zip file has 16Mb of data added to it; and it takes 43 seconds (the difference between the timings on the left). That operation ought to take about a second.

It’s not necessarily true that the server is very overloaded; it may have some severe limitations placed by policy. But only the hosting company can comment on that.

David

The server said nothing was wrong and they “reset it”.

I reduced the settings down to 25mg and it does back up now but takes forever.

Should I delete these files that are large? How do I find them?

What else can I do to optimize the backups and speed things up a bit?

Thanks!

Hi,

I’d have to see a new log file to comment on the current situation – please can you paste one of those?

> The server said nothing was wrong

The log file shows otherwise, in detail – the every logged line includes timing information.

David

Here’s a link to the log file:
https://www.dropbox.com/s/27p70bg3dn3xl4a/2015-0628-log.d40fdc2d5c37.txt?dl=0

Can you answer these questions that my server ask me:
– When you try to run a backup, do you get an error message?
– What PHP Core Directives does the plugin designer recommend that you use (i.e. memory_limit, max_execution_time, etc.)?
– You may need to review your PHP settings, which can be set in cPanel by going to “Select PHP Version”, and then clicking on “Switch to PHP Settings”.

I do not feel comfortable messing with the PHP settings and I do not know what they need to be set on. Can you tell me the PHP settings I need and I will have them do this.

Can you tell me specifically everything I need to request that my server do to fix this?

Thanks

Hi,

> When you try to run a backup, do you get an error message?

Isn’t that a question he’s asking you, rather than me? (Since I don’t have access to your site, I don’t know the answer!).

The attached log file looks fine – a successful backup. Not the fastest, but it did succeed. So, I’m thinking the other questions are moot, that being so?

David

I changed the setting to 25 and it will successfully backup. But I was hoping you could help me resolve the issue as to why it wouldn’t backup at a higher rate.

I sent you the log file earlier when it threw an error and you said “The log suggests that the server is badly overloaded – operations are taking far longer than you’d expect.” and “in the log file, things which should take a short time, take a very long time.”

I’m trying to understand what the problem is with the server so I can ask them to fix it.

My host asked these questions that I do not know the answer to.
Can you tell me what these settings need to be?
– What PHP Core Directives does the plugin designer recommend that you use (i.e. memory_limit, max_execution_time, etc.)?
– You may need to review your PHP settings, which can be set in cPanel by going to “Select PHP Version”, and then clicking on “Switch to PHP Settings”.

Thanks again for your help.
sh

Hi,

The only PHP setting likely to make a difference is max_execution_time, which should be set as high as they’ll allow (e.g. 900 seconds). Then PHP won’t keep getting killed, necessitating UD to resume from where it got to previously (and to scan to work out where that was).

David