Blackberry devices are quickly growing in popularity for both business and personal uses (Browsing over BIS (RIM proxy) is fast enough for the mobility and its economical too, in all ways managing the Blackberry Enterprise Server is also a business critical in compare to any corporate messaging systems (Like Exchange or Lotus Domino).
This article examines how high availability can be accomplished using failover software, however a single server running on standalone mode is always a night mare to any level of administration and it's also a disaster threat to the entire organization mobility services, How can we have the 99% uptime, Let's see how we can achieve this:
Here by there are two solutions to overcome these issues:
Options -1
This only feasible, If you already have 02 BES licenses , then the best thing for you to do would be to split 50% of users on BES-1 other 50% on BES-2 and make sure they are in the same BB domain, same subnet with your messaging systems and sharing a common SQL DB (Recommended to have SQL cluster in place), as this will work when one of your BES goes down you can eventually move the affected users from one BES to the other and they would be all set to function in minutes.
Note: Make sure you have good backup solution in place.
Putting half your user on server 1 and half on the other is NOT a very smart failover solution. If one of those servers were to fail then half your users are down without any backup plan, during the failure the Half of users would be still remain down until you initiate the BlackBerry manager to move from one BES to the other.
As this is one of the failover solution posted across KB/forums (Not recommended as a DR), which doesn't make sense as a failover solution.
Note: The disadvantages for SMB (Small, Medium, Business) is it required 02 licenses and it makes management to think twice on the license cost, However SMB still as the Options-2 to opt.
Options-2
Here is the smart and intelligent failover solution, which follows the RIM article KB04647, if you are currently running BES 4.0 or higher or follow KB05032 if running 3.6.
Basically what you are doing in a nutshell is having 2 boxes with a mirror image BES, for example you currently have a 4.0.6 BES named BES-1. What you would need to do, is install the EXACT same version of BES on the new box (BES-1 as your previous box) **VERY IMPORTANT**
Then depending on what types of database you use, as follow the below:
1) Remote SQL - you simply point the new server to the database running the remote SQL server
2) local MSDE/SQL - you need to create a backup of the database from your old server and then restore it onto the new server (if using the server and it goes down then all you would need to do is create a backup from the new server, copy it to the failover server and restore it there) (follow RIM article KB03112 for proper commands)
Basically all you need to do is make sure you are constantly upgrading/updating both at the same time, like wise:
- If you decide to upgrade your new 4.0.6 server to 4.1.2 then perform the same on secondary node as well.
- This applies even for OS/security patches as well. If you've added 20 new users on the new server then make sure you copy that database over to the old server to reflect the same changes.
All you need to do having an environment like this is to keep the services on one server stopped, This way if you have a server down issue all you need to do is start the services on the failover server (secondary server) and your users don't notice anything other than a possible short 10 minutes delay during the time you started the failover server.
This is one of the cost cutting Implementation BES failover scenarios, if you are limited with budget. Using the Disaster Recovery Guide (for Exchange) from Blackberry. However this is a point to be considered that there is a transactional database replication and snapshots between the primary and stand by servers and not just a database recovery (only possible if using full SQL - not MSDE).
The servers are installation/configuration are recommended to installed using the same SRP identifier (ensure the stand by instance BES services remains disabled and not using the same SRP at RIM or else it will be deactivated as a security threat) and make sure you specify the same BES server name (the physical machine/Host name is independent).
Option-3
These options will achieve the High Availability on BES using Failover Software "Neverfail" as this product will allow you to deploy an active/passive BES cluster. As this software basically clones your existing BES on a secondary BES, The secondary severs will act as hot standby and it takes over failover automatically and transparently, when the primary BES fails.
Best of all, the Neverfail for BlackBerry solution is priced for the small and mid-size market, and its manageability is awesome, which can be deployed locally or across the WAN.
This product as captured the market very quickly, even while competition with other brand "CA" XOsoft High Availability (formerly CA XOsoft WANSyncHA).
Neverfail is the leading technology in providing continuous high availability and operation to the Blackberry and Microsoft environment. For more details on Neverfail BES data sheet and case study, please find the links below:
• A link to Vodafone website and the existing partnership between them and NeverFail.
Who are the leading ISV's (independent software Vendors) in this segment?
Hello, Happy Reading! Please value your reading to post the poll. Thank you!
