UpdraftPlus Home › Forums › Paid support forum – UpdraftPlus backup plugin › Google Drive Issue #2
Tagged: Google Drive, issues, UpdraftPlus
- This topic has 18 replies, 3 voices, and was last updated 8 years, 8 months ago by Tyler.
-
AuthorPosts
-
March 1, 2016 at 2:40 pm #145811TylerParticipant
Hello,
I created a quick screen share to explain the issue:
Your help is very appreciated.
Thanks!
March 1, 2016 at 6:54 pm #145848Dee NutbourneModeratorHi Tyler,
Could you send across copies of the backup logs, especially any from a failed or ‘not finished’ backup?
You can either share the files through something like GoogleDrive or Dropbox, or post the contents in pastebin and share the link here. You can also set the reply to be private if you prefer.
David N
March 1, 2016 at 11:19 pm #145887TylerParticipantHi David,
Thanks for the response.
Here’s a link to the backup on Feb 27, 2016 22:45:
https://www.dropbox.com/s/rrl8vtve3gc5wbh/log.b6bcee10ee1d.txt?dl=0
Here’s a link to the backup on Mar 01, 2016 2:43 (Not finished):
https://www.dropbox.com/s/0x2ysi3sbaxf8sb/log.3bfe35bb7f15.txt?dl=0
March 2, 2016 at 10:38 pm #145992udadminKeymasterHi Tyler,
The error in the second log file is this one:
2883.522 (11) [Warning] Your free space in your hosting account is very low – only 17.5 Mb remain
You’ll need to get some more disk space freed up (or added) in your web hosting account to be able to make the backup. There’s some relevant info here: https://updraftplus.com/faqs/how-much-free-disk-space-do-i-need-to-create-a-backup/
The pattern in the first log file suggests that the server was struggling for CPU resources at the time of the backup – not allowing larger zip files to be manipulated in the time it makes available. You can reduce the amount of resources needed by doing this
1) Go to the UpdraftPlus settings tab
2) Scroll to the bottom, and open the ‘expert’ section
3) Reduce the ‘split’ size down to 60Mb, and then save the settings
Then start a fresh backup. It’ll make more zip files, but need less resources for each of them.
Best wishes,
DavidMarch 3, 2016 at 2:13 am #146010TylerParticipantThanks so much David. I’m trying this now so hopefully it’ll work :)
March 3, 2016 at 2:42 pm #146079TylerParticipantThis reply has been marked as private.March 3, 2016 at 5:04 pm #146100udadminKeymasterHi Tyler,
Please can you link the log file for the problematic backup?
David
March 3, 2016 at 6:06 pm #146128TylerParticipantThis reply has been marked as private.March 3, 2016 at 11:20 pm #146164udadminKeymasterHi Tyler,
Thank you. It looks like it’s struggling with limited resources. Try reducing the split size further, down to 30Mb. Then start a fresh backup again.
Best wishes,
DavidMarch 8, 2016 at 9:55 pm #146689TylerParticipantThis reply has been marked as private.March 8, 2016 at 10:17 pm #146697udadminKeymasterHi Tyler,
Please can you post a link to the log file for the problematic backup?
Many thanks,
DavidMarch 9, 2016 at 2:28 am #146721TylerParticipantThis reply has been marked as private.March 9, 2016 at 10:57 pm #146858udadminKeymasterHi Tyler,
Almost the last thing in the log file is this:
13246.222 (25) [Warning] A very large file was encountered: error_log_old (size: 296.9 Mb)
The server seems to have insufficient resources to include that file, which is 296Mb and in the same directory, in the backup.
I’d recommend either deleting that file (from the name, it seems to be an old error log), or excluding it from the backup, or just not backing up WordPress core at all (since this is usually redundant – a fresh copy of WordPress core can always be obtained from wordpress.org, or whatever WordPress installation tool you use).
David
March 11, 2016 at 2:48 am #147026TylerParticipantThis reply has been marked as private.March 11, 2016 at 3:51 pm #147083TylerParticipantThis reply has been marked as private. -
AuthorPosts
- The topic ‘Google Drive Issue #2’ is closed to new replies.