Snapshot provider error (0xE0008516): Resources specified for snapshot do not have any valid data on them. Check if files were deleted or renamed.

[Adam_Ball]

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

[CraigV]

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!

[Adam_Ball]

Hi Craig,

Thanks for your reply.

All of the writers seem to be OK.

Any ideas?

Thanks

[CraigV]

...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!

[Adam_Ball]

I tried to manually start the job, however, this failed aswell!

It got to snapshot processing and stopped....

any ideas?

Thanks

[CraigV]

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.

[Adam_Ball]

Yes we have tried all of this.

Its really strange!

[Adam_Ball]

I have remounted the Second Storage group... could this be the cause?

[CraigV]

...it could very well be. Run a backup again and see how it runs.

[TheMykeyReturns]

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

[Adam_Ball]

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

[CraigV]

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!

[Adam_Ball]

Hi Craig,

Thanks for that.

Exchange is on the local server.... so no need to use the agent.

Thanks very much

[CraigV]

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!

[Adam_Ball]

Hi Craig,

Thanks for the suggestions.

Will try this and will let you know!

Thanks!

[Adam_Ball]

Will these repairs require a reboot?

[CraigV]

Nope, it shouldn't.

[Adam_Ball]

Hi Craig,

The server shows up as 'unknown'...

.

[CraigV]

...and your services are all started up?

[Adam_Ball]

Yes. Restarted them and all seems to be OK now.

Will let you know how I get on.