Confluence 5.7 has reached end of life
Check out the [latest version] of the documentation
Confluence backs up your data regularly into a zipped XML file. By default, this backup is performed at 2.00 a.m. each day and the backup files are stored in the backups
folder under the Confluence Home directory. The default naming convention for the backup files is 'backup-yyyy_MM_dd
'. Confluence can write backups to both local and mapped network drives.
From the Backup Administration section of Confluence's administration console, you can:
You can also change the schedule of this backup using Confluence's scheduled jobs feature.
You need to have System Administrator permissions in order to configure these options.
The information on this page does not apply to Confluence Cloud.
To configure Confluence backups:
You can disable Confluence backups through the scheduled jobs feature.
Screenshot above: Editing the Backup Configuration
By default, it is not possible to specify a backup path via the Confluence Administration Console. This feature is disabled by default for security reasons. Administrators can restore this functionality by updating the relevant configuration property as described below. However, we recommend that you turn the feature off in production environments. For production environments, please review our Production Backup Strategy.
To enable the configuration option:
confluence.cfg.xml
file found in the Confluence Home and other important directories.Set the value of property admin.ui.allow.daily.backup.custom.location
to 'true
' (without the quotation marks).
<property name="admin.ui.allow.daily.backup.custom.location">true</property>
If the value of the above configuration property is 'true', it will be possible to specify a backup path via the Confluence Administration Console. If the value of this property is 'false' or the property is not present in the configuration file, the backup path is not configurable.
The time zone is taken from the server on which Confluence is running.
To check the time according to the server, do the following:
Consider using the production backup strategy if your Confluence site is large or you are encountering problems with your automated backup.