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

Backup Crucible with native db tools?

Hi,

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,

  • db-dump of the postgres-db
  • file-archives of the install and home directories

But I haven't found this setup anywhere in the Crucible/Fisheye documentation. The only alternatives discussed are:

  • scheduling backups within the GUI
  • use the CLI to create the backups from a script

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?

Best regards,

// Svante

2 answers

Just remember that native backup is always consistent, but external backup is only consisten if app is not running at the time.

0 votes

Hi Svante,

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.

Kind regards,
Felipe Kraemer

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

292 views 16 18
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