Restoring Backups: Still Easier Than Xiaxue

Here we have it. Finally…after about almost 24 hours of sheer nail-biting impatience. I have finally moved to my very own webhost…which means only one thing for me every since I have set my eyes on something like this.

Complete control.

Of course…with complete control comes many problems. I’ve written earlier this week about backing up your blogs in order to prevent something like this from happening. No doubt about it though, reading that her site is back up again with all the previous posts back in order shows that while you may have all your posts blogacidally wiped out, but with records…everything will be back in order again.

So how does this relate to my post?

Simple. I told you before that backing up is easy. Sure enough, with replicated posts around, google caching and I’m assuming Blogger’s own backups, it was fortunate to have all the posts back up there all without her having to manually back it up. Then again…for those of us with full control over what we do. That…can be a headache when you’re doing it alone without prior knowledge.

Let me explain why.

If your blog’s on a client-hosting. Restoring it is easy. Just republish everything from their backups which they would have. If you’re on your own webhost using things like WordPress. Then you’re going to have to upload the entire Database itself…which was the problem to begin with.

Because it was a complete mystery.

Now I’m not going to give you the story of the 24 hours I was trying to move my blog to the new server, but I will give you what I learnt from the whole thing that EVERYONE with a backup should know if you want to restore their blogs…especially on WordPress.

Edrei’s Lessons in Blog DB Restoration:

  1. Do not bang your head against the wall should your database be too large to upload because you’re going to have a headache and you can’t read these next instructions properly.
  2. For WordPress users, the best backup plugin you can have is Skippy’s WP-DB Backup. Why? Because you can choose the optional databases to backup. You’ll understand at point 4.
  3. Delete ALL your spam filters by logging into your PHPMyAdmin and typing this line out.
    DELETE FROM `wp_comments` WHERE `comment_approved` = 'spam'
    This ensures that you wipe out all the spam that are hidden in your comments. I had almost 28000 spam comments in my database. I don’t have to tell you that takes a lot of space.
  4. This is important so listen carefully. Do NOT under any circumstances even under the threat of death backup your Stats or Spam filter database. With Skippy’s WP-DB Backup, you can make sure that they aren’t selected at all. Like the spam comments, there would be thousands of lines of logs there you don’t need. Trust me on this one…you don’t need them.

Let’s just put it this way. Uncompressed…my totally backed up wordpress database was 70 mb big. That’s right. When everything was backed up on my blog, not including php, css and image files. It amounted to 70mb worth of data. Good luck trying to upload that onto your server in 300 seconds (which happens to be the usual upload timeout for most servers). After clearing out the spam and backing up the essential data.

My uncompressed database was 4mb.

There definitely a lot of shit in there.

More detailed instructions however can be found here so read them well. Backing up is good, but restoring can be a pain if you don’t pay attention…so be sure you read every line carefully and follow the instructions to the letter.

Remember…backing up may be a necessity.

But it ain’t going to do you any good if you can’t put it back in the first place.

Pay attention and stay smart.

Otherwise being so close will breat your heart.

One thought on “Restoring Backups: Still Easier Than Xiaxue

Leave a Reply

Your email address will not be published. Required fields are marked *