The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

fisheye cold failover

Kumaran
April 9, 2016

Has anyone implemented a cold failover instance for fisheye ? If so, are there any recommendations ?

We have a fisheye installation and a instance directory. Copying both the directories to another instance will work. But, is there a specific directory that needs to be synced between the instances ?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Piotr Swiecicki
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 19, 2016

FishEye/Crucible internal state is kept in

  • filesystem in $FISHEYE_INST folder
  • configured database

In order to keep cold failover system you need to ensure both of them are copied consistently to failover location.  Note copying live system is very dangerous as you risk having inconsistent data.  

The recommended way of backing up a system is using built in tools, documented in https://confluence.atlassian.com/fisheye/backing-up-and-restoring-fisheye-data-298976928.html.  If you want to customise it and take benefit of filesystem snapshot mechanisms for instance, I would suggest the following approach:

  • take FishEye/Crucible instance down (e.g. run bin/stop.sh)
  • copy database to failover location
  • copy filesystem to failover location (e.g. with the use of rsync, FS snapshots etc.)
  • take FishEye/Crucible instance up

it would require short downtime but should ensure consistency of the data.  

TAGS
AUG Leaders

Atlassian Community Events