This article describes an issue that occurs when data deduplication is enabled in Windows Server 2012 R2 or Windows Server 2012. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

Symptoms

Assume that you have a data deduplication-enabled volume that contains a chunk store in Windows Server 2012. You back up some optimized files by using the Data Deduplication feature in Windows Server 2012. When you try to restore an optimized file, this issue occurs.

Note This issue also occurs in Windows Server 2012 R2 in which the volumes have the data deduplication feature enabled. This Windows Server 2012 R2 is upgraded from Windows Server 2012.

Cause

This issue occurs because certain optimized files are backed up incorrectly in Windows Server 2012 or Windows Server 2012 R2. Therefore, the deduplication pipeline sets the body size of the chunk store to zero. When you try to selectively restore a file, the body size of the chunk store cannot be determined, and the restore fails.

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:

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 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.

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:

    Version

    Product

    Milestone

    Service branch

    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

Ddpbackup.dll

6.3.9600.17542

535,552

24-Nov-2014

23:20

x64

Windows Server 2012 file information and notes

Important Windows 8 hotfixes and Windows Server 2012 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/Windows Server 2012" 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.2.920 0.21xxx

    Windows Server 2012

    RTM

    LDR

  • 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" 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

File name

File version

File size

Date

Time

Platform

Ddpbackup.dll

6.2.9200.21310

499,712

24-Nov-2014

23:37

x64

Ddppipeline.dll

6.2.9200.21310

2,002,432

24-Nov-2014

23:37

x64

Ddpscan.dll

6.2.9200.21310

585,216

24-Nov-2014

23:37

x64

Ddpstore.dll

6.2.9200.21310

2,256,896

24-Nov-2014

23:37

x64

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 property

Value

File name

Amd64_eacf621fb5c515f9f841708e63741ac9_31bf3856ad364e35_6.3.9600.17542_none_a87c32f3a136081b.manifest

File version

Not applicable

File size

704

Date (UTC)

25-Nov-2014

Time (UTC)

20:56

Platform

Not applicable

File name

Amd64_microsoft-windows-dedup-backup_31bf3856ad364e35_6.3.9600.17542_none_084f44206d3442ba.manifest

File version

Not applicable

File size

4,136

Date (UTC)

25-Nov-2014

Time (UTC)

00:22

Platform

Not applicable

Additional file information for for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012

File property

Value

File name

Amd64_595aa5068032ec479bcfb5e8b722cdbe_31bf3856ad364e35_6.2.9200.21310_none_6fc133d653c677b8.manifest

File version

Not applicable

File size

706

Date (UTC)

25-Nov-2014

Time (UTC)

06:23

Platform

Not applicable

File name

Amd64_eb84f598679f62ca0f2de57bb2c2f466_31bf3856ad364e35_6.2.9200.21310_none_630e92268d9109ee.manifest

File version

Not applicable

File size

704

Date (UTC)

25-Nov-2014

Time (UTC)

06:23

Platform

Not applicable

File name

Amd64_microsoft-windows-dedup-backup_31bf3856ad364e35_6.2.9200.21310_none_710291c33c089411.manifest

File version

Not applicable

File size

4,136

Date (UTC)

25-Nov-2014

Time (UTC)

02:29

Platform

Not applicable

File name

Amd64_microsoft-windows-dedup-pipeline_31bf3856ad364e35_6.2.9200.21310_none_b2f6a7de63773567.manifest

File version

Not applicable

File size

15,120

Date (UTC)

25-Nov-2014

Time (UTC)

02:29

Platform

Not applicable

Status

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

References

See the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×