Quick ? - Cutting Over to New BES Server Downtime Involved?
Please Login to Remove!
So right now BES 4.0 is sitting on a bi-role server. We are looking to cut it over to a standalone, with 4.0 already installed. Machines are both running MSDE/SQL and the main concern is just making sure the users do not loose connectivity e-mail access at all (important functions are done through BlackBerry devices 24-7).
I'm basically just trying to figure out how I would do this and what the best way would be to ensure that there is minimal, if any, downtime.
I was thinking just export the users, (statistics don't matter), deactivate the old BES. Import the users, SRP and such and activate the new one?
Incorrect. If you simply install the EXACT same version / sp of BES on your new server, and choose not to start services you will not cause an SRP disconnect. Once this is complete, make a copy of your BESMgmt database, and attach it. Once attached, point the install of BES to your production database. Finally, stop services on old BES, and start services on new BES....voila, under 5 minute downtime cutover...=happy admin; happy users.
P.S...keep your server name IDENTICAL, otherwise you'll write a new set of tables in db...