Why isn't Bamboo backing up?

[Damiam Cleveland]

Hello, I support an on-prem instance of Bamboo. It is configured to back up every day at 10 p.m. However, it isn't backing up. I would appreciate some guidance on how to troubleshoot this issue.

Thanks.

[Eduardo Alvarenga]

Hello @Damiam Cleveland

Welcome to Atlassian Community!

The first thing you'd have to check is the Bamboo logs. They are located on the Server at <bamboo-home>/logs/atlassian-bamboo.log. Open that file, and search for the period around the scheduled backup and observe if any errors or warnings are showing up.

If you can't find any entries it may be the case that your Backup is disabled go to:

• Bamboo Administration >> Scheduled backups >> Edit
• Validate if "Disable scheduled backups" is not selected

Best regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful-- 

[Damiam Cleveland]

Thanks for the guidance, Eduardo.

I can confirm "Disable scheduled backups" is not selected. 

However, the /logs directory doesn't exist on my system.

Also peculiar is that the global configuration change history shows that the backups are taking place, but there's no trace of the backups.

Any other ideas?

Thank you

[Eduardo Alvarenga]

Hello @Damiam Cleveland

If you don't have a logs directory you may be running into a major issue. I recommend you open a ticket with Atlassian so our specialists can check your system closely and get to some good recommendations to fix your issue.

Best regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful-- 

[Damiam Cleveland]

Duly noted, Eduardo. Before I contact support, can you tell me a bit about the "Wait for jobs to complete" option? Our backups are scheduled for 10:30 p.m. If a job runs at that time, will the backup never run, or will it start once it completes?

Also, will data be corrupted if we uncheck this option, and the backups run before a job completes?

Thank you

[Eduardo Alvarenga]

@Damiam Cleveland

Bamboo will wait for all builds to be over before initiating the backup. This is documented on this bug BAM-8233.

If that's your case, either move the Backup to a less busy time or program your Plans to be built at a different time of the day.

If you'd like to enforce it, add a Script Task to the first Job of every Plan that will calculate the current time. If the time is too close or within the backup timeframe, make the script fail so the backup can start.

Cheers,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful-- 

[Damiam Cleveland]

Thanks for all of the valuable information, Eduardo.

A few more things stand out as I look closer at the issue.

The global configuration change history captures the following messages before the backup job starts:

22:32, 1 Oct 2023  System  scheduleBackupConfiguration.lastRanDate  

22:32, 1 Oct 2023  System  Server state changed to 'RUNNING' from 'PAUSED'

22:30, 1 Oct 2023  System  Server state changed to 'PAUSED' from 'PAUSING'

22:30, 1 Oct 2023  System  Server state changed to 'PAUSING' from 'RUNNING'

Is this normal?

[Eduardo Alvarenga]

Hello @Damiam Cleveland

Yes. Bamboo sets itself in a "Paused" state before any backups. Once the backups are done it restores its state back to "Running".

Backups are stored in <bamboo-home>/shared/exports by default. Did you check that location for any new files?

Kind regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful-- 

[Damiam Cleveland]

Thanks for the help.

Bamboo was installed on a docker instance, so the backups were saved to the backup directory there. I wasn’t looking in the docker instance. The backups are working.

The other part of this project was to have the backups go directly to NAS. Is this possible? I’m referencing this document Exporting data for backup | Bamboo Data Center and Server 9.3 | Atlassian Documentation. I’m unable to locate the setenv.sh script. Where is it normally located? Thank you

[Damiam Cleveland]

Eduardo, 

I found the file.

How do I edit it so that I can edit the export directory path of the scheduled backup job?

[Eduardo Alvarenga]

Hello @Damiam Cleveland

The export location can be changed directly on the Bamboo UI. If you prefer to use the Java property, you'd have to declare it by setting the JVM_SUPPORT_RECOMMENDED_ARGS environment variable in your docker container and restart it.

Best regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful-- 

[Damiam Cleveland]

Got it. So it isn't necessary to modify setenv.sh?

The current scheduled backup export path cannot be changed (it is in bold black).

If I create a new job, will the path be mutable?

Also, am I allowed to export the backup to NAS?

[Eduardo Alvarenga]

For that specific property its not necessary to change setenv.sh.

If you'd like to change the Exported directory path, you can set -Dbamboo.paths.set.allowed=true. Make sure to read this page for some additional security concerns about that property:

• Exporting data for backup

Alternatively, you can mount the static location from the container as a Docker volume on the docker host and have direct access to the exported file and later sync it to your NAS.

You can also mount that as a Docker volume directly in a folder mounted from your NAS in your host.

Best regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful-- 

[Damiam Cleveland]

Delete