Switching databases
Jira's data can be migrated from one database to:
- A different database on the same database server,
- The same database type on a different server (e.g. from one PostgreSQL server to another PostgreSQL server) or
- A different type of database server (e.g. from a MySQL server to a PostgreSQL server).
You can migrate Jira's data by:
- Migrating Jira's data to the same type of database (covers scenarios 1 and 2 above)
- Migrating Jira's data to a different type of database server (covers scenario 3 above)
If you are planning to migrate to an Amazon Aurora database, you can also review their documentation for additional advice. See Additional AWS resources for Amazon Aurora below.
For migrating Jira to another server, see Migrating Jira to another server instead.
Known issues
Migrating Jira's data to the same type of database
Use this procedure to migrate Jira's data to:
- A different database on the same database server, or
- The same database type on a different database server (e.g. from one PostgreSQL server to another PostgreSQL server).
To migrate the data:
- Use your database server's native tools to either:
- Copy your Jira database to a new database on the same database server installation, or
Copy/migrate your Jira database to a new database of the same type on a different database server installation.
- If you are unable to do either of these tasks, use the Migrating Jira's database to a different type of database server procedure (below) instead.
- You could use this procedure to migrate Jira's data to a different type of database server (e.g. MySQL to PostgreSQL). However, you would need to find tools that support these processes. Furthermore, Atlassian does not provide support for this strategy.
- Once your new database has been populated with Jira's data, shut down your Jira server.
- Make a backup of your Jira home directory and Jira installation directory.
- Reconfigure your Jira server's connection to your database:
- If you installed a "Recommended" distribution of Jira, you can use the Jira configuration tool (by running
bin/config.sh(for Linux/Solaris) orbin\config.bat(for Windows) in your Jira installation directory), which provides a convenient GUI that allows you to reconfigure Jira's database connection settings. - If any of the following points applies to your situation, you need to manually configure the
dbconfig.xmlfile in your Jira home directory. Refer to the appropriate database configuration guide in the Connecting Jira to a database section for the manual configuration instructions.- You have a console-only connection to your Jira server
- You would prefer to configure your database connection manually (for custom configuration purposes).
- If you installed a "Recommended" distribution of Jira, you can use the Jira configuration tool (by running
Migrating Jira's data to a different type of database server
Use this procedure to migrate Jira's data to a different type of database server (e.g. from a MySQL server to a PostgreSQL server).
You can also use this procedure if your Jira installation is currently using the internal H2 database (which is only supported for evaluating Jira) and you need to switch your Jira installation across to using a supported database (which are supported for Jira installations used in a production environment).
To migrate Jira's data:
- Create an export of your data as an XML backup. See Backing up data for details.
- Create a new database on your new database server to house Jira's data. See the appropriate database configuration guide in the Connecting JIRA to a database section for the database creation instructions.
- Shut down your Jira server.
- Make a backup of your Jira home directory and Jira installation directory.
- Delete the
dbconfig.xmlfile in your Jira home directory. - Restart Jira and you should see the first step of the JIRA setup wizard for configuring your database connection.
- Configure Jira's connection to your new database (created in step 2 above) and select the Next button.
- On the Application properties setup page, click the Import your existing data link and restore your data from the XML backup created in step 1 above.
Additional AWS resources for Amazon Aurora
Modular Architecture for Amazon Aurora PostgreSQL: a Quick Start that guides you through the deployment of a PostgreSQL-compatible Aurora Database cluster. This cluster has one writer and two readers, preferably in different availability zones.
Upgrading the PostgreSQL DB Engine for Amazon RDS: shows you how upgrade your database engine to a supported version before migrating it to Amazon Aurora.
Migrating Data to Amazon Aurora PostgreSQL: contains instructions for migrating from Amazon RDS to a PostgreSQL-compatibleAmazon Aurora cluster.
Best Practices with Amazon Aurora PostgreSQL: contains additional information about best practices and options for migrating data to a PostgreSQL-compatible Amazon Aurora cluster.
Amazon also offers an AWS Database Migration Service to facilitate a managed migration. This service offers minimal downtime, and supports migrations to Aurora from a wide variety of source databases.