Host Ran Upgrade, Lost Everything (19 posts)

  1. willfulexpose
    Posted 11 years ago #

    Now I'm trying to restore from a backup I made in phpmyadmin. It's a month old, but at least I have that. I've read the documentation at the Codex, but it's not working for me.
    I have a backup file called localhost.sql that I made with other instructions from the codex. When I follow the restore instructions, I get the error message "The document contains no data."
    This happens regardless of whether I try to use the text or zipped sql files and regardless of which compression option I select.
    Any ideas for what I can do to get this fixed?

    My site is willfulexpose.com.

  2. willfulexpose
    Posted 11 years ago #

    Oh yes, and let me add that there is definitely data in the backup. It's around 1,500 KB. Not too large, not too small.

  3. Root
    Posted 11 years ago #

    You are not at Web Mania are you ?

  4. willfulexpose
    Posted 11 years ago #

    No, Infinityhost.

  5. Jinsan
    Posted 11 years ago #

    Don't worry I think Root's growing pains of paranoia after a bad experience:)

    I would contact your host to see if they have another copy of the backup in case your copy is off.

    Failing that, have you read this:


    I don't know if the codex is the same, but that's generally a good guide on how to back and restore successfully.

    Not sure if that's much help. It's possible that the db was not correctly backedup?

  6. James Huff
    Support Team Rep.
    Posted 11 years ago #

    Have you contacted your hosting provider?

  7. willfulexpose
    Posted 11 years ago #

    Thanks, but I tried that documentation as well. It didn't work either. I'll keep trying though.

    I have tried, but they are not responding to any of my help tickets. I will call in a minute.

    EDIT: Called, but phone support has ended for today.

  8. Joshua Sigar
    Posted 11 years ago #

    Does the content of the backup file look normal?
    Just try to copy the whole content of the file and run it as a sql query in phpmyadmin.

  9. willfulexpose
    Posted 11 years ago #

    I don't know what normal is. Here's an excerpt:
    # phpMyAdmin SQL Dump
    # version 2.5.4
    # http://www.phpmyadmin.net
    # Host: localhost
    # Generation Time: Mar 31, 2005 at 03:56 PM
    # Server version: 3.23.56
    # PHP Version: 4.1.2
    # Database : <code>DB

    USE DB;

    # --------------------------------------------------------

    # Table structure for table blacklist

    DROP TABLE IF EXISTS blacklist;
    CREATE TABLE blacklist (
    id int(11) NOT NULL auto_increment,
    regex text NOT NULL,
    regex_type enum('ip','url','rbl','option','auto-url','auto-ip','regex-url','regex-ip') NOT NULL default 'url',
    PRIMARY KEY (id),
    KEY id (id),
    FULLTEXT KEY regex (regex)

    # Dumping data for table blacklist

    Do you think copying that as a sql query would work?
    Thanks so much for helping me!

    Oh no...just had a thought. The backup is in 4.1.2 PHP, and now I have 4.3.2 PHP! Could that explain why it's not working?

  10. willfulexpose
    Posted 11 years ago #

    I had a conversation with one technician. She said thet guy who transferred the files should have a backup of the database. I can pray. I'll know by tomorrrow. Not very fast service, eh?

  11. Mark (podz)
    Support Maven
    Posted 11 years ago #

    The above file looks fine.
    If you get no joy, I'll have a go at it for you - drop me an email ( tamba2 at gmail dot com ) and we'll go from there.

  12. RosieMBanks
    Posted 11 years ago #

    Maybe this will help? Podz saved my very small database in this thread.

  13. webwide
    Posted 11 years ago #


    It looks like you have much of your site back up. If you are still attempting to import post content, then you do NOT need to run that SQL query as it exists. It will erase and re-create your database losing more recent entries. If you start with the line "# Dumping data for table blacklist" then you will only import posts. This assumes that your database is set up and the table 'blacklist' exists. Email me if you have any questions:

    glenn @ thedixons.net

  14. willfulexpose
    Posted 11 years ago #

    Thanks everyone. I got a lot of things imported via my host, but some new problems have come up. When he/she/it restored comments, something went terribly wrong with the database. (I should note that this problem is only occuring on my main blog. It got new comments before the old comments were reinstored, whereas the other blog didn't. I think that is what caused the problem.)
    Basically, whever I do anything involving comments and mysql, I get an error message. Most notably, even when I directly enter something like UPDATE wpWE_comments SET comment_content = 'You should have as much fun as humanly possible while over in Europe. Be a problem child, for sure! Just don’t end up in jail. :) ', comment_author = 'Johnnie Walker', comment_author_email = '', comment_approved = '0', comment_author_url = 'http://www.niteowl.tv/' WHERE comment_ID = 2179 into the mysql query window, I get an error message like this:

    MySQL said:
    #2013 - Lost connection to MySQL server during query
    What in the world can be done about that?

  15. Mark (podz)
    Support Maven
    Posted 11 years ago #

    You should be able to empty the table that was being imported and try again. That does not sound great though and if that error repeated I'd be having words with the host.

  16. willfulexpose
    Posted 11 years ago #

    Podz, I will try what you have suggested if a few other plans I have don't work. Actually, I don't have those plans yet: A couple of friends are looking at my databases and specific errors. Hopefully they'll find something without deleting the table (which I'm avoiding because I would loose 7 days of data).

    Once/if I find the solution, I will definitely post it. This is a pretty specific problem, but maybe someone else will have it eventually. Oh yes, and I will definitely be having words with my host.

    Thanks for your help.

  17. DianeV
    Posted 11 years ago #

    As an aside, this information may help someone, but requires that you have more access to the server than usual with shared web hosting accounts since the mySQL files are usually not physically located where shared web hosting account holders can get to them via SSH.

    You can do a mySQL database backup via SSH using the mysqldump command, and replace it on the server, also via SSH. It sounds like this is what willfulexpose has, since his file is named "localhost.sql". If you have this kind of server access, you can also run a periodic backup from cron, which will save you from having to remember to do it regularly.

    I used another method when moving my blog from one server to another: I simply installed WP on the new server, and then FTPed the mySQL DB files to the new server. Worked like a champ. Who knew? So, if you've got FTP access to the mySQL folders, there you go.

  18. willfulexpose
    Posted 11 years ago #

    Thanks Diane. I don't think I have all the access you did, but someone surely does.

    Unfortunately, I wasn't even inspired to think about these things until after the problems began. It's a long story, but basically my host offered to do the upgrade, at which point I made a backup. but then they stopped contacting me about it for weeks, and never confirmed that they would even do the move. I assumed they forgot my upgrade, so I stopped backing up all the time (it was tedious before I found this plugin). Then, they decide to go ahead without confirming first, and they don't move the database files (as was promised). They corrupted and deleted the backups they should have made before the move.

    Now I'm let to put the pieces back together, and they know nothing about how to solve my current problems (or so I assume, because they're not responding to my help ticket).

  19. willfulexpose
    Posted 11 years ago #

    My problems have been fixed by a very kind friend at trendyblog. I'll give the most detailed explanation I can, but he did all the work, and it was way over my head.

    Basically, in the process of restoring the many versions of the database that my host and I had, comments were duplicated and missing. The database had become severely messed up and was beyond repair. The duplicates and missing comments were confusing WordPress, which in turn gave me the errors I linked above. I'll be deleting those files from my server, so let me say what was in them. Two related messages:
    Lost connection to MySQL server during query
    MySQL server has gone away
    I would also like to thank Glenn, who commented above, for suggesting the idea of dupilcates and missing comments. Thank you!
    We decided to clear the comments tables and start over with just one backup file. Once the comments tables were emptied, the above errors disappeared. My backup files were a bit problematic; various ones were not workable. I don't know why they weren't any good, but I would advise anyone who's making backups to test them on a testblog. Even though I thought I was following explicit instructions at the WP Codex, I still managed to mess things up.
    My friend found the useable backup and then added in the few other comments that he had saved somehow. That's where we stand at the moment.
    Hopefully this information can help someone. In short, do frequent backups, make sure they're viable, and don't use my host (Infinityhost).
    I'm so glad to have all of my work back. When I started this thread, I was in danger of losing everything. Thanks again everyone for your help and consideration.

Topic Closed

This topic has been closed to new replies.

About this Topic