[majiklantrn]

So I'm setting up a new BES 5.0 infrastructure using MS Server 2003 32bit with MS SQL STD 32bit. As it stands, I have designed the BES environment to have a Primary BES and a failover BES server for application redundancy. As for the database I have a Principle, a Mirror, and a Witness; all taken from the BES 5.0 install guide. With this solution I will have a fully HA BES Environment.

It appears the SQL Admins want to go the Clustering Route. According to them, DB Mirroring is an older technology that isn't useful. I couldn't find anything in the BES 5.0 with Exchange documentation and have called RIM twice to double check the status with support. Both times I was informed it isn't a supported method for redundant DBs.

Has anyone tried BES 5.0 with clustering? Has anyone used the DB Mirror and had an actual failover? Anyone know or think RIM will go the clustering path?

Any ideas or suggestions would be helpful.

[Frank Castle]

Our enterprise SQL team told me the same thing. I'm going to test in in our lab and see how BES reacts but if it works as the SQL teamed outlined the BES will be that much more HA.

[majiklantrn]

The only problem I see with clustering is losing RIM support.

[RadHaz75]

so this just came on my radar today as well. my sql team is really pushing for clustering for ha patching and maintenance (which i would want). they say the drawback then for doing mirroring as rim wants is they'd have to manually fail over to the other site if something happened.

what are people doing here for bes 5.0 db?

[majiklantrn]

So I just got done with the deployment of BES 5.0 with mirroring. So far, the mirroring is working flawless and very quick. Taking into consideration I only have 12 users on this BES cause of testing. The failover can be auto if you have a witness server.