Restore in place - FalkorDB Enterprise

What is implemented

The Admin UI restore dialog supports Override current instance. It calls the restore API for the existing deployment with:

{ "backup": { "name": "<backup-name>", "namespace": "<namespace>" } }

The backend validates that the target cluster exists, the backup exists, and the backup is marked restorable before creating a restore resource.

Restore from Admin UI

Open Deployments.
Open the target deployment.
Go to Backups.
Select Restore on the backup to use.
Choose Override current instance.
Select Restore Now.

Restoring into the current deployment replaces current data with the selected backup data. Coordinate application downtime before starting the restore.

Validate

kubectl get restores.dataprotection.kubeblocks.io -n <namespace>
kubectl get clusters.apps.kubeblocks.io -n <namespace> <deployment-name> -o yaml
kubectl get pods -n <namespace>

In the Admin UI, review Backups, Events, and deployment health after the restore finishes.

Failure conditions

The restore fails if the target cluster does not exist.
The restore fails if the backup does not exist.
The restore fails if the backup is not ready for restore.

⌘I