Quote:
|
The biggest thing you need to worry about is verifying all registry settings on each BES are specified correctly. Although the database change wizard is "supposed" to change every setting, I've noticed instances where it hadn't.
|
That is a rare case. Out of all the DB moves I've helped perform, and I've done a lot, this has never happened.
Quote:
|
That said, just take down all of your BES servers.
|
Not necessary
Quote:
|
Kill all connections to DB and Back up DB, then copy to a directory on the new SQL 2005 server.
|
Your above step would have killed the connections to the BESMgmt DB
Quote:
|
Configure the BESMgmt.cfg file accordingly with the SQL 2005 server specified, and run the CreateDB.exe
|
When running CreateDB.exe on the same server it is not necessary to change the BESMgmt.cfg if you're creating a blank DB called BESMgmt on that machine
Quote:
|
Take the DB created offline, import the backup of your SQL2000 database.
|
I assume you mean restore the original BESMgmt over the newly created blank BESmgmt
Quote:
|
On one BES, verify all services are stopped and disabled, then run the BES server configuration utility, map to the new SQL DB and verify connectivity is there. When you are prompted to restart services say no and go back to the MMC snapin for services, and re-disable them (the wizard turns them back to auto) and in the event of a crash, I don't want your users to lose activations.
|
Running the Change DB Wizard stops the services for you, no need to manually stop and disable them, it's a waste of time. Users shouldn't lose activations as no one will/should be activating while doing such an important task. Services will only start if:
a) You check start services by accident
or
b) You reboot the BES
Quote:
Browse to the following entries in the registry and verify they are correct
HKEY_CURRENT_USER Software Research in Motion Blackberry Enterprise Server Database (Confirm DatabaseName and DatabaseServerMachineName are configured with the new SQL2005 Database/Server name)
HKEY_CURRENT_USER Software Research in Motion Blackberry Enterprise Server Management Database (Confirm DatabaseName and DatabaseServerMachineName are configured with the new SQL2005 Database/Server name)
HKEY_LOCAL_MACHINE Software Research in Motion Blackberry Enterprise Server Database (Confirm DatabaseName and DatabaseServerMachineName are configured with the new SQL2005 Database/Server name)
|
While some of these steps are pre-cautionary they are not needed unless you get DB connection issues. In my expereince that is pretty rare.
@hdawg
Am I correct in assuming that this is not something you are doing but was asked to you?
Also, this reads like upgrading the current SQL 2000 Server to 2005, is that correct?
If so, backup the DB with the usual SQL backup methods and move the mdf and ldf files to a save location.
SQL Server 2005 uses different directory names than SQL Server 2000, but this upgrade is doable.
Just Remember, CYA - Cover Your A$$
@celeb
Didn't mean to rain on your parade, but some of these steps aren't necessary. After completing the Change DB Wizard you only have to open the BB Manager to confirm that the users are present, if so, you can communicate with the moved BESMgmt DB. No need to disable services, just don't start them right away.
Checking all those reg keys, while a safe step to ensure all is as it should be, is only needed if you can't communicate with the DB. That would be evident if you have issues opening the Manager or if nothing is present in the Manager. Good post though, thorough and thought out.
Just my .02
SQL 2000 to 2005 upgrade
