-
Notifications
You must be signed in to change notification settings - Fork 260
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
Save for all levels at first run. #306
Comments
You could, if you have GNU cp, |
I'm relying on similar workaround currently, but that requires parsing /etc/rsnapshot.conf to get all levels, and also depends on how exactly rsnapshot is implemented, which is why it's supposed to be done in rsnapshot. This also couples with the destructive rotation issue: if we want to rotate earlier before the level is filled up, could be intentional to avoid losing copy after intra-level rotation, or could be my computer wasn't up all day for 24 hourly backup before the daily one, we got a bubble. I believe both issues are originated from the same design choice. Instead of 'mv alpha.(retain - 1) beta.0', it should |
Checklist
My suggestion is ...
If alpha.0 exists but beta.0 does not, create beta.0 from alpha.0 immediately, instead of waiting for alpha.last_retain.
Why I want it
Currently rsnapshot saves in an "overflowing" manner, e.g. first daily backup won't exist until 24 hourly backup.
The problem with that design is, daily backup will never cover things in the first day, and similarly weekly backup never knows about the first week.
IMO the backup windows should be consistent across levels.
From another perspective, if we initially setup hourly+daily, and later on remove hourly, there're 2 issues with current design:
Why should this be in rsnapshot and not implemented using some external tool?
This behavior is purely controlled by rsnapshot.
The text was updated successfully, but these errors were encountered: