Suddenly getting warnings (IOException) because .db files being used by another process

[happysw]

Hello everyone!

So I’ve been using Duplicati for months now, without any issues, to backup my Docker Volumes. Haven’t gotten any errors at all. However, after updating to the latest version I keep getting warnings that certain database files couldn’t be backed up because they were being used by another process. It makes sense, since Docker is running at the time of the backup, but I’m wondering why I get these errors now when it was working fine before. Is it just the warning that is new, and the files haven’t been backed up before either, or is there something new that prevents them from being backed up?

[ts678]

@happysw

is there something new

@kenkendk

This is caused by the update to .NET8 where Linux advisory file locking is now honored.

Read locked files

The docs presentation is kind of interesting, as explanation of this is in a Docker section. but problem of this sort probably applies to all Linux. Is setting up LVM on Docker even feasible?

I wonder if anyone’s ever done it? I know the scripts are kind of picky about exact LVM setup.

[kenkendk]

@ts678

The docs presentation is kind of interesting, as explanation of this is in a Docker section. but problem of this sort probably applies to all Linux.

I could not find a good place for this kind of detailed instructions. but to recap, you can either:

• Add --ignore-advisory-locking=true to the job or general options
• Set the environment variable DOTNET_SYSTEM_IO_DISABLEFILELOCKING=true

This works on any Linux setup.

[davidrnewman]

I should know this but I don’t. Where do you add --ignore-advisory-locking=true? In which script?

[kenkendk]

@davidrnewman

Where do you add --ignore-advisory-locking=true?

That depends a bit on how you are using Duplicati, but the most common place would be in the application settings (so it applies to all backups):

Make sure you check the box as shown in the image, and then click “OK”