Video Screencast Help

Backup Exec claims that a full backup of SQL was not done

Created: 21 May 2013 • Updated: 21 May 2013 | 2 comments

Hi.

Our system has just recently been set up. It's a fairly standard GFS-solution, using a tapelibrary. We have three parallel systems running that are the same in all but names. Two of them work like a charm but the third generates a strange error.

Today I checked the daily backup and they all had gone through except our daily SQL-backup. That job failed due to "SQL agent was not used to create the last full, differential or log backup of this database". The error code it generates is E0000363.

However, the full backup of SQL HAS been running with success using SQL agent, twice. Also, the first daily backup succeeded as it should, but the following did not.

Anyone got any hints?

Operating Systems:

Comments 2 CommentsJump to latest comment

pkh's picture

Check that you are not doing one of the following

1) a VM backup

2) a backup using a SQL maintenance plan.

Also use the method in the solution section of this document to check which application did the last backup

http://www.symantec.com/docs/TECH58674

Wolfclaw's picture

I'v checked the article and it does indeed seem some other process did the backup instead. How ever I can't seem to find which application that is responsible. All I can find are a few rows with 'NULL'-strings.