<?xml version="1.0" encoding="UTF-8" standalone="yes"?><oembed><version><![CDATA[1.0]]></version><provider_name><![CDATA[37prime]]></provider_name><provider_url><![CDATA[https://37prime.wordpress.com]]></provider_url><author_name><![CDATA[A Prime Number]]></author_name><author_url><![CDATA[https://37prime.wordpress.com/author/37prime/]]></author_url><title><![CDATA[Resurrecting a WordPress&nbsp;Blog]]></title><type><![CDATA[link]]></type><html><![CDATA[<p>To quote the character played by Tony Shalhoub, &#8220;Here&#8217;s what happened.&#8221;</p>
<p>March 4th 204, I decided to upgrade my WordPress 2.0.x blog to version 2.3.3 after creating a backup. Long story short, the Yahoo! installed WordPress blog could not be upgraded to version 2.3.3 safely, and essentially in the process, my database was corrupted.</p>
<p>The worse news is that the backup was not good either. After a seemingly long period of self-deprecation, I started a <a href="http://37prime.com/news/" target="_blank">new WordPress 2.3.3 blog</a>. It was almost perfect, but completely functional.</p>
<p>Anyway, I reinstall the blog using Yahoo! control panel, and it turned out to be version 2.3.2 sans all my postings. I had a really old back-up, and it was not compatible with WordPress at all.</p>
<p>March 30th, I upgraded all my WordPress blog to version 2.5 including the one with all the missing postings. Still dreading from the loss, I slowly did some manual entry on the blog. Then it hit me. I tried using the backup and restore feature. I backed-up <a href="https://37prime.wordpress.com/" target="_blank">37prime.wordpress.com</a> and restored it to <a href="http://37prime.com/blog/" target="_blank">37prime.com/blog</a>.</p>
<p>IT WORKED!</p>
<p>Not perfect, but I got 80% of my postings back.</p>
<p>Now I have no worries when it comes to moving the WordPress blog.</p>
<p>I&#8217;m sleepy, so I&#8217;m gonna get some sleep.</p>
]]></html></oembed>