Backing up

We strongly recommend that you do periodic backups of your DSS data. We also recommend that you backup before upgrading DSS.


If you are using a Cloud Stacks setup, backups are managed automatically using Cloud snapshots. This section does not need to apply.

The DSS Data Directory (or DATA_DIR) contains your configuration, your projects (graphs, recipes, notebooks, etc.), your connections to databases, the filesystem_managed files, etc.

The DATA_DIR does not contains datasets stored outside of the server: SQL servers, cloud storage, hadoop, etc.


For Govern nodes, you need to make sure to properly backup your PostgreSQL database using the regular PostgreSQL backup procedures. Each time you make a Govern backup, you should also ensure that you have a matching PostgreSQL backup.

Full Backup

The simplest way to backup your data dir is to do a FULL backup of the whole data directory folder:

Make sure you don’t have any job running, then stop DSS:

DATA_DIR/bin/dss stop

Compress your data directory:

tar -zcvf your_backup.tar.gz /path/to/DATA_DIR/

Restart DSS:

DATA_DIR/bin/dss start

Other Backup Methods

The above mentioned method using tar is very simple but always performs full backups, which might not be practical with large data dirs.

There are many other backup methods, and listing them all is outside of the scope of this document, but we can mention:

  • Using rsync for incremental backups (either on the same machine or another machine)

  • The duply / duplicity couple

  • FS-level backup tools (XFS dump for instance)


The full consistency of the backup is only guaranteed if DSS is not running or if the volume is snapshotted atomically. LVM and most cloud managed block devices provide atomic snapshotting capabilities. In that case, the proper procedure would be:

  • Create the snapshot

  • Mount the snapshot as read-only

  • Execute an incremental backup tool on the mounted snapshot

  • Unmount the snapshot

  • Destroy the snapshot

Alternatively, on cloud hosted volumes, the created snapshot can be kept as it is.


All critical files of DSS are text files, which are written atomically, so partially-consistent backups (made while DSS was running) might be recoverable with the help of manual intervention.

Restoring A Backup

To restore a backup, you need to restore the files that you backed up to their original location.

“Pristine restore”

A pristine restore means a restoration of the backed up DSS data:

  • on the same machine as the original one

  • at the original location on the machine

  • on the same DSS version

For this kind of restoration, you simply need to replace the content of DATA_DIR with the content of the archive:

  • If applicable, stop the currently running DSS, and move away the current content of the DATA_DIR

  • Restore the backup

cd DATA_DIR; tar -zxvpf your_backup.tar.gz
  • Restart DSS

Restore on another machine, another location, or another DSS version


You can only restore a backup on a newer DSS version, not on an older one.

Restoration procedure:

  • If restoring on another machine, download and uncompress the DSS software on the new machine

  • Restore the backup files

mkdir new_datadir_location; tar -zxvpf your_backup.tar.gz
  • Replay the installer in “upgrade” mode: this will “reattach” the restored datadir to the installation directory. It will also, if needed, migrate to the newer DSS version:


If you installed the data dir on a different machine or in a different location, you need to rebuild the Python environment. See the “Migrating the data directory section” of our documentation on migrations

Running An Automatic Backup

Here is an example shell script that you can run periodically within a cron task.

#Purpose = Backup of DATA_DIR directory

/path/to/DATA_DIR/bin/dss stop

export GZIP=-9
TIME=`date +"%Y-%m-%d"`
tar -cpzf $DESDIR/backup-dss-data-$TIME.tar.gz $SRCDIR

/path/to/DATA_DIR/bin/dss start

#Optionally remove old backups
OLD=`date -d "4 days ago" +"%Y-%m-%d"`
rm -f $DESDIR/backup-dss-data-$OLD.tar.gz


Save this script in a file “” and set a cron task like the following one (running from Monday to Friday at 6:15am):

15 6 * * 1-5 /path/to/

What Can Be Excluded From The Backup

Temporary / Cache data

The data directory contains some folders which can safely be excluded from the backup because they only contain temporary data which can be rebuilt:

  • tmp

  • caches

  • data-catalog


In addition, the following folders only contain log data, which you might want to exclude from backup:

  • run

  • jobs

  • scenarios

  • diagnosis

Other ignorable data

The following folders contain data which you might consider excluding:

  • exports (contains the data exports made by users)

  • prepared_bundles (contains automation bundles already exported)

  • apinode-packages (contains apinode packages already exported)


The following folders contain data built by DSS. This data can generally be rebuilt, but caution should be exercised when choosing whether to backup these folders:

  • managed_datasets

  • analysis_data

  • saved_models

Datasets stored outside of DATA_DIR aren’t affected by a DSS upgrade: they will still be available after the upgrade.

Govern database

Most of the Govern configuration and all items managed by Govern are stored in a dedicated PostgreSQL database. This includes, but is not limited to:

  • governable items: business initiatives, projects, models, model versions and any other custom item.

  • blueprints

  • permissions

  • custom pages

  • relationships

  • user profiles

In addition to the DATA_DIR, for Govern nodes, you must backup the database.