Video Screencast Help

Sharepoint Server farm Backup errors

Created: 15 May 2013 | 6 comments
BEI's picture

Hi All,

I'm having backup issues with Sharepoint 2010 Server farm.

I'm using BE2012 SP1 etc.. Sharepoint 2010 on Windows 2008R2

the error is V-79-57344-5890 - The object was not found, or could not be accessed (Share point backup).

Backup- WebApplication\Content-DB 1 (Server\SP_INTERNET\SharePoint_AdminContent_5cedffe2-ea6b-4ef5-9c2b-5632597f9ef2) SharePoint_AdminContent_5cedffe2-ea6b-4ef5-9c2b-5632597f9ef2 in use - skipped.

All the Databses are there and have the correct access acording to the credential test.


Operating Systems:

Comments 6 CommentsJump to latest comment

VJware's picture

Does this occur during full or incr/diff backups ?

Is AOFO enabled or disabled in the backup job properties ? Lastly, is this a GRT enabled backup ?

BEI's picture

Hi VJware,

The AOFO is Disabled and the GRT is Enabled.

Sorry, forgot to add that it's on all backups, full, inc and Diff


VJware's picture

As a test, enable AOFO & choose explicitly the system vss provider & rerun the Full + Incr/Diff.

BEI's picture


That has solved one of my isses, thanks for that.


Sush...'s picture

Hello there,

   You may also want to refer to following technotes : SharePoint backups fail with "The object was not found, or could not be accessed" : Backup of Sharepoint 2010 fails with error 'Unable to lock the Microsoft SharePoint Portal Farm' : Sharepoint GRT Incremental or Differential backup shows exception - File \WSS_Content was not found, or could not be accessed.



Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

dfeifer's picture

I too am having the exact issue that BEI is having with the same info he listed only mine is associated with the file:

\\SP01\C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\SP01-20130516-0026.usage in use -skipped

For me this only happens on incrementals and even then it is random. Go a week without an issue then mon,tues,thurs. have the issue then skip 4 days. etc.