Troubleshooter: Restoring a Clustered Exchange Database to a Nonclustered System

Well, in fairness, the original article is three years old. Sorry you didn't find it helpful; I notice that KB 323016 was updated in April of this year, apparently to add much more detailed step-by-step instructions.

For Exchange 2003, the answer is "use a recovery storage group". Even if you're using Exchange 2000, the simplest recovery method would be to install E2K3 on another box and use the RSG to import the necessary data.

thomalski, what additional detail were you looking for?

I already knew what this article suggested from kb323016 and was hoping for some more detail. I kind of feel like I was duped into subscribing now. I certainly haven't found any information worth paying for yet and was able to get a lot more information from KBALERTZ for free.

This answer is almost word for word verbatim from the MS article-->323016 I was hoping for a further explaination on the ADSI edit "to remove the failed cluster's Exchange virtual server object from AD. " because it is not mentioned where this virtual server object resides in AD?

Editor's note: Many of you have commented on the length of the "Troubleshooter" items that appear on our site. Please be aware that these items are short Q&A pieces that appear along with numerous other items as part of a regular tips column in the "Exchange and Outlook Administrator" print newsletter. As such, they are meant to be fairly brief. However, in response to your feedback, look for the column to include more "meaty" tips in the future. Thanks for your input!