Cannot restore from backup – out of memory and killed my site!

  • Resolved PaulDoesWP

    (@pauldoeswordpress)


    8 years, 10 months ago

    Today, while editing my client’s site, I inadvertently damaged my site’s database. “No problem”, I thought, “My site was backed up a couple of days ago”. The site’s dashboard still functioned ok. Imagine my horror, when performing a restore operation of the database (using Updraft), I got an out of memory error, then the site died completely.

    After the initial horror, panic, mild heart attack and shock, I then thought “OK, I’ll manually import the database from my Updraft-created Dropbox backups”. So I decompressed the “backup_2015-06-25……-db.gz” file, assuming it would be a simple case of then importing it (as a .sql file) using phpMyAdmin. But it’s not an sql file.

    Luckily, I had a copy of the database I’d exported using phpMyAdmin earlier today, and was able to DROP all the tables in the database (after much hesitation) and then import this sql file. Lo and behold, it actually worked.

    So, a couple of questions:
    Is it common for Updraft to completely destroy a WordPress site if the restore fails?

    How would I manually import the .db file if I wanted to?

    As you can imagine, I have absolutely no faith in this plugin whatsoever, and now view it more as a ticking time bomb than a backup solution.

    https://wordpress.org/plugins/updraftplus/

Viewing 1 replies (of 1 total)
  • Plugin Author David Anderson

    (@davidanderson)

    8 years, 10 months ago

    > But it’s not an sql file.

    It is. If your MySQL tool (e.g. phpMyAdmin) is deciding that anything not matching the filename pattern sql.gz isn’t an SQL file (i.e. doesn’t like the db.gz filename pattern in UD), then just rename it so that it matches.

    > Is it common for Updraft to completely destroy a WordPress site if the restore fails?

    As it’s an SQL file, it contains a sequence of DROP, CREATE and INSERT commands. If PHP unexpectedly dies at a random point in that, then it’s not likely to turn out well. This goes for any tool which runs SQL commands – mysqlclient, phpMyAdmin, etc. – if it gets killed half way through, you’ll have an inconsistent database and need to restore the file through a different tool.

    David

Viewing 1 replies (of 1 total)
  • The topic ‘Cannot restore from backup – out of memory and killed my site!’ is closed to new replies.

Tags