BlackBerry Forums Support Community

BlackBerry Forums Support Community (http://www.blackberryforums.com/)
-   BES Admin Corner (http://www.blackberryforums.com/bes-admin-corner/)
-   -   BES site resilience architecture (http://www.blackberryforums.com/bes-admin-corner/260552-bes-site-resilience-architecture.html)

nspijoe 07-16-2012 02:00 PM

BES site resilience architecture
 
Hi,

I am in the process of deploying the 2 data center site resiliency model outlined in the 5.0.3 planning guide.

I just installed my first server pair (1 server in PDC and 1 in SDC).

It just occured to me and I cant find it specifically... do I need another license with a differen't license/SRP/auth?

- Joe

geofftech 07-16-2012 02:59 PM

Re: BES site resilience architecture
 
I believe you would need a second set of license info because you're planning on having 2x Primary servers. No more than one BES can use an SRP at a time.

nspijoe 07-16-2012 03:40 PM

Re: BES site resilience architecture
 
Thanks geofftech

Another question:
the 2nd instance gets its own database correct? I believe so but want to verify.

knottyrope 07-16-2012 03:49 PM

Re: BES site resilience architecture
 
it does not have to have its own database, It might be better to have them share then you can just move from one BES to the other with a few clicks.

with separate databases you have to use transporter and that will take some time to move users over.

BES supports SQL mirror with witness

nspijoe 07-16-2012 04:25 PM

Re: BES site resilience architecture
 
Page 44 out of the Planning_GUIDE PDF:

You can connect all of the BlackBerry Enterprise Server instances to the BlackBerry Configuration Database in data
center one.


So looks like it shares the same database

nspijoe 07-16-2012 10:37 PM

Re: BES site resilience architecture
 
So I have another question.
I am reading through the docs and trying to find exactly step by step for creating the pools.

Basically I am trying to follow the site resiliency model to the T.

I currently have 2 pairs setup.
Pair1: pdcbes1, sdcbes1
Pair2: sdcbes2, pdcbes2

I need to create pools for the following services:
Admin service (1 pool, use HLB on all 4 servers) - I believe this is done default
MDS Connection (primary pool (pdcbes1, sdcbes2), secondary (sdcbes1, pdcbes2)) - HLB needed?
BAS (primary pool (pdcbes1, sdcbes2), secondary (sdcbes1, pdcbes2))
Collaboration (primary pool (pdcbes1, sdcbes2), secondary (sdcbes1, pdcbes2)) - also need to use the HLB communication between Lync and BES (Guide anywhere?)


The next question is according to documentation I need to configure the Pair2 to connect to the Exchange servers in the SDC. Well when I added the besadmin account it automatically picked up its rpcclientaccess server which was in PDC. Is there a way to force the Pair2 to always use the CAS servers in the SDC? (DNS name pointing to VIP of LB in SDC).

knottyrope 07-17-2012 09:07 AM

Re: BES site resilience architecture
 
How many users are you making this for?

Do you have T support from RIM? I think you may be wanting to get it with this big of a setup.

I dont want to discourage you from posting, its just what you are doing is a lot more than many of us have done. I do want to assist with what I can and maybe even learn a few things as you progress.

nspijoe 07-17-2012 03:56 PM

Re: BES site resilience architecture
 
Quote:

Originally Posted by knottyrope (Post 1782906)
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


All times are GMT -5. The time now is 07:53 PM.

Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.