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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Crucible migration between servers avoiding long reindex times

Hi,

We are using Crucible 2.5.2 and have close to 70 repos spanned across 100 projects.Our Crucible & fisheye caches are quite large with a combined size of close to 150GB. The zip backups are quite huge as well and hence restore from the zip back doesn't work.

We are planning to migrate our Crucible instance to a new box with large disk capacity but don't want to compromise on the reindex/rescan time it takes to do the svn repos.

Can someone please help on the steps which could be used to migrate the server from one host to another and at the same time avoiding the rescan of repos?

Is it possible to copy the caches from one machine to another and then making the new instance point to the original db?

Will steps mentioned in the below link avoid rescaning of the repos?

https://confluence.atlassian.com/display/FISHEYE/Migrating+FishEye+Between+Servers

i came across with the below link but not sure if we can something similar just to create a pararllel copy quickly without actually doing an upgrade?

https://confluence.atlassian.com/pages/viewpage.action?pageId=298977103

Thanks,

Neeraj

1 answer

0 votes
lpater Atlassian Team Sep 22, 2013

Hi Neeraj,

you can safely move your FishEye caches from one server to another.

The steps outlined in https://confluence.atlassian.com/display/FISHEYE/Migrating+FishEye+Between+Servers will allow you to set up a new instance with the existing data.

If there were new reviews created on the original server after moving the caches, your repositories might need a review-revision reindex (see https://confluence.atlassian.com/display/FISHEYE/Re-indexing+your+repository) and a Crucible Index Maintenance (in Administration/Crucible) to sync the indexes up with the db. Both of these should be quick and unrelated to the size of your repositories.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

71 views 2 6
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