Restoring from a backup

It’s important to restore to an instance whose version matches that of the backup file. For example, if your backup is that of Plixer Scrutinizer v19.2.0, use a freshly deployed v19.2.0 instance as the restore host.

Plixer Scrutinizer includes a restore script located at /home/plixer/scrutinizer/files/ on the filesystem.

Some steps beyond what the restore utility provides are required and will vary depending on what type of Plixer Scrutinizer node is being restored.

Before using the restore utility

Be sure a backup file is available at the expected location, $BACKUPDIR or /var/db/big/restore by default. The utility will attempt to find Plixer Scrutinizer backup files in the directory and prompt for restoring from any it finds.


Restores are destructive to both the existing Plixer Scrutinizer instance and the backup file itself. It’s best to restore from a copy of a backup.

Considerations after restore

You will need to re-register the restored instance from the Plixer Scrutinizer Primary Reporter. If the deployment is stand alone that will mean registering the instance with itself.

Distributed deployments will require ssh access from the Primary Reporter to the restored instance.

If you are restoring the Plixer Scrutinizer Primary Reporter itself and its Machine ID differs from that of the backup instance a new license key will be required.