Last week our Vietnam Ride Blog suffered a corrupt database while I was adding some entries. I’m not sure how it happened, but there doesn’t seem to be any graceful way to recover from it aside from exporting all the entries, re-installing Movable Type, and importing all the entries again.
In the meantime, we can’t update that blog at all, which is a drag, as there’s lots going on.
That’s one of the downsides of using Movable Type with a Berkeley database for storage.
So, now having been made suitably nervous about Berkeley db I decided to upgrade this weblog to use MySQL for its back end storage.
Our support folks here at the UW (which happens to be the group I direct, he says proudly) have done a bang-up job of documenting how to use MySQL on our central unix servers.
I followed the documentation, and then used the Movable Type documentation on how to upgrade from Berkeley DB to MySQL.
All went mostly smoothly, though it took some hunting through the MT documentation to learn that I needed to add DBSocket and DBPort entries to the MySQL configuration section of mt.cfg. And I needed some help from our web guru Adam to understand that in my mt.cfg file I needed to specify ovid.u.washington.edu as the DBHost instead of localhost.
So if you’re looking at this post, it’s a sign that all went well and this blog is now running on MySQL.
Is that cool, or what?