You want to preserve critical data and rebuild your Tealeaf configurations in the event of a system failure.
Regularly back up all Tealeaf databases using one of the recommended strategies. Depending on the size and daily volumes of captured traffic, one strategy may be more appropriate.
Before you clear data from the Canisters or the SQL Server databases, it is recommended that you perform backups of them.
Backup recommendations for preserving environment or migrating CX settings
In preparation for a complete crash in which the entire machine is lost, you should create copies of the following Tealeaf CX Server items so you can re-create your system.
- Backup Long Term Canister and indexes
- Tealeaf report definitions (
- System folder contents
- All configuration files (
- Rules Scripts directory (especially if split pipeline)
- Registry hives:
Creating mirror servers to preserve your environment
You can preserve your environment by creating a mirror server that contains the same installation and settings as the one on which you are having problems. To do so, use Norton Ghost or a similar tool to image the server's disks.
Clearing data from databases gradually
You can clear data from databases gradually by adjusting the canister, data collection, and data retention settings so that data is removed without losing any data that was not processed by the Tealeaf system.
For example, if you configure data retention to be a single day and verify that data collection occurs shortly before the daily time for trimming the database, you can remove data more gracefully.
Gradual data clearing can be manipulated by changing system parameters.
Clearing data from the canister immediately
You can clear data from the canister immediately by using the
CanRebuild utility to rebuild it.
CanRebuild can be used to immediately remove problematic data, by default Tealeaf canisters and databases are trimmed of old data based on configuration settings.
Clearing data from the SQL Server
The SQL Server databases can be cleared by dropping and re-creating them with the following exception, as described here.
The following Tealeaf CX databases can be dropped and re-created independently: