[Borgbackup] Lock error

[Steve Schow]

Ok, I will keep that in mind that but that didn’t really answer my question about how to automate the clean up of abandoned locks

On May 15, 2016, at 1:52 PM, Adrian Klaver <adrian.klaver at aklaver.com> wrote:

> On 05/15/2016 12:32 PM, Steve Schow wrote:
>> So I ran into this problem also today while running my first very large backup.  The size of my backup is close to 2TB.  it got most of the way through and then froze for some reason.  I hit ctrl-C and tried to launch it again and got these errors about locks.  Because I was using a remote repository, I found that I had to issue the break-lock command on both computers before I could run my backup again.
>> 
>> I hope this design will get a revisit sometime in the future.
>> 
>> In the meantime, what can I do to automate the handling of this problem?  I want my backup on a cron job.  Anyone have any suggestions for how to automatically clean up the lock problem when it occurs?  Particularly since it has to be cleaned up no both machines?
> 
> My advice would be to not back up 2TB at one time, especially for the first backup. I would use:
> 
> http://borgbackup.readthedocs.io/en/stable/usage.html#borg-create
> 
> PATH                  paths to archive
> 
> to feed it smaller portions at a time. In fact if it where me and depending on what you are backing up I would probably break the backup into smaller repos.
> 
>> 
>> 
>> 
>> On May 14, 2016, at 4:36 PM, Adrian Klaver <adrian.klaver at aklaver.com> wrote:
>> 
>>> On 05/14/2016 03:24 PM, Sergio Belkin wrote:
>>>> Hi,
>>>> 
>>>> When I try to resume an interrupted "borg create" it outputs this error:
>>>> 
>>>> Failed to create/acquire the lock
>>>> /mnt/backup/sergio_backup/lock.exclusive (timeout).
>>>> 
>>>> Why?
>>> 
>>> http://borgbackup.readthedocs.io/en/stable/internals.html#lock-files
>>> 
>> 
> 
> 
> -- 
> Adrian Klaver
> adrian.klaver at aklaver.com