# Backing Up and Restoring Keycloak

This tutorial describes how to backup an active Entando Identity Management Keycloak instance and restore it in another environment.

# Prerequisites:

A Keycloak instance running on Entando with a database management system (DBMS) in the backend. This procedure will not work with an embedded database.

# Create a Backup of Keycloak Realm

  1. From the command line, get the pod name of the Keycloak server you wish to backup. In a quickstart environment, the pod name will begin with quickstart-kc-server-deployment.

  2. Use kubectl to start a bash shell in the pod:

 kubectl exec -it your-keycloak-pod-name -- /bin/bash
  1. Create a new directory in /tmp with:
mkdir -p /tmp/export 
  1. Run the following script to retrieve the data for the entando realm and save it to a JSON file in the export directory. A new Keycloak server will run on a different port (offset=200) to avoid conflicts with the original Entando Keycloak instance.
  1. If there are no errors, press Ctrl+C to stop the process.
  2. Type exit to close the bash shell in the pod.
  3. Execute this command to copy the realm data file to the proper location:
kubectl cp [keycloak-pod-name]:/tmp/export/ keycloak-backup

# Import the Keycloak Realm

  1. Login to the new Entando Keycloak server where the realm is to be restored.

  2. From the left sidebar, go to Import.

  3. Click Select file button and upload the JSON file from the keycloak-backup directory. You will see the following page:

Entando ID Management UI

  1. You have now successfully imported the Keycloak realm to a new environment.


If you are using a different environment, with a different hostname, you should import only users or set the flag for If a resource exists to Skip.