Professional Documents
Culture Documents
Version: 5.0
Planning Guide
SWD-513447-0327035016-001
Contents
1 Overview: BlackBerry Enterprise Server.................................................................................................................................. 4
11 Configuring disaster recovery for the BlackBerry Enterprise Server across data centers............................................... 51
Using BlackBerry Enterprise Server components that you installed with a standby BlackBerry Enterprise Server in the
same data center............................................................................................................................................................................. 52
Creating pools of BlackBerry Enterprise Server components that are located in different data centers............................ 54
12 Glossary......................................................................................................................................................................................... 55
13 Provide feedback......................................................................................................................................................................... 57
14 Legal notice.................................................................................................................................................................................. 58
Planning Guide Overview: BlackBerry Enterprise Server
4
Planning Guide BlackBerry Enterprise Server high availability
5
Planning Guide How the BlackBerry Enterprise Server calculates health scores
Both BlackBerry Enterprise Server instances in the BlackBerry Enterprise Server pair include, by default, the BlackBerry Attachment
Service, BlackBerry Dispatcher, BlackBerry MDS Connection Service, BlackBerry Messaging Agent, BlackBerry Policy Service,
BlackBerry Router, and BlackBerry Synchronization Service. By default, if you choose to install the BlackBerry Collaboration
Service with both instances, the BlackBerry Collaboration Service is included in the BlackBerry Enterprise Server pair.
To administer the BlackBerry Enterprise Server pair, you can install the BlackBerry Administration Service with both BlackBerry
Enterprise Server instances and configure high availability for the BlackBerry Administration Service separately.
In a large-scale environment, you can add any number of BlackBerry Enterprise Server pairs that use the same BlackBerry
Configuration Database.
6
Planning Guide How the BlackBerry Enterprise Server calculates health scores
7
Planning Guide How the BlackBerry Enterprise Server calculates health scores
The standby BlackBerry Dispatcher tests the SRP connection when it starts running
and once every hour. If the standby BlackBerry Dispatcher receives a request using
an RPC command for the health score, the standby BlackBerry Dispatcher can test
the SRP connection at most once every 5 minutes. During the automatic failover
process, the standby BlackBerry Dispatcher tests the SRP connection. The standby
BlackBerry Dispatcher must open an SRP connection before the standby BlackBerry
Enterprise Server can become the primary instance.
8
Planning Guide How the BlackBerry Enterprise Server calculates health scores
The BlackBerry Messaging Agent sets this health parameter if it can connect to all
messaging servers. If the BlackBerry Messaging Agent cannot connect to a
messaging server, the BlackBerry Messaging Agent clears the parameter value and
sends the number of unavailable messaging servers to the BlackBerry Dispatcher.
The BlackBerry Messaging Agent tests the connection to a messaging server every
minute if the BlackBerry Messaging Agent is not making other calls to the
messaging server.
9
Planning Guide How the BlackBerry Enterprise Server calculates health scores
The BlackBerry Messaging Agent sets this parameter if the BlackBerry Attachment
Service can load the extension DLL and the BlackBerry Attachment Service reports
that it is healthy. The BlackBerry Attachment Service reports that it is healthy by
processing attachment viewing requests or when it is requested to report its health
through the GetHealthScore function. The BlackBerry Messaging Agent calls the
GetHealthScore function every minute if the BlackBerry Attachment Service is not
processing attachments actively.
Organizer data synchronization This parameter indicates that the PIM connector, which is a subcomponent of the
BlackBerry Messaging Agent, is healthy.
The BlackBerry Messaging Agent sets this health parameter if it can deliver requests
for organizer data synchronization. If the BlackBerry Messaging Agent is not
synchronizing organizer data actively, the BlackBerry Messaging Agent tests the
health of the PIM connector every 10 minutes by sending a configuration request
to the user account that is the least busy of all the user accounts.
10
Planning Guide How the BlackBerry Enterprise Server calculates health scores
How the BlackBerry Messaging Agent determines that a user account is healthy:
If your organization's environment includes the BlackBerry® Enterprise Server for Microsoft® Exchange, the BlackBerry Messaging
Agent determines that a user account is healthy if the BlackBerry Messaging Agent can log in to the user account's mailbox and
create and start a UserControl object. The BlackBerry Messaging Agent might restart a user account if you change the account
information, MAPI failures occur, or the connection to the Microsoft® Exchange server fails.
If your organization's environment includes the BlackBerry® Enterprise Server for IBM® Lotus® Domino®, the BlackBerry
Messaging Agent determines that a user account is healthy if the user account initializes or if the user account fails to initialize
because the user account no longer exists in the IBM® Lotus® Domino® directory. If the user account initializes, the BlackBerry
Messaging Agent also determines that a user account is healthy if it can connect to the messaging server that hosts the user
account and if the user's mail file is healthy.
The BlackBerry Messaging Agent tests the health of the user's mail file using the following methods:
• If the IBM® Lotus® Domino® version on the computers that host the BlackBerry® Enterprise Server and the messaging
server is version 6.5.6, 7.0.2, or higher, and you did not turn off the NSFDbModifiedTimeByName function using the
DontUseModifiedByName registry setting of the BlackBerry Messaging Agent, the BlackBerry Messaging Agent calls the
NSFDbModifiedTimeByName API function every minute.
• If the IBM Lotus Domino versions on the computers that host the BlackBerry Enterprise Server and messaging server do not
support the NSFDbModifiedTimeByName function, or you turned off the NSFDbModifiedTimeByName function, the
BlackBerry Messaging Agent determines automatically that the user account's mail file is healthy.
Health parameters that the BlackBerry Collaboration Service, BlackBerry MDS Connection Service,
BlackBerry Policy Service, and BlackBerry Synchronization Service calculate
The BlackBerry® Collaboration Service, BlackBerry MDS Connection Service, BlackBerry Policy Service, and BlackBerry
Synchronization Service calculate the following health parameters and communicate the values to the BlackBerry Dispatcher.
11
Planning Guide
12
Planning Guide Conditions for failover to a standby BlackBerry Enterprise Server
13
Planning Guide Scenario: What happens after the health score of a primary BlackBerry Enterprise Server falls below the failover threshold
4. The standby BlackBerry Enterprise Server tries to open an SRP connection to the BlackBerry Infrastructure.
5. When the connection to the BlackBerry Infrastructure is stable, the standby BlackBerry Enterprise Server writes its identity
as the primary BlackBerry Enterprise Server to the BlackBerry Configuration Database.
Response of the standby BlackBerry Enterprise Server when its health score is below the promotion threshold
1. The standby BlackBerry Enterprise Server determines that the primary BlackBerry Enterprise Server stopped responding.
2. The standby BlackBerry Enterprise Server checks its health score and determines that the health score is below the promotion
threshold.
The standby BlackBerry Enterprise Server cannot become the primary instance. You must resolve any issues before the
BlackBerry Enterprise Server can recover.
1. The standby BlackBerry® Enterprise Server determines that the health score of the primary BlackBerry Enterprise Server
fell below the failover threshold.
2. The standby BlackBerry Enterprise Server checks its health score and determines that its health score is above the promotion
threshold and higher than the health score of the primary BlackBerry Enterprise Server.
3. The standby BlackBerry Enterprise Server sends a demotion request to the pimary BlackBerry Enterprise Server.
4. The primary BlackBerry Enterprise Server demotes itself.
5. The standby BlackBerry Enterprise Server opens active connections to the BlackBerry Configuration Database and
messaging server.
6. The standby BlackBerry Enterprise Server tries to open an SRP connection to the BlackBerry Infrastructure.
7. The standby BlackBerry Enterprise Server writes its identity as the primary BlackBerry Enterprise Server to the BlackBerry
Configuration Database.
14
Planning Guide Scenario: What happens after a standby BlackBerry Enterprise Server loses its connection to the primary BlackBerry Enterprise Server and the
BlackBerry Configuration Database
The following responses assume that the messaging server, BlackBerry® Infrastructure, BlackBerry Configuration Database and
standby BlackBerry Enterprise Server are available but that the BlackBerry Controller cannot restart the BlackBerry Enterprise
Server component.
Response of the primary BlackBerry Enterprise Server when the health of the nonresponsive component affects the
failover threshold
1. During a periodic health check, the primary BlackBerry Controller detects the nonresponsive BlackBerry Enterprise Server
component.
2. The BlackBerry Controller tries to restart the nonresponsive component but is not successful.
3. The BlackBerry Dispatcher lowers the health score of the BlackBerry Enterprise Server. The health score falls below the
failover threshold.
4. The standby BlackBerry Enterprise Server demotes the primary BlackBerry Enterprise Server.
5. The standby BlackBerry Enterprise Server tries to promote itself to become the primary instance.
6. When the connections to the BlackBerry Infrastructure and messaging server are open, the standby BlackBerry Enterprise
Server writes its identity as the primary BlackBerry Enterprise Server to the BlackBerry Configuration Database.
Response of the primary BlackBerry Enterprise Server when the health of the nonresponsive component does not affect
the failover threshold
1. During a periodic health check, the primary BlackBerry Controller detects the nonresponsive BlackBerry Enterprise Server
component.
2. The BlackBerry Controller tries to restart the nonresponsive component but is not successful.
3. The BlackBerry Dispatcher lowers the health score of the primary BlackBerry Enterprise Server.
The health score does not fall below the failover threshold, and the primary BlackBerry Enterprise Server continues running.
You must resolve any issues before the BlackBerry Enterprise Server component can recover.
1. The standby BlackBerry® Enterprise Server tries to open a connection to the BlackBerry® Infrastructure.
2. The BlackBerry Infrastructure pings the primary BlackBerry Enterprise Server to determine whether it is available.
One of the following events occurs:
• If the primary BlackBerry Enterprise Server does not respond, the BlackBerry Infrastructure opens the connection to
the standby BlackBerry Enterprise Server. The standby BlackBerry Enterprise Server assumes that it should become
the primary BlackBerry Enterprise Server and promotes itself.
15
Planning Guide Scenario: What happens after a standby BlackBerry Enterprise Server loses its connection to the primary BlackBerry Enterprise Server and the
BlackBerry Configuration Database
• If the primary BlackBerry Enterprise Server does respond, the BlackBerry Infrastructure does not open the connection
to the standby BlackBerry Enterprise Server. The standby BlackBerry Enterprise Server continues to try to open the
connection to the BlackBerry Infrastructure until the connection opens or until the connection to the BlackBerry
Configuration Database reopens.
16
Planning Guide High availability in a distributed environment
17
Planning Guide High availability in a distributed environment
18
Planning Guide High availability in a distributed environment
19
Planning Guide BlackBerry Administration Service high availability
20
Planning Guide Best practice: Planning for BlackBerry Administration Service high availability
21
Planning Guide Scenario: What happens after the BlackBerry Administration Service stops responding
1. The BlackBerry Administration Service instance does not respond to requests from the BlackBerry Enterprise Server
component.
2. The BlackBerry Enterprise Server component tries to connect to another BlackBerry Administration Service instance.
One of the following events occur:
• If the BlackBerry Enterprise Server component can connect to another BlackBerry Administration Service instance,
the BlackBerry Enterprise Server component sends subsequent requests to that BlackBerry Administration Service
instance.
22
Planning Guide Scenario: What happens after the BlackBerry Administration Service stops responding
• If the BlackBerry Enterprise Server component cannot connect to another BlackBerry Administration Service instance,
you must resolve the issue.
Response of the browser when the BlackBerry Administration Service instance that it is connected to stops responding
The following scenario is specific to the browser that an administrator is using. It assumes that the administrator is logged in to
the BlackBerry Administration Service instance that stopped responding.
1. The BlackBerry Administration Service does not respond to requests from the browser.
2. The browser loses the open web session.
3. The browser uses the BlackBerry Administration Service pool name to request a list of IP addresses from the DNS server.
4. The DNS server returns the list of IP addresses.
5. The browser tries to connect to one of the IP addresses on the list.
One of the following events occurs:
• If the browser cannot connect to a BlackBerry Administration Service instance that is running, the browser displays a
"The page cannot be displayed" error.
• If the browser can connect to a BlackBerry Administration Service instance that is running, the BlackBerry
Administration Service instance prompts the administrator for login information.
If you cannot resolve the issue, you should delete the nonresponsive instance from the DNS record for best performance.
23
Planning Guide BlackBerry Attachment Service high availability
24
Planning Guide BlackBerry Attachment Service high availability in a large-scale environment
25
Planning Guide Best practice: Planning for BlackBerry Attachment Service high availability
The primary BlackBerry Enterprise Server sends conversion requests only to the
BlackBerry Attachment Service instance that you install with the primary BlackBerry
Enterprise Server.
If the BlackBerry Attachment Service instance that you installed with the primary
BlackBerry Enterprise Server stops responding, the primary BlackBerry Enterprise
Server can use the BlackBerry Attachment Service instance that you installed with
the standby BlackBerry Enterprise Server.
Install BlackBerry Attachment Service If you install the BlackBerry Attachment Service instances with the primary and
instances with the BlackBerry Enterprise standby BlackBerry Enterprise Server instances, you can create a pool that includes
Server pair and configure a BlackBerry both BlackBerry Attachment Service instances. You can configure both BlackBerry
Attachment Service pool with a primary Attachment Service instances to be part of the primary group.
group only.
The primary BlackBerry Enterprise Server sends conversion requests to both
BlackBerry Attachment Service instances.
If one of the BlackBerry Attachment Service instances stops responding, the primary
BlackBerry Enterprise Server can continue to send requests to the other BlackBerry
Attachment Service instance.
Install the BlackBerry Attachment If you install multiple BlackBerry Attachment Service instances on different
Service instances with the BlackBerry computers, you can configure one or more BlackBerry Attachment Service and
Enterprise Server pair or on different configure primary and secondary groups for each pool. You can configure each
computers, and configure a BlackBerry BlackBerry Attachment Service pool to support multiple BlackBerry Enterprise
Attachment Service pool with primary Server pairs.
and secondary groups.
26
Planning Guide Scenario: What happens after the BlackBerry Attachment Service stops responding
27
Planning Guide BlackBerry Collaboration Service high availability
28
Planning Guide BlackBerry Collaboration Service high availability in a large-scale environment
29
Planning Guide Best practice: Planning for BlackBerry Collaboration Service high availability
If the BlackBerry Collaboration Service that you installed with the primary
BlackBerry Enterprise Server stops responding, the primary BlackBerry Enterprise
Server can fail over to the BlackBerry Collaboration Service instance that you
installed with the standby BlackBerry Enterprise Server.
Install the BlackBerry Collaboration If you install the BlackBerry Collaboration Service with the primary and standby
Service instances with the BlackBerry BlackBerry Enterprise Server instances, you can create a BlackBerry Collaboration
Enterprise Server pair and configure a Service pool that includes both instances. You can configure the primary BlackBerry
BlackBerry Collaboration Service pool Enterprise Server to assign an active connection to the BlackBerry Collaboration
that does not fail over automatically. Service that you installed with it, and a standby connection to the BlackBerry
Collaboration Service that you installed with the standby BlackBerry Enterprise
Server. You can choose not to configure automatic failover for the BlackBerry
Collaboration Service instances.
If the BlackBerry Collaboration Service that you installed with the primary
BlackBerry Enterprise Server stops responding, you must fail over the BlackBerry
Enterprise Server to the standby BlackBerry Collaboration Service manually.
Install multiple BlackBerry If you install multiple BlackBerry Collaboration Service instances, you can configure
Collaboration Service instances with the all the BlackBerry Collaboration Service instances to work in a pool. Each instance
BlackBerry Enterprise Server or on can support multiple primary BlackBerry Enterprise Server instances. You can
different computers and configure a configure automatic failover for the BlackBerry Collaboration Service instances and
BlackBerry Collaboration Service pool select which BlackBerry Collaboration Service is assigned the active connection for
that can automatically fail over each BlackBerry Enterprise Server.
30
Planning Guide Scenario: What happens after the BlackBerry Collaboration Service stops responding
31
Planning Guide Scenario: What happens after the primary BlackBerry Dispatcher promotes a connection to a BlackBerry Collaboration Service
1. The BlackBerry Dispatcher sends a request to a BlackBerry Collaboration Service with an acceptable health score to promote
its standby connection to an active conection.
2. The BlackBerry Collaboration Service with the acceptable health score promotes the connection to active.
3. The BlackBerry Dispatcher sends a request to the BlackBerry Collaboration Service instance with the low health score to
demote the active connection to a standby connection.
4. When the BlackBerry Collaboration Service with the low health score receives the request, it finishes processing the packets
that the BlackBerry Dispatcher sent to it previously.
5. The BlackBerry Collaboration Service with the low health score checks whether the standby BlackBerry Enterprise Server
was promoted to the primary instance. In this scenario, it has not.
6. The BlackBerry Collaboration Service with the low health score sends a message to all open BlackBerry Collaboration Service
sessions to log out.
7. The BlackBerry Collaboration Service with the active connection sends a message to all open sessions with collaboration
clients to log in.
One of the following events occurs:
• If password caching is turned off, users must log in to the collaboration client manually. The session connects to the
BlackBerry Collaboration Service with the active connection.
• If password caching is turned on, users are logged in automatically. The sessions connect to the BlackBerry
Collaboration Service with the active connection.
32
Planning Guide BlackBerry Configuration Database high availability
33
Planning Guide Scenario: What happens after the principal BlackBerry Configuration Database stops responding
The primary BlackBerry Enterprise Server connects to the principal BlackBerry Configuration Database and accesses data from
it. The name of the mirror BlackBerry Configuration Database is stored in the Windows® registry of the computers that hosts the
primary and standby BlackBerry Enterprise Server instances. The BlackBerry Enterprise Server instances do not connect to the
mirror BlackBerry Configuration Database until after the principal BlackBerry Configuration Database stops responding.
The primary BlackBerry Enterprise Server connects to the messaging server and processes the messaging data that it sends to
and receives from BlackBerry devices.
The standby BlackBerry Enterprise Server opens standby connections to the principal BlackBerry Configuration Database and
the messaging server.
34
Planning Guide Scenario: What happens after the BlackBerry Configuration Database and BlackBerry Infrastructure stop responding
35
Planning Guide BlackBerry MDS Connection Service high availability
High availability for the BlackBerry MDS Connection Service central push
server
To configure high availability for BlackBerry® MDS Connection Service central push servers, you must configure at least two
BlackBerry MDS Connection Service instances in the pool to be central push servers so that failover can occur. A BlackBerry MDS
Connection Service that also is a central push server receives content push requests from server-side applications that are located
on an application server or a web server.
To make sure that the central push server can access user information, the central push server caches the user information from
all of the BlackBerry® Enterprise Server instances that the BlackBerry MDS Connection Service pool connects to. When a central
push server receives content from push applications, it routes the data to the BlackBerry MDS Connection Service with the active
connection to the BlackBerry Enterprise Server that the user account is assigned to.
36
Planning Guide BlackBerry MDS Connection Service high availability in a large-scale environment
37
Planning Guide Best practice: Planning for BlackBerry MDS Connection Service high availability
If the BlackBerry MDS Connection Service that you installed with the primary
BlackBerry Enterprise Server stops responding, the primary BlackBerry Enterprise
Server can fail over to the BlackBerry MDS Connection Service instance that you
installed with the standby BlackBerry Enterprise Server.
38
Planning Guide Scenario: What happens after the BlackBerry MDS Connection Service stops responding
If the BlackBerry MDS Connection Service that you installed with the primary
BlackBerry Enterprise Server stops responding, the primary BlackBerry Enterprise
Server and the BlackBerry MDS Connection Service fail over to the standby
BlackBerry Enterprise Server and BlackBerry MDS Connection Service.
Install multiple BlackBerry MDS If you install multiple BlackBerry MDS Connection Service instances, you can
Connection Service instances with the configure a BlackBerry MDS Connection Service pool. Each BlackBerry MDS
BlackBerry Enterprise Server or on Connection Service instance can support multiple primary BlackBerry Enterprise
different computers and configure a Server instances. You can configure automatic failover for the BlackBerry MDS
BlackBerry MDS Connection Service Connection Service instances and select which BlackBerry MDS Connection Service
pool that can automatically failover. has the active connection to each primary BlackBerry Enterprise Server.
If the BlackBerry MDS Connection Service with the active connection stops
responding, the BlackBerry Enterprise Server can fail over to a different BlackBerry
MDS Connection Service instance.
Scenario: What happens after the BlackBerry MDS Connection Service stops
responding
If the BlackBerry® MDS Connection Service with the active connection to the primary BlackBerry® Enterprise Server stops
responding, the response of the primary BlackBerry® Enterprise Server is based on whether it can promote a different BlackBerry
MDS Connection Service.
These responses assume that the health score for the BlackBerry MDS Connection Service is above the failover threshold.
If you choose to install BlackBerry MDS Connection Service instances with the BlackBerry Enterprise Server pair, and either the
primary BlackBerry Enterprise Server or the BlackBerry MDS Connection Service stops responding, all of the BlackBerry Enterprise
Server components fail over to the standby BlackBerry Enterprise Server and BlackBerry MDS Connection Service.
Response of a primary BlackBerry Enterprise Server when it can promote a different BlackBerry MDS Connection Service
1. The primary BlackBerry Enterprise Server loses its active connection to the BlackBerry MDS Connection Service.
39
Planning Guide Scenario: What happens after the BlackBerry MDS Connection Service central push server stops responding
2. If users are browsing, the session information is lost. If the web site that the users browsed to required authentication, and
the BlackBerry devices cached the password and cookies, users are not affected.
3. If the primary BlackBerry Enterprise Server is connected to other BlackBerry MDS Connection Service instances, the
BlackBerry Enterprise Server promotes the connection to one of the BlackBerry MDS Connection Service instances to active.
It determines which instance to promote by checking the health scores.
4. The primary BlackBerry Enterprise Server writes the new information to the BlackBerry Configuration Database.
You must resolve any issues before the nonresponsive BlackBerry MDS Connection Service instance can recover.
Response of a primary BlackBerry Enterprise Server when it cannot promote a different BlackBerry MDS Connection
Service
1. The primary BlackBerry Enterprise Server loses its active connection to the BlackBerry MDS Connection Service.
2. If users are browsing, the session information is lost. If the web site that the users browsed to required authentication, and
BlackBerry devices cached the password and cookies, users are not affected.
3. If the primary BlackBerry Enterprise Server is connected to other BlackBerry MDS Connection Service instances, the
BlackBerry Enterprise Server tries to promote the connection to one of the BlackBerry MDS Connection Service instances
to active. It determines which instance to promote by checking the health scores.
The primary BlackBerry Enterprise Server cannot promote any BlackBerry MDS Connection Service.
4. The primary BlackBerry Enterprise Server lowers its health score.
The health score of the primary BlackBerry Enterprise Server falls below the failover threshold.
5. The standby BlackBerry Enterprise Server checks its health score to determine if it is above the promotion threshold.
6. If the health score of the standby BlackBerry Enterprise Server is above the promotion threshold, it tries to promote the
connection to one of the BlackBerry MDS Connection Service instances from a standby connection to an active connection.
One of the following events occur:
• If the standby BlackBerry Enterprise Server can promote the connection to an active connection, it demotes the primary
BlackBerry Enterprise Server and promotes itself to become the primary instance.
• If the standby BlackBerry Enterprise Server cannot promote the connection to an active connection, it cannot become
the primary instance. You must resolve any issues before the BlackBerry Enterprise Server pair can recover.
40
Planning Guide Scenario: What happens after the primary BlackBerry Dispatcher promotes a connection to a BlackBerry MDS Connection Service
1. The BlackBerry Dispatcher sends a request to a BlackBerry MDS Connection Service with an acceptable health score to
promote its standby connection to an active connection.
2. The BlackBerry MDS Connection Service with the acceptable health score promotes the connection to active.
3. The BlackBerry Dispatcher sends a request to the BlackBerry MDS Connection Service with the low health score to demote
the active connection to a standby connection.
4. When the BlackBerry MDS Connection Service with the low health score receives the request, it finishes processing the
packets that the BlackBerry Dispatcher sent to it previously.
5. The BlackBerry MDS Connection Service with the low health score checks whether the standby BlackBerry Enterprise Server
was promoted to the primary instance. In this scenario, it has not.
6. The BlackBerry MDS Connection Service with the low health score opens all IPPP sessions and sends error messages to
open sessions.
7. The BlackBerry MDS Connection Service with a low health score sends a message to all open sessions to log out.
8. The BlackBerry MDS Connection Service with the active connection sends a message to all open sessions to log in.
41
Planning Guide BlackBerry MDS Integration Service high availability
BlackBerry MDS Integration Service high availability using DNS round robin
To configure BlackBerry® MDS Integration Service high availability, you can configure multiple BlackBerry MDS Integration
Service instances in a pool that use the same DNS name. You can provision the DNS name in a DNS server for each IP address
that the BlackBerry MDS Integration Service instances use.
All BlackBerry MDS Integration Service clients that connect to the BlackBerry MDS Integration Service pool must resolve the
DNS name into the list of IP addresses, and try to connect to each BlackBerry MDS Integration Service instance using DNS round
robin until the clients can connect to an BlackBerry MDS Integration Service instance. Clients must distribute initial messages
42
Planning Guide BlackBerry MDS Integration Service high availability using a hardware load balancer
equally across all BlackBerry MDS Integration Service instances in the pool. To enhance performance of the BlackBerry MDS
Integration Service, clients can monitor the connections to the BlackBerry MDS Integration Service instances in the pool and
maintain a list of available and unavailable BlackBerry MDS Integration Service instances.
If the client is a Java® application, you must turn off DNS caching at the JVM level. For more information, see the BlackBerry
Enterprise Server Administration Guide.
The following diagram shows an BlackBerry MDS Integration Service pool that includes three BlackBerry MDS Integration Service
instances that you configured for DNS round robin.
43
Planning Guide Best practice: Planning for BlackBerry MDS Integration Service high availability
44
Planning Guide Scenario: What happens after a BlackBerry MDS Integration Service instance stops responding
For more information about upgrading a BlackBerry MDS Integration Service instance and configuring BlackBerry MDS
Integration Service high availability, see the BlackBerry Enterprise Server Upgrade Guide.
1. The BlackBerry MDS Integration Service client or hardware load balancer loses its connection to the BlackBerry MDS
Integration Service instance.
2. The BlackBerry MDS Integration Service client or hardware load balancer redirects incoming traffic to the other BlackBerry
MDS Integration Service instances in the pool.
Response of the other BlackBerry MDS Integration Service instances
1. The BlackBerry MDS Integration Service instances detect that a BlackBerry MDS Integration Service instance stopped
responding.
2. The BlackBerry MDS Integration Service instances assign the BlackBerry device sessions that the nonresponsive BlackBerry
MDS Integration Service instance open to themselves.
45
Planning Guide How a BlackBerry MDS Integration Service pool maintains sessions with BlackBerry devices
1. The BlackBerry MDS Integration Service client loses its connection to a BlackBerry MDS Integration Service instance.
2. The BlackBerry MDS Integration Service client excludes the IP address of the nonresponsive BlackBerry MDS Integration
Service instances from the list of IP addresses of the BlackBerry MDS Integration Service pool temporarily.
3. The BlackBerry MDS Integration Service client tries to connect to the next IP address in the list of BlackBerry MDS Integration
Service instances in the BlackBerry MDS Integration Service pool.
4. If the BlackBerry MDS Integration Service client is a BlackBerry MDS Connection Service instance, the BlackBerry MDS
Connection Service instance determines that the BlackBerry MDS Integration Service instance is not healthy and sends the
health score to the BlackBerry Dispatcher. You can check the health status of the BlackBerry MDS Integration Service pool
by viewing the health parameters in the BlackBerry Administration Service.
How the hardware load balancer redirects client traffic when you configure a hardware load balancer
1. The hardware load balancer detects that a BlackBerry MDS Integration Service instance stopped responding.
2. The hardware load balancer removes the BlackBerry MDS Integration Service instance from the pool automatically.
3. The hardware load balancer redirects the BlackBerry MDS Integration Service client requests to another BlackBerry MDS
Integration Service instance in the pool automatically.
When you configure a hardware load balancer, the health parameter for the nonresponsive BlackBerry MDS Integration Service
instance does not change to indicate the health status of the BlackBerry MDS Integration Service pool. You can detect that a
BlackBerry MDS Integration Service instance is not responding when you try to manage the BlackBerry MDS Integration Service
instance using the BlackBerry Administration Service and the BlackBerry Administration Service cannot make the changes.
46
Planning Guide BlackBerry Router high availability
47
Planning Guide Best practice: Planning for BlackBerry Router high availability
48
Planning Guide Scenario: What happens after the BlackBerry Router stops responding
The primary BlackBerry Enterprise Server can connect to any of the BlackBerry
Router instances. If a BlackBerry Router instance stops responding, the primary
BlackBerry Enterprise Server connects to another BlackBerry Router in the pool.
You can create a BlackBerry Router pool in the DMZ. If you create a BlackBerry
Router pool in the DMZ, and you want to install the BlackBerry Router in the
protected network, you can create another BlackBerry Router pool in the protected
network.
If you want to create a BlackBerry Router pool on computers that do not host the
BlackBerry Enterprise Server pair, turn off the BlackBerry Router instances that you
installed with the BlackBerry Enterprise Server pair.
49
Planning Guide Scenario: What happens after the BlackBerry Router stops responding
50
Planning Guide Configuring disaster recovery for the BlackBerry Enterprise Server across data centers
In this scenario, you connect the primary BlackBerry Enterprise Server in Data center one to the standby BlackBerry Enterprise
Server in Data center two to create a BlackBerry Enterprise Server pair. Similarily, you connect the primary BlackBerry Enterprise
Server in Data center two to the standby BlackBerry Enterprise Server in Data center one to create a BlackBerry Enterprise Server
pair.
51
Planning Guide Using BlackBerry Enterprise Server components that you installed with a standby BlackBerry Enterprise Server in the same data center
You can connect all of the BlackBerry Enterprise Server instances to the BlackBerry Configuration Database in Data center one.
You can also connect all BlackBerry Enterprise Server instances in one data center to the messaging server that is located in the
same data center. If the BlackBerry Configuration Database stops responding, the BlackBerry Enterprise Server instances can
connect to the mirror BlackBerry Configuration Database.
52
Planning Guide Using BlackBerry Enterprise Server components that you installed with a standby BlackBerry Enterprise Server in the same data center
In this scenario, you can configure the primary BlackBerry Enterprise Server in Data center one to use the BlackBerry
Administration Service, BlackBerry Attachment Service, BlackBerry MDS Connection Service and BlackBerry Router instances
that you installed with the standby BlackBerry Enterprise Server in Data center one.
If a failover event occurs, the primary BlackBerry Enterprise Server in Data center one can fail over to the standby BlackBerry
Enterprise Server in Data center two.
53
Planning Guide Creating pools of BlackBerry Enterprise Server components that are located in different data centers
54
Planning Guide Glossary
Glossary 12
API
application programming interface
BlackBerry MDS
BlackBerry® Mobile Data System
DMZ
A demilitarized zone (DMZ) is a neutral subnetwork outside of an organization's firewall. It exists between the trusted LAN
of the organization and the untrusted external wireless network and public Internet.
DNS
A Domain Name System (DNS) is an Internet database that translates domain names that are meaningful and recognizable
by people into the numeric IP addresses that the Internet uses.
failover pair
A failover pair consists of two BlackBerry® Enterprise Server instances that are set up together in a failover environment.
One instance is the active BlackBerry Enterprise Server and the other instance is the standby BlackBerry Enterprise Server.
FQDN
fully qualified domain name
HTTP
Hypertext Transfer Protocol
IP address
An Internet Protocol (IP) address is an identification number that each computer or mobile device uses when it sends or
receives information over a network, such as the Internet. This identification number identifies the specific computer or
mobile device on the network.
IPPP
Internet Protocol Proxy Protocol
JVM
Java® Virtual Machine
MAPI
Messaging Application Programming Interface
mirror database
In database mirroring, a mirror database is a standby copy of a principal database.
55
Planning Guide Glossary
PIM
personal information management
principal database
In database mirroring, a principal database is the database that starts the mirroring session.
RPC
remote procedure call
SRP
Server Routing Protocol
witness
In database mirroring, a witness is an optional Microsoft® SQL Server® instance that permits the mirror database to know
when to promote itself.
56
Planning Guide Provide feedback
Provide feedback 13
To provide feedback on this deliverable, visit www.blackberry.com/docsfeedback.
57
Planning Guide Legal notice
Legal notice 14
©2009 Research In Motion Limited. All rights reserved. BlackBerry®, RIM®, Research In Motion®, SureType®, SurePress™ and
related trademarks, names, and logos are the property of Research In Motion Limited and are registered and/or used in the U.S.
and countries around the world.
BIG-IP is a trademark of F5 Networks, Inc. IBM, Domino, and Lotus are trademarks of International Business Machines Corporation.
Microsoft, SQL Server, and Windows are trademarks of Microsoft Corporation. Java is a trademark of Sun Microsystems, Inc. Wi-
Fi is a trademark of the Wi-Fi Alliance. All other trademarks are the property of their respective owners.
The BlackBerry smartphone and other devices and/or associated software are protected by copyright, international treaties, and
various patents, including one or more of the following U.S. patents: 6,278,442; 6,271,605; 6,219,694; 6,075,470; 6,073,318;
D445,428; D433,460; D416,256. Other patents are registered or pending in the U.S. and in various countries around the world.
Visit www.rim.com/patents for a list of RIM (as hereinafter defined) patents.
This documentation including all documentation incorporated by reference herein such as documentation provided or made
available at www.blackberry.com/go/docs is provided or made accessible "AS IS" and "AS AVAILABLE" and without condition,
endorsement, guarantee, representation, or warranty of any kind by Research In Motion Limited and its affiliated companies
("RIM") and RIM assumes no responsibility for any typographical, technical, or other inaccuracies, errors, or omissions in this
documentation. In order to protect RIM proprietary and confidential information and/or trade secrets, this documentation may
describe some aspects of RIM technology in generalized terms. RIM reserves the right to periodically change information that
is contained in this documentation; however, RIM makes no commitment to provide any such changes, updates, enhancements,
or other additions to this documentation to you in a timely manner or at all.
This documentation might contain references to third-party sources of information, hardware or software, products or services
including components and content such as content protected by copyright and/or third-party web sites (collectively the "Third
Party Products and Services"). RIM does not control, and is not responsible for, any Third Party Products and Services including,
without limitation the content, accuracy, copyright compliance, compatibility, performance, trustworthiness, legality, decency,
links, or any other aspect of Third Party Products and Services. The inclusion of a reference to Third Party Products and Services
in this documentation does not imply endorsement by RIM of the Third Party Products and Services or the third party in any way.
EXCEPT TO THE EXTENT SPECIFICALLY PROHIBITED BY APPLICABLE LAW IN YOUR JURISDICTION, ALL CONDITIONS,
ENDORSEMENTS, GUARANTEES, REPRESENTATIONS, OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING
WITHOUT LIMITATION, ANY CONDITIONS, ENDORSEMENTS, GUARANTEES, REPRESENTATIONS OR WARRANTIES OF
DURABILITY, FITNESS FOR A PARTICULAR PURPOSE OR USE, MERCHANTABILITY, MERCHANTABLE QUALITY, NON-
INFRINGEMENT, SATISFACTORY QUALITY, OR TITLE, OR ARISING FROM A STATUTE OR CUSTOM OR A COURSE OF DEALING
OR USAGE OF TRADE, OR RELATED TO THE DOCUMENTATION OR ITS USE, OR PERFORMANCE OR NON-PERFORMANCE
OF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES REFERENCED HEREIN, ARE
HEREBY EXCLUDED. YOU MAY ALSO HAVE OTHER RIGHTS THAT VARY BY STATE OR PROVINCE. SOME JURISDICTIONS
MAY NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES AND CONDITIONS. TO THE EXTENT
PERMITTED BY LAW, ANY IMPLIED WARRANTIES OR CONDITIONS RELATING TO THE DOCUMENTATION TO THE EXTENT
THEY CANNOT BE EXCLUDED AS SET OUT ABOVE, BUT CAN BE LIMITED, ARE HEREBY LIMITED TO NINETY (90) DAYS FROM
THE DATE YOU FIRST ACQUIRED THE DOCUMENTATION OR THE ITEM THAT IS THE SUBJECT OF THE CLAIM.
58
Planning Guide Legal notice
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, IN NO EVENT SHALL RIM BE LIABLE
FOR ANY TYPE OF DAMAGES RELATED TO THIS DOCUMENTATION OR ITS USE, OR PERFORMANCE OR NON-
PERFORMANCE OF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES REFERENCED
HEREIN INCLUDING WITHOUT LIMITATION ANY OF THE FOLLOWING DAMAGES: DIRECT, CONSEQUENTIAL, EXEMPLARY,
INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE, OR AGGRAVATED DAMAGES, DAMAGES FOR LOSS OF PROFITS OR REVENUES,
FAILURE TO REALIZE ANY EXPECTED SAVINGS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, LOSS OF
BUSINESS OPPORTUNITY, OR CORRUPTION OR LOSS OF DATA, FAILURES TO TRANSMIT OR RECEIVE ANY DATA, PROBLEMS
ASSOCIATED WITH ANY APPLICATIONS USED IN CONJUNCTION WITH RIM PRODUCTS OR SERVICES, DOWNTIME COSTS,
LOSS OF THE USE OF RIM PRODUCTS OR SERVICES OR ANY PORTION THEREOF OR OF ANY AIRTIME SERVICES, COST OF
SUBSTITUTE GOODS, COSTS OF COVER, FACILITIES OR SERVICES, COST OF CAPITAL, OR OTHER SIMILAR PECUNIARY
LOSSES, WHETHER OR NOT SUCH DAMAGES WERE FORESEEN OR UNFORESEEN, AND EVEN IF RIM HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, RIM SHALL HAVE NO OTHER
OBLIGATION, DUTY, OR LIABILITY WHATSOEVER IN CONTRACT, TORT, OR OTHERWISE TO YOU INCLUDING ANY LIABILITY
FOR NEGLIGENCE OR STRICT LIABILITY.
THE LIMITATIONS, EXCLUSIONS, AND DISCLAIMERS HEREIN SHALL APPLY: (A) IRRESPECTIVE OF THE NATURE OF THE
CAUSE OF ACTION, DEMAND, OR ACTION BY YOU INCLUDING BUT NOT LIMITED TO BREACH OF CONTRACT, NEGLIGENCE,
TORT, STRICT LIABILITY OR ANY OTHER LEGAL THEORY AND SHALL SURVIVE A FUNDAMENTAL BREACH OR BREACHES
OR THE FAILURE OF THE ESSENTIAL PURPOSE OF THIS AGREEMENT OR OF ANY REMEDY CONTAINED HEREIN; AND (B)
TO RIM AND ITS AFFILIATED COMPANIES, THEIR SUCCESSORS, ASSIGNS, AGENTS, SUPPLIERS (INCLUDING AIRTIME
SERVICE PROVIDERS), AUTHORIZED RIM DISTRIBUTORS (ALSO INCLUDING AIRTIME SERVICE PROVIDERS) AND THEIR
RESPECTIVE DIRECTORS, EMPLOYEES, AND INDEPENDENT CONTRACTORS.
IN ADDITION TO THE LIMITATIONS AND EXCLUSIONS SET OUT ABOVE, IN NO EVENT SHALL ANY DIRECTOR, EMPLOYEE,
AGENT, DISTRIBUTOR, SUPPLIER, INDEPENDENT CONTRACTOR OF RIM OR ANY AFFILIATES OF RIM HAVE ANY LIABILITY
ARISING FROM OR RELATED TO THE DOCUMENTATION.
Prior to subscribing for, installing, or using any Third Party Products and Services, it is your responsibility to ensure that your
airtime service provider has agreed to support all of their features. Some airtime service providers might not offer Internet browsing
functionality with a subscription to the BlackBerry® Internet Service. Check with your service provider for availability, roaming
arrangements, service plans and features. Installation or use of Third Party Products and Services with RIM's products and services
may require one or more patent, trademark, copyright, or other licenses in order to avoid infringement or violation of third party
rights. You are solely responsible for determining whether to use Third Party Products and Services and if any third party licenses
are required to do so. If required you are responsible for acquiring them. You should not install or use Third Party Products and
Services until all necessary licenses have been acquired. Any Third Party Products and Services that are provided with RIM's
products and services are provided as a convenience to you and are provided "AS IS" with no express or implied conditions,
endorsements, guarantees, representations, or warranties of any kind by RIM and RIM assumes no liability whatsoever, in relation
thereto. Your use of Third Party Products and Services shall be governed by and subject to you agreeing to the terms of separate
licenses and other agreements applicable thereto with third parties, except to the extent expressly covered by a license or other
agreement with RIM.
Certain features outlined in this documentation require a minimum version of BlackBerry® Enterprise Server, BlackBerry® Desktop
Software, and/or BlackBerry® Device Software.
59
Planning Guide Legal notice
The terms of use of any RIM product or service are set out in a separate license or other agreement with RIM applicable thereto.
NOTHING IN THIS DOCUMENTATION IS INTENDED TO SUPERSEDE ANY EXPRESS WRITTEN AGREEMENTS OR WARRANTIES
PROVIDED BY RIM FOR PORTIONS OF ANY RIM PRODUCT OR SERVICE OTHER THAN THIS DOCUMENTATION.
Certain features outlined in this documentation might require additional development or Third Party Products and Services for
access to corporate applications.
This product contains a modified version of HTML Tidy. Copyright © 1998-2003 World Wide Web Consortium (Massachusetts
Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University). All Rights Reserved.
This product includes software developed by the Apache Software Foundation (www.apache.org/) and/or is licensed pursuant
to one of the licenses listed at (www.apache.org/licenses/). For more information, see the NOTICE.txt file included with the
software.
Published in Canada
60