1-800-691-1991 | 9am - 8pm ET

Best Practices for Microsoft Deduplication

KB ID: 2023
Product: Veeam Backup & Replication
Version: All
Published: 2015-04-22
Last Modified: 2020-08-13


You could experience significant slowdown in performance or failures(in rare cases) when performing Backup or Backup Copy tasks to volumes with Microsoft Windows deduplication enabled where resulted backup files are larger than 1TB in size.


The issue comes from Windows deduplication limitations, which could cause significant performance degradation while reading/appending data from/to very large files (more than 1TB). MS Requirements for Data Deduplication:


a) Avoid growth of backup files more than 1TB on deduplication storage, split backup jobs if possible(reducing amount of VMs per job).
b) If size of VMs does not allow splitting, try to avoid Windows deduplicated volumes usage and transfer backup files to another repository without MS Windows deduplication enabled.

More information

Best practices for MS deduplicated volumes as backup repository:

1) It is important to format the volume with large NTFS File Record Segment (FRS) (4096 bytes instead of 1024 by default) as you could face NTFS limitation errors in future. You could verify FRS size with the following command:
fsutil fsinfo ntfsinfo <volume pathname>
Command to reformat NTFS volume with larger FRS (/L):
format <volume pathname> /L

2) Use maximum NTFS allocation unit size(cluster size) of 64Kb.
Considering option mentioned in pt. 1,  two commands should be united into one:
format <volume pathname> /A:64K /L

3) Avoid growth of files more than 1TB;

4) For Backup jobs preferred backup method is Forward Incremental with Active Full backups enabled.

Introduction to Data Deduplication in Windows Server 2012:
Plan to Deploy Data Deduplication:
KB ID: 2023
Product: Veeam Backup & Replication
Version: All
Published: 2015-04-22
Last Modified: 2020-08-13

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.