QUOTE
Can anyone tell me my options for:
1) restoring another backup from last Thursday and fixing MT before the said corruption occurs OR
MT (the application) isn't the problem - it's your database files. There are tools that allow someone who knows what they're doing to attempt to repair a Berkeley DB, but from what I've read, they're command line tools, and most users have neither the access nor the expertise to use them. Your host *might* have the necessary knowledge and expertise, but that's a pretty big "if". (They'd also have to want to put in the time to try to repair your database, and they may decide it's not worth the time/money - restoring a database backup may be the most they're willing to do.)
QUOTE
2) Restoring a backup from last Thursday, exporting all data and completely reinstalling MT. I've never exported entries, is it easy? Are category names retained? Are post dates and other meta data retained? Would the corruption to the DB also get exported and potentially affect a new install?
Exporting your entries is pretty easy. Whether you will be able to get a complete and successful export depends on how corrupted your database is.
Category names are retained in an export, as well as post dates, titles, comments, and trackbacks. To see a full list of what an export contains, take a look at MT's
Import File Format - the same info/data/fields are exported.
What's *not* included in an export is your templates and your Weblog Config options. If you've done a lot of customization of your templates, you'll want to try to get a copy of those as well before deleting your database and starting over.
I don't know if the database corruption would make it into an export; as I noted above, I think it is more likely that database corruption would prevent you from exporting some or all of your entries.
QUOTE
Any help is appreciated, even if it's just sound advice because this is all beyond the realm of my knowledge.
1) After you restore a database backup, don't do anything that writes to the database, such as posting entries. Your database is corrupted enough that writing new data into the database is corrupting it more. Think "Look but don't touch".
2) If it is available on your host, now would be a great time to migrate your database to MySQL. MySQL is faster, more robust, usually has better tools to manage your database, and is much less prone to corruption. (Not to mention that you'd be able to use plugins that require MySQL.)
Hope this helps...