This page last changed on May 31, 2009 by alui.

This page describes how to back up your JIRA data, and establish processes for maintaining continual backups. Backing up your JIRA data is the first step in upgrading your server to a new JIRA revision, or splitting your JIRA instance across multiple servers. See also Restoring JIRA data and Restoring a Project from Backup.

Creating a complete backup of JIRA consists of two stages:

  1. Backing up the data in the database
  2. If attachments are enabled, backing up the attachments directory

1. Backing up database contents

There are two possibilities: native database-specific tools, or JIRA's XML backup utility.

For production use, it is strongly recommended to use native database-specific tools. The XML backup is not guaranteed to be consistent, as the database is not locked during the backup process.

Using native database tools

All serious databases come with tools to back up and restore databases (the 'MS' inRDBMS). We strongly recommend these tools in preference to the XML backup option described below, as they:

  • ensure integrity of the database by taking the backup at a single point in time
  • are much faster and less resource-intensive than JIRA's XML backup.
  • integrate with existing backup strategies (e.g. allowing one backup run for all database-using apps).
  • may allow for incremental (as opposed to 'full') backups, saving disk space.
  • avoid character encoding and format issues relating to JIRA's use of XML as a backup format.

See the documentation for your database on how to set up periodic backups. This typically involves a cron job or Windows scheduled task invoking a command-line tool like mysqldump or pg_dump,

Using JIRA's XML backup utility

To perform a once-off backup, e.g. before an upgrade, follow the steps below. (Note that you can also configure scheduled XML backups, as described in Automating JIRA Backups. )

  1. Log in as a user with the 'JIRA System Administrators' global permission.
  2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
  3. Under the 'Import & Export' sub-menu in the left-hand navigation column, click the 'Backup Data to XML' link. This will display the 'Backup JIRA data page:
  4. In 'File name' field, type the full path, including filename, of the location to which you want JIRA to write the backup file. Note: Ensure that JIRA has rights to write to this location.
  5. (Optional but recommended) Select the 'Backup as Zip' checkbox.
  6. Click the 'Backup' button, and wait while your JIRA data is backed up.
  7. When the backup is complete, a message will be displayed, confirming that JIRA has written the data to the file you specified.

2. Backing up attachments

If you have attachments enabled you also need to create a backup of the attachments directory, as the attachments do not get stored in the database. By default, file attachments are stored in the JIRA home directory under the data/attachments sub-directory.

To back up attachments, you need to create a snapshot of the attachment directory (including all files and subdirectories). Note that the directory structure under the attachments directory must be preserved in the snapshot.

Creating this snapshot is an operating system-specific task, e.g.:

  • On MS Windows, a batch script copying the directory can be written and scheduled periodically (Programs > Accessories > System Tools > Scheduled Tasks). There are also various utilities available to simplify this (eg. http://www.picozip.com).
  • On Linux/Solaris, it is best to write a small shell script, placed in /etc/cron.daily , backing up files to a directory like /var/backup/jira . It is best to copy an existing script in /etc/cron.daily to ensure local conventions (file locations, lockfiles, permissions) are adhered to.

Document generated by Confluence on Oct 06, 2009 00:26