Skip to content
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

Retention policy should respect hostname #247

Closed
berti34 opened this issue Apr 24, 2024 · 3 comments
Closed

Retention policy should respect hostname #247

berti34 opened this issue Apr 24, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@berti34
Copy link

berti34 commented Apr 24, 2024

It appears that the retention policy of a plan results in the deletion of snapshots from other servers when utilizing a centralized restic rest server.

How can I configure the "forget" jobs to respect the hostname, so that snapshots from other hosts will not get removed?

@berti34 berti34 added the bug Something isn't working label Apr 24, 2024
@berti34
Copy link
Author

berti34 commented Apr 25, 2024

The forget job depends on the "plan"- name. So I attached the hostname to the "plan" name - and it works as expected.
Maybe this should be documented more explicitly in the forget documentation here:
https://garethgeorge.github.io/backrest/docs/operations#forget

@berti34 berti34 closed this as completed Apr 25, 2024
@garethgeorge garethgeorge reopened this Apr 25, 2024
@garethgeorge
Copy link
Owner

hey, actually going ahead and reopening this — sorry for not commenting earlier. Glad you found a workaround!

As I look towards better support for multi-host management this is something I’ll want to fix, will track here.

@garethgeorge
Copy link
Owner

Will be addressed by #256 , this is looking likely to be a change that requires user intervention to set a hostname for their installs. Saving it for the 1.0.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants