Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

how can I point existing crowd installation to new database (had to move it to new server)

I have updated the crowd.cfg.xml file to point to the new db instance, but crowd still isn't hitting it 

1 answer

1 vote

Hi @Regina Frost

Updating the crowd.cfg.xml file is not the right way to do what you want to do.

Here is a link to Atlassian's documentation regarding Crowd migration to another database:

So here is what you must do:

  1. Stop Crowd and put back your old crowd.cfg.xml file (I suppose you have a backup of this file)
  2. Start Crowd and log into Crowd's console. Then go to the backup section and perform an XML backup
  3. Stop Crowd and then delete crowd.cfg.xml (keep a backup of it just in case something would go wrong)
  4. Restart Crowd, it will behave as if it was a fresh install and will ask you for your license key. That is absolutely fine.
  5. Select 'Import data from an XML backup'
  6. Continue the installation and point to your new database server
  7. When requested, upload your XML backup.
  8. Et voilà! Everything should work as expected. You might need to reset your Crowd SSO domain configuration if you selected to reset it when doing your XML backup at step #2.

A bit of a late reply, but hopefully this might help others too. While the XML option is what's documented, we've done numerous database migrations in the past for Crowd between mysql > mysql and later psql > psql (standard dump and restore) and updated the connector in the crowd.cfg.xml file and the process worked well. Given it's easier to script a DB dump - we use this then push offsite as part of our DR/BC process.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events