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 Request: Higher limit for available space on backup medium. #1903

Open
khenty opened this issue Oct 13, 2024 · 1 comment
Open

Feature Request: Higher limit for available space on backup medium. #1903

khenty opened this issue Oct 13, 2024 · 1 comment
Assignees
Labels
Feature requests a new feature Feedback needs user response, may be closed after timeout without a response

Comments

@khenty
Copy link

khenty commented Oct 13, 2024

Follow-up of #1880

On my installation of backintime-qt, the largest value I can enter for the limit on available backup space is 1000 GB. I propose increasing this limit as a workaround for backintime's maxing out my 12 GB backup drive (100%). It's also possible that there's a bug here. Given that I'm doing daily backups, the backup drive is maxed out about once a week. I correct the problem by manually removing snapshots ("rm -rf SNAPSHOT_PATH [SNAPSHOT_PATH ...]).

diagnostics.txt

@buhtz buhtz added the Feature requests a new feature label Oct 14, 2024
@buhtz buhtz self-assigned this Oct 14, 2024
@buhtz
Copy link
Member

buhtz commented Oct 14, 2024

Hello khenty,
thank your for your request.

What do you mean by "maxed out"?

Currently the "limit" can be set to 1.000 GB (~1 TeraByte). The meaning is not a limit, but BIT will start to remove snapshots if there is less than 1.000 GB free on your volume. Do you really want more than 1.000 GB kept free?

How can this help you? How big is one of your snapshots?

As a beginning I would suggest, that you modify your BIT installation by yourself. It is just one line.

self.spbFreeSpace.setRange(1, 1000)

There the value 1000 is the limit of the that spinbox. Just put two more 0 to it and let's see if this really helps you.

Regards, Christian

@buhtz buhtz added the Feedback needs user response, may be closed after timeout without a response label Oct 14, 2024
@buhtz buhtz added this to the 3rd release from now milestone Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature requests a new feature Feedback needs user response, may be closed after timeout without a response
Projects
None yet
Development

No branches or pull requests

2 participants