By: Filip Van Tittelboom user 26 Jan 2016 at 9:50 a.m. CST

1 Response
Filip Van Tittelboom gravatar
I'm having a hard time coming up with a decent backup restore strategy for Gluu. Right now I do a /opt/opendj/bin/backup -a -d (= all) to a directory and send it to an object storage. The thing is, if I destroy my Gluu machine and rebuild it from scratch, the backed-up OpenDJ dirs are useless, because apparently there are tons of hard-coded identifiers in the app used which do not match the data in OpenDJ anymore. I then also saved a copy of the /opt/gluu-server24/install/community-edition-setup/setup.properties.last file. I then copy it to /opt/gluu-server24/install/setup.properties, run the setup.py again... but Gluu doesn't come up anymore at all (even though it correctlty started). Errors like: ``` ERROR [org.gluu.oxtrust.config.OxTrustConfiguration] Failed to load application configuration from file: /opt/tomcat/conf/oxtrust-config.json ERROR [org.gluu.oxtrust.config.OxTrustConfiguration] Failed to load configuration from LDAP. Please fix it!!!. ``` But that file doesn't exist on other working Gluu instances. Do you have any advice on doing a decent backup/restore?

By Aliaksandr Samuseu staff 26 Jan 2016 at 10:39 a.m. CST

Aliaksandr Samuseu gravatar
Hi, Filip. So far, the best backup strategy I've heard of is probably to backup your whole Gluu CE vm, or at least its core partitions (those that are required to re-build the exact environment). There are certain export/import scripts, but I believe they were crafted for specific Gluu versions (like, for migrate your settings from 2.3.x to 2.4, or to upgrade from 2.4.0 to 2.4.1), so they may not qualify for a solid backup/restore strategy. May be Mike will be able to answer this question (as he is the author of them)?