If we have this feature, it will helps a lot to admins.

+1

Thanks

Crazy there isn't a way to do this. 

Absolutely crazy there is no way to backup insite or restore an accidentally deleted object, considering how easy it is to delete an object when the two delete buttons are within a few cms from each other.

+1 vote

Hello,

We want to use scheduled imports to regularly update an Insight schema. But to do this we need to be able to make a backup of the schema and restore it in case of problems with the imports.

Must have feature!

Hello ! I maybe have a solution for now to all users who need to backup only Insight. I use this since 3 years because one time i delete all objects by mistake but Jira is a main software in our company and it was impossible to full restore Jira. I was able to restore a full VM and export only the table of Insight and now i make a backup every hours and since 3 years i use it twice to full restore insight without any incidence on Jira BUT i don't use it since 1 year and i hope the table not changed! 

Here the script i use: (put it into a sh file and use a cron to execute it).

First line delete all backup aged more than 10 days. 

(Its for PostgresSQL)

find /var/backups_insight/ -type f -mtime +10 -exec rm -f {} \;
date=`date +%d-%m-%y_%Hh%M`
pg_dump -t \"AO_8542F1\"* -d jiradb -p 5432 -U postgres -v -F t > /var/backups_insight/$date.backup-insight.sql

output backup : /var/backups_insight/

01-12-22_08h00.backup-insight.sql  05-12-22_10h00.backup-insight.sql  07-12-22_12h00.backup-insight.sql  29-11-22_10h00.backup-insight.sql
01-12-22_10h00.backup-insight.sql  05-12-22_12h00.backup-insight.sql  07-12-22_14h00.backup-insight.sql  29-11-22_12h00.backup-insight.sql
01-12-22_12h00.backup-insight.sql  05-12-22_14h00.backup-insight.sql  07-12-22_16h00.backup-insight.sql  29-11-22_14h00.backup-insight.sql
01-12-22_14h00.backup-insight.sql  05-12-22_16h00.backup-insight.sql  07-12-22_18h00.backup-insight.sql  29-11-22_16h00.backup-insight.sql
01-12-22_16h00.backup-insight.sql  05-12-22_18h00.backup-insight.sql  08-12-22_08h00.backup-insight.sql  29-11-22_18h00.backup-insight.sql
01-12-22_18h00.backup-insight.sql  06-12-22_08h00.backup-insight.sql  08-12-22_10h00.backup-insight.sql  30-11-22_08h00.backup-insight.sql
02-12-22_08h00.backup-insight.sql  06-12-22_10h00.backup-insight.sql  28-11-22_08h00.backup-insight.sql  30-11-22_10h00.backup-insight.sql
02-12-22_10h00.backup-insight.sql  06-12-22_12h00.backup-insight.sql  28-11-22_10h00.backup-insight.sql  30-11-22_12h00.backup-insight.sql
02-12-22_12h00.backup-insight.sql  06-12-22_14h00.backup-insight.sql  28-11-22_12h00.backup-insight.sql  30-11-22_14h00.backup-insight.sql
02-12-22_14h00.backup-insight.sql  06-12-22_16h00.backup-insight.sql  28-11-22_14h00.backup-insight.sql  30-11-22_16h00.backup-insight.sql
02-12-22_16h00.backup-insight.sql  06-12-22_18h00.backup-insight.sql  28-11-22_16h00.backup-insight.sql  30-11-22_18h00.backup-insight.sql
02-12-22_18h00.backup-insight.sql  07-12-22_08h00.backup-insight.sql  28-11-22_18h00.backup-insight.sql
05-12-22_08h00.backup-insight.sql  07-12-22_10h00.backup-insight.sql  29-11-22_08h00.backup-insight.sql

Example to restore :
sudo -i -u postgres
cd /var/backups_insight/
pg_restore -d jiradb -U postgres -p 5432 -c -v 30-06-20_08h00.backup-insight.sql
 

I hope this help.

+1 vote

+1 vote
 
 

+1 vote