Confluence 4.0 : Site Backup and Restore
This page last changed on Jul 26, 2011 by pwatson.
By default, Confluence backs up all data and attachments once a day to a backup file. These files are called XML site backups, and are stored in the
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 may find that backups become slow to create and use large amounts of disk space. Backups For Large InstancesXML 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 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 GB instance of Confluence is backed up daily, it will create 30 GB 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 is the time it takes to create an XML site backup minus attachments. Manual BackupsConfluence's attachment storage configuration can be set to store attachments in the Confluence home directory, or in the database. Database Backup Attachment Backup To restore from these backups, please refer to Restoring Data from other Backups. Related Topics |
![]() |
Document generated by Confluence on Sep 19, 2011 02:38 |