Server 2012 Dedupe and iSCSI Volumes
-
A LUN is a "disk." What Windows sees is literally just another drive sitting out there like any normal hard drive.
-
I was just reading the following article: http://blogs.technet.com/b/filecab/archive/2012/05/21/introduction-to-data-deduplication-in-windows-server-2012.aspx.
This point in particular stood out to me:
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 deduplicated. -
Yes, of course. Deduplication is at the filesystem layer. If you move a file system to a different machine that can't read that filesystem, it can't read it. This is an inherent property of dedupe and has nothing to do with Windows.
-
The limitations of dedupe in portability are no different than encryption or compression.
-
What about block-level deduplication? I guess that doesn't apply to the Windows model.
-
@art_of_shred said:
What about block-level deduplication? I guess that doesn't apply to the Windows model.
Normally you just do one or the other.
-
one or the other what?
-
-
@Dashrender said:
@art_of_shred said:
one or the other what?
Block Level or File level, not both.
Exactly
-
@art_of_shred said:
What about block-level deduplication? I guess that doesn't apply to the Windows model.
The block level data is on a Drobo, so that is not an option in this case. If it were NetApp or something like that, it might be a different story.
