Documentation for Confluence 3.4.
Documentation for [Confluence Cloud] and the latest Confluence Server is available too.

Skip to end of metadata
Go to start of metadata

Atlassian suggests establishing a backup strategy using a native database tool for a production instance of Confluence.

By default, Confluence backs up all data and attachments once a day to a backup file. These files are called XML site backups, stored in the backups directory of Confluence home. You can also create XML site backups manually. This mechanism was created with small to medium-sized deployments of Confluence in mind. It is not made for large deployments with lots of pages and attachments (see below)

XML site backups are fine for most small to medium sized instances of Confluence, containing a few thousand pages and attachments. However, large instances of Confluence will find backups may become slow to create and use large amounts of disk space.

Backups For Large Instances

XML site backups are unsuitable for instances of Confluence that contain thousands of pages, as XML backups take progressively longer to complete as the amount of text increases. Another issue with XML site backups is that Confluence instances with a gigabytes of attachments will consume disk space rapidly. This is because each site backup contains all content needed for a site restore. For example, if a 1 gig instance of Confluence is backed up daily, it will create 30 gig of backups per month if left unattended. When administering a large instance, you can reduce disk space by setting XML site backups to exclude attachments, then manually scheduling a backup of your attachments from the Confluence home directory or database. The backup manager can save space by saving changed files instead of all content.

Creation Delay

Disk Usage

Recommended Backup Method

Acceptable

Acceptable

XML site backup with attachments

Acceptable

Unacceptable

XML site backup minus attachments, plus manual backup of attachments

Unacceptable

Unacceptable

Manual backup of database and attachments

Creation Delay is the time it takes to create an XML site backup minus attachments.
Disk Usage can be estimated by multiplying the frequency of your XML site backups by their current size.

Manual Backups

Confluence's attachment storage configuration can be set to store attachments in the Confluence home directory, or in the database.

Database Backup
Use your Database Administration Tool to create a backup of your Confluence database. If your database is storing your attachments, importing this later will restore all content. For instances with big attachments, please note that currently Confluence migrate attachments in a single transaction: CONF-9888.

Attachment Backup
If stored on the filesystem, attachments are placed under the attachments directory of your Confluence home directory. Copy this directory to create a backup of all attachments.

To restore from these backups, please refer to Restoring Data from other Backups.

RELATED TOPICS

Production Backup Strategy
Backup FAQ