Configuring high availability for BlackBerry Enterprise Service 10

If you want to enhance the stability and reliability of BlackBerry Enterprise Service 10, you can configure the core components to support high availability. A high availability configuration includes one or more high availability pairs. A high availability pair consists of a primary instance of the core components, and a standby instance of the same components that you install on a different computer. Both instances use the same SRP credentials, and are connected to the same BlackBerry Enterprise Service 10 databases.

The primary instance is the active instance that communicates with devices and manages data in the domain. BlackBerry Enterprise Service 10 monitors the health and availability of the primary instance and the standby instance using health parameters with predefined performance thresholds. If the health parameters indicate that the primary instance is not performing as expected (for example, a component is not responding), BlackBerry Enterprise Service 10 initiates an automatic failover of device service to the standby instance. BlackBerry Enterprise Service 10 also verifies that the standby instance is healthy enough to be promoted. The standby instance becomes the new primary instance, and device service continues uninterrupted. The instance that was previously the primary becomes the standby instance.

When a failover event occurs, device service fails over to all components on the standby instance, regardless of whether there was an issue with one or several components on the primary instance. Each core component is associated with the BlackBerry Device Service or the Universal Device Service; all of the core components fail over together and use the same primary instance.

You can configure as many high availability pairs as your organization’s environment requires. By default, the core components are configured for automatic failover. You have the option to turn off automatic failover, and you can initiate a manual failover at any time.

• Architecture: High availability for BlackBerry Enterprise Service 10
• Components that support high availability failover
• Components that do not support high availability failover
• Health parameters and the availability of BlackBerry Enterprise Service 10 components
• Prerequisites: Installing a standby instance of the core components
• Install a standby instance of the core components
• Fail over device service manually
• Switch the primary and standby instances
• Tasks to perform after an automatic or manual failover
• Turn off automatic failover
• Change the active Administration Console instance
• Monitoring a high availability configuration