Make a backup of your database, and your $JIRAHOME directory before you try this upgrade. While the steps you purpose here are what we call the rapid upgrade method. It is typically the fastest way to upgrade, but it's also the most likely to hit snags in regards to older plugins that can't run in newer jira versions without an update. You can certainly still do this, but if Jira should fail to startup upon upgrade, you will want to check the logs to get a better idea as to why that might be ( $JIRHOME/log/atlassian-jira.log and/or $JIRAINSTALL/logs/catalina.out )
Personally I prefer the Upgrading Jira applications with a fallback method. It takes longer to do, more time to setup, but has a very clear fallback should your upgrade not go as expected. For a production instance of Jira, it's usually recommended to do it this way just to help keep your users happy and less aware of downtime for the application. Upgrading Jira can go smoothly, but it can also sometimes be a nightmare.
In this case you're upgrading from Jira 7.5.2 (JSD 3.8.3) up to Jira 7.11 (JSD 3.14). I would recommend checking out the Supported platforms for Jira 7.11 before doing this upgrade. This can help you to make sure that your new version of Jira can still work with your database type/version. It is possible that Atlassian might have ended support for older database versions like MS SQL 2008, or Postgres 9.2 in this or prior versions. If you find yourself on such a database version, I would recommend migrating your data to a supported database before trying this upgrade.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.