Google Drive Issue #2

Viewing 15 posts - 1 through 15 (of 19 total)
  • Author
    Posts
  • #145811
    Tyler
    Participant

    Hello,

    I created a quick screen share to explain the issue:

    Your help is very appreciated.

    Thanks!

    #145848
    Dee Nutbourne
    Moderator

    Hi 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

    #145887
    Tyler
    Participant

    Hi 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

    #145992
    udadmin
    Keymaster

    Hi 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,
    David

    #146010
    Tyler
    Participant

    Thanks so much David. I’m trying this now so hopefully it’ll work :)

    #146079
    Tyler
    Participant
    This reply has been marked as private.
    #146100
    udadmin
    Keymaster

    Hi Tyler,

    Please can you link the log file for the problematic backup?

    David

    #146128
    Tyler
    Participant
    This reply has been marked as private.
    #146164
    udadmin
    Keymaster

    Hi 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,
    David

    #146689
    Tyler
    Participant
    This reply has been marked as private.
    #146697
    udadmin
    Keymaster

    Hi Tyler,

    Please can you post a link to the log file for the problematic backup?

    Many thanks,
    David

    #146721
    Tyler
    Participant
    This reply has been marked as private.
    #146858
    udadmin
    Keymaster

    Hi 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

    #147026
    Tyler
    Participant
    This reply has been marked as private.
    #147083
    Tyler
    Participant
    This reply has been marked as private.
Viewing 15 posts - 1 through 15 (of 19 total)
  • The topic ‘Google Drive Issue #2’ is closed to new replies.