Restoring the Raft cluster from backup

The backup does not contain temporary files, including artifacts of background tasks.

To restore the Raft cluster from backup:

1. Prepare the cluster for recovery:
   1. Stop the KUMA Core service on each node in the cluster:

      sudo systemctl stop kuma-core-<KUMA_Core_service_ID>.service

   2. On each node where the KUMA Core service is installed, delete the working directory:

      sudo rmdir <directory_name>

   3. On each node where the KUMA Core service is installed, remove the systemd service.

   At this point, all KUMA Core services are stopped and the servers are ready for cluster recovery.

2. Restore the Raft cluster with a single KUMA Core:
   1. Select the server that will become the new initial node of the Raft cluster and deploy the new initial node of the cluster without the --raft.join option:

      sudo /opt/kaspersky/kuma/kuma core --raft.node.listen 0.0.0.0:7209 --raft.node.addr "$(hostname -f):7209" --health 0.0.0.0:7208 --internal 0.0.0.0:7210 --private 0.0.0.0:7220 --cybertrace 0.0.0.0:7222 --rest 0.0.0.0:7223 --install

   2. Restore from backup using the REST API.

   The Raft cluster is restored from backup. The initial node of the KUMA Core cluster is restored.

3. If you need a high-availability Raft cluster, perform the restoration procedure on the rest of the cluster nodes:
   • If you want to use the new servers for KUMA Core services, use the expand.sh installer and the expand.inventory.yml inventory file to deploy the KUMA Core services and add the nodes to the Raft cluster.
   • If you want to use the old nodes, reinstall the KUMA Core services with the --raft.join option to add the nodes to the Raft cluster using the following command:

     sudo /opt/kaspersky/kuma/kuma core --raft.join <FQDN of the initial cluster node>:7210 --id <ID of the KUMA Core service copied from the web interface> --install

The cluster is restored. You do not need to reset certificates of services, such as collectors, correlators, storages, and others, but you may need to change the value of the --core parameter in the systemd file to make the services communicate with the correct KUMA Core if the list of cluster nodes is changed as part of the restoration process.

Page top