backup Exec 2010 - VSS Issues

blastman

blastman

blastman

Associate
Joined
8 Mar 2007
Posts
2,176
Location
between here and there
Hi all,

I've been having some issues with a UCR server and backing up foe some time.

In a nut shell, the job fails every time stating that the shadow copy and system state could not be backed up.

Event logs on the target server show that the VSS writer failed.

vssadmin list writers, shows that the 'system' writer is stuck in the 'failed' state.

I've tried rebooting, re-adding the dll files, disabling and enabling the services, all to no avail.


Anyone got any idea how I can move this forward?

thanks in advance.
 
yep, removed, rebooted and then re-installed the agent.

I've actually moved the media server as well, this issue had followed so it must be target machine specific.

I believe I have auto detect VSS option enable, which works fine for all the other servers I'm backing up. (win2003)

I could set it to specifically use MS VSS and see what happens, but I have doubts that will make much difference.

I believe the issue really lies with the VSS writer on the server it's self.
 
What is the exact error code you are getting?

Make sure that on the target server the VSS writer service is in not in a running state and the service is set to manual.

Did you set the Backup Job to use the MS system writers?

This TechNote might help:
http://www.symantec.com/business/support/index?page=content&id=TECH87439

Have all the Backup Exec updates been installed with the remote agents pushed out and the server rebooted?
 
Not particularly helpful but we had a similar issue with backing up exchange and took it up with them & Microsoft. It never got resolved and now I we use DPM. I'll have a look later and check and see what some of the fixes we tried.

EDIT: as lmosla said need the error code really, if that's not enough and you can't talk to symantec, Run SGmon on the BE & the target server and select engine,remote agent and third party debug , ,set it to capture to a file and run the job again. Those logs should have more details of the issue.
 
Last edited:
Is this an exchange backup?

I had something similar a few years ago, i think i had to seperate the jobs out so as not to overload the exchange server / backup server.
You should try and backup a single storage group on its own and see if you can get it reliably working rather than doing the entire server in one go.
Once you get it stable and you know how long each one takes to run you can schedule them to be starting when others have finished..... Pain in back side i know.. but it helped me!
 
Actually blastman, I am a BE support tech. If you would like you can add me to your contacts and let me know if you want assistance with this.
 
You must log in or register to reply here.
Back
Top Bottom