[knottyrope]

I have prepared SQL with createdb

Did a test run of MSDE backup with all BB services stopped.

Did restore to SQL but had to click Overwrite the database in options for it to work. Noticed that BESAdmin was no longer owner, changed that.

Using the PC for remote Blackberry manager changed SQL Database name and choose not to backup SQL.
Connected to the new database with Remote BB Manger and could see users.


SO now I am ready for the real deal.
Stop BB services
backup DB
copy backup file to SQL
restore DB
Change owner to BESAdmin
Change BES database config
start up BB services

PRAY this will work.

Any input?

[knottyrope]

Oh well I did it anyways.

And no one called to complain that BES was down, yet.

[knottyrope]

Backup ran last night, I am good to go.

This was not as tough as I initially thought.
Hope it changes the minds of some others.

[CanadianCrack]

Thanks for posting this Knottyrope

I'm looking at changing over to sql from MDSE soon.
Good to know it's worked well for you.

[knottyrope]

Only issue that I had was database permissions.
Might be best to logon to SSMS with besadmin to do database managment.

When I moved the files today to the correct drive (raid 10) instead of the OS drive I had to make BESAdmin the owner again, since I was the one connected, it made me the owner.

[knottyrope]

Running smooth so far.
Only thing now is to uninstall MSDE. Not sure if it requires a reboot or not.

[knottyrope]

Removed MSDE last week, no reboot needed with win2k.
Bes is running happy.
Cleaned up program files directory
Now have SQL 2005 doing the back up to file and delete old ones 2 days or older.

[curriertech]

I'm glad to hear that this was so easy! I'll be doing the same pretty soon. I've been using this document as a planning guide.

[snogger]

We are preparing to move from MSDE to SQL also. The SQL database will be hosted on a SQL server rather than on the BES server itself.

The person who was originally in charge of the two Blackberry servers was let go and I was assigned as support. Nothing like learning under fire as the only thing I knew how to do before he left was how to read my mail on my blackberry.

I have the KB articles printed out and lots of notes already added but have some questions I can't seem to find an answer to.

I was wondering if you all could give me some idea of the time frame.

From the time I take down the current services, back-up the data, restore the configuration to the new SQL server and start the services on the new server are we looking at an hour, hours, or a day??

we plan on working with the Sql server person to have the Sql part ready before we make the move so that task should be done.

BES is 4.1.6, Domino is 6.5

We are moving the current BES Server off old hardware to new hardware at the same time.
We have the new server loaded with Domino already and wondering if we can install the BES Software now with the same license without starting the services?
Or do we need to wait until the day we shutdown the current Server?

We are planning on leaving the old server setup with the local MSDE with the back out plan of firing it back up if our switch to SQL and the new hardware fails.
Any ideas if there will problems backing out that way if we have to?

Any insight would be GREATLY appreciated. I've had two months now to figure out how to work with the servers and support the current environment and now I am charged with this switch over. Learning on the job, with no training has been interesting to say the least.

[bacid]

you can't install BES without a key so unless you have their migration package you'll have to install BES the day you do a cutover.. knife-edge as RIM calls it.

I did exactly what you described, moving BES to a new server and migrating from MSDE -> SQL (which is also on a diffferent server) all at once..

The entire process only took about 1hr, I followed all the documentation provided by RIM and didn't run into any issues.

One thing to keep in mind is that because your servername is changing you'll need to make modifications to the SQL database.

It's been a long time since I did this but if you search for my post from awhile back there was a lot of good info provided by the other posters. I believe I also made a final post which summarized what I had to do.

Good luck, and don't worry, it's EASY!

[whitetiger78]

Thanks for this post. I am planning on doing this weekend. My inexperience with SQL, made me putting this off for a long time.

Real Motivator!

[snogger]

Originally Posted by bacid

you can't install BES without a key so unless you have their migration package you'll have to install BES the day you do a cutover.. knife-edge as RIM calls it.

I did exactly what you described, moving BES to a new server and migrating from MSDE -> SQL (which is also on a diffferent server) all at once..

The entire process only took about 1hr, I followed all the documentation provided by RIM and didn't run into any issues.

One thing to keep in mind is that because your servername is changing you'll need to make modifications to the SQL database.

It's been a long time since I did this but if you search for my post from awhile back there was a lot of good info provided by the other posters. I believe I also made a final post which summarized what I had to do.

Good luck, and don't worry, it's EASY!

Thanks!

As I said, I am brand new to Blackberry and hope to take a training class (or 3 ) within the next couple weeks. Until than I'm just in a constant state of confusion

An update is that at this point we plan on doing the MSDE to SQL one weekend. We will let that go for a week or two and than move from the old hardware to the new hardware.

At this time the BES Server name and the Domino Server name will stay the same even when we move to new hardware.

The only change will be the NT server name which, from what I can find, shouldn't affect BES.. ... hopefully.. ?

The last person in charge of the Blackberry's here started the MSDE to SQL conversion. We don't know what steps he was following or what he did but after 5 hours they stopped the conversation and went back to MSDE.

So I am just hoping to make this first move as painless as possible for the users and of course myself.

Thanks again!