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

[Feature] Adjust natural time boundaries for forget #4732

Open
ccmgr opened this issue Mar 18, 2024 · 1 comment
Open

[Feature] Adjust natural time boundaries for forget #4732

ccmgr opened this issue Mar 18, 2024 · 1 comment

Comments

@ccmgr
Copy link

ccmgr commented Mar 18, 2024

Output of restic version

restic 0.16.4 compiled with go1.21.6 on windows/amd64

What should restic do differently? Which functionality do you think we should add?

Ability to override the default forget time boundaries
For example Monthly to be First day or Last Day (current default)

End of Week to be Friday or Saturday

What are you trying to do? What problem would this solve?

Backups that run out of hours between 00:00 and 08:00 will be used as retained backup for the month/year
Data changes on the last day for the month/year would be in the first snapshot of the following month/year
Thus Forget Month/Year would not have the last days data when backup completes after 00:00
Add an option to override Default Boundaries

--forget-monthly-boundary First/Last

Did restic help you today? Did it make you happy in any way?

Only started to migrate from Duplicati for backups with large quantity of small files

Much quicker to scan daily/hourly changes the SQLite DB of Duplicati

@ccmgr ccmgr changed the title Adjust natural time boundaries for forget [Feature] Adjust natural time boundaries for forget Mar 18, 2024
@eharris
Copy link

eharris commented Apr 13, 2024

I would love to see this too, as I run my longer-term backups at the beginning of the month/week/day and would like to have the selection keep the oldest rather than the most recent within the given period.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants