This document describes how to migrate/upgrade to JIRA applications on different
server hardware, or perform one or more of the following operations in different server environments:
· The new operating system that will run JIRA applications,
· New location for storing indexes and/or attachments, or
· A new database or database system that will store JIRA application data.
If you upgrade to a newer version of the JIRA application during the migration process, please refer to Upgrading the JIRA Application for information on the prerequisite tasks that need to be completed before the upgrade.
If you change the operating system from Windows to Linux or vice versa, please remember that you need to reverse the "slash" ") in the file path ('/' to'\' or'\' to'/').
1, before starting
· Check License-Confirm that your license support period is still valid.
· Check for known issues-Use the JIRA knowledge base to search for any issues that will affect you in the new version.
· Check compatibility:
· Confirm that your operating system, database, other applicable platforms and hardware still meet the requirements of JIRA applications.
· Ensure that the source and target instances are initially set to have the same time zone to avoid problems with date and time fields.
· If you have installed the JIRA application accessories (that is, the JIRA application is not included), please verify that they are compatible. You can find compatibility information for add-ons on the add-on homepage on Atlassian Marketplace. You can also follow the steps described here: Check for additional compatibility of application updates so that Universal Add-on Manager can help you.
We strongly recommend performing migration in a test environment first. Do not migrate production JIRA
server applications until you are sure that the test environment upgrade has been successful.
· If your test environment has any problems that you cannot solve, please create an issue on our support site so that we can help you.
· If you encounter any problems during the migration process of the production JIRA server application, please do not let your users start using this server. instead:
· Continue to use the old JIRA server application-this will help ensure that you do not lose production data.
· At the same time, create an issue on our support site so that we can help you solve the migration problem.
Certain antivirus or other Internet security tools may interfere with the migration and prevent the process from completing successfully. If you encounter or expect to encounter such issues with antivirus/Internet security tools, please disable this tool before proceeding with the JIRA application migration.
2, backup
2.1, prevent users from updating JIRA data
During the upgrade process, you will export the JIRA database from the existing JIRA installation (via an XML backup), and then restore this backup to the new JIRA installation. In order to ensure that the data in the XML backup is consistent with the latest data in the system, you must temporarily restrict access to JIRA so that users cannot update the data. For more information, see Prevent users from accessing JIRA applications on the backup page.
Be careful! Inconsistent XML backups cannot be restored!
2.2 Backup your database
Perform an XML backup of the external database of the existing JIRA installation. For large JIRA installations, this process may take several hours to complete.
"Embedded Database" is an H2 database provided by JIRA, which is for evaluation purposes only. If you accidentally use the H2 database in the production system, perform an XML backup of this database and continue this process.
2.3, backup your JIRA home directory
1. Close JIRA.
2. Find the JIRA main directory.
You can find information about the location of the directory by navigating to the <jira-application-dir> /WEB-INF/classes/jira-application.properties file in the JIRA application installation directory. Or, you can open the JIRA configuration tool to view the directory set as your JIRA homepage.
3. Navigate to the directory specified in the configuration file and create a backup of it in another directory.
4. Once the backup is complete, delete the file <jira-home>/dbconfig.xml from the original folder.
2.4. If it is located outside the JIRA main directory, please back up the attachment and index
If the attachment and index directories are outside the JIRA home directory, they must be backed up separately. These pages describe how to find out where these directories are in your implementation:
· Your attachment directory-please refer to the "Configuration File Attachment" page in your JIRA version document.
· Index Directory-Please refer to the search index page in the documentation of your JIRA version.
For more information about backing up attachments in JIRA, see also Backing up data.
2.5, backup your JIRA installation directory
"JIRA installation directory" is the directory where JIRA application files and libraries are extracted when JIRA is installed.
3, set up a new JIRA application installation
If you are running a "mission critical" JIRA server application, we strongly recommend that you perform the remaining steps of this guide in a test environment (for example, use a separate test JIRA application database and a copy of the JIRA application home directory). Upgrade for production use .
3.1, install the new version of the JIRA application
First, you must start with a new installation of the JIRA application, whether it is the current version or the new version. If you are upgrading a JIRA application during this process, please refer to Upgrading a JIRA application for information on the prerequisite tasks that need to be completed before upgrading.
Download and extract the JIRA application you need to a new directory. Do not overwrite your existing JIRA application installation. Make sure it is closed and install the new JIRA application version to the new location.
3.2. Point your new JIRA application to your existing JIRA application home directory (a copy)
If your new JIRA 7.1 installation is on a new server, please copy a backup of the existing JIRA home directory from the old server to the new server before proceeding.
Set allocation:
1. Open the JIRA configuration tool.
2. Click the JIRA homepage tab.
3. Update the JIRA main directory field:
· If your JIRA 7.1 installation is on a new server, please update the JIRA home directory field to the path of the copied JIRA home directory.
· If your JIRA 7.1 installation is on the same server, please update the JIRA home directory field to the path of the existing JIRA home directory.
You can also set the location of the JIRA home directory by defining the operating system environment variable JIRA_HOME. This value of this variable takes precedence over the value of the jira.home property in the jira-application.properties file in the JIRA installation directory.
3.3, connect the new version of the JIRA application to a new empty database
Create a new, empty database, the new JIRA installation will be used to store its data.
Follow the instructions of "Connect JIRA to..." related to the database in the second stage. Although starting from the fourth stage, please pay attention to the following yellow precautions:
If you use a database in an existing JIRA installation (for example, called jiradb), and the database of the new JIRA installation runs on the same machine or database server, you can create a new database with a different name (for example, intuitively similar to jiradb_440 JIRA 4.4.0). However, make sure that the new database has the same access permissions as the old JIRA database. If you need help, please consult your database administrator.
If you are using an embedded H2 database, you do not need to create a new database.
