You can configure your
BlackBerry UEMenvironment so that it continues to function in the event of a severe disruption.
This document describes a hot/warm disaster recovery configuration for a large organization with a primary site and a remotely located secondary, or disaster recovery, site. For detailed information about installing the components, see the installation and configuration documentation at docs.blackberry.com.
Two general principles underlie the configuration:
- Avoid cross-site configuration, connectivity traffic, and database access because the network latency and server searches between two sites can lead to slower response times and undesired timeouts.
- Configure the secondary site with servers up and allBlackBerryservices off because this allows rapid connectivity timeouts at the application layers, rather than slower TCP timeouts. In addition, it allows security patches for the operating system to be applied regularly in a timely fashion.