Restic Backup errors due to "stale" lock file

You could try to unlock the restic repo by using the restic-wrapper also mentioned in the Backup and restore — NS8 documentation

In the following examples the backup of the app instance mail1 is used and may need to be adapted.

Show backups and destinations of the mail1 app:

runagent -m mail1 restic-wrapper --show

You should get a result like this:

Destinations:
- 23de8f38-8f4f-5400-97ad-915361d99c9b BackBlaze B2 mrmarkuz (b2:mrmarkuzbackup)
Scheduled backups:
- 1 Backup to BackBlaze B2 mrmarkuz, destination UUID 23de8f38-8f4f-5400-97ad-915361d99c9b

List locks of the repo of backup # 1:

runagent -m mail1 restic-wrapper --backup 1 list locks

Alternatively it’s possible to use the destination UUID instead of the backup ID:

runagent -m mail1 restic-wrapper --destination 23de8f38-8f4f-5400-97ad-915361d99c9b list locks

Unlock:

runagent -m mail1 restic-wrapper --backup 1 unlock
2 Likes