You are currently offline, waiting for your internet to reconnect

FIX: Event ID 833 if I/O write operation occurs during a VSS snapshot backup in SQL Server 2008 R2

Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 fix release.
Symptoms
Assume that you run an application that performs a Microsoft SQL Server Volume Shadow Copy Service (VSS) snapshot backup in Microsoft SQL Server 2008 R2. If an I/O write operation occurs during the backup process, an event ID 833 might be logged in the Application event log, and the following message might be logged in the SQL Server error log:
SQL Server has encountered <n> occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [<full path of file>] in database [<database name.>] (<dbid>). The OS file handle is <file handle>. The offset of the latest long I/O is: <offset in hexadecimal>
Note The disk performance monitor counters do not show a disk performance issue.
Cause
This issue occurs because an internal member of the overlapped structure is not initialized correctly when the I/O operation is frozen by the snapshot backup. Additionally, the event ID 833 incorrectly indicates that there is a disk performance issue.
Resolution

Cumulative update information

Cumulative Update 4 for SQL Server 2008 R2 SP2

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP 2, click the following article number to view the article in the Microsoft Knowledge Base:
2777358 Cumulative update package 4 for SQL Server 2008 R2 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 SP 2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2756574 Cumulative update package 9 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Workaround
To work around this issue, use SQL Server native backup instead. The native backup does not freeze the I/O operation.
Properties

Article ID: 2708012 - Last Review: 12/17/2012 19:36:00 - Revision: 5.0

Microsoft SQL Server 2008 R2 Datacenter, Microsoft SQL Server 2008 R2 Enterprise, Microsoft SQL Server 2008 R2 Developer, Microsoft SQL Server 2008 R2 Standard, Microsoft SQL Server 2008 R2 Express, Microsoft SQL Server 2008 R2 Web, Microsoft SQL Server 2008 R2 Workgroup

  • kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2708012
Feedback
= 1; var Route = "76500"; var Ctrl = ""; document.write(" uguay - Español
대한민국 - 한국어
España - Español
Paraguay - Español
Venezuela - Español
style="display: none; " src="https://c1.microsoft.com/c.gif?DI=4050&did=1&t="> var Route = "76500"; var Ctrl = ""; document.write(" d')[0].appendChild(m);" onload="var m=document.createElement('meta');m.name='ms.dqp0';m.content='false';document.getElementsByTagName('head')[0].appendChild(m);" src="http://c1.microsoft.com/c.gif?"> >