Alternative Backup Strategy

Confluence's Built-in Backup

Confluence automatic daily XML backup is ideal if you:

• Confluence を評価している場合
• データベースの管理に詳しくなく、Confluence インストールが小規模である場合

But once your Confluence installation reaches more than a few thousand pages, the XML backup facility can be inefficient compared to your database's own backup tools.

Establishing a Production System Backup Solution

The built in backup functionality in Confluence requires a lot of memory to run and is less reliable when restoring. Atlassian recommends establishing an alternative database backup strategy:

• Create a backup or dump of your database using tools provided by your database
• Confluence ホーム ディレクトリのファイル システム バックアップを作成します。

Once this is in place, disable the daily backups from Administration > Daily Backup Admin.

We want to stress that creating these two backups is just as good as having a Confluence XML backup, and a lot more robust for large production instances. You will be able to restore your whole site, including all data, attachments and configuration information intact with these two backups. We have written up a document on how to do this here.

Step by step instructions

Take a look a the Migrating Confluence Between Servers document for instructions on restoring a backup using this technique.

その他のプロセス

XML backups are described and used for other processes in Confluence, like upgrading and moving servers. Using the backup strategy described here will work for those processes. Our upgrade guide does not require the use of an xml backup (an old upgrade procedure, and the JIRA upgrade guide use XML backups for upgrading), and our migrate server procedure - used to set up a test server - can leverage an sql dump as well.

The only process that requires the XML backup is the database migration procedure. Large data sets will require third party database migration tools.

関連トピック

Site Backup and Restore
Backup FAQ