an interesting turn of events

so, as most of you may know, my website went down on sunday because a hard drive failed at my web hosting company. about 24 hours later, my site was back up, except some of the subdomains weren’t working, and my SQL databases were being all screwy (these databases have several purposes – for example, one holds all of my journal entries).

for some reason i had a difficult time getting a response back as to why my site was back but not correctly configured. maybe i wasn’t communicating clearly enough, maybe they’re lazy shits and wouldn’t know customer service if it bit them in the ass. it’s a moot point.

after some back and forth, it was finally made clear that while my html and so forth could be retrieved from an up-to-date backup, all of my configuration files, including my sql databases and so on, could only be return to the state they were in NOVEMBER OF 2004.

as in… six months ago.

luckily, i had a recent backup of my mt entries because of the upgrade, so it didn’t take much work to return all of my entries to the database. then i went about making sure everybody else was set up correctly again, which is loads of fun when you’ve got four different instances of mt to bring back up to speed. i’ve still got some work to do on that, but at least a solution is in sight.

i’d really like to find new hosting, but i don’t really have the money to spare at the moment, and if i just make regular manual updates and save them on my side, i’ve at least got everybody covered should (god forbid) something this ridiculous happen again.