[lucasyew]

HI Guys,

Does anyone know If below step can work for disaster recovery plan?

Before DR
- BB user account A created at BES 1
- BB user account A is already associated to BB device A before the delete the account from BES 1

During DR
- delete the BB user account A from BES 1 without erase data and disable handheld to assume DR take place
- recreate the same BB user account A into BES 2 with different SRP ID from BES 1 and set password activation
- perform enterprise activation from BB device A

From my testing for the step above, I received fail message from BB device A activation. So is that the correct way of doing DR activity?

[desertimp]

With the high availability setup, BES1 and BES2 would be sharing the same database information which would mean same user information. You should not have to recreate any users from BES1 -> BES2.

Also I was told by support that you can use the same SRP for BES1 & BES2 if they are used in the HA setup.

Note: I Am assuming you are using 5.0

[lucasyew]

I am still using BES 4.1.4 version. I am trying to use different database and different SRP ID for my Disaster Recovery Plan.

[knottyrope]

You have to wipe the device to remove the encryption keys.
or
Delete all service books that have DESKTOP in them might work too.

[BBExpert]

May be I should blog about poor man's DR for BES. Check insideBES.blogspot.com in the future.

As for your idea, I think it should work, once you solve the permission issues. But essentially what you are doing is deleting a user from one BES Server and adding it to another. Consider the following -

- Wipe will destroy all user settings, unless you could restore the device backup to your new server( if possible and practical)
- How may users would you have to handle during DR. Do you plan to automate it?

Here is another pointer. Replicate your SQL DB to DR (either live or backups). Once you have SQL DB in DR you can use it like a knife cut over method to restore your BES. GIve it a thought. Let us know your experience.

[knottyrope]

Why not install 2 BES express servers (it is free) connecting to same database and move users if one BES fails. Might even be able to script it too.

[brkdncr]

on bes 4.1.x just install BES on a 2nd server. Don't let any of the BES services start. Use the same SRP.

Using either SQL Backup or some sort of backup application, make sure your BES DB is backed up and copied to the DR BES server.

When you need to fail over to the DR BES, stop the backup job, make sure your production bES is off, and then turn on the DR BES. Magically everything continues to work!