This is the documentation for Bamboo 5.5. View this page for the

Unknown macro: {spacejump}

of Bamboo, or visit the latest Bamboo documentation.

This page describes how to clone your production instance of Bamboo to a test or staging instance in order to prepare for migration to another database or for upgrading Bamboo.
For example, you may want to transfer a snapshot of your current production Bamboo instance to a test server as permitted in the license agreement.

  • We strongly recommend to duplicate Bamboo first and then apply changes such as upgrade or migrating to another database.
  • If you are using JIRA or Crowd for user management, the URL of the Bamboo server may change when you clone the Bamboo instance, in which case you will need to edit that setting for the Bamboo application in JIRA/CROWD to match the new URL.

License

Development licenses are available for any Commercial or Academic license. Create one or contact us for help.

Clone the production instance - standard

This is the simple and straight-forward way to clone your instance:

  1. Export/Backup your current instance.
  2. Copy zip across to new server.
  3. Install the same version of Bamboo on new server.
  4. Point Bamboo.home in <bamboo-install>/webapp/WEB-INF/classes/bamboo-init.properties to your new Bamboo home directory.
  5. Start the new instance.
  6. Complete the setup wizard, and choose Import existing data.

Clone the production instance - alternative

If your current instance has grown too large and export/import does not work you can still clone your instance using an alternative backup and restore strategy.
The approach is to clone <bamboo-home> and make it available to the new test/clone instance.

  1. Shutdown production Bamboo at a convenient time.

  2. Create a backup:

    embedded DB

    external DB

    (Optional) Reduce the size of this zip by deleting the xml-data/build-dir – this directory only contains working copies of checked out sources.

    Zip <bamboo-production-home> directory; the embedded database will be part of this zip.

    (Optional) Reduce the size of this zip by deleting the xml-data/build-dir - this directory only contains working copies of checked out sources.

    Zip <bamboo-production-home> directory.

    Create a backup with the native tools provided by your DB.

  3. Restart production Bamboo.
  4. Install the same version of Bamboo on new server.
  5. Transfer the home.zip to your cloned instance and unzip into <bamboo-clone-home>.
  6. (External DB only) Create a new database for the cloned instance and import the db dump.
  7. Edit <bamboo-clone-home>/bamboo.cfg.xml and <bamboo-clone-home>/xml-data/configuration/administration.xml and change the server names/ip addresses according to the new location.
  8. (External DB only) Edit <bamboo-clone-home>/bamboo.cfg.xml and enter the new database connection details and credentials.
  9. Point bamboo.home of your cloned instance to the unzipped <bamboo-clone-home> directory.
  10. Start the Bamboo clone.

This should give you a perfectly cloned instance.

Your next steps

  • If the new server has different locations for
    • JDKs
    • Ant
    • Maven
    • Perforce
    • Msbuild tools
      then adjust the settings in the server capabilites settings to match the locations on the new machine.
  • From here you can upgrade if desired.
  • After the upgrade you should be able to export your instance without problems and then migrate to another database for instance.
  • No labels

 

 

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.