Documentation for JIRA 4.0. Documentation for other versions of JIRA is available too.
For medium to large databases, backing up JIRA data can take a long time, during which it's possible for users and JIRA services to alter the database, possibly resulting in inconsistent data in your backup.
For automated daily backups, there is no solution to this, and it's a good reason to prefer native database backup utilities, as the documentation suggests.
When exporting an XML backup (e.g. for upgrading), follow one of these methods to prevent users from accessing JIRA:
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" />
HTTPS Connector
section as well.Before you begin
Whichever method you choose, you may want to set an Announcement Banner to warn users that JIRA will be unavailable for a period of time.