We have a very old confluence 4.0.3 which we want to migrate to a newest version. Before doing this I want to clone the confluence to a staging machine where we want to try the migration first.
Is there a simple way to create a one-time copy of whole conflunce 4.0.3 including database content, all settings and license incl. get this running on another machine? This action will not be repeated, so the data does not need to be synched again.
Thanks for any response and help in advise.
I agree that using a VM is the best solution. If it is not an option for you you can follow Atlassian's steps to migrate it to another server. I have done this in the past and it is very easy to do. Information can be found here: https://confluence.atlassian.com/doc/migrating-confluence-between-servers-184150.html
Irwins solution is the best though.
Performing an xml-backup/restore does not require you to import it to the same version though.
Looks like you have to go to 4.3, then 5.10, then 6.x.
Thanks, this was also my hope.
But following the installation of copy and restoring the content the process suddenly failed at 11% and stucked for the whole day without any progress.
Now the system is not reachable at all anymore with an fatal exception:
Unable to start up Confluence. Fatal error during startup sequence: confluence.lifecycle.core:mananagedjobs (Start and stop the Managed Scheduled Jobs) - org.springframework.dao.DataIntegrityViolationException: Hibernate operation: could not insert: [com.atlassian.confluence.setup.bandana.ConfluenceBandanaRecord#2]; SQL ; integrity constraint violation: unique constraint or index violation; SYS_PK_10054 table: BANDANA; nested exception is java.sql.SQLIntegrityConstraintViolationException: integrity constraint violation: unique constraint or index violation; SYS_PK_10054 table: BANDANA
Looks that simple import did not worked into a fresh system. Unfortunately Confluence does not allow a second import anymore. Now I have too look how to get a clean system again. Seems not be easy as expected.
Cloning the server is often the easiest way as Irwin points out. Remember to backup your database if that does not reside on the same server.
We do testing all the time. In our lab we automatically check if there is a new vesion of JIRA, Confluence, Bitbucket, Bamboo and FishEye/Crucible every night. If there is a new version, the application is automatically upgraded, and our team is notified by email that there is a new version to test.
This works well in a lab, but not elsewhere. To clone our production environment so that it`s possible to perform a test upgrade we found it easiest to use use a script that performs rsync and databse export/import automatically. Since the baseurl also changes, this is also done in the script (something like this 'update jiradb.propertystring set propertyvalue="https://testjira.example.com" where ID=14043')
If you are interested in a sample of the script i can email it to you.
Lars, Kantega Single Sign-on
Hi Community! 2018 was filled with changes for our team, both big and small, and we've taken a lot of time to both celebrate our wins and recognize areas of improvement. One thing that we're a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs