Backup

Relevant files to backup on a OTH platform is the database and the services log files.

Front-end node

The front-end node can be recreated from the OTH ansible playbook with the inventory.yml, settings.yml and requirements.yml files. Make sure to backup these files.

You may also consider keep backups of the /var/log/haproxy.log

Application nodes

Since no dynamic data are stored on the application nodes other than the services logfiles, no backup is performed since all services are re-creatable from the OTH ansible playbook with inventory.yml, settings.yml, authentication.yml and requirements.yml files. Make sure to backup these files.

It is recommended to perform regular snapshots of the application node VMs, for faster recovery and to backup the /var/log/<service-name>/* logfiles or log to a central logging solution like loki, splunk or similar.

Database/storage node

MariaDB: It is highly recommended to backup your database regularly. The database contains all the dynamic data such as users, measurements, etc. Backup should be encrypted due to the sensitive nature of the data.

Minio: It is highly recommended to backup your object-storage bucket data, which is located in /data/oth-minio/* directory on the storage node.

It is recommended to perform regular snapshots of the storage node VM, for faster recovery. Please note that it is advisable to stop the Database/RabbitMQ/Minio service before performing a snapshot of the VM, to ensure consistency of data.

For both log files and database backups, it is highly recommended to copy them to an off-site location.