
BES 5.0 Best Practices Migration Strategy
With WES2009 only a week away, it’s almost certain that we’re about to have access to a brand new version of the BlackBerry Enterprise Server (BES) to work with. In a previous blog post, I talked about the new features in BES 5.0. Now it’s time to talk about some best practices we’ve observed when organizations migrate from one BES version to another.
Stabilize the Existing Environment
Before any migration can begin, it’s important to ensure that the existing environment is running as smoothly as possible. It’s worth the extra effort to stabilize the existing environment before a migration rather than to deal with issues that arise when upgrading the existing environment or migrating off of it. Due to the mission critical nature of the BlackBerry platform, performing a BES migration can be compared to changing the engine on an airplane while it’s in flight – you want everything to go just right.
Identify BlackBerry Orphans
Over time in any BlackBerry environment, BlackBerry users can end up in a state that places undue stress on the BES. This would happen, for example, when a user leaves the company and is removed from the messaging system, but not the BES; a user who has been added to the BES but never activated the device; or a user is defined in multiple BES domains. Before beginning any BES upgrade or migration, all of these burdensome users should be removed from the BES. You will want your BES humming away at peak efficiency, doing as little work as needed, before, during and after the migration.
Eliminate Under-Utilized Resources
Some users have devices that they don’t really use or don’t use very much. Before beginning an upgrade or migration, many organizations prune low- or no-usage BlackBerry users from the BES. This helps cut overall costs and reduce the number of users affected by the migration. There’s no need to put them through the process if their device is not being used.
Assess Migration Readiness
Some users will require special handling during a migration, there’s no way around it. It could be that they’re VIP’s, but it also could be because the user is using a device or running a BlackBerry Device Software version that cannot be migrated using automated tools. Each migration project usually begins with a complete end-to-end environment inventory to identify unsupported devices, inaccurate IT Policy application and users that have devices (and are using them) but shouldn’t because of their job responsibility or level within the company.
Migrate in Batches
The Help Desk call load is likely going to peak during the migration, there’s no getting around that. To mitigate any issues related to customer satisfaction and response times, many organizations migrate their users or upgrade their BES in batches, spreading the changes across time rather than all at once.
Measure, Measure, Measure & Compare
Many organizations have recognized the value of understanding the effect transitions such as a BES migration can have on system and end-user performance. Before the BES migration begins, BES and end-user performance should be baselined then regularly measured and compared to the baselines created both during and immediately after the migration. Administrators have to be ready to adjust the configuration or allocation of resources to ensure that overall system performance doesn’t degrade because of the upgrade or migration.
Regularly Optimize Resource Allocation
Of critical importance for a BlackBerry environment is the ability to optimize the distribution of BES, Mail Servers and users. End-user and BES performance will likely suffer when a BES is processing mail and PIM data for too many users or across too many mail servers. A smoothly running BlackBerry environment has an even distribution of users and mail servers for each BES.
At the conclusion of a migration, most organizations end up with an even distribution of users and/or mail servers across BES. As users are added and removed from the BES or as users move from one mail server to another, this even distribution can be disrupted. When one BES is handling more users or talking to more mail servers than another, message delivery times and user satisfaction can suffer. Organizations must plan to regularly assess resource allocation and adjust for optimal performance.
Coming to WES 2009? I’d love to hear your BES migration best practices, and what you’re looking forward to in BES 5.0. Stop by the Mobile User Management Lounge. And don’t miss The Lounge Birds of a Feather discussion on BES 5.0 Migration Strategies on Thursday at 9:00am.
John Wargo, Product Manager