Documentation Portal

There are mainly 3 ways to backup your TrendMiner appliance data:

A local database backup contains only the database data (typically user generated data). This is the bare minimum to safeguard your data. It does not include index data or system configuration and is not suited for disaster recovery. The main purpose of a local database backup is troubleshooting (e.g. compare data from before and after an upgrade in case of data migration upgrade issues). The backup is created and stored on the local TrendMiner server but can be downloaded to safeguard it in case the server becomes unusable. Local database backups can only be created manually.

A remote full backup contains next to the database data also the index data and the server independent system configuration. It can be used for disaster recovery but it will takes some time and effort since server configuration is not stored and needs to be redone. Remote full backups are stored in the cloud or on the local network, but not on the TrendMiner server itself. Full backups can be created manually or via an automatic backup schedule.

A VM snapshot is the most complete backup. It contains everything: database data, index data, server configuration, ... and is therefor the most complete option for disaster recovery. For this reason VM snapshot are mandatory before starting a big important configuration change or a TrendMiner upgrade. VM snapshots are created and managed outside of TrendMiner.