<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>backup :: Tag :: BIFIT Mitigator</title>
    <link>https://docs.mitigator.ru/v26.08/en/tags/backup/</link>
    <description></description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://docs.mitigator.ru/v26.08/en/tags/backup/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Administrator Tasks</title>
      <link>https://docs.mitigator.ru/v26.08/en/maintenance/admin/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.08/en/maintenance/admin/</guid>
      <description>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.&#xA;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.</description>
    </item>
    <item>
      <title>Backup</title>
      <link>https://docs.mitigator.ru/v26.08/en/maintenance/backup/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.08/en/maintenance/backup/</guid>
      <description>The following system components can be backed up:&#xA;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.&#xA;Info All configuration files in /srv/mitigator that are added or changed must be attached to the backup. This includes .env file, which is always configured during installation.</description>
    </item>
    <item>
      <title>Скрипт получения и восстановления конфигурации MITIGATOR</title>
      <link>https://docs.mitigator.ru/v26.08/en/maintenance/mbackup/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.08/en/maintenance/mbackup/</guid>
      <description>Warning Поддержка mbackup прекращена, начиная с версии v21.06&#xA;Доступен скрипт MBackup для получения в формате JSON-файла основных настроек системы через API, а также для восстановления из полученного файла (только на чистую систему).&#xA;Такой файл не содержит настроек пользователей, сети, журналов и не может в полной мере заменить резервное копирование.&#xA;Файл содержит: политики, правила, группы, настройки и переключатели контрмер (кроме GEO) для всех политик и глобальной защиты, настройки автодетектирования, настройки BGP, но не включает настройки сигнализации.</description>
    </item>
    <item>
      <title>Previous Version Restore</title>
      <link>https://docs.mitigator.ru/v26.08/en/maintenance/restore/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.08/en/maintenance/restore/</guid>
      <description>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.&#xA;Warning Before restoring, make sure you have a backup taken on the system version you want to restore, down to the minor version number. For example, to restore v23.12.3, you need to use a backup taken on v23.12.3. Therefore, it is important to make a backup (especially of the database) before every update, including updates within the same major.</description>
    </item>
  </channel>
</rss>