eG Monitoring
 

Measures reported by CBDataBaseTest

A key component of the Connection Broker is its database. The Connection Broker is completely self-contained and is bundled with an internal database. This database stores and maintains the following:

  • Passwords only for users that are created locally
  • Clients
  • desktops and their environments
  • Microsoft Active Directory® user credentials: Encrypted.
  • Machine centers: Access credentials are encrypted.
  • Locations, roles, and all other operational parameters

An external database, on the other hand, is required when Connection Brokers are clustered. To handle high peak loads (such as, simultaneous logons) and failure of a Connection Broker (or its host) it is necessary to cluster Connection Brokers and run each Connection Broker on a different virtualization host. As soon as you cluster Connection Brokers virtual machines, they need an external database in order to share information. Connection Broker version 5.0 uses Microsoft SQL Server® 2005 database software.

If the internal/external database is rendered unavailable or is experiencing a significant slowdown, it can cause prolonged Connection Broker outages, deny/delay users access to critical desktops/data, and thus mar the user experience. Using the CBDatabaseTest, administrators can periodically monitor the availability and responsiveness of the local and remote databases, be proactively alerted to anomalies, and avert adversities in time.  The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Availability This measure indicates whether the database is available or not. Percent While the value 100 indicates that the database is available, the value 0 indicates that it is not.

The internal database will be available as long as the Connection Broker is. If the external database is unavailable, it could be owing to an improper configuration of the database or a poor network connection (in case of an external database).
Response_time Indicates the time taken by the Connection Broker to respond to requests. Secs Ideally, the value of this measure should be low. A very high value indicates a marked deterioration in the performance of the database, which can be attributed to insufficient space, improper configuration, or a network congestion (in case of an external database).