01-08-2012 04:10 PM
I need some help here. VSS backup operation fails in Exchange 2010 using Backup Exec 2010 R2.
Solved! Go to Solution.
01-09-2012 05:09 AM
After server restart also if you are facing issues with one database and that also repeatedly. Then I would recommend windows backup to verify the integrity of the database.
And if the database is on some other drive, verify that you have enough free space on that drive in order for VSS to work.
Please check this links for further details
http://technet.microsoft.com/en-us/library/cc734457%28WS.10%29.aspx
for vss
http://blog.chrislehr.com/2009/08/backing-up-exchange-2010-and-exchange.htm
for windows backup
01-08-2012 04:58 PM
1) What exactly are the errors?
2) Have you used a command prompt and issued the command, "vssadmin list writers"? This will tell you whether there are any VSS writer errors.
01-08-2012 05:46 PM
Thanks for your response pkh appreciated it a lot.
Apparently, I have no access to run "vssadmin list writers" on the server still have to wait for my superior to do this for me. Anyway I just wondering if the failure of VSS could possible cause of mailbox migration because 2 days ago I was able to run the backup smoothly.I found some related issue in symantec forum and the solution is to reboot the exchange server. I just wondering if there's another solution instead of that because rebooting of server will then affect of users who has a blackberry phones. Hope you could give me some advise. Thank you so much
01-08-2012 05:55 PM
For VSS writer problems, a re-boot is normally the way to solve the problem.
01-08-2012 06:23 PM
another thing... I found out today that there's only specific database that could not backup.I tried to run the database backup individually then I got successful backup, only one of DB who seems to having problem. I just wondering if it's really the VSS issue then backup should not run at all. Any thought please??
01-08-2012 10:45 PM
Hi,
VSS will affect a server in its entirety (or the resources being backed up), not specific resources. What you can do is deselect the DB in question and run the job again. If it fails, restart the Exchange server, or apply 1 of the fixes as per the TN below to reregister the VSS writer *.dll's.
http://www.symantec.com/business/support/index?page=content&id=TECH70486
Thanks!
01-09-2012 05:09 AM
After server restart also if you are facing issues with one database and that also repeatedly. Then I would recommend windows backup to verify the integrity of the database.
And if the database is on some other drive, verify that you have enough free space on that drive in order for VSS to work.
Please check this links for further details
http://technet.microsoft.com/en-us/library/cc734457%28WS.10%29.aspx
for vss
http://blog.chrislehr.com/2009/08/backing-up-exchange-2010-and-exchange.htm
for windows backup