We are running 126.96.36.1995 for Hyper-V. I'd thought to first ask this here before logging a ticket as maybe I'm overlooking something very obvious. I have a seperate job for our Exchange 2016 environment. It's always been just one Edge-server and one mailbox server with about 950GB of disks and about 700-800GB of actual data including the OS itself. The Exchange stores are about 500-600GB. About 2 months ago I've installed another Exchange mailbox server and formed a DAG for redundancy and stuff. Added it to the job. In the job I have inline dedup enabled and optimized for WAN as I have to be restrictive on space and want as good dedup results as possible.
Now something that looks strange to me. We have 1 full per week, rest incrementals. As both mailbox hosts host about the same data, as expected the dedupe results of the job are quite good:
But when the full runs, it doesn't seem to dedupe at all:
This is also reflected in the .vbk file. Size of the full is over 1.1TB while there is about 600GB of 'identical' data. Now I don't see why the full job has practically no dedupe at all, as even the incrementals show that quite a bit of the changes that day can be dedupe quite well. If I have 6 days of quite good dedupe, I would expect the full backup to have at least more than 1.0.
Don't full jobs dedupe from Veeams perspective?