Updated: 2008-04-01

The Groove Relay utilizes a transactional database system that stores basic user information (including authentication keys and identity information), queues of Groove device-targeted messages (updates to Groove workspaces), and queues of identity-targeted messages (instant messages and invitations). The size of these queues changes continuously as Groove clients deposit (enqueue) and retrieve (dequeue) messages.

All Groove message queues reside in a series of database files in the Data subdirectories of the Groove Relay installation directory. User identity information, authentication keys, and other ‘metadata’ reside in another set of database files also under the Data directory.

The Groove Relay creates these databases at startup, if they are not already present. It also pre-allocates a number of Data files (Extents). The database system also creates transaction log files that are used to maintain the integrity of the Groove Relay databases in the event of system failure. The Groove Relay depends on these log files to recover message queues and other related databases when restarting after an outage.

See Also