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

Next challenges

Recent achievements

Recognition

  • Give kudos
  • My kudos

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Migrating Jira\Fisheye to different server

Hi,

Im currently playing catchup for reasons I wont bore you with. We currently have Fisheye v2.7.8 and Jira v6.1.2 running and I want to migrate them to a different server updating our Fisheye environment.

As internally managed repositories are no longer supported within Fisheye and this is what we have I will have to make the additional step of including a migration to stash. And was hoping that someone could look at my migration plan to let me know if its the best way to go about it.

Just to make things difficult the Fisheye DB was never migrated to mysql and is currently running on the internal DB.

So my plan is to install Jira (latest version) on the new server and run a backup and restore from the old to new server.

Install the same version of Fisheye on the new server and migrate the data across from the old server. Once copied convert the database to mysql.

Once I have copied migrated the database to mysql I will then need to update Fisheye to the latest version and then migrate the repositores to stash.

How does this sound?

4 answers

0 votes
Nick Atlassian Team Jan 02, 2014

Your plan sounds pretty sound.

When you migrate the data across from the old FishEye server, to the new one, you should be able to get away with copying everything in your FISHEYE_INST directory. Leave the FISHEYE_INST on the old box in situ, and that will serve as your data backup for the upgrade too.

When you copy the FISHEYE_INST directory however, be sure that your fisheye server is completely shutdown before you start to take the copy. The alternative is to take a full backup (including all caches) and restore that on the new server.

Thanks Nick,

Ive noticed within the config.xml in FISHEYE_INST that it refers to the git executable located on the server. Will this effect the migration if for now I ignore it and just make sure that this config file points to the migrated repositories on this server?

Thanks again

Nick Atlassian Team Jan 05, 2014

Yes indeed - any local paths mentioned in config.xml will need to be updated to the new locations on the new server.


Ok great Ive added it and am currently migrating as we speak (type). I've noticed whilst the upgrade is taking place that Im getting a lot of

....\XYZ.git does not appear to be a git repository, fatal: could not read from remote repository. Please make sure you have the correct access rights and the repository exists. - Cloning into bare repository 'clone'

I know it exists because I put it there but am I correct in thinking its still cloning the repository? Thanks

Nick Atlassian Team Jan 06, 2014

I would need more context around that error to determine the root cause.

Does the full path to ...\XYZ.git exist on your new server ?

Has it progressed beyond that error now ?

Hi Nick,

Apologies for the delayed reposnse but Ive managed to get the it working - I say working its 90% there. All the projects have migrated across to standard projects. Ive installed Stash and its configured and working.

All Im left to do is migrate the standard fisheye repositories to Stash, which I am about to test. Will let you know - thanks :)

Managed to fully migrate the repositories, one of my problems was that I was using the latest version of Git which would error stating unknown directory or incorrect username. I downgraded this version to 1.8.4 and then migrated with out any errors.

Nick Atlassian Team Jan 13, 2014

Glad to hear the migration is now complete.

Which version of git were you using that had problems ? We will investigate.

Hi Nick,

Using version 1.8.5 caused problems as it seems to want to push\pull using ssh I uninstalled that and installed 1.8.4

Managed to fully migrate the repositories, one of my problems was that I was using the latest version of Git which would error stating unknown directory or incorrect username. I downgraded this version to 1.8.4 and then migrated with out any errors.

Suggest an answer

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

Share your Confluence Cloud experience for a chance to win $500!

Take our 5-minute survey to win a $500 Visa gift card! Are you currently using Confluence Cloud? We want to hear from you! Fill out this quick survey about your Confluence Cloud experience so we ...

240 views 5 13
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