BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 05-24-2008, 09:10 PM   #1 (permalink)
Thumbs Must Hurt
 
Join Date: Dec 2005
Model: 9630
Carrier: Verizon
Posts: 80
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default knife edge question (SPs)

Please Login to Remove!

Hi,

I'm currently running 4.1.4 MR4 on my BES, and I need to do a knife edge cutover to transition over to a new server. I understand the basic process, but I have a question. My server is running BES Express, and I will have to run the base install of 4.1, and then install SP4, and then install MR4 patches. The knife edge installation instructions state that I should backup/recover MSDE to the new server before installing BES. But ... my initial install will be 4.1 (i.e. won't have SP4 or MR4), and if I have already recovered the DB, then the DB will be from a newer version than the BES (temporarily). Is this OK? Or should I do an install of BES 4.1, then install the patches, and then recover the DB from the old server (once the versions are in sync)?

Thanks in advance...
Offline  
Old 05-26-2008, 06:50 AM   #2 (permalink)
x14
BlackBerry Extraordinaire
 
Join Date: Jul 2005
Location: NYC
Model: 9800
OS: 6.0.0.546
Carrier: AT&T
Posts: 2,344
Post Thanks: 0
Thanked 17 Times in 16 Posts
Default

If you call RIM you can get a 4.1.4 full install file. You can restore the db first. The installation will not downgrade the db.
__________________
Exchange 2007/BES 5.0.2 MR2
Offline  
Old 05-26-2008, 04:20 PM   #3 (permalink)
Thumbs Must Hurt
 
Join Date: Dec 2005
Model: 9630
Carrier: Verizon
Posts: 80
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by x14 View Post
If you call RIM you can get a 4.1.4 full install file. You can restore the db first. The installation will not downgrade the db.
I'm not on T-support, so I'm guessing this isn't an option for me? If I stick with 4.1 install plus SP4, plus MR4, then am I still OK with DB restore first, then the installs / patches?
Offline  
Old 05-26-2008, 10:29 PM   #4 (permalink)
x14
BlackBerry Extraordinaire
 
Join Date: Jul 2005
Location: NYC
Model: 9800
OS: 6.0.0.546
Carrier: AT&T
Posts: 2,344
Post Thanks: 0
Thanked 17 Times in 16 Posts
Default

Yup. Just follow the documentation.
__________________
Exchange 2007/BES 5.0.2 MR2
Offline  
Old 05-26-2008, 11:32 PM   #5 (permalink)
BlackBerry God
 
jibi's Avatar
 
Join Date: Oct 2004
Location: Jibi's Secret Place
Model: 8900
OS: 4.6.1.174
Carrier: AT&T
Posts: 11,310
Post Thanks: 0
Thanked 1 Time in 1 Post
Default

You could also do the database restore afterwards, to be perfectly honest. Just stop the BES and SQL services, copy the MDF/LDF files and overwrite the ones created during the installation process on the new server, and restart your services (SQL first, obviously). The only thing a BES installation is doing for you in this process is creating the system tables and some other stuff - the database created can be overwritten once you're up to SP4 (the MR releases won't make database updates, I don't believe).
__________________
In the beginning the Universe was created. This has made a lot of people very angry and is widely regarded as a bad move.
Offline  
Old 05-27-2008, 08:05 AM   #6 (permalink)
Thumbs Must Hurt
 
Join Date: Dec 2005
Model: 9630
Carrier: Verizon
Posts: 80
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by jibi View Post
You could also do the database restore afterwards, to be perfectly honest. Just stop the BES and SQL services, copy the MDF/LDF files and overwrite the ones created during the installation process on the new server, and restart your services (SQL first, obviously). The only thing a BES installation is doing for you in this process is creating the system tables and some other stuff - the database created can be overwritten once you're up to SP4 (the MR releases won't make database updates, I don't believe).
That makes sense. Do the SRP and CALs all come from the database? Is it possible to do the initial install without entering an SRP (to avoid taking the original BES down, and not have my SRP locked out)? Seems like that would make sense, do the install without an SRP, patch up to the right version, then do the DB backup/restore over the installation DB (recovering the SRP, CALs, and all the config), and I'm (hopefully) up and running...
Offline  
Old 05-29-2008, 03:57 PM   #7 (permalink)
Thumbs Must Hurt
 
Join Date: Dec 2005
Model: 9630
Carrier: Verizon
Posts: 80
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by chinatti View Post
That makes sense. Do the SRP and CALs all come from the database? Is it possible to do the initial install without entering an SRP (to avoid taking the original BES down, and not have my SRP locked out)? Seems like that would make sense, do the install without an SRP, patch up to the right version, then do the DB backup/restore over the installation DB (recovering the SRP, CALs, and all the config), and I'm (hopefully) up and running...
Bumping this up in hopes of getting an answer...

Thanks in advance!
Offline  
Old 05-30-2008, 08:45 AM   #8 (permalink)
Thumbs Must Hurt
 
Join Date: Dec 2005
Model: 9630
Carrier: Verizon
Posts: 80
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I decided to go ahead, and did the installation as follows:

1. Stop all services on old BES
2. Backup BESMgmt database on old BES
3. Install 4.1.0 on new BES
4. Install 4.1.4 (SP4) and SP4/MR4 on new BES
5. Stop BES and MSDE on new BES
6. Restore BESMgmt database on new BES
7. Reboot

Pretty much up and running on new server now, with the exception of MDS Connection Services, but I'll post another question on that one...
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.