I’m running backup’s using Restic to my S3 provider and I’ve begun to see the following error messages on the backups failing:
Fatal: unable to create lock in backend: repository is already locked exclusively by PID 740.
- What is the process to remove these locks? Simply kill the PID?
- Any idea why these locks are occurring and stopping my backups for working?
I’ve done a bit of research and learned of a “restic unlock” command I can use. But I need to know the repository location: Here is the error when I issue this command:
Fatal: Please specify repository location (-r)