https://docs.mitigator.ru/v26.04/en/tags/maintenance/ Recent content in Maintenance on BIFIT Mitigator Hugo -- gohugo.io en https://docs.mitigator.ru/v26.04/en/maintenance/memo/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/maintenance/memo/ Providing Technical Support Based on the MITIGATOR Version The status of MITIGATOR versions is indicated in the Version History list. Actual – the latest released stable version (the first one in the “Version History” list): technical support is available; receives bug fixes; may receive new functionality; documentation is kept up to date; testing is focused on this version. Supported – two major versions prior to the actual one (the second and third in the “Version History” list): https://docs.mitigator.ru/v26.04/en/maintenance/admin/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/maintenance/admin/ Ensure network security of the server. Monitor free disk space. Manage logs. Keep the system up to date. Periodically backup database. It is recommended to set up monitoring of the status of the server on which MITIGATOR is installed using Zabbix, Nagios or a similar solution. Network security In the basic package, the system is designed for the management interface to be located in a secure network segment and does not in any way restrict access for unprotected additional interfaces, such as Grafana. https://docs.mitigator.ru/v26.04/en/maintenance/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/maintenance/ The MITIGATOR team is responsible for the provided software and solves issues directly related to the protection system. The tasks of system administrators are to administer and maintain the system and the server. System maintenance includes the following topics: Version Support Policy Compatibility Policy Administrator Tasks Backup Update Configuration Change Previous Version Restore Links to official Docker and Docker Compose documentation. https://docs.mitigator.ru/v26.04/en/maintenance/backup/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/maintenance/backup/ The following system components can be backed up: cluster data - settings made through the web interface and API; instance data - instance-specific settings; metrics (graphs); logs data. Backup is possible only to the same version of MITIGATOR with which the backup was made. Backing up A backup consists of a copy of the cluster data (backup.sql or backup_lite.sql) and a copy of the data of each instance (one or more backup_ownid. https://docs.mitigator.ru/v26.04/en/maintenance/reconfig/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/maintenance/reconfig/ Apply changes to any configuration files in /srv/mitigator: systemctl reload mitigator This may restart the relevant MITIGATOR components. After changing network ports (editing file /etc/systemd/system/mitigator.service.d/nics.conf) run: systemctl daemon-reload && \ systemctl restart mitigator This will turn the MITIGATOR completely off and on again. Related Content Access to the Grafana Interface Administrator Tasks Backup Configuring Tiered Protection with MITIGATOR Core Isolation for Performance Optimization Graphite on a Separate Server Incident Chart Update Period Packet Processor Settings Pgfailover Documentation Previous Version Restore https://docs.mitigator.ru/v26.04/en/maintenance/mbackup/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/maintenance/mbackup/ Warning Поддержка mbackup прекращена, начиная с версии v21.06 Доступен скрипт MBackup для получения в формате JSON-файла основных настроек системы через API, а также для восстановления из полученного файла (только на чистую систему). Такой файл не содержит настроек пользователей, сети, журналов и не может в полной мере заменить резервное копирование. Файл содержит: политики, правила, группы, настройки и переключатели контрмер (кроме GEO) для всех политик и глобальной защиты, настройки автодетектирования, настройки BGP, но не включает настройки сигнализации. https://docs.mitigator.ru/v26.04/en/maintenance/restore/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/maintenance/restore/ MITIGATOR does not have an automatic version restore mechanism. The restore procedure is similar to the update procedure, but the Compose files of the previous version are used. Thus, it is necessary to replace all configuration files, download the corresponding images, restore the database of the required version. All changes made after the backup copy was taken will be lost. Warning Before restoring, make sure you have a backup taken on the system version you want to restore, down to the minor version number.