Restoring information from a native backup
Before you begin
Make sure that you have the password to a login in the backup file that has the JIRA System Administrator global permission. Once the restoring procedure begins, all the existing data in the JIRA application database is deleted, including all user accounts.
If you are restoring data from a JIRA Cloud application site to a JIRA Server application, please read Migrating from JIRA Cloud to JIRA Server applications.
|For all of the following procedures, you must be logged in with JIRA Administrators global permission.|
1. Disable email sending/receiving
If you are restoring production data into a test JIRA instance for experimentation purposes, you have to disable all JIRA application's email features before you begin:
- Disable email notifications — if JIRA is configured to send emails about changes to issues, and you want to make test modifications to the copy, you should start JIRA with the
- Disable POP/IMAP email polling — if JIRA is configured to poll a mailbox (to create issues from mails), you will have to disable polling on your test installation by setting the
Exactly how to set these flags is dependent on your particular application server, but for JIRA, this is done by setting the
DISABLE_NOTIFICATIONS environment variable before starting JIRA (note, use
startup.sh instead of
startup.bat if you are not using Windows):
You could also try un-commenting the
DISABLE_NOTIFICATIONS=" -Datlassian.mail.senddisabled=true -Datlassian.mail.fetchdisabled=true -Datlassian.mail.popdisabled=true" line from your
/bin/setenv.bat file (
/bin/setenv.sh if you are not using Windows) and then running startup.
- Stop JIRA
- Replace the JIRA Home directory with the backed up files.
Re-apply any changes made in the JIRA Install directory
This step is required only if something has changed since the backup, it shouldn't contain any actual data.
- Restore the database using native database tools (again this depends on the specific database type)
- Start JIRA