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-11de-865d-0014220d1366}\ 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-11de-865d-0014220d1366}\

3. Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{47c28d67-4ae3-11de-865d-0014220d1366}\. 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!
LVL 7
tolinromeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

wantabe2Commented:
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?
0
tolinromeAuthor Commented:
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?
0
wantabe2Commented:
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?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

noxchoGlobal Support CoordinatorCommented:
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.
0
tolinromeAuthor Commented:
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.
0
tolinromeAuthor Commented:
anyone have any ideas??
Can this be something Symantec backup exec is causing?
0
noxchoGlobal Support CoordinatorCommented:
What event ID do you get in EventViewer for this problem?
0
tolinromeAuthor Commented:
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.
0
noxchoGlobal Support CoordinatorCommented:
Did you search MS KB for these IDs resolutions?
0
tolinromeAuthor Commented:
yes i did,thanks,
0
tolinromeAuthor Commented:
looks like its probably something with symantec...we'll see
0
tolinromeAuthor Commented:
The problem was Symantec antivirus was causing the problem. with the vssadmin list writers command there were 8 list providers showing, after disabling the anti virus, the command then showed only one list afterwards, the vss service - which is normal.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
noxchoGlobal Support CoordinatorCommented:
What exact antivirus version? This info would be helpful for others.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.