Move the BES from one computer to another - BlackBerryForums.com : Your Number One BlackBerry Community

captkave · **Move the BES from one computer to another -** 07-24-2006, 10:25 AM

I am planning to move the current BES server from one computer to another one. When I called Blackberry TSupport, I need to purchase a migration kit. Is there a way you can migarte from one machine to another one without purchasing a migration kit from blackberry? We are currently running BES 4.0.1. Any suggestions would be greatly appreciated.

StlGuyNow · 07-24-2006, 12:01 PM

Are you going to keep the same computer name?

captkave · 07-24-2006, 12:50 PM

It is going to be a different computer name.

blackberry1 · 07-24-2006, 01:43 PM

Search for "How to do a Knife Edge Cutover" on the RIM Public Knowledge Base Center

blackberry.net/support

jibi · **OS:** 4.6.0.171

Quote:

Originally Posted by captkave

I am planning to move the current BES server from one computer to another one. When I called Blackberry TSupport, I need to purchase a migration kit. Is there a way you can migarte from one machine to another one without purchasing a migration kit from blackberry? We are currently running BES 4.0.1. Any suggestions would be greatly appreciated.

What kind of database do you have (SQL 2000 or MSDE 2000 or MSDE 7.0), and does it reside on the BES? The computer name shouldn't matter one bit with the BES itself - however the database may need a single change with the computer name change (although it really shouldn't).

blackberry1 · 07-24-2006, 02:27 PM

"The computer name shouldn't matter one bit with the BES itself - however the database may need a single change with the computer name change (although it really shouldn't)."

Exactly,worse case scenario you may have to manually update a 1 or 2 of table s after the restore.

Netbios name sometimes does not get update in the table MDSConfig>MDSHost

I think RIM may have fixed that now and you don't have to worry

captkave · 07-24-2006, 02:54 PM

We have MSDE 2000 and it does reside on the BES. Can I simply copy MDF and LDF file from the config database to a temp location? Do I need to do anything with CFG file?

blackberry1 · 07-24-2006, 03:00 PM

Yes you can ,copy them and put them in the SQL data directory of the new Server and attach the datanase,copying alone won't do it.

C:\MSSQL7\Binn>osql –E
1> exec sp_attach_db @dbname = 'besmgmt',
2> @filename1 = 'C:\MSSQL7\Data\besmgmt.mdf',
3> @filename2 = 'C:\MSSQL7\Data\besmgmtlog.ldf'
4> go

jibi · **OS:** 4.6.0.171

also, just a suggestion prior to your upgrade. you MAY want to think about going ahead and upgrading the current installation to 4.0 SP5a, assuming you're using BESX (otherwise, whatever the latest SP-level is).

as for the rest of the move, all you will need to do is install the SAME version of BES on the new hardware, along with all service packs from the one you're moving from. you will need to keep the following FOUR items the same: BES service account, BES instance name (CORPBES11, etc), the SRP identifier, and the SRP auth key.

also, and most importantly, in the process of building this new server, DO NOT start the BES application or services! at the end of EVERY installation, uncheck the box that states to start the services. if it prompts you to reboot the server, BEFORE YOU DO SO, go to Windows Services and set EVERY BlackBerry service to MANUAL. if it never prompts you to reboot, then go ahead and set these services to manual ANYHOW (until the migration has been completed). Under NO circumstances do you want to start these services with the same SRP ID, etc. while the current production server is running - it will IMMEDIATELY disable your SRP and you'll have to contact RIM to have it re-enabled.

just a friendly warning...

captkave · 07-25-2006, 02:40 PM

Thank you all.

captkave · 07-25-2006, 03:12 PM

How about upgrading the OS from Windows 2000 to Windows 2003? Do I need to do anything special regarding running a different OS?

blackberry1 · 07-25-2006, 03:19 PM

Be as 2003 SP-1, make sure MDAC is atleast 2.8 sp-1

parasonic · 08-04-2006, 03:42 PM

I'm working on a migration myself. We currently have BES 4.0.1 running on a machine but only have a BES 3.6 CD. I can get 3.6 installed, no problem, but upgrading to 4.0 poses a big problem. The installer wants to upgrade the database, but it always fails. I have tried a blank test database, and that has failed. We are running MS SQL server on another machine (which I have added to the ODBC in Control Panel and in the BB server config). How can I get my software all up to date so that I can do the Knife-Edge Cutover?

Thanks.

blackberry1 · 08-04-2006, 07:10 PM

What is the error message you get when you attempt to upgrade the database
Search for db_install logs. Post the error messages you get and the ones you see in this log file

parasonic · 08-07-2006, 08:57 AM

Quote:

Originally Posted by blackberry1

What is the error message you get when you attempt to upgrade the database
Search for db_install logs. Post the error messages you get and the ones you see in this log file

Code:

[40000] (08/07 08:46:40):{0xC00} [DIAG] EVENT=Thread_report, THREADID=0xC00, THREADNAME="DebugLogger"
[30000] (08/07 08:46:40):{0x1F4} SQL Informational Message from CBESDBInstaller::Connect:  Changed database context to 'master'.
[30000] (08/07 08:46:40):{0x1F4} SQL Informational Message from CBESDBInstaller::Connect:  Changed language setting to us_english.
[30000] (08/07 08:46:40):{0x1F4} SQL Informational Message from CBESDBInstaller::GetDbmsVersionStringForSQLServer.execute:  Changed database context to 'master'.
[30000] (08/07 08:46:40):{0x1F4} SQL Informational Message from CBESDBInstaller::GetDBVersionForSQLServer.executeuse:  Changed database context to 'BESTest'.
[30000] (08/07 08:46:40):{0x1F4} SQL Informational Message from CBESDBInstaller::GetDBVersionForSQLServer.execute:  Invalid object name 'ServerDBVersion'.
[30000] (08/07 08:46:40):{0x1F4} SQL Informational Message from CBESDBInstaller::GetDBVersionForSQLServer.executeuse:  Changed database context to 'BESTest'.
[30000] (08/07 08:46:40):{0x1F4} SQL Informational Message from CBESDBInstaller::GetDBVersionForSQLServer.execute:  Invalid object name 'ServerDBVersion'.
[30000] (08/07 08:46:40):{0x1F4} SQL being executed:
 /****************************************************************************
 backup.sql
  
 This SQL script will backup the BES Mgmt database
 
 (C) 2001-2004 Research In Motion Limited.
 ****************************************************************************/
/*
 * Note C:\Program Files\Microsoft SQL Server\MSSQL\Data will be defaulted to C:\Program Files\Microsoft SQL Server\MSSQL\Data\Backup
 */



--DECLARE @Date varchar(30), @BackupName varchar(50), @BackupFile varchar(100)
--set @Date = convert(varchar,getdate(),112)

--SET @BackupName = 'BESTest_' + @Date

DECLARE @BackupFile varchar(128)
SET @BackupFile = 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\BESTestBKUP.dat'
BACKUP DATABASE "BESTest" TO DISK = @BackupFile
[10000] (08/07 08:46:42):{0x1F4} SQL Error Message from CBESDBInstaller::ExecuteSql.stillEx: SQLSTATE: 42000 Native error: 3201 Message: Cannot open backup device 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\BESTestBKUP.dat'. Device error or device off-line. See the SQL Server error log for more details.
[10000] (08/07 08:46:42):{0x1F4} SQL Error Message from CBESDBInstaller::ExecuteSql.stillEx: SQLSTATE: 42000 Native error: 3013 Message: BACKUP DATABASE is terminating abnormally.
[10000] (08/07 08:46:42):{0x1F4} Terminating because backup had a problem.  See log file for details

Thanks for the help...

ld-runner · 08-07-2006, 12:36 PM

i have done this a few times...
you must keep the same servername for the BES. Not the domain name, hte BES server name.
i setup the server per RIMs documents.
i stop all BB and SQL services on the running BES.
install the new BES onot the new server. (remeber to keep the same BES name)
when you get to the part about restarting, do the restart.
when it comes back, continue with install and allow the new BES to create the BESmgmt database.
as soon as the database is succesfully created, cancel the install
now, on the new server, stop all BB services and mssql services. (won't be but 1 or 2 running)
on the new server, delete BESmgmt database files. (C:\Program Files\Microsoft SQL Server\MSSQL\Data\BESmgmt.*)
go to the old server and copy C:\Program Files\Microsoft SQL Server\MSSQL\Data\BESmgmt.* to the new server in the same location.
now...find your BES4.1 distro and run setup.exe or just reboot
when the system comes back on, everything will be just as it was.

ld-runner · 08-07-2006, 12:42 PM

one thing that you may have to do after everything is back up is run 'Blackberry Server Configuration'. under the MDS Advanced tab, there will be 2 BlackBerry Enterprise Severs listed. one will the the BES name of the old server (that is the one you did not change) and the other will be called 'NONE'. Highlight the correct name (not NONE) and click apply. then your MDS services will start to work again. if you have questions, let me know. like i said, i have done this a few times. the first time was with RIM's help. i found a few shortcuts.

parasonic · 08-07-2006, 01:00 PM

Thanks for the info. I may try this later on today.

blackberry1 · 08-07-2006, 01:34 PM

Follow RIM KB Article Number: KB-04456 to resolve your issue

I am quite sure the first suggestion made by "id-runner" , will do nothing for your issue.The approach is completely flawed.

Aka : Your don't copy and paste a SQL database,its either restored or attached.

In your case you can backup and restore your database to the blank database that will be created once your BES Installation will succeed.

Or you could attach the database as shown in one of my posts in the same thread.

jsalvad · **BES 4.1 to BES 4.1 -** 12-07-2006, 06:25 PM

I just upgraded a bes 2.2 to bes 4.1 on the same box. Now I wanted to remove the bes services on that box and move to a new box. I purchase the migration kit from Blackberry and build a new bes 4.1. The old srp will expire in 90 days. Now whenever I activate a new user on the new bes 4.1 server it times out, but activating it on the original box works fine. Also how do I move those users from the original box to the newly built box? Do I use export/import?

parasonic · 02-26-2007, 05:53 PM

I need some help now...

We put this migration back by several months, and I need to get it done. Big problem, though...the knife-edge cutover guide has been removed from blackberry.com!

Does anyone have the file saved anywhere?

wrmckinn · **besmigration issue -** 03-09-2007, 11:58 AM

In trying to migrate users from a 3.6.4 server (OldSrv) to a new 4.1.3 server (NewSrv)

using the besmigration tool, zero users get migrated. OldSrv has 40 blackberry users.
SQLSrv is the SQL server with the databases. The only clue that something is amiss is one

line in the log file: BlackBerry Server OldSrv: Cannot deduce progress information

my comand line:

besmigration -s "Blackberry Server Management" OldSrv NewSrv -d SQLSrv newbesmgmt -l log

-t status

screen output:

User migration logs into log
Successfully connected to database newbesmgmt on host SQLSrv using trusted

authentication
Migrating BES OldSrv. Primary BES NewSrv
0 user(s) migrated 0 user(s) failed for BES OldSrv
All users from BES OldSrv are migrated to BES NewSrv
BlackBerry Server OldSrv successfully migrated

status: file:

PRIMARYBES NewSrv
BESMIGRATED OldSrv

log file:

=== Log started on 3/9/2007 at 9:50:32 ======================================
Log file log creation OK
Initializing database newbesmgmt at machine SQLSrv using trusted authentication
Database connection OK
Migrating BES OldSrv to primary BES NewSrv using MAPI profile Blackberry Server Management
Migration does not write status to the registry
BlackBerry Server OldSrv: Needs to be migrated
MAPI: Initialized MAPI with profile Blackberry Server Management
MAPI: Opened message store with profile Blackberry Server Management
MAPI: Mapi database successfully opened
BlackBerry Server NewSrv: Found in the database
BlackBerry Server NewSrv: Has 0 users
BlackBerry Server OldSrv: Cannot deduce progress information
BlackBerry Server OldSrv: 0 user(s) migrated 0 user(s) failed
BlackBerry Server NewSrv: No errors detected during migration
BlackBerry Server NewSrv: Finalizing secondary BES
Migrating properties
Property Type: Migrating...
Property SRPKey: Migrating...
Property SRPPort: Migrating...
Property SRPHostName: Migrating...
Property SessionId: Migrating...
Committing properties to the database
Database record successfully created/updated
BlackBerry Server OldSrv: Successfully migrated
Migration finished with return code 0
Writing status to file status
Status written to status
Uninitializing migration module
Disconnecting the database
Database disconnect OK
Closing the log file
=== Log ended on 3/9/2007 at 9:50:32 ======================================