Warnings About File Access Issues After Upgrade to Duplicati 2.1.0

1

Hey community,
I recently upgraded to Duplicati version 2.1.0 and since then, I’ve been receiving daily email notifications with warnings about certain files not being accessible during backups. Specifically, these warnings indicate that files are “being used by another process.” Here’s the content of the warnings:

```

2025-10-05 XX:00:32 - [Warning-Duplicati.Library.Main.Operation.Backup.FileBlockProcessor.FileEntry-PathProcessingFailed]: Failed to process path: /source/var/lib/docker/volumes/metadata.db
IOException: The process cannot access the file '/source/var/lib/docker/volumes/metadata.db' because it is being used by another process.
2025-10-05 XX:00:32 - [Warning-Duplicati.Library.Main.Operation.Backup.FileBlockProcessor.FileEntry-PathProcessingFailed]: Failed to process path: /source/var/lib/docker/volumes/gitea-data/_data/gitea/indexers/issues.bleve/store/root.bolt
IOException: The process cannot access the file '/source/var/lib/docker/volumes/gitea-data/_data/gitea/indexers/issues.bleve/store/root.bolt' because it is being used by another process.
2025-10-05 XX:00:35 - [Warning-Duplicati.Library.Main.Operation.Backup.FileBlockProcessor.FileEntry-PathProcessingFailed]: Failed to process path: /source/var/lib/docker/volumes/prometheus-grafana_prometheus-data/_data/data/lock
IOException: The process cannot access the file '/source/var/lib/docker/volumes/prometheus-grafana_prometheus-data/_data/data/lock' because it is being used by another process.

These files seem to be related to Docker volumes and other services running on my system. I’ve tried to restart the associated containers, but the warnings continue.

Has anyone else encountered similar warnings after an upgrade? Is there a specific setting or configuration I should adjust in Duplicati to handle these cases more gracefully? Any help or suggestions would be greatly appreciated!

Thanks!

2

Read locked files discusses this in a Docker context. I wish Linux page said its part too.

For regular Linux (unclear what you run), the Docker page gave the following comment:

By default, Duplicati will respect the advisory file locking and fail to open locked files, as the lock is usually an indication that the files are in use, and reading it may not result in a meaningful copy.

and names two ways. One of them is this:

  --ignore-advisory-locking (Boolean): Ignore advisory locking
    When reading files Duplicati can skip files that are marked locked by another
    application to ensure consistency. This flag can disable the check and
    perform optimistic reads of locked files.
    * default value: false
3

:up_arrow: Did the trick for me!

Thank you so much!

1 Like
4

I have updated the Linux page to mention this too.

1 Like