View Single Post
Old 10-26-2010, 05:24 PM   #5 (permalink)
New Member
Join Date: Jun 2005
Location: Houston, Texas
Model: 8530
Carrier: Verizon
Posts: 7
Post Thanks: 0
Thanked 0 Times in 0 Posts

Originally Posted by noname View Post
Start from scratch better. I have tried to do a in-place upgrade and apparently it installed another SQL instance instead. This is because BES 5.0 installed local SQL Express as a named instance named "BLACKBERRY" and when I ran the installer for SQL 2005 server, it created the default instance and effectively you have 2 SQL instances:-

1 x SQL Expresss 2005 with BLACKBERRY instance
1 x SQL 2005 Server with default instance

You may have better luck figuring ways to really do an in-place upgrade over the existing one.

Also, please do not go with this configuration (same as many of my customers - just to save cost but not troubles later on which may be more expensive). It just doesn't make sense and defeats the purpose of building a true High Availability solution.

(A) NO NO Configurations

(1) Computer A
- BES 5.0 Primary + SQL Principal Server

(2) Computer B
- BES 5.0 Standby + SQL Mirror Server

Just for laugh: We call this "cheapskate" configurations

Serious Now: This is not a truly distributed configurations and it is not scalable at all. There will be system resources contention and your BES server's performance will be affected. Also if Computer A has a hardware failure, your SQL server will be also down and you will be stuck with a broken state Computer B. You won't be able to manually promote the BES Standby server via BAS (go try out and you will know). I'm no SQL wizard, but I wonder how easy it will be to promote SQL Mirror Server as Principal server in this situation. That will be a question for the SQL Administrators here.

(B) Better Configurations

This is more scalable. Computer can be easily managed by plugging and replacing as and when required and will not disturb the other computers. In short, the disruption is minimal when one of them is offline.

(1) Computer A - BES Core services (primary BES)
(2) Computer B - BES Core services (standby BES)
(3) Computer C - BAS services
(4) Computer D - MDS-IS service (Optional)
(5) Computer E - BES Monitoring services (Optional)
(6) Computer F - SQL 2005 SP3 Principal Server
(7) Computer G - SQL 2005 SP3 Mirror Server

RIM did a very bad job by not giving out this specific best-practice information when BES 5.0 first released and there are many customers already built their "mashed" configurations.

I would advised to go configuration (B), anyway nowadays computers are VM images and can be easily built effortlessly.

I am a Lotus Domino Administrator but, am tasked with supporting BES on Domino. We have worked our way up to almost 600 users (started with only 36) and now are need of splitting our user base to 2 BES Servers in 2 Datacenters. After reading your note, it has forced me to evaluate a different scenario for our resolve.

Currently, we have 1 BES 5.0 Server. Originally, we had the plan to create a New Primary BES 5.0.2 in our Houston Datacenter with a Standby in our Atlanta Datacenter and then a Primary BES 5.0.2 in our Atlanta Datacenter with a Standby in our Houston Datacenter. We will be installing all of these on VMs.

So, now, my question is what should our scenario be? We have Mail Servers in Atlanta and Mail Servers in Houston (user base about 1/2 and 1/2). How would you suggest we plan our build-out for Failover / Disaster Recovery? Obviously, our original plan was not a good one and we do not want to have to work in reactive mode should we have failures. Will mirroring be a part of this?

Any suggestions / guidance you may have would be greatly appreciated.

Thank you.
Offline   Reply With Quote