KUMA allows you to back up the KUMA Core database and certificates. The backup functionality is intended for restoring KUMA. To move or copy resources, use the resource export and import functionality.
You can also back up individual partitions using the archival procedure.
Special considerations for KUMA backup
Data may only be restored from a backup if it is restored to the KUMA of the same version as the backup one.
Backing up collectors is not necessary, except collectors with an SQL connection. When restoring such collectors, you must revert the initial ID to the original value.
If the MongoDB service does not start, we recommend resetting the 'kuma' database in MongoDB. If the server that hosts the database loses power, the integrity of the database may be compromised. In such a case, you can reset the database and restore the data from the backup.
To perform a backup in a distributed installation with a hostname change for the KUMA Core:
On machine 1, create a backup copy of KUMA.
Place the backup from machine 1 on machine 2 and restore from backup.
After restoring from the backup, the KUMA Core is deployed on machine 2. You need to switch all services from the KUMA Core installed on machine 1 to the KUMA Core installed on machine 2.
On machine 1:
Stop the KUMA Core service:
sudo service kuma-core-00000000-0000-0000-0000-000000000000 stop
Go to the /usr/lib/systemd/system directory, find the files of the collector, correlator, storage, event router services, and replace the hostname with the new one in the --core option. For example:
On machine 2, go to the KUMA section Resources and services → Active services, in the list of services, select the check box for the relevant collector, correlator, storage, router services, and in the toolbar or menu (), select Reset certificate.
KUMA automatically generates a new certificate for each service for which the certificate has been reset. You do not need to restart running services; the new certificate is applied automatically. A stopped service must be restarted to have the certificate applied.
Backup in a distributed installation with a hostname change for the KUMA Core is complete. All services are switched from the KUMA Core installed on machine 1 to the KUMA Core installed on machine 2. Services are displayed in the KUMA section Resources and services → Active services with a green status.