Gazzoni,
i didn't tell that the /disasterrecovery switch would work. You need to change the attributes that tell exchange that it runs now on a stand allone machine, a rather undocumented task - but works. 4 Years from now i run into a similar situation where the SAN storage failed (FTDISK errors, etc). I moved all user over within 4 hours (the restore of the DB took most of the time) and i used a script to update the attributes.
But this has been the only time in my hole worklive where i had to do this. Normally SAN failures are quite limited and that all servers of a cluster go down is unusual as well.
Cluster requires more planning, administrative knowledge and maintanance, this is for sure. But it also provides a higher availability to insure that your SLA goals are met. Following these rules at least non of my exchange server installations failed in the last years .
Brgds
Wolf
PS: I dont work for Microsoft nor do i get paid for my statements :-)