Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Full farm backup failing

  Asked By: Pallavi    Date: May 14    Category: MOSS    Views: 3512

We're attempting a full farm backup in preparation for installing SP1,
but the backup is failing. Below are notes from a call this a.m. with
MSFT, which resulted in little more than "reboot and try again." The
backup is still failing with the following message: Object Shared Search
Index failed in event OnBackupComplete. For more information, see the
error log located in the backup directory. ... Shared Search Index
Completing backup 8/14/2008 10:49 AM Object Shared Search Index failed
in event OnBackupComplete. For more information, see the error log
located in the backup directory. WebException: The current operation
timed-out after 3600 seconds.

Also, it appears that the command line is not advancing.

::

Notes from PS call:

-----------------------------------------------------

SCOPE:

-----------------------------------------------------

Customer is running a full farm backup through the GUI and the backup is
failing with error "Backup failed for object shared search index failed
in event Onbackup".

-----------------------------------------------------

ENVIRONMENT:

-----------------------------------------------------

moss 2007

1 index server (Central Administration is located)

2 WFE

You mentioned that you performed a full farm backup last night and the
backup log shows that it failed with the error "Backup failed for object
shared search index failed in event Onbackup".

You sent the backup log to me and I have found the error listed.

A few things I wanted to try and one was to try a full backup using
STSADM:

1. Ran stsadm -o execsvcadm to pass any timer jobs that are hung.

2. Performed full backup through command line (stsadm -o backup).

3. The backup hung for awhile on search service index.

4. We looked through the application log and found many errors regarding
search.

5. We stopped the backup process from the command line 'ctrl-c'.

6. We then rebooted the index server and the errors no longer appeared.

At this point we deleted the failed backup timer job and ran the STSADM
-o backup command and the backup ran pass where it hung the last time.

::

Any ideas? We need to get a good backup; we have our outage for SP1
scheduled/approved for tomorrow.

Share: 

 

7 Answers Found

 
Answer #1    Answered By: Georgia Barr     Answered On: May 14

Is it possible that there is a search  index process running when you
attempt the backup?

 
Answer #2    Answered By: Jessi Sweet     Answered On: May 14

MS has just instructed us to stop the timer service and
retry, so we're trying that. Just want to cover all the bases in
terms of ideas because we're on a tight timeline.

 
Answer #3    Answered By: Kelvin Mckinney     Answered On: May 14

I'm 90% sure that a SharePoint backup  will pause an Index.

 
Answer #4    Answered By: Gaurav Ghosh     Answered On: May 14

I have had this more than once. Each time we eventually had to reset the Index
to get a farm  backup to complete successfully.

SP1 seems to have resolved this for those customers, however.

 
Answer #5    Answered By: Katelynn Donovan     Answered On: May 14

Given that we need the backup  to prepare for SP1,
but there it is.

 
Answer #6    Answered By: Geraldine Slater     Answered On: May 14

What does your spbackup.log file in the backup  SPBRxxxx directory  say near the
end when the error  occurs?

 
Answer #7    Answered By: Gail Richmond     Answered On: May 14

That's one of the odd things about this--the log  isn't showing any
errors. They just show in the UI.

 
Didn't find what you were looking for? Find more on Full farm backup failing Or get search suggestion and latest updates.




Tagged: