BlackBerry Enterprise Server High Availability Disaster Recovery Failover and Failback

INFORMATION

In the case the primary active directory site (SITE01) is to have an unexpected catastrophy that leads to the entire site to become unavailable, it is assumed that Exchange services will either automatically fail over to the secondary site (SITE02) or an administrator has manually activated the servers in DR site. Once that has been done, BES services will need to be brought to the DR site as well and BESSEC be made primary.

In the case the primary BES server (BESPRI) is to become unresponsive or the entire primary site is to become unavailable, the necessary measures can be taken to restore BES services on the standby server (BESSEC). Because BES disaster recovery has been configured for manual failover, administrative interaction to restore services is required. The process involves the failover of the SQL database followed by the activation of the standby BES server.

Disaster Recovery Failover to BESSEC (Standby)

When the mirrored database is synchronized (that is, when the database is in the SYNCHRONIZED state), the database owner can initiate manual failover to the mirror server however in this case, the principal database is no longer online.

  1. Log on to BESSEC with the BES administrator account.
  2. From the start menu, open the SQL Management Studioand connect to the local (BESSEC) server instance
    1. In the case you receive a Login Failure message, click on Options on the Connect to Server dialog box
    2. Click on the Connection Properties tab and select Master from the drop-down Connect to Database menu
    3. Click Connect to establish the connection
    4. Expand Databases, and select the database to be failed over (BESMgmt).
    5. Right click the database and select New Query
    6. In the Query window, type the following command to Force the database service to the mirror/standby database after the principal server fails with the database in an unsynchronized state or in a synchronized state when automatic failover does not occur:

ALTER DATABASE BESMGMT SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS

Running this command makes the standby database principal.

Now that the SQL database is active on the standby server, the next step is to move BES services to the server as well. There are two possible methods for this procedure. You will notice a slight delay of between 2-5 minutes before you will be able to use either of these methods after the SQL database failover. This is because the BES services will need to reconfigure themselves to connect to the local database.

Method 1 – Fail over the BlackBerry Enterprise Server using the BlackBerry Administration Service:

  1. In the BlackBerry Administration Service, on the Servers and components menu, expand High availability then Highly available BlackBerry Enterprise Servers.
  2. Click the name of the BlackBerry Enterprise Server pair.
  3. Click Manual failover. Choose the standby BlackBerry Enterprise Server instance.
  4.  Click Yes – Failover to standby instance.  Verify that the failover event occurred.

Method 2 – Fail over the BlackBerry Enterprise Server using the BlackBerry Server Configuration Panel:

  1. Make sure you are logged onto the standby BES (BESSEC)
  2. In the BlackBerry Server Configuration Panel for the standby BlackBerry Enterprise Server, on the BlackBerry Server tab, click Make Primary.
  3. Click OK.
  4. Verify that the failover event occurred.

Please allow up to 2 minutes after activating the standby BES server for the BlackBerry Administration Service (BAS) web site to become active.

Disaster Recovery Failback to BESPRI (Primary)

Once the primary BES server (BESPRI) has been restored onto the network, all BES services can now be restored to it. Once again, the SQL database must be made principal before the BES services are restored.

  1. Log on to BESSEC (since it is now the primary server) with the BES administrator account.
  2. From the start menu, open the SQL Management Studio and connect to the local (BESSEC) server instance
  3. Expand Databases, and select the database to be failed over (BESMgmt)
  4. Right-click the database, select Tasks and then click Mirror. This opens the Mirroring page of the Database Properties dialog box.
  5. Click Resume Mirroring to restore the synchronization process.
  6. Confirm that the database status on both BESPRI and BESSEC are set to SYNCHRONIZED before continuing.
  7. Once both databases are synchronized with each other, right-click the database, select Tasks and then click Mirror.
  8. Click Failover to initiate the process.

A confirmation box appears. The principal server begins by trying to connect to the mirror server by using Windows Authentication. If Windows Authentication does not work, the principal server displays the Connect to Server dialog box. If the mirror server uses SQL Server Authentication, select SQL Server Authentication in the Authentication box. In the Login text box, specify the login account to connect with on the mirror server, and in the Password text box, specify the password for that account.

If failover succeeds, the Database Properties dialog box closes. The mirror database becomes the principal database and the principal database becomes the mirror. If failover fails, an error message is displayed and the dialog box remains open.

Now that the SQL database is active back on the primary server, the next step is to move BES services to the server as well. There are two possible methods for this procedure. You will notice a slight delay of between 2-5 minutes before you will be able to use either of these methods after the SQL database failover. This is because the BES services will need to reconfigure themselves to connect to the local database

Method 1 – Fail over the BlackBerry Enterprise Server using the BlackBerry Administration Service:

  1. In the BlackBerry Administration Service, on the Servers and components menu, expand High availability then Highly available BlackBerry Enterprise Servers.
  2. Click the name of the BlackBerry Enterprise Server pair.
  3. Click Manual failover. Choose the standby BlackBerry Enterprise Server instance.
  4.  Click Yes – Failover to standby instance.  Verify that the failover event occurred.

Method 2 – Fail over the BlackBerry Enterprise Server using the BlackBerry Server Configuration Panel:

  1. Make sure you are logged onto the standby BES (BESSEC)
  2. In the BlackBerry Server Configuration Panel for the standby BlackBerry Enterprise Server, on the BlackBerry Server tab, click Make Primary.
  3. Click OK.
  4. Verify that the failover event occurred.

Please allow up to 2 minutes after activating the standby BES server for the BlackBerry Administration Service (BAS) web site to become active.

Advertisements

3 thoughts on “BlackBerry Enterprise Server High Availability Disaster Recovery Failover and Failback

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s