Preventing users from accessing JIRA applications during backups

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

When JIRA applications are in use, XML backups are not guaranteed to be consistent as the database may be updated during the backup process. JIRA applications do 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.

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

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

            <Connector port="8080"
                  maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" useBodyEncodingForURI="true"
                  enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" />
      • Note: If you have enabled HTTPS, then you would need to edit the HTTPS Connector section as well.
    2. Restart all JIRA applications and do the XML backup.
    3. Shut down all JIRA applications, change all the settings back, then re-start the applications.
  • Alternative method 2:
    • If you have a firewall in front of your JIRA applications, you could stop requests from getting through or change the port number that it uses. Note:
      • The administrator will need to log into your JIRA applications on the temporary port number (or access it from behind the firewall), to perform the XML backup.
      • This method does not require JIRA applications to be restarted.

Before you start:

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

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