Migrate SQL to PostgreSQL

[Raj]

Hi All,

I am new to Jira and current Jira DC version 8.20.8 we are using with SQL 2019. Current application servers are setup using archive (TAR) file.

Now we are planning to migrate to new servers including app and database (migration to PostgreSQL). Is it ok to setup new app servers with "Install Jira using an installer" option?

Also what is the best way to migrate to PostgreSQL and to new app servers? Thanks in advance.

[Dirk Ronsmans · Accepted solution]

Hey @Raj ,

In addition to @Fabio Racobaldo _Herzum_ 's documentation this should help you out too

https://confluence.atlassian.com/adminjiraserver/switching-databases-938846867.html

In short you'll have to set up a new DB on the new technology and then perform an XML backup/restore within Jira (as there is no way to convert between database technologies directly)

[Raj]

Thanks @Dirk Ronsmans . This means no action on database side. Just setup new DB technology and do a XML restore in Jira (Update dbconfig.xml with new db connection name) right?

[Dirk Ronsmans]

correct!

[Raj]

Also current app servers are setup using Archive file (TAR).. Can i setup my new servers with Installer mode... or it has to be setup in same mode for XML backup/restore to work?

[Dirk Ronsmans]

They way you set up your Jira is of no concern. Once installed it will be the same just a different way of installing it.

[Raj]

Thanks again.. one more question, sorry to ask

What about the jira-shared-home directory (shared drive which stored attachments)? do i need to copy and restore to new drive?

[Dirk Ronsmans]

If you switch servers you'll have to either copy the attachments over to the new directory or if it's a share somewhere, point to that share in your config file.

Attachments will not be included in the XML backup, that's just the issue data.

You could also do this in a phase approach to avoid issues.

Perhaps first move to PostgreSQL on your current servers and then move the instance? Or set up a new Jira with the old DB architecture (could be a different DB that was restored) and then switch?

That might avoid multiple points of failure.

[Raj]

Current setup is Jira app with SQL database and shared drive for attachments

I thought of doing below:

1. First setup brand new Jira instance(multiple servers/cluster) and PostgreSQL as backend
2. Take XML backup of old jira instance
3. Restore attachments to new shared drive
4. Import XML backup to new Jira instance

Is this a good approach? No need of doing a DB restore if understood correctly. Once XML import is done, data will be updated to new PostgreSQL database?

[Dirk Ronsmans]

Sounds good to me. This way you still have your old system to fall back on if something goes wrong.

There is indeed no need to restore a DB, the XML import will inject it in to your PostgreSQL DB

[Dan Vink]

I did everything above but I lose permissions in service desk projects. Has anyone come across this?

[Fabio Racobaldo _Herzum_ · Accepted solution]

Hi @Raj ,

here an useful how-to guide for that https://confluence.atlassian.com/adminjiraserver/migrating-jira-applications-to-another-server-938846962.html

Hope this helps,

Fabio

[Raj]

Thanks @Fabio Racobaldo _Herzum_ 

[Fabio Racobaldo _Herzum_]

You're welcome @Raj