[Borgbackup] 'borg list' on bigger repo runs for days.

[David Krause]

Dear List,


borg was able to repair the backup

borg check --repair /path/to/repo

it just took about a week to do so.
The thing i take with me is that i'll try to finer granulate the backup, 
not backup the storage,
so that i'll not get such huge backups of gt 2.2PB (huge for the 
hardware borg runs on.)

Another lesson learned is that i will not prune after every backup 
(daily), but once every weekend.
So in the case i have to get data from the backup i can cancel the 
running backup and not leave
the repository in an unclean state.

For me the case is closed, thank you for your help!


Mit freundlichen Grüßen / With kind regards

David Krause
IT
Institute of Biochemistry II

Gustav Embden-Zentrum der Biochemie
Goethe University Frankfurt - Medical Faculty

University Hospital - Building 75
Theodor-Stern-Kai 7
60590 Frankfurt am Main
Germany

+49 (0)69 6301 84971 (Phone)
+49 (0)69 6301 84975 (Fax)
krause at biochem2.uni-frankfurt.de

Am 08.07.2020 um 13:11 schrieb David Krause:
>
> Am 08.07.2020 um 11:15 schrieb Dmitry Astapov:
>>
>>
>> Now, whether this means that borg intends to read 1000T at 40mb/s or 
>> not - I am not sure. You can try adding "--debug" to your list 
>> command and see if it adds any clarity.
>>
> hopefully not..
> I'll cancel the current job and try "--debug"
>
>
> Am 08.07.2020 um 12:12 schrieb Thomas Waldmann:
>>> This is ubuntu's borg 1.1.5
>> Please reproduce with borg 1.1.13.
>>
>> There's a PPA for ubuntu from the package maintainer with recent borg.
>>
> I now try the same with the newest stable from the site.
>
> borg-linux64 1.1.13
>
> root at backup1:~# ./borg-linux64 -p --debug list 
> /mnt/backups/backup_CommonStorage/
> using builtin fallback logging configuration
> 35 self tests completed in 0.08 seconds
> Replaying segments   0%
>
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup