Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

The Backup Exec SQL Agent was not used to create the last full, differential, or log backup of this database

Created: 15 Apr 2013 | 14 comments

Hi

Im getting the above error message when i run an incremental daly backup. The full backup runs fine. as in the subject field i get the error below

SIMSSRV EVERYTHING -Incremental -- The job failed with the following error: The Backup Exec SQL Agent was not used to create the last full, differential, or log backup of this database. You must use the SQL Agent to run a full backup before you can run a differential backup or transaction log backup.

When i look in the event viewer it gives the following info

Backup- SIMSSRV.school.local\SIMS2008
V-79-57344-867 - The last Full backup of database ccsfms was not made by this application.  Run a new Full backup, then run this job again.

V-79-57344-867 - The last Full backup of database sims was not made by this application.  Run a new Full backup, then run this job again.

V-79-57344-867 - The last Full backup of database sims-historical was not made by this application.  Run a new Full backup, then run this job again.

Im using BE12 to do the full backups.

Any suggestions good people of the community?

Operating Systems:

Comments 14 CommentsJump to latest comment

CraigV's picture

Hi,

 

Here are the SQL Best Practices...take a look and make sure you comply with them:

http://www.symantec.com/business/support/index?pag...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

VJware's picture

This happens when the log sequence number (LSN) gets reset by another backup (outside of Backup Exec). Either disable the external backups or modify the schedule in such a manner so the backup sequence do not conflict.

VJware's picture

Other backups include SQL native backups such as SQL maintenance plans, SQL dumps etc.

Another reason could be if the SQL server is virtualized. If yes, running backups via the VMware agent would also reset the LSN

harps's picture

is there anyway i can find out if there are any sql backups / maintenance plans / sql dumps etc being made from within sql?

harps's picture

Ive just found a batch file which backs up the databases. see below

@ECHO OFF
COLOR CF
ECHO YOUR SQL DATABASE IS CURRENTLY BEING BACKED UP, THIS MAY TAKE SEVERAL MINUTES
DBATTACH /BACKUP /AUTO /SERVER=simssrv\SIMS2008 /USER=sa /PASSWORD=?1234 /DATABASE=SIMS
DBATTACH /BACKUP /AUTO /SERVER=simssrv\SIMS2008 /USER=sa /PASSWORD=?1234 /DATABASE=SIMS-historical
DBATTACH /BACKUP /AUTO /SERVER=simssrv\SIMS2008 /USER=sa /PASSWORD=?1234 /DATABASE=ccsfms
PAUSE

 

Could this have any impact?

harps's picture

what do you recomend to get around this? i dont want to change from simple to full as it slows performance and storage would be an issue.

just re read your post above. If they are done at different times woud that resolve my issue?

VJware's picture

Different times in such a manner they don't conflict..Run the Backup Exec SQL  Full backup, then all incrementals from Backup Exec...Last run the SQL native backup & rerun the sequence of Backup Exec full + incr.

 

pkh's picture

Is this machine a VM and you are running VM backups between your full SQL database backups and your incremental SQL backups?  If so, you should not do so.  VM backups changes the LSN.

harps's picture

Hi

VJWare, can you elaborate on what you said

Different times in such a manner they don't conflict..Run the Backup Exec SQL  Full backup, then all incrementals from Backup Exec...Last run the SQL native backup & rerun the sequence of Backup Exec full + incr.

I understand i need to set backups up at different times. can you run through what i need to do please?

VJware's picture

You may consider this sequence

Mon - Full SQL backup using Backup Exec

Tue - Incremental SQL backup using Backup Exec

Wed - Incremental SQL backup using Backup Exec

Thu - Incremental SQL backup using Backup Exec

Fri - Incremental SQL backup using Backup Exec

After the Friday's backup using Backup Exec, run the native SQL backup (using the batch file mentioned earlier) & then the next week's schedule starts again with the full.

The idea is that the non-Backup Exec backups do not interrupt the incrementals by Backup Exec and are run after the entire chain of incrementals (using Backup Exec) is complete.