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.
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
- 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.
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.
- The BlackBerry Enterprise Server and SQL Server must be installed on separate servers.
- Lotus Domino must be configured with Transactional Logging.
- The Exchange Server must NOT be installed on the BlackBerry Enterprise Server.
- 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.
- Neverfail Primary and Secondary servers must have Management IP addresses configured.
- Firewall rules should be updated to enable the Management IP communicate with the RIM NOC on port 3101.
Note: Some of the Pre-Install Checks are enforced by the plug-in while others must be performed manually.
Enforced by the plug-in:
- A local database is NOT allowed.
Not enforced by the plug-in:
- This solution requires BlackBerry Enterprise Server V4.0 SP4 or V4.1 SP1. The latest Service Pack is recommended.
- The Exchange server must NOT be present on the BlackBerry Enterprise Server.
- For Lotus Domino, Transaction Logging must be enabled.
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.
- Enforced by the plug-in:
- Deploy the Neverfail for BlackBerry Enterprise Server Plug-in - V201.5.99 using the above information.
The following services will continue to run on the passive server thereby omitting the requirement for the Mail Store scanning process at start-up.
- 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.
- The BlackBerry Logs will NOT be included within the protected set because of the BlackBerry services running on the passive server.
- The passive server does NOT establish a connection to the RIM NOC, the SRP connection is in-active.
Notes on Lotus Domino Transactional Logging:
- 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.
- Crash recovery and consistency checks increase the time that the Domino messaging system is inaccessible to BlackBerry, BlackBerry devices, or Lotus Notes users.
- 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.
- Configuring Transactional Logging improves the performance and availability of BlackBerry for Lotus Domino solution.
Neverfail BlackBerry Enterprise Server Plug-in V201.5.99