As part of a major Data Migration exercise, we are planning to migrate a client's Jira installation from it's current environment: Jira Enterprise 4.1 (Build 519)/SQL Server 2008/Windows 2003 SP3 to a new environment Jira Enterprise 4.1 (Build 519)/SQL Server 2008 R2/Windows Server 2008 R2.
We WILL NOT be upgrading the Jira version at this time and so we plan to backup the SQL database & attachments folder & then restore onto the new server and configure Jira appropriately.
Are there any known issues with this approach?
We did the same last year, not a single problem. Jira 4.2.4 on Win 2003 SP3 to Jira 4.2.4 on Win 2008 R2. The MS-SQL server DB also moved from SQL 2005 to SQL 2008.
Being MS-SQL just make sure you stick to the jTDS drivers and don't even go near the Microsoft JDBC drivers, they are slow & buggy & prone to deadlocks.
I presume the new Jira host environment is 64bit? If so you may run into trouble when you try & install & run it as a service. It's a known problem with the services wrapper. Here are some instructions on where to get a version compatabile with 64 bit. It's not a difficult thing to do so I am a little surpised that Atlassian haven't a working 64-bit version.
You can use either the 32 or 62 bit JDK but it makes sense to go with the 64 bit version.
Apart from that follow the instructions in Jobin's link in his answer
At Atlassian, we believe in our own products – that's why we use them, even at the enterprise level. Doing so gives us first-hand experience of how they perform at scale; to do this, we monitor each ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs