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

Next challenges

Recent achievements


  • Give kudos
  • My kudos


  • 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

Riada Insight (Server Version): Database backup/roll back solution

We are investigating solutions for a backup/roll back for the Insight Asset management tool from Riada. The need is driven from a case where an insight administrator deleted some object types from the schema and therefore erased a ton of object history. 

If this were to happen (or somehow the add on became corrupted) we would ideally like to rollback to a previous backup. I understand that more tightly controlling access to the insight administrator and manager roles would help limit the number of users who could make breaking changes, but I would like something more foolproof. 

After reading the docs, it seems like the only solution would be to rely on a JIRA application backup. The way I understand it, we would need to do a total restore of the JIRA application in order to do a rollback of Insight. This strategy is risky/problematic because we would need to bring down JIRA and lose any JIRA changes between the rollback and the last JIRA backup. 

I struggle to find any documented sources that to describe a strategy to backup and restore insight only. Has anyone done something like this? Can you point me toward some documentation that may touch on this issue? 

For reference, we are running Insight Server version 6.4. 


1 answer

We have struggled with this as well in our environment as well. We are currently using an Oracle back-end and used Oracle's data pump to back up only the Insight related tables and a file system backup of the Insight filesystem (attachments and avatars). Then you can shut down the application and roll back/restore just those tables to the environment.

There isn't a great restore process for the product at the moment. We investigated the import/export, but that doesn't maintain the history/comments/unique id's. They recently added a synchronization import, but that has the same issues.

We also are utilizing automation rules to handle the permissions on removals by having a status for "decommission"/"retired" which will remove the objects using automation instead of giving the users the ability to delete. This process runs on a schedule and can be setup to give some time before the removal in case of error.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

5 mobile apps for Jira Cloud to boost productivity

  It’s very important to have access to the workflow process from anywhere. Especially if you manage the work of others. There is no difference whether you’re out of office, or drive a ca...

268 views 2 5
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