Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Bruno Vincent Community Leader Apr 30, 2018

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
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

328 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you