This article describes some known issues that may occur after you enable data deduplication on CSV.
Issue 1The LastWriteTime property of a file is changed to the time when the file is processed by a data deduplication optimization job. Additionally, the archive bit of the file is reset when the data deduplication optimization job is finished.
This behavior does not affect production performance or limit access to the files that are stored on the CSV. However, this behavior may affect some backup applications that use the archive bit or the LastWriteTime property to detect incremental changes of files. For example, when the file properties are changed by a data deduplication optimization job, the backup application may be triggered to back up the files again.
Issue 2When you use the Update-DedupStatus cmdlet to query a data deduplication job status on a CSV volume from a passive (non-coordinator) cluster node, you receive an error that resembles the following:
Data deduplication cannot run this cmdlet on this CSV volume on this node. Try running the cmdlet on the CSV volume resource owner node.
This behavior is expected because the job status can be queried only from the coordinator node. To obtain the status of the data deduplication job, log on to the coordinator node, and then run the Update-DedupStatus cmdlet.
Article ID: 2906888 - Last Review: Nov 19, 2013 - Revision: 1