Full backups

Full or comprehensive backups are disaster-recovery-grade images of a Plixer Scrutinizer instance and include the following elements of the filesystem:

• Application data and collected NetFlow in the PostgreSQL database

• Host index data in BadgerDB databases

• Plixer Scrutinizer’s third-party encryption key - /etc/plixer.key

• Apache Server TLS certificate and key

Important

• The license key (if the instance is a primary reporter) and the TLS certificates and keys generated by Plixer Scrutinizer are not backed up and cannot be restored.

• Any files not included in full backups must be manually backed up and restored, including:

  • Custom threat lists created under /home/plixer/scrutinizer/files/threats

  • Custom notifications created under /home/plixer/scrutinizer/files

  • LDAP authentication certificates

• Creating full backups
• Restoring from a full backup
• Alternative backup methods
  • Backup to a second Plixer Scrutinizer instance
  • Local backups