Your Tealeaf databases should be backed up regularly for recovery and performance reasons. Without valid backups, Tealeaf might be unable to recover customer data in the event of a system failure or data corruption.
Without a proper backup strategy, the log files for the Tealeaf databases may grow unbounded, causing both disk space loss and performance issues.
The strategies that are outlined below are recommended for providing the most reliable recovery capability while minimizing storage overhead and potential interference with the operation of the Tealeaf system.
Recommended backup strategy
The recommended backup strategy should be deployed for all Tealeaf databases, whenever possible. These databases contain information essential to the system operation or information that is not easily recovered from another part of the Tealeaf system.
By default, the Tealeaf databases are installed and maintained in Simple Recovery Mode. As a result, incremental backups are not necessary.
Alternate backup strategies
If the Tealeaf databases cannot be backed up on a nightly basis or another recovery model or backup strategy is required for business reasons, you should ensure that the Tealeaf databases are backed up and maintained properly. Failure to do so may result in wasted space and decreased system performance.
You can back up your Tealeaf databases using either of the following ways.
- The Tealeaf installation process includes pre-scripted SQL files to create and schedule back up jobs consistent with the backup strategy that is recommended by Tealeaf.
- You can use the Database Manager to configure and run regularly scheduled backups.
There are several options for backing up your Tealeaf system and captured data.
|Event Model data||Through the Portal Management page, you can run scheduled and on-demand backups of event model data.|
|Database data||Using the Database Manager or SQL Server Management Studio, you can perform full backups of all Tealeaf databases.|
|Canister data||Tealeaf provides a pair of utilities for backing up session and index data stored on Canisters.|
|Scorecards, dashboards, reports||Through the Portal, you can import and export templates for scorecards, dashboards, and reports.|
Archived Event Model Data
Data configured through the Event Manager are archived using the event model backup, including the items listed here.
Event definitionsNote: When events are restored, any references in reports to events that are no longer present in the system are removed from the report. In some cases, this removal may result in empty reports, scorecards, and dashboards.
Hit Attribute definitions
Dimension data, including:
- Dimension and report group definitions
- Dimension whitelists
Note: Non-whitelisted values are not backed up.
- Dimension group lists.
Note: During restore, whitelist and group list values are restored. Any additional values already in the system are untouched.
Session Attribute definitions
Top Mover definitionsNote: Alert definitions are not supported for backup through this method.