Operational Defect Database
BugZero found this defect 3638 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb1893
The requested operation could not be completed due to a file system limitation
Last update date:
9/20/2021
Affected products:
Veeam Backup & Replication
Affected releases:
11
Fixed releases:
No fixed releases provided.
Description:
Challenge
Transform operations of a large file located on a Windows Server 2012/2012 R2 deduplicated volume fail with the error:
Cause
Veeam is not able to write any data to the affected file because of an NTFS limitation. Manual un-deduplication (Expand-DedupFile) of this file also fails with the same error.
Solution
The backup repository must be located on a volume formatted with the large FRS using the command:
Workaround
Disable Windows deduplication Un-dedupe backup files: copy backup files to a temporary folder delete original backup files move copied files back to the original location. Disable NTFS compression on backup repository volume.
More Information
For Windows Server 2008(R2) please refer to Microsoft KB for a detailed description of the issue:http://support.microsoft.com/kb/967351 This issue is resolved in Windows Server 2012(R2), however formatting with the large FRS using the command “Format <Drive:> /FS:NTFS /L is still needed. Important: the command Format <Drive:> /FS:NTFS /L erases all data from the drive. Additional information regarding the suggested configuration of Server 2012 dedupe for backup storage can be found in this article: http://technet.microsoft.com/en-us/library/dn891438.aspx Depending on the total size of the volume to be formatted you may have to set the cluster size during the format process. Please reference this article to determine which cluster size is needed. http://support.microsoft.com/kb/140365/ For more information related to this issue please see this forum post: http://forums.veeam.com/veeam-backup-replication-f2/error-related-to-file-system-limitation-t21448.html Please note: reformating the volume with /L flag usually helps. However, the same error message may occur later if the 4096 Bytes Per FileRecord Segment limit is hit.
