KUMA backup

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 perform backup using the REST API.

Special considerations for KUMA backup

• Data can only be restored from a backup copy created in the same version of KUMA.
• 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.

  How to reset a database in MongoDB when the mongodb service is working

  If the KUMA Core fails to start after data recovery, repeat the recovery from scratch, but clear the kuma database in MongoDB this time.

  To restore KUMA data and clear the MongoDB database:

  1. Log in to the OS of the KUMA Core server.
  2. Stop the KUMA Core by running the following command:

     sudo systemctl stop kuma-core

  3. Log in to MongoDB by running the following command:
     1. cd /opt/kaspersky/kuma/mongodb/bin/
     2. ./mongo
  4. Clear the MongoDB database by running the following commands:
     1. use kuma
     2. db.dropDatabase()
  5. Exit MongoDB by pressing Ctrl+C.
  6. Restore data from the backup copy by running the following command:

     sudo /opt/kaspersky/kuma/kuma tools restore --src <path to the directory containing the 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. Recreate the services using the recovered service resource sets.

  Data is restored from backup.

  How to reset a database in MongoDB when the mongodb service is down