SharePoint Backup Never Finishes

Not sure if they job is paused or is the name of the job have the word paused in it? Could it be the job is waiting on another job to finish? Do other timer jobs complete? sometimes restarting the timerjob service can help.

Screenshot?  

Sure... So as you can see it's running... I'm confused as to why it has paused in the name

Can you click on it from this page and cancel?  If not, try looking on the Job Definitions page.  Delete it if its listed.

Yep deleted the job from the Job Definitions page... but as soon as I run the Backup job again… Same thing? Any ideas?

Thanks

What does your backup job consist of?  What exactly is being backed up?

The whole farm??

Have you checked the VSS writers for errors?

vssadmin list writers

Select allOpen in new window

Also, any events in the event logs relating to VSS or backups?

http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/3f576b79-0200-4f2f-ab46-ff89728eced3

OK I think I found it… But I have no idea how to fix this (or why it happened)

The mount operation for the gatherer application c565948f-b8fe-4092-9365-04f4d4371ecc has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.

So I’m guessing it can’t mount the DB to back it up so it just hangs… I don’t know why this didn’t appear before… anyway. I may be able to find something on google… but if you know the answer let me know

Thanks for all your help :)

was this environment upgraded?  is it foundation, or full sharepoint server 2010?

Yeah no its working now; for whatever reason SharePoint SP1 did not upgrade the search database. So it could not mount it for backup.

http://social.technet.microsoft.com/Forums/pl-PL/smallbusinessserver/thread/94c5f178-f020-4d0f-ba7c-11c415d0d862

That explains it… I don’t have SBS though, only dif

So upgrading the search DB, resolved the issue?

Please follow this link for the CMD that needs to be used to upgrade you DB

So I guess me going down the upgrade path doesn't deserve any credit :-|