Overview

The system uses a Microsoft SQL Server database to store the details of the call history and the configuration of the system. Due to the amount of call data that is stored within the database it is necessary that regular maintenance occurs and reliable backups are performed. The system has built in support for performing these actions.

When maintenance runs the databases are backed up and then the call history database entries are moved into an archive database. This enables the current database to remain relatively small and maintains performance.

Configuration

To configure the maintenance settings:

1. Access the Site Settings -> Database Maintenance configuration section.
2. Enter the details in the relevant areas.
   • Backup database daily: This enables or disables the daily automatic backup of the database.
   • Backup path: This defines the path where the backup file (.bak file) will be stored relative to the server.
     
     Ideally this should be changed to a different server to ensure that a backup is available in case of server hardware failure.
   • Backup time: This sets the time to perform the backup in 24 hour format.
   • Database archiving enabled: This enables the movement of the call logging data from the main database to the Archive databases.
   • Archiving period: This defines the period of time that each archive database should store. This value should only be changed under high call volumes when the Microsoft® SQL Server limits are being exceeded or where performance is affected by high volume. By default, the system will automatically create a new archive database once the limit of 1 million call records per archive database has been reached or 12 months has passed.
   • Delete old recordings: This enables the time to live option on the call recordings. When set any call recordings that are older than the value set in the Delete calls older than will be deleted. This means that the audio and dat and files will be removed from disk and permanently deleted. The associated database entry will still remain for reporting.