You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey there. We have a test instance of Confluence 6.4.1 and a production instance of Confluence 5.8.4 and I would like to regularly update the test instance to have the same content as production. Is it possible to export the database (in our instance postgres) along with the attachments directory from the earlier version and import them into the latest version ? I'm guessing the schema has changed between versions but can we manually run the schema update script to handle this ? Otherwise our test instance is going to get quickly out of date before we can update live. Thanks.
Thanks for the response. The upgrade from 5.x to 6.x has already taken place and the schema has been updated. But my concern is that if I now attempt to import data from 5.x into 6.x then during startup it will recognise an earlier schema and refuse to start. If that's the case then I wonder if we can manually run the schema update to enable the application to start. We have a test instance of a newer version because we are testing the upgrade from 5.x to 6.x and then was to keep the 6.x version up to date until it's time to migrate.
Welcome , I have never tried this myself but the upgrade should initiate again after you import the database from the production.
if the data is less you can also try importing XML https://confluence.atlassian.com/doc/restoring-a-site-152034.html
OK this does work fine. Initially on startup you'll see something like the following:
Confluence will not start up because the build number in the home directory  doesn't match the build number in the database 
But to fix this just edit the buildNumber in <confluence_home>confluence.cfg.xml to the earlier value and all required schema changes will then be applied on startup.