Tommy

Yes I am, logs clearly show the hardlinks as file => file

I'm going to call this resolved, not sure what happened but I deleted the folder containing all the HL's on the destination side and run the backup again, and all is well now.

Also just to confirm the source and where the HL's are stored I have attached a screen grab showing the tree levels etc. Blue is the top directory, Yellow is where the HL's are stored and the red is the Level 1 source of the HardLinks. The Destination drive is a mirror of everything in the Blue Directory.

Attached is a screen grab of the Unraid interface, the top Drive is the Source and the bottom the destination. As you can see the "used " space is different to the exact amount of the HardLinks directory (attached in the 2nd scren grab)

Also just to confirm the source and where the HL's are stored I have attached a screen grab showing the tree levels etc. Blue is the top directory, Yellow is where the HL's are stored and the red is the Level 1 source of the HardLinks. The Destination drive is a mirror of everything in the Blue Directory.

Also just to confirm the source and where the HL's are stored I have attached a scren grab showing up the tree levels etc. The Destination drive is a mirror of the source after I run the LB sync apart from the HL's taking up the actual space of 547gb on Unraid

Also just to confirm the source and where the HL's are stored I have attached a scren grab showing up the tree levels etc. The Destination drive is a mirror of the source after I run the LB sync apart from the HL's taking up the actual space of 547gb on Unraid

Hi Loukas, thanks for your time here mate, much appreciated. Yes I can confirm that "preserve symlinks" is indeed checked and also the "Preserve Hard Links" and the data in question has used the Hard-link process. I have attached an image to confirm