I created a test environment by replicating our production environment to upgrade Jira from 7.6.2 to 8.20.1 successfully.
I'm curious about creating a staging environment (creating two new servers for application and SQL database) and installing Jira 8.20.1 then migrating database from 7.6.2 production environment...is that possible or does the upgrade process change things within the database that would require me doing the same for my staging environment that I did for the test environment?
You are upgrading to Jira 8.20.1 not 18.20.1
I see what you are saying, I get it. Will this answer your questions?
You want a higher version of Jira with your pre-existing DB
https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html
Oops, sorry about that...yes I meant 8.20.1 and yes the supported platform page says that 8.20.1 works with SQL Server 2019 which is what I have, just wanted to confirm that if I backup my existing production database that's running on SQL Server 2014 and the Jira application server is on 7.6.2 that I can simply do what I mentioned earlier.
In my new staging environment, I install Jira 8.20.1 and use the previous database on SQL Server 2014 in my new SQL Server 2019.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Based on my experience I will say yes as long as you follow Atlassian Configuration recommendations. Your upgrade will be successful.
Wishing you all the best!
Best,
Fadoua
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I appreciate you, and I've taken backup precautions of course to reverse if it doesn't work and do it the way I know it has, but I'm hoping it works since it's going to save me some time...thanks again!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Migrate your DB first then migrate the application. Don't do both at the same time so in case something doesn't work you know where to start your troubleshooting from.
Also please read Atlassian Release Notes as there are some changes between versions.
There are recommendations regarding DB settings.
Please make sure to go through the docs.
If you have any questions, don't hesitate to ask as I will be more than happy to help.
Best,
Fadoua
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Fadoua in regards to migrating the DB first, yes that's the plan which is what the Atlassian documentation covers even if doing a clean install...the DB first has to be created, etc. then once the application is installed then I can start copying both installation & home directories to new application server, copy over the database, change the dbconfig.xml to point to it, etc.
I've read through everything trust me, when doing this test environment and yes, the new SQL sever is a newer version and I've configured it with all the steps required by the Atlassian documentation, but outside of that my question is would doing these steps work even if the database is being utilized by a version of Jira that is older?
I'm not sure if I'm explaining myself properly, but here is a summary of what I'm planning and want to know if this would be ok:
That's it, my question is basically setting up this staging environment that will become the new production environment, I just need to know if the database part will work this way or would I have to do what I did with my test environment which is upgrade 7.6.2 to newest version due to any DB settings, etc. that would not work if I simply pointed the newest version of Jira to it without going through an upgrade?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.