Cloning a bamboo instance

In case you need to clone your production instance to a test/staging instance in order to prepare migrating to another database or upgrading bamboo.
For example, you may want to transfer your current production snapshot to a test server as permitted in the license agreement.

License

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

Clone 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, choose 'import existing data',

Clone 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 purpose 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
   zip <bamboo-production-home> directory, the embedded database will be part of this zip.	zip <bamboo-production-home> directory. create a backup with the native tools provided by your DB.

3. (Optional) reduce the size of this zip by deleting the xml-data/build-dir - this directory only contains working copies of checked out sources.
4. restart production bamboo
5. transfer the home.zip to your cloned instance and unzip
6. 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.
7. point bamboo.home of your cloned instance to the unzipped <bamboo-clone-home> directory
8. start the bamboo clone

This should give you a perfectly cloned instance.

Your next steps

• If the new server has different locations for
  • JDK
  • ant
  • Maven
  • perforce
  • Msbuild tools
    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.