Highlighted
AaronQ1
1 Copper

More Avamar / VSS errors

Hello All,

We are experiencing another combination of Avamar errors associated with certain Microsoft Volume Shadow Copy Service (VSS) errors logged in system and application event logs on our Windows 2003 SP2 servers. In Avamar logs we find errors 5139 & 5325 and in event logs we see Event ID/s: 12298 & 12310 in Application log in System logs Event ID 8 is logged for each physical volume the  Interesting part is these errors seem to disappear the next or the following day only to reappear a few days later exactly the same way. Some times it takes up to two weeks for these errors to reappear on the same server. We have already applied Microsoft KB940032 and Patch MS940349-V3. No luck so far…..Any ideas or suggestions?

Thank You!

Event ID description:

Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 8
Date:  4/28/2010
Time:  7:09:22 PM
User:  N/A
Computer: SDSCOA02WA20001
Description:
The flush and hold writes operation on volume C: timed out while waiting for a release writes command.

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12298
Date:  4/28/2010
Time:  7:09:23 PM
User:  N/A
Computer: SDSCOA02WA20001
Description:
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume C:\\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000], Flush[0x00000000], Release[0x80042314], OnRun[0x00000000].

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12310
Date:  4/28/2010
Time:  7:09:22 PM
User:  N/A
Computer: SDSCOA02WA20001
Description:
Volume Shadow Copy Service error: The shadow copy could not be committed - operation timed out. Error context: DeviceIoControl(\\?\Volume{434cb752-e55d-11d8-8ec2-806e6f6e6963} - 00000130,0x0053c010,00B10148,0,002D7FF8,4096,[0]).

0 Kudos
1 Reply
DaveH8888
2 Bronze

Re: More Avamar / VSS errors

Sounds like high or constant disk I/O when the backup tries to snapshot the volume... run pefrmon on the server and monitor the PhysicalDisk "Disk Transfers/sec" "Disk Writes/sec" and "Disk Reads/sec"

if you have constant or high I/O when trying to create the snapshot it may fail.

0 Kudos