Recovery problems
Asked by sacridias:

I have followed several methods of recovery, but have had issues in all cases.  

I wanted to upgrade my database to MySQL 8, so I backed it up and upgraded.  
As it is unsupported it broke. So I ended up reinstalling MySQL 5.7 and restoring from the backup.

It was setup in the first run to authenticate with Jira.   
After the restore, I could not log in.  

I had lots of trouble trying to get everything working again, so I reinstall Ubuntu 18.04.  

I got everything working, however I did not want to mess things up, so I spun up a new server on my computer (Windows 10). And loaded the backup.  

I tried the fix where you change your environment, had several challenges with that, having to move it out of Program Files. After moving the -Datlassian.recovery.password=password to various parts of the file and the services spin up files. I was still unable to rectify the situation.  

So I tried to try the method prior to later version (where you change the database).  

I tried the provided password, but noted that the existing password hash was not even close to the same. So I copied my new password in the linux server to the windows server.  
Still no dice.  

Most of the stuff I can recreate, however there are few things that I really need out of there, so anything to get that stuff back would be helpful.  

Thanks.


Answers:
author: Ismael Jimoh
body: Hi [@sacridias](/t5/user/viewprofilepage/user-id/707770)

The above is a bit confusing to me so I will just ask for some clarification.

Do you mean you want to know what is the best practise for backup recovery or you mean you would like to recover the current backup or you want to know how you can replicate the problem you had on your Windows server and then fix it?

There is one key problem I see here which is, I would recommend taking a JIRA backup if switching databases or switching server type.

I know JIRA is just a JAVA application however with the amount of dependencies especially if you have add-ons, it is difficult to say what could go wrong.

If you have to use the database migration method though, then migrate to the same database version and jira version you have on the Linux server.

As for the password problem, what error is thrown?

This would greatly help us in understanding why it is failing.

* If the data is sensitive and you cannot provide it then I will recommend reaching out to the Atlassian support as they would also be able to help here.

Regards.

comments: author: sacridias
body: I ended up resolving this by hacking around a bit. I am not sure how the seeds are generated for the database, but I ended up editing the configuration for the new site to point to the recovery database and changing the password in the recovery database, which worked.   

The biggest problems I see is that the instructions for database recovery are for older versions. The instructions for newer versions are not detailed enough.  

It does not specify types of servers, and the put "-Datlassian.recovery.password=password" in the environment script is vague at best, resulting in not working.  

Apparently windows has other problems, so it is also possible that when I moved my recovery to linux that had something to do with it.  

The error I was getting was wrong username/password.


Tags: confluence-server

server