[FONT=Times New Roman] Anyone have any good tips or suggestions for a BES migration plan ... Server Admins forum
[FONT=Times New Roman]Anyone have any good tips or suggestions for a BES migration plan going from GW to Exchange 2007 mail platform? We're going from BES 4.0 to 4.1.6. Any migration plans or suggestions when testing the handhelds? We’re in the planning phase of setting up a complete virtual test environment before going to production.[/FONT]
Try to replicate your PROD environment as closely as possible in your sandpit.
Use a copy of the PROD DB not another one at the same version level.
Test from start to end everything you are going to perform in your PROD environment. i.e. multiple BES to upgrade? Do all of them not just one.
Backup the DB and BES platform registry at each major step of the upgrade. i.e.
SQL backup/reg backup
4.0.x > 4.1 Upgrade
SQL backup/reg backup
4.1 > 4.1.6 Upgrade
(a straight 4.0 > 4.1.6 prob wont be happy)
I recently did a 4.0.5 > 4.1 > 4.1.6 upgrade and this went nicely. Took about 3hrs all up from start to finish
If you have multiple BES bring them all up to the same version before going to the final version. (all to 4.1 then all to 4.1.6)
Thanks for the info. I'm not familiar with the SQL/DB side at all. Is it easy to copy the database to the virtual SQL server? We're building a complete virtual environment to test in to match what we plan to have in production. We will have a GW mail server running at the same time as the Exchange 2007 mail server communicating back and forth.
We will have four GW BES all running BES 4.0. They will be in full production as we re-activate accounts on the new Exchange BES. As each GW BES becomes empty we will activate those servers on the Exchange side and deactivate on the GW side. This way we can move users and set them up as we like avoiding the 90 day SRP rule. Once all user mail accounts are on Exchange and BES is fully setup, GW will go bye bye.
The BES DB is fairly easy to pickup and move to another instance. There are sometimes issues creating a blank DB from SQL Manager then turning it into a BESMGMT DB though.
Best way is to create a blank BES DB using the Database folder and tools from the installer folder "Database". This contains the CreateDB.exe and the BESMGMT.config files as well as the subdirectories that contain the sql scripts to create the schema.
So if your present environment is say 4.0 you will need to find the 4.0 installer and extract those Database folders and then use the createdb.exe.
Then you will have a clean 4.0 DB and you can backup your Prod DB and restore it over the sandpid one. As all the schema is then the same you should have no issues to restore.
You could get issues if you try to restore a copy of the Prod DB over the Sandpid DB if you create the sandpid DB straight out of the SQL management studio as the BES schema wont be there.
The BESMGMT.config file needs to be edited with all the appropriate info before you run the CreateDB command. (createdb.exe -besmgmt.cfg is the syntax from memory). Plenty of info about and the besmgmt.cfg file contains most of the info you'll need to edit it.
Tags for this Thread