I’m using the @saspus docker template on my Unraid server and just bought the personal license. I had 3 backup sets running to one B2 bucket but it wasn’t firing off on the designated schedule, so I was attempting to figure that part out. While looking at the settings in the template, I noticed I didn’t specify a config folder, so it dumped the machine-id
, licenses.json
, settings.json
, etc in the root of /mnt/user/appdata/Duplicacy
. I then set the config folder and applied changes. Not thinking clearly, I deleted the files sitting in root.
Searching in this forum I was able to “adopt” the previous backup data and reapply the license to the server/container. But I’m curious, will I now need to reconfigure the backup sets I had? Or is there another way to recover that? I’m assuming that answer is no without a backup of the original config directory, but thought I’d check.
Assuming the answer is in fact ‘no’, if I recreate the exactly backup sets in Duplicacy WebUI, and point it to the exact b2 bucket, am I going to run into any difficulty running new backups? Will it see the existing chunks and deduplicate accordingly?
And if anyone can lend a hand on the scheduling thing, that would be great. I saw that you need to create a new variable DWE_PASSWORD
but I’m not understanding which password that needs. Is it the master webUI password? Or the encryption password for the B2 storage?