Forgive me for doing Google research on this, but I like the question as it could pertain to me someday.
Here's what I've found:
Introduction to Data Deduplication in Windows Server 2012
Portability: A volume that is under deduplication control is an atomic
unit. You can back up the volume and restore it to another server. You
can rip it out of one Windows 2012 server and move it to another.
Everything that is required to access your data is located on the
drive. All of the deduplication settings are maintained on the volume
and will be picked up by the deduplication filter when the volume is
mounted. The only thing that is not retained on the volume are the
schedule settings that are part of the task-scheduler engine. If you
move the volume to a server that is not running the Data Deduplication
feature, you will only be able to access the files that have not been
Which sounds to me like if you tried to move the deduped data it would only copy the 1.3TB.
The same info, roughly, can be found here: Seven Things to know about Windows 2012 Deduplication
'Atomic units' mean that all of the deduplication information about a
given volume is kept on that volume, so it can be moved without injury
to another system that supports deduplication. If you move it to a
system that doesn't have deduplication, you'll only be able to see the
nondeduplicated files. The best rule is not to move a deduplicated
volume unless it's to another Windows Server 2012 machine.
and since in order to "un-dedupe" them you have to run something like:
Start-DedupJob -Type Unoptimization
Requirements for Drive removal for use in other systems, if keeping the data on the drive
1. The OS is Windows server 2012
2. You have configured Data deduplication on the new system.
3. OR, You have removed data deduplication from the drive prior to moving the drive >to a platform that does not support Data deduplication
Note: as mentioned above to get the drives to work without the
documents / files having the appearance of corruption when you attempt
to open them on the new system, you will to install and configure data
duplication on the new system .prior to moving the drives to the new
systems What this means is that you would need to remove data
deduplication from the volume prior to installing the drive in ANY
Operating System that is NOT Windows Server 2012
All that said , since I don't have the means to test it myself...I can't confirm for certain this means it will not re-hydrate the data as it moves, but it appears it won't. I'm sorry I can't confirm 100%. I'd post this is a comment but there's too much to share.