PKaufmann wrote: ↑Apr 05, 2021 3:01 pm
I'd like to know how you are going to proceed as I am in the same situation..
When I set up the repository, I followed the Windows Server Deduplication Part of this guide:
https://bp.veeam.com/vbr/VBP/3_Build_st ... block.html
Also if I disable dedup now and enflate all the files, my disk would be full
Capacity : 21.83 TB
FreeSpace : 11.07 TB
UsedSpace : 10.76 TB
UnoptimizedSize : 21.06 TB
SavedSpace : 10.3 TB
I followed the same article you did when setting our backups up and as it mentioned in the article "In WS2019 dedup is supported for ReFS but will only dedup the first 4TB of a file.", I enabled that also. Been running that for over 2 years now that way. Still running V10 currently and I would not be able to inflate my backups no matter how much I wanted. I have 2 stores with backup data on them and the deduplication rate is very high:
Capacity : 36.38 TB
FreeSpace : 29.81 TB
UsedSpace : 6.58 TB
UnoptimizedSize : 55.78 TB
SavedSpace : 49.2 TB
Capacity : 36.38 TB
FreeSpace : 28.98 TB
UsedSpace : 7.4 TB
UnoptimizedSize : 117.11 TB
SavedSpace : 109.7 TB
Specially on the second volume, the savings are so substantial from the deduplication that there is no options to inflate and keep that drive without deduplication.
Looking at the recommendations here mentioning issues with the ReFS and deduplication, I have run into that issue twice in 2 years where a backup gets that problem. I have set my deduplication delay to 2 days, so the last 2 day backups dont get deduplicated and if the issue rears its head, I move the affected file off the drive and copy it back, this leaves that file without deduplication for 2 days and allows Veeam to do its operations with it just fine.
If the issue is fixed, that is great, but I just want to verify that the article: https://bp.veeam.com/vbr/VBP/3_Build_st ... block.html
is still valid and running ReFS with deduplication is a supported solution as per "In WS2019 dedup is supported for ReFS but will only dedup the first 4TB of a file."?