Windows Repository with Data Deduplication error: "The requested operation could not be completed due to a file system limitation"

Recommended File Record Size

A "Bytes Per FileRecord Segment" value of 1024 would indicate that the NTFS volume was initially formatted with the default file record size (FRS).

Based on advice from Microsoft and reported experiences of other customers, issues related to file system limitations when using Windows Data Deduplication are reduced or eliminated when the NTFS volume is formatted with 'large FRS', which sets the FileRecord Segment value to 4096. However, it is possible the same error message may occur later if the 4096 Bytes Per FileRecord Segment limit is hit.

Critical Note: It is impossible to change the FRS value without reformatting the volume, which results in losing all data on that volume.

For more information, review Microsoft Documentation: Formatting requirements for large files.
 

Workarounds

As this issue is related to filesystem limitation, there is no simple fix; instead, there are ways to work around the limitation by changing how restore points are created or by changing the underlying filesystem.

• Because this issue is related to the individual backup file size and its associated FileRecord size, it is less likely to occur when Per-Machine backup files is enabled for the repository. This will cause jobs containing more than one machine to create separate restore point files for each machine, thereby ensuring restore points are smaller than restore points created containing multiple machines.
  ^{Note: Per-machine backup files became the default setting for all repositories starting in Veeam Backup & Replication version 12.}
• If storage space is available, stop all Veeam Backup & Replication operations, relocate all restore points on the current volume to another location, reformat the volume with large FRS, and then move the restore points back to the newly formatted volume.