BlackBerry MVS high availability

BlackBerry® Mobile Voice System high availability consists of an active MVS Session Manager and a standby MVS Session Manager. You can use high availability to help provide minimum downtime for BlackBerry MVS users if one of your organization's MVS Session Manager instances stops responding or requires maintenance. The failover process is designed to be automatic, but you can perform a manual failover before you perform scheduled maintenance.

When you configure the BlackBerry MVS for high availability, you install the MVS Console, active MVS Session Manager, and standby MVS Session Manager on different computers in the same BlackBerry Domain. Both MVS Session Manager instances use the same MVS Console and BlackBerry Configuration Database.

Both MVS Session Manager instances connect to the MVS Console. The MVS Console periodically checks that the active MVS Session Manager is healthy. If the health of the active MVS Session Manager falls below the failover threshold or if the active MVS Session Manager stops responding, the MVS Console promotes the standby MVS Session Manager.

If any of your organization's users are on BlackBerry MVS calls when the active MVS Session Manager stops responding, the calls remain active but the users cannot use the features that are typically available to them during a call. While the active MVS Session Manager fails over, the users cannot send or receive any BlackBerry MVS calls until the failover process completes.

You cannot configure high availability for the MVS Console because you can install only one MVS Console in a BlackBerry Domain.

To manage your organization's users, if the computer that you installed the MVS Console on stops responding, you must install another MVS Console instance and connect it to the active and standby MVS Session Manager instances.


Was this information helpful? Send us your comments.