Data Store and Backup Strategy

Nintex Solutions are based on micro-services design approach that uses several data storage solutions. This page will give you many different options for storing your data, and it will provide details, and explain the process, about how to backup and protect your data.

Data Storage Solutions

Data Storage Solution

Purpose

Store Type

MySQL / MariaDB

PD Metadata Store

SAN / Local Disks on Running Machines

Mongodb

PD Main Data Store

Local Disks on Running Machines

Redis

PD Cache Data Store

Local Disks on Running Machines

RabbitMQ

PD Queue Solution

Local Disks on Running Machines contain two types of data: definitions (metadata, schema/topology) and message store data

SEQ

PD Central Logging Solution

ClusterFS/NFS/Local Disks on Running Machines Seq contain two types of data:configuration and logs

Server Runtime OS

PD Servers Runtime & Deployment OS

Local Disks on Running Machines

Robots (Clients) Runtime OS

PD Robots Runtime & Deployment OS

Local Disks on Running Machines

Backup Strategy

Backing up your data, running test restore procedures on your backups, and storing copies of backups in a safe, offsite location protects you from potentially catastrophic data loss.

Backing up is the ONLY way to protect your data.

Data Storage Solution

Backup Details

Restore

MySQL / MariaDB

Using Mariadb Backup Solution

Recommendation : Daily incremental backup, weekly full backup

mariabackup --backup \
   --target-dir=/var/mariadb/backup/ \
   --user=mariabackup --password=mypassword

mysqldump NintexDB > NintexDB-backup.sql

mysql NintexDB < NintexDB-backup.sql

Mongodb

Using Mongodb Backup Solution

Recommendation: Daily incremental backup, weekly full backup

 

Redis

Backup the Redis rdb file

Recommendation: Daily backup

 

RabbitMQ

Backup Rabbitmq data

Recommendation: Daily backup

rabbitmqctl export_definitions /path/to/definitions.file.jso

Backup messages using file system directory copy

All message data is combined in the msg_stores/vhosts directory and stored in a subdirectory per vhost.

Restore Definitions:

rabbitmqctl import_definitions /path/to/definitions.file.json

Restore Messages: using file system directory copy - restore the content of msg_stores/vhosts

SEQ

Recommendation : Continue backup

Configuration:

Seq will automatically back up the configuration on a daily basis. The .seqbac files that are created are stored in the \Backups directory under the Storage root path.

Backups can be retrieved directly from disk, or downloaded from the web UI in Settings > Backups.

Logs Data:

Export in real-time using Seq.App.JsonArchive : https://github.com/datalust/seq-app-jsonarchive

Restore Configuration :

seq service stop
seq restore --secret-key="1234567abcdef=" --backup="C:\Data\seq_20150101.seqbac"
seq service start

Logs Data:

seqcli ingest --json -i <glob>.

Server Runtime OS

Regular OS Snapshot backup