tolinrome
asked on
2008 Server - VSS Errors
We have Windows Server 2008 Standard SP2 running VSS on 3 drives, D, E and F.
It's a file server and locks up and is only solved with a reboot.
The VSS runs 3 times a day and are hours apart in schedule and there is plenty of space available on the drives.
Event viewer shows these 3 VSS errors below:
1. The flush and hold writes operation on volume F: timed out while waiting for a release writes command.
2. Volume Shadow Copy Error: VSS waited more than 40 seconds for all voumes to be flushed. This caused volume \\?\Volume{47c28d67-4ae3-1 1de-865d-0 014220d136 6}\ to timeout while waiting for the release-writes phase of shadow copy creation. Trying again when disk activity is lower may solve this problem.
Operation:
Executing Asynchronous Operation
Context:
Current State: flush-and-hold writes
Volume Name: \\?\Volume{47c28d67-4ae3-1 1de-865d-0 014220d136 6}\
3. Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{47c28d67-4ae3-1 1de-865d-0 014220d136 6}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000], Flush[0x00000000], Release[0x00000000], OnRun[0x80042314].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
We have also Symantec Backup Exec running on another server that is backuping up these drives, but NOT during the VSS Snapshots.
Any help? Thanks!
It's a file server and locks up and is only solved with a reboot.
The VSS runs 3 times a day and are hours apart in schedule and there is plenty of space available on the drives.
Event viewer shows these 3 VSS errors below:
1. The flush and hold writes operation on volume F: timed out while waiting for a release writes command.
2. Volume Shadow Copy Error: VSS waited more than 40 seconds for all voumes to be flushed. This caused volume \\?\Volume{47c28d67-4ae3-1
Operation:
Executing Asynchronous Operation
Context:
Current State: flush-and-hold writes
Volume Name: \\?\Volume{47c28d67-4ae3-1
3. Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{47c28d67-4ae3-1
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
We have also Symantec Backup Exec running on another server that is backuping up these drives, but NOT during the VSS Snapshots.
Any help? Thanks!
I think there have been some major Win 2008 VSS updates rolled out in the past few months. Try doing a Windows Update on that server & see if the errors go away. Also, are you running DHCP on this server?
ASKER
yeah, I already checked that and there's only one update pending, a security update. Unless there are certain patches that dont come from MS Updates and you can point me to them?
Hmmm....Try killing the VSS jobs & see if the lock ups go away first. If it does, you could then enable VSS on one drive at a time to see which volume is causing the lock ups. You may have disk issues. What other things other than a file server do you have running on this box?
What does check of F: drive give you? Have you ever tried to check it via CHKDSK /f? Sometimes the problem close could be on the surface.
ASKER
cant kill the vss jobs, only delete them basically then re-create them but then I would lose all the backups.
no checkdisk on a huge san, wouldnt be possible.
no checkdisk on a huge san, wouldnt be possible.
ASKER
anyone have any ideas??
Can this be something Symantec backup exec is causing?
Can this be something Symantec backup exec is causing?
What event ID do you get in EventViewer for this problem?
ASKER
Event ID 12298 , 12340, 12298 and 24
Ive followed the solutions but some dont even pertain, I'm not out of space on the LUN and disk activity isnt very high. I called Symantec and they said it was a MS issue and MS is 'looking into it' - which can take forever.
Ive followed the solutions but some dont even pertain, I'm not out of space on the LUN and disk activity isnt very high. I called Symantec and they said it was a MS issue and MS is 'looking into it' - which can take forever.
Did you search MS KB for these IDs resolutions?
ASKER
yes i did,thanks,
ASKER
looks like its probably something with symantec...we'll see
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What exact antivirus version? This info would be helpful for others.