Will restic deduplicate if I change the directories to be on the parent instead of specific ones?

I recently changed my autorestic config file from backing up:

      - /mnt/user/backup
      - /mnt/user/backups-other
      - /mnt/user/domains
      - /mnt/user/downloads
      - /mnt/user/familia
      - /mnt/user/isos
      - /mnt/user/media
      - /mnt/user/media-ripping
      - /mnt/user/stash

to backing up

/mnt/user
/boot

I am running a backup now and I see this output

Backend: local
> Executing: /usr/local/bin/restic backup --tag ar:location:array /mnt/user /boot
no parent snapshot found, will read all files

So even if no parent snapshot is found does it still dedup so it won’t take up double storage?

Yes, dedupe will work because only the file contents matter for its algorithm, not the file paths or even file names.

Since the paths changed, the files will be rescaned, and the “no parent snapshot” message is shown. The --parent flag can speed up the first backup after a path change (or other grouping criteria, like a hostname change).

1 Like

Thanks! Side question, In this new set of paths I’m also adding a new backend on top of the existing backend I have via autorestic. Is there a way I can do as you suggest and specify the parent but at the same time make sure it does a proper backup to the new backend?

Sorry, but I’m not familiar with autorestic.