understanding disc usage #8433
Comments
|
Did you forget to add a call to You can compact after each |
|
Hallo Thomas, I did run borg compact manually, but the issue persists. Greetings, |
|
Well, you could use borg mount (and a file manager) or borg list to look what's inside your backups, to check if you backed up frequently changing stuff that should not get backed up and then adjust your excludes accordingly. If you have logs from your backup runs ( Due to the deduplication it is hard to find out otherwise (e.g. borg info) what the issue is. |
|
Hello, hm, do you think that this is something that could be added as a feature in future? Using borg mount, I would really have to go through folder by folder, as I do not really have a suspect. Greetings, |
|
I am now running borg info in a script and process the json output. If I see it correctly, each of the backups did add ~1.5GB, right? Greetings, |
|
The way to interpret that is rather like: Such an archive references NOW about 700MB .. 4GB which are not used by any of the other archives NOW. If you delete any of these, the numbers will change. |
|
Related: #71 |
|
Thanks for working on the analysis feature and for your explaination. |
|
Hello, I need to come back to this. If I add all the values in "Deduplicated Size", I get about 300GB. Best regards, |
|
What you added up is the space only used by one (not by multiple) archive(s). But of course there is a lot of overlapping use which occupies the remainder of the space. |
|
Hello Thomas, But should not the Compressed Size of this first backup an the sum of the Deduplicated sizes of the other backups add up to the total space? In any case, what I do not get: In the last three weeks, borg wrote 680GiB. Why? Greetings, |
|
|
|
Hello again, thanks. I understand your graphic. I did not recover the space. Greetings, |
|
See the docs page of https://borgbackup.readthedocs.io/en/stable/usage/compact.html |
|
Thanks for your reply, Thomas. Apart from that, I now get the message: Is that cause for concern? In the end, this did not bring the success I expected: Greetings, |
|
2 possibilities:
|
|
Hello, there may have been further backups, but none that I did not delete (the latest is from 2022, I had 4TB also in October). Best regards, |
|
Not sure, but maybe it helps, just try it. If you have a lot of archives in there, you can use |
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Of course!
Is this a BUG / ISSUE report or a QUESTION?
QUESTION
Describe the problem you're observing.
My backup-disc is full, although much larger than the source disc.
I would like to understand, what is using my backup-disc space.
borg info is too top-level (giving per - archive information only) and also is difficult to read as it provides too much information.
Is there no way to get a better overview? I could imagine for example, that I accidentally backed up some often changing DB or VM file and would not know, how to identify that.
Greetings,
Hendrik
The text was updated successfully, but these errors were encountered: