How do I make a backup?

Bulk backup

The complete DISQOVER stack can be backed-up based on the /disqover/ directory. 

tar -cvpzf disqover-backup.tar.gz /disqover/ 

We recommend storing a back-up on a cloud service (e.g. S3) or related. 

Automatisations that were not configured via the designed DISQOVER scheduling feature  (e.g. cron jobs or related) are not included in the back-up. Please make sure to have any of these schedules documented.

Component backup

In addition, the separate components can be backed-up independently from the DISQOVER UI, server back-end or both.

Component

Backup

Change tracking

Source data

/disqover/data/source_data 

Store in an external database or bucket

SOLR image

/disqover/data/solr 

Store in an external database or bucket

Pipeline

Export pipeline .yml file via Menu > Data Ingestion Engine > My_Pipeline_Name > export icon

This does not contain source, intermediate processing or published data.

Store in svn (bucket, github,…). Can be version tracked.

Templates, Default settings and User views 

Export template.txt bulk file via Menu >Template >Export 
Templates can also be exported one-by-one.

Export the User Views/Default template settings.txt file via Menu > Admin > User Views/Default Templates > export 
If no user views are set-up, this will export the Default Template settings only.

Stored in svn (bucket, github,…).

Plugins

/disqover/data/plugin/ 

Store in svn (bucket, github,…). Can be version tracked.

Configuration

/disqover/data/postgress/ 

This includes Users, User groups, Customizations, System Settings, Templates, User Views/Default Templates, set-up Event actions and Pipeline (yml file), Pipeline Schedules, RDS subscription configuration and RDS subscription schedules.

Store in an external database or bucket