There are two categories of data you might want back up :
- this includes all the config files, analytics configuration, users, web config, context configuration, and such.
- this includes the metrics, flows, alerts, packets
For a large data platform like Trisul , configuration backup is of main importance. The databases tend to be of very large Terabyte sizes. The recommended solution for full scale data backup is to setup a DR node.
/usr/local directory. Ensure to first check the directory size using
du -sh /usr/local
The following directories need be backed up. If your Trisul installation is small you can simply backup these directories using normal Linux backup tools.
|data and log files. this directory can be very large
12.14.2 Daily config backup
The trisul-hub package includes the install_setup_backup.sh (backup the Trisul setup) script which setups a CRON which automates these backups.
The supported backup methods are :
- using sftp / scp (the default)
- using FTP
- by copying to another directory, such as an external drive
The steps are :
- Go to /usr/local/share/trisul-hub
- Type ./install_setup_backup.sh
- You will be asked to enter the SFTP login details , or FTP login details
- You will be asked to enter a remote directory
Once complete a crontab entry will be automatically created to backup at 4:00AM daily. You may adjust this later.
### Backup trisul configuration####
0 4 * * * /usr/local/share/trisul-hub/setup_backup.sh /usr/local/share/trisul-hub/setup_backup.conf
The backups are placed in the remote directory in a single tar.gz file with the HOSTNAME and TIMSTAMP of the backup
If you have a distributed setup, copy the
setup_backup.sh files to each node into the /usr/local/share/trisul-probe or trisul-hub directories and repeat the above steps.
To restore the backup. Locate the backup with the correct timestamp you wish to use and untar the backup file.