How to plan for manual Bamboo Data center backup before planning an upgrade
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
The purpose of this page is to help plan for manual Bamboo backup before any schedule event like Bamboo upgrade is planned, this backup can be used during a rollback process. The steps listed on this page talks about manual steps involved in backup process.
Below 2 articles covers some detailed instructions on planning upgrade and automatic backup process available in Bamboo
Bamboo exporting data for backup
Environment
The solution listed is applicable for all the supported version of Bamboo.
Solution
For complete Bamboo backup, we suggest to backup below 3 paths
- Bamboo Database - A restore point should work, but please make sure the time of the restore point creation is in sync to time you are taking backup of the below directories, this will not be a problem if the Bamboo server is in paused stage or you have brought your bamboo instance down before planning the backup.
- Full <bamboo-install> directory
- Full <bamboo-home> directory
- Full <bamboo-shared-home> directory ( This is required if you have a separate shared home folder, normally in a single node instance this would be present under <bamboo-home>shared folder )
Having a backup of <bamboo-install> directory is ideal for quicker recovery simply because it can contain configuration changes done on few files.
For <bamboo-home> and <bamboo-install> folders, the ideal option is to just zip the entire folders and keep it safe.
In case of rollback, point the database back to restore point and start Bamboo from install directory backed above, the home directories should also be reverted back to the one backed above.