we had this problem when sql server did backup of database and third(production) database showed this error and restart sql service.
It was one times and another backups are ok without problem from this time.
I found in our monitoring system Latches wait times in this time.
Next I checked this link http://support.microsoft.com/kb/2137408
When I was thinking about this, it is possible that somebody executed very poor query and during this backup the disk fall down ?
or it is possible that Database Collection caused this ? I have set for DiskUsage, Query statistics and Server Activity. For example that this job for collection was executed in same time like database backup and wrote to disk in same time...( I have MDW Database on same disk )
Because we have externist consultant and he said that probably caused one job which is execute one per minute, but I am not sure, because this job is almost without logical reads and scan very small table ( tracking table, without add rows = just update ) .
Next is that we have more worst jobs, which have more logical reads and executed every 30sec. So I dont think that it caused this jobs, but for sure we turned off..
And why sql service was restarted ? I found this problem because I wanted select statistics for report and it was restarted.
in error log i found just this
2014-03-21 18:07:43.41 spid8s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\USERDB\MCS_MESDB_1.ldf] in database [MCS_MESDB] (8). The OS file handle is 0x0000000000000D08. The offset of the latest long I/O is: 0x000002e70cb000
Thanks a lot,
How to post data/code on a forum to get the best help: Option 1
/ Option 2