Hello Rémy,
I think Keycloak-side export/import makes more sense when migrating between DB vendors,
since the dump is in vendor-neutral JSON format.
For backup purposes, doing a DB-side backup should be sufficient (let alone it's
normally much faster than its Keycloak-side counterpart).
Cheers,
Dmitry Telegin
CTO, Acutus s.r.o.
Keycloak Consulting and Training
Pod lipami street 339/52, 130 00 Prague 3, Czech Republic
+42 (022) 888-30-71
E-mail: info(a)acutus.pro
On Sat, 2018-11-03 at 20:15 +0100, Rémy Grünblatt wrote:
Hello,
I'm wondering: what are your backup strategies for keycloak?
I plan to use docker and keycloak, and of course I'll be backuping the data.
The backup for the database side is ok: just launching psql in the
container will do it.
But for the keycloak side: do I need any backup? In there,
https://www.keycloak.org/docs/2.5/server_admin/topics/export-import.html,
a method for backuping the « entire database » is mentioned, and I was
wondering if this would be useful in addition of the database
(container) backup.
I thought about modifying the entry point to include this backup (what I
have done), but saving it to a volume is tricky as it seems keycloak is
running with 1000/1000 uid/gid (which is the first non-root user on many
linux distribution…).
Any hints? How do you do it, in your production?
Rémy
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user