[bashirs]

BES upgrade from 4.0 to 5.0 + new server + migrate + sql migrate

Hi, I have read a number of posts and done a few hours of reading, my boss has asked me to upgrade our bes server and I need some help.

OLD BES Box
bes version 4.0.7
server 2003 sp1
local msdn database

NEW BES Box
Bes 5.0
Server 2003 sp2
Remote sql 2005 database

I would like to get the new install working with our 200+ users and move the users onto a sql2005 remote database (off the new box). I don’t want to re-activate the users after the move.

Any advice steps on what i need to do will be really appreciated

Thank you

[knottyrope]

What is the BlackBerry Enterprise Transporter
View Document

BlackBerry Enterprise Server Resource Kit Docs and Files

https://www.blackberry.com/Downloads...C1D6CE93DC54B8

BlackBerry Enterprise Server Resource Kit - Manuals and Guides

[bashirs]

this is what i am thinking but need some advice if it will work.

1. down the old box and remove it from the domain
2. copy the local msdn database to the sql2005 server and attach the database
3. give the new box the same name as the old box and install bes v5 and use the same key.
4. point the new box to the sql2005 server running the database

will this work? and will i need to reactivate the handsets?

Thank you

Bashir

[MarshBklyn]

I assume you meant step2 before step1 but we all know what it means when you assume.
Anyway, you have to run some database scripts (createdb.exe) on the destination sql server even if you are going to backup and then restore your database from local msde.

[CarlSpackler]

I pretty much did the same thing you are attempting to do.

I had a 4.x environment, SQL running on the BES.

I got a migration SRP from RIM. Brought up new SQL server, Installed first 5.0 BES server with migration SRP and keys. Installed CALS on BES 5.0 server. Pointed 5.0 BES to 4.x DMZ router.

Used Enterprise transporter tool to attach to old SQL and new SQL, migrated users to BES 5.0 server.

Created new 5.0 router, installed in DMZ, repointed BES 5.0 to new router.

Turned off 4.x servers.

[TheLizardFish]

We just did this and I really like BES 5.0. One thing I would advise though is to install the BAS service seperate from the BES due to its a huge resource hog. Also, if you are thinking about doing failover I would name your standby server something like this:

BES01
BES01b
BAS01
BAS02

Were doing a migration from GW to Exchange so for right now we have 2 seperate systems. Come Novemeber everyone on the GW side will be migrated over the weekend and each BB will have to get reactivated.

[b52junebug]

We are actually do an upgrade in place.

We have the SQL database on our 4.1 BES, so we are going to copy it off and put it on a new box.

Then we are going to install 5.0 on a new box and name it the same as the 4.1. We are then going to point the 5.0 to the copied SQL database and turn off 4.1 and turn up the services on the 5.0. This makes the SQL database think we just did an upgrade to the existing server. You must ensure your incident name is EXACTLY the same as the current BES.

The reason we are doing it this way instead of using the transport too is this: We have over 600 4.3.x devices. 4.3.x is not compatible with the transport tool. RIM recommends that the either be 4.2.x or 4.5 and higher to use the transport tool. The 4.3.x software cannot handle having two policy's on it which is what happens when you use the transport tool. Once you pull the user off your 4.x server, the 4.x policy deletes itself.

By doing the upgrade this way we basically are tricking the database into thinking we upgraded in place no need for two policy's, no transport tool, etc. Also saves us about 800 man hours in doing upgrades or reactivations. In order to reactivate a 4.3 device on 5.0 you will need to wipe and reactivate, if your going to have to touch it, upgrade it to 4.5 so you have the ability to push out new OS's via OTA. Also if something happens we turn off 5.0 and simply restart 4.1, so we have a fail safe.

We are going to be doing this in the next month or so, so stay tuned!