Planning high availability for a BlackBerry UEM domain
BlackBerry UEM
domainBlackBerry UEM
uses an active-active high availability model to minimize service interruptions for device users. To configure high availability, you install multiple instances of BlackBerry UEM
, each on a separate computer. Each instance connects to the BlackBerry UEM
database and actively manages user accounts and devices.High availability in
BlackBerry UEM
includes the following features:
Feature | Description |
---|---|
iOS , Android , and Windows devices can connect to any BlackBerry UEM instance | iOS , Android , and Windows devices can connect to any BlackBerry UEM Core instance to receive device management, policy, and configuration updates. If one or more BlackBerry UEM Core instances is unhealthy, iOS , Android , and Windows devices connect to one of the healthy instances. Load balancing is performed automatically. As a result, device management services continue uninterrupted. |
Access the management console and BlackBerry UEM Self-Service from any BlackBerry UEM instance | If there is a problem with the management console or BlackBerry UEM Core for a BlackBerry UEM instance, you can continue to access the management console and the BlackBerry UEM Core of any healthy instance. |
Round-robin DNS pool for the management console | You can use third-party software to configure a round-robin DNS pool that connects to the management console in each BlackBerry UEM instance. If there is a problem with a console, the pool makes sure that you connect to a working console. |
Round-robin DNS pool for the web services API | You can use third-party software to configure a round-robin DNS pool that connects to the web services API in each BlackBerry UEM instance. If there is a problem with one web services API, using the pool makes sure that you connect to a working web services API. If there is a problem using the web services API pool, check the round robin mechanism to ensure the web services API is correctly connected. |
BlackBerry Connectivity Node | You can install one or more instances of the BlackBerry Connectivity Node to add additional instances of the device connectivity components to your organization’s domain. You can also create server groups to specify regional data paths for secure connectivity and to set up high availability for the components of the BlackBerry Connectivity Node . For more information, see High availability and the BlackBerry Connectivity Node. |
BlackBerry 10 devices | If BlackBerry 10 devices on a BlackBerry UEM instance cannot connect to work resources using enterprise connectivity, those devices are reassigned to healthy BlackBerry UEM instances. BlackBerry 10 devices can use enterprise connectivity to access email and calendar data, the work browser, and the organization’s network. Most management tasks (for example, assigning profiles) require enterprise connectivity to complete successfully. The BlackBerry Affinity Manager assigns BlackBerry 10 devices to a BlackBerry UEM instance, monitors enterprise connectivity for each instance, and moves BlackBerry 10 users if there are issues with enterprise connectivity. The BlackBerry Affinity Manager cannot assign iOS , Android , or Windows devices to a specific BlackBerry UEM instance.Only one BlackBerry Affinity Manager is active. The other BlackBerry Affinity Manager instances are on standby. If there is a problem with the active BlackBerry Affinity Manager , each standby instance starts an election process to become active. The instance that completes the election process first becomes the active BlackBerry Affinity Manager . |
When
BlackBerry UEM
is completing a recovery action, affected users experience a short service interruption. The duration depends on a number of factors, including the number of BlackBerry 10
devices and the number of BlackBerry UEM
instances. When BlackBerry 10
users are reassigned to another instance, the average down-time is 3 minutes. When a BlackBerry Affinity Manager
failover occurs, the average down-time is 10 minutes.