KUMA backup

KUMA allows you to back up the KUMA Core database and certificates. The backup function is intended for restoring KUMA. To move or copy the resources, use the resource export and import functions.

Backup can be done in the following ways:

Using the REST API
Using the /opt/kaspersky/kuma/kuma executable file
The KUMA backup using the kuma executable file is not available in KUMA higher than 2.1.

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.
Backup of collectors is not required unless the collectors have an SQL connection. When restoring such collectors, you should revert to the original initial value of the ID.
If KUMA cannot start after the restore, it is recommended to reset the kuma database in MongoDB.
How to reset a database in MongoDB
If the KUMA Core fails to start after data recovery, the recovery must be performed again but this time the kuma database in MongoDB® must be reset.

To restore KUMA data and reset the MongoDB database:
1. Log in to the OS of the server where the KUMA Core is installed.
2. On the KUMA Core server, run the following command:
  sudo systemctl stop kuma-core
3. Log in to MongoDB by running the following commands:
  1. cd /opt/kaspersky/kuma/mongodb/bin/
  2. ./mongo
4. Reset the MongoDB database by running the following commands:
  1. use kuma
  2. db.dropDatabase()
5. Log out of the MongoDB database by pressing Ctrl+C.
6. Restore data from a backup copy by running the following command:
  sudo /opt/kaspersky/kuma/kuma tools restore --src <path to folder containing backup copy> --certificates
  
  The --certificates flag is optional and is used to restore certificates.
7. Start KUMA by running the following command:
  sudo systemctl start kuma-core
8. Rebuild the services using the recovered service resource sets.
Data is restored from the backup.