Quote:
Originally Posted by knottyrope How many users are you making this for? |
Initially only a couple hundred users, but potentially 3,000.
The main goal though is complete HA and site resilience.
Downtime needs to be minimized as long as even 1 of the 4 BES servers are online.
Currently my setup is as follows:
Primary Data Center: pdcbes1, pdcbes2
Standby Data Center: sdcbes1, sdcbes2
I have made the following pairs according to the white paper guidance:
Pair1: pdcbes1(P), sdcbes1(S)
Pair2: sdcbes2(S), pdcbes2(P)
The configuration database lives on a MS SQL cluster in PDC with a mirror at the SDC.
By Component:
BlackBerry Admin Service: I have BAS installed on all 4 servers. Currently DNS points me URL directly to 1 server but plan on using a HLB for this.
BlackBerry Enterprise Server:
- Pair1
- Pair1_1 - on pdcbes1
Supported MDS Connection Service instances- pdcbes1_MDS on pdcbes1 as Primary
- pdcbes2_MDS on pdcbes2 as Standby
- Pair1_2 - on sdcbes1
Supported MDS Connection Service instances- sdcbes1_MDS on sdcbes1 as Primary
- sdcbes2_MDS on sdcbes2 as Standby
- Pair2
- Pair2_3 - on sdcbes2
Supported MDS Connection Service instances- sdcbes2_MDS on pdcbes1 as Primary
- sdcbes1_MDS on pdcbes2 as Standby
- Pair2_4 - on pdcbes2
Supported MDS Connection Service instances- pdcbes2_MDS on pdcbes2 as Primary
- pdcbes1_MDS on pdcbes1 as Standby
Attachment - Connector
- pdcbes1_AC_EMAIL on pdcbes01
Supported Attachment Server instances- pdcbes1_AS on pdcbes1 in Primary pool
- pdcbes2_AS on pdcbes2 in Primary pool
- sdcbes1_AS on sdcbes1 in Secondary pool
- sdcbes2_AS on sdcbes2 in Secondary pool
- pdcbes1_AC_MDS-CS on pdcbes1
Supported Attachment Server instances- pdcbes1_AS on pdcbes1 in Primary pool
- pdcbes2_AS on pdcbes2 in Primary pool
- sdcbes1_AS on sdcbes1 in Secondary pool
- sdcbes2_AS on sdcbes2 in Secondary pool
- pdcbes2_AC_EMAIL on pdcbes2
Supported Attachment Server instances- pdcbes2_AS on pdcbes2 in Primary pool
- pdcbes1_AS on pdcbes1 in Primary pool
- sdcbes1_AS on sdcbes1 in Secondary pool
- sdcbes2_AS on sdcbes2 in Secondary pool
- pdcbes2_AC_MDS-CS on pdcbes2
- pdcbes2_AS on pdcbes2 in Primary pool
- pdcbes1_AS on pdcbes1 in Primary pool
- sdcbes1_AS on sdcbes1 in Secondary pool
- sdcbes2_AS on sdcbes2 in Secondary pool
- sdcbes1_AC_EMAIL on sdcbes1
Supported Attachment Server instances- sdcbes1_AS on sdcbes1 in Primary pool
- sdcbes2_AS on sdcbes2 in Primary pool
- sdcbes1_AC_MDS-CS on sdcbes1
Supported Attachment Server instances- sdcbes1_AS on sdcbes1 in Primary pool
- sdcbes2_AS on sdcbes2 in Primary pool
- sdcbes2_AC_EMAIL on sdcbes2
Supported Attachment Server instances- sdcbes2_AS_ on sdcbes2 in Primary pool
- sdcbes1_AS_ on sdcbes1 in Primary pool
- sdcbes2_AC_MDS-CS on sdcbes2
Supported Attachment Server instances- sdcbes2_AS_ on sdcbes2 in Primary pool
- sdcbes1_AS_ on sdcbes1 in Primary pool
MDS Connection Service
- pdcbes1_MDS-CS on pdcbes1
Supported Dispatcher instances- Pair1 on pdcbes1 in Primary state
- Pair2 on pdcbes2 in Standby state
- pdcbes2_MDS-CS on pdcbes2
Supported Dispatcher instances- Pair1 on pdcbes1 in Standby state
- Pair2 on pdcbes2 in Primary state
- sdcbes1_MDS-CS on sdcbes1
Supported Dispatcher instances- Pair1 on sdcbes1 in Primary state
- Pair2 on sdcbes2 in Standby state
- sdcbes2_MDS-CS on sdcbes2
Supported Dispatcher instances- Pair1 on sdcbes1 in Standby state
- Pair2 on sdcbes2 in Primary state