Update: Eureka! I’ve fixed it, the blog Lives! If you want to know what went down…
As you can see, everything is all f’d up here.
Over a week ago disaster struck at my hosting company, during a fire alarm test the suppression system was triggered, hosing all the servers. This blog was dead for a full week.
We were offered to move our hosting from the version 3 infrastructure to v4, and I took up the offer since it got my domain back 2 days earlier. Unfortunately the new environment is not the same – even though I have a full backup of my Database that supports this blog, the new system does not allow you access to the directory where that data is kept.
I’m no expert in MySQL, but it looks like I’ve gone from having my own instance to sharing one on the server with everyone else.
The end result is that all my archives are gone for now and my Google juice vanishing as there’s no access to any of my archives. It looks like my only path is to install WP and MySQL on a box of my own, then do a wordpress export so I can then import it back in. I cannot believe that having the actual files is not enough for me to do a restore, that is complete crap. If anyone has any better attack plans I’d love to hear them. Please DM me @johnjwall I’m closing comments on this post b/c if all goes well this domain will resolve to the real site soon.
2 replies on “When Even a Backup is Not Enough”
[…] When Even a Backup is Not Enough | Home […]
[…] sympathetic inquiry to John after hearing the podcast, he sent me a link to a post he had titled “When Even a Backup Is Not Enough.” As you can see, everything is all f’d up […]