WinServer: What problems can deduplication, vss and wbadmin interact with?

Question

Microsoft

I decided to play around with data deduplication here and got a little crazy. The archive, accumulated over 7 years, "lost" almost 8 times, and it is only a fifth of the total amount of data. Everything else has not been touched yet. But this is a lyric.
The question is: what threatens the interaction of standard deduplication winsrv2012r2 and vss, in terms of storing vss snapshots on a separate volume? In the worst case, the loss of part of the vss snapshots? How does windows backup work with deduplication? As far as I understand, restoring optimized archives with deduplicated data is possible only on winsrv2012r2 (in this case) - these are all possible problems. Am I understanding this point correctly?

Answer 1

The archive accumulated over 7 years "lost weight" by almost 8 times,

It's normal, it happens at 20.

what threatens the interaction of regular deduplication winsrv2012r2 and vss, in terms of storing vss snapshots on a separate volume?

Nothing, shadow copies are not deduplicated.
The loss of a VSS snapshot occurs only when there is not enough space on the snapshot storage volume.
By the way, why do you need shadow copies on a deduplicated volume? This is the archive as far as I understand.

As far as I understand, restoring optimized archives with deduplicated data is possible only on winsrv2012r2 (in this case) - these are all possible problems.

More or less like this.
You can connect the drive to any computer, but it will not be able to read deduplicated files.
The deduplication service must be running.
It is available in Win Server from 2012 and higher, it can also be installed with some desire on desktop versions of Windows from 8k and higher.
Regarding VB ADMIN - it stores data in a disk image, on this disk image all changes are written as shadow copies, this is if we are talking about backup of entire volumes.
And if backup folders - banal zips.
Well, in general, we should not forget that deduplication is an intentional hard fragmentation of the volume, so do not expect a quick read.
Also, deduplication has common mechanisms with BranchCache, and works great in pairs.