Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Deduplication fixes for optimization job schedule and resiliency to hardware failures in Windows Server 2012 R2


View products that this article applies to.


This article describes a hotfix that improves the optimization schedule and addresses resiliency to hardware failure issues in Windows Server 2012 R2 in a Cloud Platform System environment. The hotfix has prerequisites.

↑ Back to the top


Fixes and Improvements

This update contains fixes for the following issues:
  • If an ongoing optimization job is canceled, the job may not process necessary files when it is restarted. This fix only applies to Cloud Platform System workloads.
  • Deduplication jobs may be falsely reported as not-scheduled by System Center Operations Manager.
This update also improves the management of resources to avoid the kernel stack space exhausting during certain file operations considering hardware failure, and the update improves resiliency to hardware failures when data deduplications run on a system with storage spaces.

↑ Back to the top


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

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, submit a request to 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, visit the following Microsoft website: Note 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 update, you must have update 2919355 installed in Windows Server 2012 R2.

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.
File information
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 and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" 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:
    VersionProductMilestoneService branch
    6.3.960 0.17xxxWindows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" 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 nameFile versionFile sizeDateTimePlatform
Dedup.sys6.3.9600.17630465,21610-Jan-201509:25x64
Ddppipeline.dll6.3.9600.176302,219,00810-Jan-201507:37x64
Ddpscan.dll6.3.9600.17630548,35210-Jan-201507:37x64
Ddpstore.dll6.3.9600.176302,356,22410-Jan-201507:39x64
Ddpcli.exe6.3.9600.17630272,89610-Jan-201507:46x64
Ddpeval.exe6.3.9600.176302,275,84010-Jan-201509:05x64
Ddpsvc.dll6.3.9600.176301,125,88810-Jan-201507:38x64
Ddpwmi.dll6.3.9600.17630464,89610-Jan-201507:48x64
Dedupfilemetadata.cdxmlNot applicable1,44618-Jun-201315:13Not applicable
Dedupjob.cdxmlNot applicable8,85119-Aug-201422:13Not applicable
Deduplication.format.ps1xmlNot applicable29,98718-Jun-201315:13Not applicable
Deduplication.psd1Not applicable1,24118-Jun-201315:13Not applicable
Deduplication.types.ps1xmlNot applicable5,45918-Jun-201315:13Not applicable
Deduplicationprovider.mofNot applicable18,03018-Jun-201315:13Not applicable
Dedupmetadata.cdxmlNot applicable1,07518-Jun-201315:13Not applicable
Dedupschedule.cdxmlNot applicable12,54718-Jun-201315:13Not applicable
Dedupstatus.cdxmlNot applicable2,23818-Jun-201315:13Not applicable
Dedupvolume.cdxmlNot applicable9,55218-Jun-201315:13Not applicable

Additional file information

Additional file information for Windows Server 2012 R2
Additional files for all supported x64-based versions of Windows Server 2012 R2
File propertyValue
File nameAmd64_404868dee2b7dce1e0d77e791bb3b173_31bf3856ad364e35_6.3.9600.17630_none_944bb99010697873.manifest
File versionNot applicable
File size704
Date (UTC)10-Jan-2015
Time (UTC)19:03
File nameAmd64_cd317bcb9a6f2e9c5a17fe27a9846915_31bf3856ad364e35_6.3.9600.17630_none_c6c8f2e731983239.manifest
File versionNot applicable
File size706
Date (UTC)10-Jan-2015
Time (UTC)19:03
File nameAmd64_d3cfa0ad54b2b2c5febcfa3e846ec4e3_31bf3856ad364e35_6.3.9600.17630_none_9c6b0bfbde0db5a8.manifest
File versionNot applicable
File size705
Date (UTC)10-Jan-2015
Time (UTC)19:03
File nameAmd64_microsoft-windows-dedup-filter_31bf3856ad364e35_6.3.9600.17630_none_f901effd2b8a22c8.manifest
File versionNot applicable
File size7,824
Date (UTC)10-Jan-2015
Time (UTC)09:32
File nameAmd64_microsoft-windows-dedup-pipeline_31bf3856ad364e35_6.3.9600.17630_none_4a4c2b79949c9298.manifest
File versionNot applicable
File size15,120
Date (UTC)10-Jan-2015
Time (UTC)09:33
File nameAmd64_microsoft-windows-dedup-service_31bf3856ad364e35_6.3.9600.17630_none_bfeab62f3d4684f1.manifest
File versionNot applicable
File size27,123
Date (UTC)10-Jan-2015
Time (UTC)09:33

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 3031417
Revision : 1
Created on : 1/7/2017
Published on : 2/10/2015
Exists online : False
Views : 247