JIRA 4.0 : Backing Up Data
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 database contentsThere 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 toolsAll 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:
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 utilityTo 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. )
2. Backing up attachmentsIf 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.:
|
![]() |
Document generated by Confluence on Oct 06, 2009 00:26 |