DumbMonit

ИнтеграцииХранилища и резервные копии

Мониторинг Kopia в DumbMonit

Бета

A Kopia server through its REST API: the last snapshot of each source (age, errors, size, files), sources that missed their schedule, and the repository connection.

ДокументацияОфициальный сайт: Kopia

Описания на английском, как в самом продукте. Подписи на странице — на вашем языке.

Что проверяет DumbMonit

Built from the Kopia server's source and API behaviour, not yet tested against a real server. Tell us what your server answers differently. A Kopia server through its REST API: the last snapshot of each source (age, errors, size, files), sources that missed their schedule, and the repository connection.

Примеры

  • Kopia server
  • KopiaUI
  • Kopia in Docker

Как подключается

Что понадобится

  • Server user name and passwordThe user name and password the Kopia server was started with.

Учётная запись не нужна.

Сетевые порты, которые нужно открыть

  • 51515/TCPServer API (HTTPS, default)
Шаги настройки: Start the Kopia server with its own user name and password
  1. On the machine that runs the backups, start the Kopia server with a generated certificate and its own user name and password.

    kopia server start --address=0.0.0.0:51515 --tls-generate-cert --server-username=dumbmonit --server-password=PASTE-A-LONG-RANDOM-PASSWORD
  2. Check that the repository is connected to that server and that the DumbMonit server can reach port 51515.

  3. In DumbMonit, enter the server address (for example nas.lan) with that user name and password.

  4. Tick Accept an unverifiable certificate: the generated certificate is self-signed. If the server runs with --insecure, choose the http protocol instead.

Обратите внимание. Kopia's API has no read-only account: the server password also lets its holder start and delete snapshots. DumbMonit only reads, but keep port 51515 on your local network.

Ещё в категории «Хранилища и резервные копии»