Neverfail for BlackBerry Enterprise Server Plug-in V201.5.99 - Release Notes



This Knowledgebase article provides information about this specific release of the Neverfail BlackBerry Enterprise Server Plug-in V201.5.99 designed for deployment in an enterprise environment.

More Information

To meet the demands of protecting BlackBerry Enterprise Servers within large enterprises, Neverfail provides a plug-in specifically designed for large enterprises with 500+ users along with advice and recommendations for implementation to ensure that BlackBerry service is Continuously Available.

Release Notes for:

  • Neverfail for BlackBerry Enterprise Server Plug-in V201.5.99

New Features

  • Fast start-up times.
    • Same BlackBerry server name on both the Primary and Secondary servers.
    • Same SRP ID information on both the Primary and Secondary servers.
    • No need to resend Service Books to devices during a switchover/failover process.
    • Full Mail Store scanning is not performed when the server becomes active reducing start-up time significantly.
    • The BlackBerry services responsible for scanning the entire Mail Store remains running on the passive.
    • The BlackBerry services running on the passive are kept up-to-date with changes within BES because a connection is maintained to the BESMgmt database.
  • No architectural restrictions imposed upon the deployment of BlackBerry Enterprise Server.
    • All RIM components can be installed on a single server.
    • Unless performance or scalability demands it, multiple or remote Attachment MDS services.
  • Infrastructure monitoring rules to ensure that the entire messaging infrastructure is available.
    • Monitoring and alerting for the remote SQL Server database.
    • Monitoring and alerting for the remote Exchange server.

    Note: SQL Server must be remote from the BlackBerry Enterprise Server.

Changed Features

  • None

Issues Fixed

  • None

Known Issues

  • None

Installation Information

The Neverfail for BlackBerry Enterprise Server Plug-in V201.5.99 is installed via the Neverfail Setup process.  Subsequent installations/upgrades may be performed using the Application -> Plugins tab of the Neverfail Heartbeat Management Client.

  1. Infrastructure Requirements
    1. The BlackBerry Enterprise Server and SQL Server must be installed on separate servers.
    2. Lotus Domino must be configured with Transactional Logging.
    3. The Exchange Server must NOT be installed on the BlackBerry Enterprise Server.
    4. This version of Neverfail for BlackBerry Enterprise Server cannot be deployed in a WAN; if Exchange fails over to the DR site, then the Dispatcher service must be restarted.
    5. Neverfail Primary and Secondary servers must have Management IP addresses configured.
    6. Firewall rules should be updated to enable the Management IP communicate with the RIM NOC on port 3101.
  2. Pre-Install Checks

    Note: Some of the Pre-Install Checks are enforced by the plug-in while others must be performed manually.
    1. Enforced by the plug-in:
      1. A local database is NOT allowed.
    2. Not enforced by the plug-in:
      1. This solution requires BlackBerry Enterprise Server V4.0 SP4 or V4.1 SP1.  The latest Service Pack is recommended.
      2. The Exchange server must NOT be present on the BlackBerry Enterprise Server.
      3. For Lotus Domino, Transaction Logging must be enabled.
      4. Management IPs must be configured on both the Primary and Secondary server.

        Note: If any of these conditions cannot be satisfied within the customer environment, then the Neverfail for BlackBerry Plug-in V201.5.99 solution should not be deployed.
  3. Implementation Notes
    1. Deploy the Neverfail for BlackBerry Enterprise Server Plug-in - V201.5.99 using the above information.
    2. The following services will continue to run on the passive server thereby omitting the requirement for the Mail Store scanning process at start-up.
      • Dispatcher
      • Synchronization
    3. The Management IP on the passive server provides a connection to the SQL Server database allowing the BlackBerry Dispatcher and Synchronization services to access configuration information within the BESMgmt Database.
    4. The BlackBerry Logs will NOT be included within the protected set because of the BlackBerry services running on the passive server.
    5. The passive server does NOT establish a connection to the RIM NOC, the SRP connection is in-active.
    6. Notes on Lotus Domino Transactional Logging:
      1. By default, Lotus Domino Transactional Logging is disabled and must be enabled. When the server recovers from a crash it performs a recovery action that performs a database consistency check. This configuration is not optimal for I/O performance on either Lotus Domino or BlackBerry Enterprise Server.
      2. Crash recovery and consistency checks increase the time that the Domino messaging system is inaccessible to BlackBerry, BlackBerry devices, or Lotus Notes users.
      3. Neverfail for Lotus Domino supports automatic filter discovery of Transactional Database and Log locations. Neverfail recommends that Neverfail for Lotus Domino Plug-in V201.5.2 be used.  Please refer to Knowledgebase article #1312 - 'Transactional Logs For Lotus Domino Are Not Protected By Default - A File Filter Can Be Added' to configure a filter for Transaction Logs when using older versions of the Neverfail for Lotus Domino product.
      4. Configuring Transactional Logging improves the performance and availability of BlackBerry for Lotus Domino solution.

Applies To

Neverfail BlackBerry Enterprise Server Plug-in V201.5.99

Related Information



0 out of 0 found this helpful



Please sign in to leave a comment.