Restoring data from an xml 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 -Datlassian.mail.senddisabled=true flag.
  • 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 -Datlassian.mail.fetchdisabled=true flag.

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 instead of startup.bat if you are not using Windows):

set DISABLE_NOTIFICATIONS=" -Datlassian.mail.senddisabled=true -Datlassian.mail.fetchdisabled=true -Datlassian.mail.popdisabled=true"
cd bin

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/ if you are not using Windows) and then running startup.

2. Restore the XML data

If you've used native database tools to back up your data, the restore process will be tool-specific and The stage 2 and 3 of these instructions don't apply to you.

  1. Choose > System
  2. Select Import & Export > Restore System to open the Restore JIRA applications data from Backup page.
  3. In the 'File name' field, type the file name of the zipped XML backup file generated by JIRA.
    (info) Ensure that this backup file has been moved or copied to the location specified below this field.
  4. The Index Path field indicates where JIRA will restore the search index data from the zipped XML backup file. This location (which cannot be modified) matches the index path specified in the zipped XML backup file. If, however, this backup file does not specify an index path, JIRA will restore the search index to the caches/indexes subdirectory of the JIRA application home directory.
    (warning) Please Note:
    • The contents of the index directory may be deleted by the restore process.
    • The index directory should only contain JIRA index data.
  5. Click the 'Restore' button and wait while your JIRA data is restored.
    (info) Once the data has been restored, JIRA will inform you that you have been logged out. This happens because all JIRA users which existed in JIRA prior to JIRA's data being restored will have been deleted and replaced by users stored in the JIRA export file.

(info) It is recommended that you avoid passing through a proxy when performing an XML restore, especially if your JIRA instance is very large. Using a proxy may cause timeout errors.

3. Restore the attachments

If you created a backup of the attachments directory, you will need to restore the backup into a directory where JIRA can access it.
(warning) If you use a custom directory for storing your attachments, ensure that JIRA has read and write permissions to this directory and its subdirectories.

The process of restoring the attachments backup depends on the way it was created. Usually you can use the same tool to restore the backup as the one that was used to create it (see Backing up attachments).

If you are restoring the attachments into a different location (i.e. a different directory path) from where they were previously located (e.g. this will be the case when moving servers), please follow the instructions provided in Configuring file attachments to change the location of the attachments directory so that JIRA can find the restored attachments

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport