I am setting up a backup scheme for our Crucible/Fisheye instance and I thought of using the same setup as we have for JIRA and Confluence,
But I haven't found this setup anywhere in the Crucible/Fisheye documentation. The only alternatives discussed are:
Is it not recommended to do it in the same way as for JIRA and Confluence?
This would fit in better in our backup infrastructure to do it that way.
Does anyone have any experiences of this way to backup Crucible/Fisheye?
You are not finding any documentation regarding the approach you want to follow because that's not what Atlassian recommends.
As you've realized, we recommend using scheduled backups or the CLI to create backups from a script.
You might be asking why Atlassian does not recommend the approach you're trying to follow. The answer is simple: to avoid data inconsistency / corruption. As Crucible reviews are stored in the database, if the database is being backed up while the instance is up and running and users are working on Crucible reviews, you might face data inconsistency problems.
It doesn't mean that the approach you want to follow won't work. It works, but only if the FishEye/Crucible instance is turned off before proceeding. This would ensure data consistency.
Everything below is tested on Ubuntu 17.10. I prefer to use Jira in a docker container because: 1. I can install Jira with a couple of commands. 2. I can start and stop Jira just by starting and s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot