I’m not sure when it started, but I’ve noticed three shares on my unRAID server that I’m pretty sure Duplicati is creating. I have backups set to every day, but there are always three shares with named like “ab_20250216_010001”. In duplicati, I have the retention set to last 3 back ups, but I thought that was in Backblaze, where I upload to in duplicati.
How do I rid of these shares? Is it simply the backup retention, or is there another setting I’m missing.
THank you.
Based on what theories? Feel free to cite external sources too. I don’t use Unraid, and don’t think Duplicati knows about unRAID (also supported by search at https://github.com/duplicati/duplicati).
Those look like the numbers might start with a YYYYMMDD day (start and end are more obscure). Do the possibly-a-date name parts move weekly (Sundays, if dates)? Could they be by a cron job?
I don’t think it’s Duplicati work, but you can change retention to 2 or 4, or have Duplicati down when you forecast a share change. Observing same share changes would seem to say it’s not Duplicati.
You can look in the Backblaze web UI. All Duplicati backup versions are in one folder as specified on Destination screen. A backup version makes a bunch of files with dblock and dindex in names, then finishes with one with dlist and UTC date in the name. There are no separate folders created.
If you don’t want to look in the Backblaze UI, you can see the uploads thing in Job → Show log → Remote. If you want a list of all the files present at some time, find a list entry and click on that.
I was mistaken. This is coming from the “Appdata Backup” plugin for unRAID. It runs on the same day and backing up the same files as duplicati. I must have set this up years ago and forgot, and a recent update started creating shares. Sorry to bother.
I’m not seeing a setting in appdata backup that creates shares, but off to google I go.
This entry in my appdata backup logs proves it.
