[GH-ISSUE #1] Use a database to store sessions.txt rather than a file #1

New issue

Closed

opened 2026-02-27 08:13:47 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 08:13:47 +03:00

Owner

Originally created by @lucascbeyeler on GitHub (Feb 23, 2017).
Original GitHub issue: https://github.com/lucascbeyeler/zmbackup/issues/1

Today, zmbackup use the file session.txt as a way to store the backup's history. This file is susceptible to failures and zmbackup only use this file because zmbkpose used before the fork. Now, that this application is restructured, is a good time to study a better way to store this log.

Two good candidates are MariaDB and PostgreSQL.

Originally created by @lucascbeyeler on GitHub (Feb 23, 2017). Original GitHub issue: https://github.com/lucascbeyeler/zmbackup/issues/1 Today, zmbackup use the file session.txt as a way to store the backup's history. This file is susceptible to failures and zmbackup only use this file because zmbkpose used before the fork. Now, that this application is restructured, is a good time to study a better way to store this log. Two good candidates are MariaDB and PostgreSQL.