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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,466,623
Community Members
 
Community Events
176
Community Groups

When upgrading Crowd to new version, do you need to take Database backup?

Edited

The Upgrade instructions https://confluence.atlassian.com/crowd/upgrading-crowd-via-automatic-database-upgrade-213519474.html have step to take up the database backup, however we are not touching the database, so why is this needed?

I have used these steps in my non-production environment to upgrade Crowd version, and it worked.

 

1. Stop Crowd service.
2. Backup Crowd home directory.
3. Rename Crowd installation directory.
4. Remove Crowd Service.
5. Unzip Crowd installation file to D:\Atlassian\Crowd.
6. Copy crowd-init.properties file from backed up Crowd installation directory to new.
7. Install and start Crowd service.

1 answer

1 accepted

1 vote
Answer accepted

Hi,

The application upgrade may well change database schema/values as part of the startup process. If this happens, and then you need to roll back, you’ll want to have the database backup to revert to. Even if there’s no changes during the upgrade, things can go wrong and you may end up with corrupt data.

I’ve been running Crowd since 2.3 or so, and have been through many upgrades. While I’ve never had to revert the database cause of a failed user upgrade, ensuring there’s a backup to restore from is always still part of the process. 

CCM

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events