Questions with our JIRA Upgrade

[Jonathan Davies]

Hello all,

We are looking to upgrade our JIRA Server instance from v7.0.0 to latest in the production environment but we are looking to test this in our non-production environment first. We also want to upgrade the Windows server at the same time.

Our plan is to:

1) Take a XML backup of the current JIRA v7.0.0 instance which is hosted on a Server 2008 R2 machine

2) Configure a new host which will run on Windows Server 2012 R2 and install the latest JIRA software on there

3) Configure a new empty SQL 2012 database

4) Restore the v7.0.0 XML backup into the new JIRA latest environment

Is this approach possible/recommended?

Regards,

Ajay

[Nic Brough -Adaptavist-]

No, this is not recommended.

What you should do is create a test server that is on 7.0.0 as per production, but using another database of course.  Use the XML to copy production over into that test server (or just duplicate the database).  Then upgrade that 7.0.0 to your target version using the recommended upgrade process (downloading and running the installer).  Once you've tested that process and results, do the same on production.

p.s. please don't use other people's accounts.  Get your own Atlassian account and use that.

[Jonathan Davies]

Ok thanks for the reply.

I will adjust the upgrade plan accordingly.

[Ajay Madar]

hi Nic, you mention above the option to "duplicate the database" across form production into our test environment. How do we use this approach in the setup of our bitbucket test instance? 

We did this and when I pointed the test installation to the replicated database I got the error along the lines of = "The target database contains tables whose names collide with Bitbucket's tables. Please migrate to a clean, empty database."

Regards,

Ajay