How do I recover data when old database assumes users are in JIRA?

[Alistair Guthrie]

I am trying to recover an old Confluence database and have got as far as determining that the database was created using Confluence 5.6.4. When I install v5.6.4, it successfully loads the database (i.e. it doesn't crash or complain about the build used to create the database) but the old database assumes that users will be authenticated via JIRA. Suddenly I have no way to login to Confluence so can't export the data or even view it. The JIRA server has been moved recently so I doubt that the information held, in Confluence, about the JIRA instance is correct.

It seems that no-one predicted this problem or they would have exported the data from Confluence before moving the servers. How can I override the user configuration to get into the database and export the data?

Thanks.

[Nic Brough -Adaptavist- · Accepted solution]

First step is to get a Confluence admin account to get in - see https://confluence.atlassian.com/doc/restore-passwords-to-recover-admin-user-rights-158390.html

Then you'll be able to change the directories around.  I'm not sure you'll be able to rescue all of it if the JIRA has gone away, but you should at the very least have admin access and a full list of users and groups in the database cwd_user and cwd_membership tables (they cache the remote directory data)

[Alistair Guthrie]

Thanks, Nic. That did the trick. Go knows how long it would have taken me without your help. Although the instructions are written assuming H2, they work fine with HSQLDB.

[Alistair Guthrie]

One more piece of information: v5.6.4 of Confluence uses an HSQLDB rather than an H2 database. Not sure if this will affect the solution or not.