This article describes issues that occur when you run data deduplication in Windows Server 2012 R2. An update is available to resolve these issue. Check out the list of issues that are fixed in this update.
Issues that are fixed in this update
-
Assume that the volume space that is used is around 1.2 terabytes (TB) and that the data deduplication job uses at least 6.5 gigabytes (GB) of memory. In this situation, the job stays at 100 percent for several minutes, and a new job cannot be started.
-
Assume that you try to run deduplication on a Cluster Shared Volumes (CSV) volume in a Windows Server 2012 R2 failover cluster. Data Protection Manager (DPM) is enabled to protect the failover cluster. When you run data deduplication, it fails.
-
Assume that multiple data deduplication jobs are queued, and the job initialization needs more than five seconds. In this situation, these jobs cannot be started together.
-
Assume that you try to run deduplication on a CSV volume in a Windows Server 2012 R2 failover cluster. DPM is enabled to protect the failover cluster. You have a large file that ran data deduplication previously. When you run data deduplication again, it runs slower than expected.
-
Assume that you have a file server that is running Windows Server 2012 R2 and that data deduplication is running. When multiple write operations occur on the file from different resources (for example, from both local and remote shares), the file server may crash.
-
Assume that you try run data deduplication on a CSV volume in a Windows Server 2012 R2 failover cluster. A data deduplication process (for example, paging I/O) may take more time than expected. In this situation, the CSV volume is paused and unavailable.
Resolution
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must first install the update 2919355 on Windows Server 2012 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2012 R2 file information notesImportant Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.3.960 0.16 xxx
Windows Server 2012 R2
RTM
GDR
6.3.960 0.17 xxx
Windows Server 2012 R2
RTM
GDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012 R2" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Dedup.sys |
6.3.9600.16425 |
463,192 |
10-Oct-2013 |
16:51 |
x64 |
|
Ddppipeline.dll |
6.3.9600.17193 |
2,215,936 |
29-May-2014 |
06:24 |
x64 |
|
Ddpscan.dll |
6.3.9600.17193 |
551,424 |
29-May-2014 |
06:24 |
x64 |
|
Ddpstore.dll |
6.3.9600.17193 |
2,368,000 |
29-May-2014 |
06:27 |
x64 |
|
Ddpcli.exe |
6.3.9600.16384 |
184,320 |
22-Aug-2013 |
10:55 |
x64 |
|
Ddpeval.exe |
6.3.9600.17193 |
2,281,472 |
29-May-2014 |
10:01 |
x64 |
|
Ddpsvc.dll |
6.3.9600.16384 |
1,129,984 |
22-Aug-2013 |
10:44 |
x64 |
|
Ddpwmi.dll |
6.3.9600.16399 |
471,040 |
10-Sep-2013 |
06:12 |
x64 |
|
Dedupfilemetadata.cdxml |
Not applicable |
1,446 |
18-Jun-2013 |
15:13 |
Not applicable |
|
Dedupjob.cdxml |
Not applicable |
8,808 |
18-Jun-2013 |
15:13 |
Not applicable |
|
Deduplication.format.ps1xml |
Not applicable |
29,987 |
18-Jun-2013 |
15:13 |
Not applicable |
|
Deduplication.psd1 |
Not applicable |
1,241 |
18-Jun-2013 |
15:13 |
Not applicable |
|
Deduplication.types.ps1xml |
Not applicable |
5,459 |
18-Jun-2013 |
15:13 |
Not applicable |
|
Deduplicationprovider.mof |
Not applicable |
18,030 |
18-Jun-2013 |
15:13 |
Not applicable |
|
Dedupmetadata.cdxml |
Not applicable |
1,075 |
18-Jun-2013 |
15:13 |
Not applicable |
|
Dedupschedule.cdxml |
Not applicable |
12,547 |
18-Jun-2013 |
15:13 |
Not applicable |
|
Dedupstatus.cdxml |
Not applicable |
2,238 |
18-Jun-2013 |
15:13 |
Not applicable |
|
Dedupvolume.cdxml |
Not applicable |
9,552 |
18-Jun-2013 |
15:13 |
Not applicable |
To resolve this issue, install update rollup 2995388. For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:
2995388 October 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates For more information about date deduplication, go to the following Microsoft website:
