Thanks for the quick response and sorry for the “German” - I post some translations/explanations from the net below. I tried retrospect.exe and VSSVC.exe as trusted processes but to no avail.
I am not sure if there is a specific volsnap task - at least it escapes me.
I will try the “exclusion” list and report back.
From MS TechNet for Volsnap 9
Explanation
This event indicates that Volume Snapshot Driver was not able to allocate enough system resources to perform an operation.
Cause
Possible causes include:
The system is low on memory.
The system is low on CPU resources.
The system has a high disk I/O load.
User Action
Do one or more of the following:
Monitor the system resources (CPU usage and disk I/O performance) to identify what is causing the system to be low on resources.
Schedule Volume Shadow Copy Service or other operations during the least busy periods for the system.
Move the Diff Area to a different, dedicated volume.
From Google for VSS 12341
Volume Shadow Copy Warning: VSS spent 0x000000000000003c seconds trying to flush and hold the volume \\?\Volume{e2be8753-0df6-11e0-8ce7-806e6f6e6963}\. This might cause problems when other volumes in the shadow-copy set timeout waiting for the release-writes phase, and it can cause the shadow-copy creation to fail. Trying again when disk activity is lower may solve this problem.
Operation:
Executing Asynchronous Operation
Context:
Current State: flush-and-hold writes
From MS TechNet for VSS 12297
Explanation
This event indicates that Volume Shadow Copy Service was not able to allocate enough system resources to perform an operation.
Cause
Possible causes include:
The system is low on memory.
The system is low on CPU resources.
The system has a high disk I/O load.
User Action
Do one or more of the following:
Monitor the system resources (CPU usage and disk I/O performance) to identify what is causing the system to be low on resources.
Schedule Volume Shadow Copy Service or other operations during the least busy periods for the system.
Move the Diff Area to a different, dedicated volume.
I am 100% sure that there is no specific high volume activity on the hard disk. My best guess is, something blocks the creation of shadow copies and that causes a time out.
Ta
Kobe