nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Migrate and Update JIRA

NickW

I am looking at creating a fresh installation of JIRA on a VM that has more resources available. In doing this I also want to move from 6.0.4 to 6.2.

Is it OK to to do the database export as listed in the online documentation from one version and then import it in to the new version?

Or would it be best to install a fresh 6.0.4 system and import into that and then do the upgrade?

Is there anything else I need to watch out for?

Cheers

Nick

Accepted answers

EddieW_h8oivr

In general Atlassian suggests migrations should occur on the same OS, but may include compatible upgrades. The filesystem depends on the OS, and even minor versions will include DB upgrade tasks.

https://confluence.atlassian.com/display/JIRA/Migrating+JIRA+to+Another+Server

https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA

The process you are describing is essentially identical to the upgrade process (assuming similar OS). And if your keeping the same DB, very easy.

Shutdown JIRA on server
Backup home, install and db
Move home to new server
Run new JIRA on new server. If the DB connections are the same, and it can find the home path, it will upgrade in place.

DId I mention to back everything up first?

All comments

Tarun Sapra

Hi Nick,

The upgrade process should be semmless because you are migrating within the same major JIRA version

Is it OK to to do the database export as listed in the online documentation from one version and then import it in to the new version?

Yes, i think the above approach should be fine. Only thing you need to be carefeul about is the plugin compatibility.

Tarun Sapra

Just make sure you thoroughly test all the plugins on the updated version on a test machine before making the actual move.

EddieW_h8oivr

In general Atlassian suggests migrations should occur on the same OS, but may include compatible upgrades. The filesystem depends on the OS, and even minor versions will include DB upgrade tasks.

https://confluence.atlassian.com/display/JIRA/Migrating+JIRA+to+Another+Server

https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA

The process you are describing is essentially identical to the upgrade process (assuming similar OS). And if your keeping the same DB, very easy.

Shutdown JIRA on server
Backup home, install and db
Move home to new server
Run new JIRA on new server. If the DB connections are the same, and it can find the home path, it will upgrade in place.

DId I mention to back everything up first?

Andris Grinbergs

You can migrate/clone database with DB tools, copy jira home, install jira 6.2, point it to copied home, and change dbconfig.xml to clonned database. After jira startup update plugins. Should be fine, but test first. Be aware of automated email notifications from new instance.

EddieW_h8oivr

Your comment is misleading. Major and minor have nothing to do with potential database impacts. Upgrade tasks can be bundled in any release.

NickW

Hi Andris

You make it sound simple.. Thanks for the tip of regarding e-mails and notifications

Nick

NickW

Hi Eddie

Thanks for this. The reason for doing the migration though is to change the OS. Originally the system was a samll local one which has now grown to be used by many people. It is currently on a VM Win7 box and I was looking at moving it to Win Server 2012 R2 - more robust/memory/cCPU cores. As I mentioned the only other change was to upgrade the JIRA version. I was planning on sticking with MySQL.

I assume when you wrote 'similar OS' you meant sticking to Windows rather than say wanting to go from Windows to Linux...

NickW

Thanks Tarun... the next stop will be checking plugin compatability

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

migration

upgrade