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,365,335
Community Members
 
Community Events
168
Community Groups

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

Atlassian Community Events