Jira Data Center Migration(Windows to Linux)

[Bhupesh Nagda]

hi All

We have Jira(8.11) and Confluence(7.13.1) applications installed on Windows Server 2012 R2 that we plan to migrate to AWS on Data center with clustering.

Since AWS is hosted on linux environment so it would mean a windows to linux migration as well. Currently we use MS SQL database and we want to use Postgres or Oracle once we migrate

I am finding it hard to plan this migration sequentially so that eveyrthing is covered end to end and in proper flow with less rework. Does anyone has any suggestions on best practices to around it.

We are a huge instance with 400000 issues and around 5k users.

Any suggestions would be appreciated

[Thomas Deiler]

Dear @Bhupesh Nagda ,

seems not to be a big deal - means no rocket science. All you need from your windows Jira installation is

• XML dump create by Jira Backup function
• %JIRA_HOME\data directory zipped archive

Set up your new instance on AWS, first with a single node. A good entry point could be this article.

When the instance is setup, you are asked to restore from XML. Now use your file from windows. Copy the /data files to the new location.

• Depending on the current license type - you need to renew it.
• Base URL needs adapted
• when External User Directory was configured, you need to reconfigure this from AWS.

It's similar with Confluence.

So long

Thomas D

[Bhupesh Nagda]

Thank you for the answer! please bear with me for a few more questions since this is going to be my first windows to linux migration, hence a bit nervous so want to plan in sequentially.

So I have requested the new EC2 instances. I understand that you are suggesting to go ahead with non-cluster installation and them migrate:

Jira data using xml dumps, would it take care of the attachments ? How would you recommend database migration from SQL Server to Postgres, I mean would it be best if we migrate to Postgres on windows only and them to linux ?

So I am planning like this:

Current Environment:

1.       License Type: Server
2.       OS: Windows
3.       Database: MS SQL Server

Desired Environment:

1.       Required License Type: Data Center
2.       Desired OS: Linux
3.       Desired Database: PostgreSQL

Out of above 3 changes License Type migration is most prior. Based on that I am planning below approach, please provide your feedback:

1.        We request a Windows Server instance in AWS with similar or slightly better configurations.
2.        We get the IP and other network details before hand for the for raising port opening requests database and external tools integration like Bamboo, Bitbucket other tools integrated via API.
3.        We raise DNS , certificates etc, in case if new URL is needed or just migrate the existing if current DNS is fine.
4.        We get standalone windows instance in AWS with MS SQL Server Database.
5.        We plan and execute the migration(weekend should be enough) without clustering.
6.        Once we finish with Data Center migration we can plan 2 and 3.
7.        We can then plan with Database migration. We can also do this step now and perform data center migration with PostgreSQL as backend(this would avoid reprovisioning of database server)
8.        Finally we migrate to Linux OS. This is again going to be a huge project involving new servers but can be planned without timeline pressure. We then enable clustering on Linux environment in AWS.

Now, i am not sure if this is the best way

[Thomas Deiler]

Dear @Bhupesh Nagda ,

when you save the 'data' directory on windows, you have all attachments. Don't think too much on DB migration - Jira does this for you. All you need is the XML dump (Backup) Jira produces. This can be taken to restore the data to any supported database type.

You do not need to go over Windows on AWS. Jira does not interest in the operation system. When you import your XML dump on Linux AWS (single node), the license of your server is imported, too.

1. Create AWS Linux environment
2. Install Jira
3. Configure PosgreSQL
4. Import the Dump
5. Copy data directory (with attachments) to proper location
6. Adapt the installation to the new environment (BaseURL, etc )
7. Verify installation
8. Re-Index
9. Replace Server License with new DC license
10. Configure first node to run clustered
11. Add more nodes

So long

Thomas