I would worry about the Duplicati running a backup doing something that drastically changes the destination. For example, The COMPACT command could run, however the –no-auto-compact option could avoid that. Defense against trojans talks about this some, where the ultimate protection against damage from ransomware is to have a destination that can only be added to… There’s still a lock file, it can probably be worked around, but doing so might have bad results in some cases. Interestingly, Duplicati knows how to avoid other copies of itself using the default port 8200 for the web UI. See Duplicati.Server.exe. This can happen by accident when somebody installs Duplicati as a Windows Service (which starts first and gets port 8200), then starts the Tray Icon (and gets 8300). By default the databases are separate, so the job view is separate. Restore doesn’t need a complete database. For most realistically trying to recreate a lost-disk recovery, you wouldn’t want one anyway, just destination files.