NTFS maximum hardlink behavior

general discussion
1

I’m continuing to learn about (and like) UrBackup. I’ve read through the forums and understand that when the number of hardlinks to a single file/data exceeds the NTFS maximum, UrBackup will report a warning/error but will continue by creating a full copy of the file/data rather than creating another hardlink. I haven’t yet exceed the maximum number of hardlinks on my NTFS volume yet, but I could foresee it potentially happening in the future.

My questions are:

  1. Since this second full copy of the file/data should have the same hash as the original (I think), does UrBackup then track and use that second full copy and allow another 1023 hardlinks to the copy, or is every subsequent backup of the same hashed file going to throw an error/warning and be a full copy of the data?

  2. If every subsequent backup of the same hashed file is a full copy of the data, is there any plan to change this in a future version of UrBackup to keep the amount of backed up data from suddenly ballooning when NTFS starts hitting its hardlink maximums?

(I’m running UrBackup server v2.0.36 running on Windows Server 2012R2.)

Thanks in advance!