Mindbreeze GmbH, A-4020 Linz, 2019.
All rights reserved. All hardware and software names are trade names and/or trademarks of their respective owners.
These documents are confidential. The delivery and presentation of these documents alone does not justify any rights whatsoever to our software, our services and service performance results or other protected rights. The disclosure, publication or reproduction is not permitted.
For reasons of easier legibility, gender differentiation has been dispensed with. In terms of equal treatment, appropriate terms apply to both sexes.
This document describes the most important aspects of backing up Mindbreeze InSpire configuration and index data.
The backup strategy should contain the following types of data and should be applied especially before installing product updates:
Mindbreeze InSpire regularly backs up:
All other data must be backed up manually.
If you want to create manual backups, you can read about this in the following documentation, depending on which Mindbreeze InSpire Generation you are using:
Automatically created backups are stored in /data/backups. The following sections provide details on restoring backups.
Please note that shell access is required to restore configuration data.
Stop the mesmaster service and run the following script:
/opt/mindbreeze/bin/import_managerconfig.sh <configuration directory>
The <configuration directory> refers to the automatically created backups in the /data/backups/mesconfig-backups/inspire_mesconfig-<date time> directory.
Automatically created index backups are stored under /data/backups/index-backups. To restore the indexes, copy the underlying /data/backups/index-backups folders (but only the contents of the current folder) to their original directory (typically /data/indices or /data/servicedata), for example:
cp -a /data/backups/index-backups/ms-file/current/* /data/indices/ms-file
Automatically created database backups are stored under /data/backups/telemetrydb-pgdump/<date> and contain the following files:
To restore the databases, first stop the services mesnode and apptelemetryserver. You can then restore the databases with pg_restore.
Copy and restore automatically created backups from the G6 Appliance to the G7 Appliance.
Note that before restoring the configuration data (from /data/backups/mesconfig-backups/inspire_mesconfig-<date time>), you must delete the following files from the backup (or move them to another location):
If you had installed plugins manually on your G6 Appliance, you can install them as usual via the Mindbreeze Management Center.
Also note that after restoring the backups, the NodeIDs in /etc/mindbreeze/mesconfig.xml must be manually adjusted to the new appliance.
In addition to the automatically created backups, it is necessary to create some backups manually. In most cases, all relevant data is stored in the /data directory. The following folders are worth mentioning:
When you have copied all relevant files to your G7 appliance, make sure they are all in the /data directory. Otherwise this data would be replaced by a Mindbreeze InSpire update of the appliance.
For example, it could be that custom search apps are not located under /data/apps but with the legacy variant in the directory /opt/mindbreeze/bin/webapps. In this case, you must make configuration changes in the Mindbreeze Management Center under Client Service (see ).