Better Mirror Repositories, calendar view, second host, scripts, self backup

[franos-bash]

Hello, first of all, thank you very much for Zerobyte, it is very impressive work.

After using it for a while, I have accumulated some ideas that I would like to share:

1. Better Mirror Repository Configuration

It is possible to add a repository as a mirror after every job on the backups tab, that works fine as it is today, however, it would be nice to add a repository as a mirror on the repositories tab, so the repository would automatically sync to the original after every single job.

2. Calendar View

I would love to see all my backup jobs in a calendar view, so I could visually notice available gaps for a new schedule, or see if there are too many backups scheduled in a given time.

3. "Second Host" or "node"?

Basically, I have zerobyte set up to send files to a local NAS, and I just sync every snapshot to 2 mirrors, so, after sending to the NAS, the server acts as a middleman to sync the repos to the cloud mirrors, and the NAS just sits there. It would be amazing if there was a way to add the NAS as a node to the zerobyte dashboard, so it could be controlled by the main host, and be more independent, syncing itself to the mirrors.

Having this second host ready would also be great in case of a disaster recovery where the zerobyte host itself is lost. the node could assume the role of the main host until the data is restored to a new machine.

I have plans to set up zerobyte on my NAS, copying the original container, but disabling all jobs, so if something goes wrong, I have a second instance ready to restore the original, with access to my volumes and repos.

4. bash scripts

would be nice to be able to execute scripts before jobs. Also, the only way to trigger a job is through the schedule, it would be interesting if I were able to trigger a job trough a webhook or some other way, for example, I could set up my minecraft server to send a request to be backed up after a session, when the server pauses because there are no players. it would remove unnecessary snapshots if no one plays for a while.

5. self back up

So, there is not much of a point to back up zerobyte data to itself, since I can't restore it with itself... would be cool to automatically back up the container data to the repositories, I am currently running a cron job that does this, backs up my zerobyte.db and compose.yml with tar to the same directory as the repositories. In case of a disaster, having access to any of my mirrors would mean an easy way to restore all my data because the container would be super easy to set up.

For your attention, thank you very much.