Migrating production Jira to new AWS instance without new database

[Jacob Gude]

Hello,

We currently have Jira running on a RedHat AWS EC2 instance. There is an issue with the RedHat EC2 instance which will not allow us to run Yum updates, therefore we cannot upgrade Jira because it requires certain pkgs that it can't pull from Yum. Long story short we need to migrate our Jira server to a new EC2 instance. We are using RDS Postgres DB for Jira to connect to. 

All of the documentation I've read says to build install latest Jira, replace Jira Home Directory with backup, create new database, and import xml backup. 

My questions is. I don't want to create a new DB since we have a perfectly fine DB it's utilizing. Can I just shutdown old Jira, move directories to new instance, edit configs and just start it up? 

[Petr Vaníček]

Hi,

if it's not a huge instance then it's usually better to have DB on same server. So just install PostgreSQL and restore data from dump. Then you can try to copy folders and change DB setting in dbconfig.xml in JIRA-HOME folder.

But if you still want to use old DB and server then you must be sure about network settings (like security groups, FWs and pg_hba.conf file).

[Jacob Gude]

Yeah we would prefer to use our RDS DB that's in the cloud. I have all the configs so really it seems I just need to copy in the Jira home directory, edit the files in the install directory to point back to our RDS DB. It's not a big instance. I'll try it this way and see what happens. 

[Joe Pitt]

I suggest taking a backup just before shutting down just to be safe 

[Jacob Gude]

Definitely. I have snapshots of our instance and Database.