07-16-2012 02:42 AM
Hi,
We are getting the message below on our Exchange Backup...
We are running SBS 2008 FE SP2. We have all BE updates and patches installed through Live Update and are running BE 2010.
Any ideas?
Thanks.
Adam
07-16-2012 02:58 AM
Hi Adam,
First thing to do is open a command prompt and type: vssadmin list writers. Make sure all the writers are stable & running...if not, then they're in error, and you can do 1 of 2 things:
1. Restart the server in question on which this error is happening.
2. Reregister the VSS *.dlls as per the TN below:
http://www.symantec.com/business/support/index?page=content&id=TECH70486
Thanks!
07-16-2012 03:03 AM
Hi Craig,
Thanks for your reply.
All of the writers seem to be OK.
Any ideas?
Thanks
07-16-2012 03:06 AM
...mmm, if not on R3 with SP2, then upgrade to that. Not guaranteed to fix your issue, but you'll be on the latest version.
What happens if you run this job manually? Does is succeed? Does your job run during a maintenance window of some application?
Thanks!
07-17-2012 12:48 AM
I tried to manually start the job, however, this failed aswell!
It got to snapshot processing and stopped....
any ideas?
Thanks
07-17-2012 01:12 AM
Have you selected the option to let BE choose the VSS provider? Otherwise select the Microsoft provider & make sure that AOFO isn't selected in the job.
07-17-2012 01:15 AM
Yes we have tried all of this.
Its really strange!
07-17-2012 04:19 AM
I have remounted the Second Storage group... could this be the cause?
07-17-2012 05:06 AM
...it could very well be. Run a backup again and see how it runs.
07-18-2012 02:39 AM
I have been working with adam on this and can confirm that this did not work on last night backup.
The backup failed again with the error code (0xE0008516)
Any other ideas for a solution would be greatly appreciated
Cheers
07-19-2012 03:19 AM
Hi Craig,
preformed the job again after remounting the storage group, however, failed again. Myself and Micheal (Poster above) are running out of ideas!
Any more suggestions?
We are looking at preforming an upgrade to R3, but would like to ideally sort this without an upgrade as we would like to minimise the amount of down time caused.
Thanks
07-20-2012 03:07 AM
I think you only have the option for the upgrade, and/or logging a call with Symantec if you have support.
If you do log a call, and you get an answer to your issue, please post back with an update.
1 last thing you can try is to uninstall the RAWS agent on the target server, and then try a push-install to the server again, making sure to keep AOFO deselected for the installation.
Thanks!
07-20-2012 03:12 AM
Hi Craig,
Thanks for that.
Exchange is on the local server.... so no need to use the agent.
Thanks very much
07-20-2012 03:14 AM
Mmm...only 2 other suggestions:
1. Run a repair of BE using Add/Remove Programs
2. Run a repair of the BEDB using the TN below:
http://www.symantec.com/business/support/index?page=content&id=TECH67239
Thanks!
07-20-2012 03:49 AM
Hi Craig,
Thanks for the suggestions.
Will try this and will let you know!
Thanks!
07-20-2012 03:58 AM
Will these repairs require a reboot?
07-20-2012 04:03 AM
Nope, it shouldn't.
07-20-2012 04:16 AM
Hi Craig,
The server shows up as 'unknown'...
.
07-20-2012 04:18 AM
...and your services are all started up?
07-20-2012 04:30 AM
Yes. Restarted them and all seems to be OK now.
Will let you know how I get on.