Dedupe-Friendly For Win2016?

[B.F.]

Greetings,
Looking for some advise on the best way to setup a backup job where the destination is a Windows Server 2016 volume that is running Windows deduplication. This link is a little older but talks about using Dedupe-Friendly. However, a newer blog says that compression should be set to None. The first states

In my experience, enabling Veeam dedupe and compression significantly speeds up job processing and do not interfere with Windows deduplication

Also

Dedupe-friendly compression saves about 10-20% on the initial VBK/VIB file size. About the same (20-30%) is lost at Data Deduplication stage. Significantly faster restores and slightly faster instant recovery.

And

Effectively you are trading some hard disk space overall (because of less dedupe) for some up front network and disk bandwidth savings.

Unless a lot has changed with Veeam and Windows 2016 since that first link was posted, seems to me a little bit of a balancing decision. More dedupe space saved but will have slower Veeam jobs, set it to None? Faster Veeam jobs at the cost of loosing some dedupe space, set to Dedupe-Friendly?

Thanks for your input.

[foggy]

Depends on the environment - since compression is performed by a proxy, switching to a higher level (dedupe-friendly) will require more proxy CPU, however, in case it is not a primary bottleneck, you might not notice the difference in overall job duration. In case network is the bottleneck, this would even save you time.