[Filip_PwC]

Hi all,

I would like to make my installation a redundant one.
How would you go about this?

I'm thinking of doing the following.

Install new server (new srp ID) on different machine.
Have it create initially a new db (locally), and then upgrade it to the same version.

Then point this newly installed server to my already existing db.

that way (according to my logic ) if one of my 2 servers fail, I can move users from my down server to my new server.

Am I correct in my planned setup or are there things I'm overseeing?
Is this a technically correct setup?
How did you setup your environment to be redundant?

Am I also able to move users between servers if they each have their own sql db and one of the servers is down? (I'm thinking no, but just to be sure )

Many thanks in advance!

Filip

[bertiebassett]

Originally Posted by Filip_PwC

Hi all,

I would like to make my installation a redundant one.
How would you go about this?

I'm thinking of doing the following.

Install new server (new srp ID) on different machine.
Have it create initially a new db (locally), and then upgrade it to the same version.

Then point this newly installed server to my already existing db.

that way (according to my logic ) if one of my 2 servers fail, I can move users from my down server to my new server.

Am I correct in my planned setup or are there things I'm overseeing?
Is this a technically correct setup?
How did you setup your environment to be redundant?

Am I also able to move users between servers if they each have their own sql db and one of the servers is down? (I'm thinking no, but just to be sure )

Many thanks in advance!

Filip

I'd create one Dbase serving 2x BES's - much easier to move users between BES's that way..

[noname]

Originally Posted by Filip_PwC

Hi all,

Am I also able to move users between servers if they each have their own sql db and one of the servers is down? (I'm thinking no, but just to be sure )

Filip

No, to move users between 2 BESes so that it kicks off the backend Enterprise Activation (EA) that switches the service books for the BlackBerry devices (i.e. transparent to users), the servers MUST share the same BESMgmt DB.

If you are moving users between 2 BESes having their own SQL BESMgmt DB, then you will need to wipe the BlackBerry and then re-EA it.

[Filip_PwC]

once again thanks noname

[ashleyneiltaylor]

I'd also create a backup SQL database using Transactional replication to another SQL server.

This is our DR plan.

1 main BES located at Primary Hubsite
1 main SQLserver at Secondary Hubsite
1 backup BES at Secondary Hubsite
1 backup SQLserver at a spoke site.

[DarkWater]

If you have the hardware for it, the best way is to combine the SQL backup with offline machines that match your online BES machines.