BlackBerry MVS high availability

The BlackBerry Mobile Voice System high availability installation is illustrated below.

High availability ensures that there is no single point of failure of BlackBerry MVS components. To provide high availability:
  1. Install two BlackBerry MVS Server instances.
  2. Configure both BlackBerry MVS Server instances (through the MVS Console).
  3. Use the MVS Console to configure a high availability association of one of the BlackBerry MVS Server instances with the other. The association creates a high availability pair.

High availability is achieved through active-active and active-standby models of redundancy. The following table summarizes the redundancy model for each BlackBerry MVS component:

Component Model

MVS Data Manager


MVS Console


MVS Witness Server


MVS Event Manager


MVS Session Manager (except MVS Event Manager)


MVS BlackBerry Enterprise Server Connector


In an active-standby model, you associate two BlackBerry MVS Server instances to form a high availability pair. When you associate two MVS Session Manager instances, one of the MVS Session Manager instances becomes active and the other standby, and one of the MVS BlackBerry Enterprise Server Connector instances becomes active and the other standby. The components themselves determine which one becomes active and which one standby. If the active component fails, the components and the MVS Witness Server manage the failover from the active component to the standby component.

In an active-active model, both components are always active. If a component fails, the BlackBerry MVS automatically stops using that component.

For example, because the MVS Data Manager instances use an active-active model, two MVS Data Manager instances provide redundancy for the high availability pair. By comparison, there must be one active and one standby MVS Session Manager for every high availability pair.

Was this information helpful? Send us your comments.