Backup and Restore
When setting up your Confluence site, it's important to consider how you will back up your data, and restore it, if needed.
Recommended backup strategy
Having a robust backup strategy for your Confluence site is essential. You should back up your database, installation directory, and home directories (including attachments) on a regular basis using the database administration or backup tool of your choice.
See Production Backup Strategy
Manual XML backup
You can export your entire site or selected spaces at any time. The backup will be generated as a zipped XML file.
See Backup a Space or multiple Spaces
Scheduled XML backup
Since Confluence 8.3, we have changed the way we do backup and restore. Learn more about these changes in the Confluence 8.3 Release Notes.
In Confluence 9.0, we removed the legacy backup and restore system. This means that scheduled backups, which used our legacy system, are no longer available.
For regular backups of production instances, use your database’s native backup tools. You may also use the backup/restore API to create XML backups, but make sure you move all backup files to a dedicated secure storage for security and redundancy purposes.
Native database backup tools offer a much more consistent and reliable means of storing (and restoring) data while Confluence is active. When Confluence is in use, there’s no guarantee that XML backups will be consistent as the database may be updated during the backup process.
Restoring your site from a backup
In the event you need to restore your site from a backup, the way you do this depends on your backup method.
- See Restore a Site to find out how to restore data from an XML backup into an existing Confluence site.
- See Restoring data from other backups for tips on how to restore Confluence from a database backup.
Version compatibility
- You can restore space XML backups to the same or newer versions of Confluence. For example, a space XML backup generated in Confluence 8.3 can be imported to Confluence 8.3 or later. Learn more about space restore
We strongly recommend restoring site XML backups to the same version only to avoid issues with incompatible plugins and features. Learn more about site restore
- You can't restore XML backups to earlier versions because backward compatibility isn't supported.
XML backups must not be used to upgrade Confluence. Upgrade Confluence by following Upgrading Confluence.
Recent backup and restore activity
View details about backup and restore tasks that have been run on your Confluence site over the last two weeks at Administration 
> General Configuration> Backup and restore. This list includes space backups generated in Space tools but excludes backups generated by scheduled backups.
The recent activity table provides an overview of:
task type (space backup, site backup, space restore, or site restore)
file name of the zip file
task status
user who created the task, and
date the task was created.
Screenshot: Backup and restore admin screen
Select the file name to find out more details about a specific job. This will take you to the Task details page. The below table describes what information is available on this page.
| Task detail | Description |
|---|---|
| File name | The name of the XML backup or restore file. For backups, you can select the file name to download a copy of the XML within 72 hours of exporting it (this is the default setting). If you chose to save permanently, the download link will not expire. |
| Status | This could be in progress, queued, canceling, canceled, failed, or completed. See below for more details on the queued and failed statuses. |
Spaces Space backup and restore only | It is the number of spaces contained within your XML space backup or restore zip file. |
| Records processed | This is the number of objects processed. Objects are the different records from the database related to your space or site. |
| Queue time | This is the amount of time your task was in the queue before it started processing. Learn more about the queued status below. |
| Time elapsed | This is the amount of time your task took to run until it was completed, canceled, or failed. Time lapsed doesn't include queue time. |
| Attachments | This specifies whether attachments have been included in your backup. Space backups will always include attachments. |
| Created on | This is the date and time the backup or restore task was created. |
| Created by | This is the user who created the backup or restore task. |
Delete scheduled Backup only | This will only appear for backups that haven't been saved permanently. It is the date the XML backup zip file is scheduled to be deleted from the server. By default, this is 72 hours after the backup was created. |
Records skipped Restore only | This is the number of records that were skipped while importing your site or space. Records can be skipped for a variety of reasons, and when they're skipped it doesn't always represent an error or data loss. If you suspect you're missing data from the restore, check the main application log to audit objects that were skipped. |
| Errors | This is a summary of the issues or errors found during the task. If you need more information about the issue or error, refer to the main application log. |
Queued status
We only process one task at a time to provide a stable and fast backup and restore experience. That means, your task will be placed in a queue when there is another in progress, or if you created the task during a rolling upgrade.
If your task was queued, and someone restarts Confluence, your task will keep its spot in the queue.
Failed status
A back up and restore will fail if someone restarts Confluence while your task is in progress. In this case, you'll need to run the task again.
A restore also fails if you try to import a file that doesn't match your job, for example, importing a site backup when running a space restore.
Migrate to Confluence Cloud
If you're migrating from Confluence Server to Confluence Cloud, you can use the Confluence Cloud Migration Assistant to migrate your content and spaces.