Finally replied to ya PM :) Thought I had already replied in some way but i guess not.
Wrote a huge one, and then for no reason i can see (seeing as i didnt actually touch anything) the browser refreshed and i lost me "not so quick" Quick Reply hehe
So many different ways u can keep the data safe in Exchange 2010 natively that it wont be a problem, minus some huge meteor type disaster like you say, but then, i think the data wont matter a jot if something like that happened ;)
DAG with Passive copies is awesome btw...
...and yes, quite true (tho ESXi-level HA has no bearing on Exchange Sukh - i,e. there are no multiple copies of VM's or anything like that if thats what you were wondering :D that would definately not be supported by MS indeed ;))...and yes, like Sukh said, you can also make a lagged copy mailbox server which would be ideal if the SAN exploded for example or killed all the data on your iSCSI LUN's hooked into your exchange VM's. So ideal idea there would be a physical server with JBOD, and setup as a lagged MBX, or even a member of the DAG that only stores the passive copies.Quote:
I've spotted a few posts on the dual HA unsupported configuration, I think I'll probably stick with the VMWare HA to cover loss of a host as the DAGs don't help much if the SAN they're all sitting on is the part that fails
All this and having the dumpster and deleted items / mailbox retentions (at the db lvl) sorted, you've pretty much got it all covered :)