BlackBerry Forums Support Community

BlackBerry Forums Support Community (
-   BES Admin Corner (
-   -   Advise on upgrade from 2.2 to 4.1 and restore options (

Davinci1969 04-15-2007 10:41 PM

Advise on upgrade from 2.2 to 4.1 and restore options
Hi all, sorry for the big title :smile:

okay, I have been reading through the Upgrade Guide for upgrading 2.2 to 4.1 and taking note of their sagely advise to backup IT Policy, BlackBerry specific Domino databases, server.ID and notes.ini file, etc in case things don't go well.... however, I do not see anywhere here the process for restoring this information to get you back from the edge, if it is possible?

Could someone please advise what, if any, restore process there is if your upgrade from 2.2 to 4.1 should fail? I know you are moving information out of the Domino databases and into an MSDE database, but how do you recover if that fails?

Also, a little help please on he upgrade process, the server I am going to be looking to upgrade is currently 2.2.3a and I will upgrade to 4.1.3.
I have seen mentioned that to have the read/unread status displayed on the devices your Domino messaging server needs to be at 6.0.4? Am I reading this correctly?

Finally, a number of BlackBerry devices software is at 3.7 and 3.8 and the Desktop software is at 3.6 and 4.0. Is there any reason why I would not want to update the Deskto and Handheld software prior to the upgrade of the server software? If some devices are left at 3.7 and then later upgraded to 4.0 or 4.1, would redocking them to the Desktop then push out the service books to allow wireless PIM redirection?

Alot of questions I'm sorry but any help is greatly received and if there is a document on the 2.2 rollback, all the better;-)

Thanks again

amukhey 04-16-2007 02:01 PM

Da Vinci,

As far the rollback is concerned, it is possible but going back to a 2.2 from a 4.0 / 4.1 Environment is not exactly easy but doable--You will need to do a full backup of up the Lotus\Domino directory--Just to be on the safe side, do a backup of Program Files\Research In Motion dir as well.

Reverting--> restore the data from the Data folder and the notes.ini. Re-install 2.2 version and bring the server back up online.
Re-install the Domino Version


1. How many user's do you currently have?
2. What version of Domino are you on right now? I am guessing 5x. You could go to 6.0 but i would suggest at least 6.5.5.

3. Question 1 is critical to find out the kind of power and processing you require for your server.
4. Use Windows 2003 Server with SP1

5. Review BES Documentation on IT Policies on what to implement

6. I would: Upgrade the current handhelds to at least 4.1 OS and then upgrade the server.

*I have been using bes since 2.1: Create a test environment (call rim / your rep for a trial server license) and build a copy of your environment and then perform the upgrade process. Review and test the policies along with the version of the handhelds that will and or will not work on your server pre 4.1 OS.

This may sound tedious but at the end of the day, worth it so you eliminate any anomalies that come up during the actual upgrade of the production server*

I am currently running 4.0 SP6 HF4 ( 2 Servers, 370 user's, IBM X Series Server with 4gb each with a remote sql server + attachment service), Windows 2003 Server and Domino 7.02 FP1. I also have a test 4.1 SP3 HF1 Environment, which is running smoothly--

Hope this makes sense..

Davinci1969 04-17-2007 07:00 PM

Thanks for that
Thanks amukhey,

The Domino version is now currently 6.5.4.

I'm assuming there are no backward compatiability issues by making the Desktop software and handheld device software 4.1?

Thanks for the information though, much appreciated.

amukhey 04-19-2007 04:55 PM

No there are no backward compatability issues with 4.1 OS but you dont have the wireless functionalities.

Davinci1969 04-19-2007 10:31 PM

Hi amukhey,

thanks very much for that, much appreciated!!

noname 04-21-2007 04:04 AM

I hope I'm not too late to contribute.

Before an upgrade to BlackBerry Enterprise Server software version 2.2 to 4.0 or later, you need to perform these steps so as to allow synchronization capabilities to be added to the state database, and also allow the wireless service books to be sent to the BlackBerry device:-

1. Upgrade BlackBerry Device Software to version 4.0 or later.
2. Connect the BlackBerry device to a computer running BlackBerry Desktop Manager version 3.6.3 or later (it is recommended to upgrade to version 4.0 or later).

The BlackBerry Enterprise Server for IBM Lotus Domino Version 4.1.2 Upgrade Guide states that BlackBerry devices with BlackBerry Device Software version 4.0 or later must be connected to BlackBerry Desktop Manager Version 3.6.3 or later before upgrading the BlackBerry Enterprise Server.

Otherwise you will some problems to tackle. See KB12982 - Prepare BlackBerry devices before upgrading to BlackBerry Enterprise Server software version 4.0 for more information.

Davinci1969 04-22-2007 04:40 PM

Hi noname,

thanks very much for that, looks like I better rethink this as a few of the users will not be anywhere near their desks before this upgrade occurs. :cry: Thanks for bringing this to my attention!


amukhey 04-24-2007 12:04 AM

Yes RIM advises that for the Wireless functions to work but if email is the primary concern here, upgrading to 4.0 / 4.1 OS handheld will work. When I moved from 3.6 to 4.0 Server, some users were using 3.6 version OS and they were working fine, they just didnt see the new featrures.

Davinci, the best way to actually prove this is to get your own test lab and work on this. This way, you work out any theories you may have and plan your work / project accordingly.

noname 04-24-2007 08:46 AM

Hey Ajay, Davinci is dealing with Domino BES 2.2 -> 4.1 and that given KB article is specifically for Domino BES upgrade. A good point on the test lab though, I agree that it's generally good to test it out if given the resources ;-)

All times are GMT -5. The time now is 02:08 PM.

Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.