Backup and restore - local
The TrendMiner Appliance automatically creates a backup before an update. However, we always advise to take a backup manually when changing important configuration such as the configuration of an external identity provider.
It is also advised to periodically create and download a backup manually in case major system failures render the system unusable.
All previously created backups are listed in a table. The time displayed for the backup is always server time.
Backup and restore functionality:
create new database backups: these backups are database backups and only contain data stored in the TrendMiner databases. These backups contain all data which cannot be reconstructed from a clean installation and can be used for troubleshooting or disaster recovery. Backups that are created, are stored on the system until they are removed (available as "Delete backup" under the options menu of that backup). Backups can be downloaded with "Download backup" in the options menu of the backup.
Important
TrendMiner backups do not replace the need for regular VM snapshots. Read here why VM snapshots are as important as database backups.
upload a backup: upload a database backup onto the TrendMiner server. This action will not automatically restore the backup. An additional manual action is required for this.
Note
The original backup date/time is not part of the backup itself. The date and time of the upload will be used to identify the backup.
restore existing backups: clear the existing databases and restore an older backup. It is not advised to use this option without consulting TrendMiner support since backup restores can involve extra complexity and are typically only advised in migration scenarios or in specific rollback scenarios.
Important
Restoring a backup created on TrendMiner version X on a TrendMiner version Y installation is not supported.
Warning
Always check the available disk space when uploading or restoring a backup. Restoring a backup will fail when there is insufficient disk space left. The available disk space must be at least the size of the backup after extraction. We recommend having at least the same disk size as the installation the backup originates from in case of doubt.
download backups: download database backups before starting an upgrade to safeguard all user generated data onto a local system.
delete backups: since database backups are not compatible with older versions it is usually not useful to keep old backups. You can permanently delete old backups here.