@droolio@feddit.uk I see what you’re asking. You’re wondering if, instead of storing a duplicate file in a backup set that already contains it, I could use a hardlink to point to the file already stored in another set.

I have a system where I create a backup set for each day of the week. When I do a backup for that day, I update the set, or if it’s out of date, I replace it entirely with a fresh backup image (After 7 backups to that set). But if the backup sets became inter-dependent, removing or updating one set could lead to problems with others that rely on files in that set.

Does that make sense? I am asking because I am not familiar with the utilities you mentioned and may be taking your post wrong.