Loading...
Loading...
This article documents Best Practices, Limitations, and Considerations relating to the use of storage that has Microsoft Windows Deduplication enabled when storing backup files created and managed by Veeam Backup & Replication.
[CRITICAL] Veeam strongly recommends that all Microsoft Data Deduplication tasks be scheduled to operate when Veeam jobs are not operating, as Microsoft Data Deduplication tasks can and will interfere with Veeam backup file creation and manipulation operations. Microsoft recommends that "Optimally, Data Deduplication should have 1 GB of memory for every 1 TB of logical data. For instance, if you are optimizing a 10 TB volume, you would optimally need 10 GB of memory allocated for Data Deduplication (1 GB * 10). This ratio will ensure the maximum performance for Data Deduplication jobs." When using a Windows-based repository with a ReFS volume, native Microsoft ReFS Deduplication should not be used. The ReFS Deduplication included with Microsoft Server 2025 utilizes the same block cloning technology as Veeam's Fast Clone technology; therefore, there is little to no benefit to enabling Microsoft ReFS Deduplication, and it may lead to performance degradation. Veeam recommends that the MinimumFileSize value be set to prevent Microsoft Data Deduplication from causing file locks on smaller metadata (vbm,vacm,vasm) files associated with restore point creation. PowerShell example command:Adjust volume letter as needed.
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.