[jhortillano]

Hello guys/gals,

I’ve been put in a very awkward position and I was hoping to get educated by all the fine BlackBerry Gurus in this forum. The BES Administrator has left the company and I have been assigned the task to upgrade our current BES Server from version BES 4.0.x(Yes it is the original version, no service packs, maintenance kits, etc. have ever been applied) to a brand new server and the most current version, BES 4.1.6.

Under the contract with our Software procurement company, we are eligible for the upgrade and I have already downloaded it, version 4.1.6. I was not employed with the company when the server was built and since the BES administrator left on bad terms, I have no documentation that he may have kept to help in my goals. My company currently has 200 BlackBerry Users and I believe the version of the database is SQL Server 8.0.760.

I’ve searched and read many ideas, how-to’s and still can’t come up with a clear plan on what to do. Some people have advised me to do a "phase" upgrade on the old server meaning since I’m on 4.0.x, apply each service pack and maintenance release all the way up to 4.0.7 then upgrade the old server to 4.1.6. After that then do a “Knife-edge” Cutover to the new server. Is this the right and simplest way? Do I have to apply each Service pack and maintenance release or can I go from 4.0.x and just apply the last service pack which is Service Pack 7 maintenance release #3, is it cumulative? Or do I necessarily have to do the phase upgrade, can I just upgrade straight to 4.1.6? I’m so confused. If anyone can shed some light on what I should do, I would be greatly indebted.

[knottyrope]

upgrade to 4.0.7(service pack are culmative) then upgrade the old server to 4.1.6. After that then do a xxx8220;Knife-edgexxx8221; Cutover to the new server.

How to perform a knife-edge cutover for BlackBerry Enterprise Server software versions 4.0 and 4.1

And dont forget to backup your database in between upgrades!!!!!

[jhortillano]

Hey Knottyrope,

Thanks for the reply! My confidence is greater now that you've said that. Is it just that simple? I have read this faq before. I'm just worried about Task 3 since I'm not really clear on if I need to upgrade the version of SQL that's on this box or not. I will ghost this box before anything though so we will definitely see.

[fadmin]

I don't think you need to do sql upgrade as this is suppposed to be 2000 sp3a. I'd upgrade it at some point as i am upgrade freak but in your case is not necessery. You can do it later.

[bbxpert]

Do any major event one at a time. Wait atleast a couple of days between each one.

You can go to 4.0.7 first or you can go straight to 4.1.6 either way works.
Make sure that works first.
Then do the cut over another day
Backup the DB before you do ANYTHING and at every step. Everything is based on that DB, if you completely nuke your server as long as you have that DB, RIM can get you online again.
Assuming the Exchange server wasn't damanaged

[knottyrope]

Originally Posted by jhortillano

I'm just worried about Task 3 since I'm not really clear on if I need to upgrade the version of SQL that's on this box or not.

SQL costs alot.
MSDE is free.

Check to see if you have MSDE installed by going to add remove programs and see if its listed on the BES.

[fadmin]

Originally Posted by knottyrope

SQL costs alot.
MSDE is free.

Check to see if you have MSDE installed by going to add remove programs and see if its listed on the BES.

But his current db is already on sql so all he needs is latest sql 2000 sp.

[knottyrope]

Ok I am confusing threads. You are correct.

Is SQL on the same box as the BES or a dedicated SQL box?

[jhortillano]

First of all,

Thanks to everyone who has chimed in to help, you all rock!

Yes the database sits on the same box. I looked at the Add/Remove Programs and it states Microsoft SQL Desktop Engine(8.00.761) hence MSDE correct? I've scheduled the outtage for next Monday night to do the following:

- Ghost Server
- Stop services
- Apply the latest service pack for that version, Service Pack 7 mr #3 cummulative according to knottyrope.
- Start services and cross fingers
- if all goes well, let it run a few days, then perform the cutover.

Sound good?

[DarthBBerry]

Originally Posted by jhortillano

First of all,

Thanks to everyone who has chimed in to help, you all rock!

Yes the database sits on the same box. I looked at the Add/Remove Programs and it states Microsoft SQL Desktop Engine(8.00.761) hence MSDE correct? I've scheduled the outtage for next Monday night to do the following:

- Ghost Server
- Stop services
- Apply the latest service pack for that version, Service Pack 7 mr #3 cummulative according to knottyrope.
- Start services and cross fingers
- if all goes well, let it run a few days, then perform the cutover.

Sound good?

Sounds likea good plan. Rinse and repeat for 4.1.6 a few days later.

[knottyrope]

[quote=jhortillano;1153008]I looked at the Add/Remove Programs and it states Microsoft SQL Desktop Engine(8.00.761) hence MSDE correct? quote]

yes, that is MSDE

Guess I was right for once.
Many people get confused about SQL and MSDE.
Thats why I asked.

You should be all set with your upgrade.
DO backups of the DATABASE! before upgrading!

Post results when you can.

[jhortillano]

Many Thanks! My stress level went from to . I will definitely post the results this coming Tuesday. I will do the cutover, pending the service pack went well, the following Monday.

[fadmin]

I guess I have jumped into conclusion as I had searched for original posted sql version and found this:
How do I know which version of SQL Server I'm running?
Which states it is SQL 2000 SP3a
Sorry about this.

[jhortillano]

Happy Halloween Everyone

Ok here is my tentative plan of attack:

Phase 1: Old Server (Monday Nov. 3rd)
- Ghost Server
- Stop services
- Apply the latest service pack for that version, Service Pack 7 mr #3 cummulative according to knottyrope.
- Start services and cross fingers
- if all goes well, let it run a few days.

Phase 2: Old Server (Monday Nov. 10)
-Ghost Server
-Stop ervices
-Upgrade to 4.1.6 mr1
-Start services and cross fingers again
-if all goes well, let it run a few more days

Phase 3: Old to New Server (Monday Nov. 17)
-Perform Cutover

I was thinking, should I just roll Phase 1 and 2 on the same day then wait a week before doing Phase 3 so I don't have to plan so many outages or just lessen the days between? Thoughts?

[jhortillano]

The upgrade to Service Pack 7 mr 3 went without a hitch. Ghosting the server took most of my time than the upgrade itself. Knottyrope was correct with the SP, it is all cumulative. Thanks again Knotty! I will give it a week until the next step, upgrade to 4.1.6 mr 1.

I just noticed that in the Event Viewer, I am getting numerous Warnings for the same user:

"{User email address} GetRIMMeetingReq Failed for LongTermEntryId=876454 in LaunchCalHelperAndGetResults"

What does this mean?

[knottyrope]

Glad to hear things are working out.

[jhortillano]

Couple of Quick questions:

-Will the upgrade to 4.1.6 mr2 cause reactivation of BlackBerry Devices on my BES?

-Once I do the Knife-Edge to the new Server, will that cause reactivation of the BlackBerry Devices as well?

Thanks in advance!

[knottyrope]

no it will not require activation

But service books will be sent out, and IIRC no email until they get them.

[jhortillano]

I just finished doing the 4.0.7 to 4.1.6 upgrade on the same server. All went as smooth as silk. I will do the cutover to the new server next week Monday and let you guys know the outcome.

Regarding 4.1.6 w/mr2, are there any documentation on how to setup administration roles or just any how to's on the actual 4.1.6 version itself? I see that they integrated the Handheld manager into the Blackberry Manager as one interface which is pretty nice.

Thanks in Advance!

[knottyrope]

I was never able to get HH's to conenct to the server. Might be I am on w2k.

I only do EA OTA.

Remote manager is sweet, since the emails are sent via your account instead of the BES, users are less confused on activations.

Check PM