Need help in migration to a new server with MySQL 5.7 DB ( Aurora)

[Transity Technologies]

Editing the original question.  

 I have a jira installation of version : JIRA Software 7.3.6 ( server ) which is being used by my company. The database used is 5.6.33-0ubuntu0.14.04.1.

I have a mandate to move the installation of JIRA Software to a new machine and new db ( Aurora MySQL 5.7)

How do I accomplish this ? What is the best practice here.

I tried to do it ; end result is a broken jira instance at the new machine. 

[Dave Theodore [Coyote Creek Consulting] · Accepted solution]

You didn't state what version of Jira or database you are starting out with, so it's a bit difficult to answer with much accuracy.  I gather you have discovered that Jira supports a range of versions of MySQL and as the version of Jira gets more recent, so do the requirements for the associated database version.

If I assume that you want to move to the latest version of Jira (7.13.0 as of today) we can see that MySQL 5.5 -> 5.7 are supported. 

You will need to research the upgrade procedure for Jira to go from the version you are on to the version you want to go to. You may be able to go directly or you may need to do one or more intermediate steps to get to the latest version.  This all depends on what version you are starting on. The intermediate version(s) that you need to upgrade to in order to get to the latest may have MySQL version requirements that are lower than the latest version.  Given that 5.5 has been supported for a long time and is supported on the latest version, I would expect the least database headache in moving to this version and kicking the can down the road on the 5.7 upgrade.

[Transity Technologies]

Dave.. thank you very much for your help . I was able to install and Jira is running successfully in the new server. I have an issue with users not able to login to Confluence after migration. I have tried few solutions suggested but was unable to rectify the situation.

I have raised another issue. 

[Transity Technologies]

Sorry to be so short on specifics

1. I have a jira installation of version : JIRA Software 7.3.6 ( server ) which is being used by my company. The database used is 5.6.33-0ubuntu0.14.04.1.

I have a mandate to move the installation of JIRA Software to a new machine and new db ( Aurora MySQL 5.7)

How do I accomplish this ? What is the best practice here.

I tried to do it ; end result is a broken jira instance at the new machine. 

[Dave Theodore [Coyote Creek Consulting]]

Got it.  That's pretty easy, then.  I would set up a fresh empty Jira 7.13 instance on the new server and connect it to the MySQL 5.7 database.  Verify that it's running happily and there are no errors.

During a change control, perform an XML backup of your Jira 7.3.6 instance. There is some chance that Jira will run out of memory when you do this, so I recommend only running the XML backup under a change control. Once that is complete, you can copy the data to the new server.

1. Locate the XML dump that you just did and copy it over to the new server.  
2. Shut down the new Jira 7.13 instance and rsync over the contents of (only) the data directory in your Jira 7.3.6 home directory.
3. Move the XML dump in to the import directory in Jira 7.13's home directory.
4. Start up Jira 7.13
5. Navigate to the Backup and Restore section of the admin interface and choose  "Restore System."
6. Select the XML dump and click "Restore."
7. Install the 3rd party Apps that you had on the 7.3.6 instance.  

I'd recommend doing this in a Dev environment before doing it in production.  Be sure to disable email in Dev! You don't want to spam people and confuse them or have your email handlers mail going in to the wrong instance.

I hope that helps

[Transity Technologies]

Thank you for your detailed email. I did not understand 

2nd point : syncing the content of data directly in jira 7.36 home directory.. What does it mean. 

I did try the procedure that you described but it gave me lot of errors while importing - I had to delete lot of tables to get the import going, during restore.