Migrating Blackberry Enterprise Server Express 5.0 database to new SQL Server
I am attempting to migrate the database for BES express 5.01 to a new SQL server. I have directions here that are a bit confusing:
http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB03112
1) In step 3 they say make sure that the MS Server Agent service is running. It is not in the list of services and I've never come across it before. There is a note that says it will not appears for MS SQL Server 2008 express but I am using the full version of SQL 2008 and yet do not see the service. Is it safe to ignore?
2) I no longer have the original installer that was used for the BES instance (5.01) we are running. In step 4 they ask you to run setup.exe (which I can't find at the location they specify). I did download what is currently available from RIM but it appears to be version 5.02 and I'm worried the difference will be enough to cause problems.
3) With BES 5 you are required to run the installer again to set the database name/location and I have the same concern here. I am running 5.01 but the installer is for 5.02. Not sure if I can do this or if it might cause trouble.
I would greatly appreciate any assistance with this migration, thanks!
http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB03112
1) In step 3 they say make sure that the MS Server Agent service is running. It is not in the list of services and I've never come across it before. There is a note that says it will not appears for MS SQL Server 2008 express but I am using the full version of SQL 2008 and yet do not see the service. Is it safe to ignore?
2) I no longer have the original installer that was used for the BES instance (5.01) we are running. In step 4 they ask you to run setup.exe (which I can't find at the location they specify). I did download what is currently available from RIM but it appears to be version 5.02 and I'm worried the difference will be enough to cause problems.
3) With BES 5 you are required to run the installer again to set the database name/location and I have the same concern here. I am running 5.01 but the installer is for 5.02. Not sure if I can do this or if it might cause trouble.
I would greatly appreciate any assistance with this migration, thanks!
Eric B
Doesnt full version of SQL allow High availability? You can setup a 2nd sql as a backup/failover to the first then bring down the first one.
ASKER
No idea at all how that might work, I am just trying to follow the explicit directions on moving the database found in the link above.
Hi,
You should be able to download the BES 5.0 Service Pack 1 Installer to run against your BES 5.0.1 environment?
Regards,
RobMobility.
You should be able to download the BES 5.0 Service Pack 1 Installer to run against your BES 5.0.1 environment?
Regards,
RobMobility.
Hi,
Just to clarify - the Service Pack 1 installer.
Regards.
Rob Mobility.
Just to clarify - the Service Pack 1 installer.
Regards.
Rob Mobility.
ASKER
Hi Rob
I'll check with RIM again and see if I can find it for download. That would solve at least one of the problems. I ran through the process last night but got an error:
The Update Schema portion of the directions require that we run a utility (createdb.exe) from the original installer to create the schema on the new SQL server. Running this utility does complete but with an error: Unexpected Exchange Type=ExchangeX. I am uncertain if we can ignore this error.
I'm still also unsure about the issue with the MS server agent service.
I'll check with RIM again and see if I can find it for download. That would solve at least one of the problems. I ran through the process last night but got an error:
The Update Schema portion of the directions require that we run a utility (createdb.exe) from the original installer to create the schema on the new SQL server. Running this utility does complete but with an error: Unexpected Exchange Type=ExchangeX. I am uncertain if we can ignore this error.
I'm still also unsure about the issue with the MS server agent service.
Hi,
You shouldn't need to run the createdb.exe file as the BESMgmt (assuming you're using the default) database should have been migrated when you moved from SQL Express to SQL Server 2008?
I believe that the createdb.exe will still be part of the service pack 1 download, however.
Regards,
RobMobility.
You shouldn't need to run the createdb.exe file as the BESMgmt (assuming you're using the default) database should have been migrated when you moved from SQL Express to SQL Server 2008?
I believe that the createdb.exe will still be part of the service pack 1 download, however.
Regards,
RobMobility.
Hi,
I stand corrected, you need to crreate the new database schema using createdb prior to importing the exported database from SQL Express.
Regards,
RobMobility.
I stand corrected, you need to crreate the new database schema using createdb prior to importing the exported database from SQL Express.
Regards,
RobMobility.
Hi,
Just make sure that you don't have the installation files on c:\research in motion?
Regards,
RobMobility.
Just make sure that you don't have the installation files on c:\research in motion?
Regards,
RobMobility.
ASKER
Hi rob
Right, according to the directions I need to modify the .cfg file from the installation package Database folder and then run that utility to generate the schema. The problem is when I do that I get the error:
Unexpected Exchange Type=ExchangeX.
I don't see any new database under the SQL management tool on the new server after running it so I assume the error is critical. The directions they provide are, lets say...lacking. :)
Right, according to the directions I need to modify the .cfg file from the installation package Database folder and then run that utility to generate the schema. The problem is when I do that I get the error:
Unexpected Exchange Type=ExchangeX.
I don't see any new database under the SQL management tool on the new server after running it so I assume the error is critical. The directions they provide are, lets say...lacking. :)
Hi,
Apologies for asking - you running the utility on the SQL Server not the BES?
You need to 'explode' the files onto the SQL server and run it there - it creates the database and associated files.
Note that you may need to specify different data file and log file locations within the config file if your SQL is configured that way (i.e.D for data, E for logs etc.).
I wouldn't expect the SQL box to know about Exchange at this point! from a BlackBerry perspective!
Regards,
RobMobility.
Apologies for asking - you running the utility on the SQL Server not the BES?
You need to 'explode' the files onto the SQL server and run it there - it creates the database and associated files.
Note that you may need to specify different data file and log file locations within the config file if your SQL is configured that way (i.e.D for data, E for logs etc.).
I wouldn't expect the SQL box to know about Exchange at this point! from a BlackBerry perspective!
Regards,
RobMobility.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No final solutions posted