View Single Post
Old 05-17-2005, 11:20 AM   #1 (permalink)
BBF Veteran User
Join Date: Aug 2004
Location: Hotwiring another Cessna
Model: OU812
Carrier: Nintendo
Posts: 3,492
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default HOWTO Upgrade BES 4.0 Hardware

Please Login to Remove!

Many of you have asked how to upgrade from MSDE to SQL, or migrate to new hardare, or other similar questions. Well I did just that last night so here's a runthrough of what it took.

Previously we were running on a dual P3 box. GroupWise BES 4.0 and MSDE on the same machine.

We were wanting to upgrade to (2) dual P4 Xeon boxes. One for SQL and one for BES. Plus full SQL Server migration as well.

for the purposes of this, we'll call the current combined server OLDBES. The new BES server will be NEWBES and the new SQL server will be NEWSQL


Shut down services, including MSDE on OLDBES. You'll need to copy the database and log files from MSDE over to NEWSQL. Going with the stock filenames this will be BESMgmt.mdf and BESMgmt.ldf. When we created the databases on NEWSQL, we created the file and then copied the populated databases on top of them, duplicating the filenames. So it looked something like this:

copy BESMgmt.mdf BESMGMT_data.MDF
copy BESMgmt.ldf BESMGMT_logs.LDF
Now restart the SQL server on NEWBES. If you use your SQL enterprise manager to navigate down through the database, you should now notice it popuplated with BES tables and information.

Now there's 2 ways of doing the next step. First is to open a command prompt and follow these steps:

ServiceName and MachineName will most likely be the same. Here the values were previously listed as OLDBES and are getting changed to NEWBES (not NEWSQL!!!!)

C:\>  osql -E
1>  use BESMgmt
2>  update ServerConfig set ServiceName = <name_of_destination_server> where Id = 1
3>  go
1>  use BESMgmt
2>  update ServerConfig set MachineName = <name_of_destination_server> where Id = 1
3>  go
1> exit
This returned some errors, something about 70000 and 70010. But the values took so we ignored the errors. The second way of doing it if it works for you is to open the SQL enterprise manager, open the BESMgmt database and look for the serverconfig table. Open it up and change the names for the related fields there.

Restart your SQL server for safe measures and it should be ready to go.

Now I'm not going to go over the installation procedure for NEWBES. If you aren't sure how to install BES for the first time, you shouldn't be attempting this procedure.

So NEWBES should be up and going (not services, but installed). Open up the configuration manager and one of the first steps will be to ask where the database is. Point it to NEWSQL, and select whatever kind of authentication you used.

Note: If you used windows domain authentication, you will need to run the BES services on NEWBES using an account that has domain privs on both boxes. Otherwise the dispatcher, policy and sync services will fail to start.

Enter in your SRP, license info and whatever groupwise/exchange/notes post office info needs done.

When it finishes it should ask you if you want to start services. Click yes and get it started. Make sure, before you do this, that OLDBES is shut down and services disabled. It will disable your SRP and a phone call to RIM tech support will be required to get it enabled again.

No re-cradling or re-activation is required so long as you keep the same SRP info on NEWBES as OLDBES. Ours took about an hour before it started pushing out mail to the last people on the list, and after that worked a hundred times more reliable than before on the consolidated server.

Good luck!!!