Context: I have lost recently more than 400Gb uploaded to Backblaze B2. I unfortunately and stupidly configured two backup jobs pointing to the same bucket in B2 (I didn’t create subfolders at that time within the bucket). When the latest job finished, it verified the data and destroyed everything. I had to cancel the job when I realized I went from 400Gb to 3Gb…
Suggestion: warn user when he is creating a job which use destination which is already existing in another job. If not possible to do this check, then highlight a warning in red so that people understand the risks.
Another alternative could be to force the option of appending a name to the backup files, so that at least these files are different and there is less risk of messing up.
Just my two cents