Prevent re-use of same target backup folder

UX
1

I got it with current release to enter in two differnt backup jobs to set up the same target backup folder.

2nd job failed after 1st job already finished before.

Final result was, that directly after this attempt to re-use one single folder for my backuped files, that the Duplicati-db was corrupted. Didn’t got it fixed with the board tools.

Resolution was, to set up both jobs completely from scratch (it was necessary to delete them before!) and even the backup.

Wish: it should not be possible to reuse same folder in seting up a job via GUI, if it is known that this will corrupt a job’s backup. Or you enable this feature if it is one :wink:

So you can avoid disappointments for users rely on their backups

2

Technically the –prefix option allows use of the same folder, but that could be accounted for if this gets done.

Another design decision might be whether to simply check within the Duplicati database at backup creation, or to try to protect against collisions with another Duplicati instance by checking destination at backup’s run. There are already some checks for what look like excess files, but apparently more safeguards are needed. Command line Duplicati runs don’t have jobs set up in the server database, so can only do run-time checks.