Backup Crucible with native db tools?

[Svante Gustafsson Björkegren]

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

[Felipe Kraemer]

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

[Sergey Svishchev]

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