Planning high availability for a BlackBerry UEM domain
BlackBerry UEMuses 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 UEMdatabase and actively manages user accounts and devices.
High availability in
BlackBerry UEMincludes the following features:
Windowsdevices can connect to any
Windowsdevices can connect to any
BlackBerry UEM Coreinstance to receive device management, policy, and configuration updates. If one or more
BlackBerry UEM Coreinstances is unhealthy,
Windowsdevices 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-Servicefrom any
If there is a problem with the management console or
BlackBerry UEM Corefor a
BlackBerry UEMinstance, you can continue to access the management console and the
BlackBerry UEM Coreof 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 UEMinstance. 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 UEMinstance. 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 Nodeto 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 10devices on a
BlackBerry UEMinstance cannot connect to work resources using enterprise connectivity, those devices are reassigned to healthy
BlackBerry 10devices 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.
BlackBerry Affinity Managerassigns
BlackBerry 10devices to a
BlackBerry UEMinstance, monitors enterprise connectivity for each instance, and moves
BlackBerry 10users if there are issues with enterprise connectivity. The
BlackBerry Affinity Managercannot assign
Windowsdevices to a specific
BlackBerry Affinity Manageris active. The other
BlackBerry Affinity Managerinstances 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.
BlackBerry UEMis completing a recovery action, affected users experience a short service interruption. The duration depends on a number of factors, including the number of
BlackBerry 10devices and the number of
BlackBerry UEMinstances. When
BlackBerry 10users are reassigned to another instance, the average down-time is 3 minutes. When a
BlackBerry Affinity Managerfailover occurs, the average down-time is 10 minutes.