You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ...]).
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.
Closing this ticket based on the comment above. Feel free to reopen
if the problem still exists. Thank you for your efforts. If you have
any further questions, ideas or encounter any other issues, please
don't hesitate to let us know.
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
The text was updated successfully, but these errors were encountered: