[Borgbackup] Lock error

[Adrian Klaver]

On 05/16/2016 09:03 AM, Steve Schow wrote:
> It hasn’t happened again, so i can’t replicate it.  Well actually I can easily..by simply hitting ctrl-C while its running it ends up in the broken lock state.
>
> However I have low confidence in using borg for automated backups at this point due to this.

Well I use it on multiple machines to back up data from even more 
machines via cron jobs that run day and night and the only problems I 
have had are self inflicted. Namely that I was not paying attention and 
had cron jobs walk over the same repo at the same time. The worse that 
happened was that particular backup failed, but the next succeeded.

>
>
> On May 16, 2016, at 2:18 AM, Thomas Waldmann <tw at waldmann-edv.de> wrote:
>
>> There is a problem why borg can't finish the backup (crashes or gets killed, leaves the lock behind)
>>
>> That is the root cause you need to find and fix.
>>
>>
>> --
>>
>>
>> GPG ID: FAF7B393
>> GPG FP: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393
>>
>> _______________________________________________
>> Borgbackup mailing list
>> Borgbackup at python.org
>> https://mail.python.org/mailman/listinfo/borgbackup
>
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
>


-- 
Adrian Klaver
adrian.klaver at aklaver.com