DB backup – fail when Compression interrupted by restart

  • Resolved tedinoz

    (@tedinoz)


    8 years, 11 months ago

    I am finding that database backups create a corrupt archive when the Compression stage is interrupted by a restart. There are no warnings or errors. The backup is “successful” but the archive has zero contents.

    The log looks like this:
    Compressing files as TarGz. Please be patient, this may take a moment.
    Restart after 33 seconds.
    Backup archive created.
    Archive size is 29.00 B.
    6 Files with 226.00 B in Archive.

    I have two other examples from this week where the “Restart after” value was 35 seconds and 28 seconds.

    Of course, this mightn’t be so bad except that BackWPup regards the backup as successful.

    https://wordpress.org/plugins/backwpup/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Daniel Hüsken

    (@danielhuesken)

    8 years, 11 months ago

    I must have a look fo that. but in my tests it works. Kann you give me some information about the system.

    Thread Starter tedinoz

    (@tedinoz)

    8 years, 11 months ago

    Hi

    I am going to close this item.

    Like many people, I have a development system and a live system. While analysing logs for this ticket, I noticed an example where the log for one system was saved in the folders of the other. At the very least, this indicates an issue in my configuration of BackWPup, and might give a clue to how/why there have been corrupt files.

    Rather than waste your time, I will re-configure each system and keep a close watch on the backups.

    I’ll open a support ticket if the problem happens again.

    Ted

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘DB backup – fail when Compression interrupted by restart’ is closed to new replies.