Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
4.3.2, 4.3.7
-
None
Description
If you import an XML backup to Confluence that has custom backup path defined, but the target instance has the custom paths variable set to false (in confluence.cfg.xml), scheduled backup will still pick up the custom backup path.
If the path does not exists/not writable on the target system, the scheduled backup will obviously fail. This way the backup path at Confluence Admin > Backup Administration will display the default value, instead of what is stored in BANDANA table (where bandanakey='atlassian.confluence.settings').
To fix this, you will have to:
- Shut down Confluence
- Set the following property to true in <CONFLUENCE-HOME>/confluence.cfg.xml:
<property name="admin.ui.allow.daily.backup.custom.location">false</property>
- Start Confluence
- Go to Confluence Admin > Backup Administration, modify the path to the correct value
Attachments
Issue Links
- duplicates
-
CONFSERVER-21844 admin.ui.allow.daily.backup.custom.location still allows Confluence to create backup to custom location even if it's set to false
- Closed