-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEATURE: Extend scope of "PRUNE_BACKUPS_*", to support x amount of backups, and maybe even "x amount of space used" #98
Comments
Yes, that sounds like a great idea. A PR would be welcome, but I'll also queue this up. |
possible partial implimentation with #194 |
I've always thought of doing this with a sort of exponential backoff like how Realms does it. For example,
|
Another way would be to look into some sort of restic powered backup, where the user only need to provide a "configure string" or similar (supporting multiple parameters). But I'm not sure if you'd allowed to bundle that in the solution. Just another input, as I really like restic. |
Restic is already supported https://github.com/itzg/docker-mc-backup?tab=readme-ov-file#restic |
@itzg ; I see. Good to know. But a build in "default easy-mode solution" would be great, too. It's clear that I didn't use Restic that much back in 2022, or, didn't see that as easy, as it can be: |
I don't know or use Restic, so will need to rely on a contributor to add an "easy mode". |
Hi,
I've tried to look through the docs and the code for a "max amount of backups", or "max amount of space" before backup-deletion.
Would you consider to expand the scope to include that?
(Today I filled up our server, by creating a backup every 30 minute 😄. I guess it's overlapping a bit with restic, but I'd like to keep it simple)
Thank you for the solution, btw.
The text was updated successfully, but these errors were encountered: