My incremental file backups are way to big based on the small number of files that I have changed on the client machine. I searched thru the forums and found a few similar posts but no resolution. In the server log, I am seeing this warning hundreds of times during the incremental file backup:
Creating hardlink from “D:\Backups\urbackup\ClientName\210207-0418\FileName.pdf” to “D:\Backups\urbackup\ClientName\210208-0734\FileName.pdf” failed. The request is not supported. (code: 50). Loading file…
My assumption is that it was trying to create a symbolic link to this file from the previous backup, but this failed so it is copying over the physical file instead. Since this message is in there hundreds of times, this would explain why my incremental file backup is so big. This question is why is this happening and how do I prevent it so I can get my incremental file backups down to a reasonable size?
Server Version: 2.4.13
Client Version: 2.4.11
Both are installed on Windows 10 Machines (2 different machines)
P.S.: I am using Stabilebit Drivepool on the Server computer and the Backups are stored on the Drivepool drive, but are not duplicated. I hope this would not be causing the issue, but thought I would mention it just in case.
P.S.2: In the client log, I am getting hundreds of this warning. Don’t know if this is related or not:
2021-02-08 07:35:58: WARNING: Parent of file with FRN 263742053178067565 (Name “03A900000002CA6D1DF3006C”) with FRN 80220368362537085 not found. Searching via MFT as fallback.
2021-02-08 07:35:58: WARNING: Parent directory not found in MFT. Was probably deleted.