• Resolved eitanc

    (@eitanc)


    Hi,

    I’m using 3.0.12.

    I just now had a an issue that I accepted two log emails for one backup job of the same site.

    One was succesful, with an error of:

    23-מאי-2013 09:43:05] Compression method is ZipArchive
    [23-מאי-2013 09:49:14] WARNING: Job restart due to inactivity for more than 5 minutes.
    [23-מאי-2013 09:49:14] 2. Trying to create backup archive …

    And a few minutes later I got a second email, with a final “warning” status, that was almost identical to the first email, but at its end there was this error text:

    [23-May-2013 02:02:54 America/Chicago] WordPress database error MySQL server has gone away for query SELECT 1 made by do_action_ref_array, call_user_func_array, BackWPup_Cron::run, BackWPup_Job::start_wp_cron, BackWPup_Job->run, BackWPup_Job->create_archive, BackWPup_Job->update_working_data [23-מאי-2013 10:02:54] Job has done with warnings in 1200 seconds. Please resolve them for correct execution.

    Looking around, I noticed that a the root of folder structure of my site, there was an “error_log” file of over 2 GB!
    Once I deleted it – the backup run smoothly again, with no duplicated emails and no errors of any kind.

    So all – FYI.

    Backwpup developers – please consider adding a feature that will enable users to configure to either abort a backup if there are files larger than X (when X is user configurable) or to run the backup but skip these files and log these skip operations in the log as errors.
    The calculation can be for either each single file size or for the total accumulated size of all files (pre-compression, of course).

    Thank you.

    http://wordpress.org/extend/plugins/backwpup/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Did you know you can exclude that error log from backup when you set up a job? There is a box to enter it into.

    Thread Starter eitanc

    (@eitanc)

    Thank you, but I didn’t look that way.

    Errors are like pain, they are an alarm that something is wrong and needs to be fixed, so it helped me to find the huge file and delete it, which solved the root cause.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Dual email and backup error when there is a huge file to backup’ is closed to new replies.