BackupExec 2010 R2 job failed - vss writer failed

Hi ,

MS Exchange server is a virtual machine  on hyper-v server 2008 R2. Backup exec running on windows server 2008 R2.

Selected the MS Exchange server and selected the entire Information Store box when making selections. Backup
job failed last night with the following error. Is there a solution to get the MS Exchange server backed up successfully?

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Started services

Rebooted exchange server and re-installed RAWS SP1. Checked to see whether the VSS services were running and all working now.

View solution in original post

7 Replies
Highlighted

Have you checked the VSS

Have you checked the VSS writer status on the Exchange Server, all the writers should be stable 

without error message.

Highlighted

How do i check

How do i check the VSS writer status on the Exchange Server  ?

Highlighted

open command prompt and type

open command prompt and type vssadmin list writers

Highlighted

Hi, If vss writer showing

Hi,

If vss writer showing failed

just restart the exchange server writer issue will get fix..

 

Regards

Highlighted

Couple of suggestions: You

Couple of suggestions:

You might want to seperate out your exchange stuff into its own job, which may reduce some troubleshooting factors and troubleshooting in general.  I think this is recommended by Symantec as well.

Are you telling the job to use MS VSS writers?  Maybe switch between the automatic setting and the microsoft setting.

Not sure about server 2008, but for 2003 I remember some VSS updates that didnt come through WSUS, so there might be some updates for the writers in 2008 that you don't get without explicitly looking for them.

 

...My 2 cents

Highlighted

When I had similar problem

When I had similar problem with Exchange 2003, the solution was to restart the Information Store service. Rebooting the whole server didn't help, but recycling services did.

Highlighted
Accepted Solution!

Started services

Rebooted exchange server and re-installed RAWS SP1. Checked to see whether the VSS services were running and all working now.

View solution in original post