rustic-rs / rustic_scheduler Goto Github PK

Statistics about backup runs (OK/disconnected/failed with error on the client) are already saved, but not used so far. They should be accessible by the web-server on the rustic_scheduler server.

Allow to configure the total number of backup jobs backing up in parallel into the repository managed by rustic_scheduler.

Maybe also add the possibility to specify the number of total backups run which are allowed to run in parallel on each client - configured per client group.

Allow a possibility to manually start a specific backup out-of-schedule.

This could be done, e.g. using a web-interface, for instance the dasboard #4 .

Add a dashboard webpage which shows state of of backups of each client but also some overall state like "all backups schedules did run OK" or even allow digging into it by client groups, etc...

related to #3

When clients are not connected, but reconnect, the last missing backup for each source should be re-scheduled.

Allow to manually start a restore of a chosen snapshot+path onto a client to a given directory.
Maybe also allow to schedule this restore to a given time.

Hi,
I'm trying to migrate from restic to rustic and get some benefits of config files.

There are tons of wrappers around restic. I'm personally using my own that also stores configuration on remote side. And I want to get rid of it :)

So I want to propose some discussion about this feature. What I would like to have is:

• Make sure that backup list (names, schedule, excludes) are configured on remote side.
• Have per-host exclude list (with partial sharing)
• Do self-update if needed using my own build (basically tested/approved build)
• Upload logs

Ideally I would like to just add rustic poll-do-geverything to /etc/cron.hourly and let it do everything needed (basically just check and do backup if needed). cron.hourly is used here to make sure backup is retried in case of network failure.

Right now I've custom wrapper for restic and I'm using rest-server as backend for this. Just extra restic-like repo is hijacked and reused to serve this. But I think we can think about extra directory layout.

PS. Most likely I'll try to contribute code if it's interesting

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update actions/checkout digest to a5ac7e5
• chore(deps): update actions/download-artifact digest to 65a9edc
• chore(deps): update embarkstudios/cargo-deny-action digest to 3f4a782
• chore(deps): update obi1kenobi/cargo-semver-checks-action digest to c730648
• chore(deps): update swatinem/rust-cache digest to 23bce25
• chore(deps): update taiki-e/install-action digest to 9c2797b
• fix(deps): update rust crate anyhow to v1.0.86
• fix(deps): update rust crate axum to v0.7.5
• fix(deps): update rust crate chrono to v0.4.38
• fix(deps): update rust crate cron to v0.12.1
• fix(deps): update rust crate log to v0.4.21
• fix(deps): update rust crate serde_json to v1.0.117
• fix(deps): update rust crate toml to v0.8.13
• fix(deps): update serde monorepo to v1.0.202 (serde, serde_derive)
• fix(deps): update rust crate clap to v4.5.4
• fix(deps): update rust crate clap_derive to v4.5.4
• fix(deps): update rust crate env_logger to 0.11
• fix(deps): update rust crate rustic_core to 0.2
• fix(deps): update rust crate serde_with to v3.8.1
• fix(deps): update rust crate tokio to v1.37.0
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): lock file maintenance

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

• https support
• authentication of clients before sending repo information (including password)
• authentication of the server (to allow trusting the clients to run the backup)