Backups

The database contains devices, checks, readings, user accounts and activation. Credentials for target systems and notification delivery channels may be included in the backup. Keep backups secure.

A consistent SQLite backup can also be created while the service is running:

sudo netzmonitor backup /root/netzmonitor-backup.sqlite3

An existing destination file will not be overwritten. The generated file is assigned restrictive file permissions. Also back up config.json, server.crt and server.key; the database command does not copy these files.

To make a complete copy of the data directory, stop the service first. Example of creating a new backup archive:

sudo netzmonitor stop
sudo tar -czf /root/netzmonitor-daten-backup.tar.gz -C /var/lib netzmonitor
sudo netzmonitor start

Choose a new archive name to avoid overwriting an existing backup. After the backup, check that the service is running again. On a remote data collector, its private configuration and, if applicable, its local buffer must be backed up separately; they are not stored in the central server’s data directory.

The application does not provide a dedicated restore dialog or a restore management command. Restoration is performed on the Linux server with the service stopped. Use an appropriate complete set of data, preserve the correct ownership and file permissions, and only then start the service. If necessary, program files must be reinstalled using the appropriate complete package.