Documentation for JIRA 4.4. Documentation for other versions of JIRA is available too.

Skip to end of metadata
Go to start of metadata
Icon

For production use, it is strongly recommended that for regular backups, you use native database backup tools instead of JIRA's XML backup service.

When JIRA is in use, XML backups are not guaranteed to be consistent as the database may be updated during the backup process. JIRA does not report any warnings or error messages when an XML backup is generated with inconsistencies and such XML backups will fail during the restore process. Native database backup tools offer a much more consistent and reliable means of storing (and restoring) data.

(warning) The information on this page does not apply to JIRA OnDemand.

If you perform an XML backup (e.g. when upgrading JIRA via a test environment or migrating JIRA to another server), you can follow one of these methods to prevent users from accessing JIRA and minimise inconsistencies in the backup file:

  • Recommended method:
    • If you have an Apache or other web/proxy server sitting in front of JIRA, then you can stop Apache from proxying to JIRA, and serve a static HTML page with a nice message along the lines of "JIRA is undergoing maintenance". Note:
      • The administrator must be able to access JIRA directly (not through Apache) to perform the XML backup.
      • This method does not require JIRA to be restarted.
  • Alternative method 1:
    1. Shut down JIRA, configure it to listen on a different port and restart. For JIRA Standalone, you would do this by editing the server.xmlfile. Change the following section:

      • Note: If you have enabled HTTPS, then you would need to edit the HTTPS Connector section as well.
    2. Restart JIRA and do the XML backup.
    3. Shut down JIRA, change all the settings back, then re-start JIRA.
  • Alternative method 2:
    • If you have a firewall in front of JIRA, you could stop requests from getting through or change the port number that it uses. Note:
      • The administrator will need to log in to JIRA on the temporary port number (or access it from behind the firewall), to perform the XML backup.
      • This method does not require JIRA to be restarted.
  • Alternative method 3:
    • In your database server, remove 'write' permissions from the database user (e.g. jirauser) that JIRA uses.
      • Users will be able to read but not update issues during the backup.
      • This method does not require JIRA to be restarted.

Before you start:

Icon

Whichever method you choose, we recommend setting an Announcement Banner to warn your users that JIRA will be unavailable for a period of time.