How to configure scheduled backups to use a nonexistent backup path
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When configuring Bamboo for Specifying a backup schedule, the specified backup path needs to exist and be accessible. This KB article will address how to bypass this security restriction.
Environment
Tested on Bamboo 7.x, 8.x, 9.
Diagnosis
Bamboo will deny configuring a scheduled backup if the destination directory does not exist or is unreachable.
As specified in Specifying a backup schedule, if the directory exists(locally) but is unreachable, a jvm argument can be provided to allow the operation. The argument is
-Dbamboo.paths.set.allowed=true(more context and information on this argument can be found in the link provided).
If the path is non existent, Bamboo will block the operation and show the mesage
Cause
This is not a bug, but the expected behavior. For security reasons, Bamboo blocks the configuration.
Solution
If the directory is planned to be created in the future, then the following workaround can be applied to bypass this restriction:
- Stop Bamboo.
- Open the file <bamboo-home-shared>/configuration/administration.xml.
- Locate the line with the tag
<backupPath>and input your value:
<backupPath>/nonexistent/path</backupPath>- Start Bamboo again.